SBTS Faults and Alarms

Single RAN, Rel. SRAN 16.2, Operating Documentation, Issue 03

SBTS Faults and Alarms DN09218837 Issue 01B Approval Date 2016-05-24

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 Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. 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 Solutions and Networks 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 Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. 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 © 2016 Nokia Solutions and Networks. 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

distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. 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 © 2016 Nokia Solutions and Networks. 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 Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.

Product”) specified

ou”) only, and it may not Solutions and Networks may be used, copied, permission of Nokia e Product, or if that any manner and You copies thereof.

personnel, and You our comments as part of

tion or statements ct are given solely on orks reserves the right works has made all of material errors and this document. But, limited to the correction software in the Product

UT NOT LIMITED TO RINGEMENT, RELATION TO THE NETWORKS BE ECT, INDIRECT, TED TO LOSS OF R DATA THAT MAY EN IN THE CASE OF

mation, which may not be a Solutions and

ned in this document ation purposes only.

sources of

e handle this

a Solutions and

ned in this document ation purposes only.

sources of

e handle this o this product.

al, Safety and

mental effects of its s to join us in working the recommendations

ronmental services we tion.

1. 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 t 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.

1.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

1.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

1.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.

1.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 ha 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.

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.

and alarm attributes including the

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 hand

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

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 01A and 01B

Alarm Number

Alarm Name

Changed

7100

HARDWARE PROBLEM

Changed

7101

RESET NOTIFICATION

Changed

7102

RESOURCE BLOCKED BY USER

Changed

7103

EXTERNAL ALARM NOTIFICATION

Changed

7104

CELL SERVICE PROBLEM

Changed

7105

RAT BASE STATION PROBLEM

Changed

7106

SINGLE RAN BASE STATION PROBLEM

Changed

7107

BASE STATION CONNECTIVITY PROBLEM

Changed

7108

BASE STATION SYNCHRONIZATION PROBLEM

Changed

7109

BASE STATION SECURITY PROBLEM

Changed

7110

BASE STATION LICENSE LIMITATION

7208

LOCAL BLOCK

7600

BCF FAULTY

7602

BCF NOTIFICATION

7606

TRX FAULTY

7607

TRX OPERATION DEGRADED

7625

PS U-PLANE CONNECTION FAILURE

7995

MAINS BREAKDOWN WITH BATTERY BACKUP

61022

BFD group $bfdGrpId down

61028

LOF on unit $U, interface $IF

61029

LOS on unit $U, interface $IF

61030

Dead Peer Detected

61040

Interface under test on unit $U, interface $IF for $T minutes

61104

EBER on unit $U, interface $IF

61150

LOMF on unit $U, interface $IF

61151

AIS on unit $U, interface $IF

61152

RDI on unit $U, interface $IF

61250

IPCP failure

61251

LCP failure

61252

PPP interface down

61605

BFD $session down, ingress, $sourceIP to $destinationIP

61606

BFD $session down, egress, $sourceIP to $destinationIP

61607

Auto-negotiation mismatch, on unit $U, Ethernet interface $IF

61610

TWAMP RTT threshold crossed on session $id

61611

TWAMP PLR threshold crossed on session $id

61622

MLPPP link degrade

61632

Dup Addr detected $duplicateIpv6Address

61639

IPsec emergency bypass active

61641

IP Traffic Capturing Ongoing [port $port,] [mac $m]

61643

IPsec tunnel switchover

61644

IKE authentication failure

61645

IKE SA failure

61646

IPSec SA failure

Probable Cause

Event Type

Default Severity

Indeterminate

Fault Dependent

N/A

Indeterminate

Fault Dependent

Warning

Indeterminate

Fault Dependent

N/A

Indeterminate

Environmental

N/A

Indeterminate

Fault Dependent

N/A

Indeterminate

Fault Dependent

N/A

Indeterminate

Fault Dependent

N/A

Indeterminate

Communications

N/A

Indeterminate

Fault Dependent

N/A

Indeterminate

Fault Dependent

N/A

Indeterminate

Quality of service

N/A

Indeterminate

Quality of service

Minor

Indeterminate

Fault Dependent

Critical

Indeterminate

Environmental

Minor

Indeterminate

Fault Dependent

Major

Indeterminate

Fault Dependent

Major

Indeterminate

Communications

Major

Indeterminate

Environmental

Minor

Indeterminate

Fault Dependent

Critical

Indeterminate

Fault Dependent

Critical

Indeterminate

Fault Dependent

Critical

Indeterminate

Fault Dependent

Major

Indeterminate

Fault Dependent

Minor

Indeterminate

Fault Dependent

Major

Indeterminate

Fault Dependent

Major

Indeterminate

Fault Dependent

Major

Indeterminate

Fault Dependent

Major

Indeterminate

Fault Dependent

Critical

Indeterminate

Fault Dependent

Major

Indeterminate

Fault Dependent

Critical

Indeterminate

Fault Dependent

Major

Indeterminate

Communications

Major

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

Major

Indeterminate

Communications

Major

Indeterminate

Communications

Major

Meaning

Effect

A hardware fault (or faults) has occurred in the base station. This fault may have an impact on the existing cells across RATs. Check the reason for the fault from the supplementary text field of the Thealarm. device is being reset to recover from a fault

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 SBTS The effect of in the alarmSystem on the Libraries. Network Element

(or faults).

depends on the fault description. For more information, see base station fault in SBTS The service/device has been blocked by the user. descriptions The service/device is System blocked Libraries. by the user. It is not possible to establish phone calls through the blocked cell, module or SBTS. This is an external user-defined alarm. The alarm The effect of the alarm depends on the purpose including the alarm text is defined by the user that was configured for during external alarm configuration the user-defined alarm input in the SBTS. A fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the supplementary text field of the alarm. A fault (or faults) has occurred in the RAT base station. 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 SBTS Libraries. of the The effect of in the fault System on the functioning

network element depends on the fault description. For more information, see base station fault SBTS Libraries. of the A fault (or faults) has occurred in the Single RAN descriptions The effect of in the fault System on the functioning base station. Check the reason for the fault from network element depends the supplementary text field of the alarm. on the fault description. For more information, see base station fault descriptions SBTS Libraries. of the A fault (or faults) has occurred in the base The effect of in the fault System on the functioning station connectivity/interface. Check the reason for the fault from the supplementary text field of the alarm.

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

A fault (or faults) has occurred in the base station synchronization. Check the reason for the network element depends fault from the supplementary text field of the on the fault description. For more information, alarm. see base station fault descriptions SBTS Libraries. of the A fault (or faults) has occurred in the base The effect of in the fault System on the functioning station security. Check the reason for the fault from the supplementary text field of the alarm.

network element depends on the fault description. For more information, see base station fault descriptions in SBTS System Libraries.

Capacity limitation (or limitations) has occurred in the base station due to a missing license. Check the reason for the fault from the supplementary text field of the alarm.

The effect of the fault on the network element depends on the fault description. For more information, see base station fault SBTS Libraries. of the The service/device has been blocked by the user. descriptions The effect of in the fault System on the functioning For details, refer to GSM/EDGE BSS Operating network element depends Documentation. on the fault description. For more information, see base station fault descriptions SBTS Libraries. of the A fault (or faults) has occurred in the BCF. The effect of in the fault System on the functioning For details, refer to GSM/EDGE BSS Operating Documentation. Fault has occurred that disallows OSC/DFCA feature operation. For details, refer to GSM/EDGE BSS Operating Documentation. A fault (or faults) has occurred in the TRX. For details, refer to GSM/EDGE BSS Operating Documentation. Fault has occurred that disallows OSC/DFCA feature operation. For details, refer to GSM/EDGE BSS Operating Documentation. A fault (or faults) has occurred in the (E)GPRS protocol layer. For details, refer to GSM/EDGE BSS Operating Documentation. Main power is lost. Battery backup is switched ON. For details refer to GSM Alarms Documentation: Base Station Alarms (7000-7999); DN9813099

network element depends on the fault description. For more information, see base station fault descriptions SBTS Libraries. of the The effect of in the fault System on the functioning network element depends on the fault description. For more information, see base station fault descriptions SBTS Libraries. of the The effect of in the fault System on the functioning network element depends on the fault description. For more information, see base station fault descriptions SBTS Libraries. of the The effect of in the fault System on the functioning network element depends on the fault description. For more information, see base station fault descriptions SBTS Libraries. of the The effect of in the fault System on the functioning network element depends on the fault description. For more information, see base station fault descriptions SBTS Libraries. of the The effect of in the fault System on the functioning network element depends on the fault description. For more information, see base station fault descriptions in SBTSlink System Libraries. The communication between the local SBTS

The alarm is raised if the service under monitoring is not available, for example, when all and the BFD peer is defective. No network paths are unavailable. This implies that communication is possible. all individual BFD sessions of the respective group areof erroneous. This loss frame alarm is raised when the local Possible impact on the connections over this receiver is unable to detect the frame alignment interface: 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 network This alarm is raised when either no or an No data elements or clock information is exchanged via Probable cause: The interface at the far end is -this loss of synchronization if the interface is used incompatible signal is received on the interface interface. Possible impact on the connections not configured to be a framed E1 interface. as a synchronization source referenced in the alarm text. over this interface: With anpeer Ethernet interface,inthe physical Ethernet A dead was detected one of the IPsec link is detected to be down. All other transmission associations of the SBTS. alarms to this signal suppressed. There isrelated no response to the are requests sent to the peer, neither during the IKE Probable for SA Ethernet SA setup,causes the IPsec setup,interfaces: nor during DPD. Note: When IPsec backup tunnel feature is -enabled, a cable/fiber is cut isornot there is no cable/fiber this alarm raised connected to the interface due to failures when trying to setup primary IPsec tunnel in "Secondary_Active_Probing_Primary" -state. the electrical/optical signal is excessively attenuated - the port at the connected far end node is switched off

-Possible voice calls or data connections are aborted and effects: cannot be established - no calls are possible anymore - loss of remote management access to other -network remote elements management connectivity is lost and cannot be established anymore - IKE SAs and IPsec SAs cannot be established or re-keyed - loss of synchronization if the interface is used as a synchronization source - Depending on use of the Ethernet interface, the above described impact can occur for the local SBTS and/or other (S)BTS elements if they are chained via the Ethernet interface.

This alarm is raised if a loopback has been configured by a management application on the interface mentioned in the alarm text.

The interface cannot be used for transmission. It can be used for connectivity checks only.

This alarm is raised when the measured bit error Possible impact: rate exceeds the threshold value of BER-3 (10E- - slow management access to the SBTS and 3). other network elements in the network - poor voice quality and data performance Probable causes: This loss of the multiframe alarm is raised if the The performance management data collected on -interface the signal level is too or lost cables referenced in low the (connectors alarm text has the this interface becomes invalid. are dirty, electrical connectors or cables are multiframe alignment. corroded) -Probable the specified maximum lengthtype of the is Thewhen interface hascable not been This alarmcause: is raised an alarm indication Possible impact on the connections over the exceeded configured to meetThis the framing ofgenerated the interface at interface in question: signal is received. signal isconnected by an -the thefar connector is not properly to the end. For E1device interfaces, configuration intermediate PDH in thethe forward direction - no calls are possible unit of the far end node should be E1 Multiframe. because it detects problem in its received - the receiver or thea far end transmitter has failed - loss of remote management access to other signal. theconnections RAN - the alarm accumulated of athe end todefect end E1 path network This is raisedBER when remote Possibleelements impact oninthe over this AIS defect is detected when the incoming signal is too high. indication is received. It is sent by the interface: has two or less each of two consecutive intermediate or zeros the farinend equipment because it - no calls are possible double frame periods (512 bits) according detects a serious fault in the received signal. - loss of remote management access to other [G.775] chapters 5.2 and I.2. network theconnections RAN This alarm is raised when the localIPAddress Possibleelements impact oninthe over this Probable cause: The far end has a LOS, LOF or negotiation with the peer fails.related to this interface: All other transmission alarms AIS alarm on its receiving interface. - the SL-PPP/ML-PPP interface is not available. signal are suppressed. - loss of remote management access. Probable There is a and transmission This alarmcause: is raised if local peer endsproblem Possible impact on the connections over this somewhere intermediate network along the PPP link: disagree on in thethe LCP configuration leading to LCP E1 path and AIS is sent instead of user traffic. negotiation failure. - in case of SL-PPP, the interface is not available. The related configuration parameters are : In case of ML-PPP, the interface is degraded (as acfcTarget, localMruTarget, pfcTarget. long as on at least one link is available). This alarm is raised if the PPP interface is not Impact the connections over this interface: loss of remote management access to other operational either when all the PPP-links in the in the RAN. access. ML-PPP interface are not available or the PPP- network - loss of elements remote management link supporting the SL-PPP interface is not available. The alarm is raised if the BFD state for the session is not AdminDown and nevertheless no BFD packet is received at the local end during the detection time. The alarm is raised if the BFD state of the The alarm is raised if the BFD in session is not AdminDown andsession the BFDispacket activated state. from the far end contains the diagnostic code = 'Control Detection Time Expired' and no BFD down Ingress alarm is present. This alarm indicates that there is a mismatch between SBTS expected auto-negotiation result The alarm is raised only if BFD session is in and actual auto-negotiation result. activated state. An link was established link TheEthernet RTT threshold alarm is raisedbut in during case the establishment a link speed downshift event took average value of the RTT for this TWAMP place. link speed downshift takesequals place when sessionA from the last 1-min period or auto-negotiation successfully negotiates a certain exceeds the configured threshold. technology but the link cannot be established with this technology. It is tried then to establish the link with the next lower speed technology.

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. 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 -TWAMP Increased packet delay value, variation and increased session (DSCP packet size) may average delay for all voice/packet and be too small, because the measurement packets management are scheduledconnection later than before. - Increase of packet loss due to congestion.

An Ethernet link was established with 1000Base- - Loss of synchronization/Timing source lost with T technology, but the negotiated clock mode Timing over Packet (IEEE1588v2) due to does not fit to the expected clock mode of increased packet delay variation. synchronous Ethernet. - Loss of synchronization/Timing source lost with The expected clock mode of synchronous Synchronous Ethernet. Ethernet is slave in case an Ethernet interface is

The alarm is raised if the packet loss ratio equals This alarm is an indication that the backhaul or exceeds the configured threshold value during capacity for traffic with same profile as this the current observation interval of 15 minutes. TWAMP session (DSCP value, packet size), may be much too small, because some of the measurement packets operates seem to have been thrown This alarm is raised if at least one of the PPPThe ML-PPP interface with reduced away. links belonging to the ML-PPP interface is not capacity. The TWAMP measurement packets are lost operational. because of degraded traffic throughput. During the IP address configuration the SBTS tests the direct attached network whether, other already configured node, on the network uses already same IPv6 addresses on their network IP interfaces. The DAD (Duplicate address SBTS has entered IPsec emergency bypass detection) detects those duplicated active state where configured IPsecIPv6 policies are addresses prohibits the operation of this ignored andand all traffic is sent unprotected. IPv6 address in the SBTS. The Alarm contains the corresponding IPv6 address and the interface The alarmthe is activated when the IP traffic on which address was configured. For each capturing session is started. DAD event a separate reporting shall be indicated. The SBTS is currently capturing IP traffic towards a local port will or into a file on the SBTS. This alarm be triggered when the primary IPsec tunnel fails and If the traffic capturingover is happening towards SBTS has switched to secondary IPseca local port, the port and destination MAC address tunnel. needs to be provided. As result is ofraised failurewhen of thethe primary IPsec tunnel, Theaalarm IKE authentication SBTS has automatically switched over to credentials provided by the Port valuesIPsec can be LMP or -. Example: LMP or FSM-EIF1, FSM-EIF2 or FTIFEIF1 The alarm is raised, if IKE parameters are not matching with the peer proposal. It can happen due to following two failures --> When the SBTS sends or receives a failure notification asraised response tothe an SBTS IKE_SA_INIT This alarm is when sends or request message. The failure notifications receives following notification as response to an includes: IKE_AUTH or CREATE_CHILD_SA request -message. NO_PROPOSAL_CHOSEN -The INVALID_SYNTAX failure notifications includes the following: -- INVALID_MAJOR VERSION NO_PROPOSAL_CHOSEN -- TS_UNACCEPTABLE INVALID _IKE_SPI -- 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 - SINGLE_PAIR_REQUIRED or include: -FAILED_CP_REQUIRED INVALID_SYNTAX - INVALID_MAJOR VERSION - INVALID _IKE_SPI - INVALID_MESSAGE_ID - UNSUPPORTED_CRITICAL_PAYLOAD

The remote peer to come online with the same IP address on the same subnet as local peer would just disable their network interface and give an error until the situation is resolved by the administrator. All configured IPsec policies are ignored and all This allowstraffic the local peerunprotected. to continue functioning the SBTS is sent without disruption, but completely breaks IP base communications for the connected network. 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 can't be established and used.

Identifying Additional Information Fields

Additional Information Fields

1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, 1. EAC line input ID RET, FYG, or SFP.

1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the 3. Destination IP address impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP.

See description of the related fault

1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. For details, refer to GSM/EDGE BSS Operating For details, refer to GSM/EDGE BSS Operating Documentation. Documentation.

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












Instructions

Please check the below fault-specific description for detailed instructions. ----------------------FAULT NAME 10b8b coding error in Optical Interface device FAULT NAME FAULT ID 10b8b coding error in Optical Interface device 2004: EFaultId_OIC_LVDSRecAl FAULT IDthe service/module with SBTS Element Manager. Unblock MEANING 2004: EFaultId_OIC_LVDSRecAl The fiber cable is experiencing interference; data transmission is faulty. FAULT NAME MEANING Cell blocked A physical connection failure between the optical and is thefaulty. The fiber cable is experiencing interference; data interface transmission summing function has occured(possibly caused by bad circuit joints). The operation depends on the type of alarm that user defined as external FAULT ID alarm. A physical connection failure between the optical interface and the 49: EFaultId_CellBlockedAl INSTRUCTIONS summing function has occured(possibly caused by bad circuit joints). Take theNAME following actions to clear the fault: FAULT MEANING [User defined] INSTRUCTIONS Please check the below description for detailed The user hasRadio blocked thefault-specific cell with the SBTS Element Manager. 1. Reset Module thethe faulty optical interface by instructions. Take the the following actions towith clear fault: blocking/unblocking it. FAULT FAULT ID NAME INSTRUCTIONS 1400: EFaultId_ExtAl0 1. Reset the Module with the faulty optical interface by 10b8b coding errorclear inunblock Optical Interface device To theRadio alarm, the cell. 2. Ifcancel this does not 1401: EFaultId_ExtAl1 blocking/unblocking it. the fault, replace the Radio Module that is causing the alarm. Please check the below fault-specific description for detailed instructions. 1402: FAULTEFaultId_ExtAl2 ID 1403: EFaultId_ExtAl3 2. If this does not clear the fault, replace the Radio Module that is causing 2004: EFaultId_OIC_LVDSRecAl 3. the System Module is the only source of the alarm, or replacing the 1404: EFaultId_ExtAl4 theIfalarm. RF Module does not clear the fault, replace the System Module that is FAULT NAME 1405: EFaultId_ExtAl5 MEANING FAULT NAME causing the alarm. Address mismatch in summing 1406: EFaultId_ExtAl6 3. If the System is the only source ofdata the alarm, or replacing the Please check below fault-specific description for detailed instructions. The fiber cablethe isModule experiencing interference; transmission is faulty. SBTS blocked 1407: EFaultId_ExtAl7 RF Module does not clear the fault, replace the System Module that is FAULT ID 1408: EFaultId_ExtAl8 causing theconnection alarm. FAULT NAME A physical failure between the optical interface and the FAULT ID 2019: EFaultId_Muksu_SsubMmAl 1409: EFaultId_ExtAl9 out of range summing function has occured(possibly caused by bad circuit joints). 50: EFaultId_BTSBlockedAl 1410: EFaultId_ExtAl10 Please check the below fault-specific description for detailed instructions. MEANING 1411: EFaultId_ExtAl11 FAULT ID INSTRUCTIONS MEANING FAULT NAME There is a baseband bus address mismatched in the summing. There are 1412: EFaultId_ExtAl12 4235: EFaultId_VswrThresholdOutOfRangeAl Take the following actions to theElement fault: Manager. The fault indicates The SBTS is causes: blocked withfailure theclear SBTS Antenna FAULT NAME line device HW two possible 1413: EFaultId_ExtAl13 that the alarms that might be raised during a SBTS BTS RNC/Flexi Direct interface signalling link failuremaintenance task 1414: EFaultId_ExtAl14 FAULT NAME MEANING 1. Reset the Radio Module with the faulty optical interface by - after an should be avoided. FAULT ID A configuration error (two different baseband units functioning) 1415: EFaultId_ExtAl15 Antenna Please check link isor the down below fault-specific description for detailed instructions. VSWR major VSWR minor value set is out of range during blocking/unblocking it. 1847: FAULT EFaultId_HardwareErrorAl ID acknowledgment, the fault returns. 1416: EFaultId_ExtAl16 commissioning. INSTRUCTIONS 17: EFaultId_CnbapLinkAl 1417: EFaultId_ExtAl17 FAULT ID NAME 2. Ifcancel this does not the fault, thewhen Radio Module that iscauses causing To the alarm, unblock the replace SBTS. Unblocking of the SBTS MEANING Data corruption onclear the bus - appears once unsynchronized data is a 1418: EFaultId_ExtAl18 476: 2M external EFaultId_Rp3BusError reference missing INSTRUCTIONS the alarm. site reset. A MEANING hardware failure detected by an antenna line device. Usually, this is a sent byEFaultId_ExtAl19 the baseband. 1419: Set the correct VSWR threshold using recommissioning Please check the below fault-specific description detailed instructions. permanent A common NBAP fault (the linkhardware failure has is values occurred broken). thatBTS is for possibly caused by a 1420: EFaultId_ExtAl20 MEANING FAULT ID with VSWR threshold supported by the Radio Module. 3. If the System Module is the only source of the alarm, or replacing the is transmission network problem. The most common reason for this alarm INSTRUCTIONS 1421: EFaultId_ExtAl21 The 1899: Antenna EFaultId_2MExtRefMissAl (RP3) link is down: the transmitter or receiver drops out RF Module does not clear the fault, replace the System Module that isof FAULT NAME INSTRUCTIONS frequent transmission breaking. Check the antenna mapping to the local cells in the commissioning file. 1422: EFaultId_ExtAl22 synchronization. causing the alarm. Automatic Operator Certificate retrieval 1. Block orBTS unblock the Radio Module to giveunsuccessful a power-off reset to the 1423: EFaultId_ExtAl23 MEANING FAULT NAME antenna INSTRUCTIONS line devices. 1424: EFaultId_ExtAl24 INSTRUCTIONS The reference clock monitoring has detected a loss of 2.048 MHz signal Toggling: FAULT IDthe 1. Reset WCDMA SW. 1425: EFaultId_ExtAl25 Perform received the from steps an external below inreference the listedsource, order until connected the faulttodisappears: Sync In 61510: NO_CERTIFICATE 2. If that does not help, replace the antenna line device. interface of the System Module. FAULT NAME FAULT ID 2. Check the SBTS. transmission links to the RNC/Flexi Direct RNC. FAULT NAME MEANING 1. Reset the Address mismatch in summing 4026: MEANING EFaultId_TogglingAl Antenna link is downon the external alarm line. High or NAME low voltage INSTRUCTIONS FAULT A requested certificate could not be retrieved from the certificate authority 3. Check the BTS and RNC/Flexi Direct RNC transmission settings. 2. Note! If that Perform not the help, steps replace below inthe the alarming listed order FSM. until the alarm FAULT IDdoes Antenna line device HW failure MEANING (CA). FAULT IDspecifies the fault text during commissioning. The user disappears. 2019: EFaultId_Muksu_SsubMmAl BTS A requested Fault, certificate fault name could is notmentioned be renewed in the from Fault the certificate name field,authority is FAULT 4. Reset NAME thewhich SBTS. 476: EFaultId_Rp3BusError FAULT ID toggling (CA). in the BTS. The toggling alarm condition is presented to the user Antenna line device missing software INSTRUCTIONS 1. Check the cabling (connected to Sync In interface). MEANING 1847: EFaultId_HardwareErrorAl

Please check the fault-specific description below for detailed instructions. FAULT NAME HSDPA users limitation alarm Please check the below fault-specific description for detailed instructions. FAULT ID 4285: EFaultId_HsdpaUsersLimitationAl MEANING Please check the below description for detailedSW instructions. Not enough #data users fault-specific licenses is available in Centralized License Server. Parameters BTSSCW/numberOfHSDPASet1, BTSSCW/numberOfHSDPASet2, BTSSCW/numberOfHSDPASet3 are to be reduced internally. Please check the below fault-specific description for detailed instructions. INSTRUCTIONS Add #data users licenses to Centralized SW License Server. Please check the below fault-specific description for detailed instructions. FAULT NAME FAULT HSUPANAME users limitation alarm Pipe dangerously overheating Please check the below fault-specific description for detailed instructions. FAULT ID FAULT ID 4286: FAULTEFaultId_HsupaUsersLimitationAl NAME 1938: EFaultId_FrPipeOverheat Pipe dangerously overheating MEANING Please check the below fault-specific description for detailed instructions. MEANING Not enough FAULT ID #data users licenses is available in Centralized SW License The temperature of any PA or Pipe sensor is in to RFbe module equals Server. Parameter BTSSCW/numberOfHSUPASet1 reduced 1938:validated EFaultId_FrPipeOverheat or exceeds the predefined value on the unit property file. internally. MEANING INSTRUCTIONS INSTRUCTIONS Please check the below fault-specific description for in detailed instructions. The validated temperature of any PA or Pipe sensor RF module equals 1. Check the temperature andunit environmental conditions are Add #dataif users licenses tovalue Centralized SW License file. Server. or exceeds the ambient predefined on the property within design limits for the radio module. When the ambient FAULTthe NAME temperature and environmental conditions Mains power break, running battery backupexceed the limits, the alarm INSTRUCTIONS startup is expected and no further actions are needed. conditions are 1. Check Check the if the ambient temperature and environmental 1. availability of IP connectivity. FAULT ID design limits for the radio module. When the ambient within the 2. Check if the airenvironmental flow is not blocked by foreign objects. Makethe sure FAULT 37: EFaultId_MainsBreakAl NAME temperature and conditions limits, alarm 2. Check whether there are active alarms atexceed the farthe end. If found,that follow minimum thermal clearances are followed. Remove any objects might IP traffic capacity limit rate $R level $L raised $T startup is expected and no further actions are needed. the instructions for handling those alarms. be blocking airflow and mount the module according to the instructions MEANING and recommendations. E1 interfaces: Check that thepower interface of the far-end interface is also FAULT There isIDaififfault in the mains supply. The SBTS has received 2. Check the flow is not blocked bytype foreign objects. Make sure a 3. Check thebeair far end has BFD switched ON. configured to a framed E1 interface. If this is not the case, reconfigure 4293: Battery EFaultId_IPTrafficCapacityLimitAl Backup alarm and the intelligent shutdown procedure has started. minimum thermal clearances are followed. Remove any objects that might 3. if excessive sunlight is causing the unit to overheat. Install the the interfaces so that they match each other. beCheck blocking airflow and mount the module according to the instructions sunshield following the mounting instructions and recommendations. MEANING INSTRUCTIONS and recommendations. Licenses Check thethat are mains missing power since supply. theare time ($T) indicated the fault name. The 1. Check the cables/fibers connected to theincorrect connectors. IP Check traffic isif throttled tosunlight the peakisrate ($R),the at the ($L) indicated 3. excessive causing unitlevel to overheat. Install in thethe fault name. Level denotes a per of the maximum IP trafficon throughput sunshield following the mounting instructions and recommendations. 2. Check that the interface at the cent far-end interface is switched and has in a 15-minutes interval before the fault has been raised. For every expiry correct auto-negotiation settings. FAULT of sevenNAME days (after missing licenses have been detected) at time($T), the Unit 1. Check (module) availability dangerously of IP overheating connectivity. level ($L) the decreases by 5%. When the level ($L)far changesIf then a newfollow 3. Check whether there are active alarms at 2. Check whether there are active at the the far end. end. If there there are, are, follow alarm is raised. for handling those alarms the instructions alarms. FAULT the instructions ID for handling those alarms. FAULT NAME 1937: EFaultId_FrDangerouslyOverheat Time: The "$T" format is a local stamp (GMT+/-xx:xx). For example: Unit overheating 4. To(module) verify thatdangerously the hardware of time the interface works correctly, connect a 2014-04-12 00:51:26 GMT+0530 loop cable and check whether the alarm disappears. MEANING Level ($L): FAULT ID 100% to 50% in 5% steps The validated sensor temperature exceeds or is equal to the predefined Rate ($R): current policed peak rate 1937: EFaultId_FrDangerouslyOverheat 5. Check that the property length/type value on the unit file.of the cable/fiber does not introduce excessive attenuation or that the cable/fiber is cut somewhere. MEANING INSTRUCTIONS INSTRUCTIONS The validated sensor temperature exceeds or is auto-negotiation equal to the predefined 6. Check that the Ethernet interface has settings, 1. Check if the temperature and correct environmental conditions are Add licenses toambient CLS value on the unit property file. fitting to the far-end interface. within the designed limits for the radio module. When the ambient temperature and environmental conditions exceed the limits, the alarm INSTRUCTIONS 7. With is anexpected optical Ethernet interface: Check that the inserted SFP module startup and temperature no further actions are needed. 1. Check the if the ambient andofenvironmental conditions matches fiber type and wavelength the Gigabit Ethernet link are

Switch off the loopback or wait for the timeout to expire which opens the loop and cancels the alarm.

1. Clean the cables and connectors. 2. Check that the connectors are properly connected to the unit. 3. Check that cable connected the matches interfacethe in question is not Check that thethe configured interfacetotype configured interface damaged and is within the specifications. type of the far end. If this is the case, the problem is somewhere in the 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 for this interface. Check ifappear 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 to at the the SLlocal end Check for LCP failure alarms of the PPP-links belonging or PPP/ML-PPP interface and follow the instructions of these alarms. peer if there is arelated mismatch. Check all PDH 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 a link speed downshift 1. Check the backhaul usage and if by other applications with theevent. same or higher PHB may compete against this TWAMP session about the 2.1 CheckAn that the cables are fully plugged in tosession the connectors. capacity. increase in the priority of TWAMP or of the backhaul capacity may clear the alarm. 2.2 Checkthe that a CAT5e or higher Category cable is used 2. Check last measured RTT values of this TWAMP session and verify that the configured RTT threshold value is not too close to average 2.3 Replace thevalues, cable. so that this alarm could be result of sporadic mismeasured RTT measurement. 3. If the clock mode of the local Ethernet interface is slave and the Ethernet interface is configured to serve as synchronization source, then the alarm is caused by a clock mode mismatch. 3.1 Check the clock mode setting of the remote link partner. It should be either "multiport device" or "manual master".

1. Check the backhaul usage and if other applications with the same or higher PHB may compete against this TWAMP session about the capacity. An increase in the priority of TWAMP session or of the backhaul capacity may clear the alarm. 2. Check destination is unreachable by IP connectivity Send an Check theif LCP failure alarms of the PPP-links belongingtest. to the ML-PPP ICMP echo request (ping) to the UDP port of the TWAMP reflector at the 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 but you have access to TWAMP reflector, you can check its status. If the status is disabled or down try to activate it again and check if 1.Check for duplicate IPv6 addresses configured in the SBTS. alarm disappears. 2.Change or delete the identified duplicate 3. Check configured PLR threshold. SettingIPv6 PLRaddresses. to 0% should be avoided, because every lost measurement packet will trigger the alarm and it cannot be cleared again (PLR>=0). Start IPsec emergency bypass by making the security gateway not reachable either by plugging out the cable or configuring wrong security gateway address. Stop IP traffic capture from WebUI page.

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

1037699495214215216217218180618151834183518361839184018411842184318441845184618471848185418691870187 • RP000911: SBTS HW Management • RP000924: SBTS Intelligent shutdown • RP000940: SBTS Diagnostics and Self Test • RP000367: Small Form Factor Pluggable Slot (SFP slot) SBTS HW Management 10121610911011112512813914915841847618061854189319001901190319041905190719101911191219261956200020012 • RP000911: •• RP000910: RP000980: SBTS SBTS Antenna RecoveryLine Management •• RP001052: LTE feature parity RP000847: BTS Synchronization mode •support RP000980: SBTS Recovery •• RP000956: and runtime LTE656: LTESBTS FaultStartup Management 4849504026 •management RP000923: SBTS State Transitions •• RP001016: inside SBTS LTE656: LTESBTS FaultOMUSIG Management SBTS OMUSIG inside SBTS • RP001016: RAN1671: Enhanced UltraSite Base Band •(EUBB) LTE656: LTE Fault Management

• 10457: field report of routing component 1400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424 • RP000956: and runtime RP000920: SBTS Startup Fault Management management • LTE656: LTE Fault Management

10232838399495103109110111115116125128133134154160161476180618071834183518361837183818391840184118421 • RP000911: SBTS HW Management • RP000912: SBTS SW Management • RP000910: SBTS Antenna Line Management • RP000924: SBTS Intelligent shutdown •• RAN1671: UltraSite Measurement Base Band 1288109110111124130139145146149154157158418420476180618932006200720082009201020192057205820592060206 ARAN1163:Enhanced Iu-PS Throughput (EUBB) for GTP Traffic •• RP001052: feature parity RP000980: LTE SBTS Recovery •• RP000980: SBTS Recovery LTE656: LTE Fault Management •• LTE435d: CN5259 New alarm to RF SW to RP001016: SBTS OMUSIG inside SBTS 2232427282930418420180618111900190119021905190719081910191119241927195519561958200620072008200920102 •indicate RP000956: SBTS Startup and runtime RP3 collision problems •management RAN1671: Enhanced UltraSite Base Band •(EUBB) RP000956: SBTS Startup and runtime •management RP000912: SBTS SW Management •• RAN1263i: GenericNew RAKE for HSPA baseband LTE435d: CN5259 alarm to RF SW to RP000788: 1PPS&ToD Sync from external efficiency final implementation indicate RP3 collision problems GNSS Receiver 1718114402661506202620362046205620662616284630363046308631763216322632368506851 • RP000980: SBTS Recovery •• RAN2262: Multimode System Modules RP001016: SBTS OMUSIGsupport inside SBTS RP000941:Flexi Datacollectors FSMF and FSMG •• LTE656: LTE656: LTE LTE Fault Fault Management Management • RP000920: SBTS Fault Management • LTE656: LTEreport Fault of Management 10457: field routing component 9162618171818181918981899190319041926200520132014205240114019402641144122412341244125412642104297429 • RP000847: RP001016: BTS SBTSSynchronization OMUSIG insidemode SBTS support • RP000929: SBTS Configuration Management • RP000384: over Packet RP000910: Timing SBTS Antenna LineResilience Management • RP000996: SRAN Clock time management •• RP000375: Ethernet 4026414542664267426842696107461510616166161861642 LTE656: LTESynchronous Fault Management •• RP000788: 1PPS&ToD Sync from external RP000912: SBTS SW Management GNSS Receiver • RP000900: SBTS user account management •• RP000357: E1 Interface RP000845: Symmetrical SBTS Operator Certificate •Management RP000979: interface between system modules • RP000376: Synchronization from 2.048MHz signal • RP000377: Synchronization from PDH interface • LTE656: LTE Fault Management • RP000980: SBTS Recovery • RAN2262: Flexi Multimode System Modules FSMF and FSMG

40264285428642874293

• LTE656: LTE Fault Management • RP001004: SBTS Data User RTU • RP000834: IP Traffic Capacity

#N/A

#N/A

#N/A

#N/A

#N/A

#N/A

19371938

19371938

#N/A

#N/A

37

• RP000924: SBTS Intelligent shutdown

61022

• RP000361: Link Supervision with BFD

61028

• RP000357: Symmetrical E1 Interface

61029

• RP000910: SBTS Antenna Line Management

61030

• RP000356: IPsec for BTS

61040


61104


61150


61151


61152


61250

• RP000176: MLPPP termination

61251


61252


61605


61606


61607

• RP000365: Electrical 10/100/1000-Base-T Interface

61610

• RP000360: IP Transport Network Measurements

61611


61622


61632

• RP000589: IPv4/IPv6 Transport Stack

61639

• RP000439: IPsec Emergency Bypass

61641

• RP000465: Local and Remote IP Traffic Capturing

61643

• RP000600: Backup IPsec Tunnel

61644


61645


61646


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.

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 service/device is unblocked by user.



Do not cancel the alarm. The system automatically cancels 0 the alarm when the fault has been corrected. [All except VSWR major alarm 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. 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 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 any BFD sessions to belonging to thatframe BFD As soon as afor signal that conforms the expected group is available again. format is received, the alarm will be cancelled.

0

0

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 protect policy. Note: When IPsec backup tunnel feature is enabled, DPD alarm due to the primary tunnel failure shall be cleared when switch-over is successful for all primary tunnels(that is, all secondary tunnels are successfully established). Similarly, any DPD alarm raised due to secondary tunnel

0

SW registers the expiration of the loopback timer.

0

As soon as the EBER is not exceeded anymore, the alarm is canceled.

0

As soon as a multiframe signal is detected, the alarm is cancelled. The Device Driver software reads the alarm status directly from the HW chip.

0

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.

0

As soon there is no remote defect indication received on the interface, the alarm is canceled.

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, 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 cancelled. For anisactive BFD session SBTS checks continuously the

0

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 BFD packets from its 0 The alarm is cancelled once error-free an auto-negotiation process BFD peer. has taken place, which does not generate a downshift event nor a clock mode which does not fit to the synchronous Ethernet configuration. The alarm will be cleared, if during 5 consecutive 1-min 0 In case a clock modevalue mismatch cause of thebelow alarm,the then periods the average of theisRTT remains the alarm is cancelled as well, when removing the Ethernet threshold. interface from the SBTS synchronization priority list (in case clock mode is clock master).

The alarm will be cleared, after at least 2 observation periods are error free again.

0

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. applies towhen the following state The alarmThis is cancelled the IKE SA fortransitions: 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 forcleared the related policy or an failure notification This alarm is 0 which will result raising this alarm. - when the SBTSinto sends or receives an IKE_AUTH_RESPONSE message without a failure Note: please not all notifications above are send by notification fornot thethat 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 01A and 01B

Fault ID

2

9

10

12

16

17

18

23

24

26

27

28

29

30

37

38

39

48

49

50

69

88

94

95

103

109

110

111

114

115

116

124

125

128

130

133

134

139

145

146

149

154

157

158

160

161

214

215

216

217

218

418

420

476

1400

1401

1402

1403

1404

1405

1406

1407

1408

1409

1410

1411

1412

1413

1414

1415

1416

1417

1418

1419

1420

1421

1422

1423

1424

1425

1806

1807

1811

1815

1817

1818

1819

1834

1835

1836

1837

1838

1839

1840

1841

1842

1843

1844

1845

1846

1847

1848

1850

New

1854

1869

1870

1871

1872

1873

1874

1893

1898

1899

1900

1901

1902

1903

1904

1905

1906

1907

1908

1910

1911

1912

1920

1921

1922

1923

1924

1925

1926

1927

1928

1932

1933

1934

1935

1936

1937

1938

1955

1956

1957

1958

1982

2000

2001

2002

2004

2005

2006

2007

2008

2009

2010

2011

2013

2014

2017

2019

2052

2054

2056

2057

2058

2059

2060

2061

2073

Changed

2074

2326

2400

2401

2402

2403

2404

2405

2406

New

2407

4001

4011

4019

4026

4029

New

4047

New

4048

4052

4064

4069

4072

4073

Changed

4077

4078

4079

4080

Changed

4082

Changed

4083

Changed

4085

4090

4114

Changed

4122

Changed

4123

Changed

4124

Changed

4125

Changed

4126

4145

4208

4210

4231

4235

4266

4267

4268

4269

4270

4285

4286

4287

4293

4294

4297

4298

4299

4300

4304

4308

4321

4323

New

4366

Changed

6051

6053

6112

6117

6118

6120

6121

6150

6202

6203

6204

6205

6206

6252

6253

6257

6261

6262

6263

6264

6265

6268

6269

6270

6274

6277

6278

6279

Changed

6280

6281

6282

6283

6284

6285

6286

6291

6292

6293

6303

6304

6308

6317

6321

6322

6323

6351

6701

6706

6707

6708

6850

6851

6852

6853

6854

61022

61028

61029

61030

61040

61050

61074

61079

61104

61150

61151

61152

61201

61250

61251

61252

61510

61605

61606

61607

61610

61611

61616

61618

61622

61623

61624

61631

61632

61634

61639

61641

61642

61643

61644

61645

61646

1825

1931

4153

61500

Fault Name

Used in Product

Unit temperature is high

SBTS

Difference between BTS master clock and reference frequency

SBTS

No connection to unit

SBTS

Baseband resources mapping to cells failure

SBTS

Unit synchronization failed

SBTS

BTS RNC/Flexi Direct interface signalling link failure

SBTS

BTS RNC/Flexi Direct interface signalling link failure

SBTS

Incompatible SW version detected in unit:

SBTS

Obsolete SW version detected

SBTS

BTS time not corrected

SBTS

Error in file server during file download type

SBTS

File corrupted in SW download

SBTS

BTS SW download or activation failed

SBTS

BTS SW download or activation failed

SBTS

Mains power break, running battery backup

SBTS

Delayed cell shutdown alarm

SBTS

Immediate cell shutdown alarm

SBTS

Unit blocked

SBTS

Cell blocked

SBTS

SBTS blocked

SBTS

POST test failed

SBTS

Missing NBAP cell parameters, defaults are used

SBTS

Unknown HW resource

SBTS

Unit not supported by running SW

SBTS

Carrier power measurement fault

SBTS

Telecom configuration failure

SBTS


SBTS


SBTS

Communication failure with RNC

SBTS

Telecom cell enabling or disabling failed

SBTS

Telecom cell enabling or disabling failed

SBTS

Not enough DSP capacity to set up a cell

SBTS

Cell power monitoring

SBTS

BTS config error (Wrong LTX Frequency Order) SBTS

Not enough resources for commissioned HSUPA

SBTS

Rx signal level failure

SBTS

Rx signal level failure

SBTS

DSP mode change failed

SBTS

Resource block not available

SBTS

Resource block occupied by high priority services

SBTS

Ten consecutive Nacks received from a DSP at SBTS DCH setup

PIC pool configuration failure

SBTS

Not enough CCCH Processing Set licenses commissioned

SBTS

Hanging HSPA resources

SBTS

One of the Common Transport Channels is deleted

SBTS

Not enough CCCH processing capacity to setup cell

SBTS

Flash operation failure

SBTS


SBTS


SBTS


SBTS


SBTS

Fatal OSE error

SBTS

Out Of Frame Data Error

SBTS

Antenna link is down

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

[User defined]

SBTS

Communication failure

SBTS

Invalid frequency channel for the BTS HW

SBTS

Baseband bus configuration was rejected

SBTS

Not able to synchronize baseband bus

SBTS

Oven oscillator heating failure

SBTS

BTS master clock tuning failure

SBTS

Oven oscillator clock missing

SBTS

Mast Head Amplifier above current window fault,

SBTS

Mast Head Amplifier below current window fault,

SBTS

Antenna line failure

SBTS

VSWR major alarm

SBTS

VSWR minor alarm

SBTS

Low noise amplifier failure

SBTS

Filter unit operation failed

SBTS

Filter unit faulty

SBTS

RET antenna control failure

SBTS


SBTS


SBTS


SBTS


SBTS

Antenna line device HW failure

SBTS

Antenna line device missing software

SBTS

SW corrupted

SBTS

FSP faulty

SBTS

MHA unit operation failure

SBTS

MHA operation failure

SBTS

Antenna line device operation failure

SBTS


SBTS


SBTS


SBTS

Internal delay measurement failure

SBTS

PPS reference missing

SBTS

2M external reference missing

SBTS

RF Module configuring failed

SBTS

RF Module critical file not found

SBTS

RF Module file not found

SBTS

Frame clock missing

SBTS

RF BB bus synchronization error

SBTS

RF BB bus configuration error

SBTS

RF BB bus connection transmission error

SBTS

TX out of order

SBTS

RF Module gain adjusting failure

SBTS

RF Module filter input power missing

SBTS

RX out of order

SBTS

RF Module out of order

SBTS

No feedback signal

SBTS

Transmission quality deteriorated

SBTS

Temperature too low (heating ongoing)

SBTS

Unit unidentified

SBTS

Configuration file corrupted

SBTS

Post test failed

SBTS

Module clock faulty

SBTS

RF power decreased

SBTS

FPGA SW update failed

SBTS

No module fan detected

SBTS

Cooling fan broken

SBTS

Cooling fan has reduced from the set speed

SBTS

Cooling fan is overspeeding

SBTS

Unit (module) temperature is high

SBTS

Unit (module) dangerously overheating

SBTS

Pipe dangerously overheating

SBTS

Increased BER detected on the optical connection to Radio Module

SBTS

Critical BER detected on the optical connection SBTS to Radio Module

Antenna line switched off

SBTS

RP3 routing collisions are detected on FR module

SBTS

RF Module External Alarm and Control lines configuration failed

SBTS

Optical interface faulty

SBTS

Optical interface faulty

SBTS

Receiving failure in optical interface

SBTS

10b8b coding error in Optical Interface device

SBTS

Synchronization failure in Optical Interface

Optical interface data/control/Ethernet buffer full

SBTS


SBTS


SBTS


SBTS


SBTS

OIC MCU Buffer Full

SBTS

Frame burst receiving fault

SBTS

Frame clock deviation fault

SBTS

BB bus transmission error

SBTS

Address mismatch in summing

SBTS

RP1 synchronization burst error

SBTS

Buffer over/underflow in clock crossing logic

SBTS

Firmware SW mismatch

SBTS

BB bus message in the wrong slot

SBTS

Message routing problem in receiver (RX)

SBTS

Summing not enabled for message type

SBTS

Transmission rule collision in Muksu

SBTS

Overload collision in transmitter

SBTS

SRIO enumeration

SBTS

SRIO retry stopped

SBTS

SRIO link degradation

SBTS

TRX initialization failure

SBTS

TRX control plane link failure

SBTS

TRX OBSAI failure

SBTS

TRX SBTS configuration mismatch between BSC and BTS

TRX RSSI failure on antenna

SBTS

Incorrect sector configuration for TRX

SBTS

TRX user plane link failure

SBTS

One of the radio modules in centralized configuration is not in working state

SBTS

BTS reset required

SBTS

GPS Receiver alarm: control interface not available

SBTS

Master unit has lost connection to the slave unit SBTS

Toggling:

SBTS

SW corrupted

SBTS

Antenna line device SW download failure

SBTS

Antenna line device SW download failure

SBTS

No connection to unit

SBTS

Missing RP3-01 link

SBTS

RS485 IUANT port failure

SBTS

Parallel RP3-01 link length mismatch

SBTS

Fan vendor not detected

SBTS

FSP overheating

SBTS

Cooling fan broken

SBTS

Cooling fan speed decreased

SBTS

Cooling fan is over speeding

SBTS

SW fallback

SBTS

SW fallback

SBTS

SW fallback

SBTS

Cell power failure

SBTS

Synchronization master missing

SBTS

GPS receiver alarm: not tracking satellites

SBTS

GPS receiver alarm: survey in progress

SBTS

GPS receiver alarm: no stored position

SBTS

GPS receiver alarm: position questionable

SBTS

GPS receiver alarm: EEPROM invalid

SBTS

Validation of signed file failed

SBTS

Unit initialization failure

SBTS

External GPS receiver in holdover

SBTS

Internal baseband bus synchronization error

SBTS

out of range

SBTS

Failure to verify the signature of a signed software release

SBTS

Failure to verify a signed software release

SBTS

Unsigned software release has been successfully downloaded

SBTS

Failure to download software due to missing software signature

SBTS

MHA in bypass mode

SBTS

HSDPA users limitation alarm

SBTS

HSUPA users limitation alarm

SBTS

LTE users limitation alarm

SBTS

IP traffic capacity limit rate $R level $L raised $T

SBTS

SBTS reset required to use hot inserted baseband extension module

SBTS

NTP Server $IP unavailable

SBTS

ToP reference missing

SBTS

Synchronous Ethernet reference missing

SBTS

PDH reference missing

SBTS

Too long fiber for mDTX activation

SBTS

Micro DTX configuration failure

SBTS

Configuration change rejected by BTS

SBTS

ToP configuration mismatch

SBTS

RAT critical application failed

SBTS

Beamforming calibration failure in RF data path SBTS

U-plane overload detected

SBTS

Phich Power Boost not applied

SBTS

High interference to UL subframe

SBTS

High interference to UL special subframe

SBTS


SBTS


SBTS

GTP-U Path Failure

SBTS

Transport layer connection failure in S1 interface

SBTS

Transport layer connection failure in X2 interface

SBTS

S1 SCTP path failure

SBTS

Transport layer connection failure in M3 interface

SBTS

M3 SCTP path failure

SBTS

Incorrect radio network parameters

SBTS

Cell configuration data distribution failed

SBTS

Cell reconfiguration data distribution failed

SBTS

Failure in connection between SBTS and 3rd party tool

SBTS

BTS vendor-specific file fault

SBTS

Failure in trace session

SBTS

No MME capacity assigned by Core Network

SBTS

Maximum number of neighbor eNBs/cells exceeded

SBTS

Maximum number of WCDMA neighbor cells is SBTS exceeded

Maximum number of WCDMA neighbor relations is exceeded

SBTS

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

SBTS

Neighbor cell ambiguity detected

SBTS

Automatic cell recovery not possible

SBTS

MFBI cell configuration conflict

SBTS

PCI confusion detected

SBTS

Phase error exceeds 5 us limit

SBTS

WCDMA PSC confusion detected

SBTS

Inter eNB CA parameter(s) inconsistency in between eNBs

SBTS

Inter eNB SW inconsistency in between cluster SBTS members

Inter eNB communication failure

SBTS

Overload detected: max number of neighbor relation objects reached

SBTS

Overload monitoring: High number of neighbor SBTS related objects

Carrier aggregation relation configuration error SBTS

Resource pool configuration failed

SBTS

eNB configuration failed

SBTS

X2 interface recovery failure

SBTS

X2 interface setup failure

SBTS

S1 interface setup failure

SBTS

S1 interface recovery failure

SBTS

S1 eNB configuration update failure

SBTS

RIM interface timeout

SBTS

RIM interface error

SBTS

System information broadcast parameters overflow

SBTS

Critical bit toggling error

SBTS

DSP platform fatal error

SBTS

DSP application fatal error

SBTS

Externally triggered DSP fatal error

SBTS

M3 interface recovery failure

SBTS

M3 interface setup failure

SBTS

MBMS subframe pattern share exceeds available share

SBTS

MBMS session cannot be resumed

SBTS

MCE configuration update failure

SBTS

BFD group $bfdGrpId down

SBTS

LOF on unit $U, interface $IF

SBTS

LOS on unit $U, interface $IF

SBTS

Dead Peer Detected

SBTS

Interface under test on unit $U, interface $IF for SBTS $T minutes

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

SBTS

CRL Update Failure

SBTS

SFP HW Failure on unit $U, interface $IF

SBTS

EBER on unit $U, interface $IF

SBTS

LOMF on slot $U, interface $IF

SBTS

AIS on unit $U, interface $IF

SBTS

RDI on unit $U, interface $IF

SBTS

Transport module missing: $U

SBTS

IPCP Failure

SBTS

LCP failure

SBTS

PPP Interface down

SBTS

Automatic BTS Operator Certificate retrieval unsuccessful

SBTS

BFD $session down, ingress, $sourceIP to $destinationIP

SBTS

BFD $session down, egress, $sourceIP to $destinationIP

SBTS

Auto-negotiation mismatch, on unit $U, Ethernet interface $IF

SBTS

TWAMP RTT threshold crossed on session $id SBTS

TWAMP PLR threshold crossed on session $id SBTS

Vendor BTS certificate is about to expire

SBTS

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

MLPPP link Degrade

SBTS

SyncE SSM Timed Out on unit $UID, interface $IF

SBTS

SyncE Quality Level Degraded on unit $UID, interface $IF

SBTS

ToP master service $IP unusable

SBTS

Dup Addr detected $duplicateIpv6Address

SBTS

Unsupported HW device

SBTS

IPsec emergency bypass active

SBTS

IP Traffic Capturing Ongoing [port $port,] [mac $m]

SBTS

BTS Local OAM user account $A has been locked

SBTS

IPSec tunnel switchover

SBTS

IKE authentication failure

SBTS

IKE SA failure

SBTS

IPSec SA failure

SBTS

Transmission parameters missing

SBTS

RF Module blocked

SBTS

Reference clock missing in startup

SBTS

Five failed logins to SBTS due to wrong user name or password

SBTS

Detecting Unit

Source

FCT

FCT, FSP

FCT

FCT

FCT

FSP, FT, ALD, FR, FCT, FBB For fault 4052 the only source is FBB

FCT

RAT

FCT

FCT

FCT

CNBAP link

FCT

DNBAP link

FCT

FCT, Radio Module, FF, FSP

FCT

FCT

FCT

TIME

FCT

FCT

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT

FCT

LCR

FCT

LCR

FCT

FR

FCT

LCR

FCT

FCT

FCT, FT, FSP

FSP, FT, FCT, DSP

FSM;

FCT

FCT

- FBB - FR - FT

FCT

FSP, FR

FSM

Tx-n/Rx1-n

FSP, FCT

FSP, Radio Module, DSP

FSP, FCT


FSP, FCT


FCT

FCT

FCT, FSP

LCR

FCT, FSP

LCR

FCT

FCT

FSM

TX antenna service

FSM

FR

FCT

FCT

FSM

Antenna Line

FSM

Antenna Line

FSM

DSP

FCT

FCT

FCT

FCT

FCT

DSP

FCT

LCR,FCT

FCT

FCT

FCT

DSP

FCT

LCR

FCT

FCT

FCT, FSP

FCT, FSP

FCT, FSP

FCT, FSP

FCT, FSP

FCT, FSP

FCT, FSP

FCT, FSP

FCT, FSP

FCT, FSP

FSP

DSP

FSP

DSP

FSP

DSP

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

FCT

FCT, Radio Module

All units can use this fault

Any unit of the BTS.

FCT

LCR

FCT

HWPORT, DSP, FSP, FR

FCT

OptIF (HWPORT)

FCT

FCT

FCT

FCT

FCT

FCT

Radio Module

MHA

Radio Module

MHA

Radio Module

Antenna line

Radio Module

Antenna line

Radio Module

Antenna line

Radio Module

RX antenna service

Radio Module

TX/RX antenna services

Radio Module

TX/RX antenna services

RET

RET

RET

RET

RET

RET

RET

RET

RET

RET

RET, AISG MHA

RET, AISG MHA

RET, AISG MHA

RET, AISG MHA

FCT

Filter, Radio Module

FCT

FSP MCU

AISG MHA

AISG MHA

AISG MHA

AISG MHA

FCT

RET, AISG MHA

FCT

RET, AISG MHA

FCT

RET, AISG MHA

FCT

RET, AISG MHA

FSP, FCT

DSP

FCT

GNSSE, SYNCHUBBTS

FCT

EXT2M

Radio Module, FCT

Radio Module

Radio Module

Radio Module

Radio Module

Radio Module

Radio Module

Radio Module, RX antenna service

Radio Module

Radio Module, TX/ RX antenna service

Radio Module

TX/RX antenna service

Radio Module

Radio Module, TX antenna service

Radio Module

TX antenna service

Radio Module

TX antenna service

Radio Module

Antenna line

Radio Module

RX antenna service

Radio Module

Radio Module

Radio Module

TX antenna service

Radio Module

Antenna line

Radio Module

Radio Module

Radio Module

Radio Module

Radio Module

Radio Module, TX/RX antenna service

Radio Module

Radio Module

Radio Module

Radio Module

Radio Module

TX antenna service

Radio Module

Radio Module

FR

FAN, FAN_GROUP

FR

FAN_GROUP

FR

FAN, FAN_GROUP

FR

FAN, FAN_GROUP

FR/RFSW

FR

FR/RFSW

FR [AAS]: FR, TX1-n / RX1-n

FR/RFSW

TX1-n

Radio Module

Radio Module

Radio Module

Radio Module

FR

Antenna line

Radio Module

Radio Module

Radio Module, FCT

Radio Module

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

OptIF

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT, FSP

FCT

FCT

FCT

OptIf

FCT

FCT

FCT

FSP

FCT

FSP

FCT

FSP

FCT

FSP

FCT

FSP

FCT

FCT

FCT

FSP, FCT, FBB, DSP

FSP

DSP

FCT

LCR

FCT

LCR

FCT

LCR

FCT

FCT

FCT

LCR

FCT

FCT

FCT

LCR

FCT

LCR

FSM

FSM

FCT

GNSSE

FCT

FCT, FSP, DSP

FSM

FSM, Radio Module

FCT

Filter, Radio Module

FCT

RET

FCT

RET

FCT

FSP, FT, ALD, FR, FCT, FBB For fault 4052 the only source is FBB

FCT

RX, TX

Radio Module

Antenna line

FCT

OptIF

FCT

FAN1-n

FCT

FSP

FCT

Fan/Fan group

FCT

Fan/Fan group

FCT

Fan/Fan group

FCT

FCT

FCT

FCT

FCT

FCT

FCT

AxC TX carrier

FCT

FCT

FCT

GNSSE

FCT

GNSSE

FCT

GNSSE

FCT

GNSS

FCT

GNSSE

FCT

FCT

FCT

FCT

FCT

GNSSE, SYNCHUBBTS

FCT

FSP

FCT

Antenna line

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

AISG MHA

AISG MHA

FSM

RAT

FSM

RAT

FSM

RAT

SBTS: FSM

SBTS: CAPLIM

FCT

FBB

FCT

TIME

FCT

TOP

FCT

SYNCE-1

FCT

PDH-x

FCT

OptIF

FSM

FR

FCT

FSMr3: FCT

FCT

TOP

FCT, FSP

WCDMA, LTE

FSP, FBB

LCR

FSP

LCR

FCT

LCR

FSP, FBB

LCR

FSP, FBB

LCR

FSP

LCR

FSP

LCR

FCT

GTP-U

FCT

LNMME

FCT

LNADJ

FCT

LNMME

FCT

LNM3

FCT

LNM3

FCT

FCT

FCT

LCR

FCT

LCR

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

LCR

FCT

LCR

LNADJ

LNADJ

FCT

LCR

FCT

FCT

FCT

LCR

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FCT

FSP

FCT

FCT

FCT

LNADJ

FCT

LNADJ

FCT

LNMME

FCT

LNMME

FCT

LNMME

FCT

LNADJG LNADJW

FCT

LNADJG LNADJW

FCT

LCR

FSP

FSP

FCT

DSP

FCT, DSP

DSP

FCT, DSP

DSP

FCT

LNM3

FCT

LNM3

FCT

FCT

FCT

FCT

FCT

FCT

FCT,FTIF

BFDGRP

FCT,FTIF

PPTT

FCT,FTIF

ETHLK, PPTT

FCT,FTIF

IKEP

FCT,FTIF

PPTT

FCT, FTIF

SFP

FCT

CRLH

FCT, FTIF

SFP

FCT,FTIF

PPTT

FCT,FTIF

PPTT

FCT,FTIF

PPTT

FCT,FTIF

PPTT

FSM

FSM

FCT,FTIF

P3SL; P3ML

FCT,FTIF

P3LP

FCT,FTIF

P3ML, P3SL

FCT

CMP

FCT,FTIF

BFD

FCT,FTIF

BFD

FCT,FTIF

ETHLK

FCT,FTIF

TWAMP

FCT,FTIF

TWAMP

FSM, FTIF

CERTH

FCT

CACERT

FCT,FTIF

P3ML

FCT

SYNCE-x

FCT

SYNCE-x

FCT

TOP

FCT,FTIF

IPIF

FSM

FSM

FCT,FTIF

IPSECC

FCT,FTIF

IPNO

FCT

SBTS

FCT,FTIF

IKEPROTGRP

FCT,FTIF

IKEP

FCT,FTIF

IKEP

FCT,FTIF

SECPOL

FCT

FCT

FR

FR

FCT

FCT

FSM, FTIF

NE-FTM-1

Meaning

State

The temperature of the unit/module exceeds the threshold value.

Start / Cancel

The reference frequency that the BTS Start / Cancel master clock receives has changed by about 200ppb or more (which equals the change magnitude of 204 DAC steps or more (with 12bit DAC)) during the to the Start / Cancel Connection to a module belonging measurement period, compared SBTS configuration has been losttoorthe FSP BTS master clock frequency. cannot be detected. The cause of the alarm can be: A was detected whenhas NodeB O&M 1. failure The reference frequency changed system FSPs to becausepresented of a fault available in the transmission WCDMA and LTE RAT software inturn order network synchronization (which in is to map FSPs to cell. The FSPs related to caused by an equipment fault or a setting the faulty operation may not be utilized. error). Note that if the network Meaning can be: The reason forsite the failure is an internal synchronization malfunction lasts for a 1. The BTS is level phase problem with the NodeB O&M system. long time, the alarm is cancelled when synchronized only (e.g. via 1PPS/ToD the frequency reaches the faulty syncBTS chain), the synchronization Master reference synchronization. The has alarm can is frequency synchronized and A common NBAP iflink has also be activated thefailure faulty reference aquired newisarbitrary phase due toa occurredathat possibly caused by synchronization is corrected and there is, reset. transmission network problem. The most again, a difference of 0.2 ppm or more. common reason for thiswhenever alarm is frequent The alarm cancelled 2. The BTSiswas at holdover for a the long transmission breaking. difference becomes less than 0.2Protocol ppm. A dedicated Node-B Application period and the accumulated phase drift (NBAP) link failure has occurred, possibly has exceeded +-5ms. 2. The reference frequency fluctuates caused by the RNC. continuously because of a significant 3. BTS Internal synchronization between amount of jitter/wander in -the units (e.g. FCT/FSP/FBB DSP) has A new unit with an incompatible transmission network. The alarmSW is failed. might have been inserted into the SBTS. continuously activated/cancelled

Start

Start

Start / Cancel

Start / Cancel

Start / Cancel

(however, the alarming state might predominate). There is always some jitter/wander Running SW in version the transmission is not able to network; install Start / Cancel the limits are requested SWdefined version. in ITU-T G.823/824/825. 3. If the BTS receives the BTS RTC initialization fails which is used Start / Cancel synchronization information via the to synchronize time for all nodes in 2.048 BTS. MHz or 1PPS synchronization input (external clock source), the alarm situation might be caused by a fault of that signal. 4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason is in the synchronization reference signal behavior (see the descriptions above).

The SBTS cannot obtain a file from the file server (error in FTP open or FTP get or HTTP(S) GET). The file server is down, the file is missing, or the path is incorrect. Thereisiscorrupted a possible The download or error the in the DCN and Iub, or a user-administration software is incorrectly produced. error (an invalid username or password, or the user does not have access rights to the files). The SBTS SW update has The in thatfailed. is included error might be caused by a unit reset the fault name is a variable parameter, during the SW update, hardware which identifies the typea of file for which problem in thefailure unit, cabinet the download has been reported. Incompatibility with the The The SBTS SW problems update has failed. download or a corrupted flash error might be caused by a unitfile reset system. during the SW update, a hardware problem in the unit, cabinet Incompatibility withpower the There is a faultproblems in the mains download or a corrupted flash supply. The SBTS has receivedfile a Battery system. Backup alarm and the intelligent

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

shutdown procedure has started. The SBTS cells are disabled because the Start / Cancel Battery Backup alarm (ID=37) is active.

The SBTS cells are disabled because the Start / Cancel Battery Backup alarm (ID=37) is active.

A unit is blocked with the SBTS Element Manager. The purpose of the fault is to avoid alarms that might be raised during the The user has blocked the cell with the unit maintenance task. SBTS Element Manager.

Start / Cancel

Start / Cancel

The SBTS is blocked with the SBTS Start Element Manager. The fault indicates that the alarms that might be raised during a SBTS maintenance task should be avoided. A failure in the unit/module has been Start detected during the BTS power-on self test (POST). One or more cell parameters are missing Start / Cancel from the RNC/Flexi Direct RNC configuration data and the BTS commissioning file.

A module cannot be identified by its product code or its physical device address (object ID).

Start

In of FR, the additional is Ancase unsupported module has meaning been that FR was found in planned HW detected in the SBTS. Typically, this configuration is connected happens whenbut a new version oftoathe wrong port. module is installed and there is an older

Start

SBTS in usepower that does not support The RFSW module measurement has Start / Cancel the new module version. failed.

The fault indicates a telecom slave Start configuration or registration failure, a unit RNW configuration failure, and a telecom RNW reconfiguration failure. The fault indicates a telecom slave - FSP unit to or FCT allocationfailure, failure a unit configuration registration DSP subunit to FSP allocation RNW configuration failure, and afailure telecom RNW reconfiguration failure. Note that depending on the fault source, The faultstatus indicates a be telecom slave the unit might related to either - FSP unit to or FCT allocation failure configuration registration failure, a unit the state of a particular carrier resource - DSP subunit to FSP allocation failure RNW failure, and telecom on theconfiguration Radio Module module oraFSP RNW reconfiguration failure. the unit board on the FCT. Therefore, Note that depending on the fault source, status might not bereceive inbe line with the source The BTS does not a response the unit status might related to - FSP unit to FCT allocation failureeither HW unit state. from the RNC (a block request). the state of a particular carrier resource - DSP subunit to FSP allocation failure on the Radio Module module or FSP board on the FCT. Therefore, thesource, unit Note that depending on the fault status might not be in line with the source Either enabling setup oftoCPICH the unitcell status might(the be related either HW unit state. and BCH)oforacell disabling (theresource release of the state particular carrier common channels) failed.or FSP on the Radio Modulehas module The reason a hardware a bus board on themight FCT.be Therefore, the or unit problem, or a lack of DSP or transport status cell might not be (the in line with of theCPICH source Either enabling setup resources. HW unit state. and BCH) or cell disabling (the release of common channels) has failed. The reason might be a hardware or a bus problem, or aenough lack of BTS DSPbaseband or transport There is not resources. capacity to set up a cell.

Start

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

Start / Cancel

The lower LCR ID has been assigned to a higher frequency, or vice versa, for an RF Module that is in dual carrier mode.

Start

A second carrier is assigned to an RF Module that is in single carrier mode.

Start

Transient

Start / Cancel

Start / Cancel

Start / Cancel

At least one LCG in the BTS does not have enough resources for the HSUPA minimum capacity commissioned with the parameter "Number of HSUPA resource steps 133: reserved for HSUPA users". If the LCG has two HSUPA schedulers, EFaultId_RxAntennaSignalLevelTooLow then Al the sum of the HSUPA Resource Steps that is statically allocated in both The RX signal level is less than -112dBm System Modules is compared with the 133: commissioned amount. The fault is 134: EFaultId_RxAntennaSignalLevelTooLow raised for the BTS. EFaultId_RxAntennaSignalLevelDifferenc Al eTooHighAl The RX signal level is less than -112dBm The difference between the maximum Unsuccessful to the and minimum DSP powerconfiguration levels of all RX 134: correct mode. antennas in the same cell and sector EFaultId_RxAntennaSignalLevelDifferenc exceeds the defined limit for cell. eTooHighAl The difference between the maximum If there are no power DSP resources forRX PIC and minimum levels of all configuration, Telecom rejects the PIC antennas in the same cell and sector configuration, and raises exceeds the defined limit an for alarm cell. to indicate "Resource block not available". If PIC configuration cannot be allocated to a DSP resource because the DSP is in use with some high-priority users, Telecom raises this fault. Telecom then tries move the high-priority users to a10 One to particular DSP Nacks DCH setup different resource block, and tries again times with cause to allocate PIC configurationor to the DSP "NotEnoughResources=10" a number of times for 3 minutes. casea "AlreadyActivated_Allocated=22" In within of failure, Telecom rejects the received 20-minute period. 1.Cell setup isand rejected because either all configuration indicate a message cells in the block same occupied LCG, having the same "Resource by high priority UARFCN users". are not mapped to the same PIC pool or there is another cell in the same LCG with same UARFCN The cell is inactive because of a outside lack of the PIC pool. sufficient Common Control Channel 2.The PIC pool (new or Processing Set configuration (CCCH Processing Set) updated) is rejected if either all LCELs in licenses commissioned to the BTS. the same LCG, having same UARFCN The PSCR request setting new do not belong to thefor same PICup pool or a HSPA resources is made ontoalready LCEL that does not belong any PIC existing in DSP SW pool hasresources UARFCN (allocated that is already internal assigneddatabases). to any PIC pool from the same LCEL's LCG. One of the Common Transport Channels 3.Rel. 3FACH, BTS only: Tooismany cellsby have (PCH, RACH) released PIC RNC.activated (number of RX of non-PIC cells + 2x number of RX of PIC cells > 48). For Fixed BB allocation due to HW The inactive because of a rel. 1cell andremains Fixed BB Allocation Pooling, lack processing capacity for the Common this condition is checked LCG-wide for Control Channel. LCGs located in Rel. 3 FSMs only. For a Flexible BB Allocation pooling, this condition is checked BTS-wide for all cells.

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start

Start / Cancel

Start / Cancel

Start

Start / Cancel

Start / Cancel

This indicates a flash memory operation Start failure. If this fault continuously appears, the flash chip might be broken. This indicates a flash memory operation Start failure. If this fault continuously appears, the flash chip might be broken. This indicates a flash memory operation Start failure. If this fault continuously appears, the flash chip might be broken. This indicates a flash memory operation Start failure. If this fault continuously appears, the flash chip might be broken. This indicates a flash memory operation Start failure. If this fault continuously appears, the flash chip might be broken. The operating system (OSE) error occurs. If only one FSP in BTS generates this fault then there is a malfunction in An out of frame data error interruption one of the FSP sub-modules. If all FSPs received from the SWS ASIC. generate this fault then there is a malfunction in the FSM. The Antenna (RP3) link is down: the transmitter or receiver drops out of synchronization.

Start

Start / Cancel

Start / Cancel

High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning.

High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning.

High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. High or low voltage on the external alarm Start / Cancel line. The user specifies the fault text during commissioning. Communication with the application

Start / Cancel

has failed. The application has not replied to the message that has been sent or re-sent to it. The requested channel in the cell setup is not acceptable for the BTS hardware, because of an incorrect frequency band and/or a carrier spacing and/or the number of carriers.

Start / Cancel

- Baseband bus configuration was rejected by NodeOAM/HWAPI.

Start / Cancel

The baseband bus synchronization has failed.

Start / Cancel

The OCXO warm-up takes too long and Start / Cancel the OCXO does not become active within a period of eight minutes from the poweron. The ambient temperature can also be too low clock or it changes tooisfast. Master frequency tuned to within Start / Cancel 5% of its minimum or maximum tuning limit. The output signal of the OXCO is missing Start / Cancel and the FCT cannot deliver the 30.72 MHz System Clock required by the other units. The Masthead Amplifier (MHA) is not working properly. The received Radio Module signal level has decreased.

Start / Cancel

If both stages ofAmplifier the LNA(MHA) on theisuplink The Masthead faulty. Start / Cancel path fail, the MHA switches The received RF signal levelthe is LNA to by-pass mode. In by-pass mode, the decreased. MHA has no gain but some loss. If a single the LNA theuplink MHA If both stage stagesofof thedetected LNAfails, on an the Radio Module has Start / Cancel still has about a half of its normal gain. path fail, theon MHA the LNA to overcurrent the switches antenna line. The With an integrated MHA, the fault might the by-pass mode. the by-pass mode, antenna linemain can and beIndamaged (short affect both diversity branches. the MHA has no gain but some loss. circuit), or an antenna line device is If only onean stage of the All LNA fails, the MHA causing overload. antenna line VSWR value exceeds the defined level. Start / Cancel still has about half of its normal gain. devices powered bymismatched the antenna line are The antenna line is With an integrated MHA, the faultormay out-of-order. damaged. affect both main and diversity branches. The Radio Module or the Filter has detected an VSWR value that exceeds the defined level. The antenna line is slightly mismatched.

Start / Cancel

The filter has detected a malfunction in the LNA unit.

Start / Cancel

A filter has not been able to tune on an appropriate sub-band (tuning failure).

Start / Cancel

Radio Module has detected major failure Start / Cancel of filter unit.

Tilting the antenna is not possible or might function incorrectly.

Start / Cancel


Start / Cancel


Start / Cancel


Start / Cancel


Start / Cancel

A hardware failure detected by an Start / Cancel antenna line device. Usually, this is a permanent fault (the hardware is broken). The unit is in Download Mode State. Returned upon unsupported procedure when in Download Mode.

Start / Cancel

A corrupted SW file in the FLASH is detected. The unit cannot perform a complete start-up.

Start

FSP control unit failure.

Start

A fault in the Masthead Amplifier (MHA) Start / Cancel has been detected. The fault can reduce the gain performance of the MHA. A fault in the Masthead Amplifier (MHA) has been detected. The fault completely prevents the gain function of the MHA.

Start / Cancel

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

Start / Cancel


Start / Cancel


Start / Cancel


Start / Cancel

An autonomous internal delay Start measurement has failed. The TCOM cannot measure the internal delay for a cell for any of the RAKEs in a certain BB unit. The reference clock monitoring has Start / Cancel detected a loss of PPS signal in the reference received from the GPS receiver. The reference clock monitoring has Start / Cancel detected a loss of 2.048 MHz signal received from an external reference source, connected to Sync In interface of the Module.configuration has TheSystem Radio module Start failed because of a hardware or software fault. A critical configuration file is missing from Start the Radio module.

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

The System Module clock reference differs from the clock on the Radio Module.

Start / Cancel

The baseband bus between the system module and the Radio module is out of synchronization.

Start / Cancel

The Radio module baseband bus is incorrectly configured.

Start / Cancel

There is an error in the baseband or optical bus.

Start / Cancel

The Radio Module TX path cannot be used.

Start / Cancel

The TX output power adjustment has failed.

Start / Cancel

The Radio module filter has measured a TX power that is too low.

Start

The Radio module RX FR synthesizer is unlocked.

Start

The Radio module is out of order Start / Cancel because of a software or hardware fault.

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

Start / Cancel

The TX signal adjustment fails.

Start / Cancel

During Radio Module start-up, the Start / Cancel temperature inside the Radio module is too low. . Wait until the alarm is canceled. Module heating is ongoing and might take up to 30 minutes. The permanent memory in the module is Start corrupted and the module product code During Module runtime, or serialRadio number is missing. It isthe also temperature inside the Radio module possible that the module product codeisis too low. A problem might occur. unknown. The Radio module SW has detected Start / Cancel conflicting or corrupted configuration data.

The Radio Module power-on self-test failed at start-up.

Start

The Radio Module lost the lock to the incoming clock.

Start / Cancel

The highest temperature exceeds the power decrease limit.

Start / Cancel

The FPGA software update has failed.

Start

RF Module cannot identify the fan vendor Start / Cancel or the fan is not installed.

The Fan(s) is(are) not running.

Start / Cancel

Fans are rotating more slowly than required.

Start / Cancel

Fans are rotating faster than required.

Start / Cancel

Validated module temperature exceeds or is equal to the predefined maximum value allowed.

Start / Cancel

The validated sensor temperature exceeds or is equal to the predefined value on the unit property file.

Start / Cancel

The validated temperature of any PA or Start / Cancel Pipe sensor in RF module equals or exceeds the predefined value on the unit property file. An increase of bit error rates has been detected on the optical link to the radio module resulting in LCV errors in downlink baseband processing.

Start / Cancel

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 cannotline behas successfully processed Start The antenna been autonomously by the Radio Module due to the disabled by FRM to protect the HW from occurrence of consecutive high reflection conditions. LCV errors. Radio module has detected permanent RP3 routing collisions either in the downlink (TX), or in the uplink (RX) transmission direction.

Start / Cancel

The configuration of Radio module's Start External Alarm and Control line(s) has failed because of a hardware or software fault. The Small Form Factor Pluggable (SFP) Start / Cancel has malfunctioned or the SFP module is not physically present (no electrical connection exists). The SFP is a part of the cable package. Thefibre Small Form Factor Pluggable (SFP) Start / Cancel has malfunctioned or the SFP module is not physically present (no electrical connection exists). The SFP is a part of the cableoptical package. Thefibre incoming signal to the Small Start / Cancel Form Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detached. The fiber cable is experiencing Start / Cancel The connection between the System interference; data transmission is faulty. Module and the Radio Module (LTX, Antenna Antenna Line between Device) or A physicalFilter, connection failure the between the Master System Module and optical interface and the summing The RP3 channel has lost the achieved Start / Cancel the Extension System Module is broken. function has occured(possibly caused by frame synchronization state. This might joints). concern the primary or bad circuit secondary link. 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 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 initialization.

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 incorrectthe Start / Cancel The control message trafficorbetween initialization. modules is malfunctioning.

The optical interface has detected a CRC Start / Cancel error in the received synchronization burst from the clock function. This fault appears on the RX side. Synchronization to the clock control unit frame pulse has been achieved earlier, but it differs from the currently received frame pulse. The internally generated frame clock error mighthas have drifted. A decoding been detected in

Start

Start / Cancel

the baseband internal link. The data packet is lost or the content is corrupted. This is also triggered when links Start / Cancel Theresituation is a baseband bus address do not synchronize with each other. mismatched in the summing. There are two possible causes: A error (twoBurst different A configuration new RP1 Frame Clock (FCB) baseband units functioning) - after from an burst/message has been received acknowledgment, the fault returns. the RP3-01 interface while processing the previous burst/message. Data corruption on the bus - appears The buffer underflow or onceclock whencrossing unsynchronized data is sent overflow in RX block and the received by the baseband. data might be invalid. The fault is an indication of either too large a clock drift between the received andfailed the or The SW update of thesignal BTS has internal clock, or an incorrect RX rate the BTS SW is corrupted. setting.

Start

Start

Start

Baseband bus message multiplexing slot Start / Cancel for the message is not possible to be filled. If a message is not routed, an Start / Cancel interruption is generated. This is considered normal when DSPs are starting up and RP3 sync has been completed. The fault might be visible when there is a missing link capacity between the System Module and radio.

Summing checks the header of the messages that are to be summed. If a specific header type is rejected then no summing is performed, and an empty message is detected sent instead. Transmitter an RP3 message

Start / Cancel

Start / Cancel

from a summing coincident with a transmission rule. The transmitter 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, preventing sRIO system maintenance. Congestion avoidance hardware of the sRIO switches has been triggered.

Start

SRIO error rate is too high.

Start / Cancel

O&M software was not able to initialize TRX into operational state, even though it should have been possible.

Start / Cancel

TRX control plane connection has been lost.

Start / Cancel

DSP related to TRX was not able to initialize OBSAI (RP3) resources.

Start / Cancel

O&M software was not able to map TRX resources received from BSC to resources available from SBTS profile.

Start / Cancel

Logical TRX has measured difference exceeding threshold between signal strength of Rx antennas.

Start / Cancel

O&M software was not able to map all Start / Cancel TRXs. TRX identifiers of a sector have to be either in a range between 1 and 12 or in a range between 13 and 24.

TRX user plane connection has been lost.

Start / Cancel

One of the radio modules in a two radio module configuration(centralized configuration) is not in working state.

Start / Cancel

The SBTS detected that a FSM2 is reset Start or removed. SBTS reset is needed to recover and utilize all available hardware. The BTS has detected a communication problem with the GPS receiver. The fault is ignored until the GPS receiver has reached The connection to thecommissioned FSP or DSP has state. been lost or the submodule reports an

Start / Cancel

Start / Cancel

error situation. BTS Fault, which fault name is Start / Cancel mentioned in the Fault name field, is toggling in the BTS. The toggling alarm condition is presented to the user with this new BTSSW Fault. Toggling alarms A corrupted file in the FLASH is are Start supressed until the toggling alarm detected. The unit cannot perform a condition cleared. Severity of this BTS complete is start-up. Fault is the same as the severity of the toggling BTS Fault. Binary data download to an antenna line Start / Cancel device failed due to incorrect checksum or file format. Binary data download to an antenna line Start / Cancel device failed due to incorrect checksum or file format. Connection to a module belonging to the Start / Cancel SBTS configuration has been lost or FSP cannot be detected. There are not enough RP3-01 links connected between FSM and FR. Commissioned cells cannot be routed through the existing RP3-01 links.

Start / Cancel

The over-current was detected on RS485 Start IUANT port. Some antenna line devices are causing overload or there is a shortcut on the port. Antenna line devices powered by the RS485 IUANT port are out of order.

The parallel RP3-01 links towards one Start / Cancel radio module have too large mutual length difference (more than 60 meters). Fan speed is too low for successful detection. Detection is attempted again after Fan.Detection.Timer expires.

Start / Cancel

This fault is reported for both operational Temperature on the FSP board exceeds Start / Cancel and non-operational fans in the hardware the critical threshold value. detection phase only. Fan(s) is/are not running although the control is higher than 0.

Start / Cancel

Speed of the fan(s) is/are deviating too much from the required control.

Start / Cancel

Fan(s) is/are running faster than required.

Start / Cancel

4082: Source unit has reached the maximum number of reset attempts, that is, the source unit cannot successfully finish start-up 4082: after the SW update.

Start

Source unit has reached the maximum 4083: number of reset attempts, that is, the Source unit cannot requests SW fallback source unit successfully finish because of a critical problem that start-up after the SW update. 4082: occurred during SW update, that is, Source unit has reached the failed. maximum configuration data migration 4083: number of reset attempts, that is, the Source unit cannot requests SW fallback source unit successfully finish 4085: because of a critical problem that start-up after the SW update. Transport SW on the source unit The Radioduring Module detected occurred SWhas update, that low is, LTE indicates need for software fallback. TX powerafrom the Flexi System Module. configuration data migration failed. 4083: There is a failure in the downlink Source unit requests transmission path. SW fallback 4085: because of a critical problem that Transport SW onSW source unit Synchronization isthe lost when that the system occurred during update, is, indicates a need for software fallback. module is working as a synchronization configuration data migration failed. slave system module. This usually indicates that a synchronization master 4085: system module has been reset or that Transport SW on the source unit The fault indicates poor GPS antenna there is a problem with the optical cable indicates a need for software fallback. installation. between the master system module and the slave system module.

Start

Start

Start / Cancel

Start

Start / Cancel

The GPS receiver is running a site/self survey.

Start / Cancel

There is no accurate position stored in the EEPROM.

Start / Cancel

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

Start / Cancel

The GPS receiver has detected that one Start / Cancel or more EEPROM segments have been found to be corrupted at reset and had to be set to their factory default settings. SW file validation against its signature failed.

Start / Cancel

TRS IP configuring or re-configuring by RROM has failed.

Start / Cancel

External GPS/GNSS receiver module Start / Cancel has lost satellite visibility and is currently operating in holdover mode. FSM-internal (including DSP expansion Start / Cancel cards) baseband bus link synchronization has failed. Frame sync state has not been reached, or link timing is incorrect. VSWR major or VSWR minor value set is Transient out of range during commissioning.

There has been a failure to validate the Start / Cancel software release signature for the software release that has just been requested to be downloaded to the BTS system module information There has beenbecause a failure the to validate the Start / Cancel of either Hash Container file or hash of the questioned SW filesHash for FCT Container Signature file is file notor present except of Hash Container Hash in the downloaded TargetBD.xml, or the Container Signature file in the software verification of the software signature files release that has just been requested to An unsigned software release has been Start / Cancel has failed. be downloaded to the BTS system downloaded to a BTS system module module becauserunning the hash value of the that is currently a software questioned SW file is missing, or release that implements software SiteOAM fails to verify the hash of the signature checking. questioned SW file.

There has been a failure to validate the Start / Cancel software signature for the software release that has been requested to be downloaded to the BTS system module because is no software MHA wasthere unexpectedly set tosignature bypass Start / Cancel for the release, and only signed software mode. can be installed. Not enough #data users licenses is available in Centralized SW License Server. Parameters BTSSCW/numberOfHSDPASet1, BTSSCW/numberOfHSDPASet2, Not enough #data users licenses is BTSSCW/numberOfHSDPASet3 are to available in Centralized SW License be reduced internally. Server. Parameter

Start / Cancel

Start / Cancel

BTSSCW/numberOfHSUPASet1 is to be reduced internally. Not enough #data users licenses is Start / Cancel available in Centralized SW License Server. # LTE users is not reduced. Licenses are missing since the time ($T) Start / Cancel indicated in the fault name. The IP traffic is throttled to the peak rate ($R), at the level ($L) indicated in the fault name. Level denotes a per cent of the maximum Start / Cancel Baseband extension module is inserted IP traffic throughput in a 15-minutes into a working SBTS. Manual SBTS reset interval before the faultand hasuse been is required to activate thisraised. unit. For every expiry of seven days (after missing licenses have been detected) at A Certain the NTPlevel server problems time($T), ($L)indicates decreases by 5%. Start / Cancel with thethe connections. When level ($L) changes then a new alarm is raised. Time: The format is a local time Timing over"$T" packet is unavailable or Start / Cancel stamp (GMT+/-xx:xx). For example: unusable as a clock source. 2014-04-12 00:51:26 GMT+0530 Level ($L): 100% to 50% in 5% steps Rate ($R): current policed peak rate Synchronous Ethernet is not available or Start / Cancel usable as a clock source.

PDH is not available or usable as a clock Start / Cancel source.

The used cable between the system Start module and the radio module exceeds the maximal supported length for Micro DTX (max supported link delay 80us, if the radio module is directly connected to system module or extension baseband module, the longest supported cable length is approx 16 km). eNB power saving, i.e. micro DTX functionality can't be provided any more.

Micro DTX configuration in a radio module has failed.

Start / Cancel

This alarm is triggered after a Start configuration change, which causes the SBTS to lose its management connection, is rejected by the SBTS and the management connection is reConfigured ToP (frequency/phase) Start / Cancel established using previous sync mode doesn't match withthe configured configuration as a recovery action. This (frequency/phase) and hence requested alarm is visible until the next SBTS ToP configuration cannot proceed. site reset. RAT critical application has crashed. RAT Start that is indicated in the Source field of the fault is not operational. Some problems in TX or RX path have Start / Cancel caused beamforming calibration to fail. The path means all units between the signaling processor (DSP) and the antenna line situation that processes datadetected Start / Cancel An overload has been transmitted (TX) by BTS or received (RX) by scheduler on the user plane. by BTS. Recovery actions are initiated to decrease the load level. The configured PHICH transmission Transient power boost cannot be applied either partly or at all because of a lack of remaining power after considering (boosted) cell-specific DL RS power, The RIP (Received Interference Power) Start / Cancel (boosted) PCFICH power, andBlock minimum value per Physical Resource (PRB) reserved PDCCH. exceeds the of the cellpower for ULfor subframes predefined threshold for at least the operator-configured The Received Interference Power (RIP) Start / Cancel alarmThresholdCrossingTime. value per Physical Resource Block (PRB) of the cell for UpPTS symbols exceeds the predefined threshold for at least the operator configured An overload situation has been detected Start / Cancel alarmThresholdCrossingTime. by scheduler on the user plane. Recovery actions are initiated to decrease the load level. An overload situation has been detected Start / Cancel by 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 MME is broken. This might be because of an unplugged cable to MME. There is no transport path available to continue operation on the faulty connection with The transport path (SCTP) for connection Start / Cancel 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 continue paths operation on the One of thetotransport (SCTP) in Start / Cancel faulty connection with the adjacent BTS. SCTP connection to MME has failed. Only applicable when SCTP multihoming is supported. An alternate transport path path is available The transport (SCTP)toforpursue connection Start / Cancel operation. to MME has broken. The reason for this can be an unplugged cable to MME. No transport path available to pursue operation the faulty connection in with One of theon transport paths(SCTP) the MME. SCTP connection to MME (which

Start / Cancel

provides MBMS service) has failed. Only applicable when SCTP multi-homing is supported. An opening, alternate reading, transportorpath There was an file is Start / Cancel available to pursue operation. content problem with a radio network configuration file at the BTS startup or at the activation of the delta configuration file. Theraises detected problem can be a file a Start A BTS this fault if it experiences handling problem (for example, problem in internal configurationopen, read, and write operations as and well Uas data distribution (cell setup)fail) to Ccontent problems (for example, no valid Plane SW components. RAML2.1 format). The BTS raises this fault if it experiences Start a problem in internal configuration data distribution (cell setup) to C-Plane and U-Plane SW components. A failure has occurred in the trace connection between the SBTS and the third party tool.

Start / Cancel

There was an opening, reading, or file Start / Cancel content problem with a BTS vendorspecific file at BTS startup. The fault is also detected when a vendorspecific missing. during A failurefile hasisoccurred Transient activation/deactivation of trace session (subscriber trace, cell trace, or interface trace session). The BTS has encountered a few possibly Start / Cancel In case of subscriber trace, the possible misconfigured PLMNs, which cannot be reasons are: used by the BTS for accepting calls from -new TheUEs, Subscriber Trace those feature is not which select PLMNs. enabled at the BTS. -These The IdPLMNs used for theare subscriber trace that considered session is already in use for another misconfigured by the BTS are: active subscriber traceatsession. - currently configured the BTS for one -orThe number of subscriber trace more cells sessions at the BTS has reached the - served by one or more MMEs and maximum number of subscriber trace therefore currently broadcast by BTS's sessions supported BTS, which is cells. However, nonebyofthe these PLMNs 60. have serving MME(s) with relative -capacity Handover at thethan BTSzero. is ongoing for of the greater Because UE to be traced.

This alarm indicates that the maximum number of LNADJ and/or LNADJL objects was exceeded in the eNB and that the new object was not stored.

Transient

This alarm indicates that a WCDMA neighbor cell, which is reported by an UE via ANR specific measurements could not be stored because the maximum number of LNADJW instances is already This alarm indicates that a WCDMA reached. The additional alarm info neighbor relation, which is reportedholds by a the UTRAN of the reported WCDMA UE via ANR CGI specific measurements, cell, could notbecause be stored in the couldwhich not be stored the form of: maximum of that neighbor relations This alarmnumber indicates WCDMA "A neighbour WCDMA cella which is per cell is already reached. The neighbor relation, which isactivated reported ANR by a reported by an UE due to additional alarm info holds the ECGI of UE because of activated UTRAN ANR feature(s) could not be stored because the LTE cell and the UTRAN CGI of the feature: the maximum number of WCDMA related WCDMA neighbor cell one in the -A has been stored but at least of neighbour cells is reached. WCDMA handover target cell cannot be uniquely form: LNRELW's mobility parameters neighbour cell information needs be selected several candidates are "LTE cell because ECGI{ecgiAdjEnbId = %d, (psHoAllowed, srvccAllowed) has been cleaned up manually by thevalue operator via available for a certain PCI and ecgiLcrId = %d, ecgiPlmnId = { %d, %d, set tofile 'forbidden', because the number of plan (WCDMA cell {rncId = %d, carrier frequency. %d}} , WCDMA cell(LNRELW CGICGI {rncId= %d, neighbor relations instances) CellId = %d, ecgiPlmnId: MNC= %s, CellId= %d, cgiPlmnId =number { %d, %d, The base station has executed baseband exceeds the maximum of %d}}". MCC= %d})". board (FSP) recovery activities. All be WCDMA neighbor cells, which might baseband available again but used by theboards eNB inare measurement not all cells could beinrestored. To restore configurations (limit 3GPP 36.331 the functionality of the remaining (32)).EARFCN of an LTE neighborcell, The cell ais base station reset is required. The additional alarm info holds the a mapped EARFCN according to the ARFCN of the affected carrier MFBI-profile configuration (thatfrequency is, the as well as the LNCEL and LNRELW requirement for a homogeneous MFBI instance number in the form of: configuration is violated). This fault WCDMA occurs when CGI carrier = %d, "Affected ARFCN As a consequence, HO to this neighbor measurements indicate that two or more LTEiscell ECGI{ecgiAdjEnbId = %d, cell not possible and call drop rate cells that operate on the same frequency ecgiLcrId = %d, ecgiPlmnId = { %d, might increase if there is no other %d, use the same PCI. %d}} , WCDMA celltarget. CGI {rncId= %d, suitable handover If the UE-based CellId= %d, cgiPlmnId = { %d, %d, This fault indicates that the absolute ANR is activated and the X2 link is %d}}" phase error of the exceeds the limit available, there willBTS be continuous retries of 5 us, and features depending on that to resolve the ECGI. accuracy have been deactivated. This can when: when CGI Thisoccur fault occurs

Transient

Transient

Transient

Transient

Start

Transient

Transient

Start / Cancel

Transient measurements indicate that two or more 1) The absolute WCDMA cells value of estimated phase error of the hassame exceeded that operateBTS on the carrierthe limit of 5us, frequency use thehas same primary An inconsistency been detected Start / Cancel scrambling code (PSC). between cluster members, which OR prevents the inter-eNB CA feature from being 2) Theenabled. BTS has been in holdover mode for more than 6 hours, means that Start / Cancel SW incompatibility has which been detected estimated phase error value might notthe be between cluster members preventing credible. It is assumed in this case that inter-eNB CA feature from being enabled. real absolute value of phase error is bigger than 5us, OR 3) The BTS has lost all phase sync reference sources, but does not have sufficient history data for holdover, OR 4) The BTS is synchronized by a Sync Hub Master which reports the phase error of the provided sync signal. The absolute value of estimated total phase

The application has detected a problem Start / Cancel with inter-eNB link communication (SRIO, RP3-01, Ethernet, and so on). Features that depend on inter-eNB communication, like the Inter This fault is reported when theeNB BTSCarrier Start / Cancel aggregation feature, are disabled. detects that the number of neighbor related objects (which represents the neighboring BTS, its cells with the relationship objects) in its database This fault is reported when the BTS are equal to or above the configured value detects that the number of neighbor maxNumAnrMoiAllowed in LNBTS. related objects (which represents the

Start / Cancel

neighboring BTS, its cells with the relationship objects) in its aggregation database is BTS has detected carrier Start / Cancel equal to or above an internal relation misconfiguration. Onethreshold or more of based on the configured value the configured carrier aggregation maxNumAnrMoiAllowed in relation(s) points towards aLNBTS. cell that does not exist inDSPs any ofpool the configuration BTSs within the Resource failed Start configured carrier aggregation between C-Plane and U-plane.cluster.

BTS configuration failed in C-Plane.

Start

The X2 interface reset has failed after Start / Cancel several attempts. This indicates that a severe failure has occurred, for example there is some configuration problem, there adjacent Start / Cancel Thereisisno noX2 X2connectivity, connectivity the to an BTS has failed, and so on. adjacent BTS, the adjacent BTS has failed, and so on. There is no S1 connectivity to an MME.

Start / Cancel

Fault is generated if S1 setup procedure has subsequently been attempted and failed "maxS1SetRetry" number times. Start / Cancel S1 interface reset has failed afterofseveral attempts. This indicates that a severe failure has occurred, for example there is some configuration problem, there is no S1 MME has failed, Theconnectivity, S1 eNB configuration updateetc. Transient procedure has failed. The MME could not be informed about the modification at serving least one of the A RIM request toofthe BSS has Start / Cancel following eNB configuration data: failed after several attempts. This means -that eNB Name Information for the related System -GERAN Supported TAs (TAC, PLMNcells Identities) or UTRAN neighbor is not -reliable. Default paging DRX

1. A RIM association could not be Start / Cancel established because a RIM Error PDU has been received for a RIM enabled GERAN neighbor cell. 2. A RIM Application Error has been System-Information-Broadcast-related Transient detected. parameters have changed more than 32 3. S1 links all configured times withintothree hours. MMEs are active, but the routing of RIM PDU to the RIM-enabled WCDMA neighbor cell is Non-correctable bit toggling error is Start not available. detected in the critical DSP memory.

Fatal error of DSP HWAPI SW has occured. If FSP in the BTS generates this fault, there is a malfunction in Fatal error of DSP Application SW has a corresponding FSP sub-module. occured. If all FSPs generate this fault, there is a malfunction the generates FSM. If FSP in theinBTS this fault, there a malfunction in GPIO is reset has been triggered for the a corresponding FSP sub-module. DSP on purpose. If all FSPs generate this fault, there is a malfunction in FSM.

Start

Start

Start

M3 interface reset has failed after several Start / Cancel attempts. This indicates that a severe failure has occurred, for example there is some configuration problem, there is no M3 connectivity, MME has failed, There is no M3 connectivity to an etc. MME, Start / Cancel the MME has failed, etc. If the fault is canceled, autonomous recovery actions (reset) have solved the fault situation. The deployed MBMS subframe pattern share is less than the required MBMS subframe pattern share, which is configured with the MBSFN parameter subfrPShareRequired. At least one suspended MBMS session

Start / Cancel

Transient

cannot be resumed because of insufficient MBMS resources. MCE configuration update has finally failed.

Transient

The MME could not be informed about the of atif least one of the Themodification alarm is raised the monitored Start / Cancel following MCE configuration data: service is unavailable when e.g. all -network global MCE pathsID are unavailable. This -implies MCE name that all individual BFD sessions of -the supported MBMS area identities respective groupservice are erroneous.

This loss of frame alarm is raised when Start / Cancel the local receiver is unable to detect the frame alignment word of the E1 signal. All other transmission alarms related to this suppressed. Thissignal alarm are is raised when either no or an Start / Cancel incompatible signal is received on the interface referenced in the alarm text. Probable cause: The interface at the far With anpeer Ethernet interface theone physical A dead was detected in of the end is not configured to be a framed Ethernet link is detected toSBTS. be down. E1 All IPsec associations of the interface. other transmission alarms related to this There is nounit response to the requests Note: The and interface variables signal suppressed. sent toare the either during the IKE ($U,$IF) willpeer, be replaced by appropriate SA setup, the IPsec SA setup, or during hardware. Example: unit-FTIF, interface This alarmcauses is raised a loopback has Probable for ifEthernet interfaces: DPD. EIF1. been configured by aormanagement - a cable/fiber is cut there is no application connected on the interface mentioned in cable/fiber to thetunnel interface Note: When IPsec backup feature the alarm text. -isthe electrical/optical signal is enabled, this alarm is not raised excessively attenuated The small form-factor pluggable (SFP) due to failures wheninterface trying tovariables setup Note: The unit and -module the port at the connected far end node is not supported, is expected but primary IPsec tunnel in by appropriate ($U,$IF) will be replaced is switched off not present, or could not be recognized. "Secondary_Active_Probing_Primary" hardware. Example: unit-FTIF, interface -The thesmall advertized technology capabilities form-factor pluggable (SFP) state. EIF1. with auto-negotiation of both devices module detected in the SFP slot doesatnot This fault is raised if not the match SBTS cannot the Ethernet link do comply withCertificate the SFP module typesList update the Revocation - the Ethernet technology at both devices supported by the BTS element. (CRL). at the Ethernet link is forced manual and The failure reasons include the following: not compatible Probable causes: -The The LDAP binding fails. -- the remote peer of inserted anaEthernet linkSFPis SFP has reported transmission No SFP module is at the -fault The LDAP search is empty (no CRL not auto-negotiation capable or has autocondition and has disabled the laser based SFP slot. found)/ The function LDAP search contains more disabled transmitter. -negotiation The SFP module's interface by contacts than one entry. configuration are corroded or dirty, preventing either -Probable The CRLcauses: signature validation fails. read access to the SFP module at the alarm is raised the measured -This The CRL file exceeds theinterfaces: BTS storage Probable causes for when PDH -time The SFP is defective. of reading compliance data from the bit rate exceeds the value limit. -SFP a error cable is cut or there is threshold no of cable or preventing detection module. of BER-3 -connected The BTS(10E-3). certificate is part of the CRL. to the interface -- The SFP module type is not distribution supported. DNS resolution for the CRL - the electrical is excessively Note: Thecauses: unit signal and interface variables Probable point fails. attenuated This loss ofunit multiframe alarm is raised if ($U,$IF) beand replaced by(connectors appropriate Note: Thewill interface variables -the the signal level is too low or -hardware. the interface port at the referenced connected in the far end alarm node text Example: unit-FSM, interface ($U,$IF) will be replaced by appropriate cables are dirty, electrical connectors or is has switched lost theExample: off multiframe alignment. EIF1. hardware. unit-FSM, interface cables areand corroded) -EIF1. transmit receive cables are mixed -Probable the specified maximum lengthtype of the up cause: Thewhen interface This alarm is raised an alarm has cable is exceeded not been configured to meet This the framing indication signalisisnot received. signal -of the connector properly connected Note: the The interface unit and at the interface far end. variables For E1 is generated by an intermediate PDH to the unit ($U,$IF) interfaces, will the be configuration replaced by appropriate of the far- it device in the forward direction because -end thenode receiver or the far end transmitter hardware. should Example: be E1 unit-FTIF, Multiframe. interface detects a problem its received signal. has Thisfailed alarm is raisedinwhen a remote EIF1. -Note: the accumulated of thevariables to end defect indication isBER received. Itend is sent by The unit and interface AIS defect is detected when theequipment incoming E1 path is too high. the intermediate or the far end ($U,$IF) will beor replaced by appropriate signal has two less zeros in each of because it Example: detects a unit-FTIF, serious fault in the hardware. interface two consecutive double frame periods Note: The unit and interface variables received signal. EIF1. Module iswill missing. The SBTS is (512 bits) according [G.775] chapters 5.2 ($U,$IF) be replaced by appropriate expecting a transport module, but it has and I.2. hardware. Example: unit-FTIF, interface not been detected. EIF1. Probable causes: All other transmission alarms related to Probable cause: The far end has a LOS, -this thesignal module issuppressed. not present. are LOF AIS alarm on its receiving - the or module is broken. interface. Note: Thecause: variable $U isisreplaced by Probable There a transmission Note: The unit and interface variables appropriate hardware. The actual value is problem somewhere in the intermediate ($U,$IF) will be replaced by appropriate FTIF. network along the E1unit-FTIF, path and interface AIS is hardware. Example: sent instead of user traffic. EIF1. Note: The unit and interface variables ($U,$IF) will be replaced by appropriate hardware. Example: unit-FTIF, interface

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Active / Cleared

This alarm is raised when the localIPAddress negotiation with the peer fails.

Start / Cancel

This alarm is raised if local and peer ends disagree on the LCP configuration leading to LCP negotiation failure.

Start / Cancel

The are Start / Cancel This related alarm isconfiguration raised if the parameters PPP interface :isacfcTarget, localMruTarget, pfcTarget. not operational either when all the PPP-links in the ML-PPP interface are not available or the PPP-link supporting the SL-PPP interface not available. A requested certificateiscould not be retrieved from the certificate authority (CA). A requested certificate could not be renewed the certificate authority The alarmfrom is raised if the BFD state for (CA). the session is not AdminDown and

Start / Cancel

Start / Cancel

nevertheless no BFD packet is received A certificate could not be time. at requested the local end during the detection retrieved as the number of certificates The alarmfrom is raised if theserver BFD state received repository (RA)oforis Start / Cancel The alarm isisraised if the BFD session the session not AdminDown andthan the certificate authority (CA) are more in activated BFD packet state. from the far end contains the expected. diagnostic code = 'Control Detection Time Expired' and nothat BFD down This alarm indicates there is Ingress a Start / Cancel alarm is present. mismatch between SBTS expected autonegotiation result and actual autonegotiation result. The RTT threshold alarm is raised in An Ethernet link was established but case the average value of the RTT for during link establishment a link speed this TWAMP session from the last 1-min downshift event place. A configured link speed period equals or took exceeds the downshift takes place when autothreshold. The alarm issuccessfully raised if thenegotiates packet loss negotiation a ratio equals or exceeds the configured certain technology but the link cannot be threshold value the currentIt is tried established withduring this technology. observation interval 15with minutes. then to establish theof link the next lower speed technology. This fault is raised when the Vendor BTS An Ethernet link was with certificate is about to established expire. 1000Base-T technology, but the The period of notification in advance is negotiated clock not days fit to the configurable frommode 1 daydoes to 4999 expected clock mode of synchronous with default 90 days. NE stores trust anchors for its own trust Ethernet. chain and for peers. When own or any trust anchors are about to expire/expired The expected clock mode of this alarm is sent. synchronous Ethernet is slave in case an Ethernet interface sync This alarm is raisedis ifentered at leastas one of the source to the SBTS synchronization PPP-links belonging to the ML-PPP priority list. applicable to 1000Baseinterface is Only not operational. T, since only with this Ethernet technology both link partners have to negotiate the clock mode. Probable causes: -Link speed downshift: a cable is of not sufficient quality to support e.g. Gigabit Ethernet technology, but sufficient to support Fast Ethernet -Link speed downshift: a cable has just two wire pairs connected, which is sufficient for Fast Ethernet, but not for Gigabit Ethernet.

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

Start / Cancel

In case the incoming SSM is not received Start / Cancel for a certain time period (configured via "ssmTimeout" parameter), an alarm is raised. This alarm is raised when SSM is Start / Cancel enabled and the received SSM indicates lower clock quality than required (configured via "ssmAcceptanceLevel" parameter). The reference clock monitoring has Start / Cancel detected a loss of ToP reference clock signal received from the master clock behind $IP. -During The SBTS not receive a replythe from Start / Cancel the IPdoes address configuration ToP Master within a certain time (5 sec) SBTS tests the direct attached network which it has sent a syncconfigured request node, whether, other already message. on the network uses already same IPv6 -addresses The SBTSon receives granted their network IPmessage interfaces. SW does not support the detected HW Active / Cleared rates from ToP Master (sync message The DAD (Duplicate address detection) type. rate, delay message rate), thataddresses does not detects those duplicated IPv6 match the requested rate by SBTS. and prohibits the operation of this IPv6 Probable causes: address in the SBTS. The Alarm contains SBTS has entered IPv6 IPsecaddress emergency Start / Cancel the corresponding andisthe -bypass The system module's SWconfigured version too active statethe where interface on which address was old to detect the HW variant. IPsec policies are ignored and allatraffic is configured. For each DAD event -sent Supported HW variant is not present in unprotected. separate reporting shall be indicated. the system module. The alarm is activated when the IP traffic Start / Cancel capturing session is started. The SBTS is currently capturing IP traffic towards a local port or into a file on the SBTS. A specific SBTS local operator account Start / Cancel If thebeen traffic capturing is happening has locked. towards a local port, the port and for a The number of failed login attempts destination MAC address needs SBTS local operator account hasto be provided. exceeded threshold andwhen the account This alarmthe will triggered the Start / Cancel Port values canbe be LMP or < HW has been locked on the SBTS. No further primary IPsec tunnel fails and SBTS has MODULE NAME >-. this account switched to secondary IPsec tunnel. until the account is unlocked. As a resultLMP of failure of the primary IPsec Example: or FSM-EIF1, FSM-EIF2 tunnel, SBTS has automatically switched or FTIF-EIF1 The alarm is raised when the IKE Start / Cancel over to secondary IPsec tunnel authentication credentials provided by terminating on secondary security the peer gateway. is not valid. The alarm is raised, if IKE parameters Start / Cancel are not matching with the peer proposal. It can happen due to following two failures This alarm is raised when the SBTS Start / Cancel --> When the SBTS sends or receives aas sends or receives following notification failure notification as response response to an IKE_AUTH or to an IKE_SA_INIT request message. The CREATE_CHILD_SA request message. failure notifications includes: The failure notifications includes the -following: NO_PROPOSAL_CHOSEN -- INVALID_SYNTAX NO_PROPOSAL_CHOSEN -- TS_UNACCEPTABLE INVALID_MAJOR VERSION -- INVALID _IKE_SPI INVALID_SYNTAX - INVALID_MESSAGE_ID

A request to retrieve the public IP address information of the FCM/FCT from the FTM has failed.

Start / Cancel

A shared (Medusa) FR is blocked.

Start / Cancel

Phase synchronization has been Start / Cancel commissioned at the btsSyncMode, but PPS and/or ToP reference clock has not become available during timeout, that is, PPS and/or ToP reference clock has to Transient Five consecutive failed login attempts been missing during startup. the BTS have been performed from WebUI.

Unit Status

Unit Status Attributes

Working

Working

Out of order

Out of order

Degraded,Out of order

Degraded

Out of order (DSP failure on every FSP) Degraded (at least one working FSP)

Degraded

Out of order

Working

Out of order

Working, when btsSyncMode = Frequency Out of order: when btsSyncMode = Phase (since start up cannot proceed without time information)

Working

Working

Working

Working

Working

Out of order

Out of order

Out of order

Working

Working

Out of order

Degraded

Out of order

Out of order

Out of order

Out of order

Out of order

Out of order

Working

Working

Working

Working

Out of order

Out of order

Out of order

Working

Degraded

Degraded (At least one RX power level is lower than threshold or the difference between max and min RX levels exceeds the limit).

Degraded

Degraded (At least one RX power level is lower than threshold or the difference between max and min RX levels exceeds the limit).

Out of order

Degraded

Degraded

Out of order

Working

Working

Out of order

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Out of order

Out of order

Out of order

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Working

Out of order

Out of order

Out of order

Out of order

Out of order

Degraded

Out of order

Out of order

Out of order

Degraded

Out of order

Degraded

Out of order

Out of order

Out of order

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Out of order

Degraded

Out of order

Degraded

Degraded

Degraded

Degraded

Out of order

Degraded,Working

Degraded,Working

Out of order

Out of order

Degraded

Out of order

Out of order

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

Out of order

Degraded

Out of order

Degraded

Out of order

Out of order

Out of order

Degraded

Degraded

Out of order,Working

Degraded

Degraded

Out-of-order during Radio Module start-up Working during Radio Module runtime

Out of order

Out of order

Degraded

Degraded

Working


Degraded (Not all fans failed) Out Of Order (All fans failed)

Working

Module = Working, Fan group = Degraded [AAS]: Working

Working

Module = Working, Fan group = Working

Working


[AAS]: Degraded if less than half of ActiveElements faulty. [Otherwise]: Out of order.


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

Degraded

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)

Out of order

Out of order

Working

Working

Out of order

Out of order

Out of order

Out of order

Out of order

Degraded

Degraded

Degraded

Degraded

Degraded

Working

Degraded

Out of order

Out of order

Degraded

Out of order

Degraded

Out of order

Out of order

Out of order

Out of order

Out of order

Out of order

Out of order

Out of order

Degraded

Out of order

Out of order

Out of order

Working

Degraded

Working

Out of order

Out of order

Degraded

Degraded,Working

Degraded

N/A

Degraded

Working

Working

Out of order

Out of order

Degraded

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

Out of order

Working

Degraded


Degraded

Not all fans have failed: alarming fan = out of order, fan group = degraded All fans have failed: all fans and fan groupfan = out of order fan Alarming = degraded, group = degraded

Degraded

Out of order

Out of order

Out of order

Out of order

Out of order

Working

Working

Working

Working

Working

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

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

Out of order

Working

Working

Working

Working

Working

Out of order

Degraded

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

Degraded

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

Degraded

"SBTS/MGMNT/CAPLIM/lteUsers" has set value.

Degraded

Degraded : - not enough licenses

Out of order

Working

Degraded,Working

Degraded (there is no other available and usable input reference source to be selected)

Degraded,Working

Working Degraded(SBTS (thereisissynchronized no other with another reference available andinput usable input source) reference source to be selected)

Degraded,Working

Working Degraded(SBTS (thereisissynchronized no other with another reference available andinput usable input source) reference source to be selected)

Working

Working (SBTS is synchronized with another input reference source)

Working

Degraded

Working

Out of order

Degraded

Working

Working

Degraded

Degraded

Working

Working

Degraded


Degraded

Degraded

Degraded

Working

Out of order

Out of order

Out of order

Working

Out of order

Working

Degraded

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

Working

Working

Working

Working

Working

Out of order

Working

Working

Working

Working

Degraded

Degraded

Degraded

Degraded

Working

Degraded

Out of order

Out of order

Degraded

Degraded


Unit status is Degraded if at least one other S1 interface is operational, or else the Unit status is 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

Out of order

Out of order

Out of order

Out of order

Degraded

Degraded

Degraded

Working

Working

Out of order

Out of order

Out of order

Degraded

Working

Out of order

Degraded

Out of order

Degraded

Degraded

Degraded

Degraded

Out of order

Out of order

Out of order

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Degraded

Working

Working

Working

Working

Out of order

Degraded

Working

Working

Degraded

Degraded

Degraded

Degraded

Degraded

Out of order

Out of order

Warning

Effect

Reported Alarms

The BTS operation might be decreased.

7106 SINGLE RAN BASE STATION PROBLEM

This fault does not immediately affect the 7108 BASE STATION SYNCHRONIZATION PROBLEM operations of the BTS, but it is a notification that the BTS master clock frequency deviates from the used reference frequency more than inin normal circumstances. The module question is out of use. This 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC alarm cancels all active alarms for the same The BTS master clock tuning continues module. regardless of the alarm, but because the BTS master clock adjustment is quite slow SBTS notinstabilities operational. 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM to filteristhe of the reference clock interface, it takes some time (even several hours) before the BTS operations start to be affected. The BTS capacity possibly decreases, 7101 RESET NOTIFICATION7108 BASE STATION SYNCHRONIZATION PROB some cells might become disabled or Flexi Zone: BTS is out of order. This fault does not immediately affect the operations of the Flexi Zone Access Point, WCDMA does not work. 7107 BASE STATION CONNECTIVITY PROBLEM but it is a SW notification that the Flexi Zone Access Point master clock frequency deviates from the used reference frequency more than in normal circumstances. Flexi Zone Point master clock The RNC NBAPAccess starts link re-establishment 7107 BASE STATION CONNECTIVITY PROBLEM tuning continues in spite the alarm, procedures and keeps onoftrying until itbut because the Flexi either succeeds orZone whenAccess the linkPoint is master clock adjustment is quite slow to removed. filter the instabilities of the reference clock The resources provided by the unit several cannot 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM interface, it takes some time (even Signaling and calls made through the be used, which means that some features hours) before the Flexi Zone Access Point related cell(s) do not work. might not work. operations start to be affected. Requested SW version cannot be installed due to the limitations of the running SW version.


Real time is not available. Alarms, logs, and 7108 BASE STATION SYNCHRONIZATION PROBLEM all reports have incorrect time. When tuning mode is phase synchronization and the alarm occurs during start-up, BTS will not go onAir as long as the alarm is active.

The BTS continues its operation with the old 7106 SINGLE RAN BASE STATION PROBLEM file.

The BTS continues operation with the old software.

7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM

If the SW download for any HW unit has failed, the SBTS continues to operate with the currently installed SW version.


If failed FCT in the 7106 SINGLE RAN BASE STATION PROBLEM If the the SW SW activation download has for any HWforunit has master FSM, the SBTS continues to operate failed, the SBTS continues to operate with with the currently installed SW version. the currently installed SW version.

If the SW fails for other HW units, If thebattery SW activation activation has is failed fororFCT in the 7100 HARDWARE PROBLEM7995 MAINS BREAKDOWN WITH BATTERY BAC The backup unit partly (for example, a Radio Module) then the master FSM, the SBTS continues to operate completely in use. The intelligent shutdown SBTS restarts andinstalled operates with the new with the currently SW version. operation hasIf started. If the mains power SW version. the SBTS is integrated to is not restored cells, sectors and carriers NetAct after the automatic recovery SW If the SWdown activation fails for other HW units, are according toand the predefined update, SBTS restarts operates Theshut cell the shutdown starts as a part ofthe the 7104 CELL SERVICE PROBLEM (for example, a Radio Module) then parameters. with the previously installed SW intelligent shutdown procedure. SBTS restarts and operates withversion. the new SW version. If the SBTS is integrated to NetAct after the automatic recovery SW update, SBTS restarts operates The cell the shutdown starts asand a part of the 7104 CELL SERVICE PROBLEM with the previously SW version. intelligent shutdowninstalled procedure.

The SBTS does not send alarms that are 7102 RESOURCE BLOCKED BY USER related to the blocked unit or module to the network management system (NMS). Alarmsending to the SBTS Element Manager is always enabled. Thesend alarmany cancellations The SBTS does not alarms that 7102 RESOURCE BLOCKED BY USER are always sent to the NMS. are related to the blocked cell or the units commissioned to the blocked cell of the Phone cannot be System established through Networkcalls Management (NMS). the blocked unit or module. Alarm-sending thesend SBTS Element The SBTS doestonot alarms to the 7102 RESOURCE BLOCKED BY USER Manager is always enabled. Alarm Network Management System (NMS) when cancellations are always sent to the NMS. the SBTS is blocked. Alarm cancellations are sent to the NMS. Calls through the blocked cell are Since it is not possible to use thephone faulty calls 7100 HARDWARE PROBLEM transferred to another cell. New All cells are disabled. WSP FSP in the configuration, BTS cannotorbe established through thethe blocked capacity decreases or the BTS gets faulty. cell. The default values are used for the cell. The 7105 RAT BASE STATION PROBLEM cell operation might become degraded.

Depending on the reported severity and HW 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM module for which the alarm is reported, the SBTS capacity might decrease (Hardware problem) or the SBTS might not be operational at all. is decreased or SBTS The SBTS capacity 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM might not be operational at all (HARDWARE PROBLEM). The gain control feature is lost, possibly 7104 CELL SERVICE PROBLEM generating an interference in the network. The NBAP common measurement message is incorrect, because of missing measurement dataunit from Module The affected FCT is the not Radio operational. In 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE module. case of an FSP fault, the channel capacity is lost and the cell(s) might become unavailable. The associated cells in the Radio ModuleFCT become The affected unit isfaulty. not operational. In

7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE

case of an FSP fault, the channel capacity is lost and the cell(s) might become unavailable. The associated cells in the Radio ModuleFCT become The affected unit isfaulty. not operational. In

7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE case of an FSP fault, the channel capacity is lost and the cell(s) might become unavailable. The associated cells in the Radio Module faulty. cell might not 7107 BASE STATION CONNECTIVITY PROBLEM Handing trafficbecome over to another work.

The affected cell state remains unchanged. 7104 CELL SERVICE PROBLEM

The affected cell state remains unchanged. 7104 CELL SERVICE PROBLEM

The cell setup is rejected.

7105 RAT BASE STATION PROBLEM

Calls are not possible through the affected 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM cell(s) (if severity is critical). Calls are possible but the cell capacity and performance might be decreased (if severity is major). The cell setup has succeeded but the cell 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM state is disabled.

The minimum HSUPA capacity, which is 7105 RAT BASE STATION PROBLEM based on the commissioning parameters, is not fully guaranteed. The HSUPA resource handling still works dynamically in addition to the partiallyisreserved minimum capacity 7104 CELL SERVICE PROBLEM Cell capacity decreased. for the HSUPA.

Cell capacity is decreased.

7104 CELL SERVICE PROBLEM

This fault prevents the BTS from functioning 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM properly. Some baseband processing resources are not the BTS is operational. BTSworking HSUPAorCapability is not degraded in the


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


Depending on the reported severity, the WCDMA RAT capacity might decrease or the WCDMA RAT might go completely out of order.

7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM

Malfunctioning cell setups or rejected new PIC pool configurations are ignored by TCOM.

7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM

Not enough CCCH Processing Set licenses 7105 RAT BASE STATION PROBLEM commissioned to the cell.

FSP is not operational.


The cell is temporarily degraded and all connected UEs are informed of the cell's status. All ongoing calls are unaffected but the UE is unable to establish new calls.


Not enough CCCH processing capacity to setup the cell with the requested parameters.


The BTS memory operations including software downloads and parameter updates, are unstable.

7100 HARDWARE PROBLEM









The BTS capacity decreases or the BTS goes out of order. The Digital Signal Processing (DSP) is not working correctly.

7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM7106 SINGL

If this fault is cancelled in 4 seconds or less 7105 RAT BASE STATION PROBLEM7106 SINGLE RAN BASE STATION PRO after the fault appears, then there is no effect. The Card functionality remains degraded, but unit status is working. The BTS is out of order or the capacity is 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE If this fault is active for more than 4 degraded. seconds, this indicates a SWS ASIC HW problem, and the digital signal processing (DSP) is not working correctly. BTS capacity Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION is permanently decreased. alarming.

Device configured on the EAC line is alarming.

7103 EXTERNAL ALARM NOTIFICATION

















































Some operations in the BTS are being interrupted. Depending on the fault source, the BTS or cell operation is degraded or faulty.

7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC

The BTS capacity possibly decreases.


Processing resources, cells, or the whole BTS might be out of order.



The system clock frequency starts to drift 7108 BASE STATION SYNCHRONIZATION PROBLEM and the air interface frequency accuracy starts to degrade. The BTS might work properly for a few days without any signs of a problem butoperate the network performance The BTS can properly for months or 7108 BASE STATION SYNCHRONIZATION PROBLEM might start to gradually decrease. even a year when being in the 5% margin area, but eventually the DAC value reaches the adjustment limit (0 or 4095) and the OCXO cannot the synchronization The BTS is notfollow operational. reference signal beyond the limit. When the DAC value is 0 or 4095, the effect depends on the network synchronization setting defined in the BTS commissioning. - The MHA is faulty, the RX performance is degraded. The cell size might be reduced Effects in Frequency Synchronization mode: (7104 CELL SERVICE Assuming that the BTSPROBLEM). reference signal has -correct No impact on system HARDWARE accuracy when (7100 the DAC value PROBLEM). theisadjustment limitperformance 0 or 4095 is -reaches The MHA faulty, the RX (meaning indication degraded.the Thealarm cell size might is real, not caused by incorrect reference), the BTS air be reduced (7104 CELL SERVICE interface starts to drift from the correct value PROBLEM). and after a while (weeks or months) the -The No antenna impact on theissystem (7100 correctly. line operating 3GPP accuracy limitnot is not met any more. HARDWARE PROBLEM). Cell is decreased. Evencapacity in that stage the BTS might still be operational but the system performance might drop, affecting, for example, the handovers. The cell is disabled if all of its critical radio resources are affected, or the cell operation Effects in Phase Synchronization mode: is degraded if a part of the cell's resources When the DAC value is affected, but the cellreaches still hasthe critical adjustment limitare 0 or 4095, the basic LTE resources that working. The output power of the antenna is system operation effects are the same as in decreased and the antenna is not working Frequencysignal Synchronization mode but the Downlink transmission on the given at thefeature(s) optimumwhich level. require Phase LTE antenna line is disabled, and the SynchronizationRadio become(s) corresponding Modulenon-operational transmitter is because The RX path the OCXO operating cannot performance adjust isphase unusable. Hence, the overall Radiothe Module synchronization decreased. state is affected.any more.

7108 BASE STATION SYNCHRONIZATION PROBLEM

7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM






The signal path is unusable. The cells using 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM the faulty unit might not work.

The signal path is unusable. The cells using 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM the faulty unit might not work. The BTS capacity possibly decreases.










The antenna line device is not working properly. The cell operation is degraded.


The device is out of use.


The unit might be started with an old SW 7104 CELL SERVICE PROBLEM version and is therefore not compatible with any other units. BTS is out of order in case the fault source is FSP. BTS capacity decreased if fault source is FBB.


The MHA gain is decreased. The cell performance may be decreased.


The MHA gain is decreased or there might even be a loss. The cell performance is decreased.


Some antenna line device functions might not work properly.








Default values for the internal delays in the BB card are used. Effects on functionality: 1) Cell boundaries cannot be defined as accurately as with measured internal If other references are available, the delay values. synchronization reference source changes 2) 3GPP Dedicated measurement (RTTthis to another source. Tuning then follows measurement) accuracy is lower than with new reference. measured internal delay values. If other references are available, the If other references are not source available, the synchronization reference changes BTS master clock (OCXO) tuning is to another source. Tuning then follows this halted and the BTS synchronization drops new reference. to holdover mode. Calls are not possible through the affected If otherorreferences are not available, the cell(s) calls are possible but the cell BTS master clock (OCXO) tuning is halted capacity and performance might decrease and the BTSSERVICE synchronization drops to (7104 CELL PROBLEM). holdover mode. Cells (7106 SINGLE Calls not are affected not possible through theRAN affected BASE STATION PROBLEM). cell(s) or calls are possible but the cell




7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA


capacity and performance might decrease (7104 CELL SERVICE PROBLEM). No the system (7106 SINGLE Theimpact Radio on Module is configured with default 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM RAN BASE STATION PROBLEM) settings and the performance is not as expected.

The faults may occur the (may be Callsfollowing are not possible through affected 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7108 BASE STAT generated) in the consequence of fault cell(s) or there might be problems with calls 1902: made through the affected cell(s) (7104 1907/EFaultId_FrTxOutOfOrder CELL SERVICE PROBLEM). 110/EFaultId_UnitRnwConfigAl Calls are not possible through the affected 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7108 BASE STAT 134/EFaultId_RxAntennaSignalLevelDiffere Cells not affected BASE STATION cell(s) or calls are (7108 possible but the cell nceTooHighAl SYNCHRONIZATION PROBLEM) capacity and performance might decrease 1924/EFaultId_FrConfigurationFileCorrupte (7104 CELL SERVICE PROBLEM). d Calls not affected (7108 BASE STATION SYNCHRONIZATION PROBLEM)

Calls are not possible through the affected cell(s) or calls are possible but the cell capacity and performance might decrease (7104 CELL SERVICE PROBLEM).


There might be problems with calls made Cell(s) SINGLE RAN throughnot theaffected affected(7106 cell(s). BASE STATION PROBLEM)


Calls are not possible through the affected cell(s) or calls are possible but the cell capacity and performance might decrease.


There might be problems with calls made through the affected cell(s) (7104 CELL SERVICE PROBLEM). No impact on the cell (7106 SINGLE RAN BASE STATION PROBLEM) Calls are not possible through the affected


cell(s) or calls are possible but the cell capacity and performance might decrease (7104 CELL SERVICE PROBLEM). No impact onpossible calls (7106 SINGLE RAN Calls are not through the affected BASE STATION PROBLEM) cell(s) (if severity is critical). There can be problems with the calls made through the paths affected cell(s) (if severity The TX/RX of the Radio moduleisare major). out of order. Calls are not possible through the affected No effect on the system, however, it might cell(s) (if the severity is critical). not be possible to commission the cells on Calls are possible but cell with capacity There might be (otherwise). problems calls and made the affected Rx performance might decrease through the affected cell(s). (if severity is major). No impact on the system (if severity is minor) There might be problems with calls made through the affected cell(s).

This fault should cancel itself. Module heating is ongoing. During Radio Module start-up, the affected cell resources are not reported to the TCOM. The Radio Module configuration might fail








and cause another fault, and there might be problems with calls made through the affected cell(s). The default configuration is used and the No on system (if severity is minor). cell impact TX and/or RX performance is degraded. There might be problems with calls through the affected cell(s) (7104 CELL SERVICE PROBLEM). Cells not affected (7106 SINGLE RAN BASE STATION PROBLEM) The following faults might occur (might be generated) in consequence of fault 1924: 1900/EFaultId_FrConfiguringFailed 1902/EFaultId_FrFileNotFound


Calls are not possible through the affected cell(s) (if severity is critical). Calls are possible but the cell capacity and performance might decrease (if severity is major). The communication between the system No impact system severity is minor). module andonthe Radio(ifModule might be corrupted. Calls are not possible through the affected cell(s) severity is critical). The TX(ifpower level is decreased and there Calls are possible cellmade capacity and might be problemsbut withthe calls through performance might decrease (if severity is the affected cell(s). major). No impact on the system (if severity is There minor).might be problems with calls made through the affected cell(s) (7104 CELL SERVICE PROBLEM). Cell(s) is not affected) (7100 HARDWARE PROBLEM). The fault might mean that fans are not


7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7108 BASE STAT




connected/working. This might cause the RF module to overheat. The be automatically If thefault fanscan areonly not rotating as required, there 7100 HARDWARE PROBLEM cancelled for RF modules where fans are is a risk of the module overheating. detected based on speed response (FRM3.x, FRGT from version 102 and FRGS from version X21). All other RF If the fansrequire are nota rotating modules reset. as required, there 7100 HARDWARE PROBLEM is a risk of the module overheating.

If the fans are rotating faster than required, unnecessary noise appears.


The RF Module might overheat, but there is 7100 HARDWARE PROBLEM no immediate effect on the module operation.

Calls are not possible with the affected cells 7104 CELL SERVICE PROBLEM7606 TRX FAULTY7607 TRX OPERATION DE (7653 CELL FAULTY). Calls are possible but the cell capacity and performance might decrease (7654 CELL OPERATION DEGRADED). There might be problems with calls made 7104 CELL SERVICE PROBLEM7606 TRX FAULTY7607 TRX OPERATION DE No impact on system with the affected cells (7652 (7654 BASE STATION NOTIFICATION). CELL OPERATION DEGRADED). No impact on the system (7652 BASE STATION Problems NOTIFICATION). might occur during calls made with the affected cell(s) (7104 CELL SERVICE PROBLEM). No impact on cells (7106 SINGLE RAN BASE STATION PROBLEM).


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


The antenna line is faulty. All cells that use this antenna line are affected.


Downlink signal transmission on the given antenna andorcorresponding The BTSline unitisisdisabled, transmitting receiving 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM RF transmitter is unusable. Hence,The overall data with degraded performance. fault RF state affected. does not is trigger any actions for BTS. Radio Modules External Alarm and Control line(s) might not be working correctly.


For the primary optical link to the Radio 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC Module, the cell(s) of the RF Module behind the broken connection is/are out of order and the RF Module cannot be used. For the primary optical link to the Radio For the primary linkoftothe Extension System Module, the cell(s) RF Module behind Module, all cells that have been allocated the broken connection is/are out of order to BB on thecannot Extension FSM are out andresources the RF Module be used. of order and the Extension FSM cannot be In the case of primary optical link to Radio used. For the primary linkoftothe Extension System Module, the cell(s) Radio Module Module, all cells that have been allocated behind broken connection arethe outRadio of to For the the secondary optical link to BB resources on the Extension FSM are order and the Radio Module cannot be out Module or thethe Extension System Module, of order and Extension FSM cannot be used. the cells are transmitted the The BTSthat capacity decreases.through The optical used. antenna or have resources allocated interface carrier loses synchronization if the In the case of primary link to Extension via secondary link are affected. Cells not number of errors exceeds the to defined limit. For the secondary link thebeen Radio System Module, alloptical cells that have affected by the fault might still be Module or the Extension System Module, allocated to BB resources on the Extension operational. the areorder the The RP3 traffic totransmitted the and appropriate Radio FSMcells are that out of thethrough Extension antenna carrier or have resources allocated Module, Extension System Module, or FSM cannot be used. via secondary linkisare affected. Cells not summing device malfunctioning. The affected by the fault might still be related cell(s) to the Radiolink Module) In the case of (traffic secondary optical to operational. is/are not operational, or the BTS operation Radio Module or Extension System Baseband bus RP3 traffic to the RF is degraded to the System Module, the (traffic cells that are Extension transmitted Module/Extension System Module, or Module), or the BTS is out of order(traffic through the antenna carrier or have between the summing and optical devicestois the summing device). resources allocated via secondary are not working. Depending on the link,link either affected. Cells notoraffected the BTS capacity cell operation is Baseband bus RP3 traffic to the RF might still be operational. degraded. Module/Extension System Module, or




7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7108 BASE STAT

7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM7106 SIN

7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM7106 SIN

between the summing and optical devices is not working. Depending on the link, either the BTS capacity or traffic cell operation is Baseband bus RP3 to the RF 7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM7106 SIN degraded. Module/Extension System Module, or between the summing and optical devices is not working. Depending on the link, either the BTS capacity or cell operation is degraded.

Baseband bus RP3 traffic to the RF 7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM7106 SIN Module/Extension System Module, or between the summing and optical devices is not working. Depending on the link, either the BTS capacity or traffic cell operation is Baseband bus RP3 to the RF 7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM7106 SIN degraded. Module/Extension System Module, or between the summing and optical devices is not working. Depending on the link, either the BTS cell operationeffects is There arecapacity possiblyorno immediate on 7106 SINGLE RAN BASE STATION PROBLEM degraded. the BTS operation but it might cause an optical interface alarm. The RP1 synchronization burst related to 7108 BASE STATION SYNCHRONIZATION PROBLEM the failed FIFO is removed and possibly has to be sent again. The BTS operation is to be degraded.

The traffic between the System Module and 7101 RESET NOTIFICATION7108 BASE STATION SYNCHRONIZATION PROB Radio Module/Extension System Module becomes unreliable. Some calls or other connections might be lost.

The data traffic to the appropriate Radio 7101 RESET NOTIFICATION7106 SINGLE RAN BASE STATION PROBLEM Module or Extension System Module is malfunctioning. Depending on the alarming module, the BTS operation is faulty (Master System Module), or baseband the BTS operation RP3 traffic from the to the is 7105 RAT BASE STATION PROBLEM7106 SINGLE RAN BASE STATION PRO degraded (Extension System Module). appropriate module/unit is malfunctioning. The BTS operation is degraded. The BTS is out of order.

7101 RESET NOTIFICATION7108 BASE STATION SYNCHRONIZATION PROB

Baseband bus RP3/RP3-01 traffic might not 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM operate correctly. The cell operation is degraded. SW update needed.


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


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

7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM

The BTS capacity decreases


The BTS operation is degraded because 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE some of the BTS resources are unavailable.

The BTS operation is degraded, because 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE some of the BTS resources are unavailable.

The BTS is out of order.


sRIO communication with devices on the impacted port is no longer possible.


The cell might enter "sleeping" mode.


The SBTS GSM capacity decreases, cell might become disabled.






TRXes which do not fit to profile stay disabled.




TRXes which do not fall into the range categories remain disabled.


The SBTS GSM capacity decreases, cell becomes disabled.


Cell remains as offline.


Available hardware resources are not fully utilized before resetting the SBTS.


GNSS become unusable.


The BTS resources have decreased or the BTS is faulty.

7101 RESET NOTIFICATION7108 BASE STATION SYNCHRONIZATION PROB

Depending on the reported alarm, the fault situation might have no impact on the operation, the BTS capacity might have decreased or the BTS might not be operational at all. The unit might be started with an old SW

7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7102 RESOURCE B


version and is therefore not compatible with any other units. There is no immediate effect on cell operation. The device continues operation with the previously used data.


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


The module in question is out of use. This 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC alarm cancels all active alarms for the same module. The commissioned cells using the missing RP3-01 link are not activated.


The RS485 interface is not operating correctly. The cell capacity decreases.


Commissioned cells are not activated.


Fan control is not optimized. The effect of noise/temperature level is marginal.


FSP DSPs not in use; SBTS operation is degraded or faulty.


If the fans are not rotating as required, there 7106 SINGLE RAN BASE STATION PROBLEM is a risk that the module temperature is rising too high. If the fan(s) is/are not rotating as required, there is a risk that the module temperature is rising too high.


If the fans are rotating faster than required, it creates unnecessary noise.


Source unit has inconsistent SW version.






Calls are not possible through affected cell(s) (if severity is critical).


Calls are possible, but the cell capacity and performance may beisdecreased (if and severity The system module out of order the 7108 BASE STATION SYNCHRONIZATION PROBLEM is major). BTS is out of order.











Due to problem detection in Start-up, BTS remains out of order.

7109 BASE STATION SECURITY PROBLEM

When the fault is detected during startup, 7105 RAT BASE STATION PROBLEM the BTS is not operational. When the fault is detected during runtime, the requested new transport configuration is not applied. GNSS accuracy is not guaranteed.



In case of VSWR major or VSWR minor, value set is out of range during commissioning. BTSOM sets the nearest values supported by Radio Module.


Software download has failed and must be retried.




The unsigned release has been 7109 BASE STATION SECURITY PROBLEM 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 passive file system and the previous SW build is still used. If it is downloaded with activation after a BTS reset, the new downloaded unsigned SW build is used.



The MHA does not compensate the signal loss of the long feeder cable to the BTS located at the base of the tower.


BTSSCW/numberOfHSDPASet1 is set to 0, 7110 BASE STATION LICENSE LIMITATION BTSSCW/numberOfHSDPASet2 is set to 0, BTSSCW/numberOfHSDPASet3 is reduced to CAPLIM/HSDPAUsers/72 and rounded up. BTSSCW/numberOfHSUPASet1 is reduced 7110 BASE STATION LICENSE LIMITATION to CAPLIM/HSUPAUsers/24 and rounded up. None

7110 BASE STATION LICENSE LIMITATION

SBTS drops low priority IP traffic.

7110 BASE STATION LICENSE LIMITATION

Baseband extension module cannot be 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM used until SBTS undergoes a manual reset.

BTS will not have time synchronization from 7108 BASE STATION SYNCHRONIZATION PROBLEM the NTP server(s) listed in the alarm.

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


If other references are available, the 7108 BASE STATION SYNCHRONIZATION PROBLEM synchronization reference source changes to another source. Tuning then follows this If other references are unavailable, the BTS new reference. master clock (OCXO) tuning is halted and If other are available, the BTSreferences synchronization drops tothe holdover 7108 BASE STATION SYNCHRONIZATION PROBLEM synchronization reference source changes mode. If references are not then available, the toother another source. Tuning follows this BTS master clock (OCXO) tuning is halted new reference. and the BTS synchronization drops to Micro DTX functionality (LTE1891) is not 7100 HARDWARE PROBLEM holdover mode. activated on the antenna line. If other references are not available, the BTS master clock (OCXO) tuning is halted and the BTS synchronization drops to holdover mode.

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


The active base station configuration is not the same as requested in the configuration change.


BTS performs switchover to another input reference clock source if available.


RAT that is indicated in the Source field of the fault is not operational.


Cell performance is decreased.


In case of U-plane overload, the system initiates actions to decrease the amount of load by limiting the traffic or the functionality on traffic. The performance power might be The system PHICH transmission is not degraded, especially in cases wheretothe boosted enough or at all compared theUplane overload countermeasures are operator's setting. enabled. "Fault ID Name" information field identifies Celltype operation is downgraded. the of overload detected: - TrOne refers to trigger UPOVT1: speech quality based detection on user plane - TrTwo refers to trigger UPOVT2: quantity based detection TTI on user plane Cell operation is per downgraded. - TrThree refers to trigger UPOVT3: PDSCH too long delay based check on user plane.





In case of U-plane overload, the system 7104 CELL SERVICE PROBLEM initiates actions to decrease the amount of load by limiting the traffic or the functionality on traffic. The system performance might In case of U-plane overload, thebe system 7104 CELL SERVICE PROBLEM degraded, especially in cases where the of Uinitiates actions to decrease the amount plane are load byoverload limiting countermeasures the traffic or the functionality enabled. on traffic. "Fault ID Name" information fieldbeidentifies The system performance For S1: The eNB loses themight connection to S- 7107 BASE STATION CONNECTIVITY PROBLEM the type of overload detected: degraded, especially casesGTP-U where data the UGW. All calls using theinfailed -plane TrOne refers to trigger UPOVT1: speech overload countermeasures aredata path are released, and new GTP-U quality based detection on user plane enabled. tunnels nottocreated the failed GTP-U -"Fault TrTwoIDare refers trigger for UPOVT2: quantity Name" information field identifies data path until it works again. based detection per TTI on user plane the type of overload detected: -- TrThree referstototrigger triggerUPOVT1: UPOVT3:speech PDSCH TrOne refers too long delay based check on user plane. quality based detection on user plane - TrTwo refers to trigger UPOVT2: quantity based detection per TTI on user plane - TrThree refers to trigger UPOVT3: PDSCH too long delay based check on user plane.

The S1 interface is unavailable.

7107 BASE STATION CONNECTIVITY PROBLEM

If no other S1 interface is available for use, BTS operation is considered faulty and no calls caninterface be set up. The X2 is unavailable. Handover


of calls to or from cells of the associated If there isBTS at least one other S1Base interface adjacent is not possible. station available for use, BTS operation is (BTS) operation is considered degraded. considered degraded and the BTS can One of the transport(that paths(SCTP) in SCTP continue operation is, set up calls) connection to MME has failed. Only using available S1 interface(s). applicable when SCTP multi-homing is supported. An alternate transport path is available to pursue the operation. M3 interface is unavailable.



No MBMS service can be provided. One of the transport paths(SCTP) in SCTP 7107 BASE STATION CONNECTIVITY PROBLEM connection to MME (which provides MBMS service) has failed. Only applicable when SCTP multi-homing is supported. An alternate path is available to to SBTS LTEtransport is not configured according 7105 RAT BASE STATION PROBLEM pursue the operation. the radio network plan file. The SBTS LTE is waiting for the correct radio network configuration file. The cell is disabled.


The cell is disabled.


[LTE RAT] See fault processing diagram: WCDMA_BTS/BTS_Requirement/LTE Operability and Maintenance(LTE_OAM_8455). SBTS LTE is not operational.


[Otherwise] In case of subscriber trace activation, if the failed trace connection was used for Trace session (forreports, subscriber/cell/interface) sending the trace the SBTS cannot be the activated/deactivated. considers trace activation for that subscriber as failed.



In case cell trace and new interface The BTSofcannot accept UEs trace, if 7105 RAT BASE STATION PROBLEM the failed trace connection was for attempting registration in any of used the reported sending the trace reports, thean SBTS doesby misconfigured PLMNs. Such attempt not start tracing until the trace connection new UEs results in call failure at the BTS. is established successfully. The UEs that might have already registered In case of syslog PLMN(s) and message trace, if the in misconfigured remain failed connection was used for sending the unimpacted. reports, the SBTS does not start streaming until the connection is established successfully.

The fault has no effect on the base station operation but the LNADJ and/or LNADJL object was not stored in the eNB.


The fault has no effect on the base station operation but LNADJW object with newly learnt WCDMA neighbor cell configuration via ANR specific measurements was not stored in eNB. The fault has no effect on the base station


operation but LNRELW object with newlylearnt WCDMA neighbor relation configuration via ANR specific measurements noton stored in thestation eNB. The fault has nowas effect the base operation. The WCDMA neighbor relation, which is reported by a UE because of activated ANR feature(s): 1) not been because to the actual Nohas handover canstored be performed cells with number of LNRELW per cell (LNCEL) per the affected PCI and frequency. UTRAN carrier (in ANRPRW profile) is equal to or greater than the lnRelWLimitForAnr parameter value (in ANPRW profile) or The cellbeen that stored cannotbut be at recovered 2) has least oneremains of unavailable. LNRELW's mobility paremeters (psHoAllowed, srvccAllowed) has been set In case when BTS itO&M is able to the 'forbidden' because has system exceeded limit to restore disabled cell(s)without in an 3GPP 36.331 (32). (See If X2 link is available, noalso typeMeaning of negative on other working cell(s) at paragraph). handoverimpact to the neighbor cell is possible BTS O&M system restores the disabled all. cell(s). In this case alarm "Unit autonomous If the UE-based ANR is activated, there will reset as recovery action (6277)" be continuous retries to resolve the ECGI. The handover failure rate for the affected is reported when autonomous baseband cell mightreset be increased. recovery is processed by O&M. See fault 52: EFaultId_UnitAutonomousResetAl description. The effect depends on the features used by the operator. The following LTE features are deactivated (if configured to be used):




7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM




-The LTE1117 (LTEfailure MBMS) handover rate for the affected 7104 CELL SERVICE PROBLEM -cell LTE1113 (eICIC - macro) might be increased. - LTE1496 (eICIC - micro) - LTE2007 (Inter eNB Carrier Aggregation) - LTE2208 (eICIC extensions-micro) Cells and eNBs remain in service, but 'Inter 7105 RAT BASE STATION PROBLEM - LTE2209 (eICIC enhancements) eNB Carrier(Network Aggregation'-related features - LTE2554 Assisted Interference that require consistent parameters between Cancellation and Suppression) cluster members are taken out of service. Cells and eNBs remain in service, but 'Inter 7105 RAT BASE STATION PROBLEM eNB Carrier Aggregation'-related features that require the same SW version between cluster members are taken out of service.

'Inter eNB Carrier Aggregation'-related features that require an inter-eNB link are taken out of service.


If the maximum number of allowed neighbor related objects is reached, the eNB does not allow the creation of additional neighbor related objects, either via O&M or via X2 Setup/X2 Configuration Update. If a and The eNB continues normal operation measurement report on the signal power or automatic neighbor relation handling is not quality of the neighbor is received, handover impacted, that is, neighbor related objects preparation is triggered, no X2 new object is can be created via O&M but or via Setup/X2 created. A result of this might be that no X2 Configuration Update. BTS isestablished operational but system level (interlink is with such neighbor or that If the number of objects infunctionality the database BTS) carrier aggregation is the CGI is known for such BTS. increases reaches or even degraded. further Carrierand aggregation with the exceeds the configured value misconfigured carrier aggregation relations New objects can be stored again when the maxNumAnrMoiAllowed, automatic is not possible. However, carrier number of neighbor related objects in the Resource DSPs pool is unavailable. neighbor relation the functionality is degraded aggregation other, properly BTS database is below Any cell that with cannot be put into usedetected: due to and an alarm indicating "Overload configured carrier aggregation relations is maxNumAnrMoiAllowed. the lack of available resource pools, is also max number of neighbor relation objects working normally. not available. reached" is raised. BTS cannot continue operation. All cells are disabled. BTS autonomous reset will be performed to recover if the number of allowed autonomous BTSorresets is of notthe exceeded. Handovers from to cells related




7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM



adjacent BTS are not possible.

Handovers to cells of the related adjacent BTS are not possible.


The S1 interface is not available for call setup and existing calls are released.


The S1 interface is unavailable and the BTS 7107 BASE STATION CONNECTIVITY PROBLEM is not available for call setup.

If the update of the TAC or PLMN identities 7107 BASE STATION CONNECTIVITY PROBLEM is not successful, the eNB performs S1 setup, which means service loss for affected cell(s). 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.

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 change. Critical impact information on FSP operation.


The BTS capacity decreases or the BTS is out of order. The Digital Signal Processing (DSP) does not work correctly.


The BTS capacity decreases or the BTS is out of order. The Digital Signal Processing (DSP) is not working correctly.


The BTS capacity decreases or the BTS is out of order. The Digital Signal Processing (DSP) is not working correctly.


The M3 interface is unavailable and MBMS service can no longer be provided.


The M3 interface is unavailable and MBMS service can no longer be provided.


The available resources for MBMS session broadcasting are less than required. The start of MBMS sessions might be rejected by the eNB because of a lack of resources.


One or more MBMS sessions cannot be broadcast by eNB because of a lack of resources.



The warning is triggered by the eNB if the 7105 RAT BASE STATION PROBLEM MME could not be informed about the modified values(s) via the MCE configuration update procedure after several retries. The communication link between the local 61022 BFD group $bfdGrpId down SBTS and the BFD peer is defective. No The eNB stops all active MBMS sessions communication is possible. and waits for new session requests from the MME if the update of the global MCE ID or MBMS service area identities was not successful A failed update of the MCE name is tolerated by the eNB.

Possible impact on the connections over this interface: - no calls are possible -No loss of or remote to data clockmanagement information isaccess exchanged other network elements via this interface. - loss of synchronization if the interface is used as aimpact synchronization source over Possible on the connections this interface: Possible effects: - voice calls or data connections are aborted and established anymore - no cannot calls arebepossible. -- remote management connectivity is lost loss of remote management access to and cannot be established anymore other network elements. The interface cannot be used -- loss of synchronization ifcannot the for interface is IKE SAs andItIPsec SAs be transmission. can be used for connectivity used as a synchronization source established re-keyed. checks only.or - Depending on use of the Ethernet interface the above described impact can occurinterface for the local The of theSBTS SFP and/or moduleother cannot be (S)BTS if they are chained via the used forelements transmission. Ethernet interface. No data or clock information is exchanged via this interface of SFP module. The module's laser cannot be switched The SFP Certificate Revocation List could not be on. updated. New revoked certificates remain unknown to the SBTS. The link may not be successfully established since the interface of the SFP The SFPisismissing not operational. module or incompatible. The interface of the SFP module cannot Possible impact on the connections over be used for transmission. this interface of SFP module: The SFP module's can't be cannot switched -Possible voice calls or datalaser connections be impact: on. established. - slow management access to the SBTS -and remote connectivity cannot othermanagement network elements in the network No data or clock information exchanged established. -be poor voice quality and data is performance via thisofinterface of SFP module. - loss synchronization if the interface is The management data usedperformance as a synchronization source collected on this interface becomes Possible impact on the connections invalid. over this interface of SFP module: - voice calls or data connections cannot be established. Possible impact on the connections over the -interface remote management in question: connectivity cannot be established. - no calls are possible loss of of remote synchronization if the access interface -- loss management to is used as a synchronization source other network elements in the RAN Possible impact on the connections over

61028 LOF on unit $U, interface $IF

61029 LOS on unit $U, interface $IF

61030 Dead Peer Detected

61040 Interface under test on unit $U, interface $IF for $T minutes




61104 EBER on unit $U, interface $IF

61150 LOMF on unit $U, interface $IF

61151 AIS on unit $U, interface $IF

61152 RDI on unit $U, interface $IF

this interface: - no calls are possible -Possible loss of remote impact:management access to other network elements in the RAN 1. No calls are possible for the connections over this transport module. 2. 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. -Possible loss of remote access. impact management on the connections over this interface: - no calls are possible anymore - loss of remote management access to other in the RAN Impactnetwork on the elements connections over this

61250 IPCP Failure

61251 LCP Failure on Interface $IF

61252 PPP Interface down

interface: - loss of remote management access. The requested service is not available.


The communication link between the local 61605 BFD $session down, ingress, $sourceIP to $destinationIP 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 $session down, egress, $sourceIP to $destinationIP 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.

61607 Auto-negotiation mismatch, on unit $U, Ethernet interface $IF

Possible impact on the connections over this Thisinterface: alarm is an indication that the backhaul 61610 TWAMP RTT threshold crossed -capacity Increased delay and as for packet traffic with thevariation same profile increased average delay for all voice/packet this TWAMP session (DSCP value, packet and connection size)management may be too small, because the -measurement Increase of packet loss due to congestion. packets are scheduled later 61611 TWAMP PLR threshold crossed This alarm is an indication that the backhaul -than Loss of synchronization/Timing source lost before. capacity for over trafficPacket with same profile as this with Timing (IEEE1588v2) due TWAMP session (DSCP packet size), to increased packet delayvalue, variation. may beofmuch too small, becausesource some of - Loss synchronization/Timing lost the withmeasurement Synchronous packets Ethernet.seem to have 7109 BASE STATION SECURITY PROBLEM been thrown away. The TWAMP measurement packets are lost because of degraded traffic throughput. Re-authentication 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.


SyncE is no longer a working synchronization source.


BTS performs switchover to another ToP master if available.


The remote peer to come online with the 61632 Dup Addr detected $duplicateIpv6Address same IP address on the same subnet as local peer would just disable their network interface and give an error until the situation is resolved by the administrator. Possible impact: 7100 HARDWARE PROBLEM This allowsare thepossible local peer - No calls for to thecontinue connections functioning without disruption, but over this HW. completely breaks IP base communications All IPsec policies are ignored 61639 IPsec emergency bypass active for configured the connected network. and all the SBTS traffic is sent unprotected.

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 [port $port,] [mac $m]

No further logins will be permitted for that account until the account is unlocked.


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 can't be established and used.

61646 IPSec SA failure

The BTS is not commissioned or integrated 7107 BASE STATION CONNECTIVITY PROBLEM to the network. The BTS cannot be accessed or configured remotely. Calls are not possible through the affected cells (if severity is critical). Calls are possible but the cell capacity and performance might decrease (if severity is major). When the BTS is the sync hub slave and No impactison systemstart-up (if severity is minor). rfsharing enabled, is stopped.

7102 RESOURCE BLOCKED BY USER


Otherwise, start-up is continued without a The BTS does faultsisrelated to the reference clock,not butsend the BTS not directed blocked Flexi Radio module (FR) to the to OnAir. None network management system (NMS). Fault 7109 BASE STATION SECURITY PROBLEM sending to BTS Site Manager is always enabled. The fault cancellations are always sent to the NMS.

Reported Alarms Description

7100 HARDWARE PROBLEM (in case of FSP or FBB if cells are not impacted, FR(there is enough critical cell resources left for the cell to remain operational), ESM, FT, ALD(failure has no impact on cell)) 7101 NOTIFICATION (FBB (in (for casefault of fault 7105 RESET RAT BASE STATION PROBLEM source 4052 raised during FBB hot removal scenario) RAT) 7104 SERVICE PROBLEM (in case FSP or 7101 CELL RESET NOTIFICATION (raised only ifofRESET FBB if cells are impacted, FR(there is not enough RECOVERY is triggered) critical cell resources left for the cell to remain 7108 is reported always has impact on cell)) operational), ALD(failure 7101 reported in a case of autonomous recovery reset will be performed

7106 SINGLE RAN BASE STATION PROBLEM (in case the source is FCT or FSP or FR without allocated LCRs) 7104 CELL SERVICE PROBLEM (in case the source is Radio Module with allocated LCRs or FF)

7106 SINGLE RAN BASE STATION PROBLEM (in case the source is FCT) 7104 CELL SERVICE PROBLEM (in case the source is Radio Module)

7100 Reported towards NetAct 7995 Reported towards BSC


7100 HARDWARE PROBLEM (if cells are not affected) 7104 CELL SERVICE PROBLEM (if cells are affected)

7100 HARDWARE PROBLEM (if cells are not affected) 7104 CELL SERVICE PROBLEM (if cells are affected)

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (thereset faultissource 7101 CELL RESET NOTIFICATION (when being is FR) performed) 7105 RAT BASE STATION PROBLEM (the fault source is FSPreset or DSP) When has not been triggered for any reason: 7104 SERVICE PROBLEM (thereset faultissource 7101 CELL RESET NOTIFICATION (when being is FR) performed) 7105 RAT BASE STATION PROBLEM (the fault source is FSPreset or DSP) When has not been triggered for any reason: 7104 CELL SERVICE PROBLEM (the fault source is FR) 7105 RAT BASE STATION PROBLEM (the fault source is FSP or DSP)

7101 RESET NOTIFICATION (when reset is being performed) 7104 CELL SERVICE PROBLEM (when reset has not been triggered for any reason) 7101 RESET NOTIFICATION (when reset is being performed) 7104 CELL SERVICE PROBLEM (when reset has not been triggered for any reason)

7101 RESET NOTIFICATION (when reset is being performed) 7105 RAT BASE STATION PROBLEM (when reset has not been triggered for any reason)

7101 RESET NOTIFICATION (when reset is being performed) 7105 RAT BASE STATION PROBLEM (when reset has not been triggered for any reason) 7104 CELL SERVICE PROBLEM (for source LCR) 7105 RAT BASE STATION PROBLEM (for source FCT)

7101 RESET NOTIFICATION (when reset is being performed) 7105 RAT BASE STATION PROBLEM (when reset has not been triggered for any reason)

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7105 7105 RAT RAT BASE BASE STATION STATION PROBLEM PROBLEM (DSP (DSP supporting supporting RAT resources) RAT resources) 7106 7106 SINGLE SINGLE RAN RAN BASE BASE STATION STATION PROBLEM PROBLEM (DSP (DSP not supporting RAT resources) not supporting RAT resources) 7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 CELL SERVICE PROBLEM (LTE/GSM, in case of WDCMA if all cells are affected) 7105 RAT BASE STATION PROBLEM (WCDMA if one or more cell is affected, and in every other case)

7101 RESET NOTIFICATION (raised only if RESET RECOVERY is triggered) 7104 CELL SERVICE PROBLEM (for fault source Radio Module or DSP/FSP assigned to LTE or GSM), ALD (failure has impact on cell)) 7105 RAT BASE STATION PROBLEM (for fault source DSP/FSP assigned to WCDMA, RAT) 7106 SINGLE RAN BASE STATION PROBLEM (otherwise) 7100 HARDWARE PROBLEM (ALD (failure has no impact on cell))

7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on cell) 7104 CELL SERVICE PROBLEM (failure has impact on cell)

7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell)

7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell)

7100 HARDWARE PROBLEM (in case of FSP or FBB if cells are not impacted) 7101 RESET NOTIFICATION (in case of autonomous reset will be performed) 7104 SERVICE PROBLEM (in case or on 7100 CELL HARDWARE PROBLEM (failure has of noFSP impact FBB if cells are impacted) the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell)

7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell) 7101 RESET NOTIFICATION (when reset is being performed) 7105 RAT BASE STATION PROBLEM (when reset has not been triggered for any reason)

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (cells affected) 7101 CELL RESET NOTIFICATION (when reset is being 7106 SINGLE RAN BASE STATION PROBLEM (cells performed) not affected) When reset has not been triggered for any reason: 7104 7104 CELL CELL SERVICE SERVICE PROBLEM PROBLEM (cell(s) (cell(s) affected) affected) 7106 SINGLE RAN BASE STATION 7106 SINGLE RAN BASE STATION PROBLEM PROBLEM (cell(s) (cell(s) not not affected) affected) 7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (cell(s) 7101 CELL RESET NOTIFICATION (when resetaffected) is being 7108 BASE STATION SYNCHRONIZATION PROBLEM performed) (cell(s) not affected) When reset has not been triggered for any reason: 7104 CELL SERVICE PROBLEM (cell(s) affected) 7108 BASE STATION SYNCHRONIZATION PROBLEM (cell(s) not affected)

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (cellsnot affected) 7100 CELL HARDWARE PROBLEM (cell(s) affected) 7106 SINGLE RAN BASE STATION PROBLEM (cells 7104 CELL SERVICE PROBLEM (cell(s) affected) not affected) 7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 7104 CELL CELL SERVICE SERVICE PROBLEM PROBLEM (cell(s) (cell(s) affected) affected) 7106 SINGLE RAN BASE STATION 7106 SINGLE RAN BASE STATION PROBLEM PROBLEM (cell(s) (cell(s) not not affected) affected) 7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (cells affected) 7101 CELL RESET NOTIFICATION (when reset is being 7106 SINGLE RAN BASE STATION PROBLEM (cells performed) not affected) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (cell(s) 7101 CELL RESET NOTIFICATION (when resetaffected) is being 7106 SINGLE RAN BASE STATION PROBLEM (cell(s) performed) not affected) When reset has not been triggered for any reason: 7104 7104 CELL CELL SERVICE SERVICE PROBLEM PROBLEM (cell(s) (cell(s) affected) affected) 7100 HARDWARE PROBLEM (cell(s) 7100 HARDWARE PROBLEM (cell(s) not not affected) affected)

7100 HARDWARE PROBLEM (cell(s) not affected) 7104 CELL SERVICE PROBLEM (cell(s) affected)

7100 HARDWARE PROBLEM (cell(s) not affected) 7104 CELL SERVICE PROBLEM (cell(s) affected)

7100 HARDWARE PROBLEM (in case cells are not impacted) 7104 CELL SERVICE PROBLEM (in case cells are impacted) 7104 CELL SERVICE PROBLEM (cells affected) 7106 SINGLE RAN BASE STATION PROBLEM (cells not affected)

7100 HARDWARE PROBLEM (cells not affected) 7104 CELL SERVICE PROBLEM (cells affected)

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 7104 CELL CELL SERVICE SERVICE PROBLEM PROBLEM (cells (cells affected) affected) 7108 BASE STATION SYNCHRONIZATION PROBLEM 7106 SINGLE RAN BASE STATION PROBLEM (cells (cells not affected) not affected) 7100 HARDWARE PROBLEM (cell not affected) 7104 CELL SERVICE PROBLEM (cell affected)

7100 HARDWARE PROBLEM This alarm is used when there is a problem with HW that cannot be directly mapped to cell operation 7100 HARDWARE PROBLEM This alarm is used when there is a problem with HW that cannot be directly mapped to cell operation 7100 HARDWARE PROBLEM This alarm is used when there is a problem with HW that cannot be directly mapped to cell operation 7104 CELL SERVICE PROBLEM This alarm is used when fault indicates impact to cell operation. 7606 7104 TRX CELLFAULTY SERVICE PROBLEM This alarm This alarm is is used used when when fault fault indicates indicates failure impact of to TRX. cell operation. 7607 TRX OPERATION DEGRADED [AAS only if less than half ofFAULTY ActiveElements are faulty. Otherwise 7606 7606 TRX longer than 7106 SINGLE RAN (when BASE condition STATIONoccurs PROBLEM (cell TRX FAULTY] tT+danger.) not affected) This alarm is used fault degradation in This alarm used when when fault indicates indicates failure of TRX. 7104 CELLisSERVICE PROBLEM (cell affected) TRX operation. 7607 TRX OPERATION DEGRADED (when condition initially occurs) This alarm is used when fault indicates degradation in TRX operation.

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 CELL SERVICE PROBLEM (cell(s) affected) 7106 SINGLE RAN BASE STATION PROBLEM (cell(s) not affected) 7104 CELL SERVICE PROBLEM (cell(s) affected) 7106 SINGLE RAN BASE STATION PROBLEM (cell(s) not affected) 7100 HARDWARE PROBLEM (problem occurred when configuring Radio Module's External Alarm and Control line(s)) 7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (if fault 7101 CELL RESET NOTIFICATION (when resetisisreported being to optical link connected to Radio Module) performed) 7100 HARDWARE PROBLEM (if fault is reported to optical link not to Radio Module) When reset hasconnected not been triggered for any reason: 7104 SERVICE PROBLEM (if fault 7101 CELL RESET NOTIFICATION (when resetisisreported being to optical link connected to Radio Module) performed) 7100 HARDWARE PROBLEM (if fault is reported to optical link not to Radio Module) When reset hasconnected not been triggered for any reason: 7104 SERVICE PROBLEM (if fault 7101 CELL RESET NOTIFICATION (when resetisisreported being to optical link connected to performed) FRM) 7100 (if fault reported WhenHARDWARE reset has notPROBLEM been triggered for is any reason:to optical link not 7104 CELL SERVICE PROBLEM (if fault 7101 RESET NOTIFICATION (when resetisisreported being to connected to FRM) optical link connected to performed) Radio Module) 7100 (if fault reported WhenHARDWARE reset has notPROBLEM been triggered for is any reason:to optical link not 7104 CELL PROBLEM reported to 7104 CELLtoSERVICE SERVICE PROBLEM (if (forfault faultissource OptIf connected Radio Module) optical link connected to towards Radio Module) Radio Module) 7105 RAT BASE STATION PROBLEM (for fault source 7108 BASE STATION FSP/FBB serving RAT)SYNCHRONIZATION PROBLEM (if fault is reported optical link not PROBLEM (for 7106 RANtoBASE STATION 7104 SINGLE CELLtoSERVICE PROBLEM (for fault source OptIf connected Radio Module) fault source FSP/FBB towards Radio Module)not serving RAT or OptIf not towards Radio Module) 7105 RAT BASE STATION PROBLEM (for fault source FSP/FBB serving RAT) 7106 RAN BASE STATION (for 7104 SINGLE CELL SERVICE PROBLEM (forPROBLEM fault source OptIf fault source FSP/FBB not serving RAT or OptIf not towards Radio Module) towards Radio Module) 7105 RAT BASE STATION PROBLEM (for fault source FSP/FBB serving RAT) 7106 SINGLE RAN BASE STATION PROBLEM (for fault source FSP/FBB not serving RAT or OptIf not towards Radio Module)

7104 CELL SERVICE PROBLEM (for fault source OptIf towards Radio Module) 7105 RAT BASE STATION PROBLEM (for fault source FSP/FBB serving RAT) 7106 RAN BASE STATION (for 7104 SINGLE CELL SERVICE PROBLEM (forPROBLEM fault source OptIf fault source FSP/FBB not serving RAT or OptIf not towards Radio Module) towards Radio Module) 7105 RAT BASE STATION PROBLEM (for fault source FSP/FBB serving RAT) 7106 SINGLE RAN BASE STATION PROBLEM (for fault source FSP/FBB not serving RAT or OptIf not towards Radio Module)

7101 RESET NOTIFICATION (when reset is being performed) 7108 BASE STATION SYNCHRONIZATION PROBLEM (when reset has not been triggered for any reason) 7101 RESET NOTIFICATION (when reset is being performed) 7106 SINGLE RAN BASE STATION PROBLEM (when reset has not been triggered for any reason) 7105 RAT BASE STATION PROBLEM (fault source FSP serving RAT) 7106 SINGLE RAN BASE STATION PROBLEM (otherwise) 7101 RESET NOTIFICATION (when reset is being performed) 7108 BASE STATION SYNCHRONIZATION PROBLEM (when reset has not been triggered for any reason) 7104 CELL SERVICE PROBLEM (cells are affected) 7106 SINGLE RAN BASE STATION PROBLEM (cells are not affected)

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 7104 CELL CELL SERVICE SERVICE PROBLEM PROBLEM (for (for LTE) LTE) 7105 RAT BASE STATION PROBLEM 7105 RAT BASE STATION PROBLEM (otherwise) (otherwise)

7101 RESET NOTIFICATION (when reset is being performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (forreset LTE)is being 7101 CELL RESET NOTIFICATION (when 7105 RAT BASE STATION PROBLEM (otherwise) performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (forreset LTE)is being 7101 CELL RESET NOTIFICATION (when 7105 RAT BASE STATION PROBLEM (otherwise) performed) When reset has not been triggered for any reason: 7104 CELL SERVICE PROBLEM (for LTE) 7105 RAT BASE STATION PROBLEM (otherwise)

7101 RESET NOTIFICATION (When reset is being performed after fault detection) 7104 CELL SERVICE PROBLEM (Site reset no longer possible(executed already 3 times)) 7105 RAT BASE STATION PROBLEM (Site reset no longer possible(executed already 3 times)) 7106 SINGLE RAN BASE STATION PROBLEM (Site reset no longer possible(executed already 3 times))

None

7108 BASE STATION SYNCHRONIZATION PROBLEM (always) 7101 RESET NOTIFICATION (in case recovery reset will be triggered) 7100 HARDWARE PROBLEM (Fault with this alarm is toggling in the BTS) 7101 RESET NOTIFICATION ((Fault with this alarm is toggling in the BTS) 7102 RESOURCE BLOCKED BY USER (Fault with this alarm is toggling in the BTS) 7103 EXTERNAL ALARM NOTIFICATION (Fault with this alarm is toggling in the BTS) 7104 CELL SERVICE PROBLEM (Fault with this alarm 7100 HARDWARE PROBLEM (failure has no impact on is toggling in the BTS) cell) 7105 RAT BASE STATION PROBLEM (Fault with this alarm is toggling in the BTS) 7106 SINGLE RAN BASE STATION PROBLEM (Fault with this alarm is toggling in the(failure BTS) has no impact on 7100 HARDWARE PROBLEM 7107 cell) BASE STATION CONNECTIVITY PROBLEM (Fault with this alarm is toggling in the BTS) 7108 BASE STATION SYNCHRONIZATION PROBLEM (Fault with this alarm is toggling in the BTS) 7100 PROBLEM (in case of FSP(Fault or FBB if 7109 HARDWARE BASE STATION SECURITY PROBLEM cells are not impacted, FR(there is enough critical cell with this alarm is toggling in the BTS) resources for the cell to remain operational), ESM, 7110 BASEleft STATION LICENCE LIMITATION (Fault with FT, has no on cell)) this ALD(failure alarm is toggling in impact the BTS) 7101 RESET NOTIFICATION (FBB (in case of fault 4052 raised during FBB hot removal scenario) 7104 CELL SERVICE PROBLEM (in case of FSP or FBB if cells are impacted, FR(there is not enough critical cell resources left for the cell to remain 7100 HARDWARE PROBLEM (failure no impact on operational), ALD(failure has impact onhas cell)) the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell)

7104 CELL SERVICE PROBLEM (the faulty FSP is mapped to the cell) 7106 SINGLE RAN BASE STATION PROBLEM (the faulty FSP is not mapped to any cell)

7100 HARDWARE PROBLEM (failure has no impact on the cell) 7104 CELL SERVICE PROBLEM (failure has impact on the cell)

7100 HARDWARE PROBLEM (in case cells are not impacted), 7104 CELL SERVICE PROBLEM (in case of cells are impacted)

Base station synchronization problem.



7101 RESET NOTIFICATION (in case of RAT reset is ongoing) 7105 RAT BASE STATION PROBLEM (in case of RAT reset cannot be performed)

7104 CELL SERVICE PROBLEM (failure has impact on cell) 7101 RESET NOTIFICATION (raised only if RESET RECOVERY is triggered)

N/A

7101 RESET NOTIFICATION (raised only if RESET RECOVERY is triggered) 7104 CELL SERVICE PROBLEM (when reset has not been triggered for any reason) 7105 RAT BASE STATION PROBLEM (otherwise) 7101 RESET NOTIFICATION (raised only if RESET RECOVERY is triggered)

7101 RESET NOTIFICATION (when reset is being performed) 7104 CELL SERVICE PROBLEM (when cells are affected) 7106 RAN BASE STATION (when 7101 SINGLE RESET NOTIFICATION (when PROBLEM reset is being reset has not been triggered for any reason) performed) When reset has not been triggered for any reason: 7104 SERVICE PROBLEM (LTE, in case of 7101 CELL RESET NOTIFICATION (when reset is being WDCMA if all cells are affected) performed) 7105 RAT BASE STATION PROBLEM (WCDMA if one or more cell has is affected, and in everyfor other When reset not been triggered any case) reason: 7104 SERVICE PROBLEM (LTE/GSM, in case of 7101 CELL RESET NOTIFICATION (when reset is being WDCMA if all cells are affected) performed) 7105 RAT BASE STATION PROBLEM (WCDMA if one or more cell has is affected, and in When reset not been triggered for any reason: every other case) 7104 CELL SERVICE PROBLEM (DSP serving LTE cell) 7105 RAT BASE STATION PROBLEM (otherwise)

None

Instructions

Check the active fan alarms and the airflow in the BTS.

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 via BTS Site Manager. You can use the history data as a tool for finding out perform the reason the fault/alarm To clear this fault, the for following steps: situation (for further instructions about the history see Ifthe 1. Make sure that the module is properly feature, connected. the online help of BTS Site Manager). Depending on theCheck module LED does not light up, the module is faulty. possible reason, follow the instructions below: the alarming module. 1. Perform RAT reset. 2. the faultSBTS. history. 2. Check Block/Unblock 3. notinhelp, replace the alarming 1. If Instep case2ofdoes a fault the transmission networkmodule. synchronization, you must correct the network synchronization. long-term accuracy of the 1. Block/unblock The the module that is causing the signal alarm.used for synch must be 0.015 ppm or better (check the 2. Replace the module that is causing the alarm. correct accuracy by measuring it). No actions on the BTS are necessary. 1. Reset the WCDMA SW. 2. the transmission linkssignal to theused RNC/Flexi Direct 2. Check If the basic accuracy of the for synch is RNC. correct, but there is too much instability, that is, the jitter/wander is outsideSW. the acceptable limits, you must 1. Reset the WCDMA 3. Check BTS and RNC/Flexi RNC transmission correct thethe synchronization of the Direct transmission network. settings. The limitsthe for transmission the jitter/wander in the ITU-T 2. Check linksare to defined the RNC. G.823/824/825. No actions on the BTS are needed. 4. Reset the SBTS. 3. Checkthe thecompatible BTS and RNC settings. Update SW intransmission the BTS (check the SW versions to the seeSystem the active SW version and update the 5. Replace Module. 4. Reset the SBTS. unless active SW version), it is fault, automatically updated 3. In case of a BTS equipment the location mightby be: NetAct. 5. Replace the System Module. Update compatible SW in the BTS. NOTE: If the fault 10:EFaultId_NoConnectionToUnitAl is also active on fault the source unit, then the SW update mustis Transport NOTE: If also part: 10:EFaultId_NoConnectionToUnitAl be postponed until the fault active on the source unit, then the SW update should be 10:EFaultId_NoConnectionToUnitAl is canceled. postponed until fault 10:EFaultId_NoConnectionToUnitAl is 1. Check the NTP setting. canceled. -2.Check ofparameter the TRS signal used Checkthe thealarms stratum on the NTPfor server. synchronization with BTS Site Manager and act accordingly. 3. Check that a GNSS is configured and connected.

FCM unit:

- If the TDM reference signal accuracy and the TRS are in order but the FCM unit is still alarming, run the fast tuning

Take the following actions to clear the fault: 1. Check the file type according to the file type number below: - Take the following steps to clear the fault: 1 - hwConfigurationFile 2 - configurationPlanFile 1. Retry the SW update. 3 - logFile 4 - swFile 2. Save a snapshot andtocheck thethe download Take following steps resolve fault: status from 5 to - licFile the BTS SWDLreport in the snapshot file. 6 - measurementFile 1. Retry the SW update. 7 - rnwConfigurationPlanFile 2. If11 other flash memory-related faults in the alarming - combinedSiteConfigurationPlanFile module are simultaneously active,the replace 12 allConfigurationPlanFile Take to following steps to resolve fault: the alarming module. 14 - testResultFile 15 - autoConfReport 1. Retry the SW update. - measurementPlanFile 2. If17 other flash memory-related faults in the alarming 18 - rnwMetadataFile module are simultaneously active, replace the alarming Check mains power supply. 19 -the topologyFile module. 22 - togglingParFile 23 - troubleShootingData [...] 41 -the AntennaParameters Check external Powerline conditions and make sure that there is an external power provided to the SBTS. 2. Retry the file update a few times. 3. Check the file server account user settings. Check the external Powerline conditions and make sure that therethe is an power provided to the SBTS. 4. Check fileexternal and path names. 5. Check the administration log on the file server. To cancel the alarm, unblock the unit or module.

To cancel the alarm, unblock the cell.

To cancel the alarm, unblock the SBTS. Unblocking of the SBTS causes a site reset.

1. Block/unblock the alarming unit/module. 2. Remove/re-insert the alarming unit/module. 3. the alarming unit/module. 1. Replace Check the cell parameters in the RNC/Flexi Direct RNC and the BTS. 2. If the parameters configured to the RNC/Flexi Direct RNC are correct, lock and unlock all cells of this BTS. Use the element manager to trigger parameter sending from the RNC to the BTS again. 3. If the parameters configured to the RNC/Flexi Direct RNC are incorrect, lock the cells and configure the parameters to the correct values. Afterwards, unlock the cells. 4. If the default values for the cell parameters (such as rampdown time/step) are not appropriate in the BTS, reconfigure the BTS with the commissioning wizard.

Follow the steps below to resolve the fault: 1. In case of FR, try to connect FR to a different port. 2. case offault, othertake sources or if FR was already checked ToIn clear the the following steps: and connected to all available ports and the fault is still active, change SBTS planned HW configuration (profile) to 1. Upgrade SBTS software. take the module into use. 2. Replace the alarming module. 1. Reset the alarming Radio Module using the blocking/unblocking function. If there was an internal failure or SW interruptions, the module must be blocked or unblocked in order for it to be restarted and reconfigured. 2. Check cables between the system module and the Follow thethe steps below to resolve the fault: RF module. 3. this does not help, replace the faulty Radio Module. 1. If Reset the BTS. 2. If step 1 does not help, check your commissioning. 3. If step does not help, replace the the fault: affected HW. Follow the2 steps below to resolve 1. Reset the BTS. 2. If step 1 does not help, check your commissioning. 3. If step does not help, replace the the fault: affected HW. Follow the2 steps below to resolve 1. Reset the BTS. 2. If step 1 does not help, check your commissioning. 3. If step does not link help,settings replaceand thethe affected HW. Check the2 signaling RNC connections.

1. Check the other active alarms. 2. Check the number of FSP units.

1. Check the other active alarms. 2. Check the number of FSP units.

1. Lock/Unlock the cells. 2. Add more baseband capacity to the BTS or - if the reason is a broken baseband unit - replace the baseband unit. Follow the instructions below to resolve the fault: 1. Make sure that alarming RF module is properly connected. 2. Make sure that all system modules docarrier not have Recommissioning is needed. For a dual RFreported Module, connection (fault 10) or synchronization (fault 3020) issues. the lower LCR must be assigned to the lower frequency If there are any, solve them first. carrier. 3. Block/Unblock the RF module. If there was an internal failure or unit SW freezes, the module must be blocked/unblocked to get it started and configured again. 4. Replace the alarming RF module.

1. Check the configuration to make sure that there are enough resources for the minimum HSUPA capacity. 2. If there are not enough resources, replace the broken module recommission BTS and pre-reserve less Take theorfollowing actionsthe to clear the fault: capacity for HSUPA. 1. Check Element Manager for the received signal levels to 3. Reset the BTS the minimum capacity prefind out which RX to is get causing the problem. selection for the HSUPA in use. Take the following actions to clear the fault: 2. If an MHA alarm is active, replace the MHA unit and check if the RX signal level failure is inactive. 1. Check Element Manager for thealarm received signal levels to find out which RX is causing the problem. 3. If there are antenna line devices, check them. Replace the alarming module/unit. 2. If an MHA alarm is active, replace the MHA unit and 4. Check theRX antenna The alarm faulty radio module, check if the signal cables. level failure is inactive. antenna feeder, or antenna can be identified by locating the of the inadequate RX level on the antenna line. 3. Ifsource there are antenna line devices, check them. Check the faulty or change the To clearand thisreplace fault, perform theequipment following steps: maximum RXfault signal level difference 1) When the is detected, a new PICradio configuration 4. Check the antenna cables. The faulty module, is to (maxRxLevelDifference) threshold during rebe provided by the Element can Manager. antenna feeder, or antenna be (given identified by locating commissioning with default value 7dB). 2) this problem thenRX remove and the FSP theIfsource of the persists inadequate level on theinsert antenna line. again. Check and replace the faulty equipment or change the To clear this Note: The RXalarm: value in Element Manager is refreshed every maximum RX signal level 1) The alarm indicates thatdifference the PIC configuration has minute. (maxRxLevelDifference) threshold (given during refailed. New BTS re-commissioning is needed. commissioning with 7dB). Commissioning donedefault by thevalue Element Manager / NetAct is to include PIC pool It module, is recommended to reIf the faulty FSP is inconfiguration. extension block/unblock Note: The RX value inthe Element Manager is refreshed every commission the BTS during low traffic time. the extension module. Otherwise, block/unblock the BTS. minute. 2) If this problem persists then the operator must restart 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 RNC, so there are no two cells in LCG The lack of CCCH licensed capacity onwith the the BTSsame (caused UARFCN while one is in PIC pool and the other is not. by an insufficient number of commissioned CCCH The operator should also caused modify the pool with the Processing Set licenses) the PIC cell setup configuration, so that the number of PIC cells is correct requested cell settings to fail. (number of RX of non-PIC cells + 2x number of RX of PIC The following 1. Reset RAT.actions can be performed to setup the cell: cells <= 48). 1. thefaulty CCCH licensed capacity consumption. 2. Decrease Replace the unit. And/Or 2. Increase the CCCH Processing Set licensed capacity in BTS commissioning ("CCCH processing set" amount) No manual action is required from the operator. The fault just notifies the BTS operator that the CCCH Common TransportSet Check that the has enough Processing Channel is deleted. licenses loaded or has received a sufficient number from NetAct in order to change the CCCH licensed capacity according the new CCCHon Processing Set The lack oftoCCCH capacity the BTS caused the cell commissioning settings. setup with the requested cell settings to fail. The following actions can be taken to decrease CCCH capacity consumption for the inactive cell or for all/any cells that are already setup: Decrease the cell RNC/BTS settings that affect CCCH capacity consumption, for example, Cell Range, number of signatures, and number of RXes.

Take the following actions to clear the fault: 1. Check the other active faults. If the /rom-disk is corrupted, change the alarming unit or module. 2. Block/Unblock that the there are no recovery Take the followingSBTS. actionsNote to clear fault: actions and blocking/unblocking can be performed once. If that does the not other help, active replacefaults. the alarming unit or module. 1. Check If the /rom-disk is corrupted, change the alarming unit or module. 2. Block/Unblock that the there are no recovery Take the followingSBTS. actionsNote to clear fault: actions and blocking/unblocking can be performed once. If that does the not other help, active replacefaults. the alarming unit or module. 1. Check If the /rom-disk is corrupted, change the alarming unit or module. 2. Block/Unblock that the there are no recovery Take the followingSBTS. actionsNote to clear fault: actions and blocking/unblocking can be performed once. If that does the not other help, active replacefaults. the alarming unit or module. 1. Check If the /rom-disk is corrupted, change the alarming unit or module. 2. Block/Unblock that the there are no recovery Take the followingSBTS. actionsNote to clear fault: actions and blocking/unblocking can be performed once. If that does the not other help, active replacefaults. the alarming unit or module. 1. Check If the /rom-disk is corrupted, change the alarming unit or module. 2. Block/Unblock SBTS. Note that there no recovery Perform the following steps until the faultare is resolved: actions and blocking/unblocking can be performed once. If that doesthe notSBTS. help, replace the alarming unit or module. 1. Reset 2. Replace the System Module or faulty FSP Take the following actions to clear the fault: card. 1. Block/unblock the SBTS. 2. If that does not help, replace the faulty module (System Module). Perform the steps below in the listed order until the fault disappears: 1. Reset the SBTS. [User defined] 2. If that does not help, replace the alarming FSM.

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

[User defined]

Take the follow actions to clear the fault: 1. Make sure that the unit/module is properly connected. If the unit/module LED does not light up, the unit/module is faulty. the alarming unit/module. There Check are different variations of the HW that might have 2. Check the fault history. limitations in the supported frequency range and bandwidth. Check the cell parameters against the BTS HW configuration and change it if needed. It might be due to any of the following causes: The cell frequency is out of the min/max limit of the HW, the number of carriers for the HW type has exceeded, or the carrier spacing limit has exceeded. BTS reset is needed to put the frequency channel into use and to clear the fault. Check RNW configuration (BSC for GSM, RNC for WCDMA) and check whether RNW configurations are aligned with SCF configurations.

Replace the alarming module.

Replace the alarming module or check the optical cable.

Replace the alarming module.

This fault is most likely the result of a BTS hardware problem or a reference source that is being followed by the BTS that is in a faulted condition, therefore producing an inaccurate reference. Perform the following steps to isolate the cause of the fault: 1. Block/unblock the System Module. 1. the other alarms of the BTS and act accordingly. 2. Check Replace the System Module. 2. If there are no other synchronization-related alarms Perform the the following steps:with BTS Site Manager. active, start fast tuning 1. thesite. MHA by fast taking one again. of the following steps: 3. Restart Reset the Run tuning -Toggling DC voltage the antenna line and 4. Check the signal accuracy byoff measuring it 1. Restart thereference MHA byon blocking and unblocking theon. Radio -Blocking and unblocking Radio Module. with a frequency counter (note: requires a good timebase Module. -Restarting BTS.The reference signal can be found from for the counter). the Sync Out interface of theall Flexi the Note: This operation affects the System antennaModule, lines and cells Note: The above operations might affect other antenna line required accuracy is +/-0.015ppm. If the reference related to the Radio Module, not just the faulty one. If the To recover from thisto fault, perform the following steps: devices connected the FR Module (and related cells), accuracy is correct, run fast tuning. If the reference alarm reappears, replace the alarming module. not just the one. the cause of the fault is with the accuracy is faulty not correct 1. Cancel the faultthe by FR Module resetTroubleshoot or BTS reset the reference source is tuning 2. Restart the MHA byBTS disabling andto. enabling DC power on or 2. Check the antenna cables and connectors towards the external synchronization network to find the root cause. the antenna lines 2. Disable and enable DC power of affected antenna line MHA. Fix or replace broken parts. Other BTSs with the the same alarm can provide furtherand 1. Check the antenna cables, connectors, antenna, connected toon MHA. (depending information about line the devices. location of the root cause. possible antenna the FR hardware type, the fault mightand be solvable by 3. Replace the alarming module. 5. If the reference accuracy isthrough: correct running fast Note: Alarm can be canceled a Radio Module switching the DC power off and on). tuning does help, replace the module. 2. Check thenot antenna line (TX-cable-antenna) impedance reset (including Radio Module hotsystem removal), arunning BTS reset, 3. Check the antenna cables and connectors to the matching. or a DC voltage turn-off by a user of the antenna line. 1. Check antenna, antenna cables, connectors and MHA. Fix the or replace thethe broken parts. other possible antenna line devices. 3. Check the antenna cables and connectors running to the MHA. Fix the or replace broken parts. 2. Check antennathe line (TX-cable-antenna) impedance matching. Replace the alarming radio module.

Reset Radio Module.

Reset Radio Module.

1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit. 1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit. 1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit. 1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit. 1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit. 1. Block or unblock the Radio Module to give a power-off reset to the antenna line devices. 2. If that does not help, replace the antenna line device. 1. Update the proper SW for the device or perform ALD power reset (for example Radio Module block/unblock) 2. If that does not help, replace the antenna line device. Update the SW in the BTS.

To clear this fault: 1. Make sure that the module is properly connected. Check the alarming module. 1. Reset the BTS. 2. Replace the module that is causing the alarm. 2. Replace the alarming module. 1. Check the MHA type and configuration settings of the BTS. If the given MHA requires DC voltage on the BTS2 (Diversity) port, perform ALD commissioning properly. 2. Reset the BTS. 3. Replace the alarming module.

1. Check the functionality of the antenna line device. 2. Check the compatibility between the antenna line device and the BTS. 1. Check the functionality of the antenna line device. 3. Make sure that given parameters are within the valid range. 2. Check the compatibility between the antenna line device and the BTS. 1. Check the functionality of the antenna line device. 3. Make sure that given parameters are within the valid range. 2. Check the compatibility between the antenna line device and the BTS. 1. Check the functionality of the antenna line device. 3. Make sure that given parameters are within the valid range. 2. Check the compatibility between the antenna line device and the BTS. None 3. Make sure that given parameters are within the valid range. 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. Check the connection between the GPS receiver and FSM. Note! Perform the steps below in the listed order until the alarm disappears. 1. Check the cabling (connected to Sync In interface). Take the following actions to clear the fault: 2. Check if the 2.048 MHz reference source is working normally and theexisting 2.048 MHz signal is available. 1. Confirm if the configuration is within the configured RF HW capabilities. 3. Replace the alarming module. 2. Check the BTS connections andthe commissioning Take the following actions to clear fault: settings. 3. 1. Block/Unblock Block/Unblock the the BTS. RF HW unit. 4. If the HW configuration is confirmed, then this problem 2. If the problem is still observed after performing the first is caused by the eNB SW. Check the other active alarms. step, replace the RF HW unit. Take the following actions to clear the fault: 1. Block/unblock RF HW unit. 2. If problem still exists after performing step 1, replace the RF HW unit.are divided into three sections. Take the Instructions following actions to clear the fault: Section A: Check the system module side: 1. Check connector is properlyTake mounted and firmly There areifthree sets ofseal instructions. the following in place. actions to clear the fault:. 2. Check if the SFP (Small Form Factor Pluggable) is properly connected/mounted in the System Module. If the Set A: Check the system module side. SFP connection/mounting is incorrect, re-adjust theand 1. Check if the connector seal is properly mounted connection/mounting. firmly in place. 3. thepluggable faulty SFP(SFP) (connected to 2. Check Check ifif the the LED smallindicates form-factor is System Module). Replace the SFP if it is faulty. properly connected or mounted to the system module. If 4. if the optical is properly connected/mounted theCheck SFP connection orcable mounting is incorrect, re-adjust the in the SFP. connection or mounting. 5. optical that are SFP connected to theto 3. Clean Check the if the LED connectors indicates the faulty (connected SFP. Reset RF HW unit by doing the block/unblock system module). Replace the SFP if it is faulty. procedures, and checkcable if thisissolves theconnected problem. or 4. Check if the optical properly mounted to the SFP. Section B: Check the radio module side:

Take the following actions to clear the fault: 1. Confirm if the existing configuration is within the configured RF HW capabilities. 2. Check BTS and Take commissioning There arethe three setconnections of instructions. the following settings. actions to clear the fault: 3. Block/Unblock the BTS. 4. theCheck HW configuration is verified, SetIf A: the system module side.then this problem is caused by the eNB SW. Check the other active alarms. 1. Check if the connector is properly mounted and Take the following actionsseal to clear the fault: firmly in place. 2. if the small 1. Check Block/Unblock the form-factor RF HW unit.pluggable (SFP) is properly connected or the performing system module. If 2. If the problem is stillmounted observedtoafter the first the SFP connection or mounting is incorrect, re-adjust the step, replace the RF HW unit. Take the following actions to clear the fault: connection or mounting. 3. Check if the LED indicates the faulty SFP (connected to 1. Block/Unblock the RF HW system module). Replace the unit. SFP if it is faulty. 2. the problem is stillcable observed after performing 4. If Check if the optical is properly connectedthe or first step, replace the RF HW unit. mounted to the SFP. Take the following actions to clear the fault: 5. Clean the optical connectors that are connected to the SFP. Reset the RF HW blocking/unblocking and 1. Block/Unblock the RFunit HWbyunit. check if this solves the problem. 2. If the problem is still observed after performing the first step, replace the RF HW unit. Take following actions to clear the fault: Set B:the Check the radio module side. 1. Check if the connector seal is properly mounted and 1. Block/Unblock firmly in place. the RF HW unit. 2. the problem is still observed after performing the first 2. If Check if the SFP is properly connected or mounted to step, replace the RF HW unit. the Radio module. actions If the SFP connection or mounting is not Take the following to clear the fault: correct, re-adjust the connection or mounting. 3. Block/Unblock Check if the optical cable properly connected or 1. the RF HWisunit. mounted to the SFP. 2. If the problem is still observed after performing the first 4. Clean the optical connectors at the Radio module end. step, replace the RF HW unit. Take actions to clear the fault: and check if Resetthe thefollowing RF HW unit by blocking/unblocking this solves the problem. 1. Block/Unblock the RF HW unit. 2. theCheck problem still observed after performing the first SetIf C: theisoptical connection. step, replace the RF HW unit. 1. Block/Unblock Check if the optical the RF cables HW unit. are not over bent. If the 2. If theofproblem radius the cable remains bending after exceeds performing the guidelines the first step, then the optical replace thecable RF HW needs unit.to be replaced as overbending can damage the cables and can detach or damage the connectors. In startup: Wait until the alarm is canceled. This might take 2. test the fiber cable (for example, measure the upOptionally, to 30 minutes. optical attenuation) from the system module end and/or the RF module the measuring equipment If the alarm end. is notCheck canceled: documentation for instruction details. Check if environment temperature is within Take the following actions to clear the fault: design limits for radio module. When environment temperature is out of If the alarm is stillisobserved after executing stepsare from limits then alarm no further the actions 1. Block/unblock RFexpected HW unit.and the instruction sets A, B, and C, replace the Radio module. needed. 2. If the problem still exists after performing step 1, replace the HW unit. actions to clear the fault: TakeRF the following 1. Block/Unblock the RF HW unit. 2. If the problem is still observed after performing the first step, replace the RF HW unit.

Take the following actions to clear the fault: 1. Block/unblock the RF HW unit. 2. If the problem still exists after performing step 1, replace the RF HW unit. There are three sets of instructions. Execute the appropriate set of instructions based on your best knowledge to minimize cost, time, and effort. Set A: Check systemtemperature/environmental module side. 1. Check if thethe ambient 1. Check if the connector seal is limits properly mounted and conditions are within the design for the radio module. firmly in place. When the ambient temperature/environmental conditions 2. the small form-factor pluggable is areCheck out ofiflimits, the alarm is expected and (SFP) no further properly connected or mounted to the system module. If actions are needed. 1. RF or HW unit theBlock/unblock SFP connection mounting is incorrect, re-adjust the 2. If the problem persists, replace the RF HW unit connection or mounting. 2. Check if air flow is not blocked by some objects. Make 3. Check if the LED indicates the faulty SFP (connected sure minimum thermal clearances are followed. Removeto system module). Replace the SFP if it is faulty. any objects that might be blocking airflow and mount 4. Check if steps the optical cable is properly connected or Follow the below to clear the fault: module according to instructions and recommendations. mounted to the SFP. 5. optical that are connected to the 1. Clean the fan orconnectors airflow of foreign objects. 3. Check the if excessive sunlightisisfree causing overheating. SFP. Reset the RF HW unit by blocking/unblocking Remove any objects blocking the faninstructions or the airflow. Install sunshield following mounting andand check if this solves the problem. 2. Check the fan connector is the properly recommendations. Follow theif steps below to clear fault: mounted. Mount fan connector according to the guidelines. SetIf B: the radio modulethen side.reset the radio module 3. theCheck alarm is still 1. Check ifif the orobserved the airflow free of mounted foreign objects. 1. Check the fan connector seal is is properly and by block/unblock. Remove any objects blocking the fan or the airflow. firmly in place. 4. If the alarm is stillconnector observedisthen replace the fanMount 2. Check the properly 2. Check the fan SFP is properly or mounted in Follow theifif steps below to clear connected the fault: mounted. module. fan connector according to theconnection guidelines.or mounting is the Radio Module. If the SFP 3. If the alarm stillor observed then reset radioobjects. module incorrect, the connection mounting. 1. Check ifre-adjust theisfan the airflow is or free of the foreign by block/unblock. 3. Check if the optical cable is properly connected or Remove any objects blocking the fan or the airflow. 4. If the alarm stillconnector observedisthen replace the fanMount mounted in theisfan SFP. 2. Check if steps the properly mounted. Follow the below to clear the fault: module. 4. Clean the optical connectors at the Radio fan connector according to the guidelines. Module end. Reset RF HW unit by blocking/unblocking and check 3. If thethe alarm still then reset radio moduleif 1. theis fan orobserved the airflow is free of the foreign objects. thisCheck solvesif the problem. by block/unblock. Remove any objects that are blocking the airflow. 4. If the alarm isfan stillconnector observedisthen replace the fan 2. Check if thethe Set Take C:the Check following optical steps to connection. clearproperly the fault:mounted. Mount module. the fan connector according thenot guidelines. 1. Check if the optical cablestoare overbent. If the radius 3. If the alarm is still observed then reset the radio module of Check 1. the cable if the bending ambient exceeds temperature/environmental the guidelines, then the by block/unblock. optical cables conditions are need withintothe bedesign replaced limits as for over-bending the radio module. the 4. If thethe alarm is stilltemperature/environmental observedthe then replace the fan optical When fiber ambient cables damages cables and can conditions detach 1. Check if the ambient temperature and environmental or module. damage exceed the the limits, connectors. thethe alarm is expected no radio further conditions are within designed limits and for the 2. actions Optionally, are needed. test the fiber cable (for example, measure the module. When the ambient temperature and environmental optical attenuation) from the system module end and/or conditions exceed the limits, the alarm startup is expected Radio 2. Check if air flow end. isCheck free of the foreign measuring objects. equipment Make sure the and noModule further are needed. 1. Check ifthermal the actions ambient temperature andare environmental documentation minimum forclearances details. guidelines followed. conditions areobjects within the design be limits for thethe radio module. Remove any that blocking airflow 2. Check ifambient air flow is free might of foreign objects. Make sureand When the temperature and environmental If mount the alarm thethermal module is still clearance observed accordingafter to instructions executing the andsteps from minimum guidelines are followed. conditions exceed the limits, the alarm startup is expected the recommendations. instruction sets A, B, and C, replace the Radio Module. Remove any objects that might be blocking the airflow and and no further actions are needed. Instructions are divided into three sections. and mount the module according to instructions 3. Check if excessive sunlight is causing the unit to recommendations. 2. CheckA:ifInstall the airthe flow is not module blocked by the foreign objects. overheat. sunshield following mounting Section Check on system side: Make sure minimum thermal clearances are followed. instructions andconnector recommendations. 1. Check if the seal causing properlythe mounted and 3. excessive sunlight unit toand Remove any objects that mightisbe blocking airflow firmly in place. overheat. Install the sunshield following the mounting mount theifmodule according to the instructions and is 2. Check the (Small Form Factor Pluggable) instructions andSFP recommendations. recommendations. properly connected to the System Module. If the SFP connection/mounting is incorrect, readjust the connection. 3. sunlight the is causing the (connected unit to 3. Check Check ifif excessive the LED indicates faulty SFP to overheat. Install the sunshield following the mounting the System Module). Replace the SFP if faulty. instructions andoptical recommendations. 4. Check if the cable is properly connected to the SFP. 5. Clean the optical connectors that are connected to the SFP. Reset the FR HW unit by following the block/unblock

Perform the steps below in the listed order until the fault disappears: 1. Check the optical connection between the system module and Radio module. Check the SFP module(s) and/or the opticalthe connectors, verify the To clearre-adjust this fault, perform following and steps: operation of any devices in the optical network 1. VSWR measured at RF (transmitter) exceedsbetween the values FSM and Radio Module, if such devices are in use. acceptable by the RF module. 2. the Radio module. 2. Block/unblock Check impedance matching of Antenna Line System 3. If the problem persists, reset the site by (replace elements that causes mismatch). 1. Check BTS connections and commisionning settings. blocking/unblocking the BTS. 3. To check if above mentioned steps haveBTS solved 2. Block/unblock BTS (usingthe theSFP local Sitethe 4. If this does notthe help, replace module(s) in which problem, block/unblock the RF module. Manager connection if a remote connection is not and/or the malfunctioning optical connection is occurring, *possible). Forcing the RF HW to work under such conditions might replace result in the RF fiber. HW permanent damage. Take the following actions to clear the fault: 1. Confirm that applied External Alarm and Control line configuration is within the used Radio modules HW capabilities. Take the following actions to clear the fault: 2. External connected. Alarm and Control line 1. Check Check Radio that themodules SFP is properly connections and BTS commissioning settings. 2. Replace the SFPactions module. Take the the following 3. Reset Radio Module.to clear the fault: 1. CheckRadio that the SFP isExternal properlyAlarm connected. 4. After modules and Control line configuration and connections have been confirmed and 2. Replace theisSFP module. Radio module reset, if the Take the following actions to problem clear thepersists fault: then it is caused by the eNB SW. Check the other active alarms. 1. Check the status of the module behind the faulty link (For example, check if the Power is on). Take the following actions to clear the fault: 2. Check the SFP from both ends (the System Module and the module faultywith link). optical interface 1. Reset thebehind Radio the Module theThe faulty optical interface LED indicates the faulty SFP. Replace the SFP if it is faulty. by blocking/unblocking it. To clear the take thetest following actions: 3. the fault, connectors, the replace fiber cable, and replace it 2. Clean If this does not clear the fault, the Radio Module ifthat faulty. is causing thebetween alarm. alarming and working ports 1. Swap the links 2. Then checkabove where do thenot alarm is replace reported. If module the alarming 4. If steps help, the 3. If the the System Module is the only source ofModule. the alarm, or port remains the same, replace the System behind the faulty link. To clear the take thedoes following actions: replacing thefault, RF Module not clear the Radio fault, replace 3. If the alarming port changes, replace the Module the System Module that is causing the alarm. behind that 1. Swap the links between alarming and working ports. link. 2. Then check where the alarm is reported. If the alarming port remains the same, replace the System To clear the fault, take the following actions:Module. 3. If the alarming port changes, replace the Radio Module behind 1. Swapthat thelink. links between alarming and working ports. 2. Then check where the alarm is reported. If the alarming port remains the same, replace the System To clear the fault, take the following actions:Module. 3. If the alarming port changes, replace the Radio Module behind 1. Swapthat thelink. links between alarming and working ports. 2. Then check where the alarm is reported. If the alarming port remains the same, replace the System Module. 3. If the alarming port changes, replace the Radio Module behind that link.

To clear the fault, take the following actions: 1. Swap the links between alarming and working ports. 2. Then check where the alarm is reported. If the alarming port remains the same, replace the System To clear the fault, take the following actions:Module. 3. If the alarming port changes, replace the Radio Module behind 1. Swapthat thelink. links between alarming and working ports. 2. Then check where the alarm is reported. If the alarming port remains the same, Check the Radio Modulereplace alarms.the System Module. 3. If the alarming port changes, replace the Radio Module behind that link. 1. Depending on the alarm source, reset the Radio Module and/or Extension System Module by blocking/unblocking it. 2. If that does not clear the fault situation, replace the Radio that causes the FollowModule/Extension the steps below toSystem resolveModule the fault: alarm. 1. Check the cables between the System Module and 3. If theModule/Extension System Module isSystem the only alarming source, or Radio Module. replacing the RF Module/Extension System Module does Follow thethe steps to resolve the steps: not clear faultbelow situation, replace the System Module 2. Reset the alarming System Module. causing the alarm. 1. Check the cables between the Master System Module 3. Reset the site. and Radio Module/Extension System Module. Check the antenna mapping to the local cells in the 4. Replace System Module. 2. Replace the the alarming alarming unit (System Module). commissioning file.

Follow the steps below to resolve the fault: 1. Reset the alarming Extension System Module by blocking/unblocking it. To clear this fault: 2. this does not clear themodule fault situation, the (for 1. If Check the status of the with thereplace faulty port alarming Extension System Module. example, power on). 3. If the System Module is the only alarming source or 2. Check thefault: alarming fiber connection. To clear this replacing the Extension System Module does not clear the fault situation, replace the alarming System Module. 3. fiber connection. 1. Replace Switch tothe thealarming latest active BTS configuration. 2. Retry the SW update. Reset the FCT.

Baseband reset must be performed.

The FCT must be reset.

Reset of FCT should be performed.

Reset of FCT should be performed.

1. Obtain technical logs for further analysis. 2. If fault source is FCT, restart system module.

1. Collect logs from the BTS. 2. If FCT is the fault source, perform a site reset.

1. Block/unblock the SBTS. 2. If that does not help, replace the faulty module (System Module). Take the following steps to clear the fault: 1. Reset the alarming TRX from BSC. 2. Reset the BCF from BSC. 3. SBTS Site from Element Manager. ToReset clear the fault, take theSBTS following steps: 4. Check configuration: a. 1. SCF Verifyconfiguration backhaul connectivity b. profile 2. SBTS Reset the alarming TRX from BSC c. BSC configuration 3. Reset the BCF from BSC Take the following action to resolve the fault: 5. faulty modules. 4. Replace Reset SBTS Site from SBTS Element Manager 5. configuration: 1. Check Reset the alarming TRX from BSC a. SCF configuration, IPSec and IP configuration 2. Reset the BCF fromespecially BSC b. BSC configuration 3. Reset SBTS Site from SBTS Element Managerif needed 1. Check configuration and update configuration 6. Replace faulty modules 4. Check configuration: a. Update SBTS profile if profile has less resources than a. SCF configuration needed b. b. SBTS Deleteprofile extra TRX/Sector objects from BSC 5. Replace faulty modules 1. Check antenna connectors for TRX 2. Replace faulty modules

To clear the fault, take the following actions: 1. Check and update the configuration if needed. 2. Make sure the TRXs belonging to the sector are either in the range between 1 and 12 or in between the range 13 and 24. 3. Delete any TRXs/Sectors that are out of range from BSC.

1. Verify backhaul connectivity 2. Reset the alarming TRX from BSC 3. Reset the BCF from BSC 4. Reset SBTS Site from SBTS Element Manager 5. configuration 1. Check Block/Unblock the faulty radio modules assigned to the a. SCF configuration, especially sector and then Lock/Unlock the IPSec sector.and IP configuration b. BSC configuration 2. Check the cabling of the faulty radio modules. c. configuration 3. firewall Reset SBTS Site frombetween WebUI.BSC and BTS 6. Replace faulty modules 4. Replace faulty radiothe modules Reset (block/unblock) SBTS.and lock/unlock the affected sectors.

Perform the steps below in the listed order until the fault disappears. If after autonomous GPS power reset the fault does not get canceled, wait for five minutes (from the start of the fault) prior to performing the actions below. Perform the steps below in the listed order until the fault Control Interface not available: disappears. 1. The BTS has detected a malfunction in the control interface of the GPS receiver. A possible reason is that the 1. Reset the BTS. BTS and the GPS receiver do not support a common 2. Replace the faulty module. Follow theOtherwise, steps below to cleara the fault: power reset for interface. perform (remote) the GPS receiver. 1. fault name of the fault. BTS. 2. Check Performthe a (remote) BTS sitetoggling reset forBTS the whole 3. Perform a power reset for the whole BTS. 2. Follow theSW instructions of the receiver toggling and BTSthe fault to clear 4. The cable between GPS BTS might Update the in the the BTS. the problem.incorrectly. Check if the pins of the connectors be working (on both ends of the cable) are free from oxide and other Note! information about the togglingquality frequency kind ofDetailed dirt, meaning that the pin connection is can be found in the alarm history file, which can be good. Note: the steps below in the listed order until the downloaded BTSthe Site Manager. The is might 5. ThePerform cable using between GPS receiver andlog thefile BTS SBTS fault disappears. available with Snapshot. be faulty. Check the situation and change the cable, if needed. 6. There might be a HW fault in the GPS receiver. Check 1. the RET configuration theCheck operation and the GPS if needed. Note: Perform the change steps below infile. themodule, listed order until the 7. There might be a HW fault in the BTS System Module. SBTS fault disappears. 2. Download the RETand configuration to the Module, antenna ifline Check the operation change thefile System device again. needed. 1. thefault, RET perform configuration file. ToCheck clear this the following steps: 1. Make sure that the module is properly connected. If the 2. Download the RET file to the antenna line module LED does not configuration light up, the module is faulty. Check device again. the alarming module. Note! Perform the steps below in the listed order. 2. faultBTS history. 1. Check Check the if other fault indications are active. 2. Make sure that all RP3-01 fiber links and SFP transceivers between the system module and radio module are properly and working. 1. Check theconnected RS485 IUANT interface Add and missing antennaparallel line RP3-01 links. devices. Fix or replace the faulty parts or devices. 3. RadioRadio Module. 2. Restart Block orthe unblock Module. 4. Restart the BTS. 3. Block or unblock SBTS.

Replace parallel RP3-01 fiber links towards one radio module so that the maximum mutual length difference between fibers is less than 60 meters. To clear this fault: 1. Check the fan and connector. 2. If step 1 does not help, replace the fan. To clear this fault: 1. Check the fans and ensure that the ambient temperature on-site is acceptable. 2. that this doesfault: not help, replace the alarming module. ToIfclear 1. Make sure the fan is not blocked. 2. surefault: the fan connector is properly mounted. ToMake clear this 3. that sure doesthe notfan help, replace the fan. 1. If Make is not blocked. 2. Make sure the fan connector is properly mounted. Replace the fan(s). 3. If that does not help, replace the fan. If the BTS is not automatically updated by NetAct, update the BTS with the SW version running on the BTS before the SW update causing SW fallback. NOTE: In case SBTS Element Manager detects an incorrect version, the SBTS Element should If the BTSSW is not automatically updated byManager NetAct, update be reconnected. the BTS with the SW version running on the BTS before the SW update causing SW fallback. NOTE: In case SBTS Element Manager detects an incorrect version, the SBTS Element should If the BTSSW is not automatically updated byManager NetAct, update be reconnected. the BTS with the SW version running on the BTS before the SW update causing SW fallback. NOTE: In case SBTS Element Manager detects an incorrect SW version, the SBTS Element Manager should Take the following actions to clear the fault: be reconnected. 1. Check the other active alarms and act accordingly. 2. If that does not help, block/unblock the system module. 3. the for faulty cell is baseband module, 1. If Wait startup to on be the completed if aextension synchronization replace the extension module. master system module has been reset. 2. If fault 1858: EFaultId_FaultyFcmConfigurationAl is active after synchronization slave's recovery reset, check the RP3-01 Perform the cable steps between below in the the synchronization listed order until master the faultand synchronization slave system modules. disappears. 2. Check the alarms in the synchronization master system module and act accordingly. Not tracking satellites: 3. Reset the synchronization master system module. 1. The most common reason for this fault indication is that the GPS antenna installation has not been done properly, that is, the sky visibility is not good enough. Refer to the documentation for installations and if there are deviations from the actual installation, re-install the GPS antenna. Note that even when the GPS antenna has a good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter antennas of the BTS, causing disturbances for the GPS receiver.

Perform the steps below in the listed order until the fault disappears. Survey in progress: 1. Do nothing. Thebelow alarministhe informative only. Normally, Perform the steps listed order until the faultthe GPS receiver runs the survey for two reasons: disappears. - somebody has started the survey manually -No thestored GPS position: receiver has noticed that the position has changed and the has startedis an automatic survey 1. One ofthe thesteps GPSreceiver receiver settings incorrect. Using the Perform below in the listedtakes order until the fault Note: The automatic survey always place during the manager SW of the GPS receiver, set the receiver to store disappears. first start-up.into non-volatile memory. the position If there isquestionable: no tick mark in the position storage selection, the Position 2. If the automatic takessurvey place every now then, GPS receiver runs survey the site/self every timeitand the GPS The GPS receiver has valid position data but is not it1. might be an indication that the sky visibility is poor and Perform thereset steps belowbyinmanager the listedcommand, order until by thepower faultin receiver is (either line with the information estimated from the actual satellite according to the poorly-tracked satellites, the GPS receiver disappears. outage, or by reason a GPS for recovery reset). This means thatthat if the visibility. The thishas fault indication might be concludes thatinstallation the position changed. Inaverage this case, GPS receiver quality is only an and the GPS installation has not(BTS been done properly, check theantenna activity of the other history data) EEPROM invalid: especially ifsky thevisibility installation is good afaults poorenough. one -fault the GPS that is, the is not Refer tothe the and if found feasible, reinstall the GPS antenna. 1. The GPS receiver has detected a malfunction in receiver turns the reference OFF every now and then Trigger SW update for BTS to the requested SW version. documentation forPPS instructions and if there are deviations EEPROM memory of the GPS receiver. Perform a (remote) during the site survey. This means the BTS master clock with actual installation, GPS antenna. 3. If the GPS installation is reinstall good butthe the automatic survey power reset for themode GPS much receiver. drops to holdover easier during the survey Note: Even when the GPS antenna a good still takes place every now and then,has there mightsky be a than during the normal operation. visibility, the problem might be caused by installing the malfunction in the GPS Perform a (remote) power 2. There might be a HWreceiver. fault in the GPS receiver. Check GPS antenna too close to the transmitter antennas of the reset for the GPS receiver. Check the transport relatedthe configuration (C-Plane the operation and change GPS module, if needed. BTS, causing disturbances for the GPS receiver. address, U-Plane address, Transport network ID). If the 2. There might be a malfunction in the GPS receiver. 4. If the actions detailed in the previous steps do not and fault was raised at start-up, correct the configuration Perform aBTS. (remote) reset forbethe GPSfault receiver. improve situation, there might a HW in the reset thethe If thepower fault was raised during eNB runtime, 3. There might be a HW in the the GPS receiver. Check GPS receiver. Check thefault operation and change the GPS correct the configuration and apply changes to the 1. One ofif the most common for this iffault indication the operation and change thereasons GPS module, needed. module, needed. BTS. (especially occasional indications) is that the GPS/GNSS antenna installation has not been done properly, that is, the sky visibility is not good enough. Refer to the documentation for installations and if there arethe deviations If the fault persists after a BTS reset, replace alarming with the actual installation, re-install the GPS/GNSS module or plug in FSP. antenna. Note that even when the GPS/GNSS antenna has good sky visibility, the problem might be caused by installing the GPS/GNSS antenna too close to the Set the correct VSWR of threshold values using BTS transmitter antenna(s) the BTS, causing disturbances to recommissioning the GPS/GNSS receiver. with VSWR threshold supported by the Radio Module. 2. Check the other possible alarms/fault indications of the GPS/GNSS Retry the SWreceiver update.and the BTS and act accordingly. 3. There might be a malfunction in the GPS/GNSS receiver. Perform a (remote) power reset for the GPS/GNSS receiver module. Retry the SW update. 4. If there is only the alarming GPS/GNSS receiver connected to the GPS/GNSS antenna, check the antenna power feeding setting in the GPS/GNSS receiver settings. The power needs be ON infrom this the case (while in shared No manual action to is needed operator. configuration, one receiver feeds the power towards the antenna and power feeding setting of the other receivers is OFF). 5. Check the connection between the GPS/GNSS receiver module and the GPS/GNSS antenna. Note that one antenna might be shared at the BTS site between many GPS/GNSS receivers and one receiver might feed the power to the antenna - the fault indication might be caused by a failure in another GPS/GNSS receiver. 6. Perform a local/physical power reset for the alarming GPS/GNSS receiver module.

Retry the SW update.

1. If MHA is shared between two BTSs (via separate AISG port for each BTS): - Check if MHA is not switched to bypass mode by other BTS. 2. IF #data MHA is not shared two BTSs: Add users licensesbetween to Centralized SW License Reset the BTS. Server. - Replace alarming unit. Add #data users licenses to Centralized SW License Server.

Add #data users licenses to Centralized SW License Server.

Add licenses to CLS

1. Reset the SBTS.

1. Check the connectivity to the NTP server. 2. Check the NTP server configuration at BTS.

1.Check the cable connectivity on ToP master side. 2.Check the TOP configuration both in SBTS and ToP master sides. 1. Check SyncE configuration 2. Check the cabling

Note! Perform the steps below in the listed order until the alarm disappears. 1. Checkthe thelong cabling (connected to Sync Replace cable with a shorter one.InIfinterface). the radio module is connected 2. Check the 2.048 MHz or reference source is working directly toifsystem module extension baseband module normally and the 2.048 MHz signal is available. the longest supported cable length for micro DTX is approx, 16km. 3. Replace the alarming module.

If the fault is raised during micro-DTX activation: deactivate the mDTX and then activate it again by recommissioning. If the fault is raised during micro-DTX deactivation: activate the mDTX and then deactivate it again by recommissioning. Cancelation of this fault is automatically performed by the If the fault not cleared of Operator repeated may activation or SBTS afterisan SBTS sitebecause reset. The prevent deactivation of the micro-DTX, a BTS site reset clears the this fault by properly configuring the SBTS such that its fault. connection to the management system is never lost. Check SBTS configuration (sync mode) and TOP configuration.

Check FCT HW.

To get the alarm's diagnostic information for lists of information similar to the following: RMOD-a/RXb=NOK (Note: 'a', 'b' are Arabic numbers in practice), if such information is available. The system has automatic actions by decreasing the traffic Based on the alarm's info, one can try the or the functionality on diagnostic traffic. No additional action is following instructions required from the operator. to recover from the fault: 1. Check whether the cell is set up under the following The PHICHco-existence (Physical HARQ Indication scenarios, with WiMAX in Channel) the same band, cotransmission power boost can be increased reducingif existence with other LTE networks from otherbyvendors; the boosts cell-specific downlink reference yes,configured check whether thefor synchronization between networks signal and/or configured. PCFICH. are correctly 2. Checknetwork whetheroptimization. the cell is set up under a network using Perform different LTE TDD eNB software releases; if yes, then it is suggested to carefully review the calibration configurations in the vendor files among different LTE TDD eNB software releases. Perform 3. Checknetwork whetheroptimization. the GPS or other synchronization sources (for example, synchronization servers) for this cell are working as expected. 4. Check whether the cell is set up under the sharing of RFMsystem with TD-SCDMA. The has automatic actions by decreasing the traffic iforyes, it is suggested checkNo whether the action carrieris the functionality on to traffic. additional configurations in TD-SCDMA and TD-LTE are not in required from the operator. conflict. 5. Check the RP3 links state, especially for the SFP as well The system automatic decreasing theinside traffic as the fibershas connecting theactions RFM(s)byand the BBU(s) or the functionality on traffic. No additional action is the eNB. required fromunblock the operator. 6. Block and the cell. 7. Reset the BTS. 8. Examine 1) Check thethe GTP-U antenna pathcable supervision connection configuration between the of the RFM and the antenna element. eNB. 9. Exchange 2) Check if the thesupervised cable connection networkbetween element antenna is operating and RFM to check whether the RRU port or the cable is faulty. correctly. 10.Check 3) Replace thethe communication hardware(RRU/BBU). equipment between the eNB and the supervised network element. In case actDualUPlaneIpAddress = true, the S-GW might still be reachable although an alarm caused by fault 6150 is reported. Check whether other alarms caused by fault 6150 are active and check whether all GTP-U paths to the S-GW are concerned or not. If you find that all GTP-U paths to the same S-GW are faulty, the S-GW is not reachable

Perform the steps below in the listed order until the alarm disappears: 1. Check the connection with MME, based on whether the S1 link isthe broken Perform stepsaccordingly. below in the listed order until the BTS 2. Check if the MME is operational. fault disappears: 3. Check if the speed and duplex setting of the eNB S1 port is consistent with thewith switch port that is based connected 1.Check the connection adjacent BTS, on directly to the eNB (for example, they are both "Autodetect" whether the X2 link is broken respectively. Follow steps below resolve the fault: or both the "1000 FulltoBTS duplex"). 2. Check if theMbit/s adjacent is operational. 1. Check whether theright transportapath is alive. If this fault happens or a If this faultthe happens right after after a commissioning commissioning or at a MME. 2. Check configuration ofthe transport addresses configuration change, verify following configuration configuration change, verify the IP address of the adjacent data: address the MME. Note: Perform theofsteps below in the listed order until the BTS. IP alarm disappears: 1. Check the connection with MME, based on whether the M3 link is broken accordingly. 2. MME isthe operational. 1. Check Check ifwhether transport path is alive. 3. Check if the speed and duplex setting of eNB M3 is 2. Check the configuration of transport addresses at port MME. consistent with switch port which is connected directly to the eNB for example both "Autodetect" or both "1000 Mbit/s Full duplex". Perform the steps below in the listed order until the BTS fault If thisdisappears: fault happens right after a commissioning or a 1. Check the commissioning parameters. configuration change, verify the following configuration 2. Load correct file to the BTS. data: IP the address of commissioning the MME. Block/unblock the BTS.

Block/unblock the BTS.

Check the connection with the third party tool.

Perform the steps below in the listed order until the BTS fault disappears: 1. Check the other active BTS faults. 2. Reset LTE RAT. During failures in subscriber trace session 3. Reset the SBTS by blocking/unblocking it. activation/deactivation, based on the error cause provided 4. Update and activate the SW to the BTS. as part of the additional info for the alarm raised, the 5. Check must the SW following be files. done: 6. Replace FSM. -Check "Subscriber & Equipment not enabled": and ensure that the Trace PLMNsfeature that have been listed Enable the subscriber trace feature at the BTS. Any with this BTS fault and that have been configured at events BTS corresponding to the failed subscriber trace and any for one or more cells have at least one MME serving other them subscriber started later,ofwhich mustisbegreater recorded, and that thetraces relative capacity that MME thanwill be recorded at the BTS after the feature is enabled. zero. - "trace reference in use, trace cannot be started": This problem is out of the scope of what can be fixed at the BTS, and is within the scope of the NMS (Network Management System) used to activate the subscriber trace. The error means that there is already an active subscriber trace at the BTS that is using the same Trace Reference Number. A possible solution is to try deactivating all subscriber traces and activating them again. - "max number of UE trace session reached, trace cannot

1.Check if the maximum number of LNADJ objects has been reached. If yes, check if there are LNADJ objects that can be manually deleted. This makes space for new LNADJ information. Check if maximum number of LNADJW was reached. If 2.Check if the maximum number objects of LNADJL yes, check if there are LNADJW that objects can be has been reached. If yes, check if there are LNADJL objects manually deleted. This makes space for new LNADJW related with LNADJ object that can be manually deleted. object. This makes space for new LNADJ information. Check if the maximum number of LNRELW objects has been reached. If it has been, check if there are LNRELW objects that can be manually deleted. This makes space for new LNRELW object. Check if: 1) the maximum number of LNRELW per cell and WCDMA carrier frequency has already been reached (is greater than or equal to the lnRelWLimitForAnr parameter value (in ANPRW profile).object If it has been, to check if there neighbor are LNRELW Add the LNREL pointing the correct to objects per cell and WCDMA carrier frequency that can be allow the handover or enable the UE-based ANR. manually deleted. This makes space for new LNRELW object per cell and WCDMA carrier frequency. 2) the maximum number of mobility parameters (either of: Reset (block/unblock) the BTS recover per the cell faulty cell. psHoAllowed, srvccAllowed) of to LNRELW and WCDMA carrier frequency is greater than or equal to the limit in 3GPP 36.331 (32). Block/unblock the BTS.

1. Check for E-UTRAN cells that operate on the same frequency layer and use the same PCI and that are in close vicinity. 2. Reassign PCIs for the discovered cells. If the GPS is configured as a reference clock, perform the following: 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. connection between the operate GPS receiver 1. Check Check the for UTRAN (FDD) cells that on theand same FSM. frequency layer and use the same PSC and that are in close vicinity. If TOP signal configured as a reference 2.the Reassign PSCsisfor the discovered cells. clock, perform the following: Reconfigure are related to the Inter eNB 1. Check the parameters connection that to the TOP server. Carrier Aggregation feature.

Upgrade/downgrade SW so that the same version is on all eNBs that have the Inter eNB Carrier Aggregation feature.

In cases wherein not enough link throughput has been detected, check the SFP module link speed capabilities and replace it if necessary. In other cases, no manual actions are needed from the operator. Removing neighbor related objects below maxNumAnrMoiAllowed brings the BTS to full operational state. Removing neighbor related objects below the internal threshold turns off the notification alarm. The BTS stays in full operational state. Perform the steps below in the listed order until the BTS fault disappears. 1. Check BTS commissioning that all the carrier aggregation relations are pointing towards a proper cell Block/unblock the BTS. that exists within the carrier aggregation cluster. Modify or delete the mismatching relations. 2. If an existing cell is totally missing from BTS within the carrier aggregation cluster, add the cell. Block/unblock themismatches BTS. 3. If there are no in the carrier aggregation relations, reset the BTS.

Perform the steps below in the listed order until the alarm disappears: 1. Check the availability of the adjacent BTS. 2. Check the connection with the adjacent BTS. 3. Disconnect and below reconnect the adjacent Perform the steps in the listed orderBTS. until the alarm disappears: 1. Check connectivity to the related adjacent BTS. 2. Check other faults. 3. Checkthe thesteps parameters related to the X2 interface to the Perform below in the listed order until the alarm adjacent BTS. disappears: 4. BTS. of MME. 1. Reset Check the availability 2. Check other faults on MME and BTS. 3. Checkthe thesteps parameters related to S1 interface in the BTS Perform below in the listed order until the alarm and MME. disappears: 4. 1. Reset Check the the BTS. availability of MME. 2. Check the connection with MME. 3. Disconnect and below reconnect MME. Perform the steps in the listed order until the alarm disappears: 1. Check the availability of the MME. 2. Check the connection with the MME. 3. Disconnect and the MME. Check the value ofreconnect the "rimStatus" parameter in LNADJG or LNADJW (according to the alarm source) objects to find all impacted RIM associations. If only a few LNADJG/LNADJW objects have "rimStatus" Unavailable, check if LNADJG/LNADJW identifiers (cell global ID) of related GERAN/UTRAN cells are correct. If many LNADJG/LNADJW objects have "rimStatus" Unavailable, check the connectivity to GSM/WCDMA network (MME<->SGSN<->BSC). Note that only one alarm for one PLMN is raised due to the RIM faults for GERAN and only one for UTRAN, no matter

Check the value of the "rimStatus" parameter in LNADJG or LNADJW (according to the alarm source) objects to find all impacted RIM associations. If only a few LNADJG/LNADJW objects have "rimStatus" This fault does not require any (special) actions. Unavailable, check if LNADJG/LNADJW identifiers (cell global ID) of related GERAN/UTRAN cells are correct. If many LNADJG/LNADJW objects have "rimStatus" Perform the steps in the listedtoorder until the fault is Unavailable, checkbelow the connectivity GSM/WCDMA resolved: network (MME<->SGSN<->BSC). 1. Reset Module. Note thatthe onlySystem one alarm for one PLMN is raised due to the RIM faults for GERAN and one for UTRAN, no fault matter Perform the steps below in only the listed order until the is 2. Replace the System Module. how many LNADJGs or LNADJWs are affected at a given resolved: time. The alarm is raised for the first LNAJDG/LNADJW where thethe fault is detected. The alarm additional 1. Reset System Module. information contains the parameters of the first Note! Perform the steps below thefault listed order until the LNADJG/LNADJW, even if the in RIM is already inactive 2. Replace the System Module or faulty FSP fault is resolved. for the LNADJG/LNADJW, but the fault is still active for card. other LNADJG/LNADJW supporting the same PLMN. 1. Reset the System Module. Note! Perform the steps below in the listed order until the 2. Replace the System Module or faulty FSP card. fault disappears. 1. Reset the System Module. Note: Perform the steps below in the listed order until the 2. Replace the System Module or faulty FSP card. alarm disappears: 1. Check the availability of MME. 2. Check the connection with MME. Note: Perform the steps below in the listed order until the 3. Disconnect and reconnect MME. alarm disappears: 1. Check availability of MME. 2. Checkthe other faults on MME and Perform following steps until theBTS. alarm disappears: 3. Check the parameters related to M3 interface in the BTS and MME. 1. Edit the delta plan file and set the MBMS subframe 4. Reset the BTS. pattern share (subfrPShareRequired) to a value equal to or less orbe modify other This than fault subfrPShareDeployed is a warning and cannot cleared. The parameters to get additional subframe resources. sessions that cannot be resumed are automatically cleared 2. Push deltaReset plan file to the BTS. using M3the Partial procedures. None

Follow the steps below to clear the fault: 1. Check the availability of IP connectivity. 2. Check whether there are active alarms at the far end. If found, follow the instructions for handling those alarms. 3. Check if the far end has BFD switched ON.

E1 interfaces: Check that the interface type of the far-end interface is also configured to be a framed E1 interface. If this is not the case, reconfigure the interfaces so that they match each other. 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. 3. there are alarms at the far end. If 1. Check Check whether the availability of IPactive connectivity. there are, follow the instructions for handling those 2. Check whether there are active alarms at the far alarms. end. If 4. To verify that the hardware of the interface works there are, follow correctly, connect loop cable andalarms. check whether the the instructions forahandling those alarm disappears. Switch offthat the the loopback or waitoffor timeout to expire 5. Check length/type thethe cable/fiber does not which opens the loopattenuation and cancels introduce excessive or the thatalarm. the cable/fiber is cut somewhere. 6. Check that the Ethernet interface has correct autonegotiation settings, fitting to the far-end interface. 1. Check that the SFP module is correctly installed. 7. an optical Ethernet 2. With Plug-out/plug-in the SFP interface: module. Check that the inserted module matches type and 3. CheckSFP for SFP validity (couldthe be fiber the wrong type) and wavelength of the Gigabit Ethernet link provided. insert a compliant SFP module. 4. Checkgeneral that theconfiguration electrical contacts of the SFP module are Execute checks: clean from dust, dirt or water. - Configuration of primary/secondary CRL server IP 5. Replace SFP module with a module recommended address andthe port. by Nokia. - Configuration of DNS server IP address. Note that only the SFP might be towards faulty, not the entire -Replace Configuration of IPsec policies the faulty SFP. Note that only theremote SFP ispeers. faulty, hardware unit. Check remote peers and intermediate network elements not the entire hardware unit. interconnections. Check the LDAP connection towards the Certificate Revocation List server. 1. Clean the names. cables and connectors. Check DNS 2. Check areCertificate properly connected the Check thethat sizethe of connectors the file at the RevocationtoList unit. server. 3. Checkconnectivity that the cable connected interface in Perform checks relatedtotothe primary/secondary question is not damaged and is within the specifications. CRL servers. Check that the configured interface type matches the 4. Follow the E1 path in the network and check configured interface type of the far end. If this iswhether the case, any other alarms concerning are on (such as the problem is somewhere in the the fault transmission network. Laser End of Life) and signal quality of each individual link. If they are, follow the instructions for handling those Check alarms.the intermediate transmission network for alarms indicating the root cause 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 Replacing faulty hardware: check that no alarms appear for thismodule interface. 1. Re-insert the expected transport referenced in the fault text. 2. If the transport module is still not recognized, replace the faulty module with a new one.

1. Check if the negotiatedLocalIPAddress is same as the configuredLocalIPaddress. 2. 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. Check for LCP failure alarms of the PPP-links belonging to Change the values to interface the correct ones accordingly either at the SL-PPP/ML-PPP and follow the instructions the local end or of these alarms. peer if there is a mismatch. Check all the PDH related alarms and follow the instructions of 1. Check CMP configuration. these alarms. 2. Check for CA server reachability. 3. If none of the above work, contact CA administrator/Nokia service personnel. 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 of the BFD local andfor remote 1. Check theconfigurations network between both BFD peers physical peers match. 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, thenand theifalarm caused by with a 1. Check the backhaul usage other is applications link speed downshift event. the same or higher PHB may compete against this 2.1 Check that theabout cables fully plugged in to the TWAMP session theare capacity. An increase in the connectors. priority of TWAMP session or of the backhaul capacity may 2.2 Check that a CAT5e or higher Category cable is used clear the alarm. 1. thethe backhaul 2.3Check Replace cable. usage and if other applications with the same or higher PHB may compete against thisis slave 3. If the clock mode of the local 2. Check the last measured RTTEthernet values ofinterface this TWAMP TWAMP session about the capacity. An increase in the and the Ethernet configured to serve as session verifyinterface that the is configured RTT threshold value priority ofand TWAMP session or the of the backhaul capacity may synchronization source, then alarm is caused by athat is not too close to average measured RTT values, so clear the alarm. clock mode mismatch. Check the could vendor certificate expiry date and renew it. this alarm beBTS result of sporadic mis-measurement. 3.1 Check the clock mode setting of the remote link 2. CheckItifshould destination is unreachable by IP connectivity partner. be either "multiport device" or "manual test. Send an ICMP echo request (ping) to the UDP port of master". the the destination IP.If ICMP echo 3.2 TWAMP Configurereflector the localatclock mode to "manual slave" Update trust Ethernet anchors. reply indicates that theinterface destination is unreachable you forcing local to operate at slave but clock have mode.access to TWAMP reflector, you can check its status. If the status is disabled or down try to activate it again and check if alarm disappears. Note: Do not execute this step remote, but only when being local at site as it alarms can cause thePPP-links Ethernet belonging link to be to Check the LCP failure of the 3. PLR PLRmight to these 0%be down. As configured a result, remote management access theCheck ML-PPP interface andthreshold. follow the Setting instructions of should be avoided, because every lost measurement lost. alarms. packet will trigger the alarm and it cannot be cleared again (PLR>=0). Note: Check whether root causeand of the fault not existing Check the related PDH alarms follow theisinstructions anymore, is done by a new auto-negotiation process. of these alarms. Retriggering auto-negotiation requires manual action by the user, (i.e. changing Ethernet interface configuration, plug out/plug in cable, triggering link down/link up).

1. Confirm that SyncE is desired as a synchronization source. 2. Confirm that configuration settings for ssmEnabled are correct. 3. with Backhaul provider about the reason 1. Troubleshoot Confirm that SyncE is desired as a synchronization for SSM errors. source. 2. Confirm that SBTS configuration settings for ssmEnabled are correct. 3. Troubleshoot Backhaulonprovider aboutside. the reason Check the cablewith connectivity ToP master for SSM errors. Check the TOP configuration both in SBTS and ToP master sides. 1.Check for duplicate IPv6 addresses configured in the SBTS. 2.Change or delete the identified duplicate IPv6 addresses. Upgrading SW: - Upgrade the SBTS SW release to the latest version that includes the support for the new HW variant. Replacing variant: bypass by making the security Start IPsecHW emergency -gateway Replacenot thereachable unsupported device variant out to another oneor either by plugging the cable that is supported by the the currently running SW release. configuring 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 that the configurations for the peer and the SBTS security policies for corresponding failure notification.

Commission the BTS site with correct IP addresses.

No action is needed.

Depending on the installed and commissioned synchronization sources, see the commissioned synchronization options below and perform the steps in the listed order until the BTS fault indication disappears. Check your username and password. GPS receiver (PPS source): 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. Check the connection between the GPS receiver and FSM. TRS reference (ToP as source): 1. Check that the signal is being received from the ToP Master. 2. Check the TRS status. 3. Check the synchronization settings of the TRS unit. BTS is Sync hub slave and rfsharing is enabled: 1) Remove the root cause that leads to a not synchronized sync hub slave. 2) If there is a need to change settings, either perform remote re-commissioning via NetAct or un-commission the BTS prior to re-commissioning using Site Element Manager.

Related Faults

Related Features

• RP000956: SBTS Startup and runtime management

• RP000847: BTS Synchronization mode support

• RP000911: SBTS HW Management


• RP000980: SBTS Recovery


• RP000912: SBTS SW Management


• RP000996: SRAN Clock time management








• RP000923: SBTS State Transitions

• RP000923: SBTS State Transitions

• RP000940: SBTS Diagnostics and Self Test



• 10457: field report of routing component

• RP000920: SBTS Fault Management

• ARAN1163: Iu-PS Throughput Measurement for GTP Traffic

• RAN1671: Enhanced UltraSite Base Band (EUBB)



























• RP001016: SBTS OMUSIG inside SBTS

• RP000788: 1PPS&ToD Sync from external GNSS Receiver


























• RP000376: Synchronization from 2.048MHz signal

• LTE435d: CN5259 New alarm to RF SW to indicate RP3 collision problems


• RAN2262: Flexi Multimode System Modules FSMF and FSMG

• RAN2262: Flexi Multimode System Modules FSMF and FSMG

• RP000920: SBTS Fault Management


• RAN1263i: Generic RAKE for HSPA baseband efficiency final implementation











• LTE656: LTE Fault Management













• RP000979: interface between system modules















• RP001004: SBTS Data User RTU



• RP000834: IP Traffic Capacity


• RP000996: SRAN Clock time management

• RP000375: Synchronous Ethernet


• RP000377: Synchronization from PDH interface

• RP001052: LTE feature parity

• RP001052: LTE feature parity

• RP000929: SBTS Configuration Management



• RP000941: Datacollectors support







• RP000367: Small Form Factor Pluggable Slot (SFP slot)

• RP000845: SBTS Operator Certificate Management

• RP000367: Small Form Factor Pluggable Slot (SFP slot)












• RP000365: Electrical 10/100/1000-Base-T Interface








• RP000384: Timing over Packet Resilience

• RP000589: IPv4/IPv6 Transport Stack


• RP000439: IPsec Emergency Bypass

• RP000465: Local and Remote IP Traffic Capturing

• RP000900: SBTS user account management

• RP000600: Backup IPsec Tunnel




#N/A

#N/A

#N/A

#N/A

SBTS Faults and Alarms

Recommend Documents