• Author / Uploaded
• Assou Ouzennou

Citation preview

Single RAN, Rel. SRAN 17A, Operating Documentation Pre-release 2, Issue 01

SBTS Faults and Alarms DN09218837 Issue 04 Approval Date 2017-10-27

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.

This document is intended for use by Nokia customers (“You”) only, and it may not be used except for the purposes define agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be 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 welcome Your comments as part of the process of continuous improvement of the documentation.

developmen

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 th document. But, Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia d 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, BU OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN 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, and they are mentioned for identification purposes only. Copyright © 2017 Nokia. All rights reserved. Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger.

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, and they are mentioned for identification purposes only. Copyright © 2017 Nokia. All rights reserved. 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 environmen 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.

cumentation,

cified

pt for the purposes defined in the rt of this document may be used,

nt applicable ocument in

d You f continuous

development and

ments olely on such the content rors that You identify in this n of such error(s). Nokia does not

TED TO , O THE S, UENTIAL S INTERRUPTION, BUSINESS ORMATION IN IT, EVEN IN THE

disclosed

cument s only.

cument s only.

.

d

ces. ner, safer environment. Please of our products and their

vices we

1. Introduction 1.1 Overview of BTS alarms and faults

This document describes the handling of base station (BTS) alarms and faults. The base station software uses these alarm and faults as a basis for internal diagnosis and fault reporting through the OMS to the Operations Support System (OSS) an the BTS Site Manager.

1.2 Handling of BTS alarms and faults

Base station alarm handling is based on unit or module state information. It prevents the sending of unnecessary alarms by checking and updating unit states. Fault messages come either from hardware devices or software components. The faults are system or hardware specific. The Fault Diagnosis System creates upper network alarms, which are based on an analys of the faults, and sends them to the BTS Site Manager. In addition NetAct is used for handling the BTS alarms.

The BTS is able to maintain alarm handling after it has been commissioned and 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 is unable to set the time using the NTP server, the default tim (1.1.2004) will be used. BTS transmission alarms The base station transmission alarms (7665) are reported towards OMS or NetAct. The transmission equipment uses the base station interface. Therefore, retrieval of the alarm information is mapped either in the OMS or in the NetAct to distinguish between the alarms by using the fault ID. Instructions for solving problems When starting to solve a problem, first refer to the instructions given in the individual alarm descriptions.

Verify the configuration of a BTS by checking the commissioning, cabling and correct installation of the modules at the BTS Make sure the environment does not cause the fault.

If an active alarm is a 'Start' alarm, a unit block/unblock (if supported by the unit) or a site reset is required to cancel it. If the site reset or unit block/unblock does not help, replace the faulty unit or module. See the fields 'Fault source' and 'Instruction in the corresponding alarm description.

Blocking and unblocking The 'Cancel' alarms are always sent to hosts (LTE BTS Site Manager). When the unit or cell is in a blocked state, the 'Start alarms are only sent to LTE BTS Site Manager.

When a unit or cell is unblocked, all the active alarms related to the unblocked unit, module, or cell are automatically sent to the hosts.

2. How to read this excel report The excel report provides a full information on faults and alarms. It shows the full set of fault and alarm attributes including the change information. The excel report consists of two main sections: - Alarm List - Fault List The alarms and faults are listed by numbers in an ascending order.

2.1 Alarm List This section shows the full alarm information including the following items: - alarm number - alarm name - meaning of the alarm - instructions - list of related faults - clearing information - change information

2.2 Fault List

- alarm name - meaning of the alarm - instructions - list of related faults - clearing information - change information

2.2 Fault List This section shows the full alarm information including the following items: - fault ID - fault name - meaning of the fault - instructions - list of related alarms - change information

2.3 Field descriptions

Field descriptions are provided in the second row of Alarm List and Fault List sections. Use fold (-) and unfold (+) buttons o the left panel to respectively hide and show the field descriptions.

2.4 Change information Change information is a part of Alarm List and Fault List sections and is available in the following ways: 1. Definition on whether the fault/alarm is new, removed. That definition is provided in the following columns: - Changes between issues ... which shows the changes since the previous issue of the document. - Changes between releases ... which shows the changes since the latest issue of the document in the previous product release. If the cell is empty, the alarm/fault is not changed, nor new, nor removed. Note that removed alarms/faults are listed in the very bottom and they are marked with red font. Filters are enabled for convenient browsing of the change categories.

2. Detailed change information showing the current and previous values of parameter attributes. That information is provide in the following columns:

- in issue ... which shows the value in the previous issue of the document. - in release ... which shows value in the latest issue of the document in the previous product release. The columns are grouped into attribute-specific sections for structured and convenient view. Use unfold (+) and fold (-) buttons in the top bar to browse the attribute-specific change details. Use unfold all (2) and fold all (1) buttons on the left hand side of the top bar to respectively show and hide the change details for the whole report.

Note that for all faults/alarms except new and removed ones, the field values for previous issue and previous release are always provided to show a total history information. Additionally, the changed attributes of faults/alarms are highlighted with grey color. Highlights are enabled to specify whether there is a change between issues or releases.

tion software uses these alarms tions Support System (OSS) and

ding of unnecessary alarms by ftware components. The faults , which are based on an analysis

gured state. During the start-up, ault diagnosis starts after the the NTP server, the default time

smission equipment uses the MS or in the NetAct to

escriptions.

tion of the modules at the BTS.

set is required to cancel it. If the s 'Fault source' and 'Instructions'

is in a blocked state, the 'Start'

or cell are automatically sent to

and alarm attributes including

old (-) and unfold (+) buttons on

wing ways:

lowing columns:

ment. ment in the previous product

ont.

tes. That information is provided

ment. n the previous product release.

Use unfold (+) and fold (-) old all (1) buttons on the left rt.

ue and previous release are ults/alarms are highlighted with eases.

Note: See the How to Read This Report tab for instructions on the usage of Alarm List Changes between issues 16.10 and 17A

Alarm Number

Alarm Name

Changed

7100

BASE STATION HARDWARE PROBLEM

Changed

7101

BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

Changed

7102

BASE STATION RESOURCE BLOCKED BY USER

Changed

7103

BASE STATION EXTERNAL ALARM NOTIFICATION

Changed

7107

BASE STATION CONNECTIVITY PROBLEM

Changed

7108

BASE STATION SYNCHRONIZATION PROBLEM

Changed

7109

BASE STATION SECURITY PROBLEM

Changed

7110

BASE STATION LICENSE LIMITATION

Changed

7111

BASE STATION SOFTWARE MANAGEMENT PROBLEM

Changed

7112

BASE STATION CONFIGURATION PROBLEM

Changed

7113

BASE STATION ANTENNA LINE PROBLEM

Changed

7114

CELL SERVICE PROBLEM

Changed

7115

BASE STATION INFORMATION

Changed

7116

BASE STATION SERVICE PROBLEM

Changed

7208

LOCAL BLOCK

Changed

7600

BCF FAULTY

Changed

7602

BCF NOTIFICATION

Changed

7606

TRX FAULTY

Changed

7607

TRX OPERATION DEGRADED

Changed

7995

MAINS BREAKDOWN WITH BATTERY BACKUP

Changed

61022

BFDGRP-$BFDGRPID down

Changed

61028

LOF on $UNIT, $INTERFACE

Changed

61029

LOS on $UNIT, $INTERFACE

Changed

61030

Dead Peer Detected

Changed

61040

Interface under test on $UNIT, $INTERFACE for $LOOPTIMEOUT minutes

Changed

61104

EBER on $UNIT, $INTERFACE

Changed

61150

LOMF on $UNIT, $INTERFACE

Changed

61151

AIS on $UNIT, $INTERFACE

Changed

61152

RDI on $UNIT, $INTERFACE

Changed

61250

IPCP failure

Changed

61251

LCP failure

Changed

61252

PPP interface down

Changed

61605

BFD-$BFDID down in ingress

Changed

61606

BFD-$BFDID down in egress

Changed

61607

Auto-negotiation mismatch on $UNIT, $INTERFACE

Changed

61610

RTT threshold crossed on TWAMP$TWAMPID

Changed

61611

PLR threshold crossed on TWAMP$TWAMPID

Changed

61622

MLPPP link degrade

Changed

61632

Dup Addr detected$DUPLICATEIPV6ADDRESS

Changed

61639

IPsec emergency bypass active

Changed

61641

IP Traffic Capturing ongoing on $UNIT, $INTERFACE, $MACADDRESS

Changed

61643

IPsec tunnel switchover

Changed

61644

IKE authentication failure

Changed

61645

IKE SA failure

Changed

61646

IPSec SA failure

Probable Cause

Event Type

Default Severity

Indeterminate

Equipment

Critical Major

Indeterminate

Quality of service

Warning

Indeterminate

Quality of service

Critical Major Minor

Indeterminate

Environmental

Critical Major Minor

Indeterminate

Communications

Critical Major

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Minor

Indeterminate

Quality of service

Critical Major

Indeterminate

Quality of service

Minor

Indeterminate

Fault Dependent

Critical

Indeterminate

Communications

Minor

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Environmental

Minor

Indeterminate

Communications

Critical

Indeterminate

Communications

Critical

Indeterminate

Communications

Critical

Indeterminate

Communications

Major

Indeterminate

Communications

Minor

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Critical

Indeterminate

Communications

Major

Indeterminate

Communications

Critical

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Minor

Indeterminate

Communications

Major

Indeterminate

Communications

Minor

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Meaning

Effect

A fault has been detected in the base station hardware. The problem causes a base station unit/service to be degraded or faulty. Check the reason for the fault from the The base station device or base station itself is supplementary text field of the alarm. being automatically reset to recover from a fault. Check the reason for the fault from the supplementary text field of the alarm.

The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries. The effect of the alarm on the Network Element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries.

The service/device has been blocked by the user. The service/device is blocked by the user. It is Check the reason for the fault from the not possible to establish phone calls through the supplementary text field of the alarm. blocked cell, module or BTS. This is an external user-defined alarm. The alarm, including the alarm text, is defined by the user during external alarm configuration. Check the reason for the fault from the supplementary text field of the alarm. A fault has occurred in the base station connection to the core network elements or neighbor elements (other base stations connected by radio network or connected physically in radio sharing or CRAN (Centralize A fault has occurred in the base station Radio Access Network) configurations). synchronization. For example, the base station The problem causes a base station unit/service reference clock signal is lost or is to be degraded or faulty. unstable/inaccurate, or the estimated phase error Check the reason for the fault from the in holdover is too big to support some services. A fault has occurred in the station security supplementary text field of base the alarm. The problem causes a base station unit/service functionality. to be degraded or faulty. The problem causes a base station unit/service Check the reason for the fault from the to be degraded or faulty. supplementary text field of the alarm. Check the reason for the fault from the Capacity limitation (or limitations) has occurred in supplementary text field of the alarm. the base station due to missing license. The problem causes a base station unit/service to be degraded or faulty. Check the reason for the fault from the A fault has occurred in the base station software supplementary text field of the alarm. management, such as software download/update/activate/fallback problem, file consistency problem, file corruption problem, etc. It may be also reported when base station One or more base station configuration software is incompatible with detected hardware. parameters have been specified incorrectly, or The problem causes a base station unit/service are inconsistent with the actual configuration. The to be degraded or faulty. alarm is also reported when base station Check the reason for the fault from the property file does not contain properties of supplementary text field of the alarm. detected hardware or reported due to some hardware configuration issues, for example, unsupported hardware is detected, cables to radio modules are too long, there is too big of a difference in the length of parallel cables, etc. The problem causes a base station unit/service to be degraded or faulty. Check the reason for the fault from the supplementary text field of the alarm.

The effect of the alarm depends on the purpose that was configured for the user-defined alarm input in the BTS. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries. The effect of the fault on the network element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SRAN System Libraries.

A fault has occurred in an antenna line or antenna line device. It may be a hardware or software failure. The problem causes a base station unit/service to be degraded or faulty. A fault has occurred in the cell service. For Check the reason for the fault from the example: MIMO (Multiple Input Multiple Output) supplementary text field of the alarm. does not work, interferences in the cell are detected, beamforming calibration fails in the cell, there are not enough internal processing A fault has occurred in the base station service resources in the base station to support the cell, that does not affect basic services of the base there is not enough hardware detected to setup station, or the operator is notified about the cell, etc. suggested manual intervention. Each fault with The problem causes a cell service to be minor or warning severity, that is, fault that has A fault hasoroccurred degraded faulty. in the base station service no impact on basic base station services, no that affects basic services of the base Check the reason for the fault from thestation. If a matter if it is hardware, software, configuration, fault may have various causes,(for supplementary text fieldroot of the alarm. example, synchronization etc., is reported as BASE hardware problem, software problem or STATION INFORMATION. The only exception to configuration problem, etc.), this type of alarm is TRX hasthe been blocked byfaults user 61xxx: via BTS Element this are transmission Minor and reported because more specific alarm Manager. warning severity transmission faults are reported assignment is not possible. as transmission alarms instead of BASE The problem causes a cell service to be STATION INFORMATION alarms. degraded or faulty. Check the reason for the fault A fault faults) has occurred in of thethe BCF. from the(or supplementary text field alarm. For details, refer to GSM/EDGE BSS Operating Documentation.

The effect of the fault on the functioning of the network element depends on the fault description. For more information, see the base station fault description in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see the base station fault description in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see the base station fault description in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see the base station fault description in SRAN System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SBTS System Libraries. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SBTS System Libraries. A fault has occurred, which either does not affect The effect of the fault on the functioning of the the SBTS operation, or the fault does not allow network element depends OSC(Orthogonal Sub Channels)/DFCA(Dynamic on the fault description. For more information, Frequency and Channel Allocation) feature to see base station fault work. descriptions in SBTS System Libraries. A critical fault has occurred on a TRX. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SBTS System Libraries. A fault has degraded the operation of TRX. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in SBTS System Libraries. Main power is lost and the SBTS is running on The effect of the fault on the functioning of the Battery backup. network element depends on the fault description. For more information, see base station fault descriptions in SBTS System Libraries. The alarm is raised if the monitored service is The communication link between the local SBTS unavailable when for example all network paths and the BFD peer is defective. No are unavailable. This implies that all individual communication is possible. BFD sessions of the respective group represented by $BFDGRPID are erroneous. This loss of frame alarm is raised when the local Possible impact on the connections over this receiver is unable to detect the frame alignment interface: Example(s) for alarm text: BFDGRP-10 down word of the E1 signal. All other transmission - no calls are possible alarms related to this signal are suppressed. - loss of remote management access to other $UNIT indicates the affected module from network elements Equipment Management (last element of the - loss of synchronization if the interface is used DN). E.g. TRMOD-1. as a synchronization source $INTERFACE indicates the interface on the module following the labeling on the frontplate of the real HW or the corresponding parameter in the Management Model. E.g. EIF1, IF1 Example(s) for alarm text: "LOF on TRMOD-1, IF2"

This alarm is raised when either no or an incompatible signal is received on the interface referenced in the alarm text. $UNIT indicates the affected module from Equipment Management (last element of the A dead peer was detected in one of the IPsec DN). E.g. SMOD-1. associations of the SBTS. $INTERFACE indicates the interface on the There is no response to the requests sent to the module following the labeling on the frontplate of peer, neither during the IKE the real HW or the corresponding parameter in SA setup, the IPsec SA setup, nor during DPD. This alarm is raised if a loopback has been the Management Model. Note: When IPsec backup tunnel feature is configured by a management application on the E.g. EIF1, IF1 enabled, this alarm is not raised interface mentioned in the alarm text. due to failures when trying to setup primary IPsec $UNIT affectedthe module from With anindicates Ethernetthe interface, physical Ethernet tunnel in "Secondary_Active_Probing_Primary" Equipment Management (last element of the link is detected to be down. All other transmission This state.alarm is raised when the measured bit error DN). E.g. TRMOD-1. alarms related to threshold this signalvalue are suppressed. rate exceeds the of BER-3 (10E$INTERFACE indicates the interface on the 3). module following the labeling on the frontplate of Probable causesthe for affected Ethernet interfaces: $UNIT indicates module from the real HW oristhe corresponding parameter in -Equipment a cable/fiber cut or there is no cable/fiber Management (last element of the This loss oftomultiframe alarm is raised if the the Management Model. connected the interface DN). E.g. TRMOD-1. interface referenced insignal the alarm text has lost the E.g. IF1 -$INTERFACE the EIF1, electrical/optical is excessively indicates the interface on the multiframe alignment. $LOOPTIMEOUT indicates the time period in attenuated module following the labeling on the frontplate of $UNIT indicates the the affected from minutes after which inserted loopback -the thereal port at the connected farmodule end node is shall HW or the corresponding parameter in Equipment Management (last element of the terminate automatically. switched off This alarm is raised when an alarm indication the Management Model. DN). E.g. TRMOD-1. -signal the EIF1, advertised capabilities withby autois received. This signal is generated an E.g. IF1 technology $INTERFACE indicates the at interface on thelink do Example(s) for alarm text: negotiation both devices Ethernet intermediateof PDH device in thethe forward direction module following the on labeling on theIF2 frontplate "Interface under test TRMOD-1, for 2 of not match because itcauses: detects a problem in its received Probable the real HW ortechnology the corresponding parameter in minutes" -signal. the Ethernet at both devices the -This the alarm signal islevel is too lowa(connectors or at cables raised when remote defect the Management Model. Ethernet link is forced manually and not are dirty, electrical connectors indication received. It is sentor bycables the are E.g. EIF1, isIF1 compatible AIS defect is detected when the incoming signal corroded) intermediate or theoffar-end equipment because it -has the remote peer link iscable not autoor less zerosan inEthernet each of of two -detects thetwo specified maximum length theconsecutive is a cause: serious fault in the received signal. Probable The interface type has not been negotiation capable or has auto-negotiation double frame periods (512 bits) according exceeded $UNIT indicates the affected module configured to raised meet the framing of the from interface at function disabled by configuration alarm is the localIPAddress [G.775] chapters and I.2. -This the connector is5.2 notwhen properly connected to the Equipment Management (last element of the the far end. For E1 interfaces, the configuration negotiation with the peer fails. unit DN). TRMOD-1. of theE.g. far-end node be E1 Multiframe. Probable causes forshould PDH interfaces: All other transmission alarms related to has this -$INTERFACE the receiver or the far-end transmitter indicates the interface on the failed -signal a cable is cut or there is no cable connected to are suppressed. -module the accumulated BER of the end-to-end E1 path following the labeling on the of Example(s) for alarm text: "LOMF onfrontplate TRMOD-1, the interface is tooalarm high This raised ifislocal and peer ends in the HWisor the corresponding parameter IF2" -$UNIT thereal electrical signal excessively attenuated indicates the affected module from to LCP disagree the connected LCP configuration leading the Model. -Equipment theManagement port on atManagement the far element endon node (last ofisthe Example(s) for alarm text: "EBER TRMOD-1, negotiation failure. E.g. EIF1,off IF1 switched DN). E.g. TRMOD-1. IF2" The related configuration parameters are : -$INTERFACE transmit and receive are mixed indicatescables the pfcTarget. interface on up the acfcTarget, localMruTarget, Probable cause: The far end has a LOS, This alarm is raised the PPPon interface isLOF not or module following theiflabeling the frontplate of AIS alarm on its receiving interface. Examples for alarm text: operational all the PPP-links in the the real HWeither or thewhen corresponding parameter in Ethernet: "LOS onModel. SMOD-1, EIF2" or the PPPML-PPP interface are not available the Management Example(s) for the alarm text: "RDI on TRMOD-1, or link supporting SL-PPP interface is not E.g. EIF1, IF1 IF2" "LOS on TRMOD-1, EIF3" available. The alarm raised if the BFD state for the PDH: "LOSison TRMOD-1, Probable There is aIF2" transmission problem session iscause: not AdminDown and, nevertheless, no somewhere in the intermediate network along BFD packet is received at the local end during the E1 and AIS is sent instead of user traffic. the path detection time. $BFDID indicates the BFD identifier. The alarm isfor raised the BFD of the Example(s) alarmif text: "AISstate on TRMOD-1, session is not AdminDown and the BFD packet IF2" Example for alarm text: from the far end contains the diagnostic code = "BFD-10 down in ingress" 'Control Detection Time Expired' and no BFD The source and destination IP addresses will be down Ingress alarm is present. displayed in alarm diagnostic info field. Source IP addr $BFDSCRIPADDR Example for alarm text: Dest IP addr $BFDDESTIPADDR "BFD-10 down in egress" The source and destination IP addresses will be displayed in alarm diagnostic info field as below: "Source IP addr $BFDSCRIPADDR, Dest IP addr $BFDDESTIPADDR"

No data or clock information is exchanged via this interface. Possible impact on the connections over this interface: - voice calls or data connections are aborted and Possible effects: cannot be established anymore - no calls are possible - loss of remote management access to other - remote management connectivity is lost and network elements cannot be established anymore - IKE SAs and IPsec SAs cannot be established The interface cannot be used for transmission. It or re-keyed can for connectivity only. - lossbeofused synchronization if thechecks interface is used as a synchronization source -Possible Depending on use of the Ethernet interface, the impact: above described impact cantooccur for theand local - slow management access the SBTS SBTS and/or other (S)BTS elements if they are other network elements in the network chained via the Ethernet interface. - poor voice quality and data performance The performance management data collected on this interface becomes invalid.

Possible impact on the connections over the interface in question: - no calls are possible - loss of remote management access to other network elements in the RAN Possible impact on the connections over this interface: - no calls are possible - loss of remote management access to other network elements in the RAN Possible impact on the connections over this interface: - the SL-PPP/ML-PPP interface is not available. - loss of remote management access. Possible impact on the connections over this PPP link: - in case of SL-PPP, the interface is not available. In case of ML-PPP, the interface is degraded (as long as at least one link is available). Impact on the connections over this interface: - loss of remote management access to other network elements in the RAN. - loss of remote management access. The communication link between the local and the remote peer is defective or the peer is defective. Transport service may not be available and calls may be dropped. The communication link between the SBTS and the BFD peer is defective.Transport service may not be available and calls may be dropped.

This alarm indicates that there is a mismatch between SBTS expected auto-negotiation result and actual auto-negotiation result. An Ethernet link was established, but during the The RTT threshold alarm is raised in case the link establishment a link speed downshift event average value of the RTT for this TWAMP took place. A link speed downshift takes place session from the last 1-min period equals or when auto-negotiation successfully negotiates a exceeds the configured threshold. certain technology, but the link cannot be The alarm iswith raised the packet loss ratio then equals established thisiftechnology. It is tried to or exceeds configured threshold establish thethe link with the next lower value speedduring the current observation interval of 15 minutes. technology. An Ethernet link was established with 1000BaseT technology, but theif negotiated mode This alarm is raised at least oneclock of the PPPdoes not fit to the expected clock mode links belonging to the ML-PPP interface of is not synchronous operational. Ethernet. The expected clock mode of synchronous During the before Ethernet is IP theaddress slave inconfiguration, case an Ethernet allocation new IPv6 interface isofentered as addresses, sync source to the SBTS the network element tests DAD (Duplicate synchronization priority list.with Only applicable to Address Detection) the direct 1000Base-T, since only with this Ethernet attached transport network whether other technology both link partners have tothe negotiate SBTS has entered IPsec emergency bypass already-configured network elements the clock mode. active state where configured IPsec policies are on the network use the same IPv6 addresses on Probable causes: ignored and all traffic is sent unprotected. their IP interfaces including -Link network speed downshift: a cable is not of sufficient the Link-Local. The DAD detects those duplicated quality to support e.g. Gigabit Ethernet The alarm isbut activated when the IP traffic IPv6 addresses and prohibits technology, sufficient to support Fast Ethernet capturing session is started. the of this IPv6 address thetwo network -Linkoperation speed downshift: a cable hasinjust wire The is currently capturing IP traffic towards element. The Alarm contains pairsSBTS connected, which is sufficient for Fast a local port ornot intofor aIPv6 file on the SBTS. the corresponding address the system Ethernet, but Gigabit Ethernet. If the traffic capturing is happening towards a attempted to allocate based on the -Clock mode mismatch: Link partner has IPsec This alarm is triggered when the primary local port, the port and destination MAC address manual configuration options. If the alarm is advertised itself that it wants to operate in slave tunnel fails and needs to for be resulting provided. reported the IP interface, clock in negotiated clockIPsec mode SBTSmode has switched over to secondary $UNIT indicates the affected module from it"master" will show the Link-Local IPv6 address thevice at the local Ethernet interface (or tunnel. Equipment Management (last element of the system failed allocate. versa). As a result of to failure of the primary IPsec tunnel, The alarm is raised when the module IKE authentication DN). E.g. SMOD-1. $UNIT indicates the affected from SBTS has automatically switched over to credentials provided by the peer $INTERFACE indicates interface on the Example for alarm text: Dup Addr detected Equipment Management (last element the secondary IPsec tunnel terminating on of secondary is notE.g. valid. module following the labeling on the frontplate of 2001:0db8:85a3:0000:0000:8a2e:0370:7334 DN). SMOD-1. security gateway. the real HW orindicates the corresponding parameter $INTERFACE the interface on the in the Management Model. module following the labeling on the frontplate The alarm is raised, if IKE parameters are not of E.g. EIF1, IF1 the real HW orthe thepeer corresponding in matching with proposal. Itparameter can happen $MACADDRESS indicates the corresponding the Management Model. due to following two failures 'macAddr' parameter in theor object model. E.g.When EIF1,the IF1SBTS sends --> receives a failure notification as response to an IKE_SA_INIT This alarm isfor raised when the SBTS sends or Example(s) alarm request message. Thetext: failure notifications receives following notification asSMOD-1, responseEIF2" to an "IP Traffic Capturing ongoingon on SMOD-1, LMP, "Auto-negotiation mismatch includes: IKE_AUTH or CREATE_CHILD_SA request aa:bb:cc:dd:ee:ff" or - NO_PROPOSAL_CHOSEN message. "IP Traffic Capturing ongoingon onTRMOD-1, SMOD-1, EIF2, mismatch EIF3" -"Auto-negotiation INVALID_SYNTAX The failure notifications includes the following: aa:bb:cc:dd:ee:ff" - INVALID_MAJOR VERSION -"IP NO_PROPOSAL_CHOSEN Traffic Capturing - INVALID _IKE_SPI ongoing on TRMOD-1, EIF3, -aa:bb:cc:dd:ee:ff" TS_UNACCEPTABLE - INVALID_MESSAGE_ID - INVALID_SYNTAX - UNSUPPORTED_CRITICAL_PAYLOAD or - INVALID_MAJOR VERSION FAILED_CP_REQUIRED - INVALID _IKE_SPI --> When the SBTS sends or receives a failure - INVALID_MESSAGE_ID notification as response to an IKE_AUTH request - UNSUPPORTED_CRITICAL_PAYLOAD message.The failure notifications include: - SINGLE_PAIR_REQUIRED or - INVALID_SYNTAX FAILED_CP_REQUIRED - INVALID_MAJOR VERSION - INVALID _IKE_SPI - INVALID_MESSAGE_ID - UNSUPPORTED_CRITICAL_PAYLOAD

The Ethernet Link got established with an unexpected clock mode or technology. Possible impact on the connections over this interface: This alarm is an indication that the backhaul capacity for traffic with the same profile as this - Increased packet delay variation and increased TWAMP session (DSCP value, packet size) may average delay for all voice/packet and be too small, because the measurement packets management connection are scheduled later than before. This alarm is an indication that the backhaul capacity with same as this - Increaseforoftraffic packet loss due profile to congestion. TWAMP session (DSCP value, packet size), may be much too small, because some of thelost with - Loss of synchronization/Timing source measurement packets seem to have been Timing over Packet (IEEE1588v2) due to thrown The ML-PPP interface operates with reduced away. increased packet delay variation. capacity. The TWAMP measurement packets are lost because degraded traffic throughput. - Loss of of synchronization/Timing source lost with Synchronous Ethernet. The local peer is not be able to go "online" as there is already a remote peer operating with the IP address the local peer intended to go "online". All configured IPsec policies are ignored and all The remote peers continue their operation the SBTS traffic is sent unprotected. without disruption. The resulting packet capture files can used for Expert analysis to identify network problems and to help determine the best course of action. SBTS traffic has switched over from the primary IPsec tunnel to secondary (backup) IPsec tunnel terminating on secondary security gateway. The IKE SA cannot be established.

IKE SA cannot be established and subsequently no IPsec SAs can be established.

The related IPsec SA cannot established and used.

Identifying Additional Information Fields

Additional Information Fields

List of cells made faulty or degraded by the fault. Path of the hardware unit.

Serial Number of the hardware unit.

Path of the hardware unit.

Serial Number of the hardware unit.

List of cells made faulty or degraded by the fault. Path of the hardware unit.

Serial Number of the hardware unit.

Path of the hardware unit.

Serial Number of the hardware unit.

List of cells made faulty or degraded by the fault.

Destination IP address.

List of cells made faulty or degraded by the fault. Path of the hardware unit.

Serial Number of the hardware unit.

List of cells made faulty or degraded by the fault.

List of cells made faulty or degraded by the fault.

List of cells made faulty or degraded by the fault. Path of the hardware unit.

Serial number of the hardware unit.

List of cells made faulty or degraded by the fault. Path of the hardware unit.

Serial number of the hardware unit.

List of cells made faulty or degraded by the fault. Path of the hardware unit.

Serial number of the hardware unit.

Path of the hardware unit.

Serial Number of the hardware unit.

List of cells made faulty or degraded by the fault. Path of the hardware unit.

Serial number of the hardware unit.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

For details, refer to GSM/EDGE BSS Operating Documentation.

Instructions

FAULT NAME BB bus reception error (summing device) FAULT ID 2016: EFaultId_Muksu_SMTimeOffAl FAULT NAME # autonomous reset as recovery action MEANING The master frame in the received baseband bus frame is not in the correct FAULT ID place related to the internally-generated master frame pulse. Either the 52: EFaultId_UnitAutonomousResetAl FAULT NAME frame has been set into the wrong place (PI delay) or the data itself is in BTS blocked the wrong place. MEANING The fault informs the operator that the BTS is trying to correct a fault FAULT ID INSTRUCTIONS situation by performing a recovery reset to a unit, the site, the BTS, or the 50: EFaultId_BTSBlockedAl 1. Check the cables between the system module and the RF module, the FAULT NAME BTS secondary unit. In case of an RF module reset in RF chaining cable between the FBBx/ABIx module and the RF module, and the cable [User defined] the configuration, BTS also resets all RF modules that are further in the MEANING between the system module and the FBBx module. chain. The BTS is blocked with the BTS Site Manager. The purpose is to avoid FAULT ID fault indications thatthat might be raised during a BTS module maintenance task. 2. Replace the unit causes the alarm (system or FBBx/ABIx). 1400: EFaultId_ExtAl0 FAULT NAME 1401: EFaultId_ExtAl1 BTS RNC interface signalling link failure INSTRUCTIONS 1402: EFaultId_ExtAl2 Unblock the BTS to cancel the fault. Unblocking the BTS causes a BTS 1403: EFaultId_ExtAl3 INSTRUCTIONS FAULT ID reset. 1404: EFaultId_ExtAl4 Check the fault history and other active faults of the unit. 17: EFaultId_CnbapLinkAl FAULT NAME FAULT NAME 1405: EFaultId_ExtAl5 BB bus transmission 2M external referenceerror missing 1406: EFaultId_ExtAl6 Note: This MEANING fault does not require any (special) actions. 1407: EFaultId_ExtAl7 A common NBAP (NodeB Application Part - interface between NodeB and FAULT ID FAULT ID 1408: EFaultId_ExtAl8 RNC) link failure has occurred that is possibly caused by a transmission FAULT NAME 2017: EFaultId_Muksu_SRx10b8bAl 1899: EFaultId_2MExtRefMissAl 1409: EFaultId_ExtAl9 FAULT NAME network problem. Cell blocked 1410: EFaultId_ExtAl10 Automatic BTS Operator Certificate retrieval unsuccessful MEANING MEANING 1411: EFaultId_ExtAl11 FAULT NAME INSTRUCTIONS FAULT ID A decoding error hasmonitoring been detected in the baseband link. The The reference clock has detected a signal internal loss of 2.048 MHz 1412: EFaultId_ExtAl12 Antenna down FAULT IDlinkisislost, Note: Perform the steps incontent the listed order until the fault is resolved. 49: EFaultId_CellBlockedAl data packet or the is corrupted. received from an external reference source connected to the Sync In 1413: EFaultId_ExtAl13 61510: NO_CERTIFICATE FAULT NAME interface of the System Module. 1414: EFaultId_ExtAl14 IDthe 1. Reset WCDMA SW.when the links are not synchronized with each MEANING This situation also occurs Active users license limitation 1415: EFaultId_ExtAl15 476: EFaultId_Rp3BusError MEANING The fault indicates that the user has blocked the cell using the BTS Site other. INSTRUCTIONS 1416: EFaultId_ExtAl16 A requested certificate could nottobethe retrieved 2. Check the transmission links RNC. from the certificate authority Manager. FAULT ID Note: Perform the steps below in the listed order until the alarm 1417: EFaultId_ExtAl17 MEANING (CA). INSTRUCTIONS 4337: EFaultId_ActiveUsersLimitAl disappears. 1418: EFaultId_ExtAl18 The antenna (RP3)and linkRNC is down. Therenewed transmitter orthe receiver dropsauthority from FAULT NAME A could not from certificate 3. requested BTS transmission settings. 1. Check thecertificate cables between thebe system module and the RF module, and 1419: EFaultId_ExtAl19 synchronization. BTS file error (CA). INSTRUCTIONS the cable between the FBBx/ABIx module and the RF module. MEANING 1. Check the cabling (connected to the Sync In interface). 1420: EFaultId_ExtAl20 A requested certificate could be retrieved because the number of 4. Reset the SBTS. Unblock the cell to cancel thenot fault. The eNB enters capacity limited mode due to missing licenses. Calls from 1421: EFaultId_ExtAl21 INSTRUCTIONS FAULT IDthereceived certificates from the repository server (RA) or certificate authority 2. Reset system module. excess users be rejected except for handover and emergency calls. 2. Check ifthe thewill 2.048 MHz reference source is working normally and the 1422: EFaultId_ExtAl22 1. Restart 1802: EFaultId_FileRequestFlashAl (CA) are more than expected. 5. Replace theBTS. System Module. FAULT NAME 2.048 MHz signal is available. 1423: EFaultId_ExtAl23 3. Replace the alarming module (system module). Address mismatch in summing INSTRUCTIONS 1424: EFaultId_ExtAl24 2. If that does not help, replace the alarming module. MEANING INSTRUCTIONS Add licenses toalarming the Centralized License Server to avoid call limitation. 3. Replace the module. 1425: EFaultId_ExtAl25 A software download to FSP, DSP, ABIx, or FR has failed. 1. Check the CMP configuration. FAULT NAME FAULT ID See "Centralized Help"replace document in NOLS for details. In case the FSP isLicense causingServer the alarm, the FSM because the alarm One orEFaultId_Muksu_SsubMmAl more carrier groups blocked 2019: MEANING is related to the fixed FSP inside the FSM. INSTRUCTIONS 2. Check if the CA server is reachable. FAULT NAME The state of thethe external alarm lineinshows thatorder an external Note: Perform steps the listed until thealarm fault is BTS RNC interfacefollowing signalling link failure FAULT ID NAME MEANING notified. If FBBx or ABIx is causing the alarm, replace the FBBx or ABIx. disappears: 3. If none the above contact the CA in administrator or aThere Nokiaare 4399: Connection Unstable Atwork, 3Gbps There isNAME aof baseband bus address mismatch the summing. FAULTEFaultId_OneOrMoreCarriersGroupsBlockedByUserAl service personnel. FAULT ID two possible causes: BTS master clock tuning The user specifies, duringfailure commissioning, the alarm number, severity, 1. Use BTS Site Manager to perform a full commissioning to the BTS and 18: EFaultId_DnbapLinkAl MEANING FAULT ID FAULT NAME polarity that indicate the fault. usingfault the NetAct backup upload SCFblocked file as template. The indicates that (two the user has oneunits or more GSM TRX of the 4310: EFaultId_ConnectionUnstableAt3Gbps 1. A configuration error different baseband functioning) - after an HSDPA users limitation alarm FAULT ID MEANING cell using the BTS Element Manager. acknowledgement, the fault returns. 1818: EFaultId_Ov_OscAl INSTRUCTIONS 2. DownloadNBAP two different packages so that the faulty file is A dedicated (NodeBsoftware Application Part - interface between NodeB MEANING FAULT ID [User-defined] removed from the BTS. FAULT NAME and RNC) link failure has occurred. INSTRUCTIONS The RP30-1 connection the system radio module, or 2. Data corruption on thebetween bus - appears once module when anand unsynchronized 4285: EFaultId_HsdpaUsersLimitationAl

FAULT NAME ALD port configuration failure FAULT ID 4255: EFaultId_AldPortFailureAl FAULT NAME Beamforming calibration failure in RF data path MEANING The Radio Module has detected switch configuration mismatch on the FAULT ID ALD port. 6051: EFaultId_PhyRxBfCalibrationDetectContinuousExceptionAl FAULT NAME 10b8b coding error in optical interface device INSTRUCTIONS MEANING 1. Check the configuration of the ALD port. Some problems in TX or RX path have caused beam-forming calibration FAULT ID to fail. The path means all units between the signaling processor (DSP) 2004: 2. TheEFaultId_OIC_LVDSRecAl alarm is cancelled only when the RF Module is reset, or the BTS is FAULT and theNAME antenna line that processes the data transmitted (TX) or received reset. 10b8bbycoding error in optical interface device (RX) the BTS. MEANING The fiber cable is experiencing interference; data transmission is faulty. FAULT ID INSTRUCTIONS 2004: EFaultId_OIC_LVDSRecAl To get the diagnostic information of the alarm for the lists of information Please check the fault-specific description below for detailed instructions. A physical connection failure between the optical interface and the similar to the following: RMOD-a/RXb=NOK (Note: "a", "b" are Arabic summing function has occurred. FAULT NAME MEANING numbers in practice and RMOD-a stands for RMOD_R-a instance), if such FAULT NAME : failure ALD Port power The fiber cable is experiencing interference; data transmission is faulty. information is available. One reason or moreofcarrier groups The the fault mightblocked be a low-quality or polluted SFP, or a lowquality optical cable used to connect radio modulefortodetailed system instructions. module FAULT ID Please check the below fault-specific description A physical connection failure between the optical interface and the Based on info of the alarm, one can try the following FAULT ID the : diagnostic and/or extension baseband module. 4069: EFaultId_Rs485PowerFailureAl summing function has occurred. instructions to recover from the fault: 4399:EFaultId_OneOrMoreCarriersGroupsBlockedByUserAl INSTRUCTIONS MEANING The reason of the faultcell might beup a low-quality or polluted SFP, or acolow1. Check whether is set under the following scenarios: MEANING : the the Note: Perform steps in the listed order until the fault is resolved. OBSAI interface: quality optical cable used to connect radio module to system module existence with WiMAX in the same band; and co-existence with other Please check the fault-specific below for detailed instructions. The fault indicates that the userdescription has blocked onecondition or more GSM TRX ofLTE the Radio Module has detected an over-current in the RS485 and/or extension baseband module. networks from other vendors. If so, check whether the synchronization cell using theradio BTS module Elementbehind Manager. 1. Reset the the cable reported as the fault source by IUANT port. between networks are correctly configured. FAULT NAME blocking and/or: line unblocking Some antenna device isit.causing overload. Antenna line devices INSTRUCTIONS Invalid BTS configuration or timeout from BSC because of the lack of DC INSTRUCTIONS : powered by the RS485 IUANT are out of order Note: Perform the the steps inisthe order the fault is different resolved.LTE 2. Check whether cell setlisted up under auntil network using 1. If the TRX is locked by BSC, then first unlock TRX and then unblock 2. Reset the system module. power. 1. Check the sectorreleases. which hasIf the affected TRX.the TDD BTS software so, then carefully review the calibration FAULT ID :group to cancel the fault. the carrier 2. Check in the alarms at NetAct or BTS Element Manager where the by 1. Reset the radio module behind the cable reported as the fault source configurations in the vendor files among different LTE TDD BTS software 2413: EFaultId_InvalidConfigOrTimeoutFromBscAl 2. If the TRX is SFP unlocked atradio BSC,module then unblock the carrier group to cancel 3. Replace the the port where the cable reported as CPRI/Ir interface: matching sector id ison visible blocking and/or unblocking it.in alarm attributes. The alarm id belongs to releases. the fault. fault source is terminated. range 7100-7116. MEANING : case: Over-current 3. Find fault id in the alarm and follow the instructionssources mentioned for the 2. Reset the system module. Check whether the GPShas oror other synchronization (for example, 1. Check the sector which the affected TRX. Invalid configuraton received timeout for or configuration procedure from 4. Replace the SFPhas on the system module extension module The Radio Module detected over-current on the ALDbaseband port. Some fault. synchronization servers) for this cell are working as expected. 2. Check inthe the alarms at NetAct or BTS Element Manager where the BSC FAULT NAME :cable port where reported as fault source is terminated. antenna line device is causing overload. Depending on hardware 3. Replacesector the SFP the radio module port where the cable reported as matching id ison visible alarm attributes. Thethe alarm id belongs Cell blocked implementation, antenna lineindevices powered by RS485 IUANT, to or fault source is terminated. 4. Check whether the cell is set up under the sharing of RFM with TDrange 7100-7116. INSTRUCTIONS : 5. Replace cable asorder. fault source. powered bythe theoptical antenna line,reported are out of SCDMA. 3. Finddiagnostic fault in info the alarm and follow theroot instruction mentioned for the on Read of alarm todescription find the cause the fault. Based FAULT ID : idthe Please check fault-specific forof detailed instructions. 4. Replace the SFP the system module below or extension baseband module If so, check whether the carrier configurations in TD-SCDMA and TD-LTE fault. the info follow ofon the actions below: 49: EFaultId_CellBlockedAl 6. Replace theone radio module behind the cable reported as fault source. Under-current case: port where the cable reported as fault source is terminated. are not in conflict. 1. Check the site configuration BSC and takeon corrective if The Radio Module has detectedatunder-current the ALD action port. There is a FAULT NAME needed. MEANING : 7. If thepower system module resetbattery helped but the fault is reported again after problem with ALD port connection. Depending on hardware Mains break, running backup 5. Replace the optical cable reported asfor fault Check the RP3 links state especially thesource. SFP as well the as the fibers 2. Few features cannot co-exist. Examples: The fault indicates that the user has blocked using BTS some time, or if the actions mentioned abovethe have not clearedIUANT, the fault implementation, antenna line devices powered bycell the RS485 or connecting the RFMs and the BBUs inside the BTS. 1. Hopping CheckManager. the availability of IP connectivity. a. sectors should not be configured for Extended cell Element situation, replace the extension baseband module (if the fault is reported powered by the antenna line, are out of order. FAULT ID the radio module behind the cable reported as fault source. 6. Replace b. and to Baseband hopping shouldornot enabled for a (if on the cablehopping connected the baseband module) thebe system module 37:Antenna EFaultId_MainsBreakAl 6. Block and unblock theare cell. 2. activeconnected alarms at to thethe farsystem end. If module). found, follow sector, INSTRUCTIONS :there theCheck faultetc. iswhether reported on the cable 7. Ifinstructions the the system module resetthose helped but the fault reported again after the for handling alarms. Correct site configurations, ifantenna such features areisconfigured. Unblock the cell tointerface cancel the fault. 1. Check theor ALD and line devices. Fix or replace the MEANING some time, if the actions mentioned above have not cleared the fault 7. Reset the BTS. 3. Check whether BSC is operational faulty parts or devices. E1 interfaces: Check that the interface type of the far-end interface is also There is a fault in the mains power supply. The SBTS has received a situation, module (if the fault is reported 3. Check ifreplace the farthe endextension has BFD baseband switched ON. 4. Resetbackup the BCF from BSC configured to be a framed E1 interface. If this is not the case, reconfigure battery alarm and intelligent shutdown procedure has started. on the cable connected to the baseband module) or the system module (if 8. Examine the Site antenna cable connection between the RFM and the 5. Reset SBTS from SBTS Element Manager 2. For CPRI-A radios, the may cancel automatically the CPRI-A the interfaces so thaton they match each other. the fault is reported thefault cable connected to the systemif module). antenna element. FAULT NAMEthat Overcurrent on AISG port no longer exists. If fault is not radio reports INSTRUCTIONS FAULT NAME : powermissing 2M external reference canceled automatically, the fault is canceled when the CPRI-A radio is Check the mains supply. 9. Exchange the cable connection between the antenna and the RFM to BCF Power compression missing reset, after BTS Site reset,feature or BTSlicense is blocked and/or unblocked. check whether the RRU port or the cable is faulty. FAULT ID FAULT IDother : 1899: 3. For EFaultId_2MExtRefMissAl all radios, the alarm is cancelled only when the RF Module is FAULT NAME 10. Replace the hardware(RRU/BBU). 2408:EFaultId_Power CompressionLicense MissingAl reset, or if the BTS is reset. Antenna link is down MEANING MEANING : clock monitoring has detected a signal loss of 2.048 MHz The reference FAULT ID txPowerPooling is reference enabled insource Site Configuration received from anfeature external connected toFile(SCF) the Sync and In Tx 476: EFaultId_Rp3BusError power pooling is not enabled from BSC interface of thefeature Systemlicense Module. FAULT NAME FAULT NAME MEANING BTS configuration: error (not enough HW for LCR) INSTRUCTIONS Antenna line device configuration failure

1. Check that the cables/fibers are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on and has correct auto-negotiation settings. 1. Check the availability of IP connectivity. 3. Check whether there are active alarms at the far end. If there are, follow 2. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms. the instructions for handling those alarms. 4. To verify that the hardware of the interface works correctly, connect a Switch off the or wait the for alarm the timeout to expire which opens the loop cable andloopback check whether disappears. loop and cancels the alarm. 5. Check that the length/type of the cable/fiber does not introduce excessive attenuation or that the cable/fiber is cut somewhere. 1. Clean the cables and connectors. 6. Check that the Ethernet interface has correct auto-negotiation settings, fitting to the interface.are properly connected to the unit. 2. Check thatfar-end the connectors 7. anthat optical Ethernet interface: that the module 3. With Check the cable connected to Check the interface in inserted questionSFP is not Check that the configured interface typeofmatches the Ethernet configured interface matches the fiber type and wavelength the Gigabit link damaged and is within the specifications. type of the far end. If this is the case, the problem is somewhere in the provided. transmission network. 4. Follow the E1 path in the network and check whether any other alarms concerning the fault are on (such as Laser End of Life) and signal quality Check intermediate network for alarms for indicating thethose root of eachthe individual link. Iftransmission they are, follow the instructions handling cause alarms.and follow the instructions for handling these alarms.

1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. 2. Check the transmit hardware, connect a loop cable and check that no alarms appear for this interface. Check if the negotiatedLocalIPAddress is same as the configuredLocalIPaddress. Change the values to the correct ones accordingly either at the local end or peer. Check the following parameters status: localMruResult, remoteMru, pfcResult, acfcResult. Check if the LCP configuration parameter values (acfcTarget, localMruTarget, pfcTarget) match with the peer. Change the values to the correct ones accordingly either at the local end Check for LCP failure alarms of the PPP-links belonging to the SLor PPP/ML-PPP interface and follow the instructions of these alarms. peer if there is a mismatch. Check all PDH related alarms and follow the instructions of these alarms. 1. Check the network between both BFD peers for physical link failures or mis-configurations. 2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD local and remote peers match. 1. Check the network between both BFD peers for physical link failures or misconfigurations. 2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD local and remote peers match.

1. Check the negotiated speed and clock mode at the Ethernet interface to determine the root cause of the alarm. 2. If the Ethernet interface speed is 100Mbps, but 1000Mbps was expected, then the alarm is caused by a link speed downshift event. 1. Check the backhaul usage and if other applications with the same or higher PHB may compete against this TWAMP session about the capacity. 2.1 Check that the cables are fully plugged in to the connectors. An increase in the priority of TWAMP session or of the backhaul capacity may clear the alarm. 2.2 Check that a CAT5e or higher Category cable is used 2. Check the last measured RTT values of this TWAMP session and verify 1. Check the backhaul usage and if other applications with the same or that the configured RTT threshold value is not too close to average higher PHB may compete against this TWAMP session about the capacity. 2.3 Replace the cable. measured RTT values, so that this alarm could be result of sporadic misAn increase in the priority of TWAMP session or of the backhaul capacity measurement. may clear the mode alarm.of the local Ethernet interface is slave and the 3. If the clock 2. Check interface if destination is unreachable byas IP synchronization connectivity test.source, Send an Ethernet is configured serve then Check the LCP failure alarms of to the PPP-links belonging to the ML-PPP ICMP echois request (ping) to themode UDPmismatch. port of the TWAMP reflector at the the alarm caused by a clock interface and follow the instructions of these alarms. destination IP.If ICMP echo reply indicates that the destination is Check the related PDH alarms and follow the instructions of these alarms. unreachable youmode have setting access of to the TWAMP reflector, you can checkbe its 3.1 Check thebut clock remote link partner. It should status. If the status is disabled or down try to activate it again and check if either "multiport device" or "manual master". 1.Check for duplicate IPv6 addresses configured in the network element. alarm disappears. 2.Change the the identified duplicate address. 3. configured PLR threshold. PLR to 0% should be avoided, 3.2Check Configure local clock modeIPv6 toSetting "manual slave" forcing local because every losttomeasurement packet willmode. trigger the alarm and it Ethernet interface operate at slave clock cannot be cleared again (PLR>=0). Note: Do notemergency execute this step remote, butthe only when being local at site as Start IPsec bypass by making security gateway not itreachable can cause the Ethernet link to be down. As a result, remote either by plugging out the cable or configuring wrong security management access might be lost. gateway address. Note: Check whether root cause of the fault is not existing anymore, is Stop from WebUI page. Retriggering auto-negotiation done IP bytraffic a newcapture auto-negotiation process. requires manual action by the user, (i.e. changing Ethernet interface configuration, plug out/plug in cable, triggering link down/link up). 1. Check the availability of IP connectivity. 2. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms. Check the authentication credential provided by the peer (certificate).

Check the IKE profile configuration of the SBTS and the peer for proper values.

Check that the configurations for the peer and the SBTS security policies for corresponding failure notification.

Related Faults

Related Features

692142154181817181918391840190719231925200020012016201720732078402643094310610506107961201 • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • RP000956: SBTS Startup and runtime management • RP000367: Small Form Factor Pluggable Slot 6101213165210311012513914915841241847618021806181118151816184119001901190319041905190719081910191119 • RP001534: SRAN FM combined service (SFP slot) • LTE146: LTE Software Management • LTE2121: Radio Unit reset in BTS SM • LTE1996: Flexi Zone Controller Application • LTE2779: CPRI-A • LTE2121: Radio Unit reset in BTS SM • LTE 161-p : Technical Log and Memory Dump • RP001498: Support of FSMF + FSMF with 48495019314399 • RP001534: SRAN FM combined LBT3196: CRL8712 New alarms service for OTN SRAN configurations •network LTE654a: LTE Configuration Management 1/2 • LTE1656: Management support for legacy • LTE1996: Flexi Zone Controller Application LTE656: LTE Fault Management Motorola/Fujitsu RF-equipment • RP001486: Support for already delivered • LTE2779: CPRI-A SRAN16.2/16.10 features 3714001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314 RP000924:CN5544 SBTS Intelligent • LBT1879: Division ofshutdown DSP Fatal •• LTE076-a : Support for already legacy MHA RP001486: Support for delivered Alarms •SRAN16.2/16.10 LTE1656: Management support for legacy features • LTE151: Autonomous LTE eNB Operability Motorola/Fujitsu RF-equipment RP001534: SRAN FM combined service • LTE505: LTE505 Transport Separation for RAN •sharing LTE1996: Flexi Zone Controller Application 1718241240264275615062026203620462056284628562876303630463086317632163226323685068516107561076610776 • RP000980: SBTS Recovery • LTE656: LTE Fault Management Multimode System Modules • RAN2262: RP001534:Flexi SRAN FM combined service FSMF and FSMG • LTE140: Ethernet OAM •• LTE1815: Clock mode forUpdate TD-SCDMA LTE915: S1 eNBSlave Configuration and TDLTE dual mode on FSIH • LTE1996: Flexi Zone Controller Application 18161818185818981899402641144153416042104298429943006162361624 • RP001534: SRAN FM combined High Capacity Systemservice Module • RAN1016: LTE656: LTE Fault Management • LTE1996: Flexi Zone Controller Application RAN20: HSDPA parameterisation • LTE3: S1, X2 and RRC common signaling • LTE2464: Synchronization with Network Time Iu-PS Throughput • ARAN1163: RP001486: Support for alreadyMeasurement delivered Protocol for GTP Traffic features SRAN16.2/16.10 • RP000375: Synchronous Ethernet SRAN Cell Sets Allocation on 40266107461510616166161861642 • RP001621: LTE656: Fault Management LTE498: LTE RAN Information Management forFull •AirScale ARAN1163: Iu-PS Throughput Measurement Module •GSM LTE1996: Flexi Zone Controller Application for GTP Traffic FSMr3b: RP3-01 operation mode •• LTE595-b15: RP001486: Support forRAN already delivered LTE1900: Centralized • LTE923: TD-LTE Ir interface support LTE2805: Monitoring RX sensitivity SRAN16.2/16.10 features • LTE505: LTE505 Transport Separation for RAN • LTE-435: RF sharing WCDMA-LTE RP001538 WCDMA SupportCertificate in new Single •sharing RP000845::SBTS Operator 428542864287429343374343 •BTS RP001004: SBTS Data User RTU RP001498: Support of FSMF + FSMF with O&M architecture Management •• LTE1: S1/X2 data path management RP001534: SRAN FMUltraSite combined service SRAN configurations Enhanced • RAN1671: RP001498: Support of FSMF +Base FSMFBand with LTE1117: LTE MBMS •(EUBB) LTE2417: Traffic Capacity RP001486:IPSupport for already delivered SRAN configurations •• LTE1771: Dual U-plane IP addresses LTE2621-B: eNodeB LimitationorActions for SRAN16.2/16.10 features Add new frequency cell without • LTE2060: RP000900: SBTS user account management LTE1196: RIM for WCDMA License Management in LTE • RP000377: Synchronization from PDH 623293018021850190119021924192820564082408340854088414543926283 •reset RP001534: SRANamount FM combined service cells LTE2029: Extend of neighboring interface ••with LTE2114 -V-e: FSIP/FBIP, FSMr4;Supporting LTE146: LTE Software Management overload control in eNB •U-Plane GPS Synchronisation CE startup • LTE80: LTE1996: Flexi Zone Controller LTE2562: ANR InterRat 1xRTT -Application O&M assisted •• RP000374: Timing overnew Packet with frequency RP001171: WCDMA17 feature LTE2305: Inter eNodeB Carrier Aggregation for synchronization implementation for SBTS17 2 macro eNodeBs 8894951541701807182519862019240324132414241540084036403840434072407642084263427842824305437043734374 RP001534: SRAN FM service •• RP000383: Timing overcombined Packet with Phase LTE2866: AirScale operation with Core LTE1656: Management support for2 legacy FDDMBMS Inter-band/Intra-band CA with • LTE1858: LTE1117: LTE Synchronization plugins Motorola/Fujitsu RF-equipment Two Flexi Zone Micro BTSs RP001498: Support ofWCDMA-LTE FSMF + FSMF with •• LTE656: LTE Fault Management LTE-435: RF sharing LBT2761: CRL5746 Configuration of RU with LTE2007: Inter eNB Carrier Aggregation SRAN configurations •incompatibility LTE1815: Clock Slave mode forMemory TD-SCDMA LTE 161-p : Technical Log and Dump software •and Flexi Zone Controller Application TDLTE dual mode on FSIH •• LTE1996: 50160: TCP/IP measurement LTE2779: CPRI-A •• LTE3199: Support for Maintenance multiple MBSFN and LTE168: LTE System • LTE1858: FDD Inter-band/Intra-band CA with Synchronization Areas •Two LTE2464: Synchronization Flexi Zone Micro BTSs with Network Time •Protocol LTE2270: FDD-TDD downlink carrier • LTE882a1: System Upgrade with Backward aggregation 2CCFSIP/FBIP, FSMr4;Supporting •Compatibility LTE2114 -V-h: - FDD - conversion •K2 LTE2612: ProSe Direct Communications for ARM platform CE crash • LTE1854 A-h: System Upgrade to RL70Public Safety consistent SW fallback • RAN3421: WCDMA Support over Nokia CPRI • LTE3340: SWM Harmonization for SBTS • RP000912: SBTS SW Management • LTE1130: Dynamic PUCCH allocation

18341835183618371838184218431844184518461847184818691870188819572900402640454046406942394270 • RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM • LTE2099: Support for harmonized MHA family • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment 11516018682401402642616051611761186253625763516561 • RP001534: SRAN FM combined service • LTE3368: PIM Cancellation for CPRI-A radios • LBT3812: AirScale Virtual MCU • LTE2779: CPRI-A • LTE1996: Flexi Zone Controller Application • LTE1976: Support for single and multi-antenna • LTE550: Radio parameter online changeable RET • LTE656: LTE Fault Management 2691013162324262728293069949511412413015415716216516721421541241847618021806181118151816183418351836 • RP001534: SRAN FMController combinedApplication service LTE1996: Flexi Zone • LTE145part1: Radio Network Configuration via • RP001498: of FSMF FSMF with RP001740: Support LTE feature parity+alignment to RROM SRAN configurations FDD-LTE17SP on Airscale • RP001486: Support for already delivered • 50160: TCP/IP measurement RAN1770: RF Sharing in WCDMA-GSM SRAN16.2/16.10 features • LTE3552: eMBMS capacity enhance. & LTE656: LTE Fault Management 1012131610311012513313413914514614915841247618061811181518411900190319041905190619081910191119121918 • RP001534: SRAN combined LTE2154: Cell stateFM audit alarm service support for RF overlapping of MBSFN Areas •• LTE-435: sharing WCDMA-LTE RP001498: Support of FSMF + FSMF with • LTE146: LTESupport Software RP001486: forManagement already delivered SRAN configurations •SRAN16.2/16.10 LTE1996: Flexi Zone Controller Application features • LTE1656: Management support for legacy • LTE3199: Support for multiple MBSFN and Motorola/Fujitsu RF-equipment #N/A #N/A Synchronization Areas • LTE2779: CPRI-A • LTE1227: Flexi Multiradio BTS SW Download • LTE1996: Flexi Zone Controller Application for Antenna Line Devices • LTE151: Autonomous LTE eNB Operability • RP000383: Timing over Packet with Phase • LTE505: LTE505 Transport Separation for RAN Synchronization #N/A #N/A sharing • FSM3TD57: Common application SW • LBT1879: CN5544 Division of DSP Fatal adaptation for FSM-r3 - Base services Alarms • LTE1656: Management support for legacy • RP001538 : WCDMA Support in new Single Motorola/Fujitsu RF-equipment BTS O&M architecture #N/A #N/A • LTE2779: CPRI-A • LTE1444: FBBC basic start up, auto detection • LTE1117: LTE MBMS and transparent mode • LTE151: Autonomous LTE eNB Operability • LTE2121: Radio Unit reset in BTS SM • LBT1464: On-line modification of • ARAN1163: Iu-PS Throughput Measurement ANTL/alDcVoltageEnabled #N/A #N/A for GTP Traffic • RP000375: Synchronous Ethernet • FSM3TD57: Common application SW • ARAN1163: Iu-PS Throughput Measurement adaptation for FSM-r3 - Base services for GTP Traffic • LBT975: Medusa single mode support for LTE • LTE2121: Radio Unit reset in BTS SM •#N/A LTE2250: Syslog substring triggered #N/A • LTE2816: High Memory Consumption Alarm for automated snapshot collection Nokia RP1/L3 Radio Modules • RP001621: SRAN Cell Sets Allocation on Full • LBT2761: CRL5746 Configuration of RU with AirScale Module incompatibility software • 50160: TCP/IP measurement • RP001621: SRAN Cell Sets Allocation on Full 37 RP000924: SBTS • LTE2060: Add newIntelligent frequencyshutdown or cell without AirScale Module •reset RP001486: Support for already delivered •SRAN16.2/16.10 RP000377: Synchronization from PDH features • LBT2534: Legacy feature porting to FSMr4interface Parent • LTE1976: Support for single and multi-antenna •• RP001486: forcombined already delivered 61022 RP001534: Support SRAN FM service RET SRAN16.2/16.10 features •• RP000361: Link Supervision BFD LBT1879: CN5544 Division ofwith DSP Fatal • RP000924: SBTS Intelligent shutdown Alarms • RP001171: WCDMA17 new feature • LTE3265: GPS outage handling for OTDOA implementation for SBTS17 •• RAN1770: RF Sharing in WCDMA-GSM 61028 SRAN FM combined • RP001534: LTE2866: AirScale operation withservice 2 Core •• LTE2023: User plane overload handling RP000357: Symmetrical E1 Interface plugins • LTE447: SW support for RF sharing GSM-LTE • RAN2262: Flexi Multimode System Modules • LTE654a: LTE Configuration Management 1/2 FSMF and FSMG • LTE937-b1: FSMr3b: L3 call support - Feature • LTE168: LTE System Maintenance porting to FSM-R3 • LTE656: LTE Fault Management • WM0628: WM0628 • LTE2114 -V-e: FSIP/FBIP, FSMr4;Supporting • LBT975: Medusa single mode support for LTE U-Plane CE startup • LTE493-b: Beamforming - Operability & • LTE2805: Monitoring RX sensitivity Configuration support • LTE595-b15: FSMr3b: RP3-01 operation mode • LTE923: TD-LTE Ir interface support • LTE923: TD-LTE Ir interface support • LTE1891: eNode B power saving - Micro DTX • LTE1829: LTE-LTE RF sharing • RP001486: Support for already delivered • RAN20: HSDPA parameterisation SRAN16.2/16.10 features • RAN1016: High Capacity System Module • LTE2099: Support for harmonized MHA family

61029

61030

61040

• RP001534: SRAN FM combined service • RP000350: Ethernet termination • RP000357: Symmetrical E1 Interface • RP000365: Electrical 10/100/1000-Base-T Interface • RP000356: IPsec for BTS • RP000367: Small Form Factor Pluggable Slot (SFP slot) • RP000368: 1000Base-SX Optical GE Interface • RP000369: 1000Base-LX Optical GE Interface • RP001534: FM combined RP000370: SRAN 1000Base-ZX Opticalservice GE Interface • RP000357: Interface RP000371: Symmetrical 1000Base-BXE1 Optical GE Interface

61104

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

61150

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

61151

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

61152

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

61250

• RP000176: MLPPP termination

61251

• RP000176: MLPPP termination

61252

• RP000176: MLPPP termination

61605

• RP001534: SRAN FM combined service • RP000361: Link Supervision with BFD

61606

• RP001534: SRAN FM combined service • RP000361: Link Supervision with BFD

61607

• RP001534: SRAN FM combined service • RP000365: Electrical 10/100/1000-Base-T Interface

61610

• RP001534: SRAN FM combined service • RP000360: IP Transport Network Measurements

61611

• RP001534: SRAN FM combined service • RP000360: IP Transport Network Measurements

61622

• RP000176: MLPPP termination

61632

• RP001534: SRAN FM combined service • RP000589: IPv4/IPv6 Transport Stack

61639

• RP000439: IPsec Emergency Bypass

61641

• RP001534: SRAN FM combined service • RP000465: Local and Remote IP Traffic Capturing

61643

• RP000600: Backup IPsec Tunnel

61644

• RP000356: IPsec for BTS

61645

• RP000356: IPsec for BTS

61646

• RP000356: IPsec for BTS

Clearing

Time to Live

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the service/device is unblocked by user.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the TRX is unblocked by user.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected. [All except VSWR(Voltage Standing Wave Ratio) major alarms are auto cancelled] Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected.

SBTS continuously checks for the received diagnostic 0 codes for activated BFD sessions as and when BFD messages are received from the peer. The SBTS cancels the alarm autonomously once the BFD functionality for any BFD sessions belonging to that BFD As soon as a signal that conforms to the expected frame 0 group is available again. format is received, the alarm will be cancelled. Device Driver software reads the alarm status directly from the HW chip.

As soon as the link transits to up and link stays up for more 0 than 10 seconds, the LOS alarm will be cancelled.

The alarm condition for a protect policy does not exist anymore if the latest IKE message is answered by the peer. The fault is cancelled as soon as the fault condition does not exist for any SW registers the expiration of the loopback timer. protect policy. Note: When IPsec backup tunnel feature is enabled, DPD alarm due to the primary As soon as the EBER is not exceeded anymore,isthe alarm tunnel failure shall be cleared when switch-over is canceled.for all primary successful tunnels(that is, all secondary tunnels are successfully established). Similarly, any DPD alarmsignal raisedisdue to secondary tunnel As soon as a multiframe detected, the alarm is failure will be cleared cancelled. when switchback successful for the secondary tunnels (that The Device Driverissoftware reads alarm status directly is, all primary tunnels from the HW chip. are successfully established). As soon as no AIS signal is received, the alarm is canceled. The Device Driver software reads the alarm status directly from the HW chip. As soon there is no remote defect indication received on the interface, the alarm is canceled.

0

0

0

0

0

0

Device Driver software reads the alarm status directly from 0 the HW chip.

Device Driver software reads the alarm status directly from 0 the HW chip. The alarm is canceled if the PPP-link is up again for 100 milliseconds. This alarm is automatically cleared when at least one of the 0 PPP-links in the ML-PPP/SL-PPP interface is up and running for more than 100 milliseconds. For a session that is not set locally in AdminDown mode, 0 the SBTS continuously monitors the received amount of BFD packets from the peer during the configurable detection time. If the peer sends again BFD packets, the alarm is cancelled. For an active BFD session SBTS checks continuously the 0 diagnostic codes in the BFD packets received from the BFD peer. The system cancels the alarm autonomously once the local BFD session again receives error-free BFD packets from its BFD peer.

The alarm is cancelled once an auto-negotiation process has taken place, which does not generate a downshift event nor a clock mode which does not fit to the synchronous Ethernet configuration.

0

The alarm is cleared, if during 5 consecutive 1-min periods 0 In case a clock mode mismatch is cause of the alarm, then the average value of the RTT remains below the threshold. the alarm is cancelled as well, when removing the Ethernet interface from the SBTS synchronization priority list (in case clock mode is clock master). The alarm is cleared, after at least 2 observation periods 0 are error free again.

Device Driver software reads the alarm status directly from 0 the HW chip.

The alarm is cleared once the duplicate address is either deleted or changed to a different address.

0

IPsec emergency bypass active state is exited by operator 0 interaction (parameter "IPsec emergency bypass exit active mode request") or reboot. The alarm is cleared when the IP traffic capturing session is 0 stopped.

The alarm is cancelled when SBTS has switched back all secondary tunnels to primary IPSec tunnels due to automatic switchback or manual switchback request from operator. This applies to the following state transitions: The alarm is cancelled when the IKE SA for that peer is 1. Secondary_Active_Probing_Primary --> Primary_Active established. 2. Secondary_Active_No_Probing_Primary --> Primary_Active

0

0

The is cleared Note:alarm The alarm is also cancelled when the IPsec backup 0 -tunnel whenfeature any other alarm on the related IKE SA is raised or IPsec -feature when the BTS sends or receives an IKE_AUTH response is disabled or SBTS is rebooted. message without a AUTHENTICATION_FAILURE notification for the related policy or an failure notification This alarm is cleared 0 which will result into raising this alarm. - when the SBTS sends or receives an IKE_AUTH_RESPONSE message without a failure Note: please not that not all notifications above are send by notification for the related policy the BTS - when the SBTS sends or receives an CREATE_CHILD_SA response message without a failure notification for the related policy Note: please not that not all notifications above are send by the SBTS.

Note: See the How to Read This Report tab for instructions on the usage of Fault List Changes between issues 16.10 and17A

Fault ID

Changed

2

New

6

Changed

9

New

10

New

12

New

13

New

16

New

17

Changed

18

New

23

New

24

New

26

New

27

New

28

New

29

New

30

New

37

New

48

New

49

Changed

50

Changed

52

Changed

69

Changed

88

Changed

94

Changed

95

New

103

Changed

110

New

114

New

115

New

124

New

125

New

130

New

133

New

134

New

139

New

145

New

146

New

149

New

154

New

157

New

158

New

160

New

162

New

165

New

167

New

170

New

214

New

215

New

412

New

418

New

476

New

1400

New

1401

New

1402

New

1403

New

1404

New

1405

New

1406

New

1407

New

1408

New

1409

New

1410

New

1411

New

1412

New

1413

New

1414

New

1415

New

1416

New

1417

New

1418

New

1419

New

1420

New

1421

New

1422

New

1423

New

1424

New

1425

New

1802

New

1806

New

1807

New

1811

New

1815

New

1816

New

1817

Changed

1818

New

1819

Changed

1825

New

1834

New

1835

New

1836

New

1837

New

1838

New

1839

New

1840

New

1841

New

1842

New

1843

New

1844

New

1845

New

1846

New

1847

Changed

1848

New

1850

Changed

1858

Changed

1868

Changed

1869

Changed

1870

New

1871

New

1872

New

1873

New

1874

New

1888

New

1893

New

1898

New

1899

New

1900

New

1901

New

1902

New

1903

New

1904

New

1905

New

1906

New

1907

New

1908

New

1910

New

1911

New

1912

New

1918

New

1920

New

1921

New

1922

New

1923

New

1924

New

1925

New

1926

New

1927

New

1928

New

1931

Changed

1932

New

1933

New

1934

New

1937

New

1938

New

1955

New

1956

Changed

1957

New

1958

New

1959

New

1967

New

1982

New

1983

New

1984

New

1985

New

1986

New

1989

New

1990

New

1991

New

1992

New

1993

New

1994

New

1995

New

1999

New

2000

New

2001

New

2002

New

2004

New

2006

New

2010

New

2011

New

2016

New

2017

New

2019

New

2052

New

2054

New

2056

New

2058

New

2059

New

2060

New

2061

New

2073

New

2074

New

2078

New

2080

New

2326

New

2400

New

2401

Changed

2403

New

2404

New

2408

New

2412

New

2413

New

2414

New

2415

New

2416

New

2900

New

2901

New

4000

Changed

4001

New

4003

New

4008

New

4011

New

4019

New

4025

New

4026

New

4030

New

4036

New

4038

New

4043

New

4044

New

4045

New

4046

New

4047

New

4048

New

4066

New

4067

New

4069

New

4072

New

4073

New

4076

Changed

4077

Changed

4078

New

4082

New

4083

New

4085

New

4088

New

4090

New

4091

New

4092

New

4107

New

4110

New

4114

New

4122

New

4123

New

4124

New

4125

New

4126

New

4141

New

4142

New

4145

Changed

4153

New

4160

New

4176

New

4180

New

4203

New

4208

New

4210

New

4220

New

4238

New

4239

New

4253

New

4256

New

4261

New

4262

New

4263

New

4266

New

4267

New

4268

New

4269

New

4270

New

4271

New

4274

New

4275

New

4278

New

4282

New

4285

New

4286

New

4287

New

4293

New

4297

New

4298

New

4299

New

4300

New

4304

New

4305

New

4308

New

4309

New

4310

New

4311

New

4328

New

4329

New

4330

New

4333

New

4334

New

4335

New

4336

New

4337

New

4340

New

4341

New

4342

New

4343

New

4352

New

4365

New

4367

New

4370

New

4373

New

4374

New

4383

Changed

4387

New

4389

New

4391

New

4392

New

4393

New

4395

Changed

4396

New

4399

New

4400

New

4401

New

4406

New

4409

New

5500

New

5501

New

5502

New

6051

New

6053

New

6112

New

6117

New

6118

New

6120

New

6121

New

6150

New

6202

New

6203

New

6204

New

6205

New

6206

New

6252

New

6253

New

6257

New

6261

New

6262

New

6263

New

6264

New

6265

New

6268

Changed

6269

New

6270

New

6274

New

6278

New

6279

New

6280

New

6281

Changed

6282

New

6283

Changed

6284

New

6285

New

6286

New

6287

New

6290

New

6291

New

6292

New

6293

New

6294

New

6295

Changed

6298

New

6299

New

6303

New

6304

New

6308

New

6317

New

6321

New

6322

New

6323

New

6351

New

6450

Changed

6502

New

6561

New

6700

New

6701

New

6702

New

6706

New

6707

New

6708

New

6709

New

6850

New

6851

New

6852

New

6854

Changed

6855

New

6856

New

6857

New

6858

New

61022

New

61028

New

61029

New

61030

New

61040

New

61050

New

61074

New

61075

New

61076

New

61077

New

61079

New

61104

New

61150

New

61151

New

61152

New

61201

New

61250

New

61251

New

61252

New

61410

New

61411

New

61510

New

61605

New

61606

New

61607

New

61610

New

61611

New

61616

New

61618

New

61622

New

61623

New

61624

New

61632

New

61639

New

61641

New

61642

New

61643

New

61644

New

61645

New

61646

Removed

1935

Removed

4040

Fault Name

Used in Product

Unit temperature is high

AirScale SBTS,Flexi SBTS

Unit SW download failed

AirScale SBTS,Flexi SBTS

Difference between BTS master clock and reference frequency

AirScale SBTS,Flexi SBTS

No connection to unit

AirScale SBTS,Flexi SBTS

Baseband resources mapping to cells failure

AirScale SBTS,Flexi SBTS

TUPC configuration failure

Flexi SBTS

Unit synchronization failed

AirScale SBTS,Flexi SBTS

BTS RNC interface signalling link failure

AirScale SBTS,Flexi SBTS

BTS RNC interface signalling link failure

AirScale SBTS,Flexi SBTS

Incompatible SW version detected

AirScale SBTS,Flexi SBTS

Obsolete SW version detected

AirScale SBTS,Flexi SBTS

BTS time not corrected

AirScale SBTS,Flexi SBTS

Error in file server during file download

AirScale SBTS,Flexi SBTS

File corrupted in SW download

AirScale SBTS,Flexi SBTS

BTS SW download or activation failed

AirScale SBTS,Flexi SBTS

BTS SW download or activation failed

AirScale SBTS,Flexi SBTS

Mains power break, running battery backup

AirScale SBTS,Flexi SBTS

Unit blocked

AirScale SBTS,Flexi SBTS

Cell blocked

AirScale SBTS,Flexi SBTS

BTS blocked

AirScale SBTS,Flexi SBTS

# autonomous reset as recovery action

AirScale SBTS,Flexi SBTS

POST test failed

AirScale SBTS,Flexi SBTS

Missing NBAP cell parameters

AirScale SBTS,Flexi SBTS

Unknown HW resource

AirScale SBTS,Flexi SBTS

Unit not supported by current BTS SW version

AirScale SBTS,Flexi SBTS

Carrier power measurement does not work

AirScale SBTS,Flexi SBTS

Unit RNW configuration failure

AirScale SBTS,Flexi SBTS

Communication failure with RNC

AirScale SBTS,Flexi SBTS

Cell enabling failure

AirScale SBTS,Flexi SBTS

Not enough DSP capacity to set up a cell

AirScale SBTS,Flexi SBTS

Tx power level too low

AirScale SBTS,Flexi SBTS

Not enough resources for commissioned HSUPA

AirScale SBTS,Flexi SBTS

Rx signal level failure

AirScale SBTS,Flexi SBTS

Rx signal level failure

AirScale SBTS,Flexi SBTS

DSP mode change failed

AirScale SBTS,Flexi SBTS

DSP allocation to PIC not possible due to DSP AirScale SBTS,Flexi SBTS resource unavailable

DSP allocation to PIC not possible because DSP is occupied by some other users

AirScale SBTS,Flexi SBTS

Ten consecutive rejects received from a DSP at AirScale SBTS,Flexi SBTS DCH setup

PIC pool configuration failure

AirScale SBTS,Flexi SBTS

Not enough CCCH Processing Set licenses commissioned

AirScale SBTS,Flexi SBTS

Hanging HSPA resources in DSP

AirScale SBTS,Flexi SBTS

One of the Common Transport Channels is deleted

AirScale SBTS,Flexi SBTS

Commissioned HS-RACH resource steps not possible to be allocated [LCG ]

AirScale SBTS,Flexi SBTS

Incorrect Carrier Aggregation Configuration [LCG ]

AirScale SBTS,Flexi SBTS

Unsupported Carrier Aggregation Group ID change [LCG ]

AirScale SBTS,Flexi SBTS

Unsupported TX Configuration

AirScale SBTS,Flexi SBTS

Flash operation failure

AirScale SBTS,Flexi SBTS

Flash operation failure

AirScale SBTS,Flexi SBTS

Fault between FSM and FSP because of the lack of RP1 clock

AirScale SBTS,Flexi SBTS

Fatal OSE Error

AirScale SBTS,Flexi SBTS

Antenna link is down

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

[User defined]

AirScale SBTS,Flexi SBTS

BTS file error

AirScale SBTS,Flexi SBTS

Communication failure

AirScale SBTS,Flexi SBTS

Invalid frequency channel for the BTS HW

AirScale SBTS,Flexi SBTS

Baseband bus configuration of was rejected

AirScale SBTS,Flexi SBTS

Not able to synchronize baseband bus with AirScale SBTS,Flexi SBTS

Transmission clock missing

AirScale SBTS,Flexi SBTS

Oven oscillator heating failure

AirScale SBTS,Flexi SBTS

BTS master clock tuning failure

AirScale SBTS,Flexi SBTS

Oven oscillator clock missing

AirScale SBTS,Flexi SBTS

Transmission parameters missing

AirScale SBTS,Flexi SBTS

Mast Head Amplifier fault above current window,

AirScale SBTS,Flexi SBTS

Mast Head Amplifier fault below current window,

AirScale SBTS,Flexi SBTS

Antenna line failure

AirScale SBTS,Flexi SBTS

VSWR major alarm

AirScale SBTS,Flexi SBTS

VSWR minor alarm

AirScale SBTS,Flexi SBTS

Low noise amplifier failure

AirScale SBTS,Flexi SBTS

Filter tuning failure

AirScale SBTS,Flexi SBTS

Filter unit faulty

AirScale SBTS,Flexi SBTS

RET Antenna control failure

AirScale SBTS,Flexi SBTS

RET Antenna control failure

AirScale SBTS,Flexi SBTS

RET Antenna control failure

AirScale SBTS,Flexi SBTS

RET Antenna control failure

AirScale SBTS,Flexi SBTS

RET Antenna control failure

AirScale SBTS,Flexi SBTS

Antenna line device HW failure

AirScale SBTS,Flexi SBTS

Antenna line device missing software

AirScale SBTS,Flexi SBTS

SW corrupted

AirScale SBTS,Flexi SBTS

Faulty configuration of system modules

AirScale SBTS,Flexi SBTS

BTS configuration error (not enough HW for LCR)

AirScale SBTS,Flexi SBTS

MHA operation degraded

AirScale SBTS,Flexi SBTS

MHA operation failure

AirScale SBTS,Flexi SBTS

Antenna Line Device Operation Failure

AirScale SBTS,Flexi SBTS

Antenna Line Device Operation Failure

AirScale SBTS,Flexi SBTS

Antenna Line Device Operation Failure

AirScale SBTS,Flexi SBTS

Antenna Line Device Operation Failure

AirScale SBTS,Flexi SBTS

Antenna line device configuration failure

AirScale SBTS,Flexi SBTS

Internal delay measurement failure

AirScale SBTS,Flexi SBTS

PPS reference missing

AirScale SBTS,Flexi SBTS

2M external reference missing

AirScale SBTS,Flexi SBTS

RF Module configuring failed

AirScale SBTS,Flexi SBTS

RF Module critical file not found

AirScale SBTS,Flexi SBTS

RF Module file not found

AirScale SBTS,Flexi SBTS

Frame clock missing

AirScale SBTS,Flexi SBTS

RF BB bus synchronization error

AirScale SBTS,Flexi SBTS

RF BB bus configuration error

AirScale SBTS,Flexi SBTS

RF BB bus connection transmission error

AirScale SBTS,Flexi SBTS

TX out of order

AirScale SBTS,Flexi SBTS

RF Module gain adjusting failure

AirScale SBTS,Flexi SBTS

RF Module filter input power missing

AirScale SBTS,Flexi SBTS

RX out of order

AirScale SBTS,Flexi SBTS

RF Module out of order

AirScale SBTS,Flexi SBTS

RF Module power supply output faulty

AirScale SBTS,Flexi SBTS

No feedback signal

AirScale SBTS,Flexi SBTS

Transmission quality deteriorated

AirScale SBTS,Flexi SBTS

Temperature too low (Heating ongoing)

AirScale SBTS,Flexi SBTS

Unit unidentified

AirScale SBTS,Flexi SBTS

Configuration file corrupted

AirScale SBTS,Flexi SBTS

Post test failed

AirScale SBTS,Flexi SBTS

Module Clock faulty

AirScale SBTS,Flexi SBTS

RF Power decreased

AirScale SBTS,Flexi SBTS

FPGA SW update failed

AirScale SBTS,Flexi SBTS

RF Module blocked

AirScale SBTS,Flexi SBTS

No module fan detected

AirScale SBTS,Flexi SBTS

Cooling fan broken:

AirScale SBTS,Flexi SBTS

Cooling fan has reduced from the set speed

AirScale SBTS,Flexi SBTS

Unit (module) dangerously overheating

AirScale SBTS,Flexi SBTS

Pipe dangerously overheating

AirScale SBTS,Flexi SBTS

Increased BER detected on the optical connection to Radio Module

AirScale SBTS,Flexi SBTS

Critical BER detected on the optical connection AirScale SBTS,Flexi SBTS to Radio Module

Antenna line switched off due to high VSWR

AirScale SBTS,Flexi SBTS

RP3 routing collisions are detected on FR module

AirScale SBTS,Flexi SBTS

RF Module power input faulty

AirScale SBTS,Flexi SBTS

Severe SFP reception power aggravation

AirScale SBTS,Flexi SBTS

RF Module External Alarm and Control lines configuration failed

AirScale SBTS,Flexi SBTS

TX output overdrive

AirScale SBTS,Flexi SBTS

RF Module faulty primary optical link

AirScale SBTS,Flexi SBTS

TX input overdrive

AirScale SBTS,Flexi SBTS

SFP on RF Module faulty or unsupported

AirScale SBTS,Flexi SBTS

Receive diversity expansion module communication failure

AirScale SBTS,Flexi SBTS

Radio module internal communication failure

AirScale SBTS,Flexi SBTS

Radio module access panel open

AirScale SBTS,Flexi SBTS

Radio module internal hardware configuration mismatch

AirScale SBTS,Flexi SBTS

Radio module internal hardware assignment indeterminate

AirScale SBTS,Flexi SBTS

Radio module low optical signal level to upper hop

AirScale SBTS,Flexi SBTS

Radio module low optical signal level to next hop

AirScale SBTS,Flexi SBTS

PIM Performance Measurement Threshold 2 Exceeded

AirScale SBTS

Optical Interface faulty

AirScale SBTS,Flexi SBTS

Optical Interface faulty

AirScale SBTS,Flexi SBTS

Receiving failure in Optical Interface

AirScale SBTS,Flexi SBTS

10b8b coding error in optical interface device

AirScale SBTS,Flexi SBTS

Optical interface data/control/ethernet buffer full AirScale SBTS,Flexi SBTS

Optical interface data/control/ethernet buffer full AirScale SBTS,Flexi SBTS

OIC MCU Buffer Full

AirScale SBTS,Flexi SBTS

BB bus reception error (summing device)

AirScale SBTS,Flexi SBTS

BB bus transmission error

AirScale SBTS,Flexi SBTS

Address mismatch in summing

AirScale SBTS,Flexi SBTS

RP1 synchronization burst error

AirScale SBTS,Flexi SBTS

Buffer over/underflow in clock crossing logic

AirScale SBTS,Flexi SBTS

Firmware SW mismatch

AirScale SBTS,Flexi SBTS

Message routing problem in receiver (RX)

AirScale SBTS,Flexi SBTS

Summing not enabled for message type

AirScale SBTS,Flexi SBTS

Transmission rule collision in Muksu

AirScale SBTS,Flexi SBTS

Overload collision in transmitter

AirScale SBTS,Flexi SBTS

SRIO enumeration

AirScale SBTS,Flexi SBTS

SRIO retry stopped

AirScale SBTS,Flexi SBTS

Eeprom read error

AirScale SBTS,Flexi SBTS

SRIO host link down

AirScale SBTS,Flexi SBTS

SRIO link degradation

AirScale SBTS,Flexi SBTS

TRX initialization failure

AirScale SBTS,Flexi SBTS

TRX control plane link failure

AirScale SBTS,Flexi SBTS

Configuration mismatch between BSC and BTS AirScale SBTS,Flexi SBTS

RSSI difference between main and diversity paths exceed the threshold

AirScale SBTS,Flexi SBTS

BCF Power compression feature license missing

AirScale SBTS,Flexi SBTS

OMU signaling connection failure in Abis interface

AirScale SBTS,Flexi SBTS

Invalid BTS configuration or timeout from BSC

AirScale SBTS,Flexi SBTS

BSC does not respond to BTS initialization procedure

AirScale SBTS,Flexi SBTS

TRX added to an antenna hopping sector at runtime

AirScale SBTS,Flexi SBTS

Mismatch in the commissioned and configured AirScale SBTS,Flexi SBTS BCF identifier

PIM Performance Measurement Out-ofCorrection Range

AirScale SBTS

Hardware and Pim Cancellation Feature Activation Mismatch

AirScale SBTS

Incoherence in cell configuration

AirScale SBTS,Flexi SBTS

BTS reset required

AirScale SBTS,Flexi SBTS

Transmission path failure

AirScale SBTS,Flexi SBTS

Power level not supported

AirScale SBTS,Flexi SBTS

GPS Receiver alarm: control interface not available

AirScale SBTS,Flexi SBTS

Master unit has lost connection to the slave unit AirScale SBTS,Flexi SBTS

Internal MTU configuration failure

AirScale SBTS,Flexi SBTS

Toggling:

AirScale SBTS,Flexi SBTS

BTS is uncommissioned

AirScale SBTS,Flexi SBTS

Invalid configuration file

AirScale SBTS,Flexi SBTS

Radio master conflict

AirScale SBTS,Flexi SBTS

Tuning frequency out of range

AirScale SBTS,Flexi SBTS

Incoherency in cell configuration

AirScale SBTS,Flexi SBTS

Antenna line faulty

AirScale SBTS,Flexi SBTS

Antenna line operation degraded

AirScale SBTS,Flexi SBTS

Antenna line device SW download failure

AirScale SBTS,Flexi SBTS

Antenna line device SW download failure

AirScale SBTS,Flexi SBTS

SRIO multicast configuration failed

AirScale SBTS,Flexi SBTS

Calibration initialization failure

AirScale SBTS,Flexi SBTS

ALD Port power failure

AirScale SBTS,Flexi SBTS

Parallel optical link length mismatch

AirScale SBTS,Flexi SBTS

Fan vendor not detected

AirScale SBTS,Flexi SBTS

Distributed site support not enabled

AirScale SBTS,Flexi SBTS

FSP overheating

AirScale SBTS,Flexi SBTS

Cooling fan broken

AirScale SBTS,Flexi SBTS

SW fallback

AirScale SBTS,Flexi SBTS

SW fallback

AirScale SBTS,Flexi SBTS

SW fallback

AirScale SBTS,Flexi SBTS

File System access failed

AirScale SBTS,Flexi SBTS

Cell power failure

AirScale SBTS,Flexi SBTS

BTS reset time increased

AirScale SBTS,Flexi SBTS

Summing service default initialization failed

AirScale SBTS,Flexi SBTS

Power on #smodLogicalId #pwrLineId line switched off remotely by user

AirScale SBTS,Flexi SBTS

Peer system module connection lost

AirScale SBTS,Flexi SBTS

Synchronization master missing

AirScale SBTS,Flexi SBTS

GPS receiver alarm: not tracking satellites

AirScale SBTS,Flexi SBTS

GPS receiver alarm: survey in progress

AirScale SBTS,Flexi SBTS

GPS receiver alarm: no stored position

AirScale SBTS,Flexi SBTS

GPS receiver alarm: position questionable

AirScale SBTS,Flexi SBTS

GPS receiver alarm: EEPROM invalid

AirScale SBTS,Flexi SBTS

DC voltage administratively disabled

AirScale SBTS,Flexi SBTS

3GPP/AISG communication administratively disabled

AirScale SBTS,Flexi SBTS

Validation of signed file failed

AirScale SBTS,Flexi SBTS

Reference clock missing in startup

AirScale SBTS,Flexi SBTS

BTS synchronization is missing during startup

AirScale SBTS,Flexi SBTS

Failure in log file gathering

AirScale SBTS,Flexi SBTS

Operation on shared optical port failed

AirScale SBTS,Flexi SBTS

Failure in connection to Real-time PM Collection Entity

AirScale SBTS,Flexi SBTS

Unit initialization failure

AirScale SBTS,Flexi SBTS

External GPS receiver in holdover

AirScale SBTS,Flexi SBTS

Radio slave has taken temporary radio master role

AirScale SBTS,Flexi SBTS

Antenna line setup failure

AirScale SBTS,Flexi SBTS

Antenna line device operation failure

AirScale SBTS,Flexi SBTS

Shared radio not synchronized to Radio Master AirScale SBTS,Flexi SBTS

Fiber delay and antenna round trip delay exceeded

AirScale SBTS,Flexi SBTS

Cell disabled due to unknown problem; logs collected

AirScale SBTS,Flexi SBTS

SRIO link outage

AirScale SBTS,Flexi SBTS

SRIO domain ID collision

AirScale SBTS,Flexi SBTS

Failure to verify the signature of a signed software release

AirScale SBTS,Flexi SBTS

Failure to verify a signed software release

AirScale SBTS,Flexi SBTS

Unsigned software release has been successfully downloaded

AirScale SBTS,Flexi SBTS

Failure to download software due to missing software signature

AirScale SBTS,Flexi SBTS

LNA in bypass mode

AirScale SBTS,Flexi SBTS

FR not critical functionality not supported or are AirScale SBTS,Flexi SBTS not configured correctly.

CRAN configuration alarm

AirScale SBTS,Flexi SBTS

CRAN inter-BTS connection loss alarm

AirScale SBTS,Flexi SBTS

RF module unauthorized

AirScale SBTS,Flexi SBTS

Configuration and hardware mismatch

AirScale SBTS,Flexi SBTS

HSDPA users limitation alarm

AirScale SBTS,Flexi SBTS

HSUPA users limitation alarm

AirScale SBTS,Flexi SBTS

LTE users limitation alarm

AirScale SBTS,Flexi SBTS

IP Traffic Capacity Limit

AirScale SBTS,Flexi SBTS

NTP Server $IP unavailable

AirScale SBTS,Flexi SBTS

ToP reference missing

AirScale SBTS,Flexi SBTS

Synchronous Ethernet reference missing

AirScale SBTS,Flexi SBTS

PDH reference missing

AirScale SBTS,Flexi SBTS

Too long fiber for mDTX activation

AirScale SBTS,Flexi SBTS

Inter eNB carrier aggregation configuration does not match available baseband HW

AirScale SBTS,Flexi SBTS

Micro DTX configuration failure

AirScale SBTS,Flexi SBTS

Connection Unstable At 6Gbps

AirScale SBTS,Flexi SBTS

Connection Unstable At 3Gbps

AirScale SBTS,Flexi SBTS

Optical cable inter-BTS or inter FSP cards too long for CRAN

AirScale SBTS,Flexi SBTS

Manual location entry not supported

AirScale SBTS,Flexi SBTS

Radio memory consumption exceeds abnormal AirScale SBTS,Flexi SBTS threshold

Radio memory consumption exceeds critical threshold

AirScale SBTS,Flexi SBTS

RTWP level below threshold

AirScale SBTS,Flexi SBTS

Serial console activated

AirScale SBTS,Flexi SBTS

DSP U-Plane computing environment startup failed

AirScale SBTS,Flexi SBTS

LTE-LTE RF sharing configuration alarm

AirScale SBTS,Flexi SBTS

Active users license limitation

AirScale SBTS,Flexi SBTS

Previously downloaded plan [planId] was overwritten by a new plan [planId]

AirScale SBTS,Flexi SBTS

FSP subunit lost

AirScale SBTS,Flexi SBTS

Optical link speed change failure

AirScale SBTS,Flexi SBTS

Max R99 CEs limitation alarm

AirScale SBTS,Flexi SBTS

No connection between primary and BTS extension system module

AirScale SBTS,Flexi SBTS

Power on #smodLogicalId #pwrLineId line switched off at the front panel

AirScale SBTS,Flexi SBTS

Ethernet malfunction between BTS primary and AirScale SBTS secondary system module

Multiple Radio Sharing Unsupported by Peer System Module

AirScale SBTS,Flexi SBTS

IP Address Conflict Between Radio Modules

AirScale SBTS,Flexi SBTS

IP Address Conflict Between Peer System Modules

AirScale SBTS,Flexi SBTS

Virtual node not responding

AirScale SBTS,Flexi SBTS

Frequency configuration error

AirScale SBTS,Flexi SBTS

OTDOA PRS transmission disabled

AirScale SBTS,Flexi SBTS

BTS Mediator connection lost

AirScale SBTS,Flexi SBTS

RAT SW Fallback

AirScale SBTS,Flexi SBTS

Configuration and RF Module mismatch for Reduced LTE Guard Band

AirScale SBTS,Flexi SBTS

Cells shutdown due to mains power break

AirScale SBTS,Flexi SBTS

Unable to assign IP Address to radio

AirScale SBTS,Flexi SBTS

One or more carrier groups blocked

AirScale SBTS,Flexi SBTS

Internal BTS software/database incompatibility AirScale SBTS,Flexi SBTS problem

Phase error exceeds threshold set by BSC

AirScale SBTS,Flexi SBTS

One or more TRXes did not receive System Information from BSC

AirScale SBTS,Flexi SBTS

RX gain configuration failure

AirScale SBTS,Flexi SBTS

Maximum number of 1xRTT neighbor relations AirScale SBTS,Flexi SBTS per cell exceeded

Maximum number of 1xRTT NR per cell and carrier exceeded

AirScale SBTS,Flexi SBTS

SIB15 information incomplete

AirScale SBTS,Flexi SBTS

Beamforming calibration failure in RF data path AirScale SBTS,Flexi SBTS

U-plane overload detected

AirScale SBTS,Flexi SBTS

Phich Power Boost not applied

AirScale SBTS,Flexi SBTS

High interference to UL subframe

AirScale SBTS,Flexi SBTS

High interference to UL special subframe

AirScale SBTS,Flexi SBTS

U-plane overload detected

AirScale SBTS,Flexi SBTS

U-plane overload detected

AirScale SBTS,Flexi SBTS

GTP-U Path Failure

AirScale SBTS,Flexi SBTS

Transport layer connection failure in S1 interface

AirScale SBTS,Flexi SBTS

Transport layer connection failure in X2 interface

AirScale SBTS,Flexi SBTS

S1 SCTP path failure

AirScale SBTS,Flexi SBTS

Transport layer connection failure in M3 interface

AirScale SBTS,Flexi SBTS

M3 SCTP path failure

AirScale SBTS,Flexi SBTS

Incorrect radio network parameters

AirScale SBTS,Flexi SBTS

Cell configuration data distribution failed

AirScale SBTS,Flexi SBTS

Cell reconfiguration data distribution failed

AirScale SBTS,Flexi SBTS

Failure in connection between BTS and BTSMED or 3rd party tool

AirScale SBTS,Flexi SBTS

BTS vendor-specific file fault

AirScale SBTS,Flexi SBTS

Failure in trace session

AirScale SBTS,Flexi SBTS

No MME capacity assigned by Core Network

AirScale SBTS,Flexi SBTS

Maximum number of neighbor eNBs/cells exceeded

AirScale SBTS,Flexi SBTS

Maximum number of WCDMA neighbor cells is AirScale SBTS,Flexi SBTS exceeded

Maximum number of WCDMA neighbor relations is exceeded

AirScale SBTS,Flexi SBTS

Maximum number of WCDMA neighbor relations per cell and carrier is exceeded

AirScale SBTS,Flexi SBTS

Neighbor cell ambiguity detected

AirScale SBTS,Flexi SBTS

MFBI cell configuration conflict

AirScale SBTS,Flexi SBTS

PCI confusion detected

AirScale SBTS,Flexi SBTS

Phase error exceeds 5 us limit

AirScale SBTS,Flexi SBTS

WCDMA PSC confusion detected

AirScale SBTS,Flexi SBTS

Inter eNB CA parameter(s) inconsistency in between eNBs

AirScale SBTS,Flexi SBTS

Inter eNB SW inconsistency in between cluster AirScale SBTS,Flexi SBTS members

Inter eNB communication failure

AirScale SBTS,Flexi SBTS

Overload detected: max number of neighbor relation objects reached

AirScale SBTS,Flexi SBTS

Overload monitoring: High number of neighbor AirScale SBTS,Flexi SBTS related objects

Inter eNB synchronization loss

AirScale SBTS,Flexi SBTS

SRIO topology failure

AirScale SBTS,Flexi SBTS

Carrier aggregation relation configuration error AirScale SBTS,Flexi SBTS

Resource pool configuration failed

AirScale SBTS,Flexi SBTS

eNB configuration failed

AirScale SBTS,Flexi SBTS

Not enough PUSCH resources for PRACH

AirScale SBTS,Flexi SBTS

PUCCH configuration inconsistency

AirScale SBTS,Flexi SBTS

Invalid sidelink transmit pool configuration

AirScale SBTS,Flexi SBTS

Maximum number of 1xRTT neighbor cells exceeded

AirScale SBTS,Flexi SBTS

X2 interface recovery failure

AirScale SBTS,Flexi SBTS

X2 interface setup failure

AirScale SBTS,Flexi SBTS

S1 interface setup failure

AirScale SBTS,Flexi SBTS

S1 interface recovery failure

AirScale SBTS,Flexi SBTS

S1 eNB configuration update failure

AirScale SBTS,Flexi SBTS

RIM interface timeout

AirScale SBTS,Flexi SBTS

RIM interface error

AirScale SBTS,Flexi SBTS

System information broadcast parameters overflow

AirScale SBTS,Flexi SBTS

Diagnostic Files collected

AirScale SBTS,Flexi SBTS

High memory consumption

AirScale SBTS,Flexi SBTS

Sleeping cell suspicion; logs collected

AirScale SBTS,Flexi SBTS

Correctable bit toggling error

AirScale SBTS,Flexi SBTS

Critical bit toggling error

AirScale SBTS,Flexi SBTS

Not critical bit toggling error

AirScale SBTS,Flexi SBTS

DSP platform fatal error

AirScale SBTS,Flexi SBTS

DSP application fatal error

AirScale SBTS,Flexi SBTS

Externally triggered DSP fatal error

AirScale SBTS,Flexi SBTS

DSP concurrent crash error

AirScale SBTS,Flexi SBTS

M3 interface recovery failure

AirScale SBTS,Flexi SBTS

M3 interface setup failure

AirScale SBTS,Flexi SBTS

MBMS subframe pattern share exceeds available share

AirScale SBTS,Flexi SBTS

MCE configuration update failure

AirScale SBTS,Flexi SBTS

MCE internal communication failure

AirScale SBTS,Flexi SBTS

MBMS session admission failure - not enough resources

AirScale SBTS,Flexi SBTS

MBMS session admission - partial admission only

AirScale SBTS,Flexi SBTS

MBMS session admission failure - overlapping MBSFN config

AirScale SBTS,Flexi SBTS

BFDGRP-$BFDGRPID down

AirScale SBTS,Flexi SBTS

LOF on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

LOS on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

Dead Peer Detected

AirScale SBTS,Flexi SBTS

Interface under test on $UNIT, $INTERFACE for $LOOPTIMEOUT minutes

AirScale SBTS,Flexi SBTS

Missing or non-compliant SFP module on unit $U, interface $IF

AirScale SBTS,Flexi SBTS

CRL Update Failure

AirScale SBTS,Flexi SBTS

Link OAM loopback inserted on unit $U, interface $F by $P peer

AirScale SBTS,Flexi SBTS

Link OAM link lost on unit $U, interface $F

AirScale SBTS,Flexi SBTS

Link OAM critical link event $E on unit $U, interface $F

AirScale SBTS,Flexi SBTS

SFP HW Failure on unit $U, interface $IF

AirScale SBTS,Flexi SBTS

EBER on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

LOMF on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

AIS on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

RDI on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

Transport module missing: $unit

AirScale SBTS,Flexi SBTS

IPCP Failure

AirScale SBTS,Flexi SBTS

LCP failure

AirScale SBTS,Flexi SBTS

PPP Interface down

AirScale SBTS,Flexi SBTS

CCM fault level $ prio $p cause $c

AirScale SBTS,Flexi SBTS

ETH AIS fault interface $IF level $l mac $x

AirScale SBTS,Flexi SBTS

Automatic BTS Operator Certificate retrieval unsuccessful

AirScale SBTS,Flexi SBTS

BFD-$BFDID down in ingress

AirScale SBTS,Flexi SBTS

BFD-$BFDID down in egress

AirScale SBTS,Flexi SBTS

Auto-negotiation mismatch on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

RTT threshold crossed on TWAMP-$TWAMPID AirScale SBTS,Flexi SBTS

PLR threshold crossed on TWAMP-$TWAMPID AirScale SBTS,Flexi SBTS

Vendor BTS certificate is about to expire

AirScale SBTS,Flexi SBTS

BTS and/or peer trust anchor expired or due to AirScale SBTS,Flexi SBTS expire

MLPPP link Degrade

AirScale SBTS,Flexi SBTS

SyncE SSM Timed Out on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

SyncE Quality Level Degraded on $UNIT, $INTERFACE

AirScale SBTS,Flexi SBTS

Dup Addr detected$DUPLICATEIPV6ADDRESS

AirScale SBTS,Flexi SBTS

IPsec emergency bypass active

AirScale SBTS,Flexi SBTS

IP Traffic Capturing ongoing on $UNIT, $INTERFACE, $MACADDRESS

AirScale SBTS,Flexi SBTS

BTS Local OAM user account $A has been locked

AirScale SBTS,Flexi SBTS

IPSec tunnel switchover

AirScale SBTS,Flexi SBTS

IKE authentication failure

AirScale SBTS,Flexi SBTS

IKE SA failure

AirScale SBTS,Flexi SBTS

IPSec SA failure

AirScale SBTS,Flexi SBTS

Cooling fan is over speeding

AirScale SBTS,Flexi SBTS

Unit initialization failure

AirScale SBTS,Flexi SBTS

Detecting Unit

Source

AirScale SBTS:FCT, FSP(HW rel.4), Flexi SBTS:FCT, FSP(HW rel.3)

FCT(HW rel.3), FCT(HW rel.4)

AirScale SBTS: FCT(Hw Rel4)Flexi AirScale SBTS: SBTS:FCT(Hw Rel3) - FCT AirScale SBTS: FCT; Flexi SBTS: FCT;

Flexi SBTS: FCT(HW rel.3); AirScale SBTS: FCT(HW rel.4)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

Flexi SBTS: FCT

Flexi SBTS: FCT(HW rel.3); AirScale SBTS:FCT(HW rel.4)

AirScale SBTS: FCT (HW rel.4); Flexi BTS: FCT (HW rel.3)

AirScale SBTS: FCT (HW rel.4); Flexi BTS: FCT (HW rel.3)

- ABIx Flexi SBTS: - DSP - FCT (HW rel.3) ABIx Flexi SBTS: AirScale SBTS: FSP - FCT - FCT (HW rel.4) FBB FCT - FSP RET - FBB FR Flexi - DSPSBTS: RAE - WCDMA RAT LNA Flexi SBTS: - FCT (FSMr3), - FSP, RNC - FBB RNC AirScale SBTS: - FCT (HW rel.4),

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS: - ABIx - FCT (FSMr3), - FSP, - FR

AirScale SBTS: - FCT (HW rel.4),

Flexi SBTS: FCT(HW rel.3); AirScale SBTS:FCT(HW rel.4)

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS:FCT(HWrel.4)Flexi SBTS:FCT(HWrel.3);

Flexi SBTS: FCT (HW rel.3),AirScale SBTS: FCT (HW rel.4) Flexi SBTS: FCT (HW rel.3),AirScale SBTS: FCT (HW rel.4) Flexi SBTS: FCT, FSP (HW rel.3),AirScale SBTS: FCT, FSP (HW rel.4) Flexi SBTS: FCT, FSP (HW rel.3),AirScale SBTS: FCT, FSP (HW rel.4)

AirScale SBTS: Flexi SBTS: - FCT (HW rel.4) - FCT (HW rel.3) FCT (HW rel.3), FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) Flexi SBTS: - FCT (FSMr3), - FR AirScale SBTS, FlexiSBTS: FCT (HW rel3,4), FR AirScale SBTS: AirScale SBTS, FlexiSBTS: FSP FCT - FCT(HW (HWrel3,4), rel.4), FR - FR

Airscale SBTS: ASIA, FlexiSBTS: FCT

Airscale SBTS: ASIA, FlexiSBTS: FCT FSP

FCT (HW rel.3), FCT (HW rel.4)

FR

AirScale SBTS:FCT(HWrel.4); Flexi LCR SBTS:FCT(HWrel.3);

AirScale SBTS:FCT(HWrel.4); Flexi Flexi SBTS: SBTS:FCT(HWrel.3); - FCT (HW rel.3) AirScale SBTS:FCT(HWrel.4); Flexi AirScale SBTS: SBTS:FCT(HWrel.3); AirScale SBTS: - FCT (HW rel.4), AirScale SBTS:FCT(HW rel.4); Flexi SBTS :FCT(HWrel.3)

- FCT (HW rel.4) - ABIx, AirScale SBTS -ABIx - FR. -FCT (HW rel.4) Flexi SBTS: Flexi SBTS: - FCT (HW rel.3), - FSP - FR, - DSP - FSP, - FCT (HW rel.3) - FBB.

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

RNC

AirScale SBTS:FCT(HW rel.4); Flexi SBTS :FCT(HWrel.3)

AirScale SBTS: - ABIx

AirScale SBTS:FCT(HW rel.4); Flexi SBTS :FCT(HWrel.3)

Flexi SBTS: Flexi SBTS: - FSP, - FSP

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

- FBB, -Tx1-n/Rx1-n FBB - FR, Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB, RX1-n, AirScaleTX1-n SBTS: - ABIx (AirScale Capacity Indoor subunit)

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

RNC - FR

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCR

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

FCT

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Tx1-n

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

FCT

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Antenna Line

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Antenna Line

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCR

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCR

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCR

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

FCT

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCR

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCG

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCG

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

LCG

AirScale SBTS: ABIx(HW rel4); Flexi SBTS:FSP, FBB;

LCR

AirScale SBTS:FCT(HW rel.4); Flexi SBTS :FCT(HWrel.3)

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS:FCT(HW rel.4); Flexi SBTS :FCT(HWrel.3)

FSP, FBB, ABIx

Flexi SBTS: FCT(HW rel.3); AirScale SBTS:FCT(HW rel.4)

Flexi SBTS: FCT(HW rel.3); AirScale SBTS:FCT(HW rel.4)

AirScale SBTS: Flexi SBTS: - FCT (HW rel.4) - FCT Flexi SBTS: - FSP Flexi SBTS: - FBB - FCT AirScale SBTS: Flexi SBTS: - ABIx - FSP - FSP - FBB AirScale SBTS: - ABIx

AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR

AirScale SBTS: AirScale SBTS: - ABIx Flexi SBTS: - FCT (HW rel.4)

AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR

- FSP - FR AirScale SBTS: - FBB - FCT (HW rel.4)

AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR

Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR - FCT - FR Flexi SBTS: - FCT - FR

AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR

AirScale SBTS: - FCT (HW rel.4) - FR AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR - FCT - FR Flexi SBTS: - FCT - FR

AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR

AirScale SBTS: - FCT (HW rel.4) - FR AirScale SBTS: - FCT (HW rel.4)

Flexi SBTS: - FR AirScale SBTS: - FCT - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: FCT (HW rel.4), AirScale SBTS: FR; Flexi SBTS: FCT (HW rel.3), - FCT FR - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: FCT (HW rel.4), AirScale SBTS: FR; Flexi SBTS: FCT (HW rel.3), - FCT FR - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: FCT (HW rel.4), AirScale SBTS: FR; Flexi SBTS: FCT (HW rel.3), - FCT FR - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS: FCT (HW rel.4), AirScale SBTS: FR; Flexi SBTS: FCT (HW rel.3), - FCT FR - FCT (HW rel.4) - FR Flexi SBTS: - FR AirScale SBTS:FCT(HW rel4)Flexi AirScale SBTS: SBTS:FCT(HW rel3); - FCT - FCT (HW rel.4), - FR Flexi SBTS: - ABIx, AirScale SBTS:FCT(HW rel4)Flexi AirScale SBTS: SBTS:FCT(HW rel3); - FCT - FR. - FCT (HW rel.4) - FR - FR AirScale SBTS:FCT(HWrel.4);Flexi LCR SBTS:FCT(HWrel.3); Flexi SBTS: - ABIx AirScale SBTS: FCT (HW rel.4), FR; Flexi SBTS: FCT (HW rel.3), FR

- FCT (HW rel.3), - MHA (or LNA - depends on which level AirScale SBTS:FCT(HWrel.4), ABIx; AirScale SBTS: Elementary Procedure is timed out) - FR, Flexi SBTS:FCT(HWrel.3),FSP,FBB; AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

- FCT rel.4),- depends on which level RET (HW (or RETU - FSP. Elementary Procedure is timed out) - ABIx, AirScale SBTS: - ABIx - FR, - OptIF Flexi SBTS: - OptIF. Flexi SBTS: -- FCT FSP (HW rel.3) - OptIF -- FTM FBB Flexi SBTS: - FSP - FCT (HW rel.3), - FR - FSP, - FBB - FR,

AirScale SBTS:FCT (HW rel.4); Flexi SBTS: FCT(HW rel.3);

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS:FCT(HWrel.4);Flexi FCT SBTS:FCT(HWrel.3); Flexi SBTS: - FCT(HW rel.3) AirScale SBTS:FCT(HWrel.4);Flexi AirScale SBTS: SBTS:FCT(HWrel.3); - FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

FCT (HW rel.3),FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3)

Flexi SBTS:FCT(HWrel.3);AirScale AirScale SBTS: SBTS:FCT(HWrel.4); - FCT (HW rel.4) FR

LNA Flexi SBTS:

FR

-FCT (HW rel.3) LNA

FR

Antenna line

Flexi SBTS:FCT (HW rel.3), AirScale SBTS:FCT (HW rel.4)

Antenna Line

FR

Antenna line

FR

RX1-n

FR

TX1-n, RX1-n

FR

TX1-n RX1-n

RET

RET

RET

RET

RET

RET

RET

RET

RET

RET

RET, MHA, RAE

RET, MHA, RAE

MHA, RET, RAE

MHA, RET, RAE

FCT

Filter, Radio Module

Flexi SBTS:FCT(HW rel.3); AirScale SBTS:FCT(HW rel.4);

FCT

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

LCR

MHA in AISG mode

MHA in AISG mode

MHA in AISG mode

MHA in AISG mode

Flexi SBTS:FCT (HW rel.3),AirScale SBTS:FCT (HW rel.4)

MHA AISG, RET, RAE

Flexi SBTS:FCT (HW rel.3),AirScale SBTS:FCT (HW rel.4)

MHA AISG, RET, RAE

Flexi SBTS:FCT (HW rel.3),AirScale SBTS:FCT (HW rel.4)

MHA AISG, RET, RAE

Flexi SBTS:FCT (HW rel.3),AirScale SBTS:FCT (HW rel.4)

MHA AISG, RET, RAE

FR

RET, RAE

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

AirScale SBTS:FCT(HWrel.4);Flexi AirScale SBTS: SBTS:FCT(HWrel.3); - FCT (HW rel.4) AirScale SBTS: FCT (HWrel.4);Flexi SBTS: FCT(HWrel.3);

FCT Flexi SBTS:

- FCT (HW rel.3) AirScale SBTS:FCT(HWrel.4);Flexi FR, TX1-n, RX1-n SBTS:FCT(HWrel.3);

AirScale SBTS:FR;Flexi SBTS: FR; FR

AirScale SBTS, Flexi SBTS: FR

FR

FR

FR, RX1-n

FR

FR, TX1-n, RX1-n

FR

FR, TX1-n, RX1-n

FR

FR, TX1-n

AirScale SBTS: FRx, LTX; Flexi SBTS: FRx, LTX;

TX1-n

AirScale SBTS:FR;Flexi SBTS: FR; FR; TX1-n

AirScale SBTS:FR;Flexi SBTS: FR; TX1-n

AirScale SBTS:FR;Flexi SBTS: FR; RX1-n

AirScale SBTS: FR, Flexi SBTS: FR;

FR

AirScale SBTS: FR, Flexi SBTS: FR;

FR TX1-n

FR

TX1-n

Radio Module

Antenna line

FR

FR

AirScale SBTS:FR;Flexi SBTS: FR; FR

AirScale SBTS:FR;Flexi SBTS: FR; FR, TX1-n, RX1-n

AirScale SBTS: FR, Flexi SBTS: FR;

FR

AirScale SBTS: FR, Flexi SBTS: FR;

FR

FR

TX1-n

FR

FR

FR

FR

FR

FR

FR

FAN, FAN_GROUP

FR

FAN, FAN_GROUP

FR

RFM connected over OBSAI RP1 interface or CPRI-A: FR

RRU connected over CPRI Ir interface: FR, TX1-n

FR

TX1-n

FR

FR

FR

FR

FR

Antenna line

FR

FR

FR

FR

FR

OptIf

Flexi SBTS: FCT (HW rel.3), AirScale SBTS: FCT (HW rel.4)

Radio Module

FR

TX1-n

FR

FR

FR

TX1-n

FR

OptIf

FR

RX1-n

FR

FR

FR

FR

FR

FR

FR

FR

FR

Optif

FR

Optif

FR

Antenna Line

Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

OptIF

Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

OptIF

Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

OptIF

Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

OptIF

Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

OptIF

Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

OptIF

Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

Flexi SBTS: - FCT (HW rel.3),

Flexi SBTS: FCT (HW rel.3), FTM, FBB; AirScale SBTS: FCT (HW rel.4), ABIx Flexi SBTS: FCT, FBB; AirScale SBTS: ABIx

Flexi SBTS: FCT (HW rel.3),FBB; AirScale SBTS: FCT (HW rel.4), ABIx Airscale SBTS and Flexi SBTS: FCT

AirScale SBTS: FCT (HW rel.4), ABIx; Flexi SBTS: FCT (HW rel.3), FBB

- FBB. Flexi SBTS: - FSP, AirScale SBTS: - FBB Flexi SBTS: - FCT (HW rel.4), - OptIf. - FCT (HW rel.3), - ABIx. - FBB. Flexi SBTS: AirScale SBTS: - FCT (HW rel.3), - OptIf, AirScale SBTS: - FBB. OptIf - ABIx. - FCT (HW rel.4), - ABIx. AirScale SBTS: OptIf - ASIx, - FCT (HW rel.4).

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS: FCT (HW rel.4), ABIx; Flexi SBTS: FCT (HW rel.3), FBB

AirScale SBTS: - ABIx Flexi BTS: - OptIF

AirScale SBTS: ABIx, FCT (HW rel.4); Flexi SBTS:FCT (HW rel.3), FBB

- FCT (HW rel.3) Flexi SBTS: AirScale SBTS: - FSP - FBB - FCT (HW rel.4) - OptIF

AirScale SBTS: ABIx, FCT (HW rel.4); Flexi SBTS:FCT (HW rel.3), FBB

- ABIx AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - ABIx - FCT (HW rel.3) - FBB Flexi SBTS: - FCT (HW rel.3) - FBB

AirScale SBTS: ABIx, FCT (HW rel.4); Flexi SBTS:FCT (HW rel.3), FBB

AirScale SBTS: - FCT (HW rel.4)

Flexi SBTS: FCT (HW rel.3), AirScale SBTS: FCT (HW rel.4)

- ABIx FCT (HW rel.3) FCT (HW rel.4)

Flexi SBTS: FCT (HW rel.3), AirScale SBTS: FCT (HW rel.4)

Flexi SBTS: FSP, FBBx, ABIx - FCT (HW rel.3) - FBB

Flexi SBTS: FCT (HW rel.3), AirScale SBTS: FCT (HW rel.4)

FSP, FBBx, ABIx

Flexi SBTS: FCT (HW rel.3), AirScale SBTS: FCT (HW rel.4)

FCT (HW rel.3) FCT (HW rel.4)

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BTS(sector)

Flexi SBTS: FCT (HW rel.3)

BTS(sector)

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BCF BTS(sector)

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

Antenna line

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BCF

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BCF

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BCF

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BCF

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BTS(Sector)

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

BCF

FR

Antenna Line

AirScale SBTS: FCT (HW Rel.4)

FR

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

AirScale SBTS: - FCT (HW rel.4)

FCT

- FCT (HW rel.3), FCT (HW rel.4) Flexi SBTS: - FBB

FCT

- FCT (HW rel.3) - FSP LCR - LCR

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

- FR LCR - WCDMA RAT

FCT

GNSS

FCT

AirScale SBTS: - FCT (HW rel.4) - ABIx - DSP

Flexi SBTS: - FCT (HW rel.3) - FSP

FCT

- FCT (HW rel.3), FCT (HW rel.4) - FSP

AirScale SBTS: FCT; Flexi SBTS: FSM

- FBB Flexi SBTS, AirScale SBTS: All units

FCT

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS: FCT (HWrel.4);Flexi SBTS: FCT(HWrel.3); FCT (HW rel.3), FCT (HW rel.4)

AirScale SBTS: Flexi SBTS: - FCT (HW rel.4) - FCT (HW rel.3) FR Flexi SBTS:

FR

- FCT (HW rel.3) TX1-n RX1-n

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

LCR

FR

Antenna line

FR

Antenna Line

FCT

MHA, RET, RAE

FCT

MHA, RET, RAE

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB

Flexi SBTS: FSP, FBB

FCT (HW rel.3), FCT (HW rel.4)

FR

FR

RS485 port, RET, RAE, LNA

FCT

OptIF

FCT (HW rel.3), FCT (HW rel.4)

FAN1-n

FCT (HW rel.3), FCT (HW rel.4)

Optif

FCT (HW rel.3), FCT (HW rel.4)

AirScale SBTS: - ABIx

FCT (HW rel.3), FCT (HW rel.4)

Fan/Fan group Flexi SBTS:

Flexi SBTS:FCT(HW rel.3); AirScale SBTS:FCT(HWrel.4)

Flexi SBTS:FCT(HW rel.3); AirScale SBTS:FCT(HWrel.4)

- FSP Flexi SBTS, AirScale SBTS: - FBB 4082: - FCT (HW rel.3), FCT (HW rel.4) Flexi SBTS, AirScale SBTS: 4082:

Flexi SBTS:FCT(HW rel.3); AirScale SBTS:FCT(HWrel.4)

FCT

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

4083: - FCT (HW rel.3), FCT (HW rel.4) Flexi SBTS, AirScale SBTS: - FCT (HW rel.3), FCT (HW rel.4) 4082: 4083: - FCT (HW rel.3), FCT (HW rel.4) AirScale SBTS: 4085: (for FSMr3 only) - FCT (HW rel.3), FCT (HW rel.4) - FCT (HW rel.4) - FSMr3: FCT 4083: LCR 4085: (for FSMr3 only) - FCT (HW rel.3), FCT (HW rel.4) Flexi SBTS: - FSMr3: FCT - FCT (HW rel.3) 4085: (for FSMr3 only) - FSMr3: FCT

FCT (HW rel.3), FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4), FBB, ABIx

FCT (HW rel.3), FCT (HW rel.4), FBB, ABIx

FCT (HW rel.3)

FCT (HW rel.3)

FCT (HW rel.3), FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4), Optif

Flexi SBTS:FCT (HW Rel3)

FCM, FCT OptIF

FCT (HW rel.3), FCT (HW rel.4)

GNSS

FCT (HW rel.3), FCT (HW rel.4)

GNSS

FCT (HW rel.3), FCT (HW rel.4)

GNSS

FCT (HW rel.3), FCT (HW rel.4)

GNSS

FCT (HW rel.3), FCT (HW rel.4)

GNSS

FCT (HW rel.3), FCT (HW rel.4)

Antenna Line, RS485 port, ALD, LNA

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

Antenna Line, RS485 port, ALD

Flexi SBTS: FCT (HW rel.3), FCT (HW rel.4)

AirScale SBTS: - FCT (HW rel.4)

Flexi SBTS: FCT (HW rel.3), FCT (HW rel.4)

FCT (HW rel.3)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

AirScale SBTS: Flexi SBTS: - FCT (HW rel.4) - FCT (HW rel.3) Flexi SBTS: - FCT (HW rel.3) Flexi SBTS: - FCT (HW rel.3) FR

FBBC

FBBC

AirScale SBTS:- FCT (HW rel.4)Flexi SBTS:- FCT (HW rel.3)

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

Flexi SBTS: - FCT (HW rel.3) FCT

FCT (HW rel.3), FCT (HW rel. 4)

Flexi SBTS, AirScale SBTS: - GNSS

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FR

FR

FR

FR

RET

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FR

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FR

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

LCR

Flexi SBTS FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

FCT

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FCT

Flexi SBTS : FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4);

FCT

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FCT (HW rel.3), FCT (HW rel.4)

AISG MHA

Flexi SBTS: - FCT (HW rel.3) FCT

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) LNA

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FR

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

FCT

FCT (HW rel.3)

OptIF

FCT (HW rel.3), FCT (HW rel.4)

FR

Flexi SBTS: FCT (HW rel.3); RET, RAE

FCT, RET, RAE

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

CAPLIM(LICENSE CAPACITY LIMITATION)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

CAPLIM(LICENSE CAPACITY LIMITATION)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

CAPLIM(LICENSE CAPACITY LIMITATION)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

AirScale SBTS, Flexi SBTS: CAPLIM (LICENSE CAPACITY LIMITATION)

Flexi SBTS:FCT(HWrel.3);

FCT

Flexi SBTS:FCT(HWrel.3);

FCT

Flexi SBTS:FCT(HWrel.3);

FCT

Flexi SBTS:FCT(HWrel.3)

FCT

FCT (HW rel.3), FCT (HW rel.4)

OptIF

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

FCT

Flexi SBTS: FSM; AirScale SBTS: FCT (HW rel.4)

FR

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

OptIF

FCT (HW rel.3)

OptIF

Flexi SBTS: FCT (HW Rel3)

OptIF

FCT (HW rel.3), FCT (HW rel. 4)

Flexi SBTS, AirScale SBTS: - GNSS

FR

FR

FR

FR

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

RX1-n

FCT (HW rel.3)

FCT (HW rel.3)

FCT (HW rel.4)

ABIx (AirScale Capacity Indoor subunit)

FCT (HW rel.3), FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS: FCT (HW rel.3);

CAPLIML (LICENSE CAPACITY LIMITATION)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

FCT

FCT

FSP, FBB

Flexi SBTS: FCT (HW rel.3), FBB; AirScale SBTS: FCT (HW rel.4), ABIx

OptIf

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

CAPLIM(LICENSE CAPACITY LIMITATION)

FCT (primary or secondary unit in dual core configuration)

FCT (primary or secondary unit in dual core configuration)

Flexi SBTS: FCT(HW Rel3)

FCT

AirScale SBTS: FCT (HW rel.4)

AirScale SBTS: FCT (HW rel.4)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FCT

FCT (HW rel.3), FCT (HW rel. 4)

FR

FCT (HW rel.3), FCT (HW rel. 4)

FCT (HW rel.3) FCT (HW rel.4)

Flexi SBTS: FCT (HW rel.3), AirScale SBTS: FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS: FCT (HW rel.3)

BTS(sector), WCEL, LCR.

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

FCT

Flexi SBTS: FCT (HW rel.3), AirScale SBTS: FCT (HW rel.4)

FCT (HW rel.3) FCT (HW rel.4)

Flexi SBTS:FCT(HW rel.3)

Flexi BTS FDD :FCT (HW rel.3)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3); FR

LCR, FR

Airscale SBTS: ASIA, Flexi SBTS: FCT (HW rel.3)

MRBTS

FCT (HW rel.3), FCT (HW rel. 4)

FR

Flexi SBTS: FCT (HW rel.3)

BTS(Sector)

Flexi SBTS

Flexi SBTS - FCT (HW rel.3)

Flexi SBTS: FCT (HW rel.3)

FCT

Flexi SBTS: FCT (HW rel.3)

BTS(Sector)

FR

Antenna Line

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3)

AirScale SBTS:- FCT (HW rel.4)Flexi SBTS:- FCT (HW rel.3)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) LCR

Flexi SBTS: FSP, FBB; AirScale SBTS: ABIx;

LCR

AirScale SBTS: ABIA; Flexi SBTS: FSP

LCR

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS, AirScale SBTS: LCR

AirScale SBTS: ABIx; Flexi SBTS: FSP, FBB;

LCR

AirScale SBTS: ABIx;Flexi SBTS: FSP, FBB

LCR

AirScale SBTS: ABIA; Flexi SBTS: FSP

LCR

AirScale SBTS: ABIA; Flexi SBTS: FSP

LCR

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

GTP-U

FCT (HW rel.3), FCT (HW rel.4)

LNMME

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

LNADJ

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

LNMME

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

LNM3

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

LNM3

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

FCT

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

LCR

AirScale SBTS:- FCT (HW rel.4)Flexi SBTS:- FCT (HW rel.3)

LCR

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

AirScale SBTS: - FCT (HW rel.4)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

Flexi SBTS: - FCT (HW rel.3) FCT

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) FCT

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FCT

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3)

FCT (HW rel.3), FCT (HW rel. 4)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) FCT

LCR

AirScale SBTS, Flexi SBTS: LNADJ LNADJ

FCT (HW rel.3), FCT (HW rel.4)

LNCEL

FCT

Flexi SBTS: - FCT (HW rel.3)

FCT (HW rel.3), FCT (HW rel.4)

LCR AirScale SBTS:

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

FCT (HW rel.3), FCT (HW rel.4)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

- FCT (HW rel.4) AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) FCT

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) FCT

FCT

Flexi SBTS : FCT (HW rel.3);

FCT

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

FCT

FCT

FCT

FCT

Flexi SBTS: - FSP

FCT

AirScale SBTS: AirScale SBTS: - FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

- ABIx LCR Flexi SBTS:

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

FCT (HW rel.3), FCT (HW rel. 4)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

- FCT LCR

AirScale SBTS: - FCT (HW rel.4) Flexi SBTS: - FCT (HW rel.3) FCT

FCT (HW rel.3), FCT (HW rel.4)

LNADJ

FCT (HW rel.3), FCT (HW rel.4)

LNADJ

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

LNMME

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

LNMME

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

LNMME

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS, AirScale SBTS: LNADJG LNADJW

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

Flexi SBTS, AirScale SBTS: LNADJG LNADJW

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

LCR

Flexi SBTS:FCT(HW rel.3); AirScale SBTS:FCT(HW rel.4)

AirScale SBTS: - FCT (HW rel.4), ABIx

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS: - FCT (HW rel.3), FSP, FBB AirScale SBTS: - ASIA

Flexi SBTS: FBB, FSP

- ABIA LCR

AirScale SBTS: ABIx; Flexi SBTS: FSP, FBB

Flexi SBTS: AirScale SBTS: - ABIx FCT (HW rel.3)

AirScale SBTS: ABIx; Flexi SBTS: FSP, FBB

Flexi - FSPSBTS: - FSP AirScale SBTS: - FBB - ABIx

AirScale SBTS: ABIx; Flexi SBTS: FSP, FBB

AirScale SBTS: - ABIx Flexi SBTS:

AirScale SBTS: ABIx, Flexi SBTS: FSP, FBB

Flexi SBTS: - FSP - FSP AirScale SBTS: - FBB - FBB - ABIx

Flexi SBTS: - FSP - FBB

AirScale SBTS: ABIx, Flexi SBTS: FSP, FBB

AirScale SBTS: - ABIx

AirScale SBTS: ABIx, Flexi SBTS: FSP, FBB

AirScale SBTS: ABIx, Flexi SBTS: FSP, FBB;

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

AirScale SBTS: Flexi SBTS: - ABIx - FSP AirScale SBTS: - ABIx FBB Flexi SBTS: Flexi SBTS: - FSP - FSP LNM3 - FBB - FBB

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3)

LNM3

AirScale SBTS: FCT (HW rel.4); Flexi SBTS: FCT (HW rel.3);

LNMCE

Flexi SBTS: FCT (HW rel.3); AirScale SBTS: FCT (HW rel.4)

AirScale SBTS: - FCT (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS: - FCT (HW rel.3) AirScale SBTS: - LNMCE (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

Flexi SBTS: - LNMCE (HW rel.3) LNMCE (HW rel.3), LNMCE (HW rel.4)

AirScale SBTS : FCT (HW Rel4) , Flexi SBTS: FCT (HW Rel 3);

LNMCE (HW rel.3),LNMCE (HW rel.4)

FCT (HW rel.3), FCT (HW rel.4)

LNMCE

Flexi SBTS: FCT (HW rel.3)

BFDGRP

Flexi SBTS: FCT (HW rel.3)

PPTT

Flexi SBTS: FCT (HW rel.3)

ETHLK, PPTT

Flexi SBTS: FCT (HW rel.3)

IKEP

Flexi SBTS: FCT (HW rel.3)

PPTT

Flexi SBTS: FCT (HW rel.3)

SFP

Flexi SBTS: FCT (HW rel.3)

CERTH

AirScale SBTS: ASIA; Flexi SBTS: FSM, FTIF

ETHLK

AirScale SBTS: ASIA; Flexi SBTS: FSM, FTIF

ETHLK

AirScale SBTS: ASIA; Flexi SBTS: FSM, FTIF;

ETHLK

Flexi SBTS: FCT (HW rel.3)

SFP

Flexi SBTS: FCT (HW rel.3)

PPTT

Flexi SBTS: FCT (HW rel.3)

PPTT

Flexi SBTS: FCT (HW rel.3)

PPTT

Flexi SBTS: FCT (HW rel.3)

PPTT

Flexi SBTS: FCT (HW rel.3)

SMOD

Flexi SBTS: FCT (HW rel.3)

P3SL; P3ML

Flexi SBTS: FCT (HW rel.3)

P3LP

Flexi SBTS: FCT (HW rel.3)

P3ML, P3SL

AirScale SBTS: ASIA; Flexi SBTS: FSM, FTIF

OAMMA, OAMMD

AirScale SBTS: ASIA; Flexi SBTS: FSM, FTIF

OAMMEP

Flexi SBTS: FCT (HW rel.3)

CERTH

Flexi SBTS: FCT (HW rel.3)

BFD

Flexi SBTS: FCT (HW rel.3)

BFD

Flexi SBTS: FCT (HW rel.3)

ETHLK

Flexi SBTS: FCT (HW rel.3)

TWAMP

Flexi SBTS: FCT (HW rel.3)

TWAMP

Flexi SBTS: FCT (HW rel.3)

CERTH

Flexi SBTS: FCT (HW rel.3)

CERTH

Flexi SBTS: FCT (HW rel.3)

P3ML

FCT

SYNCE-x

FCT

SYNCE-x

Flexi SBTS: FCT (HW rel.3)

IPADDRESSV6;IPIF_R

Flexi SBTS: FCT (HW rel.3)

IPSECC

Flexi SBTS: FCT (HW rel.3)

IPNO

AirScale SBTS: ASIA (HW rel.4); Flexi SBTS: FCT (HW rel.3)

SBTS

Flexi SBTS: FCT (HW rel.3)

IKEPROTGRP

Flexi SBTS: FCT (HW rel.3)

IKEP

Flexi SBTS: FCT (HW rel.3)

IKEP

Flexi SBTS: FCT (HW rel.3)

SECPOL

FR

FAN, FAN_GROUP

AirScale SBTS: ASIA; Flexi SBTS: FCT

AirScale SBTS: - ASIA, - ABIA Flexi SBTS: - FCT (HW rel.3) - FSP - FBB

Meaning

State

The temperature of a unit exceeds the threshold value.

Start / Cancel

A software update in the module or submodule has failed.

Start

The reference frequency that the BTS Start / Cancel master clock receives has changed by about 0.2 ppm or more (which equals the change magnitude of 204 DAC steps or more) during the measurement period as The connection to a module that belongs Start / Cancel compared to the BTS master clock to the BTS configuration has been lost. frequency. In case of SNMP radios, there is a The cause of the alarm can be: problem with the optical interface or an A failure is detected when the eNodeB internal fault, which results in a radio O&M presents available FSPs to 1. Thesystem reference frequency has changed reset. C-plane to map FSPs to becausesoftware of a faultininorder the transmission a cell. The FSPs related towhich the faulty network synchronization, in turn is operation cannot be takenfault intooruse. The caused by an equipment setting The initialization of control plane a part for reason for the failure might be an internal error. Note that if the network WCDMA RAT has failed. problem in the eNodeB O&Mlasts system. synchronization malfunction for a long time, the alarm is canceled when the BTS frequency reaches the faulty The FSP, FCT (HW rel.4), or ABIx reference synchronization. The alarm can synchronization failed. also be activatedhas if the faulty reference synchronization is corrected and there is, again, a difference of 0.2 ppm or more. The alarm isNBAP canceled whenever the A common (NodeB Application difference becomes less than 0.2 ppm. Part - interface between NodeB and

Start

Start

Start

Start / Cancel

RNC) link failure has occurred that is 2. The reference frequency fluctuates possibly caused by a transmission continuously because of a significant network problem. A dedicated NBAP (NodeBinApplication Start / Cancel amount of jitter or wander the Part interface between NodeB and transmission network. The alarm is RNC) link failure has occurred. continuously activated or canceled (however, the alarming state might predominate). There is always some jitter Start / Cancel An incompatible software has been or wander in the transmission network; detected. the limits are defined in ITU-T G.823/824/825. 3. If the BTS-integrated transport part receives the synchronization information through the 2.048 MHz synchronization input (external clock source), the alarm situation might be caused by a fault of that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid.

There is an attempt to download an unsupported SW version.

Start / Cancel

The SNTP time or GPS time cannot be fetched within the time limit.

Start / Cancel

The BTS cannot obtain a file from the file server (there is an error in either FTP open or FTP get): the file server is down, the file is missing, or the path is incorrect. A possible error in the DCN and Iub, or a The download is corrupted, or the user administration error (an invalid software is incompatible. username or password, or the user does not have access rights to the files) has occurred. The SW update to the BTS has failed. The error can be caused by a module reset during the SW update, a hardware problem in the module, or a corrupted flash file system. The SW update to the BTS has failed. The error can be caused by a module reset during the SW update, a hardware problem in the module, or a corrupted flash file system. There is a fault in the BTS main power supply. The BTS has received a battery backup alarm, and the BTS cells intelligent shutdown procedure has started. A module is blocked with the BTS Element Manager.

Start / Cancel

The purpose is to avoid fault indications that might be raised during the module The fault indicates that the user has maintenance task. blocked the cell using the BTS Element Manager. The fault is raised only when an LTE system module (FSM) is the master The BTS is blocked the BTS (FR) agent of the blockedwith radio module Element Manager. The purpose is to a or when an LTE system module shares avoid fault indications that an might be CPRI/Ir radio module with SCDMA raised a BTS task. systemduring module (dualmaintenance mode configuration). In other cases, that is, The fault informs the operator that the when a WCDMA system module is the BTS is trying to correct a fault situation master agent for the blocked shared by performing a recovery reset to the (WCDMA/LTE) fault 1931 DSP group, theradio FSP, module, the GNSS, the is raised. baseband card, the RAT, the site, the The unit or module has been tested BTS, or the BTS secondary core. In case during the BTS power-on self test of an RF module reset in RF chaining (POST), and a failure has been detected. configuration, the BTS also resets all RF modules that are further in the chain. # in fault name indicates what recovery level is performed for example "BTS secondary core autonomous reset as recovery action"

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start

Transient

Start

NBAP: PRIVATE MESSAGE Start / Cancel (Configuration Data) message from RNC with valid parameters for a cell was not received by BTS. A unit cannot be identified by its product code or by its physical device address (object ID).

Start

An unsupported unit has been detected Start in the System Module. This typically happens when a new unit version is installed while an older system module SW, which does not support the new unit The RF module carrier power Start / Cancel version, is in use. measurement has failed.

Unit RNW (Radio Network) configuration Start or reconfiguration failure. The fault is detected for DSP or CARRIER when it does not accept The BTS does not receive a response configuration, configuration failure or from the RNC to a cell block request. does not respond to configuration request.

Transient

Cell enabling (the setup of CPICH and Start / Cancel BCH) has failed. The reason might be a hardware or a bus problem, or a lack of DSP. There is not enough BTS baseband capacity to set up a cell.

Start / Cancel

The radio output power has dropped. There is a fault in the downlink transmission path.

Start / Cancel

At least one Local Cell Group (LCG) in Start / Cancel the BTS does not have enough resources for the HSUPA minimum capacity commissioned with the parameter "Number of HSUPA resource 133: Start / Cancel steps reserved for HSUPA users". EFaultId_RxAntennaSignalLevelTooLow If the LCG has two HSUPA schedulers, Al then the sum of the HSUPA Resource The RX signal level is less than -112dBm Steps that is statically allocated in both . 133: Start / Cancel System Modules is compared with the EFaultId_RxAntennaSignalLevelTooLow commissioned amount. 134: Al EFaultId_RxAntennaSignalLevelDifferenc The RX signal level is less than -112dBm eTooHighAl . The difference between the maximum and minimum power levels of all RX 134: antennas in the same cell and sector EFaultId_RxAntennaSignalLevelDifferenc exceeds the defined limit for a cell. eTooHighAl The difference between the maximum and minimum power levels of all RX antennas in the same cell and sector exceeds the defined limit for a cell.

Unsuccessful DSP configuration to the correct mode.

Start

If there are no DSP resources for Parallel Start / Cancel Interference Cancellation (PIC) configuration, the PIC configuration is rejected. Parallel Interference Cancellation (PIC) Start / Cancel configuration cannot be allocated to a DSP resource because the DSP is in use with some users. One particular DSP rejects a Dedicated Channel (DCH) setup repetitively.

Start

1.Cell setup is rejected because either all cells in the same Local Cell Group (LCG) having the same UTRA Absolute Radio Frequency Channel Number (UARFCN) are not mapped to the same Parallel There is not enough Common Control Interference Cancellation (PIC) pool, or Channel Processing Set (CCCH there is another cell in the same LCG Processing Set) licenses commissioned with the same UARFCN outside the PIC to the BTS. pool. The Physical Shared Channel Reconfiguration (PSCR) request foror 2.The PIC pool configuration (new setting upisnew HSPAif resources is updated) rejected either all LCELWs rejected because it is made on UARFCN an in the same LCG having same already existing resources (allocated in do not belong to the same PIC pool, or One of the Common Transport Channels DSP SW internal databases). an LCELW that does not belong to any (PCH, FACH, RACH) is released by PIC RNC.pool has UARFCN that is already assigned to any PIC pool from the same LCS of an LCELW. There are not enough baseband resources (or they are temporarily unavailable for HS-RACH (High Speed Cell_FACH UL) service) in LCG (Local Cell Group) for the commissioned "Min During HSDPA setup: number of HSUPA resource steps for HSRACH users HSDPA setup is rejected because (minNumOfHsRachResourcesStepsRes). Physical Shared Channel Reconfiguration message contains a The carrier aggregation group ID change Tcell value which belongs to a Tcell group is not acceptable. The carrier other than the existing cells in MAC-hs aggregation group ID is changed from a scheduler. Tcell is a parameter that non-zero value to another non-zero represents frame timing offset of a cell. It value. Only acceptable changes are nonTelecom SW for detects that connection can be used grouping schedulers to zero to zero value or zero to non-zero types TX carrier resources for one or cells ifofminimum baseband allocation value. LCR have both scheduler of CPRI and This shared HSDPA forOBSAI. baseband configuration is not supported. efficiency scheduler are used.

Start / Cancel

During runtime activation: Carrier aggregation functionality for local cell group is not available because cells from two different Tcell Groups are already set up in MAC-hs schedulers.

Start / Cancel

Start

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

A flash memory operation failure. If this Start fault continuously appears, the flash chip might be broken. A flash memory operation failure. If this Start fault continuously appears, the flash chip might be broken. Flexi SBTS: The synchronization between the FCM, and/or FCT and FSP is lost. AirScale SBTS: The operating system (OSE) goes into The synchronization between the FCT the error handler with a fatal status. This and ABIx is lost. might be caused of an out-of-memory situation. The antenna (RP3) link is down. The If only one FSP/ABIx in the BTS transmitter or receiver drops from generates this fault, there is a synchronization. malfunction in one of the FSP/ABIx submodules. The state of the external alarm line shows that generate an external notified. If all FSPs thisalarm fault,isthere is a malfunction in the FCT. The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start

Start

Start

Start / Cancel

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, severity, and polarity that indicate the fault.

The state of the external alarm line shows that an external alarm is notified.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, severity, and polarity that indicate the fault.

The state of the external alarm line shows that an external alarm is notified.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, The state of the external alarm line severity, and polarity that indicate the shows that an external alarm is notified. fault.

Start / Cancel

The user specifies, during commissioning, the alarm number, A software download to FSP, DSP, ABIx, severity, and polarity that indicate the or FR has failed. fault.

Start

The communication with an application has failed. It has not replied to the message that has been sent and/or resent to it.

Start / Cancel

The radio channel that has been Start / Cancel requested in the commissioning file is not supported by the detected BTS radio or MHA hardware because of an incorrect carrier bandwidth or incorrect center The baseband-bus-related configuration Start frequency. of has been rejected by the HW SW, DSP, or RF SW. The baseband bus synchronization towards has failed.

Start / Cancel

The reference clock monitoring has Start / Cancel detected a loss of signal in the reference received from the FT. The OCXO warm-up takes too long, and the OCXO does not become active within a period of eight minutes from power-on. The ambient temperature might also be too low, or it changes too fast. The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is less than or equal to the value of the parameter Min.OcxoControlValue.Alarm.Set The output signal of the OXCO is specified in BPF, or greater than or equal missing, and the FCM/FCT cannot to the value of the parameter deliver the 30.72 MHz System Clock Max.OcxoControlValue.Alarm.Set required by the other units. specified in BPF. A request to retrieve the public IP address information of the FCT (HW rel.3) from the FTM has failed, FCT (HW rel.4).

Start / Cancel

The Masthead Amplifier (MHA) does not work properly. However, the system cannot determine the impact on the RX signal level.

Start / Cancel

The Masthead Amplifier (MHA) does not work properly. Because of the low current drawn by the device, it is assumed that it does not provide gain in the RX signal path, and therefore, the received RF The Radio module or filter has detected signal level is decreased. over-current on the antenna line. The antenna line might be damaged (shortcircuited), or some antenna line device is causing overload. All antenna line The VSWR value exceeds the level that devices powered by the antenna line are is defined as a criterion for VSWR major out of order. event. The impedance of the antenna line does not match the impedance that the radio module requires. The VSWR value exceeds the level defined as criterion for VSWR Minor event. The impedance of the antenna line does not match the impedance required by the Radio Module. The Radio Module has detected a malfunction of an internal LNA unit.

Start

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

The Radio Module is unable to tune to a Start / Cancel required sub-band properly (tuning failure), or another major failure has been detected by the Radio Module (unit faulty).

The radio module has detected an internal filter failure.

Start / Cancel

1845: TILT is not configured.

Start / Cancel

Others: Antenna tilting is not possible or might not function correctly. 1845: TILT is not configured.

Start / Cancel

Others: Antenna tilting is not possible or might not function correctly. 1845: TILT is not configured.

Start / Cancel

Others: Antenna tilting is not possible or might not function correctly. 1845: TILT is not configured.

Start / Cancel

Others: Antenna tilting is not possible or might not function correctly. 1845: TILT is not configured.

Start / Cancel

Others: Antenna tilting is not possible or might not function correctly. A hardware failure has been reported by ALD (RET, MHA).

Start / Cancel

The unit is in download mode state. This Start / Cancel fault is returned when an unsupported procedure occurs in download mode. A corrupted SW file in the FLASH is detected. The unit cannot perform a complete start-up.

Start / Cancel

The synchronization setup between secondary core (working as sync slave) and primary core (working as sync master) has failed during BTS startup.

Start / Cancel

During BTS startup, BTS recomissioning, Start / Cancel or BTS resources reassignment due to a failure, the BTSOAM has detected that there are not enough of the following: a. radio resources A fault in the Masthead Amplifier (MHA) Start / Cancel b. FSP resources is detected. MHA functionality is c. cables between the system module degraded. The real impact cannot be and the radio module, or cables between determined. the extension baseband module (FBBx/ABIx) and the radio module, to setup the cell according to the configuration requested in the site configuration file d. PRACH resources

During BTS startup, BTS recomissioning, or BTS resources reassignment due to

A fault in the Masthead Amplifier (MHA) has been detected. The MHA is not working.

Start / Cancel

The device is not working properly, the configuration is not valid, or a given parameter is incorrect.

Start / Cancel

The device is not working properly, the configuration is not valid, or a given parameter is incorrect.

Start / Cancel

The device is not working properly, the configuration is not valid, or a given parameter is incorrect.

Start / Cancel

The device is not working properly, the configuration is not valid, or a given parameter is incorrect.

Start / Cancel

The antenna line device is not properly configured.

Start / Cancel

The antenna line device set-up fails, for example, due to protocol error or interAn autonomous internal delay operability problem. measurement has failed. The internal delay cannot be measured for a cell for any of the RAKE receivers in a certain baseband unit. 1. The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver or the SyncHub master.

Transient

Start / Cancel

The reference clock monitoring has Start / Cancel 2. (TDD only) The PPS signal from the detected a signal loss of 2.048 MHz SyncHub master is unusable because its received from an external reference reported phase error is too large. source connected to the Sync In interface of the System Module. The RF module configuration has failed Start because of a HW or SW fault.

A critical configuration file is missing from Start the RF Module.

The RF Module SW has detected that a non-critical configuration file is missing.

Start

The System Module clock reference differs from the RF Module clock.

Start / Cancel

The baseband bus between the System Module and RF Module is out of synchronization.

Start / Cancel

The RF Module baseband bus was configured incorrectly.

Start / Cancel

There is an error in the baseband or optical bus.

Start / Cancel

The TX path of the RF module cannot be Start / Cancel used.

The TX output power adjustment has failed.

Start / Cancel

The RF Module filter has a measured TX Start power that is too low.

The RX RF synthesizer of the RF module Start is not locked. For SNMP interface, the received power is low for the RRH. The RF module is out of order because of a software or hardware fault. For CPRI-A interface, the RX path in the FR module is faulty.

Start / Cancel

The power supply supervision has detected an overvoltage, undervoltage, or overcurrent in the RF module.

Start / Cancel

The feedback signal to predistortion is too weak or missing. The TX performance is degraded.

Start / Cancel

The TX signal adjustment fails.

Start / Cancel

Out of order unit status: The radio unit is too cold for proper operation. Heating of the module is ongoing.

Start / Cancel

Working unit status: The radio unit is The permanent memory in the RF Start below its normal operating temperature module is corrupted, the module product but is still capable of transmitting. code or serial number is missing, or the Problems might occur. module product code is unknown. The RF Module SW has detected conflicting or corrupted configuration data.

Start / Cancel

A power-on self-test of the RF module has failed at start-up.

Start

The RF module has lost lock to the incoming clock.

Start / Cancel

The highest temperature exceeds the power decrease limit in the RF module.

Start / Cancel

The FPGA software update in the RF module has failed.

Start

This fault is detected in a radio-sharing Start / Cancel configuration where a WCDMA FSM is the master system module, and an LTE FSM/ASIA plays the role of the slave module. This fault means that the FR is The RF module cannot identify the fan Start / Cancel blocked. When an LTE FSM/ASIA plays vendor, or the fan is not installed. the role of the master, or an LTE system module shares a CPRI/Ir radio module with an WCDMA system module (dual Fans inconfiguration), the RF module arethe notFR running. Start / Cancel mode and is blocked, fault 48:EFaultId_UnitBlockedAl is detected and not 1931. Fans in the RF module are rotating slower than requested.

Start / Cancel

The validated RF sensor temperature is greater than or equal to the pre-defined value in the unit property file.

Start / Cancel

The validated temperature of any PA or Pipe sensor in the RF module is greater than or equal to the pre-defined value in the unit property file.

Start / Cancel

Increased bit error rate has been Start / Cancel detected on the optical link to the radio module, which results in sporadic LCV errors in downlink baseband processing. An abnormally high bit error rate has Start been detected on the optical link to the radio module, which results in permanent baseband processing failure. I/Q data stream cannot be successfully processed The Tx in the RF module has been Start by FRM. This is caused by the burst of switched off to protect the radio module consecutive LCV errors. hardware, which might be damaged because of high-reflection (VSWR) conditions. The FR module has detected permanent Start / Cancel RP3 routing collisions in either downlink (TX), or uplink (RX) transmission directions. Input voltage to the radio unit is outside of the expected range, but the radio unit power supply can still provide output voltages adequate for operation.

Start / Cancel

The optical interface is not working Start / Cancel properly. The received power aggravation is high. 1. The configuration of the External Alarm Start and Control (EAC) lines of the Radio Module has failed because of a hardware or software fault. OR Hardware protection logic in the radio Start 2. Number of commissioned EAC lines of unit has disabled the TX path to protect the Radio Module is incorrect, i.e. higher the radio unit because of an overdrive than number of EAC lines supported by condition detected in the power amplifier the detected Radio Module. circuitry. The radio unit has detected a failure on Start / Cancel its optical connection to the system module or an upstream radio unit (chaining case). Hardware protection logic in the radio Start / Cancel unit has activated overdrive protection on the TX path to avoid damage to hardware. Overdrive protection keeps the TX path operational but with degraded The SFP on the radio unit is either faulty Start / Cancel performance. or not supported.

The communication radio module with Start / Cancel external Receive Diversity Expansion Module (RDEM) is lost. The cable to the external RDEM module may be broken or disconnected, and external module may The fault is reported in radio modules Start / Cancel have failed. that consist of two separate hardware units connected by an optical cable. The near end Radio Module sub-unit cannot communicate with the far end sub-unit, The Radio Module is reporting that the Start / Cancel possibly due to failed CPRI link between access door protecting the maintenance the two sub-units, or a failed far end subdata port is open. The maintenance port unit. allows local control of the Radio Module. The fault is reported by complex radio modules with multiple physical units where functionality is distributed. An incompatibility has been found between board revisions. The fault is reported by complex radio modules with multiple physical units where functionality is distributed. An incompatibility has been found with the identification method. The received optical signal on the link port is unexpectedly low from upper hop (toward the system module), though communication is still possible. There is a poor CPRI link connection, The received optical signal on the link bad CPRI cable, or failing CPRI port is unexpectedly low from the next transceiver at the previous radio module hop (further from system module), though or system module connected to the cable communication is still possible. reported as the fault source. There is a poor CPRI link connection, The detected Passive InterModulation bad CPRI cable, or failing CPRI performance measurement has transceiver at the next radio module exceeded threshold Level 2. connected to the cable reported as fault source. A PIM cancellation fault is an indication A small form-factor pluggable (SFP) of non-linearity in the antenna system. malfunction has occurred (fault 2000), or This may be caused by damage to the the SFP module is not physically present, RF feeders, the antenna assembly, or that is, there is no electrical connection caused from external structures. Damage (fault 2001). The SFP is a part of the fiber A small pluggable (SFP) may be form-factor caused by water intrusion, cable package. malfunction has cables, occurred (fault 2000), or crimped coaxial loose the SFP module is notdamage, physically connectors, lightning or present, that is, there is notoelectrical connection physical damage the antenna (fault 2001). The SFP is a part of the fiber assembly. The incoming optical signal to the Small cable package. Form-Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detached.

Start

Start

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

The fiber cable is experiencing Start / Cancel The connection between the System interference; data transmission is faulty. Module and the RF Module is broken, or the connection between the Baseband A physical connection failure between the Module (for example, FBBC) and the RF optical interface and the summing Module is broken. function has occurred. The reason of the fault might be a lowquality or polluted SFP, or a low-quality optical cable used to connect radio module to system module and/or extension baseband module.

The RP3 or Ethernet buffering is not Start / Cancel working, and the buffer becomes full. The optical device is malfunctioning. The fault might be generated because of synchronization problems or incorrect The RP3 or Ethernet buffering is not Start / Cancel initialization. working, and the buffer becomes full. The optical device is malfunctioning. The fault might be generated because of synchronization problems or incorrect The control message traffic between the Start / Cancel initialization. modules is malfunctioning.

The master frame in the received Start / Cancel baseband bus frame is not in the correct place related to the internally-generated master frame pulse. Either the frame has been set into the wrong place (PI delay) A decoding error has been detected in Start / Cancel or the data itself is in the wrong place. the baseband internal link. The data packet is lost, or the content is corrupted. This situation also occurs when the links There is a baseband bus address Start / Cancel are not synchronized with each other. mismatch in the summing. There are two possible causes: 1. A configuration error (two different A new RP1 Frame Clock Burst (FCB) has Start baseband units functioning) - after an been received from the RP3-01 interface acknowledgement, the fault returns. while processing the previous FCB. 2. Data corruption on the bus - appears The buffer underflow or Start / Cancel onceclock-crossing when an unsynchronized data is overflow in the RX block, and the sent by the baseband. received data, might be invalid. The fault is an indication that either there is too large of a clock drift between the The software update to the BTS has Start received signal and the internal clock, or failed, or the BTS software is corrupted. the RX rate setting is wrong. Interrupt is generated if a message does Start / Cancel not get routed. This is considered normal when DSPs are starting up, and RP3 sync is done. Summing checks the headers of the Start / Cancel messages to be summed. If the header is not an allowed type, summing is not performed and an empty message is sent instead. The transmitter has detected an RP3 Start / Cancel message from a summing coincident with a transmission rule.

The transmitter has detected more data Start / Cancel coming from a summing than the current link rate can support. The enumeration algorithm has detected Start a permanent failure that prevents sRIO (serial RapidIO) system maintenance. Congestion avoidance hardware of the Start sRIO (serial RapidIO) switches has been triggered. BMU (Board Management Unit) product data EEPROM of an extension board (FSP) cannot be read out during a connect event.

Start

It has been detected that the host link, which is used for the sRIO (serial RapidIO) system maintenance, is going down.

Start

The error rate is too high in the BTS internal bus.

Start

O&M software is unable to initialize TRX into operational state.

Start / Cancel

TRX control plane connection has been lost.

Start / Cancel

There is mismatch between BSC and BTS configuration. The reason of the fault could be one or more of the below: 1. Number of sectors configured in BSC The difference of received signal strength does not match with the number of between the main and diversity paths of commissioned local cells at BTS. logical TRX at DSP is exceeding the 2. Number of TRXs configured in BSC threshold defined by BSC. does not match with the number of If the RSSI difference between main and The txPowerPooling feature is enabled in commissioned channel groups under the diversity RX is a negative value, then the Site localConfiguration cells at BTS. File(SCF) and Tx antenna hosting the RX main path is power pooling feature license is not 3. Number of paths in the TRXs reported as faulty. Otherwise, the enabled from BSC.does not match with configured in BSC antenna hosting the RX diversity path is the number ofplane commissioned channels in Management reported as faulty. connection (OMU the channel groups under the Signaling) to BSC could not belocal cells at BTS. established, or it is broken.

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

An invalid configuration is received, or timeout for configuration procedure from BSC.

Start / Cancel

The BSC does not respond to BTS initialization procedure.

Start / Cancel

A TRX is added to an antenna hopping sector without locking the sector.

Start / Cancel

There is a mismatch between the commissioned and configured BCF Identifier.

Start / Cancel

The Passive InterModulation level has exceeded the PIM cancellation algorithm's ability to effectively remove PIM from Receive (Rx) path.

Start / Cancel

The actPimCanellation feature flag is set This Passive Inter-Modulation (PIM) to true at a radio which does not support cancellation fault is an indication that the the PIM Cancellation feature. PIM Canceller is unable to remove PIM as an indicated comparison of PIM power Too many cells are commissioned to the before cancellation, to PIM power after BTS. cancellation. The presence of PIM is an indication of non-linearity in the antenna system. This may be caused by damage to thefault RF notifies feeders,the theoperator antennathat assembly, This the or caused from external structures. BTS must be reset to solve a problem Damage may be caused by that has been discovered bywater the BTS intrusion, crimped coaxial cables, loose O&M system, and that BTS O&M will not connectors, trigger an autonomous reset on its own. A TX pathdamage, failure has caused the lightning or physical damage to multiple-input multiple-output (MIMO) or the antenna assembly. 1. The BTS has detected a beamforming functionality to be not commissioned (configured in SCF) operational or degraded in the cell that is extension baseband related to the faulty TX. This fault is not 1. The power level thatFBBC) is defined in thenot module (for example, that was reported in super cell cases. radio network (RNW) part of the sitethe detected during BTS startup. Thus, configuration (SCF) is not BTS must be file reset to take thesupported module by HW. intothe use. 2. Having different power levels for The BTS has detected a communication subcells of combined supercells, as 2. Obsolete problem with the GPS receiver. defined in the RNW part of the SCF file, is not supported by HW. 3. Obsolete The fault is ignored until the GPS receiver has reached the commissioned The connection to the FSP or DSP has 4. Obsolete state. been lost, or the sub-module reports an error 5. Thesituation. BTS O&M system detected that the speed of transmission on a baseband link has changed because of a hardware problem (for example, the SFP has been changed to an SFP that does not support the configured speed), and a BTS reset might be needed to solve the problem.

Start / Cancel

Note: The affected LCR is reported as the fault source in this case. 6. In BTS runtime, the BTS O&M system has detected resources necessary to cell

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

The internal maximum transfer unit (MTU) configuration has failed on the FSP or FBB.

Start

This alarm is used to inform the operator Start / Cancel that another BTS fault (the original fault) is toggling. The alarm that is related to the original The commissioning file download has not Start fault is suppressed and the new alarm, been started from the BTS Element which is related to fault 4026: Manager or from NetAct during autoEFaultId_TogglingAlFault, is raised. configuration. Either the autoconfiguration might not be enabled in the The commissioning corrupted, or Start / Cancel Toggling alarms thatfile areisrelated to the NetAct or the commissioning file is not an incorrect has beenuntil detected original faultsSCF are file suppressed the found. during startupisas follows: togglingBTS condition cleared. 1. Commissioning The ofhas thisdata: BTS The fault is the the same Start The severity BTSOAM noticed that commissioning filethe is corrupted, or a as the severity of original connected radio unit already has another parameter hasfault. a missing or incorrect toggling BTS radio master defined apart from the value. System Module, which should be the radio master for the connected radio unit. The Radio Module has detected that the Start / Cancel 2. RNW data: "RNW has wrong format", requested frequency does not fit thehas "RNW could not be parsed", "RNW capabilities offered by the Radio wrong schema", "Validation failedModule. due to incompatible data", "no RNW cell managedObject is created", or an invalid Start The cell configuration is not officially combination of the cell parameters supported. Too many cells are assigned administrativeState and to the Tx group of the radio module. preventCellActivation. An alarm message has been received from the antenna line. The antenna line is faulty.

Start / Cancel

An alarm message has been received from the antenna line device. The antenna line operation is degraded.

Start / Cancel

An SW download to an antenna line Start / Cancel device has failed because of an incorrect checksum or file format. An SW download to an antenna line Start / Cancel device has failed because of an incorrect checksum or file format. Problem is detected when response is Start not received or response is received with unsuccessful status for SRIO multicast configuration related messages. SRIO = Serial RapidIO (highperformance interconnect technology between DSPs).

Beam-forming calibration configuration has failed.

Start

OBSAI interface:

Start

The Radio Module has detected an overcurrent condition in the RS485 IUANT port. - The mutual length difference of the parallel RP3-01/CPRI links toward one Some antenna line device is causing radio module is too large (more than 60 overload. Antenna line devices powered meters in OBSAI RRU, and 146 meters by the RS485 IUANT are out of order in CPRI RRU). The main link is A fan delivered by anofunknown vendor is because of the lack DC power. considered as a reference, and the detected (system module hardware secondary link is compared to the main rel.2), or the fan speed is too low for link. successful detection. Another detection CPRI/Ir interface: attempt occurs after the fan test timer A long distance between - RF sharing has(high beenlatency) disabled with expires (system module hardware rel.3). Over-current the FSMWCDMA and case: antenna hasthe been master because mutual detected, but the between Distributed feature length difference theSite cables of This fault isModule reported fordetected both operational The Radio has overhas not beensystem enabled (actDistributedSite the WCDMA module-shared RF, and non-operational fansSome in hardware current onFor theFHCC ALD port. antenna = False). modules, this fault and the LTE system module-shared RF is The device temperature of the FSP/ABIx board detection phase only. line is causing overload. means that there is a long distance too large. has exceeded the criticalimplementation, threshold value. Depending hardware between theonFSM and the customer's antenna line devices powered by the device. The additional info in the alarm about RS485 IUANT, or powered by the difference in length should be delivered antenna line, fans are out order. One more areofnot running in theoralarm only when LTE is radio although the temperature (indicated by master. Undercurrent case:than the value of the Tcontrol) is higher T.start parameterconsists in the BTS The information of: Property The Radio Module has detected File -4082: The(BPF). number of physical port on the undercurrent on the ALD port. There is a system module where primary link starts. problem with the ALD port connection. -The Thesource number of has physical portthe on the unit reached Depending on hardware implementation, system module where secondary too maximum number of reset retries, that is, antenna line devices powered by the long/too short link starts. the source unit cannot successfully RS485 IUANT, or powered by the finish 4082: -start-up The difference in lengths with the update. antenna after line, the are SW out of order. information if the secondary link is too The source has reached the short too unit long. If BTSorO&M has detected that the BTS maximum number of resetinretries, that is, -can Thestart difference delays with theinpreviously-active SW the source unit cannot successfully finish nanoseconds. 4082: version, the BTS O&M processed start-up after the SW update. consistent fallback and the previouslyThe source unit has theall HW active SW version is reached running in If BTS O&M has detected that the BTS maximum of reset retries, that is, units in thenumber BTS. The BTS is up and can start with the previously-active SW the source unit cannot successfully finish running. The file system operations like file version, the BTSaccess O&M processed start-up after the SW update. system mounting file the opening have consistent fallbackorand previouslyOtherwise, the previously-active SW failed. active SW version is running in all HW If BTS O&M detected BTS version is nothas running in allthat HWthe units in units in the BTS. The BTS is up and can start with previously-active the BTS, and the BTS is not up andSW running. The Flexi(recovery Radio has detected version, the BTSModule O&M processed running SW update is still low downlink carrier input from the consistent fallback andpower the previouslysupported). Otherwise, the previously-active SW System Module. active SW version is running in all HW version is not running in all HW units in units the for BTS. The BTS iscan up and Fault in 4082 FSP fallback be the BTS, and the BTS is not up and running. canceled due to SW upgrade on FSP running (recovery SW update is still only. supported). Otherwise, the previously-active SW version is notan running in alltoHW units in In this case, FSP reset activate the Fault 4082 for FSP fallback can be the andofthe BTS not up the andfault. newBTS, version SW mayis cancel canceled due to SW upgrade on FSP running (recovery SW update is still only. supported). The state of the fault is start/cancel for FSP SW fallback only. In this case, an FSP reset to activate the Fault 4082 for FSP fallback can be new version of SW may cancel the fault. canceled due to SW upgrade on FSP only. 4083:

Start / Cancel

Start / Cancel

Start

Start / Cancel

Start / Cancel

Start

Start

Start

Start

Start / Cancel

The BTS has detected that an RF Start module connected to the system module is affected by a power cycle failure and other additional actions performed by the BTS during reset. Therefore, the BTS The summing service default Start reset lasts longer. This fault notifies the configuration has failed. operator that the BTS reset will be extended. Power feeding for the given radio module Start / Cancel has been remotely switched off using BTS Element Manager. The master system module has lost optical or sync connection to the peer system module.

Start / Cancel

Synchronization is lost when the system module is working as a synchronization slave system module. This usually indicates that a synchronization master system module has been reset, or that The fault indicates poor GPS antenna there is a problem with the optical cable installation. between the master system module and the slave system module.

Start

The GPS receiver is running a site or self-survey.

Start / Cancel

There is no accurate position stored in the EEPROM.

Start / Cancel

The receiver is used in stored position but has been moved to a new position after that.

Start / Cancel

Start / Cancel

The GPS receiver has detected that one Start / Cancel or more EEPROM segments were corrupted at reset and had to be set to their factory default settings. The feeding voltage is disabled for the selected antenna line.

Start / Cancel

The HDLC link has been disabled for the Start / Cancel reporting Antenna Line or IUANT port.

SW file validation against its signature has failed.

Start / Cancel

Phase synchronization has been Start / Cancel commissioned at the btsSyncMode, but the phase reference clock is unavailable during a waiting period within the start-up procedure. The synchronization source of the BTS is Start / Cancel not available when it works as synchronization slave during start-up. Gathering logs from the unit has failed, and one or more log files from a particular RF module is not available in the BTS snapshot.

Start

The shared OptIF mode cannot be read from or changed in the FBBC card.

Start

A failure has occurred in the connection Start / Cancel to the configured Real-time Performance Management (RTPM) entity, for example, the Traffica Network Element Server (TNES). The RROM TRS IP configuring or Start / Cancel reconfiguring has failed.

The external GPS or GNSS receiver module has lost satellite visibility and is currently operating in holdover mode.

Start / Cancel

The radio master is either missing at start-up or is lost at run-time.

Start / Cancel

The radio slave waits for a user-defined amount of time for the radio master An antenna line or antenna line device is Start / Cancel to become available again before taking not properly configured. a temporary radio master role. The antenna line setup and device scan fails because of exceeded time limit or An alarm due to the fault is reported too many ALDs detected from the ALD The module indicated error upon Start whenradio the radio master is notan available port. execution of remote electrical (RET)after the user-defined amount tilt of time, The radio module reports the fault when related operation. and thelogical slave takes a temporary radio the antenna line starts. master role. The radio slave system module cannot use the shared radio because the radio master system module has not provided a reference clock to the shared radio.

Start / Cancel

Fiber Delay and Antenna Round Trip Delay exceeds the supported capability of the BTS.

Start

The cell state audit detected that the cell Start / Cancel was unintentionally deactivated without warning. The symptom data is automatically collected. SRIO link failure has been detected by the NE.

Start / Cancel

The inter-BTS SRIO link cannot be Start / Cancel established because the domain ID is not unique. There has been a failure to validate the software release signature for the software release that has just been requested to be downloaded to the BTS system module. This is because the There has been a failure to validate the information of either the Hash Container hash of the questioned SW files for FCT file or the Hash Container Signature file except of the Hash Container file or the is not present in the downloaded Hash Container Signature file in the TargetBD.xml, or the verification of the software release that has just been An unsigned software has been software signature filesrelease has failed. requested to be downloaded to the BTS downloaded to a BTS system module system module. This is because the hash that is currently running a software value of the questioned SW file is release that implements software missing, or the BTSOM fails to verify the signature checking. There a failureSW to validate the hash ofhas thebeen questioned file. software signature for the software release that has been requested to be downloaded to the BTS system module because there is no software signature The MHA was unexpectedly set to for the release, and only signed software bypass mode. The fault might be the can be installed. result of a conflict in MHA management for a device that can be managed from more than one BTS at the same time. FR functions that are not critical for cell setup are not supported or are not configured correctly. The reason for this might be an incompatible RFSW version.

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start

The Centralized Radio Access Network Start / Cancel (CRAN) configuration and the exchanged information between the connected BTSs show conflicts. CRAN functionality between the alarming BTSs cannot be The connection between two BTSs in the Start / Cancel established. Centralized Radio Access Network (CRAN) cluster is not detected or is lost.

RFM product authorization has failed Start / Cancel because of missing RFM properties. RFM is not supported by the current BTS software release, and the BTS did not find relevant hardware properties for the The detected hardware does not support Start RF module on FSM. The BTS failed to the SCF configuration. retrieve the corresponding RFM plug-in module from the Network Management System as well. Not enough licenses are available in Start / Cancel Centralized SW License Server. SBTS is limited with HSDPA users. Not enough licenses are available in Start / Cancel Centralized SW License Server. SBTS is limited with HSUPA users. Not enough licenses is available in the Centralized SW License Server. The number of LTE users is not reduced but calls from excess users will be rejected except for handover and emergency The SBTS IP traffic of the user is calls. throttled because of a missing license.

Start / Cancel

Connection to NTP (Network Time Protocol) server is lost.

Start / Cancel

ToP (Timing over Packet) signal is unavailable or unusable as reference clock source.

Start / Cancel

Synchronous Ethernet is unavailable or unusable as reference clock source.

Start / Cancel

PDH is unavailable or unusable as reference clock source.

Start / Cancel

Start / Cancel

The cable used between the system Start module and the radio module exceeds the maximum supported length for micro DTX (the maximum supported link delay is 80 us; if the radio module is directly The configuration of the inter-BTS carrier Start / Cancel connected to the system module or the aggregation in the SCF of own BTS and extension baseband module, the longest peer BTSs cannot be supported with the supported cable length is approximately detected HW. 16 km). The BTS power saving (that is, the micro DTX functionality) can no longer be provided.

The micro DTX configuration in a radio module has failed.

Start / Cancel

The RP30-1 connection between the system module and the radio module, or between an extension baseband module (FBBx/ABIx) and the radio module, is not stable at 6 Gbps. The RP30-1 connection between the system module and radio module, or between the extension baseband module (FBBx) and the radio module, is not stable at 3 Gbps. The fault may be reported in FSMx only due to two root causes: - The optical cable used to connect BTSs working in the same Centralized Radio Access Network (CRAN) cluster The BTS has detected that the GNSS exceeds the maximum supported length receiver does not support the operatorfor CRAN. selected manual location entry. - The optical cable used to connect the BTSs working in the same CRAN cluster Free memory on the radio module is is limited. not connected to the third port on the FBBC cards.

Start / Cancel

The radio module has no free memory.

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

The Measured Received Total Wideband Start / Cancel Power (RTWP) is below the threshold.

Serial console is activated in the BTS.

Start

DSP U-plane computing environment startup has failed.

Start

DSP U-plane computing environment covers U-plane applications and real-time The LTE-LTE RF Sharing configuration Start / Cancel platform services on DSP cores and and the exchanged information between MCU cores. the two LTE BTSs show conflicts. The BTS enters capacity limited mode due to missing licenses. Calls from excess users will be rejected except for handover and emergency calls.

Start / Cancel

Previously downloaded plan[Id] was overwritten by a new plan[Id].

Start / Cancel

An FSP sub-unit is unavailable (lost).

Start

The optical interface is not operating at the maximum speed. Not all cell configurations are supported.

Start

Not enough licenses are available in the Start / Cancel Centralized SW License Server. Parameter BTSSCW/numberOfR99ChannelElement is to be reduced internally. Connection to a secondary unit that Start / Cancel belongs to the BTS Dual Core or FSMF + FSMF configuration has been lost. Power feeding for the given Radio Module has been switched off by the user from the front panel of the PDU.

Start / Cancel

The Ethernet connection between the primary and secondary system module does not work.

Start

LTE BTS is connected to more than one peer system modules, but one of the peer system modules does not support multiple radio sharing.

Start

The shared radio module connected to Start the BTS is using the same IP addresses as other shared radio module connected to the same BTS. The peer system module connected to the BTS is using the same IP addresses as other peer system module connected to the same BTS.

Start

A virtual node (software container) within Start / Cancel the BTS has stopped working or failed to start. The symptom data is automatically collected when possible. Frequency overlapping when carriers Start / Cancel from different cells are configured on the same antenna port.

Positioning service offered by OTDOA (Observed Time Difference Of Arrival) feature is unusable. PRS (Positioning Reference Signal) transmission required for feature OTDOA is disabled. BTS has lost connection to the BTS The reason of the failure may be either of Mediator. the following: BTS Mediator is a unit responsible for 1. The BTS falls back (that is, the BTS is BTS connection to the Network currently synchronized to a sync input Management System (e.g. NetAct). The source unit hasfor requested source not allowed OTDOA SW fallback because of a critical problem that operation). occurred during RAT start-up after the RAT SW update. 2. If BTS is working in holdover mode, If BTS O&M has detected the BTS the estimated phase error that exceeds The Radio module configuration hasthe can start with the previously-active SW otdoaPhaseErrorThreshold of the last failed because the Radio module does version - BTS O&M processed consistent sync input source allowed for OTDOA not support Reduced LTE Guard Band fallback and: operation. functionalities. 1. The previously-active SW version is The cellsinare disabled running all HW unitsafter in thea BTS. Scenario A: The "Reduced LTE Guard preconfigured time period due to the 2. The BTS is up and running. Band" is activated, but the referenced intelligent Otherwise:shutdown procedure. Radio module does not support Reduced The fault is also reportedSW when the BTS 1. The previously-active version is LTE Guard Band function. power supply is available again, but not not running in all HW units in the BTS. The radio module remains disabled all cellsBTS are enabled yet. all 2. The is OAM not upcould andWhen running because BTS assign IP Scenario B: The "Reducednot LTE Guard previously shutupdate down cells are enabled (recovery SW is still supported). address the radioand module. Band" is to activated, Radio module again, the alarm due to this fault is supports Reduced LTE Guard Band cleared. function, the configured frequency The fault but indicates that the user has offset exceeds the RF module blocked one or more GSM TRXcapability of the for Band". cell"Reduced using the LTE BTS Guard Element Manager.

Start / Cancel

Start / Cancel

Start

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

During Cell start-up, the RF module An incompatibility internal database of Start detects that criticalinfault "Configuration BTS software has been detected. and RF module mismatch for Reduced LTE Guard Band" and could not be OnAir. This fault indicates that the absolute value of an estimated phase error of a BTS which is in holdover has increased more than limit set by BSC.

Start / Cancel

The fault indicates that the one or more Start / Cancel TRXes in the sector are not on-air due to the unavailability of System Information from BSC. The Radio Module is not able to configure the commissioned front end gain.

Start / Cancel

A neighbor relation, which is detected by Transient a UE through measurements due to activated ANR features, could not be stored because the maximum number of neighbor relations (LNRELX instances) per cell is already reached. Neighbor relation information needs to be cleaned up manually by the operator through the plan file.

A neighbor relation, which is detected by a UE through measurements due to activated ANR features, is created, but due to the 3GPP limits that max 32 cells can be configured per frequency object, The maximum length of SIB15 or the O&M configured maximum number information depends, for example, on the of e1xCSFB target cells per frequency, it cell bandwidth, configured SIB (System is not provided for measurement by the Information Block) coding rate, and MFBI UEs. (Multiple Frequency Band Indicator) Some problems in TX or RX path have feature activation. The warning is caused beam-forming calibration to fail. reported if one or more SAIs (Service The path means all units between the Area Identities) are omitted by BTS in signaling processor (DSP) and the order not to exceed the maximum length. antenna line that processes the data An overload situation has been detected transmitted (TX) or received (RX) by the by the scheduler on the user plane. BTS. Recovery actions are initiated to decrease the load level.

Transient

The configured PHICH transmission power boost cannot be applied either partly or entirely because of a lack of remaining power after considering (boosted) cell-specific DL RS power, The received interference power (RIP) (boosted) PCFICH power, and minimum value per physical resource block (PRB) reserved power for PDCCH. of the cell for UL subframes exceeds the predefined threshold for at least the operator-configured parameter The Received Interference Power (RIP) alarmThresholdCrossingTime. value per Physical Resource Block (PRB) of the cell for UpPTS symbols exceeds the predefined threshold for at least the operator-configured parameter An overload situation has been detected alarmThresholdCrossingTime. by the scheduler on the user plane. Recovery actions are initiated to decrease the load level.

Transient

Transient

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

An overload situation has been detected Start / Cancel by the scheduler on the user plane. Recovery actions are initiated to decrease the load level. In GTP-U supervision, a network element Start / Cancel did not respond to the GTP-U: Echo Request message within the allotted time. The transport path (SCTP) for connection Start / Cancel to the MME is broken. This might be because of an unplugged cable to the MME. There is no transport path available to continue operation on the The transport path (SCTP) for connection Start / Cancel faulty connection with the MME. to an adjacent BTS is broken. This might be because of an unplugged cable to the adjacent BTS. There is no transport path available to continue operation on the faulty connection with the adjacent BTS.

One of the transport paths (SCTP) in SCTP connection to the MME has failed. This is only applicable when SCTP multihoming is supported. An alternate transport path is available to continue The transport path (SCTP) for connection operation. to MME has been broken. The reason for this can be an unplugged cable to MME. No transport path is available to pursue operation on the faulty connection with One of the transport paths (SCTP) in the MME. SCTP connection to MME (which provides MBMS service) has failed. This is only applicable when SCTP multihoming is supported. An alternate There was a problem with a radio transport path is available to pursue network configuration at the BTS startup operation. or at the activation of the delta configuration related to a problem with the data A BTS raises this fault if it experiences a reading or inconsistent configuration. problem in the internal configuration data distribution (cell setup) to the CPlane and U-Plane SW components. The root cause of the fault might be an The BTS raises this fault if it experiences incorrect cell configuration in the site a problem in the internal configuration configuration file (scf). data distribution (cell setup) to C-Plane and U-Plane SW components.

Start / Cancel

A failure has occurred in the trace connection between the BTS and the BTSMED, or a third-party tool.

Start / Cancel

There has been an opening, reading, or file content problem with a BTS vendorspecific file at BTS startup.

Start

The fault is also detected when a vendorA failure has occurred during activation or specific file is missing. deactivation of a trace session. This failure case is applicable to subscriber trace, cell trace, interface trace session, or PCMD (Per Call Measurement Data) The BTS has encountered a few possibly report. misconfigured PLMNs, which cannot be used by the BTS for accepting calls from In case of subscriber trace, the following new UEs, which select those PLMNs. are the possible reasons: This indicates thatfeature the maximum - Thealarm Subscriber Trace is not The PLMNs that are considered number enabled of in LNADJ, the BTS.LNADJL, or both misconfigured by the BTS are: LNADJ LNADJL hastrace been - The IDand used for the objects subscriber - Those currently configured at the BTS exceeded the BTS, andfor that the new session is in already in use another for one or more cells where each cell is object has not been stored. active subscriber trace session. This alarm indicates a WCDMA of a specific RAT typethat "Wideband Lte" or -neighbor The number of subscriber traceby a UE cell, IoT". which is reported "Narrowband sessions in the BTS has reached the measurements, -through Those ANR-specific served by more than one MMEs, maximum number of subscriber could not be stored because thetraceby and therefore, currently broadcasted sessions supported by the BTS, which is maximum of However, LNADJW none instances the cells ofnumber the BTS. of 60. is already reached. additional these PLMNs have The MMEs serving alarm -info Theholds handover in the BTS is for thetype UTRAN of ongoing the specific RAT with CGI relative capacity the UE to be traced. reportedthan WCDMA whichofcould not greater zero. cell, Because this, the be stored, the form BTS cannotinselect anyof: of these MMEs In case of cell,WCDMA interface, PCMD "A celland which is for neighbour any new UEs attempting registration report trace, the possible reasons reported by an UE due to activatedare: ANR in these PLMNs. -feature(s) The Cell could Trace not feature is not because enabled in be stored the BTS. the maximum number of WCDMA Each MME can be assigned to handle -neighbour The PCMD report trace feature is not cells is reached. cells of a given RAT types: WCDMA enabled in the BTS. neighbour information needs be no - Widebandcell LTE (default, used when

Start / Cancel

Start / Cancel

Start

Start

Start

Transient

Start / Cancel

Transient

Transient

This alarm indicates that a WCDMA neighbor relation, which is reported by a UE through ANR-specific measurements, could not be stored because the maximum number of neighbor relations This alarm indicates that a WCDMA per cell is already reached. The neighbor relation, which is reported by a additional alarm info holds the ECGI of UE because of activated UTRAN ANR the LTE cell and the UTRAN CGI of the feature has been stored, but at least one related WCDMA neighbor cell in the form: of the mobility parameters of LNRELW A handover target cell cannot be uniquely "LTE cell ECGI{ecgiAdjBTSId = %d, (csfbPsHoAllowed, psHoAllowed, and selected several candidates are ecgiLcrIdbecause = %d, ecgiPlmnId = { %d, %d, srvccAllowed) available for a certain PCI value %d, and %d}} , WCDMA cell CGI {rncId= has been set to "forbidden" because the carrier CellId=frequency. %d, cgiPlmnId = { %d, %d, %d}}". number of neighbor relations The EARFCN of an LTE neighbor (LNRELW instances) exceeds the cell is a mapped number EARFCN to the maximum ofaccording WCDMA neighbor MFBI-profile cells, which configuration (that is, the requirement forby a homogeneous MFBI might be used the BTS in configuration isconfigurations violated). measurement (for This fault occurs when CGI psHoAllowed srvccAllowed, in measurementsorindicate that twolimit or more As a consequence, HO to this neighbor 3GPP 36.331 is (32); for cells that operate on the same frequency cell is not possible, and call drop rate csfbPsHoAllowed use the same PCI.is might increase if there is no other LNHOW::maxNumCsfbTargets). This faulthandover indicates that absolute suitable target. If the UE-based The additional alarm infothe holds the phase of affected a BTS theislimit of ANR iserror activated and exceeds the X2 link ARFCN of the carrier frequency 5 and depending on that available, there will beand continuous retries asus, well asthe thefeatures LNCEL LNRELW accuracy have been deactivated. This to resolve the ECGI. instance number in the form of: can occur when theARFCN following conditions "Affected This fault WCDMA occurs when CGI carrier = %d, happen: LTE cell ECGI{ecgiAdjBTSId = %d, measurements indicate that two or more ecgiLcrId = %d, ecgiPlmnId = { %d, %d, WCDMA cells -%d}} The ,absolute value of the estimated WCDMA cell same CGI {rncId= that operate on the carrier%d, phase error of an BTS has exceeded the CellId= %d,use cgiPlmnId = {primary %d, %d, %d}}" frequency the same An has been detected limitinconsistency of 5 us. scrambling code (PSC). between cluster members, which prevents - The BTSthe is in holdover mode for more inter-BTS CA feature from being enabled. than 6 hours, which means that the estimated phase error value might not be A SW incompatibility has been detected reliable. It is assumed in this case that between cluster members, which the real absolute value CA of phase error prevents the inter-BTS feature fromis greater than 5 us. being enabled.

Transient

Transient

Transient

Transient

Transient

Start / Cancel

Transient

Start / Cancel

Start / Cancel

The has detected a problem - Theapplication BTS is in assisted holdover mode Start / Cancel with inter-BTS linkhours, communication (SRIO, for more than 24 which means RP3-01, Ethernet, phase and soerror on). Features that the estimated value that the inter-BTS mightdepend not be on reliable. It is assumed in this communication, like the "Inter BTS case thatthe real absolute of phase Start / Cancel This fault is reported whenvalue the BTS Carrier aggregation" feature, are error is greater than 5 us. detects that the number of neighbordisabled. related objects (which represents the -neighboring The BTS isBTS, synchronized by awith Sync and its cells the Master, which reports the phase error of relationship objects) in its database are This fault is reported whenThe theabsolute BTS Start / Cancel the provided sync the signal. equal to or above configured value of detects that the numbertotal of neighborvalue of the estimated phase error the parameter "maxNumAnrMoiAllowed" related objects (which represents thelimit. in Sync Slave exceeds the 5 us in the LNBTS. neighboring BTS, and its cells with the relationship objects) in its database is equal to or above an internal threshold based on the configured value of the parameter "maxNumAnrMoiAllowed" in LNBTS.

BTS is informed about sync loss of Start / Cancel neighbor BTS in the same cluster and as a consequence needs to deactivate Carrier Aggregation feature. Inter BTS SRIO link couldn't be Start / Cancel established due to DomainIds not being unique or other errors in cluster topology. BTS has detected carrier aggregation Start / Cancel relation misconfiguration. One or more of the configured carrier aggregation relations point towards a cell that does not exist in any of the BTSs within the The pool configuration of the resource Start / Cancel configured carrier aggregation cluster. DSPs has failed between C-Plane and Uplane. The BTS configuration has failed in the C-Plane.

Start

The configured PUSCH masking and/or Start / Cancel PUCCH blanking size for the cell leads to a situation where there are no remaining resources for the PRACH allocation. The automatic PUCCH allocation Start / Cancel configuration cannot support the operator configuration. The sidelink transmit resource pool configuration is invalid and overlapping with PUCCH region, or leaving insufficient resource for PRACH.

Start / Cancel

A neighbor cell, which is detected by a Transient UE through measurements due to activated ANR features, could not be stored because the maximum number of 1xRTT neighbor cells (LNADJX The X2 interface reset has failed after Start / Cancel instances) is already reached. Neighbor several attempts. This indicates that a cell information needs to be cleaned up severe failure has occurred. For manually by the operator through the example, there is some configuration plan file. problem, there is no X2 connectivity, the There is no X2 connectivity to an Start / Cancel adjacent BTS has failed, and so on. adjacent BTS, the adjacent BTS has failed, and so on. There is no S1 connectivity to an MME. The fault is generated if the S1 setup procedure has subsequently been attempted but failed the number of times equal to the value of the parameter "maxS1SetRetry".

Start / Cancel

The S1 interface reset has failed after several attempts. This indicates that a severe failure has occurred: there is some configuration problem; there is no S1 connectivity; MME has failed, and so The S1 BTS configuration update on. procedure has failed. The MME could not be informed about the modification of at least one of the A RIM request to the serving BSS has following BTS configuration data: failed after several attempts. This means - BTS Name that the System Information for the - Supported TAs (TAC, PLMN Identities) related GERAN or UTRAN neighbor cells - Default paging DRX is not reliable. 1. An RIM association could not be established because an RIM Error PDU has been received for an RIM-enabled GERAN neighbor cell. 2. An RIM Application Error has been The System Information Broadcastdetected. related parameters have changed more 3. S1 links to all configured MMEs are than 32 times within three hours. active, but the routing of RIM PDU to the RIM-enabled WCDMA neighbor cell is After a DSP crash, the BTS collects core not available. dumps and DSP memory dumps from the crashed DSP. After an FCT or an FSP crash, the BTS collects core dumps from the crashed The physical memory supervision has unit. detected that memory usage has Fault 6450 notifies the operator that the exceeded a HW/board specific threshold. logs are stored in the BTS and can be collected in the snapshot. The sleeping cell suspicion has been detected. The symptom data is automatically collected.

Start / Cancel

Transient

Start / Cancel

Start / Cancel

Transient

Start / Cancel

Start / Cancel

Start

A correctable bit toggling error is detected in DSP memory.

Transient

A non-correctable, bit-toggling error has been detected in the critical DSP memory.

Start

A non-correctable bit toggling error is Transient detected in the non-critical DSP memory area. A fatal error of the DSP HWAPI SW has occurred. If an FSP in the BTS generates this fault, there is a malfunction in the corresponding FSP sub-module. If all FSPs generate this fault, there is a malfunction in the FSM.

Start

A fatal error of the DSP Application SW has occurred.

Start

If an FSP in the BTS generates this fault, there is a malfunction in the The BTS has purposely triggered a GPIO Start corresponding FSP sub-module. reset for the DSP. If all FSPs generate this fault, there is a malfunction in the FSM. A digital signal processing (DSP) concurrent crash has occurred (a fatal error was indicated in one of the DSP cores that belong to the same chip). M3 interface reset has failed after several attempts. This indicates that a severe failure has occurred. There might be some configuration problem, there is no M3 connectivity, MME has failed, and so There is no M3 connectivity to an MME, on. the MME has failed, and so on. If the fault is canceled, autonomous recovery actions (reset) have solved the fault situation. There is a resource conflict in the MBMS subframe configuration, or the MBMS subframe configuration is inconsistent or respectively wrong. Reasons are either of the following: MCE configuration update has finally failed. 1. The maximum MBMS subframe pattern share of an MBMS The MME could not be informed about synchronization area, which is configured the modification of at least one of the The has encountered an internal with MCE the parameter following MCE configuration data: failure such as a timeout, unsuccessful maxSyncSubfrPShare, exceeds the - global MCE ID outcome while syncSubfrPShareAllowed, communicating with lower allowed share - MCE name layers/TRSW/RROM, and sowhich on. is that is, the maximum share - supported MBMS service area identities available due to the BTS feature An MBMS SESSION START REQUEST configuration. is received by MCE and cannot be

Start

Start / Cancel

Start / Cancel

Start / Cancel

Transient

Transient

Transient

admitted because the maximum number 2. maximum MBMS subframe of The MBMS sessions per MCE is exceeded, pattern share of an MBMS area, is or because the resources are notwhich enough An MBMS SESSION START REQUEST Transient configured with maxSubfrPShare, in any MBSFN supporting the requested is received MCE and is successfully exceeds thebyallowed service area, in whichshare case, the session admitted in at least one MBSFN but subfrPShareAllowed, is, the area, is suspended after thethat MCE/BTS has failed to beshare admitted due to resource maximum which is available in the already responded to MME with an constraints in other MBSFN areas MBSFN synchronization area considering Transient An MBMS SESSION START REQUEST MBMS SESSION START RESPONSE. supporting the requested servicestarting area. the configuration of the MBSFN is received and accepted MCE, but If the admission control is by periodically If admission control is performed subframe with parameter the session the admission some performed, warningfails shallinnot be periodically, the warning shall not be mbsfnStartingSF. MBSFN to other session reported area againdue if the content wouldwith be reported again if the content would be higher precedence that iswarning. admitted to identical to the previous The alarm raised if thewarning. monitored identical toisthe previous 3. The MBSFN subframe of Start / Cancel some other MBSFN area configuration with service is are unavailable when for example MBSFNs overlapping when overlapping subframes. all network paths are unavailable.isThis parameter If admissionmbsfnOverlapAllowed control is performed set to implies that all individual BFD sessions of "false". In such periodically, thecase, warning shall not be the respective group represented by syncSubfrPShareAllowed of the affected reported again if the content would be $BFDGRPID are erroneous. MBSFNSYNCAREA instance is set identical to the previous warning. to "0". Example(s) for alarm text: BFDGRP-10 down

This loss of frame alarm is raised when the local receiver is unable to detect the frame alignment word of the E1 signal. All other transmission alarms related to this signal are suppressed. This alarm is raised when either no or an $UNIT indicates the affected module incompatible signal is received on the from Equipment Management (last interface referenced in the alarm text. element of the DN). E.g. TRMOD-1. $UNIT indicates the affected module $INTERFACE indicates the interface on from Equipment Management (last A dead peerfollowing was detected in one on of the the module the labeling the element of the DN). E.g. SMOD-1. IPsec associations the or SBTS. frontplate of the realofHW the $INTERFACE indicates the interface on There is no response to the corresponding parameter in requests the the module following the labeling on the sent to the peer, either during the IKE Management Model. frontplate of the real HW or the SA setup, the IPsec SA setup, or during E.g. EIF1, This alarm IF1 is raised if a loopback corresponding parameter in the has DPD. been configured by a management Management Model. Example(s) forthe alarm text: "LOF on application on interface mentioned in E.g. EIF1, IF1 Note: WhenIF2" IPsec backup tunnel feature TRMOD-1, the alarm text. is enabled, this alarm is not raised $UNIT the affectedthe module With anindicates Ethernet interface, physical The small form-factor pluggable due to failures when to setup Probable cause: Thetrying interface at(SFP) the far from Equipment Management (last Ethernet link is detected to be down. All module is not supported, is aexpected but primary IPsec tunnel in end is not configured to be framed E1 element of the DN).alarms E.g. TRMOD-1. other transmission related to this not present, or could not be recognized. "Secondary_Active_Probing_Primary" interface. $INTERFACE indicates the interface on signal are suppressed. The state.small form-factor pluggable (SFP) the module following the labeling on the module detected if the SFP slot does not This fault causes is if the cannot frontplate of raised the real HWSBTS or theinterfaces: Probable for Ethernet comply with the SFP module types update the Certificate Revocation List corresponding parameter in the -supported a cable/fiber is cut or there is no by the BTS element. (CRL). Management Model. to the interface cable/fiber connected E.g. IF1 -Probable the EIF1, electrical/optical signal is causes: The failure reasons include the following: $LOOPTIMEOUT indicates time excessively attenuated A loopback is requested for an - No SFP module is inserted in Ethernet the SFPperiod in either minutes after which the inserted -interface the port at the connected far end node the based SFP slot.locally at the BTS, or -loopback The LDAP binding fails. automatically. shall terminate is switched off clientcontacts of the BTS is set into -Link TheOAM interface of the SFP -loopback the advertised technology mode by theorremote Link OAM module are corroded dirty,capabilities preventing -Example(s) Theauto-negotiation LDAP for search is of empty (no CRL at alarm text: with both devices peer. either read access to the SFP module at On an interface for which the Link OAM found)/ The LDAP search contains more "Interface under test on match TRMOD-1, IF2 the Ethernet link do not the time of reading compliance data from functionality was switchedat on, no devices Link than entry. for 2 one minutes" -the the Ethernet technology both SFP, or preventing detection ofthe the OAM PDUs were received during at the Ethernet link is forced manually module. period specified in configuration -and Thenot CRL signature validation fails. compatible -parameter The SFP module type is (2-10 not supported. "linkLostTime" seconds, - the peer containing of an Ethernet link islink A Linkremote OAM PDU a critical step 1CRL second). -not The file exceeds the BTS storage auto-negotiation capable or has autoevent flag was received on the Ethernet Note: The unit and interface variables limit. negotiation function disabled by interface. The is raised with the ($U,$IF) will bealarm replaced by appropriate configuration first detection of the flag. hardware. Example: unit-FSM, interface - The BTS certificate is part of the CRL. EIF1. The SFP has reported a transmission Probable causes for PDH interfaces: The following critical link events are fault condition has the laser -possible: DNS resolution thedisabled distribution a cable is cutand orfor there isCRL no cable transmitter. point fails. to the interface connected -- the electrical excessively Critical Event:signal eitherisan Errored Symbol A probable cause could be that the SFP attenuated This alarm is raised whenFrame the measured Period Event, an Errored Event, is defective. - the portrate atFrame the connected far end bit error exceeds the Event, threshold value an Errored Period ornode an is switched off Seconds Summary Event of BER-3Frame (10E-3). Errored Note: The and unit receive and interface -$UNIT transmit cablesvariables are mixed indicates the affected module was detected. ($U,$IF) will be replaced by an up from Equipment Management (last This loss of multiframe alarm is raised appropriate hardware. Example: unit- if element of the either DN). E.g. TRMOD-1. -the Dying Gasp: the local oralarm the text interface referenced in the FSM, interface EIF1. Examples forhas alarm text:error $INTERFACE indicates the interface remote a fatal and is on has lostpeer the multiframe alignment. Ethernet: "LOS on SMOD-1, EIF2"on the the module following the labeling about to restart. $UNIT indicates the affected module or frontplate of the real HW or the from Equipment Management (last "LOS TRMOD-1, EIF3" corresponding inhas thedetected a -element Link on Fault: theparameter localE.g. peer of the DN). TRMOD-1. PDH: "LOS TRMOD-1, IF2"direction, Management Model. physical linkon fault in receiving $INTERFACE indicates the interface on E.g. EIF1, IF1a LOS. for example, the module following the labeling on the frontplate of the real HW or the Probable causes: Note: corresponding parameter in the -Inthe signal level is OAMPDU too low (connectors case a received has more or Management Model. cables arecritical dirty, electrical connectors than one event flag set, the or E.g. EIF1, IF1 cables areshall corroded) following be reported in the alarm: -Link the Fault specified maximum length ofset| the bit set |Dying Gasp bit Probable cause: The interface type has cable isEvent exceeded Critical bit set| Reported not been configured to meet the framing

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Active / Cleared

Start / Cancel

Start / Cancel

This alarm is raised when an alarm indication signal is received. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its received signal. This alarm is raised when a remote defect indication is received. It is sent by AIS defect is detected when the incoming the intermediate or the far-end signal has two or less zeros in each of equipment because it detects a serious two consecutive double frame periods fault in the received signal. The is missing. The SBTS is 5.2 (512module bits) according [G.775] chapters $UNIT indicates the affected module expecting and I.2. a transport module, but it has from Equipment Management (last not element of the DN). E.g. TRMOD-1. been detected. All other transmission alarms related to $INTERFACE indicates the interface on this signal suppressed. This alarm are isfollowing raised when the the module the labeling on the The probable causes are the following: localIPAddress frontplate of thenegotiation real HW or with the the peer -$UNIT The module is not indicates the present. affected module fails. corresponding parameter in the -from TheEquipment module is broken. Management (last Management Model. element of the DN). E.g. TRMOD-1. E.g. EIF1, IF1 This alarm is raised if local and peer Note: The variable $U isthe replaced by the $INTERFACE indicates interface on ends disagree on the the LCP configuration appropriate hardware. The actual on value the module following labeling the Probable cause: The far end has a LOS, leading LCP is FTIF. to of frontplate thenegotiation real HW orfailure. the LOF or AIS alarm on its receiving corresponding parameter in the interface. The related configuration Management Model.if the parameters This alarm is raised PPP interface are: acfcTarget, localMruTarget, and E.g. EIF1, IF1 is not operational either when the Example(s) for alarm text: "RDIallon pfcTarget. PPP-links the ML-PPP interface are TRMOD-1,inIF2" Probable cause: There is a transmission not available, or the PPP-link supporting problem somewhere in the SL-PPP interface is the not intermediate available. The alarm is triggered whenever a is network along the E1 path and AIS service OAM error related to the sent instead of user traffic. transmission of Continuity Check Messages persists on a on given Example(s)(CCM) for alarm text: "AIS Ethernet interface as soon as one of the TRMOD-1, IF2" When an MEP receives a valid ETH-AIS error conditions below occur: frame and AIS is enabled, it shall trigger an AIS alarm containing the following The following alarms are defined: information: - receiving interface A certificatepriority could 5 not be 1. requested MDL_MISMATCH, (highest - MD level retrieved the authority priority): Afrom CCM is certificate received with an MDL - Source MAC address (CA). that is lower than the highest configured A requested certificate could be any one in the BTS, and does notnot match Note:For FSMr3/AirScale unit types, the renewed from theones. certificate authority of the configured The alarmisisprovided raised ifas: the"module BFD state for interface type (CA). Example: CCM fault level - prioand, 5 cause the session is not AdminDown name" EIF "interface number". A requested certificate could not be MDL_MISMATCH nevertheless, BFDBTS, packet received For Flexi Zoneno Micro theisinterface retrieved because the number of it Note: cases, at the For localMDL_MISMATCH endEIF during the detection time. is provided as: "interface number". certificates from the repository might notindicates bereceived possible to display the local $BFDID the BFD identifier. The the authority BFD state(CA) of server (RA)isthe orraised certificate MDLalarm where faultifwas detected. the is not AdminDown and the are session more than expected. Example for alarm text: BFD packet from the far end contains 2. MAID_MISMATCH priority 5: A CCMthe is "BFD-10 down in ingress" diagnostic code =MDL 'Control Detection received with an that is configured The source and destination IP addresses Time Expired' noanBFD down Ingress in BTS, butand with that This alarm indicates thatMAID there is adoes willthe be displayed in alarm diagnostic info alarm is present. not match any MA configured in the BTS mismatch between SBTS expected autofield as below: on this MDL. negotiation result$BFDSCRIPADDR, and actual auto- Dest "Source IP addr Example for alarm Example: CCM faulttext: level 5 prio 5 cause negotiation result. IP addr $BFDDESTIPADDR" "BFD-10 down in egress" MAID_MISMATCH The source and destination IP addresses An Ethernet link was established, but will be displayed in alarm diagnostic infois 3. MAID_MISMATCH priority 5: A CCM during the link establishment a link speed field as below: received matching MDLAand downshiftwith event took place. link MAID, speed "Source IP addr $BFDSCRIPADDR, Dest but the VLAN membership the downshift takes place whenofautoIP addr $BFDDESTIPADDR" received frame does not match the VLAN negotiation successfully negotiates a configuration of the but addressed MA. be certain technology, the link cannot Example: CCM fault level 5 prio established with this technology.5Itcause is tried MAID_MISMATCH then to establish the link with the next lower speed technology. 4. 4: A CCM iswith AnERR_CCM, Ethernet linkpriority was established

Start / Cancel

Start / Cancel

Active / Cleared

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

The RTT threshold alarm is raised in case the average value of the RTT for this TWAMP session from the last 1-min period equals or exceeds the configured threshold. The alarm is raised if the packet loss $TWAMPID indicates the TWAMP ratio equals or exceeds the configured session identifier. threshold value during the current observation interval of 15 minutes. Example(s) for alarm text: $TWAMPID indicates the TWAMP This is raised whenon theTWAMP-10" Vendor BTS "RTTfault threshold crossed session identifier. certificate is about to expire. The period of notification in advance is Example(s) for alarm text: configurable from 1 day to 4999 days. "PLR threshold crossed on TWAMP-10" The default is 90 days. NE stores trust anchors for its own trust chain and for peers. When own or any trust anchors are about to expire or already expired, this alarm is sent.

Start / Cancel

This alarm is raised if at least one of the Note: This alarm is only generated for PPP-links belonging to the ML-PPP operator TA and not vendor TA. interface is not operational.

Start / Cancel

In case the incoming SSM (Synchronization Status Message) is not received for a certain time period (configured via "ssmTimeout" parameter), an alarm is This alarm is raised when SSM raised. (Synchronization Status Message) is $UNIT indicates the affected module enabled and the received SSM indicates from Equipment Management (last lower element of the DN). E.g. SMOD-1. clock quality than required (configured During the IP address $INTERFACE indicatesconfiguration, the interface on via "ssmAcceptanceLevel" parameter). before allocation of new addresses, the module following the IPv6 labeling on the $UNIT indicates the affected module the network testsorwith frontplate of element the real HW the DAD from Equipment Management (last (Duplicate Address Detection) corresponding parameter in thethe direct element of the DN). E.g. SMOD-1. attached transport network whether the Management Model. SBTS has entered IPsecthe emergency $INTERFACE indicates interface on other already-configured network E.g. EIF1 bypass active state where configured the module following the labeling on the elements on the network use the same IPsec policies are ignored, frontplate of the real HW orand the all traffic IPv6 addresses on their network IP Example(s) for alarm text: is sent unprotected. corresponding parameter in the interfaces including The "SyncE SSM Timed the OutLink-Local. on TRMOD-1, Management Model. when the IP traffic The is activated DAD detects those duplicated IPv6 EIF3"alarm E.g. EIF1 capturing is started. addressessession and prohibits the operation of The SBTSaddress is currently traffic this IPv6 in thecapturing network IP element. Example(s) for alarm towards a local port the ortext: into a file on the The Alarm contains corresponding "SyncE Quality Level Degraded on SBTS. IPv6 address thelocal system attempted to A specific SBTS operator account TRMOD-1, EIF3" If the traffic capturing is happening allocate based on the manual has been locked. towards a local port, the portalarm and is configuration If the The number ofoptions. failed login attempts for a destination MAC address needs be reported for the IP interface, it willtoshow SBTS local operator account has provided. the Link-Local IPv6 address exceeded the threshold and the the system account This alarm will bethe triggered at least $UNIT affectedwhen module failed toindicates allocate. has been locked on the SBTS. No further one IPsec tunnel fails, (last and fromprimary Equipment Management logins will be permitted from this account SBTS has switched overDup to secondary element of the DN).text: E.g. SMOD-1. Example for alarm Addr until the account is unlocked. IPsec tunnel. indicates the interface on $INTERFACE detected the module following the labeling on the 2001:0db8:85a3:0000:0000:8a2e:0370:7 As failure at or least frontplate real in HW theone 334a resultofofthe primary IPsec tunnel, SBTS has corresponding parameter in the automatically Management switched Model. over to secondary IPsec tunnel E.g. EIF1, IF1terminating on secondary security gateway. indicates the $MACADDRESS corresponding 'macAddr' parameter in the object model.

Start / Cancel

Example(s) for alarm text: "IP Traffic Capturing ongoing on SMOD-

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

The alarm is raised when the IKE authentication credentials provided by the peer are not valid.

Start / Cancel

The alarm is raised if IKE parameters are Start / Cancel not matching with the peer proposal. It can happen due to the following two failures: This alarm is raised when the SBTS --> When the SBTS sends or receives a sends or receives the following failure notification as a response to an notification as a response to an IKE_SA_INIT request message. The IKE_AUTH or CREATE_CHILD_SA failure notifications includes: request message. The fans in the RF module rotate faster than required. - NO_PROPOSAL_CHOSEN The failure notifications includes the following: - INVALID_SYNTAX

Start / Cancel

A module initialization has failed. - NO_PROPOSAL_CHOSEN - INVALID_MAJOR VERSION

Start

- TS_UNACCEPTABLE - INVALID _IKE_SPI - INVALID_SYNTAX - INVALID_MESSAGE_ID - INVALID_MAJOR VERSION UNSUPPORTED_CRITICAL_PAYLOAD - INVALID _IKE_SPI or FAILED_CP_REQUIRED - INVALID_MESSAGE_ID --> When the SBTS sends or receives a failure notification as a response to an IKE_AUTH request message. The failure UNSUPPORTED_CRITICAL_PAYLOAD notifications include: - SINGLE_PAIR_REQUIRED or - INVALID_SYNTAX FAILED_CP_REQUIRED - INVALID_MAJOR VERSION - INVALID _IKE_SPI - INVALID_MESSAGE_ID UNSUPPORTED_CRITICAL_PAYLOAD

Start / Cancel

Unit Status

Unit Status Attributes

Working

Degraded,Out of order,Working

Working

Out of order (FCT, FSP/FBB/ABIx when shutdown)

Degraded(FSP/FBB/ABIx otherwise)

Out of order

Out of order

Out of order

Degraded,Out of order

Out of order (1. FCT 2.FSP/FBB/ABIx when shutdown or when FSP/FBB/ABIx critical core is faulty)

Out of order

Out of order

Out of order,Working

Degraded (FSP/FBB/ABIx otherwise)

FCT (HW rel.3), FCT (HW rel.4), ABIx, FSP = Out of order FR(the cell cannot operate)= Out of order FR(the cell can operate)= Working

Working

Working

Working

Working

Degraded,Working

Degraded,Working

Working

Working - if incompatible software version has been detected on the same unit and corresponding fault 23:EFaultId_IncompatibleSwVersi onAl has been already reported. Working - if incompatible software version has been detected on the Degraded - in any other case. same unit and corresponding fault 23:EFaultId_IncompatibleSwVersi onAl has been already reported. Degraded - in any other case.

Out of order

Out of order

Out of order

Working

Out of order

Degraded

Out of order

Out of order

Out of order

Degraded,Out of order

Working

Out of order

Working

Out of order

Working

Degraded

Degraded

Degraded(FSP/FBB/ABIx otherwise) Out of order (FSP/FBB/ABIx when shutdown) Out of order (RX/TX)

Degraded,Out of order

Degraded(FSP/FBB/ABIx otherwise) Out of order (FSP/FBB/ABIx when shutdown)

Degraded

Degraded

Degraded,Out of order

Degraded(FSP/FBB/ABIx otherwise) Out of order (FSP/FBB/ABIx when shutdown)

Out of order,Working

Out of order: in cell setup phase Working: runtime, when new PIC pool configuration is ignored.

Working

Degraded,Out of order

Degraded

Working

Working

Working

Out of order

Degraded(FSP/FBB/ABIx otherwise) Out of order (FSP/FBB/ABIx when shutdown)

Degraded

Degraded

Degraded,Out of order

Out of order (FSP/FBB/ABIx critical core is faulty) Degraded (FSP/FBB/ABIx otherwise)

Degraded,Out of order

Out of order (FSP/FBB/ABIx when shutdown)

Degraded,Out of order

Working

Working

Working

Working

Working

Working

Working

Degraded(FSP/FBB/ABIx otherwise) Out of order (FSP/FBB/ABIx when shutdown) Degraded(FSP/FBB/ABIx otherwise)

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Out of order,Working

Working if the fault is notified by FR, out of order in other cases.

Degraded,Out of order

Out of order (1. FCT, 2. FTM 3.FR, 4.MHA, 5. RET. 6.FSP/FBB/ABIx when shutdown or when FSP/FBB/ABIx critical core is faulty)

Out of order

Degraded (FSP/FBB/ABIx otherwise) Out of order

Out of order

Out of order (FSP/FBB/ABIx when shutdown, FCT, FR, OptIF) Degraded(FSP/FBB/ABIx otherwise)

Degraded,Out of order,Working

Out of order

Degraded

Out of order

Degraded

Degraded - when no other reference clock sources are available Working - when there is at least one more working reference clock source available. Out of Order - Holdover not Degraded: the DAC value of possible because of word insufficient the is lower dataOCXO or phase error or in equal holdover Min.OcxoControlValue.Alarm.Set exceeds 3 us or the DAC word value of the OCXO is higher or equal Max.OcxoControlValue.Alarm.Set. Out of order: the DAC word value of the OCXO is equal Min.Accept.OcxoControlValue or equal Max.Accept.OcxoControlValue.

Degraded

Out of order

Degraded

Degraded,Out of order

Degraded

CPRI-A: Degraded (as long as VSWR level is below the HW limit defined in the radio) Otherwise: Out of order - in normal BTS operation

Out of order

Out of order

Out of order

Degraded

Degraded

Degraded

Degraded

Degraded

Out of order

Out of order

Degraded

Out of order

Out of order

Degraded

Out of order

Working

Working

Working

Working

Out of order

Working

Degraded,Working

Degraded,Working

Degraded (there is no other available and usable input reference source to be selected) Working (SBTS is synchronized with another input reference Degraded (other clock is not source) available) Working (other clock is available)

Out of order

Out of order

Degraded

Out of order

Out of order

Out of order

Degraded

Degraded,Out of order

Degraded (if cell can still operate because it still has enough available and needed resources: both Tx and Rx)

Degraded,Out of order

Degraded (TX path is still Out of order (cell cannot operate operational but with degraded because of not enough available performance) and needed resources: Tx or Rx).

Out of order

Degraded,Out of order

Out of order

Degraded,Out of order

Out of order (TX path is out of service)

Degraded (if cell can still operate because it still has enough available and needed resources: both Tx and Rx) Out of order (cell cannot operate because of not enough available and needed resources: Tx or Rx). RRU connectedfor over CPRI Ir See Reference details. interface: Degraded

Degraded

Degraded

Other radio modules - e.g. RFM connected over OBSAI RP1 interface: Out of Order

Out of order,Working

Degraded

Out of order (The radio unit is too cold to properly generate RF) Working (The radio unit is able to generate RF)

Degraded

Degraded,Out of order

Out of order

Degraded

Out of order - the radio's power-on self test detected a critical failure that prevents the radio from operating. Degraded - at least one failure was detected during the radio's power-on self-test, but the unit may still be functional, though in a degraded state

Degraded

Out of order

Working

Degraded,Working

Working

One fan failed: Module = Working, Fan group = Degraded Two or three fans failed: Module = Degraded, Fan group = Out Of Module = Working, Fan group = Order Degraded [AAS]: Working

Out of order

Degraded,Out of order

Degraded

Out of order

Out of order

Working

Degraded

Out of order

Working

Out of order

Out of order

Degraded

Out of order

Degraded - validated temperature of any PA or Pipe sensor is >= Tdanger (when any TX/RX resources are available on alarming FRM)

Out of order - dangerously high temperature occurs longer than tT+danger and carriers are deactivated (when no RX/TX resources are available on alarming FRM)

Working

Working

Working

Working

Out of order

Working

Working

Working

Out of order

Out of order

Out of order

Degraded

Degraded

Degraded

Working

Out of order

Out of order

Degraded

Out of order

Degraded

Degraded,Out of order,Working

Out of order

Working - if raised for SSD firmware update. Degraded - if raised for Atmel uController FW update. Out of order - in any other case.

Degraded

Degraded

Degraded

Out of order

Degraded,Out of order

Out of order(FSP/FBB/ABIx when shutdown or critical core is faulty) Degraded(FSP/FBB/ABIx otherwise)

Out of order

Out of order

Degraded

Degraded,Out of order

Degraded,Out of order

Degraded,Out of order,Working

Degraded

Working

Out of order,Working

- Out of order (GNCEL state when all the channel groups of the cell are faulty) - Degraded (GNCEL state - when only few of the channel groups of - Out of order (GNCEL state the cell are faulty) when all the channel groups of the cell are faulty) - Degraded (GNCEL state - when only few of the channel groups of - Out of order (BTS (sector) state the cell are faulty) - fault is reported when the sector is not able to be mapped to a local cell) - Out of order (BTS (sector) state - Degraded (Antenna line state - fault is reported when the sector fault is reported on any of the is configured TRXes of the sector) with no TRX and there is corresponding local cell -commissioned This fault is a with notification channelto the operator groups) to inform that license for the TX power pooling - Degraded (BCF statefeature - fault is missing. reported when local cell is not able to be of order(BCF state - OMU - Out mapped BTS not (sector)) signallingtocould be established -during Degraded (BTS the startup)(sector) state other cases) state - OMU - Working(BCF signalling broken during runtime)

Out of order,Working

Out of order

Degraded

Working

- Out of order (BCF state - when the fault is reported during base station startup) - Working (BCF state - when the fault is reported during runtime) BCF state is set as Out of order when BSC does not respond to BTS initialization proecdure GNCEL state is set as degraded when a TRX is added to an antenna hopping sector and newly added TRX can not be part of any hopping group - Working (fault is reported at BCF)

Degraded

Working

Working

Degraded,Out of order,Working

Degraded/Out of order (case 12 and 15) Out of order (otherwise)

Working

Out of order

Out of order

Degraded,Out of order

Out of order (1. FCT, 2.FSP/FBB/ABIx when shutdown or when FSP/FBB/ABIx critical core is faulty) Degraded (FSP/FBB/ABIx otherwise)

Out of order

N/A

Working

Out of order,Working

Degraded

Out of order

Working

Out of order

Degraded

Working

Working

Out of order

Out of order: when the problems prevents BTS to reach operational state (wrong or missing RNW data/active commissioning data not readable).

Working: if there have been problems with commissioning data in SW package but still BTS is operational.

Out of order

Degraded,Out of order

Out of order

Working

Out of order

Out of order

Degraded,Out of order

Out of Order: When ALD commissioned is only powered from the RS485 port. - If a DC LOGLINK between port and ALD unit (LNA, RETU, RAEU) exists and this is the only DC LOGLINK connected to that ALD unit (ALD unit is powered from single source) Degraded: Otherwise. - If DC LOGLINK between port and ALD unit (LNA, RETU, RAEU) doesn't exist or there is no ALD connected to that port, - If a DC LOGLINK between port and ALD unit (LNA, RETU, RAEU) exists but this ALD unit has also another DC LOGLINK (ALD unit is powered from multiple sources),

Not all fans failed: alarming fan = out of order, fan group = degraded

Degraded,Out of order

All fans failed: all fans and fan group = out of order - Out-of-order - in case of inconsistent SW after SW fallback

Degraded,Out of order

- Degraded in - case of consistent SW after SW fallback - Out-of-order - in case of inconsistent SW after SW fallback

Degraded,Out of order

- Degraded in - case of consistent SW after SW fallback - Out-of-order - in case of inconsistent SW after SW fallback

Out of order

Degraded,Out of order

- Degraded in - case of consistent SW after SW fallback

Out of order - the cell can not operate because downlink carrier which transmits PSS/SSS signals is failed. Degraded - the cell can still operate because downlink carrier which transmists PSS/SSS signals is still working.

Working

Out of order

Working

Working

Out of order

Out of order

Out of order

Out of order

Out of order

Out of order

Degraded

Out of order

The master system module works properly.

Out of order,Working

Out of order - in BTS startup Working - in BTS runtime

Degraded,Out of order

Out of order

Out of order: when startup stopped or startup continued without reference clock but the BTS doesn't go to OnAir

Working

Degraded: startup continued in frequency mode

Degraded

The card may be used (e.g. radio may be connected to port 1 and provide services for some cells) and this is why it is "Degraded".

Working

Degraded,Out of order

Status "degraded" is used for failure during BTS runtime Status "out of order" is used for failure during BTS startup.

Degraded,Working

Working: -other valid synchronization reference source is available

Degraded

Working

Degraded

Out of order

Degraded: -otherwise

Out of order

Out of order

Degraded

Degraded

Working

Working

Working

Working

Out of order

Working

Working

Degraded

Out of order

Out of order,Working

Out of order - - IQ Compression issue Working - / - ALD commissioning issue

Degraded

Degraded

"SBTS/MGMNT/CAPLIM/hsupaUs ers" has set value.

Degraded

Degraded

Working

Degraded,Working

Degraded,Working

Degraded,Working

Working

Degraded

Degraded - when no other reference clock source is available Working - when there is at least one more working reference clock source available Degraded - when no other reference clock source is available Working - when there is at least one more working reference clock source available Degraded - when no other reference clock source is available Working - when there is at least one more working reference clock source available

Working

Degraded,Out of order

Out of order

Out of order - link is unsynchronized both at 3Gbps and 6Gbps Degraded - link is synchronized at 3Gbps

Working

Working

Working

Degraded

Out of order

Degraded

Degraded,Out of order

Out of order (ABIx when shutdown) Degraded(ABIx otherwise)

Working

Degraded

Working

Degraded,Out of order

Out of order (FBB/FSP when shutdown or when last FSP is faulty) Degraded (FBB/FSP otherwise)

Working

Degraded

Out of order

Working

Out of order

Out of order

Out of order

Out of order

Degraded,Out of order

Working

Degraded if some cells can continue to operate Out of order if all cells cannot operate

Working

Working

Degraded

Flexi SBTS: - Degraded - in case of consistent SW after SW fallback

Out of order

Degraded,Out of order

Out of order

Degraded

Degraded - At least one cell is still operational Also reported when the BTS power supply is available again but not all cells are enabled yet. Out of order - All cells are disabled - Degraded (GNCEL state - Only few of the channel groups of a cell are blocked)

Out of order

Working

Degraded,Out of order

Degraded

Working

- Out of order (GNCEL state when all the TRXes of the sector are disabled) - Degraded (GNCEL state - when only few of the TRXes of the sector are disabled)

Working

Working

Degraded

Working

Working

Degraded

Degraded

Working

Working

Degraded

Degraded,Out of order

Degraded

Degraded - there is still at least one S1 interface available for use Out of order - no other S1 interface available for use.

Degraded

Degraded

Working

Out of order

Out of order

Out of order

Working

Out of order

Working

Degraded

Working

Working

Working

Working

Working

Working

Working

Working

Working

Degraded

Degraded

Degraded

Degraded

Working

Degraded

Degraded

Degraded

Out of order

Out of order

Out of order

Working

Out of order

Working

Degraded

Degraded

Degraded,Out of order

Unit status is Degraded if at least one other S1 interface is operational, or else the Unit status is Out of order.

Degraded,Out of order

Unit status is Degraded if at least one other S1 interface is operational, or else the Unit status is Out of order

Working

Degraded

Degraded

Working

Working

Working

Out of order

Working

Working

Working

Degraded,Out of order

Out of order (FSP/FBB/ABIx when shutdown)

Degraded(FSP/FBB/ABIx otherwise)

Degraded,Out of order

Out of order (FSP/FBB/ABIx when shutdown)

Degraded,Out of order

Out of order (FSP/FBB/ABIx when Degraded(FSP/FBB/ABIx shutdown) otherwise)

Degraded,Out of order

AirScale SBTS, Flexi SBTS: Degraded(FSP/FBB/ABIx Out of order (FSP/FBB/ABIx when otherwise) shutdown)

Degraded

Degraded

Degraded

Working

Working

Working

Working

Working

Out of order

AirScale SBTS, Flexi SBTS: Degraded(FSP/FBB/ABIx otherwise)

Out of order

Out of order

Degraded

Working

Out of order

Degraded

Major

Major

Major

Out of order

Degraded

Degraded

Degraded

Degraded

Out of order

Out of order

Degraded

Out of order

Major

Major

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Working

Working

Working

Degraded

Working

Working

Degraded

Degraded

Degraded

Degraded

Working

Out of order

Module = Working, Fan group = Working

Effect

Reported Alarms

The operation of the BTS decreases.

7115 BASE STATION INFORMATION

If the FSP/ABIx update fails, the BTS capacity drops. If the optical interface FPGA SW update fails, communication to radio modules does not work, and the BTS is not operational. This fault does not immediately affect the operations of the BTS, but it is a notification that the BTS master clock frequency deviates from the used reference frequency more than in normal circumstances. The module in question is out of use. This fault cancels all the active faults for the The BTS master clock tuning continues same module. regardless of the alarm, but because the BTS master clock adjustment is quite slow Allfilter cellsthe areinstabilities not operational. to of the reference clock interface, it takes some time (even several hours) before the BTS operations start to be affected.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7111 BASE

The wcdma cells are not operational.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

7115 BASE STATION INFORMATION

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

The BTS capacity possibly decreases; some 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE cells might become disabled. The BTS is out of order. All cells are disabled. All ongoing calls are dropped. New calls are not possible.

7107 BASE STATION CONNECTIVITY PROBLEM

All cells are disabled. All ongoing calls are droped. New calls are not possible.

7107 BASE STATION CONNECTIVITY PROBLEM

The resources provided by the module cannot be used, which means that some features might not work.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT

For FR modules, the resources provided by the module can be used if critical functionality for cell set-up is available. In case of FR modules with factory SW loaded, other alarms can be reported later for this FR module (or FR modules further in the chain) when the RF modules will be incapable to provide services properly for the cells.

Resources provided by the module cannot be used, which means that some features might not work.

7115 BASE STATION INFORMATION

If the fault is reported for the FR module, Real time is not available. Alarms, logs, and 7115 BASE STATION INFORMATION BTSOM does not know the real state of the all reports have an incorrect time. FR module, and thus, BTSSM keeps the FR LED display disabled (grayed). The reason When btsSyncMode is PhaseSync, and the for the status inconsistency of the FR LED is alarm occurs during start-up, the BTS will The BTS continues itscommunication operation with the the restriction of RP1 onlyold to 7115 BASE STATION INFORMATION not go onAir as long as the alarm is active. file. SW management procedures in case of an SW mismatch situation. Therefore, there is When btsSyncMode is PhaseSync, the no possibility to align the RF LED and BTS alarm is canceled during start-up. When the SM display status. The LED BTS continues withminutes, the old 7115 BASE STATION INFORMATION alarm is present for operations more than five software. the BTS is reset.

If the SW download to any HW unit failed, the SBTS continues operating with the currently running SW version.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT

If the SW activation failed on FCT, the SBTS If the SW download to any HW unit failed, 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT continues operating with the currently the SBTS continues operating with the running SW version. currently running SW version. If the SW activation failed on another HW If the SW activation failed on FCT, the SBTS The battery backup is partly or unit (for example, RFunit unit), the following continues operating with the currently completely in use. The intelligent shutdown events will happen: running SW version. operation has started. If the main power is not restored, cells,and sectors, and with carriers 1. The SBTS the restarts operates the If the SW activation failed on another HW are shut down according to the predefined new SW version installed. The BTSexample, does notRF send faults, are unit (for unit), the which following parameters. related to the blocked module, to the events will happen: 2. Eventually, if the SBTS is integrated to network management system (NMS). The the NetAct, after the automatic recovery SW fault-sending to the BTS 1. The SBTS restarts andElement operatesManager with the update, the SBTS restarts and operates is always enabled. The fault cancellations new SW version installed. The BTS does send installed. any faults that are with the old SWnot version are always sent to the NMS. related to the blocked cell, or the modules 2. Eventually, ifto the SBTS is integrated commissioned the blocked cell, to theto It is NetAct, not possible to establish phone calls SW the after the automatic recovery network management system (NMS). Faultthrough blocked module. Inoperates the case of update, the SBTS restarts and sending to the BTS Element Manager is The BTS does send installed. any faults, dual mode configuration, thatother is, radio with the old SWnot version always enabled. The fault cancellations are other than transport faults,between to the network module CPRI/Ir is shared LTE BTS always sent to the NMS. management system when themodule BTS and SCDMA BTS, the(NMS) blocking radio is blocked. TheBTS faultSite cancellations are sent from both LTE Manager and Calls through the blocked cell are to the NMS. SCDMA BTS (BTS OAM SM system isOMS/NetAct) needed to shut The operator andNew is transferred to another cell. calls cannot down the transmission from the radio informed about through the autonomously-triggered be established the blocked cell. All cells are disabled. module. recovery reset. FCT is the fault source: BTS startup is terminated. FSP, DSP or ABIx is the fault source: FSP or ABIx is not taken into use.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION7995 MAINS BREAK

7102 BASE STATION RESOURCE BLOCKED BY USER

7102 BASE STATION RESOURCE BLOCKED BY USER

7102 BASE STATION RESOURCE BLOCKED BY USER

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT

Default values are used for the cell. The cell 7112 BASE STATION CONFIGURATION PROBLEM operation might become degraded.

Depending on the reported severity, the 7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO BTS capacity might have decreased, or the BTS might be not operational at all. Depending on the reported severity, the BTS capacity might have decreased or the BTS might be not operational at all. For resources that are not in use (not 1. The gain control feature is lost, possibly commissioned), lack of support is reported generating an interference in the network. by minor severity alarm (BASE STATION NOTIFICATION). 2. The NBAP common measurement message is incorrect because of missing If the source is DSP, then the cell supported measurement data from the Radio Module. by the DSP might be degraded or disabled. If the source is Rx/Tx, then possibly some 3. The cell supported by the radio module, carriers weren't configured. which is visible as alarm source in the After cell blockorrequest, RNC should alarm,the is disabled degraded. start handover from the blocked cell to other cells because NodeB did not receive response from RNC. Handing traffic over to another cell might not work. The cell, which The cell is disabled. should be blocked, might still be operational.

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

7115 BASE STATION INFORMATION

7114 CELL SERVICE PROBLEM

The cell setup is rejected.

7115 BASE STATION INFORMATION

The cell supported by radio module, which is visible as alarm source in the alarm, is disabled or degraded.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

The minimum HSUPA capacity, which is 7115 BASE STATION INFORMATION based on the commissioning parameters, is not fully guaranteed. The HSUPA resource handling still works dynamically in addition to the partially reserved minimum capacity Cell capacity is decreased. 7116 BASE STATION SERVICE PROBLEM for the HSUPA.

Cell capacity is decreased.

7116 BASE STATION SERVICE PROBLEM

Some baseband processing resources are not working, a cell or cells are not operational, or the BTS is not operational.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

BTS HSUPA Capability is degraded in the cell where the Parallel Interference Cancellation (PIC) feature is active.

7116 BASE STATION SERVICE PROBLEM

BTS HSUPA Capability is degraded in the cell where the Parallel Interference Cancellation (PIC) feature is active.

7116 BASE STATION SERVICE PROBLEM

The WCDMA RAT capacity might decrease, 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE or the WCDMA RAT might go completely out of order.

Cells cannot be set up, or there is no impact 7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO to cell operation if the fault is triggered runtime. Not enough CCCH Processing Set licenses 7115 BASE STATION INFORMATION commissioned to the cell. Affected cells are disabled.

DSP is not operational, and cells supported 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE by the DSP are disabled.

The cell is temporarily degraded, and all 7114 CELL SERVICE PROBLEM connected UEs are informed of the status of the cell. All ongoing calls are unaffected, but the UE is unable to establish new calls. Some end-users will not experience the 7115 BASE STATION INFORMATION improvement in the uplink due to HS-RACH.

During HSDPA cell setup:

7115 BASE STATION INFORMATION

Operator can still use the carrier aggregation functionality. However, HSDPA cell setup is rejected. Operator can still use the carrier 7115 BASE STATION INFORMATION aggregation functionality. However, new During carrier aggregation runtime carrier aggregation group ID is not taken activation: into account. Cell visible as alarm disabled. Operator cannot usesource carrier is aggregation functionality due to a wrong carrier aggregation configuration.

7112 BASE STATION CONFIGURATION PROBLEM

The BTS memory operations (for example, the software download and parameter updates) are not stable. The In Service Time Indicator (ISTI) value The BTS memory operations (for example, for HW Repair Center might not be correct the software download and parameter or readable. updates) are not stable. The In Service Time Indicator (ISTI) value The BTS capacity decreases. The digital for HW Repair Center might not be correct signal processing (DSP) does not work or readable. correctly.

7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT

7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The BTS capacity decreases, or the BTS is 7100 BASE STATION HARDWARE PROBLEM7101 BASE STATION/UNIT AUTO not operational. The digital signal processing (DSP) does not work correctly.

The BTS is not operational, or its capacity is 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE degraded.

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

There is no actual effect to the BTS functionality: this is user-specific.

7103 BASE STATION EXTERNAL ALARM NOTIFICATION

The BTS is not operational.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7111 BASE

Some action inside the BTS is interrupted. The BTS does not operate normally. The fault is in the unit reported in the fault source field.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The BTS capacity possibly decreases. The cell with the incorrect configuration is not working.

7112 BASE STATION CONFIGURATION PROBLEM

This fault prevents the BTS from functioning. Depending on , some processing resources, some cells, or the entire BTS is out of order.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

This fault can prevent the BTS from functioning when the RF Module is needed for the required cell configuration.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

If other references are available, the synchronization reference source changes to another source. Tuning then follows this new reference.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7108 BASE

The system clock frequency starts drifting, If other references are not available, the and the air interface frequency accuracy BTS master clock (OCXO) tuning is halted, starts to degrade. The BTS might work and the BTS synchronization drops to properly for a few days without an external holdover mode. reference, but the network performance The BTS can operate properly for months, might start to decrease gradually. or even a year, beingisinavailable, the 5% the If no other valid when reference margin area,mode but eventually thenormal DAC value BTS tuning moves from to reaches adjustment limitpossible (0 or 4095), holdover.the If holdover is not because and the OCXOdata, cannot follow error the in of insufficient or phase The BTS is not operational. synchronization reference signal beyond holdover exceeds 3 us, then the cells arethe limit. When the DAC value is 0 or 4095, the deactivated. effect depends on the network synchronization setting defined in the BTS The BTS is not commissioned or integrated commissioning. to the network. The BTS cannot be accessed or configured remotely. Effects in FDD Frequency Synchronization mode:

7100 BASE STATION HARDWARE PROBLEM

7108 BASE STATION SYNCHRONIZATION PROBLEM

7100 BASE STATION HARDWARE PROBLEM

7112 BASE STATION CONFIGURATION PROBLEM

The MHA is degraded and the RX signal 7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM Assuming the BTS reference level mightthat be decreased. The sizesignal of thehas the accuracy when the DAC value cell correct might be reduced. reaches the adjustment limit of 0 or 4095 (meaning the alarm indication is real and not The MHA faulty, and the RX performance caused byisan incorrect reference), the BTS 7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM might be degraded. The size of the cell air interface starts to drift from the correct might reduced. value, be and after a while (weeks or months), the 3GPP accuracy limit is not met anymore. Even the BTS might 7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM The antenna lineinisthat notstage, operating correctly. still be operational, but the system The cell capacity might be decreased. performance might drop, affecting, for example, the handovers. TXs thatingo through affected antenna Effects FDD Phasethe Synchronization line are disabled. mode:

7113 BASE STATION ANTENNA LINE PROBLEM

The following will happen as a the result: When the DAC value reaches adjustment limit of 0 or 4095, the basic LTE 7113 BASE STATION ANTENNA LINE PROBLEM The output power at the antenna is 1. The cell that has lost itsare only TX, or hasin system operation effects the same decreased because of the reflection of as the no primary TX available, is disabled. Frequency mode, but the signal in theSynchronization TX path. The antenna is not LTE features, which require Phase working optimally. The size of the cell might 2. The cell that still has itsnon-operational primary TX Synchronization become be reduced. The operating performance of the RX path 7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT available, butOCXO has lost its secondary TX, is because the cannot adjust the phase is decreased. degraded. Such anymore. cell also loses its MIMO or synchronization VAM capability.

3. The radiopath module becomesThe degraded. The signal is unusable. cells using 7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT the faulty unit might not work. Note: For CPRI-A radios, the antenna line is not disabled when the Major VSWR alarm is reported. These radios have internal protection mechanisms, so the VSWR alarm does not indicate imminent harm to the hardware. The TX for the antenna line is marked as degraded, and the associated cell remains on air.

The signal path is unusable. The cells using 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE the faulty unit might not work.

The BTS capacity might be decreased.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The BTS capacity might be decreased.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The BTS capacity might be decreased.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The BTS capacity might be decreased.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The BTS capacity might be decreased.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The antenna line device does not work properly. The cell operation is degraded.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The device is out of use.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The unit might be started with an old SW version and is, therefore, not compatible with any other units.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM

Secondary core startup is halted.

7108 BASE STATION SYNCHRONIZATION PROBLEM

The BTS capacity drops. The cell is not operational.

7114 CELL SERVICE PROBLEM

The gain of the MHA might be decreased. The cell performance might also be decreased. The real level of gain provided by the MHA cannot be determined.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

The MHA does not provide gain in the RX path. The cell performance might be decreased. Within the recovery action, the missing gain is compensated by the additional gain delivered by the LNA in the Some antenna line device functions might Radio Module. not work properly.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

Some antenna line device functions might not work properly.

7115 BASE STATION INFORMATION

Some antenna line device functions might not work properly.

7115 BASE STATION INFORMATION

Some antenna line device functions might not work properly.

7115 BASE STATION INFORMATION

The antenna line device is out of use.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

Default values for the internal delays in the BB card are used. The effects on functionality include: 1. Cell boundaries cannot be defined as accurately as with measured internal delay If other references are available, the values. synchronization reference source changes 2. 3GPP Dedicated measurement (RTT to another source; the tuning follows this measurement) accuracy is lower than with new reference. measured internal delay values. If other references are available, the If other references are not available, tuning synchronization reference source changes does not follow the external reference any to another source. Tuning then follows this more. Clock tuning is halted, and the BTS new reference. continues its operation based on the internal Calls are not possible through the affected oven oscillator. If other references are not available, the cells (BASE STATION SERVICE BTS master clock (OCXO) tuning is halted, PROBLEM). If the FCM [FSMr3: FCT] is approaching the and the BTS synchronization drops to end of its lifetime but the reference holdover mode. There might problems in the calls frequency is be still correct, the BTS Calls are not possible through theand affected through the affected cells (BASE STATION system performance might be normal for cells. SERVICE months, orPROBLEM). even one year, after the alarm activation (provided that the DAC is not at There is no on the system the edge of impact the adjustment area). (BASE The RF Module is configured using defaults, STATION NOTIFICATION). and the performance is not as expected.

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7108 BASE STATION SYNCHRONIZATION PROBLEM7115 BASE STATION IN

7108 BASE STATION SYNCHRONIZATION PROBLEM7115 BASE STATION IN

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7111 BASE

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT

Calls are not possible through the affected cells. There might be problems in the calls through the affected cells.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

Calls are not possible through the affected cells. There might be problems in the calls through the affected cells.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

There is no impact on the system. Calls are not possible through the affected cells (7116 BASE STATION SERVICE PROBLEM).

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

There can be problems in calls through the There might be problems in the phone calls 7116 BASE STATION SERVICE PROBLEM affected cells (7116 BASE STATION through the affected cells, or calls might not SERVICE PROBLEM). be possible. There is no impact on the system (7115 Calls not possible through the affected BASEare STATION NOTIFICATION). cells.

7100 BASE STATION HARDWARE PROBLEM7101 BASE STATION/UNIT AUTO

The TX and/or RX performance of the cell 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE might be degraded because of the failure, or calls are not possible through the affected cells. Calls are not possible through the affected cells.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

Calls are not possible through the affected 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE cells. Problems might occur in calls through the affected cells. The TX/RX paths of the RF module are out of order, and phone calls through the affected cells are not possible.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The TX part is out of power, and calls are not possible through the affected cells.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

There can be problems in the calls through the affected cells.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

There might be problems with calls made through the affected cells.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

This fault should cancel itself. Heating of the 7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM module is ongoing. During RF startup, the affected cell resources are not reported to RROM. The RF Module configuration might fail and cause another fault, and there can be problems in the calls through the affected cells on the alarming device.

7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT

The default configuration is used, and the 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT TX and/or RX performance of the cell is degraded. There might be problems in the calls through the affected cells on the alarming device. The TX and/or RX performance of the cell 7100 BASE STATION HARDWARE PROBLEM7101 BASE STATION/UNIT AUTO might be degraded because of the failure, or calls are not possible through the affected cells on the alarming device.

The communication between the System 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE Module and RF module might be corrupted. Calls are not possible through the affected cells.

The TX power level is decreased, and there 7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM might be problems with phone calls through the affected cells. There might be problems in calls through the affected cells.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT

It is not possible to establish phone calls through the blocked FR.

7102 BASE STATION RESOURCE BLOCKED BY USER7115 BASE STATION IN

The BTS does not send faults that are related to the blocked Flexi Radio module The fault might mean that fans are not 7116 BASE STATION SERVICE PROBLEM (FR) to the Network Management System connected and/or working. This might cause (NMS). Fault sending to BTS Element the RF module to overheat. Manager is always enabled. Fault cancelations are always sent to the NMS The fault can only be automatically canceled If theBTS fansElement do not rotate as required, the 7116 BASE STATION SERVICE PROBLEM and Manager. for RF modules where fans are detected temperature of the module might rise too based on speed response (FRM3.x, FRGT high. from version 102, and FRGS from version X21). All other RF modules require a reset. If the fans do not rotate as required, the 7115 BASE STATION INFORMATION module temperature might rise too high.

Calls are not possible through the affected cells. The Fujitsu radio will reset itself when a critical fault is detected. However, the radio is not enabled upon start-up if the condition persists. Once the condition is cleared, the radio is enabled again.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

There might be problems with calls made through the affected cells.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

Calls and data transmissions are possible with degraded quality and lower bandwidth because of increased bit error rate on the optical connection.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

Calls and data transmissions are not possible through the affected cells.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

A cell that uses the resources of the FR module that has raised the fault is disabled or degraded (depending on the amount and type of Tx/Rx resources lost - see also Reported Alarms Description). The Flexi BTS unit in question is transmitting or receiving data with degraded Downlink signal transmission on the given performance. The fault does not trigger antenna line is disabled and the special actions in the BTS. corresponding FR transmitter is unusable. Cell performance might be degraded. The overall FR module state is not affected since the fault is caused by an external phenomena on the antenna line (that is, an extremely high VSWR through level). RF and its Calls are not possible theHW affected subsystems are not affected by the fault, cells, or cell performance is degraded. but some functions of FR module (for example, transmitter on the alarming antenna line) cannot be used as long as the fault remains The External Alarm and Control lines of the active. Radio Module might not be working correctly.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

Calls are not possible through the affected cells.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

Downlink signal transmission on the given antenna line is disabled, and the The TX or RX paths of the RF module are corresponding FR transmitter is unusable. out of order, and calls through the affected Hence, the overall FR state is affected. cells are not possible.

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

7115 BASE STATION INFORMATION

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

There can be problems with calls through the affected cells.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

Calls are not possible through the affected cells (7653 CELL FAULTY). Problems might occur in calls through the affected cells (7654 CELL OPERATION DEGRADED).

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

If no other RX-related alarm is reported, RX resources of Receive Diversity Expansion Module (RDEM) do not work optimally. If other RX-related alarm is reported, RX resources of RDEM do not work. If no other TX or RX related alarms on the same radio module are reported, cells supported on this radio module are still operational. If other TX or RX related alarms on the This alarm indicates that technicians are same radio module are reported, cells accessing connectors for debugging or supported on this radio module are monitoring purpose. Alternatively, this would degraded or faulty. Check the other alarms be a warning that there is an unauthorized to know the cells state. intrusion to the Radio Module. If no other TX or RX related alarms on the same radio module are reported, the cells supported on this radio module are still operational.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

Cells assigned to this RFM remain disabled If other TX or RX related alarms on the or degraded until the fault is corrected. same radio module are reported, the cells supported on this radio module are degraded or faulty. Check the other alarms There is the no impact of the fault on services to know cell's state. provided by the BTS if the fault is reported alone. If other faults are reported at the same time, this fault might be their root cause. There is no impact of the fault on services provided by the BTS if the fault is reported alone. If other faults are reported at the same time, the fault might be their root cause. There is a potential for degradation in the Rx path. If the PIM cancellation algorithm is running, it will attempt to remove the detected PIM.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The traffic between the system module and the connected radio module is interrupted. The cell operation is faulty.

7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT

The traffic between the baseband module The traffic between the system module and (for example, FBBC) and the connected the connected radio module is interrupted. radio module is interrupted. The cell The cell operation is faulty. operation is faulty. The traffic between the baseband module The cells of the RF Module behind the (for example, FBBC) and the connected broken connection are not operational; the radio module is interrupted. The cell RF Module cannot be used. operation is faulty. The cell operation is degraded. The optical interface loses its synchronization if the amount of errors exceeds the defined limit.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

The baseband bus RP3 traffic to the RF Module is not working; cell operation is degraded.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

The baseband bus RP3 traffic to the RF Module is not working; cell operation is degraded.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

There is possibly no immediate effect on the 7115 BASE STATION INFORMATION BTS operation, but it might cause an optical interface alarm.

The connection to the associated link is lost. 7100 BASE STATION HARDWARE PROBLEM7101 BASE STATION/UNIT AUTO The data is partially or completely lost. The worst-case fault effect can expand further from the cell level.

Data traffic to the connected RF module is 7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT This fault can prevent BTS operation when malfunctioning. The BTS operation is faulty. the RF module is needed for the required cell configuration. The RP3 traffic from thefor baseband is fault is visible only the first radio in malfunctioning. system or FRs the chain. Fault The 10 sends formodule the other FBBx/ABIx module operation when pooling breaks becauseisofdegraded. the lost sync.

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

The baseband bus RP3 traffic to the system 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE module behind the alarming link is not working. Cells supported by this unit are degraded or disabled (depends on configuration). Baseband bus RP3/RP3-01 traffic might 7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM work incorrectly. The cell operation is degraded. A software update is needed.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT

The BTS operation is degraded because some of the BTS resources are not available.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The BTS operation is degraded because some of the BTS resources are not available.

7115 BASE STATION INFORMATION

The BTS operation is degraded because some of the BTS resources are not available.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

The BTS operation is degraded because some of the resources of the BTS are unavailable.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

This BTS is Out of Order since reliable 7100 BASE STATION HARDWARE PROBLEM7101 BASE STATION/UNIT AUTO message communication cannot be granted.

Some baseband processing resources are not working. A cell (or cells) are not operational, or the BTS is not operational.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

Some baseband processing resources are not working. A cell (or cells) is not operational, or the BTS is not operational.

7100 BASE STATION HARDWARE PROBLEM

The BTS is out of order because of malfunctioning sRIO communication.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

The cell might enter "sleeping" mode.

7116 BASE STATION SERVICE PROBLEM

When all the TRXes of the sector are faulty, 7116 BASE STATION SERVICE PROBLEM the sector reported as alarm source is disabled. When a few of the TRXes of the sector are faulty, the sector capacity is degraded. When all the TRXes of the sector are faulty, 7114 CELL SERVICE PROBLEM the sector reported as alarm source is disabled. When only few of the TRXes of the sector When all the channel groups of the cell are 7112 BASE STATION CONFIGURATION PROBLEM are faulty, the sector capacity is degraded. faulty, the cell is disabled. When this fault is reported on all the channel groups of the cell due to mismatch on channel and path, but not all the channel groups are faulty, Capacity of sector supported by antenna 7116 BASE STATION SERVICE PROBLEM then the cell capacity is degraded. line instance reported in alarm is degraded.

If the TX power pooling feature license is 7115 BASE STATION INFORMATION not enabled from BSC, the feature will not work. Few TRXs will not be on-air as enough RF resources will not be available, thus reducing the capacity. If OMU signaling link could not be 7107 BASE STATION CONNECTIVITY PROBLEM7115 BASE STATION INFOR established during the startup, then no configuration data would be received by BTS, and hence, the alarm source is disabled. If OMU signaling link is broken during runtime, then management interface towards BSC is not available, and hence, no OAM operation can be triggered from BSC.

BCF state is set as Out of order when configuration is rejected, or timeout is seen in the configuration during startup.

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

Base station is out of order and cannot provide any service.

7112 BASE STATION CONFIGURATION PROBLEM

The newly added TRX will remain out of service.

7112 BASE STATION CONFIGURATION PROBLEM

No impact on the working of the SBTS, and 7115 BASE STATION INFORMATION the operator shall refer to the BCF ID configured at BSC. Loss of receiver sensitivity, which results in reduced range, increases dropped calls, and/or reduces uplink RF performance.

7113 BASE STATION ANTENNA LINE PROBLEM

The PIM Cancellation feature is not activated at the RMOD.

7115 BASE STATION INFORMATION

The BTS capacity might have decreased.

7115 BASE STATION INFORMATION

The effect depends on the case when the fault is detected. See the "Meaning" field.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

Any attempt by the operator to configure modes other than the single TX mode for the cell is unsuccessful.

7115 BASE STATION INFORMATION

The cells remain down.

7112 BASE STATION CONFIGURATION PROBLEM

The fault has no direct impact on the operation.

7115 BASE STATION INFORMATION

The BTS resources have decreased, or the 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE BTS is faulty.

The BTS operation is degraded, the cell 7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM operation is degraded or out of order, or the BTS is not operational (FCT/all FSPs and FBB are faulty). Depending on the reported alarm, the fault situation might not have an impact on the operation, the BTS capacity might have decreased, or the BTS might not be operational at all. The BTS is not commissioned.

7100 BASE STATION HARDWARE PROBLEM7103 BASE STATION EXTERNA

BTS startup is interrupted, and the BTS is out of order.

7112 BASE STATION CONFIGURATION PROBLEM

7115 BASE STATION INFORMATION

This fault can prevent the BTS from 7112 BASE STATION CONFIGURATION PROBLEM functioning when the radio unit is needed for the required cell configuration. The signal path is not usable. The cells using the faulty unit might not work.

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

This cell-specific fault does not prevent the cell configuration. It is for informative purposes only.

7115 BASE STATION INFORMATION

The antenna line is not operating correctly. The cell is disabled.

7113 BASE STATION ANTENNA LINE PROBLEM

The antenna line is not operating correctly. The cell capacity decreases.

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

There is no immediate effect on cell operation. The device continues operation with the previously used data.

7115 BASE STATION INFORMATION

There is no immediate effect on cell operation. The device continues operation with the previously used data.

7115 BASE STATION INFORMATION

The affected unit is not operational. In case 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE of an FSP fault, the channel capacity is lost and cell(s) become unavailable. The associated cells in the Radio Module become faulty.

The radio module cannot be used.

7115 BASE STATION INFORMATION

The ALD interface is not operating correctly. 7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM Communication with TILT devices is not possible.

Cells are not activated. It relates to cells that 7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO were going to use the radio unit connected to the system module through the faulty fiber optic cable. Fan control is not optimized. The effect to noise or temperature level is marginal.

7115 BASE STATION INFORMATION

The Radio Module connected to this OptIF is not started.

7112 BASE STATION CONFIGURATION PROBLEM

The FSP/ABIx resource is shut down, and the BTS operation is degraded or faulty.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

The FCT (HW rel.3), FCT (HW rel.4), and possibly other FSPs/ABIx's that are not If the fans do not rotate as requested, the alarming are kept powered. module temperature might rise too high.

7115 BASE STATION INFORMATION

The source unit has an inconsistent SW version.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM

The source unit has an inconsistent SW version.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM

The source unit has an inconsistent SW version.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM

1. Save to file the cause of the SW fallback on request.

7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM

2. Mount the passive file system, and thus, read the cause of the SW fallback on The cell is disabled (the downlink carrier request from the file. that transmits PSS/SSS signals has failed). The cell is degraded (the downlink carrier that transmits PSS/SSS signals is working).

7115 BASE STATION INFORMATION

The ongoing BTS reset lasts longer.

7115 BASE STATION INFORMATION

The cell or BTS is not operational or is degraded.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The radio module is powered off. Therefore, 7115 BASE STATION INFORMATION calls and data transfers cannot be served by that module. 1. Other than sync hub configuration, the master system module works properly.

7115 BASE STATION INFORMATION

2. In sync hub configuration, detection of the peer system module is still possible through The system module is out of order, and the 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7108 BASE the shared radio, or the shared radio BTS is out of order. module might be lost and the cell that supports the radio module might be down. The fault has no direct impact on the operation.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The fault has no direct impact on the operation.

7115 BASE STATION INFORMATION

The fault has no direct impact on the operation.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The fault has no direct impact on the operation.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

The fault has no direct impact on the operation.

7115 BASE STATION INFORMATION

The DC voltage is disabled on the reporting 7115 BASE STATION INFORMATION antenna line.

The HDLC link will be disabled on the reporting Antenna Line or IUANT port.

7115 BASE STATION INFORMATION

If the problem has been detected during SW 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT activation, the SW activation and consequent reset are aborted. If the problem has been detected during 1. If one of the commissioned BTS 7108 BASE STATION SYNCHRONIZATION PROBLEM start-up, the BTS remains out of order. The synchronization sources is ToP, a start-up is customer should request both a rollback to continued without a reference clock, but the the previous SW and another SW download. BTS does not go to OnAir. The start-up procedure stops, and no cells 2. If ToP is not commissioned as a BTS are set up. synchronization source (it means only PPS is commissioned as sync source) then:

7108 BASE STATION SYNCHRONIZATION PROBLEM

The log filethe from a particular unitslave is notand 7115 BASE STATION INFORMATION 2.a. When BTS is sync hub included in theisBTS snapshot. radio sharing enabled, start-up is stopped.

2.b. When the BTS is a part of CRAN cluster, start-up is continued without The radio unit connected to port 3 ora4 of 7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM reference clock, but the BTS does not go the FBBC card cannot provide services toto OnAir. the cells, and the cells are degraded or not operational. 2.c. Otherwise, start-up is continued in The BTS issync operational. frequency mode, and BTS goes to OnAir. Features requiring phase synchronization (for example, OTDOA, eICIC, MBMS, inter-eNB Carrier Aggregation) deactivated. When the faultare is detected during startup,

7115 BASE STATION INFORMATION

7112 BASE STATION CONFIGURATION PROBLEM

the BTS is not operational. When the fault is detected during runtime, the requested new transport configuration is not applied. If another synchronization source is available, the BTS starts to use that for the BTS reference, then there are no effects to the BTS air interface accuracy. The BTS can continue normal operation. Cells assigned to shared radio module are working, but their capacity might be affected If there are no other synchronization because the slave system module working sources available, the external GPS or as temporary master cannot GNSS receiver module continues providing configure antenna line devices (for example, Thereference antenna line device is The out of use. has the for the BTS. receiver MHAs and RETs). a high-performance oscillator, and therefore, the BTS air interface accuracy (both phase Additionally, antenna line device alarms are and frequency) can be maintained up to 24 not visible for the slave (for hours. Eventually, because of the phase The antenna line alarms). device is not operating example, VSWR drifting, the phase deviation is considered to correctly. reach the threshold value, and then the Alarm Base Station Notification due to fault features requiring phase synchronization 4110 (Peer System module connection lost) become non-operational. After that, the is reportedslave together withmodule this fault. The cannot use basicradio system issystem still fully operational the shared the radio until the radio master (excluding above-mentioned features) system is available. becausemodule the frequency accuracy in the air interface is still within the required limits: typically over several months.

7108 BASE STATION SYNCHRONIZATION PROBLEM7115 BASE STATION IN

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

Calls are not possible through the affected cells.

7115 BASE STATION INFORMATION

The cell is out of order.

7114 CELL SERVICE PROBLEM

The NE is in service, but features that use SRIO connection (for example, Inter-eNB Carrier Aggregation) do not work.

7115 BASE STATION INFORMATION

The NE is in service but the features that use SRIO connection (for example, IntereNB Carrier Aggregation) do not work.

7112 BASE STATION CONFIGURATION PROBLEM

Software download has failed and must be retried.

7115 BASE STATION INFORMATION

Software download has failed and must be retried.

7115 BASE STATION INFORMATION

The unsigned release has been successfully downloaded, but no signature verification is possible for the release. If it is downloaded without activation, the unsigned SW build is only downloaded to a passive file system, Software download has failed and must be and the previous SW build is still used. If it retried. is downloaded with activation after a BTS reset, the new downloaded unsigned SW build is used. The MHA does not provide gain in RX path. The cell performance might be decreased. Within the recovery action, missing gain is compensated by additional gain delivered by the LNA in the Radio Module. FR functions that are not critical for cell setup cannot be used.

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7113 BASE STATION ANTENNA LINE PROBLEM7115 BASE STATION INFORM

7115 BASE STATION INFORMATION

CRAN functionality between connected 7115 BASE STATION INFORMATION BTSs cannot be established. Helper-cell RX data cannot be used in processing of the IQ data streams resulting in non-maximal RX gain. BTSs connected in the CRAN cluster cannot 7107 BASE STATION CONNECTIVITY PROBLEM exchange the helper-cell customer data anymore. CRAN functionality is still provided, but RX gain is reduced.

The radio module resources cannot be used by the BTS SW because of unknown RF hardware capabilities (missing hardware properties for the given RFM product). The radio module cannot be recognized and The effect depends on the case when the properly configured by the BTS software. fault was detected: - If the diagnostic information is "IQ compression or forced link speed incorrect in site configuration file", the BTS startup SBTS is limited with HSDPA users. procedure is terminated and cells are not enabled. After maximum number of HSDPA users is - If the diagnostic information is "Number of reached, then no more users will be allowed detected RET units in multiRET is to use HSDPA. SBTS is limitedwith withsite HSUPA users. file", or not consistent configuration its equivalent for RAE, the operator is only After maximum number of HSUPA users informed that not all commissioned ALD is reached, then no more users will be allowed devices are detected. to use is HSUPA. There no other effect. The number of LTE data users is limited to the value pointed by the "LteUsers" parameter. After the maximum number of LTE data users is reached, then no more users will be allowed to use LTE service. Customer IP traffic is limited. The level of traffic decreases by 5%-6% every seven days after the missing licenses have been detected. A new alarm is raised If BTS doesn't succeed to switch over to when the level changes. another time source alarms: - if there was no time source from the beggining logs and all reports have an incorrect time, If other references are available and - else difference of BTS time and logs and configured, then the synchronization all reports time increase. reference source changes to another source. Tuning then follows this new reference. If other references are available and configured, then the synchronization reference source changes to another If other references are not available, the source. Tuning then follows this new BTS master clock (OCXO) tuning is halted reference. If other references and and in phase mode,are theavailable BTS configured, then drops the synchronization synchronization to holdover mode. reference source changes to another If other references are not available, the source. Tuning then follows this new BTS master clock (OCXO) tuning is halted. reference. The micro DTX functionality (LTE1891) is not activated on the antenna line. If other references are not available, the BTS master clock (OCXO) tuning is halted.

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

7110 BASE STATION LICENSE LIMITATION

7110 BASE STATION LICENSE LIMITATION

7110 BASE STATION LICENSE LIMITATION

7110 BASE STATION LICENSE LIMITATION

7115 BASE STATION INFORMATION

7108 BASE STATION SYNCHRONIZATION PROBLEM7115 BASE STATION IN

7108 BASE STATION SYNCHRONIZATION PROBLEM7115 BASE STATION IN

7108 BASE STATION SYNCHRONIZATION PROBLEM7115 BASE STATION IN

7115 BASE STATION INFORMATION

The inter-eNB carrier aggregation cannot be 7112 BASE STATION CONFIGURATION PROBLEM set up. The BTS starts up without activating the inter-eNB carrier aggregation.

The micro DTX functionality is not successfully activated or deactivated in a radio module.

7115 BASE STATION INFORMATION

The transmission to the RF module at 6 7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT Gbps is lost. Data is not transmitted from or to the RF module at all, or is transmitted at a lower speed (3 Gbps). The cells supported by the faulty link are The transmission to the RF module at 3 7100 BASE STATION HARDWARE PROBLEM7115 BASE STATION INFORMAT disabled, or the cell operability is degraded. Gbps is lost. Data is not transmitted from or to the RF module at all. The cells supported by the faulty link are disabled, or the cell operability is degraded. BTSs or FSP cards connected in the CRAN 7115 BASE STATION INFORMATION cluster cannot exchange the helper-cell customer data. CRAN functionality is still provided, but RX gain is reduced. The fault has no direct impact on the current 7115 BASE STATION INFORMATION operation (BASE STATION NOTIFICATION). The fault situation has no immediate effect. Operation of the cells supported by the radio module might be impacted if memory consumption continues to increase.

7115 BASE STATION INFORMATION

Correct operation of the radio module is not 7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM guaranteed. Operation of the cells supported by the radio module are impacted. The radio module can crash at any moment. Too low RTWP value means the value of Rx 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE signal processed inside the BTS is too low; the Rx carrier is disabled; the cell using the faulty Rx carrier is degraded or faulty. FCT/ABIx performance is degraded.

7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM

Collisions with synchronization/GPS signal might happen. FSP (ABIx) startup is terminated. The FSP (ABIx) is not operational.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

Info Model exchange cannot proceed.

7115 BASE STATION INFORMATION

The eNB starts to reject incoming calls except for a few exceptions including Handovers, re-establishments, emergency calls, high priority calls, etc.

7110 BASE STATION LICENSE LIMITATION

The newly downloaded configuration plan overwrites the previously downloaded configuration plan.

7115 BASE STATION INFORMATION

If a non-critical sub-unit is unavailable (lost), 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE cells supported by the faulty sub-unit are not operational. If a critical sub-unit is unavailable (lost), cells supported by the FSP are not operational. Because of the limited optical interface 7115 BASE STATION INFORMATION capacity, not all cell configurations are supported by the impacted radio. Capability of SBTS for WCDMA support is 7110 BASE STATION LICENSE LIMITATION reduced due to the number of R99 Channel Elements limitation.

The secondary core is out of order or 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE removed, or SRIO connection is out of order. All cells supported by the secondary baseband modules connected to secondary unit are disabled. The radio module is powered off. Therefore, 7115 BASE STATION INFORMATION calls or data transfers cannot be served by that module.

Setting up cells on the secondary core fails. 7115 BASE STATION INFORMATION7116 BASE STATION SERVICE PROBLEM All cells supported by the secondary baseband modules connected to the secondary unit are disabled. Connection to fault source peer system module is disabled. Shared radio modules connected to the peer system module will not be used by LTE BTS. Cells configured on the radio modules are disabled. 1. Connection to peer system module where the radio module is connected is disabled. 2. Radio modules connected to the peer system module are disabled, and cells configured on the radio modules are Connection to fault source peer system disabled too. module is disabled. Shared radio modules connected to the peer system module will not be used by LTE BTS. Cells configured on the radio modules are disabled. The cell is out of order if the failed virtual node is used by the cell.

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE

The BTS is out of order if a virtual node failed to start, or the failed virtual node is Used additional frequency might be affected 7115 BASE STATION INFORMATION used by all cells. due to existing overlapping frequency.

PRS transmission is disabled on all cells of 7115 BASE STATION INFORMATION the eNodeB, therefore OTDOA service is disabled. UE requests for inter-frequency RSTD (Reference Signal Time Difference) measurement for inter-frequency OTDOA Because BTS connection to BTS Mediator 7115 BASE STATION INFORMATION can still be supported. Telecom traffic is still and Network Management System (NMS) is supported. lost, the following are not possible: 1) BTS management operations like e.g. configuration activation/upload, BTS SW The source unit has an inconsistent SW 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM download/activation/upload version. 2) alarms and counters reporting from BTS to NMS The RF module could not be on-air, and the 7112 BASE STATION CONFIGURATION PROBLEM affected cell operational state is disabled.

Calls are not possible through the affected cell(s).

7116 BASE STATION SERVICE PROBLEM

1. Configuration Management Connection to the radio module cannot be established. 2. The radio module remains uninitialized and disabled. 3. Cells configured on the radio module are Calls through the blocked TRX are disabled. transferred to another TRX. New calls cannot be established through the blocked TRXes. The BTS does not send any faults to BSC, which are related to the blocked The BTS cannot provide service - startup TRX. cannot proceed. Fault 4399 always makes sector as degraded. If all TRXes of sector are blocked, alarm with fault 49 is reported. High accuracy related GSM features, such as DFCA, will be disabled.

7112 BASE STATION CONFIGURATION PROBLEM7115 BASE STATION INFO

7102 BASE STATION RESOURCE BLOCKED BY USER

7112 BASE STATION CONFIGURATION PROBLEM

7115 BASE STATION INFORMATION

- When all the TRXes of the sector are 7115 BASE STATION INFORMATION faulty, the sector reported as alarm source is disabled. - When a few of the TRXes of the sector are faulty, the sector capacity is degraded. The operating performance of the RX path 7112 BASE STATION CONFIGURATION PROBLEM supported by the Antenna Line reported as fault source is decreased. The fault is raised if a 1xRTT neighbor relation, which is detected by a UE through measurements due to activated ANR features, could not be stored because the maximum number of neighbor relations per cell is already reached.

7115 BASE STATION INFORMATION

A neighbor relation, which has been created 7115 BASE STATION INFORMATION by ANR, is not used because the maximum number of cells that can be configured per frequency object per LTE CELL exceeds the 3GPP limit of max 32 cells, or the O&M UEs are not aware of the omitted MBMS 7115 BASE STATION INFORMATION threshold for maximum number of e1xCSFB SAIs. target cells per frequency (rttMaxNumCsfbTargets). eNB will nevertheless create the LNRELX instance Cellblacklist performance is decreased.mobility type 7114 CELL SERVICE PROBLEM but the corresponding (for example: SRVCC, CSFB). The operator may decide to manually optimize the neighbor relations. In case of U-plane overload, the system initiates actions to decrease the amount of load by limiting the traffic or the functionality on the traffic. The system performance might be degraded The PHICH transmission power is not especially in cases where the U-plane boosted enough, or at all, as compared to overload countermeasures are enabled. the operator's setting. The "Fault ID Name" information field identifies the type of overload detected: operation -Cell TrOne refers is to downgraded. trigger UPOVT1, which is speech quality-based detection on the user plane. - TrTwo refers to trigger UPOVT2, which is quantity-based per TTI on the user Cell operation isdetection downgraded. plane. - TrThree refers to trigger UPOVT3, which is a long delay-based check of PDSCH on the user plane. In case of U-plane overload, the system initiates actions to decrease the amount of load by limiting the traffic or the functionality on the traffic. The system performance might be degraded In case of U-plane overload, the system especially in cases where the U-plane initiates actions to decrease the amount of overload countermeasures are enabled. load by limiting the traffic or the functionality The "Fault ID Name" information field on the traffic. identifies the type of overload detected: The system performance might be degraded For S1: The eNB loses the connection to is S- TrOne refers to trigger UPOVT1, which especially in cases where the U-plane GW. All quality-based calls using thedetection failed GTP-U data speech on the user overload countermeasures are enabled. path plane.are released, and new GTP-U data The "Fault ID Name" information field tunnels nottocreated the failed GTP-U - TrTwo are refers trigger for UPOVT2, which is identifies the type of overload detected: data path until itdetection works again. quantity-based per TTI on the user S1 interface is unavailable. -The TrOne refers to trigger UPOVT1, which is plane. speech quality-based detection on the user -If TrThree to trigger UPOVT3,for which no otherrefers S1 interface is available use,is plane. a long delay-based check of PDSCH on the operation is trigger considered faultywhich and no -BTS TrTwo refers to UPOVT2, is user plane. calls can be setdetection up. quantity-based per TTI on the user The X2 interface is unavailable. Handover of plane. calls to or from cells of the associated If there is refers at least one other S1 interface -adjacent TrThree UPOVT3, which is BTS is to nottrigger possible. Base station available for use, BTS operation is on the a long delay-based check of PDSCH (BTS) operation is considered degraded. considered user plane. degraded but can continue operation (that is, set up calls) using the available S1 interfaces.

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7114 CELL SERVICE PROBLEM

7114 CELL SERVICE PROBLEM

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7107 BASE STATION CONNECTIVITY PROBLEM

7107 BASE STATION CONNECTIVITY PROBLEM

7107 BASE STATION CONNECTIVITY PROBLEM

One of the transport paths (SCTP) in SCTP 7107 BASE STATION CONNECTIVITY PROBLEM connection to the MME has failed. This is only applicable when SCTP multi-homing is supported. An alternate transport path is available to continue operation. The M3 interface is unavailable, and MBMS 7107 BASE STATION CONNECTIVITY PROBLEM service cannot be provided.

One of the transport paths (SCTP) in SCTP 7115 BASE STATION INFORMATION connection to MME (which provides MBMS service) has failed. This is only applicable when SCTP multi-homing is supported. An alternate transport path is available to The BTS is not configured according to the 7112 BASE STATION CONFIGURATION PROBLEM pursue the operation. radio network plan file. The BTS is waiting for the correct radio network configuration file. The cell is disabled.

7114 CELL SERVICE PROBLEM

The cell is disabled.

7114 CELL SERVICE PROBLEM

In the case of subscriber trace activation, if 7115 BASE STATION INFORMATION the failed trace connection was used for sending the trace reports, the BTS considers the trace activation for that subscriber as failed. BTS startup is interrupted, and the BTS is 7112 BASE STATION CONFIGURATION PROBLEM not operational. In the case of cell trace and interface trace, if the failed trace connection was used for sending the trace reports, the BTS does not The session (fortrace subscriber or cell start trace tracing until the connection is or 7115 BASE STATION INFORMATION interface or PCMD report) cannot be established successfully. activated or deactivated. The BTS cannot accept new UEs of a given 7115 BASE STATION INFORMATION RAT type attempting registration in any of the reported misconfigured PLMNs. Such an attempt by new UEs results in call failure at the BTS. The fault has no effect on the base station 7115 BASE STATION INFORMATION operation, but the LNADJ, LNADJL, or both The UEs that might have already registered LNADJ and LNADJL objects have not been in misconfigured PLMNs remain unaffected. stored in the eNB. The fault has no effect on the base station operation, but LNADJW object with the newly-learned WCDMA neighbor cell configuration through ANR-specific measurements was not stored in the eNB.

7115 BASE STATION INFORMATION

The fault has no effect on the base station operation, but LNRELW object with newlylearned WCDMA neighbor relation configuration through ANR-specific measurements was not stored in the eNB. The fault has no effect on the base station operation. The WCDMA neighbor relation, which is reported by a UE because of activated ANR features, has been stored, but at least one of the mobility parameters No handover can be performed to cells with of the LNRELW (csfbPsHoAllowed, the affected PCI and frequency. psHoAllowed, and srvccAllowed) has been set to "forbidden" because it has exceeded the limit. (Refer to the section "Meaning"). If an X2 link is available, no type of handover to the neighbor cell is possible at all. If the UE-based ANR is activated, there will be continuous retries to resolve the ECGI. The handover failure rate for the affected cell might increase.

7115 BASE STATION INFORMATION

The following features are deactivated (if configured to be used):

7115 BASE STATION INFORMATION

- Enhanced Inter-eNB Interference Cancelation The handover failure rate for the affected cell might be increased. - Multimedia Broadcast Multicast Service

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

- Inter-eNB Carrier Aggregation Cells and eNBs remain in service, but 7112 BASE STATION CONFIGURATION PROBLEM features related to "Inter eNB Carrier - Network-Assisted Interference Cancelation Aggregation" that require consistent and Suppression parameters between cluster members are taken out of service. Cells and eNBs remain in service, but 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM7115 BASE STAT features related to "Inter eNB Carrier Aggregation" that require the same SW version between cluster members are taken out of service. Other features related to the "Inter eNB 7107 BASE STATION CONNECTIVITY PROBLEM Carrier Aggregation" feature that require an inter-eNB link are taken out of service. If the maximum number of allowed 7107 BASE STATION CONNECTIVITY PROBLEM neighbor-related objects is reached, the eNB does not allow the creation of additional neighbor-related objects either through O&M or X2 Setup/X2 Configuration The eNB continues normal operation, and 7115 BASE STATION INFORMATION Update. If a measurement report on the automatic neighbor relation handling is not signal power or quality of the neighbor is impacted, that is, neighbor-related objects received, handover preparation is triggered, can be created through O&M or X2 but no new object is created. A result of this Setup/X2 Configuration Update. might be that no X2 link is established with If the number of objects in the database such neighbor, or that the CGI is known for increases further and reaches, or even such BTS. exceeds, the configured value of the parameter "maxNumAnrMoiAllowed", New objects can be stored again when the automatic neighbor-relation functionality is number of neighbor-related objects in the degraded, and an alarm indicating BTS database is below the value of the "Overload detected: max number of parameter "maxNumAnrMoiAllowed". neighbor relation objects reached" is raised.

Inter eNB Carrier Aggregation'-related features requiring cluster-wide phase synchronization are taken out of service in the cluster.

7107 BASE STATION CONNECTIVITY PROBLEM

SRIO cannot be set up and features requiring SRIO link cannot be activated inbetween the eNB and the partner eNB.

7112 BASE STATION CONFIGURATION PROBLEM

BTS is operational but system level (inter7112 BASE STATION CONFIGURATION PROBLEM BTS) carrier aggregation functionality is degraded. Carrier aggregation with the misconfigured carrier aggregation relations is not possible. However, carrier The pool of the resource DSPs is 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE aggregation with the other, properly unavailable; any cell that cannot be put into configured carrier aggregation relations is use because of a lack of available resource working normally. pools will not be available.

The BTS cannot continue to operate. All 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7116 BASE An autonomous reset of an FSP or FSPs (in cells are disabled. the case of spread pool) will be performed unless it will disable any working cell. The cell cannot provide to the User 7112 BASE STATION CONFIGURATION PROBLEM An additional alarm withservice fault 4001 (BTS As long as the number of allowed Equipment (UE). PUSCH masking reset needed) is raised when the recovery autonomous BTS resets has not yet been activation, with automatic PUCCH reset of thetogether autonomous FSPs is not exceeded, an autonomous BTS reset will be configuration for a cell where the PUSCH allowed. performed in an attempt to recover. mask area setting, results in not enough The BTS operates normally, but the number 7115 BASE STATION INFORMATION consecutive uplink resource blocks (UL of active User Equipment (UE) in the cell is RBs) for PRACH allocation. limited to the automatic allocated values coming from the lookup table. The cell cannot provide service to a UE. The 7112 BASE STATION CONFIGURATION PROBLEM activation of ProSe Direct Communication, together with automatic PUCCH configuration, for a cell are such that the configuration of the sidelink transmit The alarm is raised if a 1xRTT neighbor cell, 7115 BASE STATION INFORMATION resource pool overlaps with PUCCH, or which is detected by a UE through results in insufficient consecutive resources measurements due to activated ANR for PRACH allocation. features, could not be stored because the maximum number of instances is already Handovers from or to the cells of the related 7107 BASE STATION CONNECTIVITY PROBLEM reached. adjacent BTS are not possible.

Handovers to cells of the related adjacent BTS are not possible.

7107 BASE STATION CONNECTIVITY PROBLEM

The S1 interface is not available for call setup, and existing calls are released.

7107 BASE STATION CONNECTIVITY PROBLEM

The S1 interface is unavailable, and the BTS is not available for call setup.

7107 BASE STATION CONNECTIVITY PROBLEM

If the update of the TAC or PLMN identities is not successful, the eNB performs S1 setup, which means service loss for the affected cells.

7107 BASE STATION CONNECTIVITY PROBLEM

The System Information for the related 7107 BASE STATION CONNECTIVITY PROBLEM GERAN or UTRAN neighbor cells is not reliable, and will not be provided to the UEs, which are released with redirect. System Information for the related GERAN 7107 BASE STATION CONNECTIVITY PROBLEM or UTRAN neighbor cells is not reliable and will not be provided to UEs, which are released with redirect. Some of the UEs with a complete set of system information of the cell stored that has left the cell, and has come back within three hours, might not recognize that there was a system information change. This fault has no effect on the BTS operation.

7114 CELL SERVICE PROBLEM

There is high memory usage, which might result in memory outage.

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

The cell is disabled, no calls are possible in 7114 CELL SERVICE PROBLEM the cell.

No impact on FSP operation.

7115 BASE STATION INFORMATION

Critical impact on FSP/ABIx operation.

7115 BASE STATION INFORMATION

No critical impact on FSP operation.

7115 BASE STATION INFORMATION

The BTS capacity decreases, or the BTS is 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE not operational. The Digital Signal Processing (DSP) does not work correctly.

The BTS capacity decreases, or the BTS is 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE not operational. The Digital Signal Processing (DSP) does not work correctly.

The BTS capacity decreases, or the BTS is 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE not operational. The Digital Signal Processing (DSP) does not work correctly.

The BTS capacity decreases, or the BTS is 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE not operational. The DSP does not work correctly. The M3 interface is unavailable, and MBMS 7107 BASE STATION CONNECTIVITY PROBLEM service can no longer be provided.

The M3 interface is unavailable, and MBMS 7107 BASE STATION CONNECTIVITY PROBLEM service can no longer be provided.

There are insufficient or no resources for 7112 BASE STATION CONFIGURATION PROBLEM MBMS session broadcasting. Start of MBMS sessions may be suspended by eNB due to lack of resources. The warning is triggered by the eNB if the MME could not be informed about the modified values through the MCE configuration update procedure after several retries. MBMS session is suspended, which might cause interference with other eNBs. The eNB stops all active MBMS sessions and waits for new session requests from the MME if the update of the global MCE ID or 1. If theservice max number of MBMSwas sessions MBMS area identities not per MCE is exceeded, the MCE/eNB responds successful. to MME with MBMS SESSION START FAILURE. A failed update of the MCE name is tolerated by session the eNB.is started in at least one The MBMS 2. If the session is suspended because the but not all affected MBSFN areas. resources are not enough in any MBSFN Nevertheless, MCE/eNB responds with an supporting the requested service area, the MBMS SESSION START RESPONSE MCE/eNB responds to MME with MBMS indicating success. The MBMSSTART session is suspended in at least SESSION RESPONSE indicating one MBSFN areas. success. Nevertheless, MCE/eNB responds with an MBMS SESSION START RESPONSE indicating The communication link between the local success. SBTS and the BFD peer is defective. No communication is possible.

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

61022 BFDGRP-$BFDGRPID down

Possible impact on the connections over this interface: - no calls are possible - loss of remote management access to No data or clock information is exchanged other network elements via this interface. - loss of synchronization if the interface is used as a synchronization source Possible impact on the connections over this interface: The possible effects are the following: - voice calls or data connections are aborted and cannot be established anymore - No calls are possible. - remote management connectivity is lost - There is loss of remote management and cannot be established anymore access to other network elements. The cannot be used - lossinterface of synchronization if the for interface is - IKE SAs and IPsec SAs cannot be transmission. It can be used for connectivity used as a synchronization source established or rekeyed. checks only. on use of the Ethernet - depending interface, the above described impact can occur for the local SBTS and/or The interface cannot be used forother (S)BTS elements if they are chained via the transmission. The laser of the SFP module Ethernet interface cannot be switched on.

61028 LOF on $UNIT, $INTERFACE

61029 LOS on $UNIT, $INTERFACE

61030 Dead Peer Detected

61040 Interface under test on $UNIT, $INTERFACE for $LOOPTIMEOUT minute

7100 BASE STATION HARDWARE PROBLEM

An Ethernet Link cannot be successfully The Certificate Revocation List could not be 7109 BASE STATION SECURITY PROBLEM established since it is down. updated. New revoked certificates No Ethernet data or clock information is remain unknown to the SBTS. exchanged via this interface. Normal is interrupted. Only loopback 7107 BASE STATION CONNECTIVITY PROBLEM Possibletraffic impact on the connections over OAM frames are transmitted and received this interface: over thecalls interface. the test frame - voice or dataIf connections cannot be generator establishedis switched on, test frames are transmitted. -The remote management Ethernet interface connectivity might be outcannot of order, 7107 BASE STATION CONNECTIVITY PROBLEM be established or the remote peer might be out of order. -Traffic loss of synchronization if the interface is might get lost. used as a synchronization source - depending on use of the Ethernet The Ethernet interface is defective, or the 7107 BASE STATION CONNECTIVITY PROBLEM interface, the above described impact can remote peer is defective. Traffic might get occur for the local BTS and/or other BTS lost. elements if they are chained through the Ethernet interface. The SFP is not operational.

7100 BASE STATION HARDWARE PROBLEM

The interface of the SFP module cannot be used for transmission. The laser of the SFP module cannot be Possible impact: 61104 EBER on $UNIT, $INTERFACE switched on. - slow management access to the SBTS and other network elements in the network No data or clock information is exchanged - poor voice quality and data performance through this interface of SFP module. The performance management data 61150 LOMF on $UNIT, $INTERFACE collected on this becomes invalid. The following areinterface the possible impact on the connections over this interface of the SFP module: - Voice calls or data connections cannot be established. - The remote management connectivity cannot be established. - There is loss of synchronization if the interface is used as a synchronization source.

Possible impact on the connections over the 61151 AIS on $UNIT, $INTERFACE interface in question: - no calls are possible - loss of remote management access to other network elements in the RAN Possible impact on the connections over 61152 RDI on $UNIT, $INTERFACE this interface: - no calls are possible - loss of remote management access to The possible impacts are the following: other network elements in the RAN - No calls are possible for the connections over this unit. - There is loss of remote management The possible impact on the connections access to other network elements in the over this interface are: RAN. - The SL-PPP/ML-PPP interface is not available. - Loss of remote management access. The possible impact on the connections over this interface are: - No calls are possible anymore. - Loss of remote management access to other network elements in the RAN. Impact on the connections over this interface:

7100 BASE STATION HARDWARE PROBLEM

61250 IPCP Failure

61251 LCP failure

61252 PPP Interface down

- There is loss of remote management access. The transport connection toward the remote 7107 BASE STATION CONNECTIVITY PROBLEM peer might be defective. Traffic might get lost. The transport connection towards the remote peer may be defective. Traffic may get lost.

7107 BASE STATION CONNECTIVITY PROBLEM

The requested service is not available.

7109 BASE STATION SECURITY PROBLEM

The communication link between the local 61605 BFD-$BFDID down in ingress and the remote peer is defective or the peer is defective. Transport service may not be available and calls may be dropped. The communication link between the SBTS 61606 BFD-$BFDID down in egress and the BFD peer is defective. Transport service may not be available and calls may be dropped. The Ethernet Link got established with an unexpected clock mode or technology. Possible impact on the connections over this interface: - Increased packet delay variation and increased average delay for all voice/packet and management connection - Increase of packet loss due to congestion - Loss of synchronization/Timing source lost with Timing over Packet (IEEE1588v2) due to increased packet delay variation - Loss of synchronization/Timing source lost with Synchronous Ethernet

61607 Auto-negotiation mismatch on $UNIT, $INTERFACE

This alarm is an indication that the backhaul 61610 RTT threshold crossed on TWAMP-$TWAMPID capacity for traffic with the same profile as this TWAMP session (DSCP value, packet size) may be too small, because the measurement packets are scheduled later This alarm is an indication that the backhaul 61611 PLR threshold crossed on TWAMP-$TWAMPID than before. capacity for traffic with the same profile as this TWAMP session (DSCP value, packet size), may be much too small, because some of the measurement packets seem to None 7109 BASE STATION SECURITY PROBLEM have been thrown away. The TWAMP measurement packets are lost because of degraded traffic throughput. Reauthentication of existing and 7109 BASE STATION SECURITY PROBLEM establishment of new IPsec and TLS sessions may fail. The ML-PPP interface operates with reduced capacity.

61622 MLPPP link Degrade

SyncE is no longer a working synchronization source.

7108 BASE STATION SYNCHRONIZATION PROBLEM

SyncE is no longer a working synchronization source.

7108 BASE STATION SYNCHRONIZATION PROBLEM

The local peer will not be able to go "online" 61632 Dup Addr detected-$DUPLICATEIPV6ADDRESS as there is already a remote peer operating with the IP address the local peer intended to go "online". All configured IPsec policies are ignored, 61639 IPsec emergency bypass active The remote peers continue their operation and all the SBTS traffic is sent unprotected. without disruption. The resulting packet capture files can used for Expert analysis to identify network problems and to help determine the best course of action.

61641 IP Traffic Capturing ongoing on $UNIT, $INTERFACE, $MACADDRESS

No further logins are permitted for that account until it is unlocked.

7109 BASE STATION SECURITY PROBLEM

SBTS traffic has switched over from the 61643 IPsec tunnel switchover primary IPsec tunnel to secondary (backup) IPsec tunnel terminating on secondary security gateway.

The IKE SA cannot be established.

61644 IKE authentication failure

IKE SA cannot be established and subsequently no IPsec SAs can be established.

61645 IKE SA failure

The related IPsec SA cannot be established 61646 IPSec SA failure and used.

If the fans rotate faster than required, they cause unnecessary noise.

7115 BASE STATION INFORMATION

The BTS is not operational or is degraded.

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION7115 BASE

Reported Alarms Description

When fault affects basic services of the base station: 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION When autonomous recovery reset is being performed When affects basic services of the base station: due to fault the fault: 7116 SERVICE PROBLEM RESET 7101 BASE STATION STATION/UNIT AUTONOMOUS NOTIFICATION When fault does not affect basic services of the base station: When autonomous recovery reset is being performed 7115 BASE STATION INFORMATION due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET When autonomous recovery reset is being performed NOTIFICATION due to the fault: -7101 When fault STATION/UNIT affects basic services of the baseRESET station: BASE AUTONOMOUS When autonomous recovery reset is not being NOTIFICATION performed due to the fault: 7116 BASE STATION SERVICE PROBLEM 7116 BASE STATION SERVICE PROBLEM - When fault does not affect basic services of the base When fault affects basic services of the base station: station: 7116 BASE STATION SERVICE PROBLEM 7115 BASE STATION INFORMATION When fault does not affect basic services of the base station: - When autonomous recovery reset is being performed 7115 BASE STATION INFORMATION due to the fault: When autonomous recovery reset is being performed 7101 BASE STATION/UNIT AUTONOMOUS RESET due to the fault: NOTIFICATION 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When fault affects basic services of the base station: 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When fault affects basic services of the base station: When fault does not affect basic services of the base station: 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM 7115 BASE STATION INFORMATION 7103 BASE STATION EXTERNAL ALARM When fault does not affect basic services of the base NOTIFICATION is reported towards NetAct. station: 7995 MAINS BREAKDOWN WITH BATTERY BACKUP 7115 BASE STATION INFORMATION is reported towards BSC. 7102 BASE STATION RESOURCE BLOCKED BY USER

7102 BASE STATION RESOURCE BLOCKED BY USER

7102 BASE STATION RESOURCE BLOCKED BY USER

When fault affects basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7112 BASE STATION CONFIGURATION PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7112 BASE STATION CONFIGURATION PROBLEM When fault does not affect basic services of the base station: 7101 BASE STATION/UNIT AUTONOMOUS RESET 7115 BASE STATION INFORMATION NOTIFICATION (raised only if RESET RECOVERY is triggered) 7116 BASE STATION SERVICE PROBLEM When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

7101 RESET NOTIFICATION (when reset is being performed) 7116 BASE STATION SERVICE PROBLEM (when reset has not been triggered for any reason)

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION (Raised only if RESET RECOVERY is triggered.) 7116 BASE STATION SERVICE PROBLEM (When reset has not been triggered for any reason.)

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION (When reset is being performed.) 7116 BASE STATION SERVICE PROBLEM (When reset has not been triggered for any reason.) 7112 BASE STATION CONFIGURATION PROBLEM (At startup when the cell will be out of order.) 7115 BASE STATION INFORMATION (At runtime when state is working)

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION (when reset is being performed) 7116 BASE STATION SERVICE PROBLEM (when reset has not been triggered for any reason)

When fault affects basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7100 BASE STATION HARDWARE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: 7101 BASE STATION/UNIT AUTONOMOUS RESET 7115 BASE STATION INFORMATION NOTIFICATION When autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When fault affects basic services of the base station: 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When fault does not affect basic services of the base When fault affects basic services of the base station: station: 7116 BASE STATION SERVICE PROBLEM 7115 BASE STATION INFORMATION When fault does not affect basic services of the base When autonomous recovery reset is being performed station: due to the fault: 7115 BASE STATION INFORMATION 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION When autonomous recovery reset is being performed due to the fault: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station AirScale SBTS, Flexi SBTS: 7101 BASE STATION/UNIT AUTONOMOUS RESET 7115 BASE STATION INFORMATION NOTIFICATION When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When fault affects basic services of the base station: 7108 BASE STATION SYNCHRONIZATION PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When fault affects basic services of the base station 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base When fault affects basic services of the base station: station 7113 BASE STATION ANTENNA LINE PROBLEM 7115 BASE STATION INFORMATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM NOTIFICATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION 7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7108 BASE STATION SYNCHRONIZATION PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7108 BASE STATION SYNCHRONIZATION PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When autonomous recovery reset is being performed due to the fault: When fault does not affect basic services of the base When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS station: 7111 BASE STATION SOFTWARE MANAGEMENT NOTIFICATION 7115 BASE STATION INFORMATION PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: 7101 BASE STATION/UNIT AUTONOMOUS RESET 7115 BASE STATION INFORMATION NOTIFICATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: 7101 BASE STATION/UNIT AUTONOMOUS RESET 7115 BASE STATION INFORMATION NOTIFICATION When autonomous recovery reset is being performed due to the fault: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7100 BASE STATION HARDWARE PROBLEM NOTIFICATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM; When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When autonomous recoveryAUTONOMOUS reset is being executed 7101 BASE STATION/UNIT RESET 7115 BASE STATION INFORMATION due to the fault: NOTIFICATION 7101 BASE STATION/UNIT AUTONOMOUS RESET When autonomous recovery reset is being performed NOTIFICATION due to the fault: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS When autonomous recovery reset is not being executed 7116 BASE STATION SERVICE PROBLEM NOTIFICATION due to the fault: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When fault does not affect basic services of the base When fault affects basic services of the base station: station: 7100 BASE STATION HARDWARE PROBLEM 7115 BASE STATION INFORMATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7111 BASE STATION SOFTWARE MANAGEMENT NOTIFICATION PROBLEM When fault does not affect basic services of the base When fault affects basic services of the base station: station: 7102 BASE STATION RESOURCE BLOCK BY USER 7115 BASE STATION INFORMATION When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

- when fault affects basic services of the base station 7116 BASE STATION SERVICE PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when fault affects basic services of the base station - when autonomous recovery reset is being performed 7116 BASE STATION SERVICE PROBLEM due to the fault - when fault does not affect basic services of the base 7101 BASE STATION/UNIT AUTONOMOUS RESET station NOTIFICATION 7115 BASE STATION INFORMATION - when fault affects basic services of the base station - when autonomous recovery reset is being performed 7116 BASE STATION SERVICE PROBLEM due to the fault - when fault does not affect basic services of the base 7101 BASE STATION/UNIT AUTONOMOUS RESET station NOTIFICATION 7115 BASE STATION INFORMATION - when fault affects basic services of the base station 7112 BASE STATION CONFIGURATION PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION

- when autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION - when autonomous recovery reset is not being - when autonomous recovery reset is being performed performed due to the fault due to the fault 7115 BASE STATION INFORMATION 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION - when autonomous recovery reset is not being performed due to the fault 7115 BASE STATION INFORMATION

- when fault affects basic services of the base station 7116 BASE STATION SERVICE PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When fault affects basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7100 BASE STATION HARDWARE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7112 BASE STATION CONFIGURATION PROBLEM NOTIFICATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed due to the fault: When fault affects basic services of the base station: 7101 BASE STATION/UNIT AUTONOMOUS RESET 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When fault does not affect basic services of the base When fault affects basic services of the base station: station: 7116 BASE STATION SERVICE PROBLEM 7115 BASE STATION INFORMATION When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM 7115 BASE STATION INFORMATION 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION (raised if RESET RECOVERY is triggered) 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION (when reset is being performed) 7116 BASE STATION SERVICE PROBLEM (when reset has not been triggered for any reason)

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION (When reset is being performed.) 7116 BASE STATION SERVICE PROBLEM (When reset has not been triggered for any reason.)

7115 Base Station Information

7107 BASE STATION CONNECTIVITY PROBLEM alarm reported during base station startup 7115 BASE STATION INFORMATION alarm reported during base station runtime

7112 BASE STATION CONFIGURATION PROBLEM alarm reported during base station startup 7115 BASE STATION INFORMATION alarm reported during base station runtime

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM (Level 7115 BASE STATION INFORMATION BTS fault is toggling in the BTS.) 7107 BASE STATION CONNECTIVITY PROBLEM (Level BTS fault is toggling in the BTS.) 7108 BASE STATION SYNCHRONIZATION PROBLEM (Level BTS fault is toggling in the BTS.) 7109 BASE STATION SECURITY PROBLEM (Level BTS fault is toggling in the BTS.) 7113 BASE STATION ANTENNA LINE PROBLEM (Level BTS Line fault is toggling in the BTS.) 7114 CELL SERVICE PROBLEM (Level BTS fault is toggling in the BTS.) When fault affects basic services of the(Level base BTS station: 7115 BASE STATION INFORMATION fault 7112 BASEinSTATION is toggling the BTS.)CONFIGURATION PROBLEM When fault does not affect basic PROBLEM services of the base 7116 BASE STATION SERVICE (Level BTS station: fault is toggling in the 7115 BTS.)BASE STATION INFORMATION 7103 BASE STATION EXTERNAL ALARM NOTIFICATION (EAC1=7401, EAC2=7402, etc.)

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION (when reset is being performed) 7116 BASE STATION SERVICE PROBLEM (when reset has not been triggered for any reason)

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7112 BASE STATION CONFIGURATION PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION When autonomous recovery reset is being performed When autonomous recovery reset is not being due to the fault: performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET 7108 BASE STATION SYNCHRONIZATION PROBLEM NOTIFICATION When autonomous recovery reset is not being performed due to the fault: 7115 BASE STATION INFORMATION - when autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION When autonomous recovery reset is being performed due to the fault: - when autonomous recovery reset is not being 7101 BASE STATION/UNIT AUTONOMOUS RESET performed due to the fault NOTIFICATION 7115 BASE STATION INFORMATION When autonomous recovery reset is not being performed due to the fault: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7108 BASE STATION SYNCHRONIZATION PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM when fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7113 BASE STATION ANTENNA LINE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7112 BASE STATION CONFIGURATION PROBLEM When fault does not affect basic services of the base station: - when fault affects basic services of the base station 7115 BASE STATION INFORMATION 7112 BASE STATION CONFIGURATION PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7108 BASE STATION SYNCHRONIZATION PROBLEM When fault affects basic services of the base station: When fault does not affect basic services of the base 7108 BASE STATION SYNCHRONIZATION station: PROBLEM 7115 BASE STATION INFORMATION When fault does not affect basic services of the base When fault affects basic services of the base station: station: 7108 BASE STATION SYNCHRONIZATION 7115 BASE STATION INFORMATION PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

When fault affects basic services of the base station: 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7100 BASE STATION HARDWARE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

- when fault affects basic services of the base station 7116 BASE STATION SERVICE PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION - when autonomous recovery reset is not being - when fault affects basic services of the base station performed due to the fault 7116 BASE STATION SERVICE PROBLEM 7116 BASE STATION SERVICE PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION - when autonomous recovery reset is not being performed due to the fault 7116 BASE STATION SERVICE PROBLEM

- when fault affects basic services of the base station 7116 BASE STATION SERVICE PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

- when autonomous recovery reset is being performed due to fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when fault affects basic services of the base station 7116 BASE STATION SERVICE PROBLEM - When fault affects basic services of the base station 7116 BASE STATION SERVICE PROBLEM - When fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when fault affects basic services of the base station 7112 BASE STATION CONFIGURATION PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when fault affects basic services of the base station 7112 BASE STATION CONFIGURATION PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION - when fault affects basic services of the base station 7112 BASE STATION CONFIGURATION PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION When autonomous recovery reset is not being performed due to the fault: 7116 BASE STATION SERVICE PROBLEM

When fault affects basic services of the base station: 7112 BASE STATION CONFIGURATION PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION

- when fault affects basic services of the base station 7111 BASE STATION SOFTWARE MANAGEMENT PROBLEM - when fault does not affect basic services of the base station 7115 BASE STATION INFORMATION

- when autonomous recovery reset is being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION - when autonomous recovery reset is being performed due to the fault - when autonomous recovery reset is not being performed due to the fault 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION 7116 BASE STATION SERVICE PROBLEM - when autonomous recovery reset is not being performed due to the fault 7116 BASE STATION SERVICE PROBLEM

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When fault does not affect basic services of the base station: When fault affects basic services of the base station: 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: When fault affects basic services of the base RESET station: 7101 BASE STATION/UNIT AUTONOMOUS 7115 BASE STATION INFORMATION 7116 BASE STATION SERVICE PROBLEM NOTIFICATION When autonomous recovery reset is being performed When fault does not affect basic services of the base due to the fault: station: 7101 BASE STATION/UNIT AUTONOMOUS RESET AirScale SBTS, Flexi SBTS: 7115 BASE STATION NOTIFICATION INFORMATION When autonomous recovery reset is being performed due to the fault: AirScale SBTS, Flexi SBTS: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

When the fault affects basic services of the base station: 7116 BASE STATION SERVICE PROBLEM When the fault does not affect basic services of the base station: 7115 BASE STATION INFORMATION When autonomous recovery reset is being performed due to the fault: 7101 BASE STATION/UNIT AUTONOMOUS RESET NOTIFICATION

Instructions

Check the active fan alarms and the air flow of the BTS.

1. Download the BTS SW again. 2. Reset (block and unblock) the BTS. 3. If step 2 does not help, replace the alarming module. Because there are several possibilities for the alarm activation, a BTS Clock Frequency History feature has been developed. You can access the stored history data through the BTS Element Manager. You can use the history data as a tool for finding out the reason for the fault 1. Ensure that the module is properly connected. If the or alarm situation (for further instructions about the history module LED does not light up, the module is faulty. Check feature, see the online help of BTS Element Manager). the module that is causing the alarm. Depending on the possible reason, follow the instructions below: 2. Check the fault history. 1. Block and unblock the BTS. 1. In case of a fault in the transmission network 2. Perform a power-off reset. synchronization, you must correct the network synchronization. The long-term accuracy of the Iub signal 3. If steps 1 and 2 do help, replace the module that is must 0.015 ppm ornot better (check correct Note: be perform the steps bellow in thethe listed orderIub until the causing the accuracy by measuring it). No actions on the BTS are fault disappear: alarm. necessary. 1. Perform WCDMA RAT Reset. 2. accuracypersists of the Iub signal is correct, 2. If If the the basic fault condition after the RAT Reset,but restart 1. Block or unblock the module that is causing the alarm. there is too much instability, that is, the jitter or wander is the BTS. outside the acceptable limits, you must correct the 3. Save the snapshot, it should contain all necesarry logs 2. Replace the module that is causing the alarm. synchronization to be analyzed. of the transmission network. The limits for the jitter or wander are defined in the ITU-T G.823/824/825. Nosteps actions on listed the BTS areuntil needed. Note: Perform the in the order the fault is resolved. 3. In case of a BTS equipment fault, the location might be: 1. Reset the WCDMA SW. Transport part: Note: Perform the steps in the listed order until the fault is 2. Check the transmission links to the RNC. resolved. - First, check the alarms of the TRS with the BTS Element Manager andBTS act accordingly. 3. Check the and RNC transmission settings. 1. Reset the WCDMA SW. -Update therethe are no alarms, the TRS with thecheck compatible SWsynchronization (check the SW 4.IfReset theBTS SBTS. 2. Check the transmission links to the RNC. settings. versions to see the active SW version and update the active SW version) unless it is automatically updated by 5. Replace the System Module. 3. Check BTS and RNC transmission settings. Note that the if the reason is in the transmission network NetAct. synchronization, replacing the faulty unit does not solve 4. Reset the SBTS. the problem. alarmSW activity (frequent In case of RFFurthermore, modules withthe factory loaded, SW update alarms or cancels) points to instability in the transmission is a mandatory step. 5. Replace network, notthe to System a fault inModule. the unit. 4. After the fault situation has been cleared, you might need to tune the BTS master clock because the BTS master clock adjustment is quite slow. You can perform the tuning:

Update to a compatible SW of the BTS (check the SW versions to see the active SW version, and update the active SW version) unless it is automatically updated by the NetAct. 1. Check the NTP setting. 2. Check the stratum parameter on the NTP server. 3. Check that a GNSS is configured and connected. Note: Perform the steps in the listed order until the fault is resolved. 1. Retry the file update for a few times. Note: Perform the steps in the listed order until the fault is 2. Check the FTP account user settings. resolved. 3. Check the file and path names. 1. Retry the SW update. Note: Perform the steps in the order until the fault is 4. Check the administration loglisted on the file server. 2. Save the snapshot and check the download status from resolved. the BTS SWDLreport in the snapshot file. 1. Retry the SW update. Note: Perform the steps in the listed order until the fault is 2. If other flash memory-related faults are active for the resolved. alarming module at the same time, replace the alarming module. 1. Retry the SW update. Check the main power supply of the base station. 2. If other flash memory-related faults are active for the alarming module at the same time, replace the alarming module. Unblock the module with the BTS Element Manager.

Unblock the cell to cancel the fault.

Unblock the BTS to cancel the fault. Unblocking the BTS causes a BTS reset.

Check the fault history and other active faults of the unit. Note: This fault does not require any (special) actions. 1. Reset the alarming unit or module. 2. Remove or reinsert the alarming unit or module. 3. Replace the alarming unit or module.

Note: Perform the steps in the listed order until the fault is resolved. 1. Check the cell parameters (pre-configuration under private configuration data) in the RNC and the BTS. Replace the alarming unit or module. 2. If the parameters configured to the RNC are correct, lock and unlock all cells of this BTS. Use the BTS element manager to trigger parameter sending from the RNC to the 1. Upgrade BTS again. the system module SW. 2. the unit. configured to the RNC are incorrect, 3. Replace If the parameters lock the cells and configure the parameters to the correct values. Afterwards, unlock Note: Perform the steps in the the cells. listed order until the fault is resolved. 4. If the default values for the cell parameters (such as rampdown notunit. appropriate in the BTS, 1. Reset thetime/step) alarming are radio reconfigure the BTS. Note: Perform the steps in the listed order until the fault is 2. If the fault is reported again, replace the optical cables resolved. and SFPs used to connect the alarming radio module to the system module/extension baseband module. 1. Reset the BTS. 2. Check the commissioning. Check signaling link settings and thethe RNC connections. 3. If thethe fault is reported again, replace alarming radio 3. Replace the affected HW. module hardware.

Note: Perform the steps in the listed order until the fault is resolved. 1. Check the other active alarms and act accordingly. 2. If there are no other active alarms, or step 1 does not Add more baseband capacity to the BTS or, if the reason is help, reset the BTS. a broken baseband unit, replace the baseband unit. 3. Replace the System Module. Too low Tx signal level measured in radio module may be detected due to failure of any unit on the path between the tx antenna line port on radio module and the DSP. Execute the following actions to recover the fault in the presented sequence: Note: Perform the steps in the listed order until the fault is 1. Reset the alarming radio unit. resolved. 2. If previous step has been executed and fault is reported again, reset the BTS 1. Check the configuration to make sure that there are (block / unblock BTS). enough resources for the minimum HSUPA capacity. 1. IDENTIFICATION 3. PROBLEM If previous steps have been executed and the fault is Ensure youreplace have the latest documentation available. reportedthat again, 2. If there are not enough resources, add additional Check SWand version, of Generic Faults (LGF), and optical the cables SFPsList used to connect the alarming HSUPA licence. Technical Notes for any known faults related to the SW in radio module to the system use. Check the configuration module / extension basebandpictures module.of cabling and 1. IDENTIFICATION 3. PROBLEM Reset the BTS to get the minimum capacity predevices installed. 4. If previous steps have been executed and fault is Ensure that theinlatest selection foryou the have HSUPA use. documentation available. Note: Useagain, the fault-specific troubleshooting instructions reported replace Check the SW version, List of Generic Faults (LGF), and from NOLS;" radio RX Signal hardware. the alarming Technical Notes formodule any known faults related to the SW in level trouble shooting" document as detailed 5. If previous steps have beenpictures executed and guidance fault is for use. Check the configuration of cabling and remote and site-specific reported again, replace devices installed. investigations. the system module hardware or extension baseband Note: Use the fault-specific troubleshooting instructions module hardware (depends on from NOLS;" RX Signal 2. REMOTE INVESTIGATIONS where the alarming radio module as is connected). level trouble shooting" document detailed guidance for Check if anything has changed in the system, and what remote and site-specific triggered the alarm. investigations. - SW updates, configuration, commissioning or Carrier power changes, RF sharing 2. REMOTE INVESTIGATIONS activation or HW unit swap. If the alarm appeared after any Check if anything has changed in the system, and what changes, return triggered the alarm.

Note: Perform the steps in the listed order until the fault is resolved. 1. BTS reset. Note: Perform the steps in the listed order until the fault is 2. Replace the alarming module. resolved. 1. Reduce the number of PIC pools in the BTS configuration or add new FSP to the BTS. Note: Perform the steps in the listed order until the fault is resolved. 2. BTS reset. 1. Reduce the number of PIC pools in the BTS configuration or add new FSP to the BTS. If the faulty FSP is in the extension system module, block and/or unblock the extension system module. Otherwise, 2. Perform a BTS reset. block and/or unblock the BTS. When the fault is detected, the operator should check the UARFCN configuration of the cells and the PIC pool configuration. The operator should change the UARFCN of the cell at the The lack of CCCH licensed capacity on the BTS (caused RNC so there are no two cells in the LCG with the same by an insufficient number of commissioned CCCH UARFCN while one is in PIC pool and the other is not. Processing Set licenses) caused the cell setup with the The operator should also modify the PIC pool configuration requested cell settings to fail. so that the number of PIC cells is correct (number of RX of Note: Perform in the listed order until=0). Check the related PDH alarms and follow the instructions 1. Confirm that SyncE is desired as a synchronization of these alarms. source. 2. Confirm that configuration settings for ssmEnabled are correct. 3. Troubleshoot with Backhaul provider about the reason 1. Confirm that SyncE is desired as a synchronization for SSM errors. source. 2. Confirm that SBTS configuration settings for ssmEnabled are correct. 3. Troubleshoot with Backhaul provider about the reason 1.Check for duplicate IPv6 addresses configured in the for SSM errors. network element. 2.Change the identified duplicate IPv6 address. Start IPsec emergency bypass by making the security gateway unreachable either by plugging out the cable or configuring the wrong security gateway address. Stop IP traffic capture from SBTS Element Manager.

Check the validity of the username and password of the account.

1. Check the availability of IP connectivity. 2. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.

Check the authentication credential provided by the peer (certificate).

Check the IKE profile configuration of the SBTS and the peer for proper values.

Check the configurations for the peer and the SBTS security policies for the corresponding failure notification.

1. Check if the fan or air flow is blocked by any object. Remove any objects that might be blocking the fan or air flow. 2. Check if the fan connector is properly mounted. Mount 1. Block and/or unblock the alarming module. the fan connector properly. 2. If FSP or FBB or ABIA is the fault source, perform FSP 3. If the alarm continues, reset the radio module. or FBB or ABIA reset recovery. If FCT/ASIA is the fault source, perform a system module reset recovery. If that 4. If the alarm still continues, replace the fan module. does not help, perform a power-off reset. 3. If steps 1 and 2 do not help, replace the alarming module.

Related Faults

Related Features

• RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • 50160: TCP/IP measurement • RP001534: SRAN FM combined service • LTE146: LTE Software Management • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • RP001534: SRAN FM combined service • LTE2779: CPRI-A • LTE151: Autonomous LTE eNB Operability • LTE505: LTE505 Transport Separation for RAN sharing • RP001534: SRAN FM combined service • LTE151: Autonomous LTE eNB Operability • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • ARAN1163: Iu-PS Throughput Measurement for GTP Traffic • RP000980: SBTS Recovery • RP001534: SRAN FM combined service

• RP000980: SBTS Recovery • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • LBT2761: CRL5746 Configuration of RU with incompatibility software • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE146: LTE Software Management

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE146: LTE Software Management

• RP001534: SRAN FM combined service • LTE146: LTE Software Management • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE146: LTE Software Management • LTE1996: Flexi Zone Controller Application • RP000924: SBTS Intelligent shutdown • RP001486: Support for already delivered SRAN16.2/16.10 features • RP001534: SRAN FM combined service • LTE654a: LTE Configuration Management 1/2

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE654a: LTE Configuration Management 1/2 • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE654a: LTE Configuration Management 1/2 • RP001621: SRAN Cell Sets Allocation on Full AirScale Module

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RAN3280: Dynamic Baseband Configuration for High Speed Cell_FACH • RP001171: WCDMA17 new feature implementation for SBTS17 • RAN3067: Carrier Aggregation • RP001171: WCDMA17 new feature implementation for SBTS17 • RAN3067: Carrier Aggregation • RP001171: WCDMA17 new feature implementation for SBTS17 • RAN3421: WCDMA Support over Nokia CPRI for SBTS

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE 161-p : Technical Log and Memory Dump • RP001534: SRAN FM combined service • LTE168: LTE System Maintenance • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • ARAN1163: Iu-PS Throughput Measurement for GTP Traffic • RP001534: SRAN FM combined service • LTE168: LTE System Maintenance • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE2779: CPRI-A • ARAN1163: Iu-PS Throughput Measurement for GTP Traffic • LTE1996: Flexi Zone Controller Application • RAN20: HSDPA parameterisation • RP001534: SRAN FM combined service • RAN1671: Enhanced UltraSite Base Band (EUBB) • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE2464: Synchronization with Network Time Protocol • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • ARAN1163: Iu-PS Throughput Measurement for GTP Traffic • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE2779: CPRI-A • RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE076-a : Support for legacy MHA • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • RP000912: SBTS SW Management

• RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • LTE-435: RF sharing WCDMA-LTE • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE80: GPS Synchronisation • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • RP001534: SRAN FM combined service • LTE2779: CPRI-A • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • RP001534: SRAN FM combined service • LTE2779: CPRI-A • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • LTE2779: CPRI-A • RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • RP001534: SRAN FM combined service • LTE2779: CPRI-A • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • LTE2779: CPRI-A • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • LTE2779: CPRI-A • RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • LTE2779: CPRI-A • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE2121: Radio Unit reset in BTS SM • LTE2779: CPRI-A • RP001534: SRAN FM combined service • LTE151: Autonomous LTE eNB Operability

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • LTE2779: CPRI-A • LBT975: Medusa single mode support for LTE

• RP001534: SRAN FM combined service • LBT975: Medusa single mode support for LTE

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE435d: CN5259 New alarm to RF SW to indicate RP3 collision problems • RP001534: SRAN FM combined service • LTE923: TD-LTE Ir interface support • LTE2779: CPRI-A • RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • RP000356: IPsec for BTS

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service • LTE2779: CPRI-A

• LTE3368: PIM Cancellation for CPRI-A radios • RP001740: LTE feature parity alignment to FDDLTE17SP on Airscale • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • RAN1016: High Capacity System Module • RAN2262: Flexi Multimode System Modules FSMF and FSMG • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • 50160: TCP/IP measurement

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• LTE3368: PIM Cancellation for CPRI-A radios • RP001740: LTE feature parity alignment to FDDLTE17SP on Airscale • LTE3368: PIM Cancellation for CPRI-A radios • RP001740: LTE feature parity alignment to FDDLTE17SP on Airscale • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• LTE2250: Syslog substring triggered automated snapshot collection • RP001534: SRAN FM combined service • RP001621: SRAN Cell Sets Allocation on Full AirScale Module • RP001534: SRAN FM combined service • LTE1444: FBBC basic start up, auto detection and • LTE654: LTE Configuration Management transparent mode • LTE441a: CN4796 Keep cell in service in case of one TX path failure • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE2578 : RRU path failure handling improvement for • LTE1996: Flexi Zone Controller Application TDD 8 path beamforming • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• LTE656: LTE Fault Management • LTE1996: Flexi Zone Controller Application • RP001486: Support for already delivered SRAN16.2/16.10 features • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• LTE2442: Preventing cell activation

• RP001534: SRAN FM combined service • LTE447: SW support for RF sharing GSM-LTE

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE654a: LTE Configuration Management 1/2 • RP001534: SRAN FM combined service • LTE-435: RF sharing WCDMA-LTE

• RP001534: SRAN FM combined service • RAN1770: RF Sharing in WCDMA-GSM

• RP001534: SRAN FM combined service • LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices • RP001534: SRAN FM combined service • LTE1227: Flexi Multiradio BTS SW Download for Antenna Line Devices • RP001538 : WCDMA Support in new Single BTS O&M architecture

• RP001534: SRAN FM combined service • LTE493-b: Beamforming - Operability & Configuration support • LTE937-b1: FSMr3b: L3 call support - Feature porting to FSM-R3 • RP001534: SRAN FM combined service • LTE1976: Support for single and multi-antenna RET

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • FSM3TD57: Common application SW adaptation for FSM-r3 - Base services • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • FSM3TD57: Common application SW adaptation for FSM-r3 - Base services • RP001534: SRAN FM combined service • RP001498: Support of FSMF + FSMF with SRAN configurations • FSM3TD57: Common application SW adaptation for FSM-r3 - Base services • RP001534: SRAN FM combined service • LTE882a1: System Upgrade with Backward Compatibility - FDD - conversion • LTE1854 A-h: System Upgrade to RL70-consistent SW fallback • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE882a1: System Upgrade with Backward Compatibility - FDD - conversion • LTE1854 A-h: System Upgrade to RL70-consistent SW fallback • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE882a1: System Upgrade with Backward Compatibility - FDD - conversion • LTE1854 A-h: System Upgrade to RL70-consistent SW fallback • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE882a1: System Upgrade with Backward Compatibility - FDD - conversion • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE595-b15: FSMr3b: RP3-01 operation mode

• RP001534: SRAN FM combined service • LTE3043: Remote Power Port Control for FPFD PDU

• RP001534: SRAN FM combined service • LTE447: SW support for RF sharing GSM-LTE

• RP001534: SRAN FM combined service • LTE-435: RF sharing WCDMA-LTE • LTE1815: Clock Slave mode for TD-SCDMA and TDLTE dual mode on FSIH • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LBT1464: On-line modification of ANTL/alDcVoltageEnabled • RP001534: SRAN FM combined service • LBT1464: On-line modification of ANTL/alDcVoltageEnabled

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • WM0628: WM0628 • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE923: TD-LTE Ir interface support

• RP001534: SRAN FM combined service • LTE923: TD-LTE Ir interface support • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • RP001534: SRAN FM combined service • LTE1444: FBBC basic start up, auto detection and transparent mode • RP001534: SRAN FM combined service • LTE1053: Real-time KPI-monitoring with Traffica • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE505: LTE505 Transport Separation for RAN sharing • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1710: Temporary Master Role for LTE Radio Slave

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • RP001534: SRAN FM combined service • LTE1829: LTE-LTE RF sharing

• RP001534: SRAN FM combined service • LTE1656: Management support for legacy Motorola/Fujitsu RF-equipment • LTE2779: CPRI-A • LTE3114-B: Nokia SM Delay Compens. for CPRI-A • RP001534: SRAN FM combined service Radios with almost no buffer • LTE2154: Cell state audit alarm

• RP001534: SRAN FM combined service • LTE2305: Inter eNodeB Carrier Aggregation for 2 macro eNodeBs • RP001534: SRAN FM combined service • LTE2305: Inter eNodeB Carrier Aggregation for 2 macro eNodeBs • RP001534: SRAN FM combined service • LTE790: Signed SW

• RP001534: SRAN FM combined service • LTE790: Signed SW

• RP001534: SRAN FM combined service • LTE790: Signed SW

• RP001534: SRAN FM combined service • LTE790: Signed SW

• RP001534: SRAN FM combined service • LTE2099: Support for harmonized MHA family

• RP001534: SRAN FM combined service • LBT2761: CRL5746 Configuration of RU with incompatibility software • LTE2816: High Memory Consumption Alarm for Nokia RP1/L3 Radio Modules • RP001534: SRAN FM combined service • LTE1900: Centralized RAN

• RP001534: SRAN FM combined service • LTE1900: Centralized RAN

• RP001534: SRAN FM combined service • LTE2523: Plug-in radio SW interface for OBSAI • LTE2779: CPRI-A • RP001534: SRAN FM combined service

• RP001004: SBTS Data User RTU • RP001534: SRAN FM combined service

• RP001004: SBTS Data User RTU • RP001534: SRAN FM combined service

• RP001004: SBTS Data User RTU • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2417: IP Traffic Capacity

• RP000996: SRAN Clock time management

• RP000374: Timing over Packet with frequency synchronization • RP000383: Timing over Packet with Phase Synchronization • RP000375: Synchronous Ethernet

• RP000377: Synchronization from PDH interface

• RP001534: SRAN FM combined service • LTE1891: eNode B power saving - Micro DTX

• RP001534: SRAN FM combined service • LTE2270: FDD-TDD downlink carrier aggregation 2CC

• RP001534: SRAN FM combined service • LTE1891: eNode B power saving - Micro DTX

• LBT3196: CRL8712 New alarms for OTN network • RP001534: SRAN FM combined service

• LBT3196: CRL8712 New alarms for OTN network • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2470: Centralized RAN for FL16

• RP001534: SRAN FM combined service • LTE2645: GNSS Manual Location Entry for Macro BTS • RP001534: SRAN FM combined service • LTE2816: High Memory Consumption Alarm for Nokia RP1/L3 Radio Modules • RP001534: SRAN FM combined service • LTE2816: High Memory Consumption Alarm for Nokia RP1/L3 Radio Modules • RP001534: SRAN FM combined service • LTE2805: Monitoring RX sensitivity

• LBT2534: Legacy feature porting to FSMr4-Parent

• RP001534: SRAN FM combined service • LTE2114 -V-e: FSIP/FBIP, FSMr4;Supporting U-Plane CE startup • RP001534: SRAN FM combined service • LTE2387: LTE-LTE RF Sharing + Dual Band LTE Site with RF Sharing GSM • RP001534: SRAN FM combined service • LTE2621-B: eNodeB Limitation Actions for License Management in LTE

• RP001534: SRAN FM combined service • LTE2621-A: eNodeB Limitation Actions for License Management in LTE • RP001534: SRAN FM combined service • LTE2114 -V-h: FSIP/FBIP, FSMr4;Supporting K2 ARM platform CE crash • RP001534: SRAN FM combined service • LTE2779: CPRI-A

• RP001004: SBTS Data User RTU • RP001534: SRAN FM combined service

• RP001498: Support of FSMF + FSMF with SRAN configurations • LTE2866: AirScale operation with 2 Core plugins • RP001534: SRAN FM combined service • LTE3043: Remote Power Port Control for FPFD PDU

• RP001621: SRAN Cell Sets Allocation on Full AirScale Module • LTE2866: AirScale operation with 2 Core plugins • RP001534: SRAN FM combined service • LTE2483: Classical WCDMA/LTE RF-sharing on AirScale SM Indoor • RP001534: SRAN FM combined service • LTE2483: Classical WCDMA/LTE RF-sharing on AirScale SM Indoor • RP001534: SRAN FM combined service • LTE2483: Classical WCDMA/LTE RF-sharing on AirScale SM Indoor • RP001171: WCDMA17 new feature implementation for SBTS17

• RP001534: SRAN FM combined service • LTE3265: GPS outage handling for OTDOA

• SR001536: BTS InfoModel Adapter (IMP)

• RP001534: SRAN FM combined service • LTE3340: SWM Harmonization

• RP001534: SRAN FM combined service • LTE1530: Reduced LTE Guard Band

• RP000924: SBTS Intelligent shutdown • RP001534: SRAN FM combined service • RP001486: Support for already delivered SRAN16.2/16.10 features • *: * • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• LTE3397: LTE C-Plane in new Single BTS OAM architecture

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service

• LTE3086: Legacy ALD management protocol for CPRI-A

• RP001534: SRAN FM combined service • LTE2562: ANR InterRat 1xRTT - O&M assisted

• RP001534: SRAN FM combined service • LTE2562: ANR InterRat 1xRTT - O&M assisted

• RP001534: SRAN FM combined service • LTE1834: LTE MBMS Service Continuity

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2023: User plane overload handling

• RP001534: SRAN FM combined service • LTE430: DL power boosting for control channels • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE2023: User plane overload handling

• RP001534: SRAN FM combined service • LTE2023: User plane overload handling

• RP001534: SRAN FM combined service • LTE1: S1/X2 data path management • LTE505: LTE505 Transport Separation for RAN sharing • LTE1771: Dual U-plane IP addresses • RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • LTE3: S1, X2 and RRC common signaling • LTE505: LTE505 Transport Separation for RAN sharing • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE3: S1, X2 and RRC common signaling • LTE505: LTE505 Transport Separation for RAN sharing • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE3: S1, X2 and RRC common signaling • LTE505: LTE505 Transport Separation for RAN sharing • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE1117: LTE MBMS

• RP001534: SRAN FM combined service • LTE1117: LTE MBMS

• RP001534: SRAN FM combined service • LTE145part1: Radio Network Configuration via RROM • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE145part1: Radio Network Configuration via RROM • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE145part1: Radio Network Configuration via RROM • LTE1996: Flexi Zone Controller Application • LTE163: Subscriber and Equipment Trace • LTE163b: Subscriber and Equipment Trace (vendor specific extensions) • LTE433-b : Basic Cell Trace adaptations • LTE690: LTE Interface Trace Support • RP001534: SRAN FM combined service • LTE690-b: LTE Interface Trace Support • LTE654c: Configuration of Vendor Specific Parameters • LTE1996: Flexi Zone Controller Application • LTE1996: Flexi Zone Controller Application • RP001486: Support for already delivered SRAN16.2/16.10 features • LTE163: Subscriber and Equipment Trace • LTE163b: Subscriber and Equipment Trace (vendor specific extensions) • LTE433-b : Basic Cell Trace adaptations • LTE644: Configurable cell trace content • LTE450: MME capacity value change • LTE1996: Flexi Zone Controller Application • LTE1996: Flexi Zone Controller Application • RP001486: Support for already delivered • LTE3071: NB-IoT Inband SRAN16.2/16.10 features • RP001534: SRAN FM combined service • LTE782: ANR Fully UE based • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE908: ANR Inter-RAT UTRAN - Fully UE Based

• RP001534: SRAN FM combined service • LTE908: ANR Inter-RAT UTRAN - Fully UE Based

• RP001534: SRAN FM combined service • LTE908: ANR Inter-RAT UTRAN - Fully UE Based

• RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application • 50160: TCP/IP measurement • RP001534: SRAN FM combined service • LTE 1685-C: Neighbor Relation Robustness • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE1117: LTE MBMS • LTE1113: eICIC - macro • LTE1496: eICIC - micro • LTE2007: Inter eNB Carrier Aggregation • RP001534: SRAN FM combined service • LTE2208: eICIC extensions-micro • LTE2062: IRAT UTRAN Neighbor Relation • LTE2209: eICIC enhancements Robustness • LTE2554: Network Assisted Interference Cancellation and Suppression • RP001534: SRAN FM combined service • LTE1858: FDD Inter-band/Intra-band CA with Two Flexi Zone Micro BTSs • LTE2305: Inter eNodeB Carrier Aggregation for 2 macro eNodeBs • RP001534: SRAN FM combined service • LTE1858: FDD Inter-band/Intra-band CA with Two Flexi Zone Micro BTSs • LTE2305: Inter eNodeB Carrier Aggregation for 2 macro eNodeBs • RP001534: SRAN FM combined service • LTE1858: FDD Inter-band/Intra-band CA with Two Flexi Zone Micro BTSs • LTE2305: Inter eNodeB Carrier Aggregation for 2 macro eNodeBs • LTE2029: Extend amount of neighboring cells with overload control in eNB • RP001534: SRAN FM combined service • LTE2562: ANR InterRat 1xRTT - O&M assisted • LTE2029: Extend amount of neighboring cells with overload control in eNB • RP001534: SRAN FM combined service

• RP001534: SRAN FM combined service • LTE2007: Inter eNB Carrier Aggregation

• RP001534: SRAN FM combined service • LTE2007: Inter eNB Carrier Aggregation

• RP001534: SRAN FM combined service • LTE2007: Inter eNB Carrier Aggregation

• RP001534: SRAN FM combined service • LTE2060: Add new frequency or cell without reset

• RP001534: SRAN FM combined service • LTE2060: Add new frequency or cell without reset

• RP001534: SRAN FM combined service • LTE1130: Dynamic PUCCH allocation

• RP001534: SRAN FM combined service • LTE1130: Dynamic PUCCH allocation

• RP001534: SRAN FM combined service • LTE2612: ProSe Direct Communications for Public Safety • RP001534: SRAN FM combined service • LTE2562: ANR InterRat 1xRTT - O&M assisted

• RP001534: SRAN FM combined service • LTE3: S1, X2 and RRC common signaling • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE3: S1, X2 and RRC common signaling • LTE505: LTE505 Transport Separation for RAN sharing • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE3: S1, X2 and RRC common signaling • LTE505: LTE505 Transport Separation for RAN sharing • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE3: S1, X2 and RRC common signaling • LTE505: LTE505 Transport Separation for RAN sharing • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE915: S1 eNB Configuration Update • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE498: RAN Information Management for GSM • LTE1196: RIM for WCDMA • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE498: RAN Information Management for GSM • LTE1196: RIM for WCDMA • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE550: Radio parameter online changeable • LTE1996: Flexi Zone Controller Application • LBT1879: CN5544 Division of DSP Fatal Alarms • LTE1996: Flexi Zone Controller Application • RP001486: Support for already delivered SRAN16.2/16.10 features • RP001534: SRAN FM combined service • LTE168: LTE System Maintenance • LBT1693: CRL0823: CR Memory Supervision • LTE1996: Flexi Zone Controller Application • LBT3812: AirScale Virtual MCU

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LBT1879: CN5544 Division of DSP Fatal Alarms • LTE1996: Flexi Zone Controller Application

• RP001534: SRAN FM combined service • LBT1879: CN5544 Division of DSP Fatal Alarms • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LBT1879: CN5544 Division of DSP Fatal Alarms • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LBT1879: CN5544 Division of DSP Fatal Alarms • LTE1996: Flexi Zone Controller Application • RP001534: SRAN FM combined service • LTE1117: LTE MBMS

• RP001534: SRAN FM combined service • LTE1117: LTE MBMS

• RP001534: SRAN FM combined service • LTE3199: Support for multiple MBSFN and Synchronization Areas • LTE1117: LTE MBMS • RP001534: SRAN FM combined service • LTE1117: LTE MBMS

• RP001534: SRAN FM combined service • LTE3199: Support for multiple MBSFN and Synchronization Areas • LTE1117: LTE MBMS • RP001534: SRAN FM combined service • LTE3199: Support for multiple MBSFN and Synchronization Areas • RP001534: SRAN FM combined service • LTE3199: Support for multiple MBSFN and Synchronization Areas • RP001534: SRAN FM combined service • LTE3552: eMBMS capacity enhance. & support for overlapping of MBSFN Areas • RP001534: SRAN FM combined service • RP000361: Link Supervision with BFD

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

• RP001534: SRAN FM combined service • RP000350: Ethernet termination • RP000357: Symmetrical E1 Interface • RP000365: Electrical 10/100/1000-Base-T Interface • RP000367: Small Form Factor Pluggable Slot (SFP • RP000356: IPsec for BTS slot) • RP000368: 1000Base-SX Optical GE Interface • RP000369: 1000Base-LX Optical GE Interface • RP000370: 1000Base-ZX Optical GE Interface • RP001534: FM combined RP000371: SRAN 1000Base-BX Opticalservice GE Interface • RP000357: Symmetrical E1 Interface

• RP000367: Small Form Factor Pluggable Slot (SFP slot)

• RP000845: SBTS Operator Certificate Management

• LTE140: Ethernet OAM • LTE1996: Flexi Zone Controller Application

• LTE140: Ethernet OAM • LTE1996: Flexi Zone Controller Application

• LTE140: Ethernet OAM • LTE1996: Flexi Zone Controller Application

• RP000367: Small Form Factor Pluggable Slot (SFP slot)

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

• RP001534: SRAN FM combined service • RP000357: Symmetrical E1 Interface

• RP000956: SBTS Startup and runtime management

• RP000176: MLPPP termination

• RP000176: MLPPP termination

• RP000176: MLPPP termination

• LTE140: Ethernet OAM

• LTE140: Ethernet OAM

• RP000845: SBTS Operator Certificate Management

• RP001534: SRAN FM combined service • RP000361: Link Supervision with BFD

• RP001534: SRAN FM combined service • RP000361: Link Supervision with BFD

• RP001534: SRAN FM combined service • RP000365: Electrical 10/100/1000-Base-T Interface

• RP001534: SRAN FM combined service • RP000360: IP Transport Network Measurements

• RP001534: SRAN FM combined service • RP000360: IP Transport Network Measurements

• RP000845: SBTS Operator Certificate Management

• RP000845: SBTS Operator Certificate Management

• RP000176: MLPPP termination

• RP000375: Synchronous Ethernet

• RP000375: Synchronous Ethernet

• RP001534: SRAN FM combined service • RP000589: IPv4/IPv6 Transport Stack

• RP000439: IPsec Emergency Bypass

• RP001534: SRAN FM combined service • RP000465: Local and Remote IP Traffic Capturing

• RP000900: SBTS user account management • RP001498: Support of FSMF + FSMF with SRAN configurations • RP000600: Backup IPsec Tunnel

• RP000356: IPsec for BTS

• RP000356: IPsec for BTS

• RP000356: IPsec for BTS

• RP001534: SRAN FM combined service • LTE2121: Radio Unit reset in BTS SM

• RP001534: SRAN FM combined service • LTE151: Autonomous LTE eNB Operability • LTE1996: Flexi Zone Controller Application