You are on page 1of 318

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


ur 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:

- <fault/alarm attribute> in issue ... which shows the value in the previous issue of the document.
- <fault/alarm attribute> 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 Alarm Number Alarm Name


01A and 01B

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 The effect of the fault on the functioning of the
base station. This fault may have an impact on network element depends
the existing cells across RATs. Check the reason on the fault description. For more information,
for the fault from the supplementary text field of
see base station fault
the alarm. descriptions in SBTS System Libraries.
The device is being reset to recover from a faultThe effect of the alarm on the Network Element
(or faults). depends
on the fault description. For more information,
see base station fault
descriptions in SBTS System Libraries.
The service/device has been blocked by the user. The service/device is blocked 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)


The effect of the fault on the functioning of the
that belong to the sector indicated in the alarm. network element depends
Check the reason for the fault from the on the fault description. For more information,
supplementary text field of the alarm. see base station fault
descriptions in SBTS System Libraries.
A fault (or faults) has occurred in the RAT base The effect of the fault on the functioning of the
station. Check the reason for the fault from the network element depends
supplementary text field of the alarm. on the fault description. For more information,
see base station fault
descriptions in SBTS System Libraries.
A fault (or faults) has occurred in the Single RAN The effect of the fault on the functioning of the
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 in SBTS System Libraries.
A fault (or faults) has occurred in the base The effect of the fault on the functioning of the
station connectivity/interface. Check the reason network element depends
for the fault from the supplementary text field of on the fault description. For more information,
the alarm. see base station fault
descriptions in SBTS System Libraries.
A fault (or faults) has occurred in the base The effect of the fault on the functioning of the
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 in SBTS System Libraries.
A fault (or faults) has occurred in the base The effect of the fault on the functioning of the
station security. Check the reason for the fault network element depends
from the supplementary text field of the alarm. on the fault description. For more information,
see base station fault
descriptions in SBTS System Libraries.
Capacity limitation (or limitations) has occurred in
The effect of the fault on the network element
the base station due to a missing license. Check depends
the reason for the fault from the supplementary on the fault description. For more information,
text field of the alarm. see base station fault
descriptions in SBTS System Libraries.
The service/device has been blocked by the user. The effect of the fault on the functioning of the
For details, refer to GSM/EDGE BSS Operating network element depends
Documentation. on the fault description. For more information,
see base station fault
descriptions in SBTS System Libraries.
A fault (or faults) has occurred in the BCF. The effect of the fault on the functioning of the
For details, refer to GSM/EDGE BSS Operating network element depends
Documentation. on the fault description. For more information,
see base station fault
descriptions in SBTS System Libraries.
Fault has occurred that disallows OSC/DFCA The effect of the fault on the functioning of the
feature operation. network element depends
For details, refer to GSM/EDGE BSS Operating on the fault description. For more information,
Documentation. see base station fault
descriptions in SBTS System Libraries.
A fault (or faults) has occurred in the TRX. The effect of the fault on the functioning of the
For details, refer to GSM/EDGE BSS Operating network element depends
Documentation. on the fault description. For more information,
see base station fault
descriptions in SBTS System Libraries.
Fault has occurred that disallows OSC/DFCA The effect of the fault on the functioning of the
feature operation. network element depends
For details, refer to GSM/EDGE BSS Operating on the fault description. For more information,
Documentation. see base station fault
descriptions in SBTS System Libraries.
A fault (or faults) has occurred in the (E)GPRS The effect of the fault on the functioning of the
protocol layer. network element depends
For details, refer to GSM/EDGE BSS Operating on the fault description. For more information,
Documentation. see base station fault
descriptions in SBTS System Libraries.
Main power is lost. Battery backup is switched The effect of the fault on the functioning of the
ON. network element depends
For details refer to GSM Alarms Documentation: on the fault description. For more information,
Base Station Alarms (7000-7999); DN9813099 see base station fault
descriptions in SBTS System Libraries.
The alarm is raised if the service under The communication link between the local SBTS
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 are erroneous.
This loss of frame alarm is raised when the local Possible impact on the connections over this
receiver is unable to detect the frame alignment interface:
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 elements
This alarm is raised when either no or an No data or clock information is exchanged via
Probable cause: The interface at the far end is - loss of synchronization if the interface is used
incompatible signal is received on the interface this 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 an Ethernet interface, the physical Ethernet - voice calls or data connections are aborted and
A dead peer was detected in one of the IPsec Possible effects:
link is detected to be down. All other transmission cannot be established anymore
associations of the SBTS. - no calls are possible
alarms related to this signal are suppressed.
There is no response to the requests sent to the - loss of remote management access to other
- remote management connectivity is lost and
peer, neither during the IKE network elements
Probable causes for Ethernet interfaces: cannot be established anymore
SA setup, the IPsec SA setup, nor during DPD. - IKE SAs and IPsec SAs cannot be established
Note: When IPsec backup tunnel feature is or re-keyed
- a cable/fiber is cut or there is no cable/fiber - loss of synchronization if the interface is used
enabled, this alarm is not raised
connected to the interface as a synchronization source
due to failures when trying to setup primary IPsec
tunnel in "Secondary_Active_Probing_Primary"
- the electrical/optical signal is excessively - Depending on use of the Ethernet interface, the
state.
attenuated above described impact can occur for the local
SBTS and/or other (S)BTS elements if they are
- the port at the connected far end node is chained via the Ethernet interface.
switched off
This alarm is raised if a loopback has been The interface cannot be used for transmission. It
configured by a management application on the can be used for connectivity checks only.
interface mentioned in the alarm text.

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
- the signal level is too low (connectors or cables
interface referenced in the alarm text has lost the this interface becomes invalid.
are dirty, electrical connectors or cables are
multiframe alignment.
corroded)
- the specified maximum length of the cable is
Probable cause: The interface type has not been
This alarm is raised when an alarm indication
exceeded Possible impact on the connections over the
configured to meet the framing of the interface at
signal is received.
- the connector Thisproperly
is not signal isconnected
generatedtoby an interface in question:
the
the far end. For E1 interfaces, the configuration
intermediate
unit PDH device in the forward direction - no calls are possible
of the far end node should be E1 Multiframe.
because it detects
- the receiver or thea far
problem in its received
end transmitter has failed - loss of remote management access to other
signal.
-This
the alarm
accumulated network elements in the RAN
is raised when a remote defectE1 path Possible impact on the connections over this
BER of the end to end
AIS
is defect
too high. is detected when the incoming signal
indication is received. It is sent by the interface:
has two or less zeros in each of two consecutive
intermediate or the far end 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 elements in the RAN
This alarm is raised when the localIPAddress Possible impact on the connections over this
Probable cause: The far end has a LOS, LOF or
negotiation with the peer
All other transmission fails.related to this
alarms interface:
AIS alarm on its receiving interface.
signal are suppressed. - the SL-PPP/ML-PPP interface is not available.
- loss of remote management access.
Probable cause: There is a transmission
This alarm is raised if local and peer ends problem Possible impact on the connections over this
somewhere
disagree on in thethe intermediate
LCP configuration network along
leading the PPP link:
to LCP
E1 path andfailure.
negotiation AIS is sent instead of user traffic. - 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 at least one link is available).
This alarm is raised if the PPP interface is not Impact on the connections over this interface:
- loss of remote management access to other
operational either when all the PPP-links in the
network elements in the RAN.
ML-PPP interface are not available or the PPP- - loss of remote management access.
link supporting the SL-PPP interface is not
available.
The alarm is raised if the BFD state for the The communication link between the local and
session is not AdminDown and nevertheless no the remote peer is defective or the peer is
BFD packet is received at the local end during defective.
the detection time. Transport service may not be available and calls
may be dropped.
The alarm is raised if the BFD state of the The communication link between the SBTS and
The alarm is raised if the BFD session is in
session is not AdminDown and the BFD packet the BFD peer is defective.Transport service may
activated state.
from the far end contains the diagnostic code = not be available and calls may be dropped.
'Control Detection Time Expired' and no BFD
down Ingress alarm is present.
This alarm indicates that there is a mismatch The Ethernet Link got established with an
between SBTS expected auto-negotiation result unexpected clock mode or technology.
The alarm is raised only if BFD session is in
and actual auto-negotiation result.
activated state.
Possible impact on the connections over this
An Ethernet link was established but during link interface:
The RTT threshold alarm is raised in case the This alarm is an indication that the backhaul
establishment a link speed downshift event took
average value of the RTT for this TWAMP capacity for traffic with the same profile as this
place. A link speed downshift takes place when - Increased packet delay variation and increased
session from the last 1-min period equals or TWAMP session (DSCP value, packet size) may
auto-negotiation successfully negotiates a certain average delay for all voice/packet and
exceeds the configured threshold. be too small, because the measurement packets
technology but the link cannot be established management connection
are scheduled later than before.
with this technology. It is tried then to establish
the link with the next lower speed technology. - 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 seem to have been thrown
This alarm is raised if at least one of the PPP- The ML-PPP interface operates 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 The remote peer to come online with the same IP
tests the direct attached network whether, other address on the same subnet as local peer would
already configured node, on the network uses just disable their network interface and give an
already same IPv6 addresses on their network IP error until the situation is resolved by the
interfaces. The DAD (Duplicate address administrator.
SBTS has entered IPsec emergency bypass All configured IPsec policies are ignored and all
detection) detects those duplicated IPv6 This allows the local peer to continue functioning
active state where configured IPsec policies are the SBTS traffic is sent unprotected.
addresses and prohibits the operation of this without disruption, but completely breaks IP base
ignored and all traffic is sent unprotected.
IPv6 address in the SBTS. The Alarm contains communications for the connected network.
the corresponding IPv6 address and the interface
The alarmthe
on which is activated when
address was the IP traffic
configured. For each The resulting packet capture files can used for
capturing
DAD eventsession is started.
a separate reporting shall be Expert analysis to identify network problems and
indicated. to help determine the best course of action.
The SBTS is currently capturing IP traffic towards
a local port or into a file on the SBTS.
This alarm will be triggered when the primary SBTS traffic has switched over from the primary
IPsec tunnel fails and IPsec tunnel to secondary (backup) IPsec tunnel
If the traffic capturing is happening towards a
SBTS has switched over to secondary IPsec terminating on secondary security gateway.
local port, the port and destination MAC address
tunnel.
needs to be provided.
As a result of failure of the primary IPsec tunnel,
The alarm is raised when the IKE authentication The IKE SA cannot be established.
SBTS has automatically switched over to
credentials
Port values provided by the
can be LMP or <peer
HW MODULE
secondary IPsec tunnel terminating on secondary
is
NAMEnot valid.
>-<PORT ID>.
security gateway.
Example: LMP or FSM-EIF1, FSM-EIF2 or FTIF-
EIF1
The alarm is raised, if IKE parameters are not IKE SA cannot be established and subsequently
matching with the peer proposal. It can happen no IPsec SAs can be established.
due to following two failures
--> When the SBTS sends or receives a failure
notification as response to an IKE_SA_INIT
This alarm is raised when the SBTS sends or The related IPsec SA can't be established and
request message. The failure notifications
receives following notification as response to an used.
includes:
IKE_AUTH or CREATE_CHILD_SA request
- NO_PROPOSAL_CHOSEN
message.
- INVALID_SYNTAX
The failure notifications includes the following:
- INVALID_MAJOR VERSION
- NO_PROPOSAL_CHOSEN
- INVALID _IKE_SPI
- TS_UNACCEPTABLE
- INVALID_MESSAGE_ID
- INVALID_SYNTAX
- UNSUPPORTED_CRITICAL_PAYLOAD or
- INVALID_MAJOR VERSION
FAILED_CP_REQUIRED
- INVALID _IKE_SPI
--> When the SBTS sends or receives a failure
- INVALID_MESSAGE_ID
notification as response to an IKE_AUTH request
- UNSUPPORTED_CRITICAL_PAYLOAD
message.The failure notifications include:
- SINGLE_PAIR_REQUIRED or
- INVALID_SYNTAX
FAILED_CP_REQUIRED
- INVALID_MAJOR VERSION
- INVALID _IKE_SPI
- INVALID_MESSAGE_ID
- UNSUPPORTED_CRITICAL_PAYLOAD
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, RET, FYG, or SFP.
1. EAC line input ID

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 See description of the related fault
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.
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 For details, refer to GSM/EDGE BSS Operating
Documentation. Documentation.

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 For details, refer to GSM/EDGE BSS Operating
Documentation. Documentation.

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 For details, refer to GSM/EDGE BSS Operating
Documentation. Documentation.

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

Please check the below fault-specific description for detailed instructions.

-----------------------
FAULT NAME
10b8b coding error in Optical Interface device <opt link/RP3>
FAULT NAME
FAULT ID
10b8b coding error in Optical Interface device <opt link/RP3>
2004: EFaultId_OIC_LVDSRecAl
FAULT ID
Unblock
MEANING the service/module with SBTS Element Manager.
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 interface and the
The fiber cable is experiencing interference; data transmission is faulty.
summing function
The operation depends has occured(possibly
on the type of alarm caused thatbyuser baddefined
circuit as joints).
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
FAULT theNAME following actions to clear the fault:
MEANING
[User defined]
INSTRUCTIONS
Please
The
1. Resetuser checkhasRadio
the the below
blocked Modulethefault-specific
cell
with withthethe description
faultySBTS for detailed
Element
optical by instructions.
Manager.
interface
Take the following actions to clear the fault:
blocking/unblocking
FAULT ID it.
FAULT
INSTRUCTIONS NAME
1400:
1. Reset EFaultId_ExtAl0
the Radio Module with the faulty optical interface by
10b8b
To
2. cancel
If thiscoding
does errorclear
the alarm,
not inunblock
Optical
the fault, Interface
the cell. device
replace the Radio<opt link/RP3>
Module that is causing
1401: EFaultId_ExtAl1
blocking/unblocking it.
the
Please alarm.check the below fault-specific description for detailed instructions.
1402: EFaultId_ExtAl2
FAULT ID
1403:
2. If EFaultId_ExtAl3
this does not clear the fault, replace the Radio Module that is causing
2004:
3. If the EFaultId_OIC_LVDSRecAl
System Module is the only source of the alarm, or replacing the
1404:
the EFaultId_ExtAl4
alarm.
RF
FAULT
1405: ModuleNAME does not clear the fault, replace the System Module that is
EFaultId_ExtAl5
MEANING
FAULT
causing NAME
the alarm. in summing
Address
1406:
3. If the mismatch
EFaultId_ExtAl6
System
Please
The
SBTS fibercheck
blockedcablethe isModule
below is
experiencing the only
fault-specific source ofdata
description
interference; the alarm,
for or replacing
detailed
transmission the
instructions.
is faulty.
1407:
RF Module EFaultId_ExtAl7
does not clear the fault, replace the System Module that is
FAULT
1408:
causing ID
EFaultId_ExtAl8
theconnection
alarm.
A physical
FAULT NAME
ID failure between the optical interface and the
2019:
1409: EFaultId_Muksu_SsubMmAl
EFaultId_ExtAl9
<parameterName>
summing
50: function has
EFaultId_BTSBlockedAl outoccured(possibly
of range caused by bad circuit joints).
1410: EFaultId_ExtAl10
Please
MEANING
1411: check the below fault-specific description for detailed instructions.
EFaultId_ExtAl11
FAULT
INSTRUCTIONS
MEANING ID
There
1412: isNAME
a baseband bus address mismatched in the summing. There are
EFaultId_ExtAl12
4235:
Take
The
Antenna EFaultId_VswrThresholdOutOfRangeAl
the
SBTS following
is causes:
line blocked
device actions
HW to
theclear
withfailure SBTS theElement
fault: Manager. The fault indicates
FAULT
two
1413: NAME
possible
EFaultId_ExtAl13
that
BTS the alarms
RNC/Flexi that might be raised
Direct interface signalling link during a SBTS
failuremaintenance task
1414:
FAULT
MEANING EFaultId_ExtAl14
NAME
1. Resetbe
should
FAULT ID the Radio Module with the faulty optical interface by
avoided.
A configuration
1415:
Antenna
Please EFaultId_ExtAl15
link isor
check error
down
the below (twofault-specific
different baseband description unitsfor functioning)
detailed - after an
VSWR major
blocking/unblocking
1847: VSWR
EFaultId_HardwareErrorAl it. minor value set is out of range duringinstructions.
FAULT
1416: ID
acknowledgment,
EFaultId_ExtAl16 the fault returns.
commissioning.
INSTRUCTIONS
17: EFaultId_CnbapLinkAl
1417:
FAULT EFaultId_ExtAl17
FAULT
2.
To thisID
Ifcancel NAME
does not clear
the alarm, the fault,
unblock the replace
SBTS. the Radio Module
Unblocking that iscauses
of the SBTS causing
MEANING
Data
1418:
476:
2M corruption
EFaultId_ExtAl18
EFaultId_Rp3BusError
external on the
reference bus - appears
missing once when unsynchronized data is a
INSTRUCTIONS
the
site
A alarm.
reset.
hardware failure detected by an antenna line device. Usually, this is a
MEANING
sent
1419: byEFaultId_ExtAl19
the baseband.
Set
Please the
permanent correct
check fault VSWR
(the
the below threshold
hardware is
fault-specific values
broken). using
description BTS recommissioning
A common
1420:
MEANING NBAP
EFaultId_ExtAl20 link failure has occurred that is for detailed
possibly instructions.
caused by a
FAULT
with
3. VSWR
If the IDSystem threshold
Module supported
is the only by source
the Radio of theModule.
alarm, or for
replacing the is
transmission
INSTRUCTIONS
1421:
The Antenna network
EFaultId_ExtAl21
(RP3) linkproblem.
is down: Thethe most common
transmitter or reason
receiver this alarm
drops out
1899:
RF EFaultId_2MExtRefMissAl
Module
INSTRUCTIONS
FAULT
frequent NAME does
transmission not clear the
breaking. fault, replace the System Module that isof
Check
1422: the antenna mapping
EFaultId_ExtAl22
synchronization. to the local cells in the commissioning file.
causing
1. Block
Automatic the
orBTS alarm.
unblockOperatorthe Radio Module
Certificate to giveunsuccessful
retrieval a power-off reset to the
1423:
MEANING EFaultId_ExtAl23
FAULT
antenna
INSTRUCTIONS NAME
line devices.
1424:
The EFaultId_ExtAl24
reference clock monitoring has detected a loss of 2.048 MHz signal
Toggling:
FAULT
1. Reset IDthe<Fault
the WCDMA name> SW.
1425:
Perform
received EFaultId_ExtAl25
from steps
an below
external inreference
the listedsource,order until the faulttodisappears:
connected
2. If that does
61510: NO_CERTIFICATE not help, replace the antenna line device. Sync In
interface
FAULT NAMEof the System Module.
IDthe transmission links to the RNC/Flexi Direct RNC.
2.
1. Check
FAULT
ResetNAME
MEANING the SBTS.in summing
Address
4026:
MEANING mismatch
EFaultId_TogglingAl
Antenna
High or
INSTRUCTIONS lowlinkvoltage
is downon the external alarm line.
FAULT
A
3. requested
Check NAME thecertificate
BTS could notthe
and RNC/Flexi be retrieved
Direct RNCFSM. from the certificate
transmission settings.authority
2. If
Note!
FAULT
Antenna that does
Perform
IDline devicenot
the help, HWreplace
steps failure in thealarming
below listed order until the alarm
MEANING
(CA).
FAULT ID
The user
disappears.
2019: specifies
EFaultId_Muksu_SsubMmAl the fault text during commissioning.
BTS
FAULT
A
4. Fault,
requested
476:Reset thewhich
NAME fault name
certificate
SBTS.
EFaultId_Rp3BusError could is notmentioned
be renewed in the
from Fault
the name field,authority
certificate is
FAULT
toggling
Antenna
(CA). IDin the
line BTS.
device The
missing toggling
software alarm condition is presented to the user
INSTRUCTIONS
1. Check the cabling (connected
MEANING
1847:
with EFaultId_HardwareErrorAl
this
5. Replace new theBTS SystemFault. Togglingtoalarms
Module.
Sync In areinterface).
supressed until the toggling
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
Not check#data
enough the below
users fault-specific description
licenses is available for detailedSW
in Centralized instructions.
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
HSUPANAMEusers limitation alarm
Pipe dangerously overheating
Please check the below fault-specific description for detailed instructions.
FAULT ID
FAULT
4286: ID
FAULTEFaultId_HsupaUsersLimitationAl
NAME
1938: EFaultId_FrPipeOverheat
Pipe dangerously overheating
MEANING
Please
MEANING
Not check the below fault-specific description for detailed instructions.
enough
FAULT ID #data users licenses is available in Centralized SW License
The validated
Server. temperature
Parameter of any PA or Pipe sensor is
BTSSCW/numberOfHSUPASet1 in to
RFbemodule equals
reduced
1938: EFaultId_FrPipeOverheat
or exceeds the predefined value on the unit property file.
internally.
MEANING
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.
Add Check
#dataif usersthe ambientlicenses temperature
tovalue
Centralized and SWenvironmental
License file. conditions are
Server.
or exceeds the predefined on the unit property
within
FAULTthe NAME design limits for the radio module. When the ambient
temperature
Mains powerand break, environmental
running battery conditions
backupexceed the limits, the alarm
INSTRUCTIONS
startup is expected and no further actions are needed.
1.
1. Check
Check ifthe theavailability
ambient temperature and environmental conditions are
of IP connectivity.
FAULT
within the ID design limits for the radio module. When the ambient
2. Check
FAULT
37: NAMEif the air flow is not blocked by foreign objects. Make sure
EFaultId_MainsBreakAl
temperature
2. Check and environmental
whether thererate are$R activeconditions
alarms atexceed
the farthe
end.limits, the alarm
If found, follow
minimum
IP traffic thermal limit
capacity clearances are
levelfollowed.
$L raised Remove
$T any objects that might
startup
theblocking is expected
instructions and
for handling no further
those actions are needed.
alarms. according to the instructions
be
MEANING airflow and mount the module
and
FAULT
E1 recommendations.
isIDaiffault
interfaces: Check
in the that thepower
interface
There
2.
3. Check
Check if the
the airfar flow
mains
end hasis notBFDblocked bytype
supply.
switched
of the
The
foreign SBTSfar-end
has interface
ON. objects. Make sure
received a is also
4293:
configured
Battery
minimum EFaultId_IPTrafficCapacityLimitAl
Backupto bealarm
thermal aclearances
framedand E1 interface.
theareintelligent Ifshutdown
followed. this is notprocedure
Remove the
anycase,
objects reconfigure
has started.
that might
3.
the Check
interfaces if excessive
so that sunlight
they match is causing the unit to overheat. Install the
be blocking airflow and mount theeach
moduleother.
according to the instructions
sunshield
MEANING
INSTRUCTIONS following the mounting instructions and recommendations.
and recommendations.
Licenses
Check are
thethatmains missing since the time ($T) indicated in the fault name. The
1. Check
IP the power supply.
cables/fibers are connected to the correct connectors.
3. Check if excessive sunlight israte
traffic is throttled to the peak ($R),the
causing at the
unitlevel ($L) indicated
to overheat. Install in
thethe
fault
sunshieldname. Level
following denotes
the mounting a per cent of the
instructions maximum IP traffic
and recommendations. throughput
2.
in aCheck
15-minutesthat theinterval
interface at the
before thefar-end interface
fault has is switched
been raised. on and
For every has
expiry
correct
FAULT auto-negotiation
NAME settings.
of seven days (after missing licenses have been detected) at time($T), the
Unit
level
1. Check(module)
($L) the dangerously
decreases
availability by 5%. overheating
of IP When the level ($L) changes then a new
connectivity.
3. Check
alarm is whether there are active alarms at the far end. If there are, follow
raised.
2. Check whether there are active alarms at the far end. If there are, follow
the
FAULT instructions
ID for handling those alarms.
the
FAULT instructions
NAME for handling those alarms.
1937:
Time: EFaultId_FrDangerouslyOverheat
The "$T"dangerously
format is a local time stamp (GMT+/-xx:xx). For example:
Unit
4. To(module)
verify that the hardware overheating
of the interface works correctly, connect a
2014-04-12 00:51:26 GMT+0530
loop
MEANING
Level cable and check whether the alarm disappears.
FAULT($L): ID 100% to 50% in 5% steps
The
Rate validated
($R): sensor
current temperature
policed peak rate exceeds or is equal to the predefined
1937:
5. Check EFaultId_FrDangerouslyOverheat
thatunitthe property
length/type
value on the file.of the cable/fiber does not introduce
excessive attenuation or that the cable/fiber is cut somewhere.
MEANING
INSTRUCTIONS
The
6. validated
Check that sensor temperature exceeds or is auto-negotiation
equal to the predefined
1.
Add licenses if thethe Ethernet
toambient
CLS interface
temperature has
and correct
environmental conditionssettings,
are
value
fitting onthe
to thefar-end
unit property file.
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
startup and no interface: Check
further actions that
are the inserted SFP module
needed.
1. Check the
matches if the ambient
fiber type and temperature
wavelength andofenvironmental
the Gigabit Ethernetconditions
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 the cable connected to the interface in question is not


Check that the configured interface type matches the 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
of eachthe intermediate
individual link. Iftransmission network
they are, follow for alarms for
the instructions indicating thethose
handling root
cause
alarms.and follow the instructions for handling these alarms.

1. Check the intermediate transmission network for alarms indicating the


root cause and follow the instructions for handling these alarms.

2. Check the transmit hardware, connect a loop cable and check that no
alarms appear for this interface.
Check if the negotiatedLocalIPAddress is same as the
configuredLocalIPaddress. Change the values to the correct ones
accordingly either at the local end or peer.

Check the following parameters status: localMruResult, remoteMru,


pfcResult, acfcResult.
Check if the LCP configuration parameter values (acfcTarget,
localMruTarget, pfcTarget) match with the peer.
Change the values to the correct ones accordingly either at the local end
Check for LCP failure alarms of the PPP-links belonging to the SL-
or
PPP/ML-PPP interface and follow the instructions of these alarms.
peer if there is a mismatch.
Check all PDH related alarms and follow the instructions of these alarms.

1. Check the network between both BFD peers for physical link failures or
mis-configurations.
2. Check if the BFD functionality in the peer is switched on and that the
configurations of the BFD local and remote peers match.
1. Check the network between both BFD peers for physical link failures or
misconfigurations.
2. Check if the BFD functionality in the peer is switched on and that the
configurations of the BFD local and remote peers match.
1. Check the negotiated speed and clock mode at the Ethernet interface
to determine the root cause of the alarm.

2. If the Ethernet interface speed is 100Mbps, but 1000Mbps was


expected, then the alarm is caused by a link speed downshift event.
1. Check the backhaul usage and if other applications with the same or
higher PHB may compete against this TWAMP session about the capacity.
2.1 Check that the cables are fully plugged in to the connectors.
An increase in the priority of TWAMP session or of the backhaul capacity
may clear the alarm.
2.2 Check that a CAT5e or higher Category cable is used
2. Check the last measured RTT values of this TWAMP session and verify
that the configured RTT threshold value is not too close to average
2.3 Replace the cable.
measured RTT values, so that this alarm could be result of sporadic mis-
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 if destination is unreachable by IP connectivity test. Send an
Check the LCP failure alarms of the PPP-links belonging 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
3. Check configured PLRidentified duplicate
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)
10121610911011112512813914915841847618061854189319001901190319041905190719101911191219261956200020012
• RP000911: SBTS HW Management
• RP000910: SBTS Antenna Line Management
• RP000980: SBTS Recovery
• RP001052: LTE feature parity
• RP000847: BTS Synchronization mode
• RP000980: SBTS Recovery
support
• RP000956: SBTS Startup and runtime
• LTE656: LTE Fault Management
4849504026 •management
RP000923: SBTS State Transitions
• RP001016: SBTS OMUSIG inside SBTS
• LTE656:
RP001016:LTESBTS
FaultOMUSIG
Managementinside SBTS
• RAN1671: Enhanced UltraSite Base Band
• LTE656: LTE Fault Management
(EUBB)
• 10457: field report of routing component
1400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424
• RP000956:
RP000920: SBTS Startup and runtime
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: Enhanced UltraSite Base Band
1288109110111124130139145146149154157158418420476180618932006200720082009201020192057205820592060206
• ARAN1163: Iu-PS Throughput Measurement
(EUBB)
for GTP Traffic
• RP001052: LTE feature parity
• RP000980: 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:
RP3 SBTS Startup
collision and runtime
problems
• RAN1671: Enhanced UltraSite Base Band
management
• RP000956: SBTS Startup and runtime
(EUBB)
•management
RP000912: SBTS SW Management
• RAN1263i: Generic RAKE for HSPA baseband
• LTE435d:
RP000788:CN5259
1PPS&ToDNew Sync
alarmfrom
to RF SW to
external
efficiency final implementation
indicate
GNSS RP3 collision problems
Receiver
1718114402661506202620362046205620662616284630363046308631763216322632368506851
• RP000980: SBTS Recovery
• RAN2262: Flexi Multimode System Modules
• RP001016:
RP000941: SBTS OMUSIGsupport
Datacollectors inside SBTS
FSMF andLTE
•• LTE656: FSMG Fault Management
LTE656: LTE Fault Management
• RP000920: SBTS Fault Management
• LTE656: LTEreport
10457: field Fault of
Management
routing component
9162618171818181918981899190319041926200520132014205240114019402641144122412341244125412642104297429
• RP000847:
RP001016: BTSSBTSSynchronization
OMUSIG insidemode SBTS
support
• RP000929: SBTS Configuration Management
• RP000384:
RP000910: Timing over Packet
SBTS Antenna Line Resilience
Management
• RP000996: SRAN Clock time management
• RP000375: Synchronous Ethernet
4026414542664267426842696107461510616166161861642
• LTE656: LTE Fault Management
• RP000788: 1PPS&ToD Sync from external
• RP000912: SBTS SW Management
GNSS Receiver
• RP000900: SBTS user account management
• RP000357: Symmetrical E1 Interface
• RP000845: SBTS Operator Certificate
• RP000979: interface between system modules
Management
• 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 • RP000357: Symmetrical E1 Interface

61104 • RP000357: Symmetrical E1 Interface

61150 • RP000357: Symmetrical E1 Interface

61151 • RP000357: Symmetrical E1 Interface

61152 • RP000357: Symmetrical E1 Interface

61250 • RP000176: MLPPP termination

61251 • RP000176: MLPPP termination

61252 • RP000176: MLPPP termination

61605 • RP000361: Link Supervision with BFD

61606 • RP000361: Link Supervision with BFD

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


Interface

61610 • RP000360: IP Transport Network


Measurements
61611 • RP000360: IP Transport Network
Measurements

61622 • RP000176: MLPPP termination

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 • RP000356: IPsec for BTS

61645 • RP000356: IPsec for BTS

61646 • RP000356: IPsec for BTS


Clearing Time to Live

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the service/device is unblocked by user.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


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

Do not cancel the alarm. The system automatically cancels 0


the alarm when the service/device is unblocked by user.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.

Do not cancel the alarm. The system automatically cancels 0


the alarm when the fault has been corrected.
[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 0


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

The alarm condition for a protect policy does not exist 0


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
failure will be cleared
SW registers the expiration of the loopback timer. 0

As soon as the EBER is not exceeded anymore, the alarm 0


is canceled.

As soon as a multiframe signal is detected, the alarm is 0


cancelled.
The Device Driver software reads the alarm status directly
from the HW chip.
As soon as no AIS signal is received, the alarm is 0
canceled.
The Device Driver software reads the alarm status directly
from the HW chip.
As soon there is no remote defect indication received on 0
the interface, the alarm is canceled.

Device Driver software reads the alarm status directly from 0


the HW chip.

Device Driver software reads the alarm status directly from 0


the HW chip.
The alarm is canceled if the PPP-link is up again for 100
milliseconds.
This alarm is automatically cleared when at least one of the 0
PPP-links in the ML-PPP/SL-PPP interface is up and
running for more than 100 milliseconds.

For a session that is not set locally in AdminDown mode, 0


the SBTS continuously monitors the received amount of
BFD packets from the peer during the configurable
detection time. If the peer sends again BFD packets, the
alarm is cancelled.
For an active BFD session SBTS checks continuously the 0
diagnostic codes in the BFD packets received from the
BFD peer.
The system cancels the alarm autonomously once the local
BFD session again receives error-free BFD packets from its
The alarm is cancelled once an auto-negotiation process 0
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 mode mismatch is cause of the alarm, then
periods the average value of the RTT remains below the
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 0
periods are error free again.

Device Driver software reads the alarm status directly from 0


the HW chip.

The alarm is cleared once the duplicate address is either 0


deleted or changed to a different address.

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 0


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

The
Note:alarm is cleared
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
is disabled or receives
or SBTS an IKE_AUTH response
is rebooted.
message without a AUTHENTICATION_FAILURE
notification for the related policy or an failure notification
This alarm is cleared 0
which will result into raising this alarm.
- when the SBTS sends or receives an
IKE_AUTH_RESPONSE message without a failure
Note: please not that not all notifications above are send by
notification for the related policy
the BTS
- when the SBTS sends or receives an
CREATE_CHILD_SA response message without a failure
notification for the related policy
Note: please not that not all notifications above are send by
the SBTS.
Note:
See the How to Read This Report tab
for instructions on the usage of Fault List

Changes between issues Fault ID


01A and 01B

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 SBTS


reference frequency

No connection to unit SBTS

Baseband resources mapping to cells failure SBTS

Unit synchronization failed SBTS

BTS RNC/Flexi Direct interface signalling link SBTS


failure

BTS RNC/Flexi Direct interface signalling link SBTS


failure

Incompatible SW version detected in unit: SBTS


<unitName>

Obsolete SW version detected SBTS

BTS time not corrected SBTS


Error in file server during file download type SBTS
<fileTypeNumber>

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 SBTS


used
Unknown HW resource SBTS

Unit not supported by running SW SBTS

Carrier power measurement fault SBTS

Telecom configuration failure SBTS

Telecom configuration failure SBTS

Telecom configuration failure 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 SBTS
HSUPA

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 SBTS


services

Ten consecutive Nacks received from a DSP at SBTS


DCH setup

PIC pool configuration failure SBTS

Not enough CCCH Processing Set licenses SBTS


commissioned

Hanging HSPA resources SBTS

One of the Common Transport Channels is SBTS


deleted

Not enough CCCH processing capacity to SBTS


setup cell
Flash operation failure SBTS

Flash operation failure SBTS

Flash operation failure SBTS

Flash operation failure SBTS

Flash operation failure 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 SBTS


fault, <line>

Mast Head Amplifier below current window SBTS


fault, <line>

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

RET antenna control failure SBTS

RET antenna control failure SBTS

RET antenna control failure SBTS

RET antenna control failure 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

Antenna line device operation failure SBTS

Antenna line device operation failure SBTS

Antenna line device operation failure 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 SBTS


connection to Radio Module
Critical BER detected on the optical connection SBTS
to Radio Module

Antenna line switched off SBTS

RP3 routing collisions are detected on FR SBTS


module

RF Module External Alarm and Control lines SBTS


configuration failed

Optical interface faulty SBTS

Optical interface faulty SBTS

Receiving failure in optical interface SBTS

10b8b coding error in Optical Interface device SBTS


<opt link/RP3>

Synchronization failure in Optical Interface <opt SBTS


link/RP3 link>

Optical interface data/control/Ethernet buffer SBTS


full

Optical interface data/control/Ethernet buffer SBTS


full

Optical interface data/control/Ethernet buffer SBTS


full
Optical interface data/control/Ethernet buffer SBTS
full

Optical interface data/control/Ethernet buffer SBTS


full

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 <trxId> initialization failure SBTS

TRX <trxId> control plane link failure SBTS

TRX <trxId> OBSAI failure SBTS

TRX <trxIds_separated_with_comma> SBTS


configuration mismatch between BSC and BTS

TRX <trxId> RSSI failure on <radioType- SBTS


radioNumber> antenna <antennaNumber>

Incorrect sector configuration for TRX SBTS


<trxIds_seperated_with_comma>
TRX <trxId> user plane link failure SBTS

One of the radio modules in centralized SBTS


configuration is not in working state

BTS reset required SBTS

GPS Receiver alarm: control interface not SBTS


available

Master unit has lost connection to the slave unit SBTS

Toggling: <Fault name> 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

<parameterName> out of range SBTS

Failure to verify the signature of a signed SBTS


software release

Failure to verify a signed software release SBTS

Unsigned software release has been SBTS


successfully downloaded
Failure to download software due to missing SBTS
software signature

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 SBTS


$T

SBTS reset required to use hot inserted SBTS


baseband extension module

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

U-plane overload detected SBTS

U-plane overload detected SBTS

GTP-U Path Failure SBTS


Transport layer connection failure in S1 SBTS
interface

Transport layer connection failure in X2 SBTS


interface

S1 SCTP path failure SBTS

Transport layer connection failure in M3 SBTS


interface

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 SBTS


party tool

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 SBTS
exceeded

Maximum number of WCDMA neighbor cells is SBTS


exceeded

Maximum number of WCDMA neighbor SBTS


relations is exceeded

Maximum number of WCDMA neighbor SBTS


relations per cell and carrier is exceeded

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 SBTS


between eNBs

Inter eNB SW inconsistency in between cluster SBTS


members
Inter eNB communication failure SBTS

Overload detected: max number of neighbor SBTS


relation objects reached

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 SBTS


overflow

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 SBTS


available share

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 SBTS


$U, interface $IF

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 SBTS


unsuccessful

BFD $session down, ingress, $sourceIP to SBTS


$destinationIP

BFD $session down, egress, $sourceIP to SBTS


$destinationIP

Auto-negotiation mismatch, on unit $U, SBTS


Ethernet interface $IF

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 SBTS
$IF

SyncE Quality Level Degraded on unit $UID, SBTS


interface $IF

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 SBTS


$m]

BTS Local OAM user account $A has been SBTS


locked

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 SBTS


name or password
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, Radio Module, DSP

FSP, FCT FSP, Radio Module, DSP

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 Start / Cancel


exceeds the threshold value.

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
Connection to a module belonging to the Start / Cancel
measurement period, compared to the
SBTS configuration has been lost or FSP
BTS master clock frequency.
cannot be detected.
The cause of the alarm can be:
A
1. failure was detected
The reference frequencywhenhasNodeB
changedO&M Start
system
becausepresented
of a fault available FSPs to
in the transmission
WCDMA and LTE RAT software
network synchronization (which in in turn
orderis
to map FSPs
caused by an to cell. The fault
equipment FSPsorrelated
a settingto
the faulty
error). Note operation
that if may
the not be utilized.
network
Meaning can be: Start
The reason for the
synchronization failure is an
malfunction internal
lasts for a
1. The BTS is site level phase
problem
long time,with
the the
alarmNodeBis O&M system.
cancelled when
synchronized only (e.g. via 1PPS/ToD
the
syncBTS frequency
chain), reaches the faulty
the synchronization Master
reference synchronization.
is frequency synchronized and The hasalarm can
A common
also NBAP iflink
be activated thefailure
faulty has Start / Cancel
aquired a new arbitrary phasereference
due to
occurred that is possibly
synchronization is correctedcaused
and by a is,
there
reset.
transmission
again, a differencenetwork problem.
of 0.2 ppm or The most
more.
common
The alarm reason for thiswhenever
alarm is frequent
2. The BTSiswas cancelled
at holdover the
for a long
transmission
difference breaking.
becomes less thanphase
0.2Protocol
ppm.
A dedicated
period and the Node-B Application
accumulated Start / Cancel
drift
(NBAP) link failure
has exceeded has occurred, possibly
+-5ms.
2. The reference
caused by the RNC. frequency fluctuates
continuously because of a significant
3. BTS Internal synchronization between
amount
units of
(e.g. jitter/wander
FCT/FSP/FBB in -the
DSP) has
A new unit with
transmission an incompatible
network. The alarmSW is Start / Cancel
failed.
might have been inserted into the SBTS.
continuously activated/cancelled
(however, the alarming state might
predominate). There is always some
jitter/wander
Running SW in the transmission
version is not able tonetwork;
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
synchronization fails which
information via theis 2.048
used Start / Cancel
to
MHzsynchronize time for all nodes
or 1PPS synchronization in BTS.
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 Start / Cancel
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. There is a possible error in the
The download is corrupted or the Start / Cancel
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
<fileTypeNumber> thatfailed. The in
is included Start / Cancel
error might
the fault namebe caused by a unit
is a variable reset
parameter,
during the SW update,
which identifies the typea of
hardware
file for which
problem in thefailure
the download unit, cabinet
has been reported.
Incompatibility problems with the
The SBTS SW update has failed. The Start / Cancel
download or a corrupted flash file
error might be caused by a unit reset
system.
during the SW update, a hardware
problem in the unit, cabinet
Incompatibility problems with the
There is a fault in the mains power Start / Cancel
download or a corrupted flash file
supply. The SBTS has received a Battery
system.
Backup alarm and the intelligent
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 Start / Cancel


Manager.

The purpose of the fault is to avoid


alarms that might be raised during the
The user has blocked the cell with the Start / Cancel
unit maintenance task.
SBTS Element Manager.

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 Start
product code or its physical device
address (object ID).

In case of FR, the additional meaning is


An unsupported module has been Start
that FR was found in planned HW
detected in the SBTS. Typically, this
configuration but is connected to the
happens when a new version of a
wrong port.
module is installed and there is an older
SBTS SW in use that does not support
The RF module power 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 Start
- FSP unit to FCT allocation failure
configuration or registration failure, a unit
- DSP subunit to FSP allocation failure
RNW configuration failure, and a telecom
RNW reconfiguration failure.
Note that depending on the fault source,
The faultstatus
the unit indicates
mighta betelecom
related slave
to either Start
- FSP unit to FCT allocation failure
configuration
the state of a or registration
particular carrierfailure, a unit
resource
- DSP subunit to FSP allocation failure
RNW
on theconfiguration
Radio Module failure,
module and oraFSP
telecom
RNW
board reconfiguration failure. the unit
on the FCT. Therefore,
Note that depending on the fault source,
status
The might
BTSstatus not be
does might in line with
not receive the source
a response Transient
the unit be related to either
- FSP
HW unit
unit to FCT allocation failure
state.
from the RNC
the state (a block request).
of a particular carrier resource
- DSP subunit to FSP allocation failure
on the Radio Module module or FSP
board on the FCT. Therefore, the unit
Note that depending on the fault source,
status
Either might not be (the
in line with oftheCPICH
source
the unitcell enabling
status setup
might be related to either Start / Cancel
HW unit
andstate state.
BCH)ofora cell disabling (theresource
release of
the particular carrier
common
on the Radiochannels)
Module has failed.or FSP
module
The
boardreason
on themight
FCT. be a hardware
Therefore, the or a bus
unit
problem,
status or anot
might lackbeofinDSP
line or transport
with the source
Either cell enabling (the setup of CPICH Start / Cancel
resources.
HW
and unit
BCH) state.
or cell disabling (the release of
common channels) has failed.
The reason might be a hardware or a bus
problem, or a lack of DSP or transport
There is not enough BTS baseband Start / Cancel
resources.
capacity to set up a cell.

The radio output power has dropped. Start / Cancel


There is a fault in the downlink
transmission path.

The lower LCR ID has been assigned to Start


a higher frequency, or vice versa, for an
RF Module that is in dual carrier mode.

A second carrier is assigned to an RF


Module that is in single carrier mode.
At least one LCG in the BTS does not Start / Cancel
have enough resources for the HSUPA
minimum capacity commissioned with the
parameter "Number of HSUPA resource
steps reserved for HSUPA users".
133: Start / Cancel
If the LCG has two HSUPA schedulers,
EFaultId_RxAntennaSignalLevelTooLow
then the sum of the HSUPA Resource
Al
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 Start / Cancel
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
and minimum DSP powerconfiguration to the
levels of all RX Start / Cancel
134:
correct
antennas mode.
in the same cell and sector
EFaultId_RxAntennaSignalLevelDifferenc
exceeds the defined limit for cell.
eTooHighAl
The difference between the maximum
If
andthere are no power
minimum DSP resources forRX
levels of all PIC Start / Cancel
configuration,
antennas in the Telecom rejects
same cell and the PIC
sector
configuration, and raises
exceeds the defined limit an
for alarm
cell. to
indicate "Resource block not available".
If PIC configuration cannot be allocated Start / Cancel
to a DSP resource because the DSP is in
use with some high-priority users,
Telecom raises this fault. Telecom then
tries to move the high-priority users to a
One particular DSP Nacks DCH setup 10 Start
different resource block, and tries again
times with cause
to allocate PIC configuration to the DSP
"NotEnoughResources=10" or
a number of times for 3 minutes. In case
"AlreadyActivated_Allocated=22" within a
of failure, Telecom rejects the received
20-minute period.
1.Cell setup isand
configuration rejected
indicatebecause
a messageeither all Start / Cancel
cells in the block
"Resource same occupied
LCG, having the same
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 outside
The cell is inactive because of a lack of Start / Cancel
the PIC pool.
sufficient Common Control Channel
2.The PIC pool configuration (new or
Processing Set (CCCH Processing Set)
updated) is rejected if either all LCELs in
licenses commissioned to the BTS.
the same LCG, having same UARFCN
The
do notPSCR request
belong to thefor setting
same PICup new
pool or a Start
HSPA
LCEL thatresources
does notis made
belong ontoalready
any PIC
existing
pool hasresources
UARFCN (allocated in DSP SW
that is already
internal
assigneddatabases).
to any PIC pool from the same
LCEL's
One of the LCG.
Common Transport Channels Start / Cancel
3.Rel. 3
(PCH, FACH,BTS only:
RACH) Tooismany cellsby
released have
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
rel. 1cell
andremains
Fixed BB inactive because
Allocation of a
Pooling, Start / Cancel
lack processing
this condition capacity for
is checked the Common
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.
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 Start


occurs.

If only one FSP in BTS generates this


fault then there is a malfunction in
An out of frame data error interruption Start / Cancel
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 Start / Cancel


transmitter or receiver drops out of
synchronization.

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 <x> 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 Start / Cancel
is not acceptable for the BTS hardware,
because of an incorrect frequency band
and/or a carrier spacing and/or the
number of carriers.
- Baseband bus configuration was Start / Cancel
rejected by NodeOAM/HWAPI.

The baseband bus synchronization has Start / Cancel


failed.

The OCXO warm-up takes too long and Start / Cancel


the OCXO does not become active within
a period of eight minutes from the power-
on. The ambient temperature can also be
too low or it changes too fast.
Master clock frequency is 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 Start / Cancel
working properly. The received Radio
Module signal level has decreased.

If both stages of the LNA on the uplink


The Masthead Amplifier (MHA) is faulty. Start / Cancel
path fail, the MHA switches the LNA to
The received RF signal level is
by-pass mode. In by-pass mode, the
decreased.
MHA has no gain but some loss. If a
single stage of the LNA fails, the MHA
If both stages of the LNA on the uplink
Radio
still hasModule
about a has detected
half an gain.
of its normal Start / Cancel
path fail, the MHA switches the LNA to
overcurrent on the MHA,
With an integrated antenna theline.
faultThe
might
the by-pass mode. In the by-pass mode,
antenna
affect bothline can and
main be damaged (short
diversity branches.
the MHA has no gain but some loss. If
circuit), or an antenna line device is
only one stage of the LNA fails, the MHA
causing an overload. All antenna line
VSWR
still hasvalue
aboutexceeds
half of itsthe defined
normal level. Start / Cancel
gain.
devices powered by the antenna line are
The
Withantenna line isMHA,
an integrated mismatched
the faultormay
out-of-order.
damaged.
affect both main and diversity branches.

The Radio Module or the Filter has Start / Cancel


detected an VSWR value that exceeds
the defined level. The antenna line is
slightly mismatched.
The filter has detected a malfunction in Start / Cancel
the LNA unit.

A filter has not been able to tune on an Start / Cancel


appropriate sub-band (tuning failure).
Radio Module has detected major failure Start / Cancel
of filter unit.

Tilting the antenna is not possible or Start / Cancel


might function incorrectly.

Tilting the antenna is not possible or Start / Cancel


might function incorrectly.

Tilting the antenna is not possible or Start / Cancel


might function incorrectly.

Tilting the antenna is not possible or Start / Cancel


might function incorrectly.

Tilting the antenna is not possible or Start / Cancel


might function incorrectly.

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. Start / Cancel


Returned upon unsupported procedure
when in Download Mode.

A corrupted SW file in the FLASH is Start


detected. The unit cannot perform a
complete start-up.

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) Start / Cancel


has been detected. The fault completely
prevents the gain function of the MHA.
The device is not working properly, the Start / Cancel
configuration is not valid, or a given
parameter is incorrect.

The device is not working properly, the Start / Cancel


configuration is not valid, or a given
parameter is incorrect.

The device is not working properly, the Start / Cancel


configuration is not valid, or a given
parameter is incorrect.

The device is not working properly, the Start / Cancel


configuration is not valid, or a given
parameter is incorrect.

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 System Module.
The Radio module configuration has 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 Start / Cancel


differs from the clock on the Radio
Module.

The baseband bus between the system Start / Cancel


module and the Radio module is out of
synchronization.
The Radio module baseband bus is Start / Cancel
incorrectly configured.

There is an error in the baseband or Start / Cancel


optical bus.

The Radio Module TX path cannot be Start / Cancel


used.

The TX output power adjustment has Start / Cancel


failed.

The Radio module filter has measured a Start


TX power that is too low.

The Radio module RX FR synthesizer is Start


unlocked.

The Radio module is out of order Start / Cancel


because of a software or hardware fault.

The feedback signal to predistortion is Start / Cancel


too weak or is missing. The TX
performance is degraded.

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 Radio Module runtime, the
or serial number is missing. It is also
temperature inside the Radio module is
possible that the module product code is
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 Start
failed at start-up.

The Radio Module lost the lock to the Start / Cancel


incoming clock.

The highest temperature exceeds the Start / Cancel


power decrease limit.

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 Start / Cancel


required.

Fans are rotating faster than required. Start / Cancel

Validated module temperature exceeds Start / Cancel


or is equal to the predefined maximum
value allowed.

The validated sensor temperature Start / Cancel


exceeds or is equal to the predefined
value on the unit property file.

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 Start / Cancel
detected on the optical link to the radio
module resulting in LCV errors in
downlink baseband processing.
An abnormally high bit error rate has Start
been detected on the optical link to the
Radio Module which results in permanent
baseband processing failure. I/Q data
stream cannot be successfully processed
The antenna line has been autonomously Start
by the Radio Module due to the
disabled by FRM to protect the HW from
occurrence of consecutive LCV errors.
high reflection conditions.

Radio module has detected permanent Start / Cancel


RP3 routing collisions either in the
downlink (TX), or in the uplink (RX)
transmission direction.
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 fibre cable package.
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 fibre cable package.
The incoming optical 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 Filter, Antenna Line Device) or
A physical connection failure between the
between the Master System Module and
optical interface and the summing
The RP3 channel
the Extension has lost
System the achieved
Module is broken. Start / Cancel
function has occured(possibly caused by
frame synchronization
This might concern thestate.
primary or
bad circuit joints).
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 or incorrect
The control message traffic between the Start / Cancel
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 Start
frame pulse has been achieved earlier,
but it differs from the currently received
frame pulse. The internally generated
frame clock might have drifted.
A decoding error has been detected in Start / Cancel
the baseband internal link. The data
packet is lost or the content is corrupted.

This situation is also triggered when links


There is a baseband bus address Start / Cancel
do not synchronize with each other.
mismatched in the summing. There are
two possible causes:

A configuration error (two different


A new RP1 Frame Clock Burst (FCB) Start
baseband units functioning) - after an
burst/message has been received from
acknowledgment, the fault returns.
the RP3-01 interface while processing
the previous burst/message.
Data corruption on the bus - appears
The
onceclock
whencrossing buffer underflow
unsynchronized or
data is sent Start
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 signal and the
The SW update of the BTS has failed or Start
internal clock, or an incorrect RX rate
the BTS SW is corrupted.
setting.

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 Start / Cancel
messages that are to be summed. If a
specific header type is rejected then no
summing is performed, and an empty
message is sent instead.
Transmitter detected an RP3 message 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 Start


sRIO switches has been triggered.

SRIO error rate is too high. Start / Cancel

O&M software was not able to initialize Start / Cancel


TRX into operational state, even though
it should have been possible.

TRX control plane connection has been Start / Cancel


lost.

DSP related to TRX was not able to Start / Cancel


initialize OBSAI (RP3) resources.

O&M software was not able to map TRX Start / Cancel


resources received from BSC to
resources available from SBTS profile.

Logical TRX has measured difference Start / Cancel


exceeding threshold between signal
strength of Rx antennas.

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 Start / Cancel
lost.

One of the radio modules in a two radio Start / Cancel


module configuration(centralized
configuration) is not in working state.

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 Start / Cancel


problem with the GPS receiver.

The fault is ignored until the GPS


receiver has reached commissioned
The connection to the FSP or DSP has Start / Cancel
state.
been lost or the submodule reports an
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 BTS Fault. Toggling alarms are
A corrupted SW file in the FLASH is Start
supressed until the toggling alarm
detected. The unit cannot perform a
condition is cleared. Severity of this BTS
complete 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 Start / Cancel


connected between FSM and FR.
Commissioned cells cannot be routed
through the existing RP3-01 links.
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 Start / Cancel


detection. Detection is attempted again
after Fan.Detection.Timer expires.

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 Start / Cancel


control is higher than 0.

Speed of the fan(s) is/are deviating too Start / Cancel


much from the required control.

Fan(s) is/are running faster than Start / Cancel


required.

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

There is no accurate position stored in Start / Cancel


the EEPROM.

The receiver is used in the stored Start / Cancel


position but has been moved to a new
position.

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 Start / Cancel
failed.

TRS IP configuring or re-configuring by Start / Cancel


RROM has failed.

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 because the information
There has been a failure to validate the Start / Cancel
of either Hash Container file or Hash
hash of the questioned SW files for FCT
Container Signature file is not present in
except of Hash Container file or Hash
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
hasunsigned
failed. software release has been Start / Cancel
be downloaded to the BTS system
downloaded to a BTS system module
module because the hash value of the
that is currently running 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 there is no software signature
MHA was unexpectedly set to bypass Start / Cancel
for the release, and only signed software
mode.
can be installed.

Not enough #data users licenses is Start / Cancel


available in Centralized SW License
Server. Parameters
BTSSCW/numberOfHSDPASet1,
BTSSCW/numberOfHSDPASet2,
Not enough #data users licenses is Start / Cancel
BTSSCW/numberOfHSDPASet3 are to
available in Centralized SW License
be reduced internally.
Server. Parameter
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
Baseband extension module is inserted Start / Cancel
IP traffic throughput in a 15-minutes
into a working SBTS. Manual SBTS reset
interval before the fault has been raised.
is required to activate and use this unit.
For every expiry of seven days (after
missing licenses have been detected) at
A Certain the
time($T), NTPlevel
server
($L)indicates problems
decreases by 5%. Start / Cancel
with
When the connections.
the level ($L) changes then a new
alarm is raised.

Time:
TimingThe
over"$T" format
packet is a local time
is unavailable or Start / Cancel
stamp (GMT+/-xx:xx). For
unusable as a clock source. example:
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 Start / Cancel
module has failed.

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 re-
Configured ToP (frequency/phase) Start / Cancel
established using the previous
doesn't match with configured sync mode
configuration as a recovery action. This
(frequency/phase) and hence requested
alarm is visible until the next SBTS site
ToP configuration cannot proceed.
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 that processes data
An overload situation has been detected Start / Cancel
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, and minimum
value per Physical Resource Block (PRB)
reserved power for PDCCH.
of the cell for UL subframes exceeds the
predefined threshold for at least the
operator-configured
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 to continue operation on the
One of the transport paths (SCTP) in Start / Cancel
faulty connection with the adjacent BTS.
SCTP connection to MME has failed.
Only applicable when SCTP multi-
homing is supported. An alternate
transport path is available to pursue
The transport path (SCTP) for 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 on the faulty connection with
One of the transport paths(SCTP) in Start / Cancel
the MME.
SCTP connection to MME (which
provides MBMS service) has failed. Only
applicable when SCTP multi-homing is
supported. An alternate transport path is
There was an opening, reading, or file 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. The detected problem can be a file
A BTS raises this fault if it experiences a Start
handling problem (for example, open,
problem in internal configuration
read, and write operations fail) as well as
data distribution (cell setup) to C- and U-
content 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 Start / Cancel
connection between the SBTS and the
third party tool.

There was an opening, reading, or file Start / Cancel


content problem with a BTS vendor-
specific file at BTS startup.
The fault is also detected when a vendor-
specific file is missing.
A failure has occurred during 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
- The Subscriber Trace feature is not
new UEs, which select those PLMNs.
enabled at the BTS.
- The Id used for the subscriber trace
These PLMNs that are considered
session is already in use for another
misconfigured by the BTS are:
active subscriber trace session.
- currently configured at the BTS for one
- The number of subscriber trace
or 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 by the BTS, which is
cells. However, none of these PLMNs
60.
have serving MME(s) with relative
- Handover at the BTS is ongoing for the
capacity greater than zero. Because of
UE to be traced.
this, the BTS cannot select any of these
This alarm indicates that the maximum Transient
number of LNADJ and/or LNADJL
objects was exceeded in the eNB and
that the new object was not stored.
This alarm indicates that a WCDMA Transient
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 Transient
reached. The additional alarm info holds
neighbor relation, which is reported by a
the UTRAN CGI of the reported WCDMA
UE via ANR specific measurements,
cell, which could not be stored in the
could not be stored because the
form of:
maximum number of neighbor relations
This alarm indicates
"A neighbour WCDMA thatcella which
WCDMA is Transient
per cell is already reached. The
neighbor
reported by relation,
an UEwhichdue toisactivated
reported ANR by a
additional alarm info holds the ECGI of
UE because
feature(s) of activated
could not be stored UTRAN ANR
because
the LTE cell and the UTRAN CGI of the
feature:
the maximum number of WCDMA
related WCDMA neighbor cell in the form:
-neighbour
has beencells stored but at least
is reached. WCDMAone of
A handover
"LTE target cell cannot
cell ECGI{ecgiAdjEnbId =be%d,uniquely Transient
LNRELW's
neighbour mobility
cell parameters
information needs be are
selected because
ecgiLcrId several candidates
= %d, ecgiPlmnId = { %d, %d,
(psHoAllowed,
cleaned up srvccAllowed)
manually by the has been
operator
available
%d}} for a certain
, WCDMA cell CGI PCI value %d,
{rncId= and via
set
plantofile
'forbidden',
(WCDMA because
cell CGI the number
{rncId = %d,of
carrier frequency.
CellId= %d, cgiPlmnId = { %d, %d, %d}}".
neighbor
CellId = %d, relations (LNRELW
ecgiPlmnId: MNC= instances)
%s,
The base
exceeds
MCC= station
the
%d})". has executed
maximum number baseband of Start
board
WCDMA (FSP) recovery
neighbor cells,activities.
which might All be
baseband
used by theboards eNB inare available again but
measurement
not all cells could
configurations beinrestored.
(limit 3GPP 36.331 To restore
the functionality of the remaining cell, a
(32)).
The EARFCN of an LTE neighbor cell is Transient
base
The station reset
additional alarm is required.
info holds to thethe
a mapped EARFCN according
ARFCN of the affected carrier
MFBI-profile configuration (that is, the frequency
as well as theforLNCEL
requirement and LNRELW
a homogeneous MFBI
instance number in
configuration is violated). the form of:
This fault WCDMA
"Affected occurs when ARFCN CGI carrier = %d, Transient
As a consequence, HO to this neighbor
measurements
LTE cell indicate that two
ECGI{ecgiAdjEnbId = %d, or more
cell is not possible and call drop rate
cells that operate
ecgiLcrId on the same frequency
might increase if there is no other %d,
= %d, ecgiPlmnId = { %d,
use
%d}} the same PCI.
, WCDMA celltarget.
CGI {rncId= %d,
suitable handover If the UE-based
CellId=
ANR is activated and the X2 link is %d}}"
This %d,
fault cgiPlmnId
indicates that = {
the %d, %d,
absolute Start / Cancel
phase error
available, of the
there willBTS exceeds the
be continuous limit
retries
of
to 5 us, and
resolve thefeatures
ECGI. depending on that
accuracy have been deactivated. This
can occur when:
This fault occurs when CGI Transient
measurements indicate that two or more
1) The absolute value of estimated phase
WCDMA cells
error of the BTS has exceeded the limit
that operate on the same carrier
of 5us,
frequency use the same primary
An inconsistency has been detected Start / Cancel
scrambling code (PSC).
between
OR cluster members, which
prevents the inter-eNB CA feature from
being
2) Theenabled.
BTS has been in holdover mode
for more than 6 hours,
SW incompatibility has which means that Start / Cancel
been detected
estimated phase error value
between cluster members preventing might notthebe
credible. It is assumed in this case
inter-eNB CA feature from being enabled. that
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 eNB Carrier
This fault is reported when the BTS 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 are
This fault is reported when the BTS Start / Cancel
equal to or above the configured value
detects that the number of neighbor
maxNumAnrMoiAllowed in LNBTS.
related objects (which represents the
neighboring BTS, its cells with the
relationship objects) in its database is
BTS has detected carrier aggregation Start / Cancel
equal to or above an internal threshold
relation misconfiguration. One or more of
based on the configured value
the configured carrier aggregation
maxNumAnrMoiAllowed in LNBTS.
relation(s) points towards a cell that does
not exist in any of the BTSs within the
Resource DSPs pool configuration failed Start
configured carrier aggregation cluster.
between C-Plane and U-plane.

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 is no X2 connectivity, the adjacent
There is no X2 connectivity to an Start / Cancel
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 of times.
S1 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
S1 connectivity, MME has failed, etc.
The S1 eNB configuration update Transient
procedure has failed.

The MME could not be informed about


the modification of at least one of the
A RIM request to the serving BSS has Start / Cancel
following eNB configuration data:
failed after several attempts. This means
- eNB Name
that System Information for the related
- Supported TAs (TAC, PLMN Identities)
GERAN or UTRAN neighbor cells is not
- Default paging DRX
reliable.
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 to all configured MMEs are
times within three hours.
active, but the routing of RIM PDU to the
RIM-enabled WCDMA neighbor cell is
Non-correctable
not available. bit toggling error is Start
detected in the critical DSP memory.

Fatal error of DSP HWAPI SW has Start


occured.

If FSP in the BTS generates this fault,


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

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, etc.
There is no M3 connectivity to an 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 Start / Cancel
share is less than the required MBMS
subframe pattern share, which is
configured with the MBSFN parameter
subfrPShareRequired.
At least one suspended MBMS session Transient
cannot be resumed because of
insufficient MBMS resources.

MCE configuration update has finally Transient


failed.

The MME could not be informed about


the modification of at least one of the
The alarm is raised if the monitored Start / Cancel
following MCE configuration data:
service is unavailable when e.g. all
- global MCE ID
network paths are unavailable. This
- MCE name
implies that all individual BFD sessions of
- supported MBMS service area identities
the respective group 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
signal are suppressed.
This alarm 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 an Ethernet interface the physical
A
end deadis not peer was detected
configured to be in a one
framed of the
E1 Start / Cancel
Ethernet link is detected to be down. All
IPsec
interface. associations of the SBTS.
other transmission alarms related to this
There
Note: The is nounit response
and interface to the requests
variables
signal are suppressed.
sent
($U,$IF) to the willpeer, either during
be replaced the IKE
by appropriate
SA
hardware. setup, the IPsec SA
Example: setup, or
unit-FTIF, during
interface
This
Probable alarmcauses is raised forifEthernet
a loopback has
interfaces: Start / Cancel
DPD.
EIF1.
-been configured
a cable/fiber by aormanagement
is cut there is no
application
cable/fiber connected on the interface to thementioned
interface in
Note: When IPsec backup tunnel feature
the
- thealarm text.
electrical/optical signal is
is enabled, this alarm is not raised
excessively
The small attenuatedpluggable (SFP)
form-factor Start / Cancel
due to failures when trying to setup
Note:
-module the port Theatunit the and interfacefar
connected variables
end node
primary is not
IPsec supported,
tunnel in is expected but
($U,$IF)
is switched willoffbe replaced by appropriate
not present, or could not be recognized.
"Secondary_Active_Probing_Primary"
hardware.
-The the advertized Example: technologyunit-FTIF, interface
capabilities
state.small form-factor pluggable (SFP)
EIF1.
with
module detected in the SFP slot doesatnot
auto-negotiation of both devices
This
the fault is raised
Ethernet linkSFP doif not
the match
SBTS cannot Start / Cancel
comply with the module types
update
-supported the Ethernet the Certificate
technology Revocation
at both devicesList
by the BTS element.
(CRL).
at the Ethernet link is forced manual and
The
not failure reasons include the following:
compatible
Probable causes:
- The the LDAP binding
remote peer fails.
of inserted
anaEthernet linkSFP-
is
The
- No SFP SFP has
module reported is transmission
at the Start / Cancel
-not The LDAP search iscapable
auto-negotiation empty (no or CRLauto-
has
fault
based condition
SFP slot. and has disabled the laser
found)/
negotiation The function
LDAP search disabled contains more
transmitter.
- The SFP module's interface by contacts
than
configuration one entry.
are corroded or dirty, preventing either
- The CRL signature validation fails.
Probable
read access causes:
This
-Probable Thealarm CRLcauses isto
file
the SFP
raised
exceedsforwhenPDH
module
the at the
measured
theinterfaces:
BTS storage Start / Cancel
-time TheofSFP readingis defective.
compliance data from the
bit
limit.
-SFP a error
cable rate
is exceeds
cut or there theis threshold
no cable value
of BER-3or preventing detection of module.
-connected
The BTS(10E-3).
certificate
to the interface is part of the CRL.
- The SFP module type is not supported.
- DNS the resolution
electrical for the
signal CRL distribution
is excessively
Note: The unit and interface variables
Probable
point
attenuated fails. causes:
This
($U,$IF)
Note: loss
The ofunit
will multiframe
beand replaced alarm
interface is raised if
by appropriate
variables Start / Cancel
- the signal port at level
the is too low (connectors
connected far end node or
the
hardware.
($U,$IF) interface referenced
Example:
willdirty,
be replaced in
unit-FSM, the alarm
interfacetext
cables
is switched are off electricalby appropriate
connectors or
has
EIF1.
hardware. lost theExample: multiframe alignment.
unit-FSM, interface
-cables
EIF1. transmit areand corroded)
receive cables are mixed
-up the specified maximum length of the
Probable cause: The interface type has
This
cablealarm is exceededis raised when an alarm Start / Cancel
not been configured to meet the framing
indication
-Note:the connector signal isisnotreceived.
properly This signal
connected
of the interfaceand
The unit at the interface
far end.variables
For E1
is
to generated
the unitwill be
($U,$IF) by replaced
an intermediate by PDH
appropriate
interfaces, the configuration of the far-
device
-hardware.
the receiver in the forward
or the far
Example: direction because
interface it
end transmitter
unit-FTIF,
end node should be E1 Multiframe.
detects
has
EIF1. failed a problem in its received signal.
This alarm is raised when a remote Start / Cancel
-defect
the accumulated
indication BER
is interface of the
received. variablesend
It is sent to end
by
Note: The unit and
AIS
E1 defect
path is is detected
too high. when the incoming
the intermediate
($U,$IF) or the farbyend
will be replaced equipment
appropriate
signal has two or less zeros in each of
because
hardware.it Example: detects a unit-FTIF, serious fault in the
interface
two
Note: consecutive
Thesignal.
unit and doubleinterfaceframe periods
variables
received
EIF1.
Module
(512
($U,$IF) bits) iswill
missing.
according
be replaced The SBTS
[G.775] is
chapters
by appropriate 5.2 Active / Cleared
expecting
and I.2. aExample:
hardware. transportunit-FTIF,module, but it has
interface
not
EIF1. been detected.
Probable causes:
All other transmission alarms related to
Probable cause: The far end has a LOS,
-this
thesignal
module areissuppressed.
not present.
LOF or AIS alarm on its receiving
- the module is broken.
interface.
Note: Thecause:
Probable variable $U isisreplaced
There by
a transmission
Note: The unit and interface variables
appropriate hardware.inThe
problem somewhere the actual value is
intermediate
($U,$IF) will be replaced by appropriate
FTIF.
network along the E1 path and AIS is
hardware. Example: unit-FTIF, interface
sent instead of user traffic.
EIF1.
Note: The unit and interface variables
($U,$IF) will be replaced by appropriate
hardware. Example: unit-FTIF, interface
EIF1.
This alarm is raised when the Start / Cancel
localIPAddress negotiation with the peer
fails.

This alarm is raised if local and peer Start / Cancel


ends disagree on the LCP configuration
leading to LCP negotiation failure.

The related configuration parameters are


This alarm is raised if the PPP interface Start / Cancel
: acfcTarget, localMruTarget, pfcTarget.
is 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 is not available.
A requested certificate could not be Start / Cancel
retrieved from the certificate authority
(CA).
A requested certificate could not be
renewed from the certificate authority
The alarm is raised if the BFD state for Start / Cancel
(CA).
the session is not AdminDown and
nevertheless no BFD packet is received
A requested certificate could not be
at the local end during the detection time.
retrieved as the number of certificates
The alarmfrom
received is raised if the server
repository BFD state
(RA)ofor Start / Cancel
The alarm is raised if the BFD session is
the session
certificate is not AdminDown
authority (CA) are moreandthan
the
in activated state.
BFD packet from the far end contains the
expected.
diagnostic code = 'Control Detection
Time Expired' and no BFD down Ingress
This alarm indicates that there is a Start / Cancel
alarm is present.
mismatch between SBTS expected auto-
negotiation result and actual auto-
negotiation result.
The RTT threshold alarm is raised in Start / Cancel
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 took place. A link speed
period equals or exceeds the configured
downshift takes place when auto-
threshold.
The alarm issuccessfully
negotiation raised if thenegotiates
packet lossa Start / Cancel
ratio equals
certain or exceeds
technology but the thelink
configured
cannot be
threshold
established value
withduring the currentIt is tried
this technology.
observation
then to establishintervaltheof 15with
link minutes.
the next
lower speed technology.
This fault is raised when the Vendor BTS Start / Cancel
An Ethernet
certificate link was
is about to established
expire. with
1000Base-T technology, but
The period of notification in advance is the
negotiated
configurableclock frommode
1 daydoes not days
to 4999 fit to the
expected clock
with default 90 days. mode of synchronous
NE stores trust anchors for its own trust
Ethernet. Start / Cancel
chain and for peers. When own or any
trust anchors are
The expected clockabout
mode to of
expire/expired
this alarm is sent.
synchronous Ethernet is slave in case an
Ethernet
This alarm interface
is raisedis ifentered
at leastas sync
one of the Start / Cancel
source to the SBTS synchronization
PPP-links belonging to the ML-PPP
priority
interfacelist.
is Only applicable to 1000Base-
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.
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.
- The SBTS does not receive a reply from
During the IP address configuration the Start / Cancel
ToP Master within a certain time (5 sec)
SBTS tests the direct attached network
which it has sent a sync request
whether, other already configured node,
message.
on the network uses already same IPv6
- The SBTS receives granted message
addresses on their network IP interfaces.
SW
ratesdoes
fromnot
ToPsupport
Masterthe detected
(sync message HW Active / Cleared
The DAD (Duplicate address detection)
type.
rate, delay message rate), that does not
detects those duplicated IPv6 addresses
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
the corresponding IPsecaddress
emergency
and the Start / Cancel
- The system module's SW version is too
bypass
interfaceactive statethe
on which where configured
address was
old to detect the HW variant.
IPsec policies
configured. Forare ignored
each DAD and allatraffic is
event
- Supported HW variant is not present in
sent 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 the traffic capturing is happening
has been locked.
towards a local port, the port and
The number of failed login attempts for a
destination MAC address needs to be
SBTS local operator account has
provided.
exceeded the threshold and the account
This alarm will
Port values canbebetriggered
LMP or <whenHW the Start / Cancel
has been locked on the SBTS. No further
primary
MODULE IPsec
NAME tunnel fails and
>-<PORT SBTS has
ID>.
logins will be permitted from this account
switched over to secondary IPsec tunnel.
until the account is unlocked.
As a resultLMP
Example: of failure of the primary
or FSM-EIF1, IPsec
FSM-EIF2
tunnel,
or SBTS has automatically switched
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 a
sends or receives following notification as
failure notification as response to an
response to an IKE_AUTH or
IKE_SA_INIT request message. The
CREATE_CHILD_SA request message.
failure notifications includes:
The failure notifications includes the
- NO_PROPOSAL_CHOSEN
following:
- INVALID_SYNTAX
- NO_PROPOSAL_CHOSEN
- INVALID_MAJOR VERSION
- TS_UNACCEPTABLE
- INVALID _IKE_SPI
- INVALID_SYNTAX
- INVALID_MESSAGE_ID
- INVALID_MAJOR VERSION
A request to retrieve the public IP Start / Cancel
address information of the FCM/FCT
from the FTM has failed.

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
Five consecutive failed login attempts to Transient
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 Out of order (DSP failure on every


FSP)

Degraded (at least one working


FSP)
Degraded

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

Out of order

Working

Working

Working

Working

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 (there is no other


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

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

Out of order,Working Out-of-order during Radio Module


start-up
Working during Radio Module
runtime
Degraded

Degraded
Out of order

Out of order

Degraded

Degraded

Working

Degraded,Out of order 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

Degraded,Out of order [AAS]: Degraded if less than half


of ActiveElements faulty.
[Otherwise]: Out of order.

Degraded,Out of order Degraded - validated temperature


of any PA or Pipe sensor is >=
Tdanger (when any TX/RX
resources are available on
alarming FRM)
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 (there is no other


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

N/A

Degraded

Working

Working

Out of order

Out of order

Degraded
Out of order

Working

Degraded

Degraded,Out of order Not all fans have failed: alarming


fan = out of order, fan group =
degraded
All fans have failed: all fans and
fan group = out of order
Degraded Alarming fan = degraded, fan
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

Degraded,Out of order Status "degraded" is used for


failure during BTS runtime
Status "out of order" is used for
failure during BTS startup.
Degraded,Working Degraded (there is no other
available and usable input
reference source to be
selected)
Working (SBTS is synchronized
Out of order
with another input reference
source)

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)

Working (SBTS is synchronized


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

Working (SBTS is synchronized


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

Working (SBTS is synchronized


Working
with another input reference
source)
Working

Degraded

Working

Out of order

Degraded

Working

Working

Degraded

Degraded

Working

Working

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

Degraded

Degraded

Working

Out of order

Out of order

Out of order

Working

Out of order

Working

Degraded
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

Degraded,Out of order Unit status is Degraded if at least


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

Degraded
Degraded

Working

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 in normal circumstances.
The module in 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
to filteristhe
notinstabilities
operational.of the reference 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM
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
BTS is Zone:
out of order.
This fault does not immediately affect the
operations of the Flexi Zone Access Point,
WCDMA
but it is a SW does notthat
notification work.
the Flexi Zone 7107 BASE STATION CONNECTIVITY PROBLEM
Access Point master clock frequency
deviates from the used reference frequency
more than in normal circumstances.
The
The Flexi
RNC ZoneNBAPAccess Point
starts link master clock
re-establishment 7107 BASE STATION CONNECTIVITY PROBLEM
tuning
procedures and keeps on tryingalarm,
continues in spite of the until itbut
because the Flexi Zone Access
either succeeds or when the link is Point
master
removed. clock adjustment is quite slow to
filter the instabilities of the reference clock
The resources
interface, provided by the unit several
cannot 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
Signaling itand takes some
calls made time (even
through the
be used,
hours) whichthe
before means
Flexi that
Zone some features
Access Point
related cell(s) do not work.
might not work.
operations start to be affected.

Requested SW version cannot be installed 7106 SINGLE RAN BASE STATION PROBLEM
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 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
software.

If the SW download for any HW unit has 7106 SINGLE RAN BASE STATION PROBLEM
failed, the SBTS continues to operate with
the currently installed SW version.

If the SW activation has failed for FCT in the


If the SW download for any HW unit has 7106 SINGLE RAN BASE STATION PROBLEM
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 activation fails for other HW units,
If the SW activation has failed for FCT in the
The battery backup
(for example, a Radio unit is partlythen
Module) or the 7100 HARDWARE PROBLEM7995 MAINS BREAKDOWN WITH BATTERY BAC
master FSM, the SBTS continues to operate
completely
SBTS restarts in use.
and The intelligent
operates shutdown
with the new
with the currently installed SW version.
operation
SW version. hasIf started.
the SBTS If the mains power
is integrated to is
not restored
NetAct cells, sectors
after the automatic and carriers
recovery SW
If the SW activation fails for other HW units,
are shutthe
update, downSBTSaccording
restarts to the operates
predefined
The cell shutdown
(for example, starts
a Radio asand
Module) a part
thenofthe
the 7104 CELL SERVICE PROBLEM
parameters.
with the previously installed SW version.
intelligent
SBTS shutdown
restarts procedure.
and operates with the new
SW version. If the SBTS is integrated to
NetAct after the automatic recovery SW
update,
The cell the SBTS restarts
shutdown starts asand operates
a part of the 7104 CELL SERVICE PROBLEM
with
intelligent shutdown procedure. version.
the previously installed SW

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). Alarm-
sending to the SBTS Element Manager is
always enabled. The alarm cancellations
The SBTS does not send any 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 calls cannot be established through
Network Management System (NMS).
the blocked unit or module.
Alarm-sending to the SBTS Element
The SBTS does not send 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
transferred to possible to use
another cell. Newthephone
faulty calls 7100 HARDWARE PROBLEM
All cells are disabled.
WSP
cannotorbe FSP in the configuration,
established through thethe BTS
blocked
capacity
cell. decreases or the BTS gets faulty.

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.
The SBTS capacity is decreased or SBTS 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 data from the Radio Module
The affected FCT unit is not 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 Module become faulty.
The affected FCT unit is 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 become faulty.
The affected FCT unit is 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 become faulty.
Handing traffic over to another cell might not 7107 BASE STATION CONNECTIVITY PROBLEM
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 partially reserved minimum capacity
Cell capacity is decreased. 7104 CELL SERVICE PROBLEM
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 working or the BTS is not operational.
BTS HSUPA Capability is degraded in the 7105 RAT BASE STATION PROBLEM
cell where the Parallel Interference
Cancellation (PIC) feature is active.

BTS HSUPA Capability is degraded in the 7105 RAT BASE STATION PROBLEM
cell, where the Parallel Interference
Cancellation (PIC) feature is active.

Depending on the reported severity, the 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM
WCDMA RAT capacity might decrease or
the WCDMA RAT might go completely out of
order.
Malfunctioning cell setups or rejected new 7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM
PIC pool configurations are ignored by
TCOM.

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

FSP is not operational. 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM

The cell is temporarily degraded and all 7104 CELL SERVICE PROBLEM
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 7104 CELL SERVICE PROBLEM
setup the cell with the requested
parameters.
The BTS memory operations including 7100 HARDWARE PROBLEM
software downloads and parameter
updates, are unstable.

The BTS memory operations including 7100 HARDWARE PROBLEM


software downloads and parameter
updates, are unstable.

The BTS memory operations including 7100 HARDWARE PROBLEM


software downloads and parameter
updates, are unstable.

The BTS memory operations including 7100 HARDWARE PROBLEM


software downloads and parameter
updates, are unstable.

The BTS memory operations including 7100 HARDWARE PROBLEM


software downloads and parameter
updates, are unstable.

The BTS capacity decreases or the BTS 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM7106 SINGL
goes out of order. The Digital Signal
Processing (DSP) is not working correctly.

If this fault is cancelled in 4 seconds or less 7105 RAT BASE STATION PROBLEM7106 SINGLE RAN BASE STATION PROB
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
is permanently on the EAC line is
decreased. 7103 EXTERNAL ALARM NOTIFICATION
alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.
Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION
alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.
Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION
alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Device configured on the EAC line is 7103 EXTERNAL ALARM NOTIFICATION


alarming.

Some operations in the BTS are being 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC
interrupted. Depending on the fault source,
the BTS or cell operation is degraded or
faulty.
The BTS capacity possibly decreases. 7104 CELL SERVICE PROBLEM
Processing resources, cells, or the whole 7106 SINGLE RAN BASE STATION PROBLEM
BTS might be out of order.

7100 HARDWARE PROBLEM

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 but the network performance
The BTS can operate 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 follow the synchronization
The BTS is not operational. 7108 BASE STATION SYNCHRONIZATION PROBLEM
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 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
degraded. The cell size
Effects in Frequency might be reduced
Synchronization mode:
(7104
Assuming CELL SERVICE
that the BTSPROBLEM).
reference signal has
-correct
No impact
accuracyon system
when (7100
the DAC HARDWARE
value
PROBLEM).
reaches the adjustment limit 0 or 4095 is
- The MHA is faulty, the RX performance 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
(meaning the alarm indication
degraded. The cell size might is real, not
caused by incorrect reference),
be reduced (7104 CELL SERVICE the BTS air
interface
PROBLEM). starts to drift from the correct value
and
- No after
impacta while
on the (weeks
system or(7100
months) the
The
3GPP antenna
accuracy linelimit
is not
is operating
not met correctly.
any more. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
HARDWARE PROBLEM).
Cell
Evencapacity is decreased.
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 7104 CELL SERVICE PROBLEM
resources are affected, or the cell operation
Effects in Phase
is degraded Synchronization
if a part mode:
of the cell's resources
When the DAC value reaches the
is affected, but the cell still has critical
adjustment
resources that limitare
0 or 4095, the basic LTE
working.
The
systemoutput power effects
operation of the antenna is
are the same as in 7104 CELL SERVICE PROBLEM
decreased
Frequency and the antenna mode
Synchronization is not working
but the
Downlink signal transmission on the given
at
LTEthefeature(s)
optimumwhich level. require Phase
antenna line is disabled, and the
Synchronization
corresponding Radio become(s)
Modulenon-operational
transmitter is
because
The RX path
unusable. the OCXO cannot
operating
Hence, the adjust
Radiothe
performance
overall isphase 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
Module
synchronization
state is affected.any more.
decreased.

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. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM

The BTS capacity possibly decreases. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM

The BTS capacity possibly decreases. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM

The BTS capacity possibly decreases. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM

The BTS capacity possibly decreases. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM

The antenna line device is not working 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
properly. The cell operation is degraded.

The device is out of use. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM

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 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC
is FSP.
BTS capacity decreased if fault source is
FBB.
The MHA gain is decreased. The cell 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
performance may be decreased.

The MHA gain is decreased or there might 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
even be a loss. The cell performance
is decreased.
Some antenna line device functions might 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
not work properly.

Some antenna line device functions might 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
not work properly.

Some antenna line device functions might 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
not work properly.

Some antenna line device functions might 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
not work properly.

Default values for the internal delays in the 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM
BB card are used.
Effects on functionality:
1) Cell boundaries cannot be defined as
accurately as with measured internal delay
If other references are available, the 7108 BASE STATION SYNCHRONIZATION PROBLEM
values.
synchronization reference source changes
2) 3GPP Dedicated measurement (RTT
to another source. Tuning then follows this
measurement) accuracy is lower than with
new reference.
measured internal delay values.
If other references are available, the 7108 BASE STATION SYNCHRONIZATION PROBLEM
If other references are not available, the
synchronization reference source 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 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA
If other references are not available, the
cell(s) or calls are possible but the cell
BTS master clock (OCXO) tuning is halted
capacity and performance might decrease
and the BTS synchronization drops to
(7104 CELL SERVICE PROBLEM).
holdover mode.
Cells not affected (7106 SINGLE RAN
Calls are not possible through the affected 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA
BASE STATION PROBLEM).
cell(s) or calls are possible but the cell
capacity and performance might decrease
(7104 CELL SERVICE PROBLEM).
No impact on the system (7106 SINGLE
The Radio 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 following faults may occur (may be


Calls are not possible through the 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 (7108 BASE STATION
cell(s) or calls are possible but the cell
nceTooHighAl
SYNCHRONIZATION PROBLEM)
capacity and performance might decrease
1924/EFaultId_FrConfigurationFileCorrupte
(7104
d CELL SERVICE PROBLEM).

Calls not affected (7108 BASE STATION


SYNCHRONIZATION PROBLEM)
Calls are not possible through the affected 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA
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 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
Cell(s) not affected (7106 SINGLE RAN
through the affected cell(s).
BASE STATION PROBLEM)

Calls are not possible through the affected 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA
cell(s) or calls are possible but the cell
capacity and performance might decrease.

There might be problems with calls made 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
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 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA
cell(s) or calls are possible but the cell
capacity and performance might decrease
(7104 CELL SERVICE PROBLEM).
No impact on calls (7106 SINGLE RAN
Calls are not possible through the affected 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA
BASE STATION PROBLEM)
cell(s) (if severity is critical).

There can be problems with the calls made


through the affected cell(s) (if severity is
The TX/RX paths of the Radio module are 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC
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 capacity and
There might Rx
the affected be (otherwise).
problems with calls made 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
performance might decrease (if severity is
through the affected cell(s).
major).
No impact on the system (if severity is
minor)
There might be problems with calls made 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
through the affected cell(s).

This fault should cancel itself. 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
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 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
and cause another fault, and there might be
problems with calls made through the
affected cell(s).
The default configuration is used and the 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
No impact on system (if severity is minor).
cell 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 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
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 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7108 BASE STAT
No impact on system (if severity is minor).
module and the Radio Module might be
corrupted.
Calls are not possible through the affected
cell(s) (if severity is critical).
The TX power level is decreased and there 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
Calls are possible but the cell capacity and
might be problems with calls made 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 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
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 7100 HARDWARE PROBLEM
connected/working. This might cause the
RF module to overheat.

The fault can only be automatically


If the fans are 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
modules are nota rotating
reset. as required, there 7100 HARDWARE PROBLEM
is a risk of the module overheating.

If the fans are rotating faster than required, 7100 HARDWARE PROBLEM
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 (7652 BASE STATION
with the affected cells (7654
NOTIFICATION).
CELL OPERATION DEGRADED).
No impact on the system (7652 BASE
STATION NOTIFICATION).
Problems might occur during calls made 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
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 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA
possible through the affected cell(s).

The antenna line is faulty. All cells that use 7104 CELL SERVICE PROBLEM
this antenna line are affected.

Downlink signal transmission on the given


antenna line is disabled, and corresponding
The BTS unit is transmitting or receiving 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
RF transmitter is unusable. Hence, overall
data with degraded performance. The fault
RF state is affected.
does not trigger any actions for BTS.

Radio Modules External Alarm and Control 7100 HARDWARE PROBLEM


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 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC
For the primary link to Extension System
Module, the cell(s) of the RF Module behind
Module, all cells that have been allocated to
the broken connection is/are out of order
BB resources on the Extension FSM are out
and the RF Module cannot be used.
of order and the Extension FSM cannot be
In the case of primary optical link to Radio
used. 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC
For the primary link to Extension System
Module, the cell(s) of the Radio Module
Module, all cells that have been allocated to
behind
For the the broken connection
secondary optical link to arethe
outRadio
of
BB resources on the Extension FSM are out
order
Module andor thethe Radio
Extension Module cannot
System be
Module,
of order and the Extension FSM cannot be
used.
the
Thecells
used. BTSthat are transmitted
capacity decreases.through the
The optical 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7104 CELL SERVIC
antenna carrier or have resources
interface loses synchronization if the allocated
In
viathe case of primary
secondary are link
linkexceeds to Extension
affected. Cells not
number
For of errors
the secondary the to
optical link defined limit.
the Radio
System
affected Module,
by the fault all cells
mightthat
stillhave
be been
Module or the Extension System Module,
allocated
operational. to BB resources on the Extension
the
The cells that aretotransmitted through the
FSMRP3 are outtraffic
of orderthe and
appropriate Radio
the Extension 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7108 BASE STAT
antenna
Module, carrier
Extension or have resources
System Module, or allocated
FSM cannot be used.
via secondary
summing device linkisare affected. Cells
malfunctioning. The not
affected
related by
cell(s) the fault might still be
In the case of (traffic
secondary to the Radiolink
optical Module)
to
operational.
is/are not operational, or theSystem
BTS operation
Radio Module or Extension
Baseband bus RP3 traffic to the RF 7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM7106 SIN
is degraded
Module, (trafficthat
the cells to the
are Extension
transmitted System
Module/Extension System Module, or
Module),
through theor the BTS is
antenna out ofororder(traffic
carrier have to
between the summing and optical devices is
the summing
resources device).
allocated via secondary link are
not working. Depending on the link, either
affected. Cells notoraffected
the BTS capacity cell operation is
Baseband
might bus RP3 traffic to the RF 7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM7106 SIN
degraded.be operational.
still
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
Baseband bus RP3 traffic 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 cell operation is
Baseband bus RP3 traffic 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
There are possibly no immediate effects 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 the BTS operation is
RP3 traffic from the baseband to the 7105 RAT BASE STATION PROBLEM7106 SINGLE RAN BASE STATION PROB
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. 7106 SINGLE RAN BASE STATION PROBLEM

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

The BTS operation is degraded because 7104 CELL SERVICE PROBLEM7105 RAT BASE STATION PROBLEM
some BTS resources are unavailable.
The BTS capacity decreases 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE

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. 7106 SINGLE RAN BASE STATION PROBLEM

sRIO communication with devices on the 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE
impacted port is no longer possible.

The cell might enter "sleeping" mode. 7105 RAT BASE STATION PROBLEM

The SBTS GSM capacity decreases, cell 7104 CELL SERVICE PROBLEM
might become disabled.

The SBTS GSM capacity decreases, cell 7104 CELL SERVICE PROBLEM
might become disabled.

The SBTS GSM capacity decreases, cell 7104 CELL SERVICE PROBLEM
might become disabled.

TRXes which do not fit to profile stay 7105 RAT BASE STATION PROBLEM
disabled.

The SBTS GSM capacity decreases, cell 7104 CELL SERVICE PROBLEM
might become disabled.

TRXes which do not fall into the range 7105 RAT BASE STATION PROBLEM
categories remain disabled.
The SBTS GSM capacity decreases, cell 7104 CELL SERVICE PROBLEM
becomes disabled.

Cell remains as offline. 7104 CELL SERVICE PROBLEM

Available hardware resources are not fully 7106 SINGLE RAN BASE STATION PROBLEM
utilized before resetting the SBTS.

GNSS become unusable. 7108 BASE STATION SYNCHRONIZATION PROBLEM

The BTS resources have decreased or the 7101 RESET NOTIFICATION7108 BASE STATION SYNCHRONIZATION PROB
BTS is faulty.

Depending on the reported alarm, the fault 7100 HARDWARE PROBLEM7101 RESET NOTIFICATION7102 RESOURCE B
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 7104 CELL SERVICE PROBLEM
version and is therefore not compatible with
any other units.

There is no immediate effect on cell 7100 HARDWARE PROBLEM


operation. The device continues operation
with the previously used data.

There is no immediate effect on cell 7100 HARDWARE PROBLEM


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 7106 SINGLE RAN BASE STATION PROBLEM
RP3-01 link are not activated.

The RS485 interface is not operating 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
correctly. The cell capacity decreases.
Commissioned cells are not activated. 7106 SINGLE RAN BASE STATION PROBLEM

Fan control is not optimized. The effect of 7106 SINGLE RAN BASE STATION PROBLEM
noise/temperature level is marginal.

FSP DSPs not in use; SBTS operation is 7104 CELL SERVICE PROBLEM7106 SINGLE RAN BASE STATION PROBLEM
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, 7106 SINGLE RAN BASE STATION PROBLEM
there is a risk that the module temperature
is rising too high.

If the fans are rotating faster than required, 7106 SINGLE RAN BASE STATION PROBLEM
it creates unnecessary noise.

Source unit has inconsistent SW version. 7106 SINGLE RAN BASE STATION PROBLEM

Source unit has inconsistent SW version. 7106 SINGLE RAN BASE STATION PROBLEM

Source unit has inconsistent SW version. 7106 SINGLE RAN BASE STATION PROBLEM

Calls are not possible through affected 7104 CELL SERVICE PROBLEM
cell(s) (if severity is critical).

Calls are possible, but the cell capacity and


performance may be decreased (if severity
The system module is out of order and the 7108 BASE STATION SYNCHRONIZATION PROBLEM
is major).
BTS is out of order.

GNSS become unusable. 7108 BASE STATION SYNCHRONIZATION PROBLEM


GNSS become unusable. 7108 BASE STATION SYNCHRONIZATION PROBLEM

GNSS become unusable. 7108 BASE STATION SYNCHRONIZATION PROBLEM

GNSS become unusable. 7108 BASE STATION SYNCHRONIZATION PROBLEM

GNSS become unusable. 7108 BASE STATION SYNCHRONIZATION PROBLEM

Due to problem detection in Start-up, BTS 7109 BASE STATION SECURITY PROBLEM
remains out of order.

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. 7108 BASE STATION SYNCHRONIZATION PROBLEM

7106 SINGLE RAN BASE STATION PROBLEM

In case of VSWR major or VSWR minor, 7106 SINGLE RAN BASE STATION PROBLEM
value set is out of range during
commissioning. BTSOM sets the nearest
values supported by Radio Module.
Software download has failed and must be 7109 BASE STATION SECURITY PROBLEM
retried.

Software download has failed and must be 7109 BASE STATION SECURITY PROBLEM
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.
Software download has failed and must be 7109 BASE STATION SECURITY PROBLEM
retried.

The MHA does not compensate the signal 7100 HARDWARE PROBLEM7104 CELL SERVICE PROBLEM
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 7108 BASE STATION SYNCHRONIZATION PROBLEM
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
theother
BTSreferences are available,
synchronization drops tothe
holdover 7108 BASE STATION SYNCHRONIZATION PROBLEM
synchronization
mode. reference source changes
If other references are not available, the
to another source. Tuning then follows this
BTS master clock (OCXO) tuning is halted
new reference.
and the BTS synchronization drops to
Micro DTX
holdover functionality (LTE1891) is not
mode. 7100 HARDWARE PROBLEM
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 7104 CELL SERVICE PROBLEM
activated or deactivated in a radio module.

The active base station configuration is not 7106 SINGLE RAN BASE STATION PROBLEM
the same as requested in the configuration
change.

BTS performs switchover to another input 7108 BASE STATION SYNCHRONIZATION PROBLEM
reference clock source if available.

RAT that is indicated in the Source field of 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM
the fault is not operational.

Cell performance is decreased. 7104 CELL SERVICE PROBLEM

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 be
The PHICH transmission power is not 7104 CELL SERVICE PROBLEM
degraded, especially in cases where the U-
boosted enough or at all compared to the
plane overload countermeasures are
operator's setting.
enabled.
"Fault ID Name" information field identifies
Celltype
the operation is downgraded.
of overload detected: 7104 CELL SERVICE PROBLEM
- TrOne refers to trigger UPOVT1: speech
quality based detection on user plane
- TrTwo refers to trigger UPOVT2: quantity
based detection
Cell operation is per TTI on user plane
downgraded. 7104 CELL SERVICE PROBLEM
- 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 be
In case of U-plane overload, the system 7104 CELL SERVICE PROBLEM
degraded, especially in cases where the U-
initiates actions to decrease the amount of
plane overload countermeasures are
load by limiting the traffic or the functionality
enabled.
on traffic.
"Fault ID Name" information field identifies
The system performance might be
For S1: The
the type eNB loses
of overload the connection to S- 7107 BASE STATION CONNECTIVITY PROBLEM
detected:
degraded, especially in cases where the U-
GW.
- TrOneAll calls
refersusing the failed
to trigger GTP-U
UPOVT1: data
speech
plane overload countermeasures are
path
qualityare released,
based and new
detection GTP-U
on user planedata
enabled.
tunnels
- TrTwo are nottocreated
refers trigger for the failed
UPOVT2: GTP-U
quantity
"Fault ID Name" information field identifies
data
basedpath until it works
detection per TTIagain.
on user plane
the type of overload detected:
- TrThree refers to trigger UPOVT3: PDSCH
- TrOne refers to trigger UPOVT1: speech
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 can be set up.
The X2 interface is unavailable. Handover 7107 BASE STATION CONNECTIVITY PROBLEM
of calls to or from cells of the associated
If there is at least one other S1 interface
adjacent BTS is not possible. Base station
available for use, BTS operation is
(BTS) operation is considered degraded.
considered degraded and the BTS can
One of the
continue transport(that
operation paths(SCTP) in SCTP
is, set up calls) 7107 BASE STATION CONNECTIVITY PROBLEM
connection to MME
using available has failed. Only
S1 interface(s).
applicable when SCTP multi-homing is
supported. An alternate transport path is
available to pursue the operation.
M3 interface is unavailable. 7107 BASE STATION CONNECTIVITY PROBLEM

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 transport path is available to
SBTS LTE is not configured according to 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. 7104 CELL SERVICE PROBLEM

The cell is disabled. 7104 CELL SERVICE PROBLEM

[LTE RAT] 7107 BASE STATION CONNECTIVITY PROBLEM


See fault processing diagram:
WCDMA_BTS/BTS_Requirement/LTE
Operability and
Maintenance(LTE_OAM_8455).
SBTS LTE is not operational. 7105 RAT BASE STATION PROBLEM
[Otherwise]
In case of subscriber trace activation, if the
failed trace connection was used for
Trace
sendingsession (forreports,
the trace subscriber/cell/interface)
the SBTS 7105 RAT BASE STATION PROBLEM
cannot
considersbe the
activated/deactivated.
trace activation for that
subscriber as failed.

In
Thecase
BTSofcannot
cell trace and new
accept interface
UEs trace, if 7105 RAT BASE STATION PROBLEM
the
attempting registration in any of used
failed trace connection was for
the reported
sending the trace
misconfigured reports,
PLMNs. Suchthean
SBTS doesby
attempt
not
new UEs results in call failure at the BTS. is
start tracing until the trace connection
established successfully.
The UEs that might have already registered
In case of syslog PLMN(s)
in misconfigured and message
remaintrace, if the
failed connection
unimpacted. was used for sending the
reports, the SBTS does not start streaming
until the connection is established
successfully.
The fault has no effect on the base station 7105 RAT BASE STATION PROBLEM
operation but the LNADJ and/or LNADJL
object was not stored in the eNB.

The fault has no effect on the base station 7105 RAT BASE STATION PROBLEM
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 7105 RAT BASE STATION PROBLEM
operation but LNRELW object with newly-
learnt WCDMA neighbor relation
configuration via ANR specific
measurements was not stored in the eNB.
The fault has no effect on the base station 7105 RAT BASE STATION PROBLEM
operation. The WCDMA neighbor relation,
which is reported by a UE because of
activated ANR feature(s):
1) has not been stored because the actual
No handover can be performed to cells with 7104 CELL SERVICE PROBLEM
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
2) has cellbeen
that stored
cannotbutbe atrecovered
least oneremains
of 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM
unavailable.
LNRELW's mobility paremeters
(psHoAllowed, srvccAllowed) has been set
In
to the case when
'forbidden' BTS itO&M
because has system
exceeded is able
limit
to
in restore36.331
3GPP disabled cell(s)without
(32). (See also Meaning
If an X2 link is available, no type of 7105 RAT BASE STATION PROBLEM
negative
paragraph). impact on other working cell(s)
handover to the neighbor cell is possible at
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
is reported whenfailure rate for the
autonomous affected
baseband 7104 CELL SERVICE PROBLEM
cell mightreset
recovery be increased.
is processed by O&M.
See fault 52:
EFaultId_UnitAutonomousResetAl
description.
The effect depends on the features used by 7108 BASE STATION SYNCHRONIZATION PROBLEM
the operator. The following LTE features are
deactivated (if configured to be used):

- LTE1117 (LTE MBMS)


The handover failure rate for the affected 7104 CELL SERVICE PROBLEM
- LTE1113 (eICIC - macro)
cell might be increased.
- LTE1496 (eICIC - micro)
- LTE2007 (Inter eNB Carrier Aggregation)
- LTE2208 (eICIC extensions-micro)
Cells and eNBs
- LTE2209 (eICICremain in service, but 'Inter 7105 RAT BASE STATION PROBLEM
enhancements)
eNB Carrier(Network
- LTE2554 Aggregation'-related features
Assisted Interference
that require consistent
Cancellation parameters between
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 7107 BASE STATION CONNECTIVITY PROBLEM
features that require an inter-eNB link are
taken out of service.

If the maximum number of allowed neighbor 7105 RAT BASE STATION PROBLEM
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
The eNB continues normal operation and 7105 RAT BASE STATION PROBLEM
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, but no new object
can be created via O&M or via X2 Setup/X2
is created. A result of this might be that no
Configuration Update.
BTS is operational
X2 link is established butwith
system
suchlevel (inter-or
neighbor 7105 RAT BASE STATION PROBLEM
If the number of objects in the database
BTS)
that thecarrier
CGI aggregation
is known for functionality
such BTS. is
increases further and reaches or even
degraded. Carrier aggregation with the
exceeds the configured value
misconfigured
New objects can carrier aggregation
be stored relations
again when the
maxNumAnrMoiAllowed, automatic
is not possible.
number of However,
neighbor relatedcarrier
objects in the
Resource DSPs pool
neighbor relation is unavailable.
functionality is degraded 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM
aggregation
BTS database withis the
belowother, properly
Any
and ancell that cannot
alarm be put
indicating into usedetected:
"Overload due to
configured carrier aggregation relations is
maxNumAnrMoiAllowed.
the
maxlack of available
number resource
of neighbor pools,
relation is also
objects
working normally.
not available.
reached" is raised.
BTS cannot continue operation. All cells are 7101 RESET NOTIFICATION7105 RAT BASE STATION PROBLEM
disabled.
BTS autonomous reset will be performed to
recover if the number of allowed
autonomous BTS resets is not exceeded.
Handovers from or to cells of the related 7107 BASE STATION CONNECTIVITY PROBLEM
adjacent BTS are not possible.

Handovers to cells of the related adjacent 7107 BASE STATION CONNECTIVITY PROBLEM
BTS are not possible.

The S1 interface is not available for call 7107 BASE STATION CONNECTIVITY PROBLEM
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 7104 CELL SERVICE PROBLEM
system information of the cell stored that
has left the cell and has come back within
three hours might not recognize that there
was a system information change.
Critical impact on FSP operation. 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7106 SINGLE RA

The BTS capacity decreases or the BTS is 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE
out of order. The Digital Signal
Processing (DSP) does not work correctly.

The BTS capacity decreases or the BTS is 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE
out of order. The Digital Signal
Processing (DSP) is not working correctly.

The BTS capacity decreases or the BTS is 7101 RESET NOTIFICATION7104 CELL SERVICE PROBLEM7105 RAT BASE
out of order. The Digital Signal
Processing (DSP) is not working correctly.

The M3 interface is unavailable and MBMS 7107 BASE STATION CONNECTIVITY PROBLEM
service can no longer be provided.

The M3 interface is unavailable and MBMS 7107 BASE STATION CONNECTIVITY PROBLEM
service can no longer be provided.

The available resources for MBMS session 7105 RAT BASE STATION PROBLEM
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 7105 RAT BASE STATION PROBLEM
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 61028 LOF on unit $U, interface $IF
this interface:

- no calls are possible


- loss of remote management access to
No data or clock information is exchanged 61029 LOS on unit $U, interface $IF
other network elements
via this interface.
- loss of synchronization if the interface is
used as a synchronization source
Possible impact on the connections over
this interface:
Possible effects: 61030 Dead Peer Detected
- voice calls or data connections are aborted
and cannot be established anymore
- no calls are possible.
- remote management connectivity is lost
- loss of remote management access to
and cannot be established anymore
other network elements.
The
- lossinterface cannot be used
of synchronization if the for
interface is 61040 Interface under test on unit $U, interface $IF for $T minutes
- IKE SAs and IPsec SAs cannot be
transmission. It can be used
used as a synchronization for connectivity
source
established or re-keyed.
checks only. on use of the Ethernet
- Depending
interface the above described impact can
occur for the local
The interface of theSBTSSFP and/or
moduleothercannot be 7100 HARDWARE PROBLEM
(S)BTS elements
used for transmission. if they are chained via the
Ethernet
No data or interface.
clock information is exchanged
via this interface of SFP module.
The SFP module's laser cannot be switched
The Certificate Revocation List could not be 7109 BASE STATION SECURITY PROBLEM
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
module not operational.
or incompatible. 7100 HARDWARE PROBLEM

The
Possible interface of the
impact SFP
on the module cannot
connections over be
used for transmission.
this interface of SFP module:
The
-Possible SFP
voice module's
calls or datalaser can't be cannot
connections switched be
impact: 61104 EBER on unit $U, interface $IF
on.
established.
- slow management access to the SBTS
-and remote
othermanagement connectivity
network elements cannot
in the network
No
be data or clock information is exchanged
established.
- poor voice quality and data performance
via
- lossthisofinterface of SFP module.
synchronization if the interface is
The
usedperformance management
as a synchronization sourcedata 61150 LOMF on unit $U, interface $IF
collected
Possible impacton this on
interface becomes invalid.
the connections over
this interface of SFP module:
- voice calls or data connections cannot be
established.
Possible impact on the connections over the 61151 AIS on unit $U, interface $IF
-interface
remote management
in question: connectivity cannot
be established.
- no calls are possible
-- loss
loss of
of synchronization
remote management if the access
interface
to is
used as a synchronization
other network elements in the RANsource
Possible impact on the connections over 61152 RDI on unit $U, interface $IF
this interface:

- no calls are possible


- loss of remote management access to
Possible impact: 7100 HARDWARE PROBLEM
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 61250 IPCP Failure
this interface:
- the SL-PPP/ML-PPP interface is not
available.
- loss of remote management access.
Possible impact on the connections over 61251 LCP Failure on Interface $IF
this interface:
- no calls are possible anymore
- loss of remote management access to
other network elements in the RAN
Impact on the connections over this 61252 PPP Interface down
interface:

- loss of remote management access.


The requested service is not available. 7109 BASE STATION SECURITY PROBLEM

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 61607 Auto-negotiation mismatch, on unit $U, Ethernet interface $IF
unexpected clock mode or technology.

Possible impact on the connections over


this interface:
This alarm is an indication that the backhaul 61610 TWAMP RTT threshold crossed
- Increased packet delay variation and
capacity for traffic with the same profile as
increased average delay for all voice/packet
this TWAMP session (DSCP value, packet
and management connection
size) may be too small, because the
- Increase of packet loss due to congestion.
measurement packets are scheduled later
This
- Lossalarm is an indication that the
of synchronization/Timing backhaul
source lost 61611 TWAMP PLR threshold crossed
than before.
capacity
with Timingfor over
trafficPacket
with same profile as this
(IEEE1588v2) due
TWAMP session
to increased packet(DSCP
delayvalue, packet size),
variation.
may
- Lossbeofmuch too small, becausesource
synchronization/Timing some oflost
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 61622 MLPPP link Degrade


reduced capacity.
SyncE is no longer a working 7108 BASE STATION SYNCHRONIZATION PROBLEM
synchronization source.

SyncE is no longer a working 7108 BASE STATION SYNCHRONIZATION PROBLEM


synchronization source.

BTS performs switchover to another ToP 7108 BASE STATION SYNCHRONIZATION PROBLEM
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 allows the local peer to continue
- No calls are possible for the connections
functioning without disruption, but
over this HW.
completely breaks IP base communications
All
for configured IPsec
the connected policies are ignored
network. 61639 IPsec emergency bypass active
and all the SBTS traffic is sent unprotected.

The resulting packet capture files can used 61641 IP Traffic Capturing Ongoing [port $port,] [mac $m]
for Expert analysis to identify network
problems and to help determine the best
course of action.
No further logins will be permitted for that 7109 BASE STATION SECURITY PROBLEM
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 61645 IKE SA failure


subsequently no IPsec SAs can be
established.

The related IPsec SA can't be established 61646 IPSec SA failure


and used.
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 7102 RESOURCE BLOCKED BY USER
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 7108 BASE STATION SYNCHRONIZATION PROBLEM
No impact on system (if severity is minor).
rfsharing is enabled, start-up is stopped.
Otherwise, start-up is continued without a
The BTS does not send faults related to the
reference clock, but the BTS is not directed
blocked Flexi Radio module (FR) to the
to OnAir.
None management system (NMS). Fault 7109 BASE STATION SECURITY PROBLEM
network
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 RESET NOTIFICATION (FBB (in case of fault
7105 RAT BASE STATION PROBLEM (for fault source
4052 raised during FBB hot removal scenario)
RAT)
7104 CELL SERVICE PROBLEM (in case of FSP or
7101 RESET NOTIFICATION (raised only if RESET
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
operational), always has impact on cell))
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


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 CELL SERVICE PROBLEM (the fault source is
7101 RESET NOTIFICATION (when reset is being
FR)
performed)
7105 RAT BASE STATION PROBLEM (the fault source
is FSP or DSP)
When reset has not been triggered for any reason:
7104 CELL SERVICE PROBLEM (the fault source is
7101 RESET NOTIFICATION (when reset is being
FR)
performed)
7105 RAT BASE STATION PROBLEM (the fault source
is FSP or DSP)
When reset 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 RAT BASE STATION PROBLEM (DSP supporting
7105 RAT BASE STATION PROBLEM (DSP supporting
RAT resources)
RAT resources)
7106 SINGLE RAN BASE STATION PROBLEM (DSP
7106 SINGLE RAN BASE STATION PROBLEM (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 CELL SERVICE PROBLEM (in case of FSP or
7100 HARDWARE PROBLEM (failure has no impact on
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 CELL SERVICE PROBLEM (cells affected)
7101 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 CELL SERVICE PROBLEM (cell(s) affected)
7104 CELL SERVICE PROBLEM (cell(s) affected)
7106 SINGLE RAN BASE STATION PROBLEM (cell(s)
7106 SINGLE RAN BASE STATION PROBLEM (cell(s)
not affected)
not affected)

7101 RESET NOTIFICATION (when reset is being


performed)

When reset has not been triggered for any reason:


7104 CELL SERVICE PROBLEM (cell(s) affected)
7101 RESET NOTIFICATION (when reset 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 CELL SERVICE PROBLEM (cells affected)
7100 HARDWARE PROBLEM (cell(s) not 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 CELL SERVICE PROBLEM (cell(s) affected)
7104 CELL SERVICE PROBLEM (cell(s) affected)
7106 SINGLE RAN BASE STATION PROBLEM (cell(s)
7106 SINGLE RAN BASE STATION PROBLEM (cell(s)
not affected)
not affected)

7101 RESET NOTIFICATION (when reset is being


performed)

When reset has not been triggered for any reason:


7104 CELL SERVICE PROBLEM (cells affected)
7101 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 CELL SERVICE PROBLEM (cell(s) affected)
7101 RESET NOTIFICATION (when reset is being
7106 SINGLE RAN BASE STATION PROBLEM (cell(s)
performed)
not affected)
When reset has not been triggered for any reason:
7104 CELL SERVICE PROBLEM (cell(s) affected)
7104 CELL SERVICE PROBLEM (cell(s) affected)
7100 HARDWARE PROBLEM (cell(s) not affected)
7100 HARDWARE PROBLEM (cell(s) not 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 CELL SERVICE PROBLEM (cells affected)
7104 CELL SERVICE PROBLEM (cells 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 TRX FAULTY


7104 CELL SERVICE PROBLEM
This alarm is used when fault indicates failure of TRX.
This alarm is used when fault indicates impact to cell
operation.
7607 TRX OPERATION DEGRADED [AAS only if less
than half of ActiveElements are faulty. Otherwise 7606
7606 TRX FAULTY (when condition occurs longer than
7106 SINGLE RAN BASE STATION PROBLEM (cell
TRX FAULTY]
tT+danger.)
not
Thisaffected)
alarm is used when fault indicates degradation in
This alarm is used when fault indicates failure of TRX.
7104 CELL SERVICE 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 CELL SERVICE PROBLEM (if fault is reported to
7101 RESET NOTIFICATION (when reset is being
optical link connected to Radio Module)
performed)
7100 HARDWARE PROBLEM (if fault is reported to
optical link not connected to Radio Module)
When reset has not been triggered for any reason:
7104 CELL SERVICE PROBLEM (if fault is reported to
7101 RESET NOTIFICATION (when reset is being
optical link connected to Radio Module)
performed)
7100 HARDWARE PROBLEM (if fault is reported to
optical link not connected to Radio Module)
When reset has not been triggered for any reason:
7104 CELL SERVICE PROBLEM (if fault is reported to
7101 RESET NOTIFICATION (when reset is being
optical link connected to
performed)
FRM)
7100 HARDWARE PROBLEM (if fault is reported to
When reset has not been triggered for any reason:
optical link not
7104 CELL SERVICE PROBLEM (if fault is reported to
7101 RESET
connected NOTIFICATION (when reset is being
to FRM)
optical link connected to
performed)
Radio Module)
7100 HARDWARE PROBLEM (if fault is reported to
When reset has not been triggered for any reason:
optical link not
7104 CELL SERVICE PROBLEM (if fault is reported to
7104 CELLtoSERVICE
connected PROBLEM (for fault source OptIf
Radio Module)
optical link connected to
towards Radio Module)
Radio Module)
7105 RAT BASE STATION PROBLEM (for fault source
7108 BASE STATION SYNCHRONIZATION PROBLEM
FSP/FBB serving RAT)
(if fault is reported to optical link not
7106 SINGLE RAN BASE STATION PROBLEM (for
7104 CELLtoSERVICE
connected PROBLEM (for fault source OptIf
Radio Module)
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
7104 CELL SERVICE PROBLEM (for 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 SINGLE RAN BASE STATION PROBLEM (for
7104 CELL SERVICE PROBLEM (for 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 CELL SERVICE PROBLEM (for LTE)
7104 CELL SERVICE PROBLEM (for LTE)
7105 RAT BASE STATION PROBLEM (otherwise)
7105 RAT BASE STATION PROBLEM (otherwise)
7101 RESET NOTIFICATION (when reset is being
performed)

When reset has not been triggered for any reason:


7104 CELL SERVICE PROBLEM (for LTE)
7101 RESET NOTIFICATION (when reset is being
7105 RAT BASE STATION PROBLEM (otherwise)
performed)

When reset has not been triggered for any reason:


7104 CELL SERVICE PROBLEM (for LTE)
7101 RESET NOTIFICATION (when reset is being
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
is toggling PROBLEM (failure has no impact on
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
7100this alarm is toggling
HARDWARE PROBLEM in the(failure
BTS) has no impact on
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
7109 HARDWARE
BASE STATION PROBLEM
SECURITY (in case of FSP(Fault
PROBLEM or FBB if
cells are alarm
with this not impacted, FR(there
is toggling is enough critical cell
in the BTS)
resources
7110 BASEleft for the cell
STATION to remain
LICENCE operational),
LIMITATION ESM,
(Fault with
FT,
this ALD(failure has noinimpact
alarm is toggling the BTS)on cell))
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
operational), PROBLEM
ALD(failure (failure
has impact onhas no impact on
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.

Base station synchronization problem.

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 SINGLE RAN BASE STATION PROBLEM (when
7101 RESET NOTIFICATION (when reset is being
reset has not been triggered for any reason)
performed)

When reset has not been triggered for any reason:


7104 CELL SERVICE PROBLEM (LTE, in case of
7101 RESET NOTIFICATION (when reset is being
WDCMA if all cells are affected)
performed)
7105 RAT BASE STATION PROBLEM (WCDMA if one
or more cell is affected, and in every other case)
When reset has not been triggered for any reason:
7104 CELL SERVICE PROBLEM (LTE/GSM, in case of
7101 RESET NOTIFICATION (when reset is being
WDCMA if all cells are affected)
performed)
7105 RAT BASE STATION PROBLEM (WCDMA if one
or more cell is affected, and in
When reset has 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 the reason for the fault/alarm situation
To clear this fault, perform the following steps:
(for further instructions about the history feature, see the
1. Make sure that the module is properly connected. If the
online help of BTS Site Manager). Depending on the
module LED does not light up, the module is faulty. Check
possible reason, follow the instructions below:
the alarming module.
1. Perform RAT reset.
2. Check the fault history.
2. Block/Unblock SBTS.
3.
1. If
Instep
case2ofdoes notinhelp,
a fault replace the alarming
the transmission networkmodule.
synchronization, you must correct the network
synchronization.
1. Block/unblock The long-term
the module thataccuracy of the
is causing the signal
alarm.used
for
2. Replace the module that is causing the alarm. correct
synch must be 0.015 ppm or better (check the
accuracy by measuring it). No actions on the BTS are
necessary.

1. Reset the WCDMA SW.

2. Check the transmission


If the basic accuracy of the linkssignal
to theused
RNC/Flexi Direct
for synch is
RNC.
correct, but there is too much instability, that is, the
jitter/wander
1. Reset the WCDMA is outsideSW. the acceptable limits, you must
3. Check
correct thethe BTS and RNC/Flexi
synchronization of the Direct RNC transmission
transmission network.
settings.
The limits for the jitter/wander are defined in the ITU-T
2. Check the transmission links to the RNC.
G.823/824/825. No actions on the BTS are needed.
4. Reset the SBTS.
3. Check the BTS and RNC transmission settings.
Update the compatible SW in the BTS (check the SW
versions
5. Replace to the
seeSystem
the active SW version and update the
Module.
4. Reset the SBTS.
active
3. In caseSW of version), unless it is fault,
a BTS equipment automatically updated
the location mightbybe:
NetAct.
5. Replace the System Module.
Update compatible SW in the BTS.
NOTE: If the fault 10:EFaultId_NoConnectionToUnitAl is
also activepart:
Transport on the source unit, then the SW update must be
NOTE: If also fault 10:EFaultId_NoConnectionToUnitAl is
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.
- Check the alarms of the TRS signal used for
2. Check the stratum
synchronization parameter
with BTS on the NTP
Site Manager and server.
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:
<fileTypeNumber> - <fileType>
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 and check the download status from
Take5 to following steps to resolve the fault:
- licFile
the BTS SWDLreport in the snapshot file.
6 - measurementFile
1. Retry the SW update.
7 - rnwConfigurationPlanFile
2. If11other flash memory-related faults in the alarming
- combinedSiteConfigurationPlanFile
module
12 - are simultaneously active, replace the alarming
allConfigurationPlanFile
Take to following steps to resolve the fault:
module.
14 - testResultFile
15 - autoConfReport
1. Retry the SW update.
2. If17 - measurementPlanFile
other flash memory-related faults in the alarming
18 - rnwMetadataFile
module are simultaneously active, replace the alarming
Check19 -the mains power supply.
topologyFile
module.
22 - togglingParFile
23 - troubleShootingData
[...]
Check41 -the AntennaParameters
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
4. Check is an
fileexternal
and pathpower provided to the SBTS.
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. Replace the alarming unit/module.


1. 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. In case of other sources or if FR was already checked


To clear the fault, take 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 the cables between the system module and the
Follow the steps below to resolve the fault:
RF module.
3. If this does not help, replace the faulty Radio Module.
1. Reset the BTS.
2. If step 1 does not help, check your commissioning.
3. If step 2 does not help, replace the affected HW.
Follow the steps below to resolve the fault:

1. Reset the BTS.


2. If step 1 does not help, check your commissioning.
3. If step 2 does not help, replace the affected HW.
Follow the steps below to resolve the fault:

1. Reset the BTS.


2. If step 1 does not help, check your commissioning.
3. If step 2 does not help, replace the affected HW.
Check the signaling link settings and the 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 do not have reported
Recommissioning is needed. For a dual carrier RF 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 or recommission the BTS and pre-reserve less
Take the following actions to clear the fault:
capacity for HSUPA.
1. Check Element Manager for the received signal levels to
3. Reset the BTS to get the minimum capacity pre-
find out which RX is 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 alarm is inactive.
1. Check Element Manager for the 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 the antenna cables. The faulty radio module,
check if the RX signal level failure alarm is inactive.
antenna feeder, or antenna can be identified by locating
the source of the inadequate RX level on the antenna line.
3. If there are antenna line devices, check them.
Check
To clearandthisreplace the faulty
fault, perform theequipment or change the
following steps:
maximum
1) Check
When the RX signal level difference
4. the fault
antennais detected, a new
cables. The PICradio
faulty configuration
module, is to
(maxRxLevelDifference)
be provided by the threshold
Element Manager.(given during re-
antenna feeder, or antenna can be identified by locating
commissioning
2) Ifsource
this problem with default value 7dB).and insert the FSP
the of the persists
inadequatethenRXremove
level on the antenna line.
again.
Check and replace the faulty equipment or change the
To clear
Note: Thethis
RXalarm:
value in Element Manager is refreshed every
maximum RX signal level difference
1) The alarm indicates that the PIC configuration has
minute.
(maxRxLevelDifference)
failed. New BTS re-commissioningthreshold (given during re-
is needed.
commissioning with default value 7dB).
Commissioning done by the Element Manager / NetAct is
to include PIC pool configuration. It is recommended to re-
If the faulty
Note: The RXFSP is in the
value extension module, block/unblock
commission the BTSinduring
Element
lowManager is refreshed
traffic time. every
the extension
minute. module. Otherwise, block/unblock the BTS.
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 with the same
The lack of CCCH licensed capacity on the BTS (caused
UARFCN while one is in PIC pool and the other is not.
by an insufficient number of commissioned CCCH
The operator should also modify the PIC pool
Processing Set licenses) caused the cell setup with the
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 actions can be performed to setup the cell:
1. Reset
cells RAT.
<= 48).
1. Decrease the CCCH licensed capacity consumption.
2. Replace the faulty 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
Checknotifies the BTS
that the operator that the CCCH
has enough Common TransportSet
Processing
Channel is deleted.
licenses loaded or has received a sufficient number from
NetAct in order to change the CCCH licensed capacity
according
The lack oftoCCCH
the new CCCHon
capacity Processing Set
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 SBTS. Note that there are no recovery
Take the following actions to clear the fault:
actions and blocking/unblocking can be performed once. If
that does not help, replace the alarming unit or module.
1. Check the other active faults. If the /rom-disk is
corrupted, change the alarming unit or module.
2. Block/Unblock SBTS. Note that there are no recovery
Take the following actions to clear the fault:
actions and blocking/unblocking can be performed once. If
that does not help, replace the alarming unit or module.
1. Check the other active faults. If the /rom-disk is
corrupted, change the alarming unit or module.
2. Block/Unblock SBTS. Note that there are no recovery
Take the following actions to clear the fault:
actions and blocking/unblocking can be performed once. If
that does not help, replace the alarming unit or module.
1. Check the other active faults. If the /rom-disk is
corrupted, change the alarming unit or module.
2. Block/Unblock SBTS. Note that there are no recovery
Take the following actions to clear the fault:
actions and blocking/unblocking can be performed once. If
that does not help, replace the alarming unit or module.
1. Check the other active faults. If the /rom-disk is
corrupted, change the alarming unit or module.
2. Block/Unblock SBTS. Note that there are no recovery
Perform the following steps until the fault is resolved:
actions and blocking/unblocking can be performed once. If
that does not help, replace the alarming unit or module.
1. Reset the SBTS.

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. Check the alarming unit/module.
There 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. Check the other alarms of the BTS and act accordingly.
2. Replace the System Module.
2. If there are no other synchronization-related alarms
Perform the the
active, start following steps:with BTS Site Manager.
fast tuning

1.
3. Restart thesite.
Reset the MHA by fast
Run taking one again.
tuning of the following steps:

-Togglingthe
4. DC voltage on the antenna line
byoff and on. it
1. Check
Restart thereference signal
MHA by blocking accuracy
and unblocking measuring
the Radio
-Blocking
with a and unblocking
frequency counter Radiorequires
(note: Module.a good timebase
Module.
-Restarting
for the counter).BTS.The reference signal can be found from
the Sync Out interface
Note: This operation of theall
affects Flexi
the System
antennaModule,
lines and thecells
Note:
requiredTheaccuracy
above operations
is +/-0.015ppm.might affect
If the other antenna line
reference
related to the Radio Module, not just the faulty one. If the
To recover
devices
accuracy isfrom
connected thisto
correct, fault,
runthefastperform
FR Module the following
If (and relatedsteps:
cells),
alarm reappears, replace thetuning.
alarming the reference
module.
not just the
accuracy is faulty one. the cause of the fault is with the
not correct
1. Cancel the faultthe
reference by FR Module resetTroubleshoot
or BTS reset the
2. Restart source
the MHA byBTS is tuning
disabling andto.enabling DC power on
or
2. Checksynchronization
external the antenna cables networkand toconnectors
find the roottowards
cause. the
the antenna lines
2. Disable
MHA.
Other Fix
BTSs and
or enable
replace
the the DC power
broken of affected
parts. antenna line
1. Check
connected thetowith
antenna
MHA. same
cables, alarm can
connectors,provide furtherand
antenna,
(depending
information on
about the location of the root cause.
possible antenna line devices.
the
3.
5. FR hardware
Replace
If the type, the
the alarming
reference fault
module. mightand be solvable by
Note: Alarm can beaccuracy
canceledisthrough:
correct running
a Radio fast
Module
switching
tuning doesthenotDChelp,
power off and
replace theon).
system module.
2. Check
reset the antenna
(including Radio line Module(TX-cable-antenna)
hot removal), a BTS impedance
reset,
3. Check the antenna cables and connectors running to
matching.
or a DC voltage turn-off by a user of the antenna line.
1.
theCheck
MHA. theFix antenna,
or replacethe theantenna
broken cables,
parts. connectors and
other possible antenna line devices.
3. Check the antenna cables and connectors running to
the MHA. the
2. Check Fix antenna
or replace the
line broken parts.
(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 the 2.048 MHz signal is available.
1. Confirm if the existing configuration is within the
configured RF HW capabilities.
3. Replace the alarming module.
2. Check the BTS connections and commissioning
Take the following actions to clear the fault:
settings.
3. Block/Unblock the BTS.
1. Block/Unblock the RF HW unit.
4. If the HW configuration is confirmed, then this problem is
2. If the problem is still observed after performing the first
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.
Instructions are divided into three sections. Take the
following actions to clear the fault:

Section A: Check the system module side:


1. Check if connector seal is properly mounted and firmly
There are three sets of instructions. Take 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 the
1. Check if the connector seal is properly mounted and
connection/mounting.
firmly in place.
3. Check if the LED indicates the faulty SFP (connected to
2. Check if the small form-factor pluggable (SFP) is
System Module). Replace the SFP if it is faulty.
properly connected or mounted to the system module. If
4. Check if the optical cable is properly connected/mounted
the SFP connection or mounting is incorrect, re-adjust the
in the SFP.
connection or mounting.
5. Clean the optical connectors that are connected to the
3. Check if the LED indicates the faulty SFP (connected to
SFP. Reset RF HW unit by doing the block/unblock
system module). Replace the SFP if it is faulty.
procedures, and check if this solves the problem.
4. Check if the optical cable is properly connected or
mounted to the SFP.
Section B: Check the radio module side:
5. Clean the optical connectors that are connected to the
Take the following actions to clear the fault:

1. Confirm if the existing configuration is within the


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

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 the system module side.


1. Check if the ambient temperature/environmental
1. Check if the connector seal is properly mounted and
conditions are within the design limits for the radio module.
firmly in place.
When the ambient temperature/environmental conditions
2. Check if the small form-factor pluggable (SFP) is
are out of limits, the alarm is expected and no further
properly connected or mounted to the system module. If
actions are needed.
1.
theBlock/unblock
SFP connection RF or HW unit
mounting is incorrect, re-adjust the
2. If the problem
connection persists, replace the RF HW unit
or mounting.
2. Check if air flow is not blocked by some objects. Make
3. Check if the LED indicates the faulty SFP (connected to
sure minimum thermal clearances are followed. Remove
system module). Replace the SFP if it is faulty.
any objects that might be blocking airflow and mount
4. Check if steps
Follow the optical cable is properly connected or
modulethe accordingbelow to clear
to instructions theandfault:
recommendations.
mounted to the SFP.
5.
1. Clean thethe optical
fan orconnectors
airflow thatof are connected to the
3. Check if excessive sunlightisisfree causing foreign objects.
overheating.
SFP.
Remove Reset the
any objectsRF HW unit
blocking by blocking/unblocking
the faninstructions
or the airflow. and
Install sunshield following mounting and
check if this solves the problem.
2. Check if the fan connector is properly mounted. Mount
recommendations.
Follow the steps below to clear the fault:
fan connector according to the guidelines.
Set
3. If B:theCheck
alarmthe radio
is still modulethen
observed side.reset the radio module
1. Check if the fan or the airflow
connector seal is is free of mounted
properly foreign objects.
and
by block/unblock.
Remove
firmly in any
place. objects blocking the fan or the airflow.
4. If the alarm is still observed then replace the fan module.
2. Check if the fan SFP connector
is properly is properly mounted. Mount
Follow the steps below to clear connected
the fault: or mounted in
fan
the connector
Radio Module. accordingIf the SFP to theconnection
guidelines.or mounting is
3. If the alarm is stillthe
incorrect, observed thenor reset the radio module
1. Check ifre-adjustthe fan or the connection
airflow is free mounting.
of foreign objects.
by
3. block/unblock.
Remove any objects blocking the fan or the airflow.or
Check if the optical cable is properly connected
4. If the alarm
mounted theisfan
still observed then replace the fan module.
2. Check in if the SFP. connector is properly mounted. Mount
Follow
4. Clean the the steps below
optical to clear the
connectors at thefault:
Radio Module end.
fan connector according to the guidelines.
Reset the RF HW unit by blocking/unblocking
3. If the alarm is still observed then reset the radio and check
moduleif
1.
thisCheck
solves if the problem.
fan or the airflow is free of foreign objects.
by block/unblock.
Remove any objects that are blocking the airflow.
4. If the alarm is still observed then replace the fan module.
2.
SetCheck
C:theCheckif thethefanoptical
connector is properly mounted. Mount
connection.
Take following steps to clear the fault:
the fan connector
1. Check if the opticalaccordingcablestoare thenotguidelines.
overbent. If the radius
3.
of If
the the alarm
cable is still observed
bending exceeds thenguidelines,
the reset the radio module
then the
1. Check if the ambient temperature/environmental
by block/unblock.
optical cables need to be replaced as over-bending the
conditions are within the design limits for the radio module.
4. If thefiber
optical alarm is stilldamages
observedthe then replace the fan module.
When the ambient temperature/environmental conditionsor
cables cables and can detach
1. Checkthe
damage if the ambient temperature and environmental
connectors.
exceed the limits, the alarm is expected and no further
conditions
2. Optionally, aretest
within
thethe fiberdesigned
cable (for limits for themeasure
example, radio the
actions are needed.
module. When the ambient
optical attenuation) from thetemperature
system module and end
environmental
and/or
conditions
Radio Module exceed
end.the limits, the alarm startup is expected
2. Check if air flow isCheck
free ofthe measuring
foreign objects. equipment
Make sure the
and no
documentationfurther actions
forclearances
details.are needed.
1. Check ifthermal
minimum the ambient temperature
guidelines andare environmental
followed.
conditions
Remove any areobjects
within the thatdesign
might be limits for thethe
blocking radio module.
airflow and
2.
If Check
the alarm if air flowobserved
is still is free of afterforeign objects.the
executing Make sure
When
mount the
the ambient
module temperature
according and andsteps from
environmental
to instructions
minimum
the thermal
instruction setsclearance
A, B, andguidelines
C, replace are
thefollowed.
Radio Module.
conditions
recommendations. exceed the limits, the alarm startup is expected
Remove any objects that might be blocking the airflow and
and no further actions are needed.
Instructions
mount the module are divided
according into three sections. and
to instructions
3. Check if excessive sunlight is causing the unit to
recommendations.
2. Check if the airthe
overheat. flow is not blocked by the
foreign objects.
Section A:Install Check onsunshieldsystem module following side: mounting
Make sure minimum
instructions and thermal clearances are followed.
recommendations.
1.
3. Check if the connector
excessive seal is causing
sunlight properly the mounted
unit toand
Remove any objects that might be blocking airflow and
firmly
overheat. in place.
Install the sunshield following the mounting
mount the module according to the instructions and
2. Check if the
instructions andSFP (Small Form Factor Pluggable) is
recommendations.
recommendations.
properly connected to the System Module. If the SFP
connection/mounting is incorrect, readjust the connection.
3. Check if excessive sunlight is causing the unit to
3. Check if the LED indicates the faulty SFP (connected to
overheat. Install the sunshield following the mounting
the System Module). Replace the SFP if faulty.
instructions and recommendations.
4. Check if the optical 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
procedures, and check if this solves the problem.
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 re-adjust the optical connectors, and verify the
To clear this fault, perform the following steps:
operation of any devices in the optical network between
1. VSWR measured at RF (transmitter) exceeds the values
FSM and Radio Module, if such devices are in use.
acceptable by the RF module.
2. Block/unblock the Radio module.
2. 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
blocking/unblocking the BTS. and commisionning settings.
3. To check if above mentioned steps have solved the
2.
4. Block/unblock
If this does notthe BTS
help, (usingthe
replace theSFP
localmodule(s)
BTS Site in which
problem, block/unblock the RF module.
Manager connection
the malfunctioning if a remote
optical connection
connection is not and/or
is occurring,
* Forcing the RF HW to work under such conditions might
possible).
replace the fiber.
result in RF 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. Check Radio modules External Alarm and Control line
1. Check that the SFP is properly connected.
connections and BTS commissioning settings.
2. Replace the SFP module.
Take the the
3. Reset following
Radioactions
Module.to clear the fault:

1. Check
4. After that the
Radio SFP isExternal
modules properlyAlarm
connected.
and Control line
configuration and connections have been confirmed and
2. Replace
Radio moduletheisSFP 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 behind the faulty link). The optical interface
1. Reset the Radio Module with the faulty optical interface
LED indicates the faulty SFP. Replace the SFP if it is faulty.
by blocking/unblocking it.
To clear the
3. Clean the fault, take thetest
connectors, following
the fiberactions:
cable, and replace it
2. If this does not clear the fault, replace the Radio Module
if faulty.
that is causing the alarm.
1. Swap the links between alarming and working ports
2.
4. Then checkabove
If the steps where do thenot
alarm
help,is replace
reported.theIf module
the alarming
3. If the System Module is the only source of the alarm, or
port
behind remains
the the same,
faulty link. replace the System Module.
To clear the
replacing thefault, take thedoes
RF Module following actions:
not clear the fault, replace
3. If the alarming port changes, replace the Radio 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 Module.
To clear the fault, take the following actions:
3. If the alarming port changes, replace the Radio Module
behind that link.
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 Module.
To clear the fault, take the following actions:
3. If the alarming port changes, replace the Radio Module
behind that link.
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 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 Module.
To clear the fault, take the following actions:
3. If the alarming port changes, replace the Radio Module
behind that link.
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 Module.
Check the Radio Module alarms.
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 Module/Extension System Module that causes the
Follow the steps below to resolve the fault:
alarm.
1. Check the cables between the System Module and
3. If the System Module is the only alarming source, or
Radio Module/Extension System Module.
replacing the RF Module/Extension System Module does
Follow
not clearthethe
steps
faultbelow to resolve
situation, the
replace steps:
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
4. Replace mapping
the alarming to the
System local cells in the
Module.
2. Replace the 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. If this does not clear the fault situation, replace the
1. Check the status of the module with the faulty port (for
alarming Extension System Module.
example, power on).
3. If the System Module is the only alarming source or
2. Check the alarming fiber connection.
To clear this
replacing thefault:
Extension System Module does not clear the
fault situation, replace the alarming System Module.
3. Replace the alarming fiber connection.
1. Switch to the 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. Reset SBTS Site from SBTS Element Manager.
To clear the fault, take the following steps:
4. Check configuration:
a. SCF configuration
1. Verify backhaul connectivity
b. SBTS profile
2. Reset the alarming TRX from BSC
c. BSC configuration
3. Reset the BCF from BSC
Take the following
5. Replace action to resolve the fault:
faulty modules.
4. Reset SBTS Site from SBTS Element Manager
5. Check configuration:
1. Reset the alarming TRX from BSC
a. SCF configuration, especially IPSec and IP configuration
2. Reset the BCF from BSC
b. BSC configuration
3. Reset SBTS Site from SBTS Element Manager
1.
6. Check
Replace configuration and update configuration if needed
faulty modules
4. Check configuration:
a. Update SBTS profile if profile has less resources than
a. SCF configuration
needed
b. SBTS profile
b. Delete 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. Check configuration
1. Block/Unblock the faulty radio modules assigned to the
a. SCF configuration, especially IPSec and IP configuration
sector and then Lock/Unlock the sector.
b. BSC configuration
2. Check the cabling of the faulty radio modules.
c. firewall configuration between BSC and BTS
3. Reset SBTS Site from WebUI.
6. Replace faulty modules
4. Replace faulty radio modules and lock/unlock the
Reset (block/unblock) the SBTS.
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,
interface. steps below to clear
perform a the fault: power reset for
(remote)
the GPS receiver.
1.
2. Check
Performthe fault name
a (remote) BTSof the
site toggling
reset forBTS fault. BTS.
the whole
3. Perform a power reset for the whole BTS.
2.
4. Follow
The the between
cable instructionsthe of
GPSthe receiver
toggling and
BTSthe fault to clear
BTS might
Update the SW in 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!
kind ofDetailed information
dirt, meaning that the about the togglingquality
pin connection frequencyis
can
good.be found in the alarm history file, which can be
Note:
5. ThePerform
downloaded the steps
cable using
between BTSthe below
Site
GPS in
Manager.the listed
receiver The order
andlogthefileuntil the
is might
BTS
SBTS fault
available
be faulty. disappears.
with
Check Snapshot.
the situation and change the cable, if
needed.
6. There might be a HW fault in the GPS receiver. Check
1.
theCheck the RET change
operation configuration file.
Note: Performand the steps below the GPS
in themodule, if needed.
listed order until the
7. There might be
SBTS fault disappears. a HW fault in the BTS System Module.
2. Download
Check the RETand
the operation configuration
change thefile to the Module,
System antenna ifline
device
needed.again.
1. Check the RET configuration file.
To clear this fault, perform the following steps:
1. Make sure that the module is properly connected. If the
2. Download the RET configuration file to the antenna line
module LED does not light up, the module is faulty. Check
device again.
the alarming module.
Note! Perform the steps below in the listed order.
2. Check the fault history.
1. Check if other BTS 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 connected and working. Add missing parallel
1. Check the RS485 IUANT interface and antenna line
RP3-01 links.
devices. Fix or replace the faulty parts or devices.
3. Restart the Radio Module.
2. Block or unblock Radio 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. If that does not help, replace the alarming module.
To clear this fault:

1. Make sure the fan is not blocked.

2. Make sure the fan connector is properly mounted.


To clear this fault:
3. If that does not help, replace the fan.
1. Make sure the fan 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 SW version, the SBTS Element Manager should
If the BTS is not automatically updated by 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
If the BTS is not automatically updated by 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. If the faulty cell is on the baseband extension module,
1. Wait for startup to be completed if a 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 cable between the synchronization master and
Perform the steps below in the listed order until the fault
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. The alarm is informative only. Normally, the
Perform the steps below in the listed order until the fault
GPS receiver runs the survey for two reasons:
disappears.
- somebody has started the survey manually
- the GPS receiver has noticed that the position has
No stored position:
changed and the receiver has started an automatic survey
1. One of the GPS receiver settings is incorrect. Using the
Perform
Note: The the steps below
automatic survey in the listedtakes
always orderplace
until the
during faultthe
manager SW of the GPS receiver, set the receiver to store
disappears.
first start-up.
the position into non-volatile memory.
If there is no tick mark in the position storage selection, the
Position questionable:
2. If the automatic survey takes place every now and then,
GPS receiver runs the site/self survey every time the GPS
1. The GPS
itPerform
might be anreceiver
indication hasthat validtheposition data but
sky visibility it is not
is poor andin
receiver the is resetsteps belowby
(either inmanager
the listed order until
command, thepower
by fault
line with the
according to information
the estimated
poorly-tracked from the
satellites, theactual
GPS satellite
receiver
disappears.
outage, or by a GPS recovery reset). This means that if the
visibility.
concludes The thatreason for thishas
the position faultchanged.
indicationInmight
this case,be that
GPS receiver installation quality is only an average - and
the
check GPS the antenna
activity installation
of the other has
faults not(BTS
beenfault
done properly,
history data)
EEPROM
especially invalid: if the installation is a poor one - the GPS
that
and is,
if the sky
found visibility
feasible, is not good
reinstall the enough.
GPS Refer to the
antenna.
1. The GPS
receiver turns receiver
the PPS has detectedOFF
reference a malfunction
every now inandthethen
Trigger
documentation SW update for BTS
for instructions to the
andrequested
if there are SW version.
deviations
EEPROM
during the memory site survey. of theThis GPSmeansreceiver.
the BTSPerform
master a (remote)
clock
with
3. the GPS
If the actualinstallation
installation, is reinstall
good butthe theGPS antenna.
automatic survey
power
drops to reset for themode
holdover GPS much receiver.easier during the survey
Note:
still takesEven when
place the GPS
every now and antennathen,has a good
there mightsky be a
than during the normal operation.
visibility,
malfunction the in problem
the GPS might be caused
receiver. Perform by ainstalling
(remote) thepower
2. There might be a HW fault in the GPS receiver. Check
GPS
reset
Check antenna
for the too
GPS
the transport close
receiver. to
relatedthethe transmitter
configuration antennas
(C-Plane of the
the operation and change GPS module, if needed.
BTS, causing disturbances for the
address, U-Plane address, Transport network ID). If the GPS receiver.
2.
4. There
If the
fault might
wasactionsraisedbe at astart-up,
malfunction
detailed in the in the
previous
correct the GPS
steps receiver.
do not and
configuration
Perform
improve a (remote) power reset for
reset the BTS. If the fault was raised during eNBinruntime,
the situation, there might bethea GPS
HW receiver.
fault the
3.
GPS There might
receiver. be
Check a HWthe fault in
operation
correct the configuration and apply the changes to the the GPS
and receiver.
change the Check
GPS
1.
the One ofif the
operation
module, most
and
needed. common
change the reasons
GPS for this iffault
module, indication
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 are deviations
If the fault persists after a BTS reset, replace the 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
transmitter VSWR threshold
antenna(s) of the BTS, values
causingusing BTS
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
No manual action to be ON infrom
is needed this the
case (while in shared
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 MHA is not shared between two BTSs:
Add #data users licenses 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. Check the cabling (connected to Sync In interface).


Replace the long cable with a shorter one. If the radio
module is connected
2. Check if the 2.048 MHz reference source is working
directly to system module or 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 is not cleared because of repeated activation or
SBTS after an SBTS site reset. The Operator may 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 diagnostic info, one can try the
or the functionality on 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
scenarios, (Physical HARQ Indication
with WiMAX in Channel)
the same band, co-
transmission
existence withpower other boost can be increased
LTE networks from otherbyvendors;
reducingif
the
yes,configured
check whether boosts
thefor cell-specific downlink
synchronization between reference
networks
signal and/or configured.
are correctly PCFICH.
2. Checknetwork
Perform whetheroptimization.
the cell is set up under a network using
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
RFM with TD-SCDMA.
The system has automatic actions by decreasing the traffic
iforyes, it is suggested
the functionality on to check
traffic. Nowhether the action
additional carrieris
configurations in TD-SCDMA
required from the operator. and TD-LTE are not in
conflict.
5. Check the RP3 links state, especially for the SFP as well
The
as the system
fibershas automatic
connecting theactions
RFM(s)byand
decreasing
the BBU(s) theinside
traffic
or
thethe functionality on traffic. No additional action is
eNB.
required
6. Block and fromunblock
the operator.
the cell.
7. Reset the BTS.
8.
1) Examine
Check thethe antenna
GTP-U pathcable connection
supervision between the
configuration of the
RFM
eNB. and the antenna element.
9.
2) Exchange
Check if the the cable connection
supervised networkbetween
element antenna and
is operating
RFM to check whether the RRU port or the cable is faulty.
correctly.
10. Replace
3) Check thethe hardware(RRU/BBU).
communication 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
anymore.
Perform the steps below in the listed order until the alarm
disappears:

1. Check the connection with MME, based on whether the


S1 link is broken accordingly.
Perform the steps 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 the switch port that is connected
1.Check the connection with adjacent BTS, based on
directly to the eNB (for example, they are both "Autodetect"
whether the X2 link is broken respectively.
Follow
or both the steps
"1000 below
Mbit/s Fulltoduplex").
resolve the fault:
2. Check if the adjacent BTS is operational.
1. Check
If this faultwhether
happenstheright
transport
after apath is alive.
commissioning or a
If this fault happens right after a commissioning or a
2. Check the configuration
configuration change, verifyofthe
transport
following addresses at MME.
configuration
configuration change, verify the IP address of the adjacent
data: IP address of the MME.
Note: Perform the steps below in the listed order until the
BTS.
alarm disappears:
1. Check the connection with MME, based on whether the
M3 link is broken accordingly.
2. Check if MME is operational.
1. Check whether the transport path is alive.
3. Check if the speed and duplex setting of eNB M3 port is
2. Check the configuration of transport addresses at 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
configuration change, verify theparameters.
following configuration
2. Load
data: IP the correct
address of commissioning
the MME. file to the BTS.
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 the SW files.
following must be done:
6. Replace FSM.
- "Subscriber & Equipment Trace feature not enabled":
Check and ensure that the PLMNs that have been listed
Enable the subscriber trace feature at the BTS. Any events
with this BTS fault and that have been configured at BTS
corresponding to the failed subscriber trace and any other
for one or more cells have at least one MME serving them
subscriber traces started later, which must be recorded, will
and that the relative capacity of that MME is greater than
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 of LNADJL objects has
yes, check if there are LNADJW objects that can be
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). If it has been, check if there are LNRELW
Add the LNREL object pointing to the correct neighbor 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)
psHoAllowed, the BTS
srvccAllowed) of to recover per
LNRELW the cell
faulty cell.
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. Check the connection between the GPS receiver and
1. Check for UTRAN (FDD) cells that operate on the same
FSM.
frequency layer and
use the same PSC and that are in close vicinity.
If the TOP signal is configured as a reference clock,
2. Reassign PSCs for the discovered cells.
perform the following:
Reconfigure
1. Check the parameters
connection that are
to the related
TOP to the Inter eNB
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
3. If there are no BTS. 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 reconnect the adjacent BTS.
Perform the steps below in the listed order until the alarm
disappears:
1. Check connectivity to the related adjacent BTS.
2. Check other faults.
3. Check the parameters related to the X2 interface to the
Perform the steps below in the listed order until the alarm
adjacent BTS.
disappears:
4. Reset the BTS.
1. Check availability of MME.
2. Check other faults on MME and BTS.
3. Check the parameters related to S1 interface in the BTS
Perform the steps below in the listed order until the alarm
and MME.
disappears:
4. Reset the BTS.
1. Check the availability of MME.
2. Check the connection with MME.
3. Disconnect and reconnect MME.
Perform the steps below 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 reconnect the MME.
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"


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
how many LNADJGs or LNADJWs are affected at a given
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
Unavailable, checkbelow in the listedtoorder
the connectivity until the fault is
GSM/WCDMA
resolved:
network (MME<->SGSN<->BSC).

1. Reset
Note thatthe
onlySystem Module.
one alarm for one PLMN is raised due to the
RIM
Perform the steps below in only
faults for GERAN and one for
the listed UTRAN,
order no fault
until the matteris
2.
howReplace
many the System
LNADJGs orModule.
LNADJWs are affected at a given
resolved:
time. The alarm is raised for the first LNAJDG/LNADJW
where
1. Reset thethe
fault is detected.
System Module. The alarm additional
information contains the parameters of the first
Note! Perform the steps
LNADJG/LNADJW, even below in thefault
if the RIM listed order until
is already the
inactive
2. Replace the System Module or faulty FSP
fault
for is LNADJG/LNADJW,
the resolved. 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. Check other faults on MME and BTS.
Perform the following steps until the 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 than subfrPShareDeployed or modify other
This fault is a warning and cannot be cleared. The
parameters to get additional subframe resources.
sessions that cannot be resumed are automatically cleared
2. Push the delta plan file to the BTS.
using M3 Partial Reset 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. Check whether there are active alarms at the far end. If
1. Check the availability of IP connectivity.
there are, follow the instructions for handling those alarms.
2. Check whether there are active alarms at the far end. If
4. To verify that the hardware of the interface works
there are, follow
correctly, connect a loop cable and check whether the
the instructions for handling those alarms.
alarm disappears.
Switch
5. Checkoffthat
the the
loopback or waitoffor
length/type thethe timeout to
cable/fiber expire
does not
which opens
introduce the loopattenuation
excessive and cancels or the
thatalarm.
the cable/fiber is
cut somewhere.
6. Check that the Ethernet interface has correct auto-
negotiation
1. Check that settings,
the SFP fitting to the
module far-end interface.
is correctly installed.
7.
2. Plug-out/plug-in the SFP module. Check that the
With an optical Ethernet interface:
inserted
3. CheckSFP module
for SFP matches
validity (couldthebefiber type and
the wrong type) and
wavelength of the Gigabit
insert a compliant SFP module. Ethernet link provided.
4. Check that the electrical contacts of the SFP module are
Execute general configuration checks:
clean from dust, dirt or water.
- Configuration of primary/secondary CRL server IP
5. Replace the SFP module with a module recommended
address and port.
by Nokia.
- Configuration of DNS server IP address.
Note that only the SFP might be faulty, not the entire
- Configuration of IPsec policies towards remote peers.
Replace
hardwarethe faulty SFP. Note that only the SFP is faulty,
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
Check the names.
DNS cables and connectors.
2. Check
Check thethat
sizethe
of connectors areCertificate
the file at the properly connected
RevocationtoList
the
unit.
server.
3. Checkconnectivity
Perform that the cable connected
checks relatedtotothe interface in
primary/secondary
question
CRL is not damaged and is within the specifications.
servers.
Check that the configured interface type matches the
4. Follow the E1 path in the network and check whether
configured interface type of the far end. If this is the case,
any other alarms concerning the fault are on (such as
the problem is somewhere in the 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 this interface.
1. Re-insert the expected transport module 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 the correct ones accordingly either at
the SL-PPP/ML-PPP interface and follow the instructions
the local end or
of these alarms.
peer if there is a mismatch.
Check all PDH related alarms and follow the instructions of
1. Check the 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 configurations of the BFD local and remote
1. Check the network between both BFD peers for 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, then the alarm is caused by a
link speed downshift event.
1. Check the backhaul usage and if other applications with
2.1 Check that the cables are fully plugged in to the
the same or higher PHB may compete against this TWAMP
connectors.
session about the capacity. An increase in the priority of
2.2 Check that a CAT5e or higher Category cable is used
TWAMP session or of the backhaul capacity may clear the
2.3 Replace the cable.
alarm.
1.
3. Check the backhaul
If the clock mode of the usage and
local if otherinterface
Ethernet applications with
is slave
the
andsame or higher
the Ethernet PHB may
interface compete against
is configured to serve this
asTWAMP
2. Check the last measured RTT values of this TWAMP
session about the
synchronization capacity.
source, thenAnthe
increase
alarm isincaused
the priority
by aof
session and verify that the configured RTT threshold value
TWAMP
clock mode session or of the backhaul capacity may clear the
mismatch.
is not too close to average measured RTT values, so that
alarm.
3.1 Check the clock mode setting expiry
of the remote link
Check
this the could
alarm vendor beBTS certificate
result of sporadic date and
mis-measurement. renew it.
partner. It should be either "multiport device" or "manual
2. Check if destination is unreachable by IP connectivity
master".
test. Send an ICMP
3.2 Configure echo
the local request
clock mode(ping) to the UDP
to "manual slave"port of
the TWAMP
forcing local reflector
Ethernet at the destination
interface to operate IP.IfatICMP
slave echo
clock
Update
reply
mode. trust anchors.
indicates that the destination is unreachable but you
have access to TWAMP reflector, you can check its status.
If the status
Note: Do notisexecute
disabledthis
or step
downremote,
try to activate
but onlyit when
again and
check if alarm
being local disappears.
at site as it can cause the Ethernet link to be
down.
Check As theaLCP result, remote
failure alarmsmanagement accessbelonging
of the PPP-links might be to
3. Check
lost. configured PLR threshold.
the ML-PPP interface and follow the instructions of Setting PLR to these
0%
should
alarms. be avoided, because every lost measurement
packet
Note: Checkwill trigger the root
whether alarm and itofcannot
cause beiscleared
the fault again
not existing
(PLR>=0).
anymore, is done by a new auto-negotiation
Check the related PDH alarms and follow the instructions process.
Retriggering
of these alarms. 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. Troubleshoot with Backhaul provider about the reason
1. Confirm that SyncE is desired as a synchronization
for SSM errors.
source.
2. Confirm that SBTS configuration settings for
ssmEnabled are correct.
3. Troubleshoot with Backhaul provider about the reason
Check the cable connectivity on ToP master side.
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 HW variant:
Start IPsec emergency bypass by making the security
- Replace the unsupported device variant to another one
gateway not reachable either by plugging out the cable or
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

• RP000847: BTS Synchronization mode support

• RP000980: SBTS Recovery

• RP000980: SBTS Recovery

• RP000912: SBTS SW Management

• RP000912: SBTS SW Management

• RP000996: SRAN Clock time management


• RP000912: SBTS SW Management

• RP000912: SBTS SW Management

• RP000912: SBTS SW Management

• RP000912: SBTS SW Management

• RP000924: SBTS Intelligent shutdown

• RP000924: SBTS Intelligent shutdown

• RP000924: SBTS Intelligent shutdown

• RP000923: SBTS State Transitions

• RP000923: SBTS State Transitions

• RP000940: SBTS Diagnostics and Self Test


• RP000911: SBTS HW Management

• RP000911: SBTS HW Management

• 10457: field report of routing component

• RP000920: SBTS Fault Management


• ARAN1163: Iu-PS Throughput Measurement for GTP
Traffic
• RAN1671: Enhanced UltraSite Base Band (EUBB)

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management


• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management


• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP001016: SBTS OMUSIG inside SBTS

• RP000788: 1PPS&ToD Sync from external GNSS


Receiver
• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000847: BTS Synchronization mode support

• RP000847: BTS Synchronization mode support

• RP000847: BTS Synchronization mode support

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management


• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000912: SBTS SW Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management


• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• RP000910: SBTS Antenna Line Management

• 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

• RP000956: SBTS Startup and runtime management


• RAN2262: Flexi Multimode System Modules FSMF
and FSMG

• RAN2262: Flexi Multimode System Modules FSMF


and FSMG

• RP000920: SBTS Fault Management

• RP000980: SBTS Recovery


• RAN1263i: Generic RAKE for HSPA baseband
efficiency final implementation

• RP001016: SBTS OMUSIG inside SBTS

• RP001016: SBTS OMUSIG inside SBTS

• RP001016: SBTS OMUSIG inside SBTS

• RP001016: SBTS OMUSIG inside SBTS

• RP001016: SBTS OMUSIG inside SBTS

• RP001016: SBTS OMUSIG inside SBTS


• RP001016: SBTS OMUSIG inside SBTS

• RP001016: SBTS OMUSIG inside SBTS

• RP000788: 1PPS&ToD Sync from external GNSS


Receiver

• RP000847: BTS Synchronization mode support

• LTE656: LTE Fault Management

• RP000912: SBTS SW Management

• RP000911: SBTS HW Management

• RP000956: SBTS Startup and runtime management

• RP000910: SBTS Antenna Line Management


• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000956: SBTS Startup and runtime management

• RP000912: SBTS SW Management

• RP000912: SBTS SW Management

• RP000912: SBTS SW Management

• RP000979: interface between system modules

• RP000788: 1PPS&ToD Sync from external GNSS


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

• RP000788: 1PPS&ToD Sync from external GNSS


Receiver

• RP000788: 1PPS&ToD Sync from external GNSS


Receiver

• RP000788: 1PPS&ToD Sync from external GNSS


Receiver

• RP000912: SBTS SW Management

• RP000788: 1PPS&ToD Sync from external GNSS


Receiver

• RP000956: SBTS Startup and runtime management

• RP000910: SBTS Antenna Line Management

• RP000912: SBTS SW Management

• RP000912: SBTS SW Management

• RP000912: SBTS SW Management


• RP000912: SBTS SW Management

• RP000910: SBTS Antenna Line Management

• RP001004: SBTS Data User RTU

• RP001004: SBTS Data User RTU

• RP001004: SBTS Data User RTU

• RP000834: IP Traffic Capacity

• RP000980: SBTS Recovery

• RP000996: SRAN Clock time management

• RP000375: Synchronous Ethernet

• RP000375: Synchronous Ethernet

• RP000377: Synchronization from PDH interface

• RP001052: LTE feature parity


• RP001052: LTE feature parity

• RP000929: SBTS Configuration Management

• RP000357: Symmetrical E1 Interface

• RP000980: SBTS Recovery


• RP000941: Datacollectors support
• RP000847: BTS Synchronization mode support
• RP000361: Link Supervision with BFD
• RP000357: Symmetrical E1 Interface

• RP000910: SBTS Antenna Line Management

• RP000356: IPsec for BTS

• RP000357: Symmetrical E1 Interface

• RP000367: Small Form Factor Pluggable Slot (SFP


slot)

• RP000845: SBTS Operator Certificate Management

• RP000367: Small Form Factor Pluggable Slot (SFP


slot)

• RP000357: Symmetrical E1 Interface

• RP000357: Symmetrical E1 Interface

• RP000357: Symmetrical E1 Interface

• RP000357: Symmetrical E1 Interface

• RP000911: SBTS HW Management


• RP000176: MLPPP termination

• RP000176: MLPPP termination

• RP000176: MLPPP termination

• RP000845: SBTS Operator Certificate Management

• RP000361: Link Supervision with BFD

• RP000361: Link Supervision with BFD

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

• RP000360: IP Transport Network Measurements

• RP000360: IP Transport Network Measurements

• RP000845: SBTS Operator Certificate Management

• RP000845: SBTS Operator Certificate Management

• RP000176: MLPPP termination


• RP000375: Synchronous Ethernet

• RP000375: Synchronous Ethernet

• RP000384: Timing over Packet Resilience

• RP000589: IPv4/IPv6 Transport Stack

• RP000911: SBTS HW Management

• RP000439: IPsec Emergency Bypass

• RP000465: Local and Remote IP Traffic Capturing

• RP000900: SBTS user account management

• RP000600: Backup IPsec Tunnel

• RP000356: IPsec for BTS

• RP000356: IPsec for BTS

• RP000356: IPsec for BTS


#N/A

#N/A

#N/A

#N/A