Ref Bts Alarms and Fault Sran21b Sran21a

Single RAN, Rel.
SRAN 21B,
Reference Documentation
SRAN 21B BTS Alarms and Faults

(delta SRAN 21A)
DN09265653
Issue 02A
Approved on 2021-12-29
Nokia is comitted to diversity and inclusion. We are continuously reviewing our customer documentation a
with standard bodies to ensure that terminology is inclusive and aligned with the industry. Our future docu
be updated accordingly.
This document is intended for use by Nokia customers (“You”/"Your") in connection with a product purcha
licensed from any company within Nokia Group of companies. Use this document as agreed. You agree t
of any errors you may find in this document; however should you elect to use this document for any purpo
which it is not intended. You understand and warrant that any determinations You may make or any actio
take will be based upon Your independent judgement and analysis of the content of this document.
Nokia reserves the right to make to make changes to this document without notice. At all times, the contro
the one avaiable on Nokia's site.
No part of this document may be modified.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIA
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTE
BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR T
INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT
CONTENT.
Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names me
document
may be trademarks of their respective owners.
© 2021 Nokia.
1B,
n
nd Faults
wing our customer documentation and consultiing
d with the industry. Our future documentation will
n connection with a product purchased or

s document as agreed. You agree to notify Nokia
to use this document for any purpose(s) for
nations You may make or any actions You may
he content of this document.
thout notice. At all times, the controlling version is
NCLUDING BUT NOT LIMITED TO

TLE, NON-INFRINGEMENT,
, IS MADE IN RELATION TO THE
ABLE FOR ANY DAMAGES,
NCIDENTAL OR CONSEQUENTIAL
OFIT, REVENUE, BUSINESS INTERRUPTION,
E USE OF THIS DOCUMENT OR THE
SSIONS FROM THIS DOCUMENT OR ITS
rporation. Other product names mentioned in this

1. Introduction
1.1 Overview of BTS alarms and faults

This document describes the handling of the BTS alarms and faults for 5G and SRAN. The BTS software uses these alarm
and faults as a basis for internal diagnosis and fault reporting in the WebEM.
Note: For troubleshooting process overview and basic procedures, see the 5G and SRAN Troubleshooting document.
1.2 Handling of BTS alarms an

faults
The BTS alarm handling is based on the unit or module state information. It prevents to send unnecessary alarms by check
and updating the unit states. Fault messages come either from hardware devices or software components. The faults are
system or hardware-specific. The Fault Diagnosis System creates upper network alarms, which are based on an analysis o
faults, and sends them to the WebEM.
In addition, you can also use the Network Managment System (NMS) to handle the BTS alarms.
The BTS is able to maintain alarm handling after it has been commissioned and is in a configured state. During the start-up
the BTS waits for the real-time clock from the Network Time Protocol (NTP) server, and the fault diagnosis starts after the ti
has been set or a time-out has been detected. If the BTS is unable to set the time using the NTP server, the default time
(1.1.2004) is used.
BTS transmission alarms

The BTS transmission alarms (7665) are reported towards NMS. The transmission equipment uses the base station interfac
Therefore, the retrieval of the alarm information is mapped in the NMS to distinguish between the alarms by using the fault
Instructions for solving problems

When starting to solve a problem, first refer to the instructions given in the individual fault descriptions.
Verify the configuration of a BTS by checking the commissioning, cabling, and correct installation of the modules at the BTS
Make sure the environment doesn't cause the fault.
If an active alarm is a 'Start' alarm, a unit block/unblock (if supported by the unit) or a site reset is required to cancel it. If the
site reset or unit block/unblock doesn't help, replace the faulty unit or module. See the fields 'Fault source' and 'Instructions'
the corresponding alarm description.
Blocking and unblocking

The 'Cancel' alarms are always sent to hosts (WebEM). When the unit or cell is in a blocked state, the 'Start' alarms are onl
sent to WebEM.
When a unit or cell is unblocked, all the active alarms related to the unblocked unit, module, or cell are automatically sent to
hosts.
2. How to read this excel report
The excel report provides a full information on faults and alarms. It shows the full set of fault and alarm attributes.
The excel report consists of two main sections:

- Alarm List
- Fault List
The alarms and faults are listed by numbers in an ascending order.
2.1 Alarm List

This section shows the full alarm information including the following items:
- alarm number
- alarm name
- meaning of the alarm
- instructions
- list of related faults
- clearing information
- Change information
Summary of changes
Changes between document issues are cumulative for a release. Therefore, the latest document issue contains
all changes made to previous issues of this release.
Changes between issues 02 (2021-09-30, SRAN 21B) and 02A (2021-12-29, SRAN 21B)
Instructions of the 16 and 1868 faults have been updated.
Changes between releases SRAN Changes since previous issue Restriction status
21A and SRAN 21B
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
No
Changed No
No
New No
New No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
Changed No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Changed No
No
No
No
No
No
Yes
No
Yes
No
Removed No
Alarm Number Alarm Name
7100 BASE STATION HARDWARE PROBLEM
BASE STATION/UNIT AUTONOMOUS

7101 RESET NOTIFICATION
BASE STATION RESOURCE BLOCKED BY

7102 USER
BASE STATION EXTERNAL ALARM

7103 NOTIFICATION
BASE STATION CONNECTIVITY

7107 PROBLEM
BASE STATION SYNCHRONIZATION

7108 PROBLEM
7110 BASE STATION LICENSE LIMITATION
BASE STATION SOFTWARE

7111 MANAGEMENT PROBLEM
BASE STATION CONFIGURATION

7112 PROBLEM
7113 BASE STATION ANTENNA LINE PROBLEM
7114 CELL SERVICE PROBLEM
7115 BASE STATION INFORMATION
7116 BASE STATION SERVICE PROBLEM

7208 LOCAL BLOCK
7220 BASE STATION SECURITY PROBLEM
7222 TEMPORARY ALARM
ORAN RU VENDOR SPECIFIC

7240 INFORMATION
7241 ORAN RU EXTERNAL PROBLEM
7401 EXTERNAL AL 1
7402 EXTERNAL AL 2
7403 EXTERNAL AL 3
7404 EXTERNAL AL 4
7405 EXTERNAL AL 5
7406 EXTERNAL AL 6
7407 EXTERNAL AL 7
7408 EXTERNAL AL 8
7409 EXTERNAL AL 9
7410 EXTERNAL AL 10
7411 EXTERNAL AL 11
7412 EXTERNAL AL 12
7413 EXTERNAL AL 13
7414 EXTERNAL AL 14
7415 EXTERNAL AL 15
7416 EXTERNAL AL 16
7417 EXTERNAL AL 17
7418 EXTERNAL AL 18
7419 EXTERNAL AL 19
7420 EXTERNAL AL 20
7421 EXTERNAL AL 21
7422 EXTERNAL AL 22
7423 EXTERNAL AL 23
7424 EXTERNAL AL 24
7425 EXTERNAL AL 25
7426 EXTERNAL AL 26
7427 EXTERNAL AL 27
7428 EXTERNAL AL 28
7429 EXTERNAL AL 29
7430 EXTERNAL AL 30
7431 EXTERNAL AL 31
7432 EXTERNAL AL 32
7433 EXTERNAL AL 33
7434 EXTERNAL AL 34
7435 EXTERNAL AL 35
7436 EXTERNAL AL 36
7437 EXTERNAL AL 37
7438 EXTERNAL AL 38
7439 EXTERNAL AL 39
7440 EXTERNAL AL 40
7441 EXTERNAL AL 41
7442 EXTERNAL AL 42
7443 EXTERNAL AL 43
7444 EXTERNAL AL 44
7445 EXTERNAL AL 45
7446 EXTERNAL AL 46
7447 EXTERNAL AL 47
7448 EXTERNAL AL 48
7600 BCF FAULTY
7602 BCF NOTIFICATION
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
7650 BASE STATION FAULTY
7651 BASE STATION OPERATION DEGRADED
7652 BASE STATION NOTIFICATION
7653 CELL FAULTY

7653 CELL FAULTY
7654 CELL OPERATION DEGRADED
7655 CELL NOTIFICATION
7656 BASE STATION CONNECTIVITY LOST
BASE STATION CONNECTIVITY

7657 DEGRADED
MAINS BREAKDOWN WITH BATTERY

7995 BACKUP
61022 BFDGRP-$BFDGRPID down
61028 LOF on $UNIT, $INTERFACE
61029 LOS on $UNIT, $INTERFACE

61030 Dead Peer Detected
Interface under test on $UNIT, $INTERFACE

61040 for $LOOPTIMEOUT minutes
Missing SFP module on $UNIT,

61050 $INTERFACE
Link OAM loopback inserted on $UNIT,

61075 $INTERFACE by $PEER
61076 Link OAM link lost on $UNIT, $INTERFACE
Link OAM critical link event $E on $UNIT,

61077 $INTERFACE
61079 SFP HW Failure
61104 EBER on $UNIT, $INTERFACE
61150 LOMF on $UNIT, $INTERFACE
61151 AIS on $UNIT, $INTERFACE
61152 RDI on $UNIT, $INTERFACE
61250 IPCP failure
61251 LCP failure

61252 PPP interface down
CCM fault level $LEVEL, prio $PRIORITY,

61410 cause $CAUSE
ETH AIS fault on $UNIT, $INTERFACE, level

61411 $LEVEL, MAC $MACADDRESS
61605 BFD-$BFDID down in ingress
61606 BFD-$BFDID down in egress
Auto-negotiation mismatch on $UNIT,

61607 $INTERFACE
RTT threshold crossed on TWAMP-

61610 $TWAMPID
PLR threshold crossed on TWAMP-

61611 $TWAMPID
61622 MLPPP link degrade
Dup Addr detected-

61632 $DUPLICATEIPV6ADDRESS
61639 IPsec emergency bypass active
IP Traffic Capturing ongoing $UNIT,

61641 $INTERFACE, $MACADDRESS
61643 IPsec tunnel switchover

61644 IKE authentication failure
61645 IKE SA failure
61646 IPSec SA failure
61647 IPSec expert mode activated
61654 IPsec FQDN failure
CCM MAC mismatch MEP $ID, MDL

61655 $LEVEL, MA $MAID, MAC $MACADDRESS
61657 IPsec Tunnel Endpoint is not unique
Ethernet link switchover in link aggregation

61662 group $STATUS
61663 PS tunnel Switchover
71106 TROUBLESHOOTING DATA RECEIVED

Probable Cause Event Type Default Severity
Indeterminate x5 Critical,Major
Indeterminate x4 Warning
Indeterminate x4 Critical,Major,Minor
Indeterminate x3 Critical,Major,Minor
Indeterminate x4 Minor
Indeterminate x4 Major
Indeterminate x4 Critical,Major,Minor,Warning
Indeterminate x1 Indeterminate
Indeterminate x0 Critical
Indeterminate x0 Warning
Alarm Severity Information Meaning
A fault has been detected in the base station

hardware.
The problem causes a base station unit/service to
be degraded or faulty.
Critical Check the reason for the fault from the
Major supplementary text field of the alarm.
The base station device or base station itself is

being automatically reset to recover from a fault.
Check the reason for the fault from the
Warning supplementary text field of the alarm.
Critical The service/device has been blocked by the user.

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

antenna line device. It may be a hardware or
software failure.
A
be fault has occurred
degraded or faulty.in the cell service. For
Critical example: MIMO
Check the reason (Multiple Inputfrom
for the fault Multiple
the Output)
Major does not work, interferences
supplementary text field of the inalarm.
the cell are
detected, beamforming calibration fails in the cell,
there are not enough internal processing
resources in the base station to support the cell,
there is not enough hardware detected to setup
the cell, etc.
A
Thefault has occurred
problem causes aincellthe service
base station
to be service
degraded
that does not affect basic services of the base
or faulty.
Critical station,
Check the or the operator
reason for theis fault
notified
fromabout
the
Major suggested
supplementary manual
textintervention. Each fault with
field of the alarm.
minor or warning severity, that is, fault that has no
impact on basic base station services, no matter if
it is hardware, software, configuration,
synchronization etc., is reported as BASE
STATION INFORMATION. The only exception to
this are the transmission faults 61xxx: Minor and
warning severity transmission faults are reported
Minor as transmission alarms instead of BASE
Warning A fault hasINFORMATION
STATION occurred in the alarms.
base station service
that affects basic services of the base station. If a
fault may have various root causes,(for example,
hardware problem, software problem or
configuration problem, etc.), this type of alarm is
reported because more specific alarm assignment
is not possible.
The problem causes a cell service to be degraded
Critical or faulty. Check the reason for the fault from the
TRX has been blocked by user via BTS Element
Minor Manager.
A fault has occurred in the base station security

functionality.
Check
This is the reason for
a temporary the fault
alarm from thelate churn
for handling
Critical supplementary text field
in the release. Please see of the alarm.
Major This
(1) additional information fields in the of
alarm is applicable independent the value
alarm to
Minor of parameter actCategoryAlarms.
determine the BTS temporary fault that raised this
Critical alarm and the (2) reported dynamic severity in the
Major
Alarm severity depends on the alarm to determine the urgency of the issue.
Minor
source fault severity. Possible This alarm is applicable independent of the value
Warning
values: of parameter
O-RAN actCategoryAlarms.
compliant RU is able to report vendor
Critical specific
An O-RAN fault. BTS is not
compliant RUable
mayto determine
report a faultthe
Major
Alarm severity depends on the meaning of the problem reported by O-RU.
related to an external device (e.g. Antenna Line Check
Minor
source fault severity. Possible the
Device). In such case the source of the alarmby
reason for the fault from the data provide is
Warning
values: the BTS, itand
unknown includes
the BTStheisdata
not received from O-RU.
able to determine
Critical the meaning of the problem. The reason for the
Major fault may be checked from the data provide by
Minor the BTS that include the data received from the
Warning O-RU.
This is an external user-defined alarm. The alarm

Minor is defined by the user in a hardware database.



is defined by the user in a hardware database.
Not applicable to Flexi Zone Micro platform and
Minor Flexi Zone platform.









is defined by the user
Minor in a hardware database.

is defined by the user
Minor in a hardware database.
A fault (or faults) has occurred in the BCF.

For details, refer to GSM/EDGE BSS Operating
Critical Documentation.
A fault has occurred, which either does not affect
the SBTS operation, or the fault does not allow
OSC(Orthogonal Sub Channels)/DFCA(Dynamic
Frequency and Channel Allocation) feature to
Minor work.
Major A critical fault has occurred on a TRX.
Major A fault has degraded the operation of TRX.
A critical fault (or faults) has occurred in the base

station. Check the reason for the fault from the
Critical supplementary text field of the alarm.
A major fault (or faults) has occurred in the base

A minor fault (or faults) has occurred in the base

Minor, Warning supplementary text field of the alarm.
A critical fault (or faults) has occurred in a unit (or

units) that belongs to the sector indicated in the
alarm. Check the reason for the fault from the
A critical fault (or faults) has occurred in a unit (or
alarm. Check the reason for the fault from the
A major fault (or faults) has occurred in a unit (or

alarm. Check
This alarm the reason
is raised whenfor the fault
either no orfrom
an the
Major supplementary
incompatible text field
signal of the alarm.
is received on the interface
referenced in the alarm text.
$UNIT indicates the affected module from
Equipment Management (last element of the DN).
A minor
E.g. fault (or faults) has occurred in a unit (or
SMOD-1.
units) that belong
$INTERFACE to the the
indicates sector indicated
interface in the
on the
alarm.
module following the labeling on the frontplate of
the real HW or the corresponding parameter in
Check the reasonModel.
the Management for the fault from the
Minor, Warning supplementary
E.g. EIF1,fault
A critical text field has
IF1 (or faults) of the alarm. in the base
occured
station interface.
With
Check anthe
Ethernet
reasoninterface, thefrom
for the fault physical
the Ethernet
link is detected text
supplementary to befield
down. All other transmission
of the
Critical alarms
alarm. related to this signal are suppressed.
Probable causes for Ethernet interfaces:

- a cable/fiber is cut or there is no cable/fiber
connected to the interface
- the electrical/optical signal is excessively
attenuated
-Athe major
portfault (orconnected
at the faults) hasfar occured
end node in the
is base
station interface.
switched off Check the reason for the fault
Major -from
the the supplementary
advertised technology textcapabilities
field of the withalarm. auto-
This loss of of
negotiation frame
both alarm
devices is raised
at the when
Ethernetthe link
local
do
A fault (or
receiver is faults)
unablehas occurred
to detect the in the base
frame station
alignment
not match
connectivity/interface. Check the reason for the
word
-fault of the E1technology
the from
Ethernet signal. All other at both transmission
devices at the
alarms the supplementary
related to this signal textsuppressed.
are field of the
Critical, Major Ethernet
alarm. link is forced manually and not
compatible
Equipment
- the remoteManagement
peer of an Ethernet (last element
link is of
notthe DN).
auto-
E.g. TRMOD-1.
negotiation
The alarm iscapable
$INTERFACE raised
indicatesiforthe
has
the
auto-negotiation
monitored
interface service
on the is
Main power
function
unavailable is lost
disabled
when by and
for the SBTS
configuration
example all is running
network on
paths
Minor module
Battery following the labeling on the frontplate
backup. of
are
the unavailable.
real HW or theThis implies that all
corresponding individualin
parameter
Probable
BFD sessionscauses for PDH
of the interfaces:
respective group
the Management
- a cable is cut or Model.
there is no cable connected to
represented
E.g. EIF1, IF1 by $BFDGRPID are erroneous.
the interface
Critical -Example(s)
the electrical
forsignal
alarm is excessively attenuated
text:
Example(s)
- the port at for
thealarm text: BFDGRP-10
connected "LOF onnode
far end
down
TRMOD-1,
is
IF2"
switched off
- transmit and receive cables are mixed up
Probable cause: The interface at the far end is
Critical not configured
Examples to betext:
for alarm a framed E1 interface.
Ethernet: "LOS on SMOD-1, EIF2"
or
"LOS on TRMOD-1, EIF3"
Critical PDH: "LOS on TRMOD-1, IF2"
-$UNIT
There
$UNIT Critical isindicates
no
Event:
indicates response the affected
either
the affected to
anthe Erroredmodule
requests
module Symbolfrom
sentPeriod
from to the
Equipment
peer,
Event, neither
an Management
Errored during the
Frame IKE(last
Event, element
an Errored
Equipment
of the DN). Management
E.g. SMOD-1. (last element of the DN).
SA
Frame
E.g. setup, Period
TRMOD-1. the IPsec
Event, SAor an setup, nor during
Errored FrameDPD.
$INTERFACE
Note:
Seconds When Summary indicates
IPsec backup
Event the interface
tunnel
was on the
feature
detected. is
$INTERFACE
module following indicates
the the interface
labeling on the on the
enabled,
-module Dying Gasp: this
following alarm
either the isthe not raised
local on
labeling or thethe remote
frontplate peer of
frontplate
due
has atofatal oferror
failures thewhenreal
and HW
trying
is aboutorto the corresponding
setup
to restart.primary IPsec
the
parameter real HW or
inthe the
thelocal corresponding
Management parameter
Model. a in
-tunnel
the Link in "Secondary_Active_Probing_Primary"
Fault:
Management Model. peer has detected
E.g.
state.
physical EIF1, linkIF1 fault in receiving direction, for
E.g. EIF1, IF1
NOTE:
example,
$LOOPTIMEOUT The a alarm
LOS. is not raised
indicates the for
time IPsec
period tunnels
in
Probable
configured
Note: causes:
with "IKEthe SAinserted
connection establishment
minutes
- No SFP after
module which isOAMPDU
inserted loopback shall
Major mode"
In
terminate case set to responder
a received
automatically. only.inhas themore SFP-basedthan one
SFP
critical
A slot.
loopback event flag
is requestedset, the following
for will be
-On The
reported anSFP interface
in module's
the for which
alarm: interface theanLink Ethernet
contacts OAMare interface
either
Example(s)
functionality locally forat
was the
alarm BTS,
switched text: or the
on,eitherLink OAM
no set|Critical
Link OAM client
PDUs of
corroded
Link
the BTSFault isorbit
set dirty,
setinto preventing
|Dying
loopback Gasp bit
mode by the Event
remote
"Interface
were
read received
access under toduring
thetest SFP ontheTRMOD-1,
period or
module of 5 IF2 for 2
seconds.
preventing
Minor bit
Linkset|
minutes" OAM Reported
peer.
detection x of the module.x x
$UNIT
This alarmindicates
is
Link raised
Faultthe when affected the module
measured frombit error
$UNIT
Equipment indicatesManagement the affected module from
Example(s)
rate
Equipment exceeds
x forthe alarm
Management threshold text:x (last
(last
element
value
elementof BER-3 (10E-
of
"Missing
3). the DN). SFP
LinkE.g. SMOD-1.
module
Fault on SMOD-1, EIF2" or
of the DN).
$INTERFACE E.g. SMOD-1.
indicates
Critical "Missing
$UNIT
$INTERFACE x SFP
indicates module
the
indicates onxthe
affectedthe
interface
TRMOD-1,module EIF3"
interface
on the
from
on the
module
Equipment following
Management
Link Fault the labeling (last onon the
element of the DN).
module
frontplate following the labeling
of the real HWx or the corresponding the
E.g.
frontplate TRMOD-1.
x ofinthe real HW or theModel. corresponding
parameter
This
$INTERFACE alarmDying is theraised Management
indicates
Gasp when the aninterface
alarm indication
on the
parameter
E.g. EIF1 in the Management Model.
signal
module
Always isthereceived.
following
latest the This
received signal
labeling is generated
on
critical the eventby
linkfrontplate is anof
Major E.g. EIF1
intermediate
the
reported. real HW orPDH the device
corresponding in the forward
parameter direction
in
Examples
because
the
$UNIT Management it for
detects
indicates alarm atext:
Model.
the problem module
affected in its receivedfrom
Ethernet:
signal.
E.g.
Equipment EIF1, IF1 "Link OAM link
Management (last element lost on SMOD-1, EIF2"
or
of thelossDN). E.g. SMOD-1.
Major This
"Link
AIS OAM
defect ofis multiframe
link lost on TRMOD-1,
detected alarmthe
when is raised EIF3"
incoming if the signal
Probable
$INTERFACE
interface causes:
referenced indicates in thealarm
the interface text on
has the
lost the
-has the two
signal
module following
multiframe
or less
level
alignment.
zeros
is too in each
low
the labeling on the of two
(connectors consecutive
or cables
double
are
frontplatedirty, frame
electrical
of the periods
real (512
connectors
HW orbits)
the according
orcorresponding
cables are [G.775]
$UNIT
chapters indicates
5.2 and the
I.2. affected module from
corroded)
parameter
Equipment in the Management
Management Model. of the DN).
(last element
Major -E.g.
E.g. the specified
EIF1
TRMOD-1. maximum length of the cable is
A
All malfunctioning
exceededother transmission of thealarms SFP transceiver
related to this wassignal
$INTERFACE
detected. indicates the interface on the
-are thesuppressed.
module connector
following is the
not labeling
properlyon connected
the frontplateto theof
The
unit SFP has reported a transmission fault
the realindicates
condition
$UNIT HW andoror the
has the corresponding
disabled
affectedthe laser
module parameter
from in
-thetheManagement
receiver the
Model.far-end transmitter has failed
Critical transmitter.
Equipment
-E.g.
the EIF1,
accumulated Management of(last element of the
E1 DN).
This alarm is
IF1 raisedBER when athe end-to-end
remote defect path
E.g.
is too TRMOD-1.
high
indication is received. It is sent by the
$INTERFACE
intermediate orindicates
the far-end theequipment
interface on the
because it
Probable
module cause:
following The
the interface
labeling ontype the has not been
frontplate
Example(s)
detects
configured a serious
tofor alarm
meet fault
the text:
in "EBER
the received
framing of on
the signal. of
TRMOD-1,
interface at
Major the
IF2"
$UNIT realindicates
HW or the thecorresponding
affected module parameter
from in of
the
the far end. For E1
Management interfaces,
Model. the configuration
Equipment
the far-endIF1 Management
node should be (lastE1element
Multiframe. of the DN).
E.g.
E.g. EIF1,
TRMOD-1.
$INTERFACE
Example(s) forindicates
alarm text:the interface on on the
Probable
module cause:
following There
the labeling is a"LOMFtransmission TRMOD-1,
on the frontplate problem of
Major IF2"
somewhere
the real HW or the corresponding parameter inthe
in the intermediate network along
E1
the path
Management and AIS is sent instead of user traffic.
Model.
E.g. EIF1, IF1
Example(s) for alarm text: "AIS on TRMOD-1,
Major IF2"
Probable cause: The far end has a LOS, LOF or
AIS alarm on its receiving interface.
Example(s) for alarm text: "RDI on TRMOD-1,

Major IF2"
This alarm is raised when the localIPAddress

Critical negotiation
This alarm iswith the peer
raised fails.
if local and peer ends
disagree on the LCP configuration leading to LCP
negotiation failure.
The related configuration parameters are :
Major acfcTarget, localMruTarget, pfcTarget.
and AIS is enabled, it will trigger an AIS alarm
CCM
containing not received
the clock from at-least
following information: one of the remote
The
MEPs expected
since 3.5 times mode the of synchronous
configured CCM
-Ethernet
receiving is interface
the slave in case an Ethernet interface
interval
-isMD period.
level as sync source to the SBTS
Ex: entered
CCM MAC fault level 5 prio 3 cause
-synchronization
Source address
priority list. Only applicable to
REMOTE_CCM_DEFECT
$UNIT indicates theonly affected module from
1000Base-T,
7. since
REMOTE_DEFECT_INDICATION, with this Ethernet priority 1
Equipment
This alarm
technology Management
is raised
both link if the
partners (last
PPP element
interface
have to ofisthe
negotiatenotDN).
(lowest
E.g. priority):
TRMOD-1. An RDI flag is detected in the
operational
the
CCM clock
frames mode. either
from when
one remote all the peer.
PPP-links in the
$INTERFACE
ML-PPP
Probable interface
causes: indicates
are not the interfaceoron
available thethe PPP-
Example:
module CCM fault
following the level
labelling 5 prio on 1the
cause front plate of
link
-Linksupporting
speed downshift: a cable is not of not
REMOTE_DEFECT_INDICATION the SL-PPP interface is sufficient
Critical the realtoHW
available.
quality supportor thee.g. corresponding
Gigabit parameter in
Ethernet
The
the alarm text provides
Management Model.following additional
technology,
information:- but sufficient to support Fast Ethernet
E.g.
-Link
The IF1
speed
alarm isdownshift:
raisedthe if the a cable
BFD has just
state two wire
for the
$LEVEL
$LEVEL indicates
indicates the MD MD level
level.
pairs
sessionconnected,
&PRIORITY is not which
AdminDown
indicates is sufficient
and,
the alarm for Fast
nevertheless,
priority no
$MACADDRESS
Ethernet,
BFD packet butisnot indicates
for
received Gigabit
at thethe corresponding
Ethernet.
local endalarmduring the
Major $CAUSE
'macAddr' indicates
parameter the condition
in the of the
-Clock
detection mode time. mismatch: Linkobject
partner model.
has
advertised
$BFDID itself
indicates that it
the the wants
BFD to operate
identifier. in slave
The
clockalarm
modeisfor
Example(s) raised
alarmif in
resulting text: BFD
negotiated stateclock
of themode session
is not
"ETH
"master"AdminDown
AIS at fault on and
TRMOD-1, the BFD packet
EIF1, level from
l, the
mac
Example
far end forthe
contains alarmlocaltext:
the
Ethernet interface (or vice
diagnostic code = 'Control
Major aa:bb:cc:dd:ee:ff"
versa).
"BFD-10 down
Detection
$UNIT Timein
indicates
ingress"
Expired'
the affected and no BFD from down
The source
Ingress alarm and is destination
present. IPmodule
addresses will be
Equipment
displayed inManagementalarm diagnostic (last info
element
field. of the DN).
E.g.
SourceSMOD-1.
IPfor addr $BFDSCRIPADDR
Example
$INTERFACE alarm text: the interface on the
indicates
Major Dest
"BFD-10IP addrdown $BFDDESTIPADDR
in egress"
module following the labeling on the frontplate of
The source
the real HWand or thedestination
corresponding IP addresses
parameter willinbe
displayed in
the Management Model. alarm diagnostic info field as below:
"Source
E.g. EIF1, IPIF1 addr $BFDSCRIPADDR, Dest IP addr
Major $BFDDESTIPADDR"
Example(s) for alarm text:
During the IP address
"Auto-negotiation configuration,
mismatch on SMOD-1, before EIF2"
The alarmof
allocation is new
activatedIPv6 when the IP traffic
addresses,
or
capturing
the network session
element is started.
tests with
Major "Auto-negotiation mismatch on DAD
TRMOD-1,(Duplicate
EIF3"
The
AddressSBTS is currently
Detection) thecapturing
direct IP traffic towards
The
a RTT
local
attached portthreshold alarm
or into anetwork
transport file iswhether
raised inthe case the
other
average
on value of the
the SBTS.
already-configured RTT forelements
network this TWAMP
session
If
on the fromcapturing
thetraffic
network theuse lastthe 1-min
is same period
IPv6 equals
happening towards
addressesora on
Major exceeds
local port,the
their network theconfigured
port
IP threshold.
and destination
interfaces including
MAC address needs
the Link-Local. The DAD to bedetects
provided. those duplicated
$UNIT
IPv6 indicates
addresses
The alarm is raised the affected
andifprohibits
the packetmoduleloss from
ratio equals
Equipment
the operation
or exceeds Management
this IPv6 (last
theofconfigured element
address
threshold in value
the network
during
Critical of
thethe
element. DN).
current The E.g. SMOD-1.
Alarm
observation contains
interval of 15 minutes.
$INTERFACE
the corresponding indicates the interface
IPv6 address on the
the system
module
attempted following
to allocate the labeling
based on onthethe
This alarm
frontplate
manual ofistheraised
configuration realifHW at least
or theone
options. theofalarm
the PPP-
If corresponding is
links belonging
parameter
reported forinthe to
theIP the
interface, Model. is not
ML-PPP
Management interface
Major operational.
E.g.
it willEIF1,
showIF1 the Link-Local IPv6 address the
$MACADDRESS
system failed to allocate. indicates the corresponding
'macAddr' parameter in the object model.
Example for alarm text: Dup Addr detected
Minor Example(s) for alarm text:
2001:0db8:85a3:0000:0000:8a2e:0370:7334
"IP Traffic Capturing ongoing on SMOD-1, LMP,
aa:bb:cc:dd:ee:ff"
SBTS has Capturing
"IP Traffic entered IPsec ongoingemergency
on SMOD-1, bypass EIF2,
active state
aa:bb:cc:dd:ee:ff" where configured IPsec policies are
Major This
ignoredalarm
and will
all be triggered
traffic is sent when at least one
unprotected.
"IP Traffic
primary IPsecCapturing
tunnel ongoing
fails, andon BTSTRMOD-1,
has switchedEIF3,
aa:bb:cc:dd:ee:ff"
over to secondary IPsec tunnel or PS tunnel.
Example
As a resultforofalarm
failuretext in least
in at file mode:
one primary IPsec
Minor "IP Traffic Capturing ongoing"
tunnel, BTS has automatically switched over to
secondary IPsec tunnel or PS tunnel terminating
on secondary security gateway.
Note: PS tunnel is not supported in standalone
Major 5G classical BTS.
- NO_PROPOSAL_CHOSEN
- INVALID_SYNTAX
- INVALID_MAJOR VERSION
- INVALID _IKE_SPI
- INVALID_MESSAGE_ID
-This UNSUPPORTED_CRITICAL_PAYLOAD
alarm is raised when the SBTS sends or or
FAILED_CP_REQUIRED
receives following notification as response to an
-->
IKE_AUTH When the SBTS
orraised sends or receives
CREATE_CHILD_SA a failure
request
The
notification alarm isas response whentothe an IKE authentication
IKE_AUTH request
message.
credentials provided by the peer include:
message.The
The failure notifications
Major is notfailure
-- INVALID_SYNTAX valid.notifications includes the following:
NO_PROPOSAL_CHOSEN
-- INVALID_MAJOR
TS_UNACCEPTABLE VERSION
-- INVALID
INVALID_SYNTAX _IKE_SPI
-- INVALID_MESSAGE_ID
INVALID_MAJOR VERSION
Major -- UNSUPPORTED_CRITICAL_PAYLOAD
INVALID
This alarm _IKE_SPI
is triggered when ETH-CC is enabled
-and INVALID_MESSAGE_ID
local MEP receives a valid ETH-CC frame
-The
fromUNSUPPORTED_CRITICAL_PAYLOAD
alarm
remote is MEP
raisedwith under below MAC
a source conditions
Addressfor a
-different
SINGLE_PAIR_REQUIRED
link aggregation
to its manually group when or or previously
configured
Major FAILED_CP_REQUIRED
the primary
learned MAC link fails.
address.
1.
It
The After
contains
IPSecsuccessful
the
expert switchover
following
mode fromactivated
information:
has been primary to
The
$ID alarm is
secondary
indicates raised
link.the if primary,
remote MEP secondary
Id configuredor by
PS
the
tunnelBTSEM.
IPsec The
FQDN IPSecfails expert
to mode
resolve or allows
service
2.
underSwitchover
advanced Maintenance failed Association(MA).
configuration when forsecondary
testing andlink is not
trouble
provides
accessible.
$LEVEL invalid
indicates response.
the Maintanence Domain Level
Minor shooting
Failed purposes.
FQDN details will be displayed in alarm
(MDL).
The alarm is raised under the following
diagnostic
$STATUS
$MAID info
indicates
indicates field
theas below:
ifMaintenance
the switchover is
Association Id.
conditions:
"Remote
"successful" tunnel Endpoint
or "failure".
$MACADDRESS
1. indicates the
IKEP instances are configured with local tunnel source MAC
$remoteTunnelEndpoint,
address in remote
the CCM frame received from remote
Major end point, for alarmtunnel
$remoteTunnelEndpoint2"
Example text: endpoint FQDN(s) or IP
MEP.
address
"Ethernetand link switchover in link aggregation group
2. Local tunnel and remote tunnel end point IP
successful"
Example(s)
address for alarm are
combination text:not unique across IKEP
The
"CCM Ethernet
MAC link $ETHLK
mismatch MEPdetails
1111, and
MDLcause
1, MA 15,
instances.
$CAUSE will be displayed in alarm
Minor MAC
Non-Uniqueaa:bb:cc:dd:ee:ff"
RTEP
diagnostic info field details
as below: will be displayed in
alarm
" From $PRIMARY_LINK to below:
diagnostic info field as
"Remote
$SECONDARY_LINK tunnel Endpoint , $CAUSE". $CAUSE
indicates
Major $remoteTunnelEndpoint2"
either "LOS" or "LACP failure".
E.g: From MRBTS-1/TNLSVC-1/TNL-1/ETHSVC-
1/ETHLK-1 to
MRBTS-1/TNLSVC-1/TNL-1/ETHSVC-1/ETHLK-2
Minor , LOS
This alarm will be triggered when switchover

Major happens to public safety tunnel.
Indeterminate Troubleshooting file is received from the NE.

Effect Identifying Additional Information Fields
The effect of the fault on the functioning of the

network element depends
on the fault description. For more information, see
base station fault List of cells made faulty or degraded by the fault. Path of
descriptions in SRAN System Libraries. the hardware unit.
The effect of the alarm on the Network Element

depends on the fault description. For more
information, see base station fault descriptions in
SRAN System Libraries. Path of the hardware unit.
The service/device is blocked by the user. It is not

possible to establish phone calls through the List of cells made faulty or degraded by the fault. Path of
blocked cell, module or BTS. the hardware unit.
The effect of the alarm depends on the purpose

that was configured for
the user-defined alarm input in the BTS. Path of the hardware unit.

on the fault description. For more information,
see base station fault
descriptions in SRAN System Libraries. List of cells made faulty or degraded by the fault.

see base station fault List of cells made faulty or degraded by the fault. Path of
descriptions in SRAN System Libraries. the hardware unit.
The effect of the fault on the network element
depends on the fault description. For more
information, see base station fault descriptions in
SRAN System Libraries. List of cells made faulty or degraded by the fault.

network element depends on the fault
description. For more information, see base
station fault descriptions in SRAN System List of cells made faulty or degraded by the fault. Path of
Libraries. the hardware unit.

description. For more information, see base
station fault descriptions in SRAN System List of cells made faulty or degraded by the fault. Path of

description. For more information, see the base
station fault description in SRAN System List of cells made faulty or degraded by the fault. Path of

station fault description in SRAN System
Libraries.

station fault description in SRAN System
Libraries. Path of the hardware unit.

station fault description in SRAN System List of cells made faulty or degraded by the fault. Path of
see base station fault For details, refer to GSM/EDGE BSS Operating
descriptions in SBTS System Libraries. Documentation.
The effect of the fault on the functioning of the 1. rack (cabinet) number
network element depends on the fault 2. shelf number
description. For more information, see base 3. slot
station fault descriptions in SRAN System 4. type of unit
Libraries. 5. unit number
6. subunit number
The effect of the fault on the functioning of the 7. path
network element depends on the fault 8. supplAlarmInfo (contains the real Alarming Object and
description. Alarm Name)
Effect of this alarm depends on reported vendor

specific fault. Operator must check source fault
meaning in O-RU vendor specification.
Effect of the alarm depends on the details

reported by the O-RU.

that was configured for the user-defined alarm
input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.
input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.
input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

the user-defined alarm input in the BTS.

the user-defined alarm input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.
input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.

input in the BTS.
input in the BTS.

input in theofBTS.
The effect the fault on the functioning of the
descriptions
The effect of in SBTS
the fault System Libraries. of the
on the functioning Documentation.
descriptions
descriptions
1. Rack (cabinet) number
2. Shelf number
3. Slot
4. Type of unit
5. Unit number
The effect of the fault on the network element 6. Sub-unit number
(NE) function depends on the fault description. 7. Path (for alarms where the type of unit field contains
For more information, see base station fault one of the following values: FSM, FT, FSP, FBB, FR, FAN,
descriptions in LTE System Libraries. AntennaLine, MHA, RET, FYG, SFP, ASIA, ABIA)
2. Shelf number
3. Slot
4. Type of unit
5. Unit number
The effect of the fault on the function of the 6. Sub-unit number
network element (NE) depends on the fault 7. Path (for alarms where type of unit field contains one of
description. For more information, see base the following values: FSM, FT, FSP, FBB, FR, FAN,
station fault descriptions in LTE System Libraries. AntennaLine, MHA, RET, FYG, SFP)
2. Shelf number
3. Slot
4. Type of unit
5. Unit number
station fault descriptions in LTE System Libraries. AntennaLine, MHA, RET, FYG, SFP, ASIA, ABIA)
2. Shelf number
3. Slot
4. Type of unit
5. Unit number
2. Shelf number
3. Slot
4. Type of unit
5. Unit number
2. Shelf number
1.
3. rack
Slot (cabinet) number
4. Type of unit
2.
5. shelf number
Unit number
network element (NE) depends on the fault 3.
7. slot
Path (for alarms where type of unit field contains one of
station fault descriptions in LTE System Libraries. 4. type of unit MHA, RET, FYG, SFP, ASIA, ABIA)
AntennaLine,
5. unit number
6. subunit number
The effect of the fault on the functioning of the 7. path (for alarms where field "type of unit" contains one
network element depends on the fault description. of the values: FSM, FT, FSP, FBB, FR, FAN,
For more information, see base station fault AntennaLine, MHA,
1. rack (cabinet) RET, FYG,
number
descriptions in LTE System Libraries. SFP, ASIA, ABIA)
2. shelf number
3. slot
4. type of unit
5. unit number
6. subunit number

2. Shelf number
The effect of the fault on the network element 3. Slot
(NE) function depends on the fault description. 4. Type of unit
For more information, see base station fault 5. Unit number
descriptions
The effect of in LTE
the System
fault on theLibraries.
functioning of the 6. Sub-unit number
network element depends on
the fault description. For more information, see
base station fault descriptions
in
TheLTE System
effect of theLibraries.
fault on the functioning of the
network
No data element depends is exchanged via this
or clock information
on
interface. Possible impactFor
the fault description. onmore information,
the connections
see base
over station fault
this interface: For details, refer to GSM/EDGE BSS Operating
- voice calls or data connections are aborted and
cannot
The be established
communication linkanymore
between theoverlocalthis
SBTS
Possible impact on the connections
and the
interface: BFD peer is defective. No communication
-isremote
possible.management connectivity is lost and
-cannot
no calls
beare possible anymore
established
- loss of remote management access to other
network elements
- loss of synchronization if the interface is used as
-a loss
synchronization sourceif the interface is used as
of synchronization
a synchronization source
- Depending on use of the Ethernet interface, the
above described impact can occur for the local
SBTS and/or other (S)BTS elements if they are
chained via the Ethernet interface.
at all.
The Ethernet Link is down.
An Ethernet Link cannot be successfully
established.
No Ethernet data or clock information is
exchanged between this interface.
Possible effects:
- no calls are possible
Possible impact management
- loss of remote on the connections
accessover this
to other
interface:
network elements
- Voice
IKE SAscalls
andorIPsec
data connections
SAs cannot cannot be
be established
established.
or re-keyed
- Remote management connectivity cannot be
established.
- Loss of synchronization if the interface is used
The
as a interface cannot source.
synchronization be used for transmission. It
can be used for connectivity checks interface,
- Depending on use of the Ethernet only. the
above-described impact can
occur for the local BTS and/or other BTS
elements if they are chained through
the Ethernet interface.
Normal traffic is interrupted. Only loopback OAM
frames are transmitted and received over the
interface. If the test frame generator is switched
on, test frames are transmitted.
The Ethernet interface might be out of order, or

the remote peer might be out of order. Traffic
might get lost.
The Ethernet interface is defective, or the remote

peer is defective. Traffic might get lost.
The SFP is not operational.

Possible impact:
- slow management access to the SBTS and
other network elements in the network
- poor voice quality and data performance
The performance management data collected on

this interface
Possible becomes
impact on the invalid.
connections over the
interface in question:
network
Possibleelements
impact oninthe
theconnections
RAN over this
interface:
network elements in the RAN
Possible impact on the connections over this
interface:
Possible impact on the connections over this PPP
-link:
the SL-PPP/ML-PPP interface is not available.
-- loss of remote
in case management
of SL-PPP, access.
the interface is not available.
In case of ML-PPP, the interface is degraded (as
long as at least one link is available).
network elements in the RAN.
Impact on the connections over this interface:
- loss of remote management access.
The transport connection toward the remote peer

might be defective. Traffic might get lost.
The Ethernet Link got established with an
unexpected clock mode or technology.
The transport
Possible impactconnection towards the
on the connections remote
over this
peer may
interface:
The be defective. Traffic may get
communication link between the local lost.and
the remote peer is defective or the peer is
-defective.
Increased packet delay variation and increased
average
Transportdelay for may
service all voice/packet and and calls
not be available
management
may be dropped.connection
- Increase of packet loss due to congestion.

The communication link between the SBTS and
the BFD
- Loss of peer is defective.Transport
synchronization/Timing service
source lost may
with
not be available and calls may be dropped.
Timing over Packet (IEEE1588v2) due to
increased packet delay variation.
- Loss of synchronization/Timing source lost with

Synchronous Ethernet.
This alarm is an indication that the backhaul
capacity foristraffic
This alarm with the that
an indication same profile
the as this
backhaul
TWAMP
capacity for traffic with same profile as this may
session (DSCP value, packet size)
be too small,
TWAMP sessionbecause
(DSCPthevalue,
measurement packets
packet size), may
are scheduled later than before.
be much too small, because some of the
measurement packets seem to have been thrown
away.
The TWAMP measurement packets are lost
because of degraded traffic throughput.
The local peer will not be able to go "online" as

The
thereML-PPP interface operates with reduced
is already
capacity.
a remote peer operating with the IP address the
local peer intended to go "online".
The remote peers continue their operation without

disruption.
All configured IPsec policies are ignored and all

the SBTS traffic is sent unprotected.
The resulting packet capture files can used for

Expert analysis to identify network problems and
to help determine the best course of action.
SBTS traffic has switched over from the primary

IPsec tunnel to secondary (backup) IPsec tunnel
terminating on secondary security gateway.
The IKE SA cannot be established.
IKE SA cannot be established and subsequently

no IPsec SAs can be established.
The related IPsec SA can't be established and

used.
This alarm alerts technicians to the fact that the
expert mode is active and any expert mode
associated configuration changes may cause
IPSec instability or failure.
Given FQDN is not used to connect to the service

or service does not work.
None
It is not possible to send traffic for IPsec tunnels

which have not
The primary linkbeen established.
between the local BTS and the
peer is defective. The communication
is possible only through secondary link when link
aggregation switchover is
a SUCCESS.
SBTS traffic has switched over from the primary

IPsec tunnel or secondary (backup) IPsec tunnel
to public safety tunnel.
The file is available in NMS disk. Troubleshooting file name, TRSHId

Additional Information Fields
Serial Number of the hardware unit.
Destination IP address.

Serial number of the hardware unit.

Documentation.
Serial Number (when applicable)

Documentation.

Documentation.

Documentation.

Documentation.
Destination IP address
Destination IP address

Documentation.
-
MEANING
the
Performrole
Controlled of
thethe slave
Oscillator
steps module.
below(OCXO) in the This
output fault
listed and means
order the that
thethe
reference
until FR
faultphaseis blocked.
provided by
disappears:
1408
cable.
alarming
The : EFaultId_ExtAl8
Communication
transportmodule. path failure(SCTP) for connection between gNB-CU and gNB-DU
When
the
1.
3. CPRI
Reset
Check
INSTRUCTIONS
1424 an LTE
theIr FSM/ASIx
interface
System exceeds
Module plays or the
theABIC role
limit
the parameters related to M3 interface in the BTS and MME.
: EFaultId_ExtAl24 of
of
module. the
50ns. master, or an LTE system
has
module
2. failed
Replace sharestothe beSystem
aestablished.
CPRI/Ir radio
Module This might
module
or ABIC be
with because
module.an SCDMA of an unplugged
system module cable
Replace
FAULT
INSTRUCTIONS IDthe alarming Radio Module.
between
(dual mode
INSTRUCTIONS
4. Reset them. There
theconfiguration),
BTS. is no transport path
and the FR is blocked, fault available to continue operation
MEANING
1806
1.
on the: EFaultId_CommunicationFailureAl
Refrain faulty from requesting
connection any
between procedure
gNB-CU which
and involves
gNB-DU. restarting of the
48:EFaultId_UnitBlockedAl
1.
The Check if
statemodule other
of the external alarms are
alarm isactive
detected,
line in thenot
shows LTE 1931.
that BTS or SCDMA
analarming
external alarm BTS. isis
alarming
Note:
2. Check The the fault can
optical (forbe example,
cancelled,
connection SW whenupdate)
between unblock
the until
SCDMA operation and module
will
LTE beBTS.
notified.
MEANING
FAULT
replaced.
INSTRUCTIONS NAME
performed
Replace the byoptical
mastercable system and/or module SFPs. accordingly.
The
PPS
2.
Note:
If communication
sharedreference
ReplacePerform thenot
technology missing
alarming
the with
stepsis the application
module.
below
fALU in the
CDMA, listed
LTE hasRRH failed.
order It has
until
blocking themaynot
alarm replied
be cleared to theby
3.
The If
FAULT this does
NAME
user specifies, help,
during reset LTE
commissioning, BTS. the alarm number, severity, and
message
disappears:
a that
full-unconditional has been
restore sent on and/or
CDMA. resent to it.
4.
LTE If
FAULT
Filter this
polarity ID does
Hardware
NAME
tuning not help,
Accelerator
failure
that indicate the fault. reset SCDMA
Externally BTS.
Triggered Crash
FAULT
5. If this does
Transport
INSTRUCTIONS
1898 : layernot
EFaultId_PpsRefMissAl
help, replace
connection failure FCT.in M3 interface
1. Check
INSTRUCTIONS
FAULT ID the connection between gNB-CU and gNB-DU.
INSTRUCTIONS
Take the following actions to clear the fault:
5G
7002
FAULT
1840 BTS:: EFaultId_ExternallyTriggeredLtefeFatalErrAl
ID
EFaultId_TuningFailureAl
[User-defined]
MEANING
FAULT
2. Check
Instructions
No action NAMEifisthe gNB-CU or gNB-DU is operational.
needed.
6205
1.
5G Ensure: EFaultId_M3SctpEndpointAl
BTS, AirScale that the unit
BTS and/or
FDD, AirScale module is BTS properly
TDD, connected.
AirScale SBTS, If theFlexi unit
Degraded
MEANING boot flash detected
and/or
BTS
3. Check
AirScale FDD,module Flexi
if theFDD,
BTS LEDBTS
speed does
TDD, not
and duplex Flexi light up,
SBTS:
setting the unit
ofhas and/or
the been
VNF module
F1 port is
isBTS faulty.
consistent
FAULT
LTE
MEANING
The
Check
The
FAULT Radio NAME
Hardware
the
reference
ID Module
unit and/or
clock isAirScale
Accelerator unable
module
monitoring
BTS
instance
to tune
that
TDD, crash
to
hasisdetected aAirScale
causingrequired the
a
SBTS,
loss sub-band
alarm.
Flexiproperly
triggered
of PPS signal
by FDD,
external
in the
with
Flexi
PPS
script.
The BTS
reference
transport TDD, path Flexi
from SBTS:
backplane
(SCTP) for missing.
connection to MME has been
(tuning
reference failure),
received or another
from the major
GPS failure has orbeen detected bybroken.
the Radio The
6916
No
reason
Module
FAULT
: EFaultId_BootFlashDegradedAl
action for
(unit
NAME isthisneeded.
can
faulty). be The
an fault
unplugged canreceiver
becable
cancelled,
to
the SyncHub
MME. when No unlockmaster.
transport operation
path is
2.
the
willCheck
switch
be the
performedport fault
that history.
by ismaster
connected system directly
module toconnection
the VNF (for
accordingly. example, they are
FAULT
INSTRUCTIONS
available
Toggling: IDto <Faultpursue name> operation on the faulty with the MME.
INSTRUCTIONS
MEANING
If shared technology is fALU CDMA,
4385
Perform : EFaultId_PpsRefFromBackplaneMissingAl
INSTRUCTIONS the steps below in the listed LTE orderRRH untillocking
the faultmay be cleared by
disappears:
5G
The
both
a BTS,
boot AirScale
flash
"Autodetect"
full-unconditional in the BTS
or both
restore FDD,
alarming "1000
on AirScale
module
Mbit/s
CDMA. BTS
in TDD,
BTS AirScale
theduplex").
Full is degraded. SBTS, At Flexi
least one
1. Reset
INSTRUCTIONS
Replace
FAULT the
ID of System
alarming Module
Radio or
Module ABIx module.
and/or MultiRadio Combiner.
BTS
valid
MEANING FDD,
copy Flexidata BTS still TDD,
exists Flexi
in theSBTS:boot flash memory in the alarming
2. Replace
Note:
4026 :Perform the the
EFaultId_TogglingAl System steps Module
below inorthe
ABIx module.
listed order until the alarm
1.
module.
4.
BTS Checkhas lost ifthe theGPS
the speed1PPSreceiver
and installation.
duplex
reference setting
signal at of thethe 1PPS/ToD
gNB-DU F1backplane port is
disappears.
FAULT
2. Check NAMEthe GPS receiver status.
consistent
interface. with
MEANING
RF
3. Module
Check
INSTRUCTIONS thefilter input power
connection between missing the GPS receiver and the FSM/ASIx.
In
1.
Thisa dual
Checkalarm core
the is configuration,
connection
used to informwiththe where
MME, backplane
particularly,
operator that sync
whether
another between
BTS the M3cores linkisisused,
4.
1.
the Check
Refrain
FAULT
broken.switch NAME
synchronization the from
port cableupdating
that
is or
is
lost connection
SW
connected
by in
secondary eNBtowards
until
directlycore. to a
the SyncHub
the alarming
gNB-DU (forfault
master
module is(the
when
example, replaced.
they
original
FAULT
operating
2.
are Replace fault)
ID asthe isalarming
SyncHubtoggling. slave.
module.
One
FAULT
2. Checkor more
NAMEifthe carrier
thestatusMMEofisthe groups blocked
operational.
1910
5. Check : EFaultId_FrFilterInputPowerMissing SyncHub master.
INSTRUCTIONS
5G
3.
The BTS
Check
alarm configuration
if that
the speedis related failed
and to duplex
the originalsettingfault of BTS M3 port is and
is suppressed consistent
the new with
both
FAULT
In
switch "Autodetect"
casewhich ID
of single
port, which or
core both
scenario
is connected "1000 Mbit/sifFull
check
directly module
to the duplex").providing
BTS, signal is
for example, isbothworking.
alarm,
MEANING is related to fault 4026: EFaultId_TogglingAlFault, raised.
4399
In case
FAULT : EFaultId_OneOrMoreCarriersGroupsBlockedByUserAl
of Dual Core "1000 scenario:
The RF ID
"Autodetect" Module or both filter has a Mbit/s measured Full TX duplex".
power that is too low.
1.
4539Wait : for Secondary
EFaultId_GnbConfigurationFailed Unit reset.
Toggling alarms that are related to the original faults are suppressed until
MEANING
2.
If
the Iftoggling
this it fault
doeshappens not help,right
condition replace afterthe
is cleared. unit one by oneorinathe
a commissioning order below:
configuration change,
INSTRUCTIONS
FAULT
The fault NAMEindicates that the user has blocked one or more GSM TRX of the
a. primary
verify the unit
following (ASIx primary)
configuration data: IP address of the MME.
1.
2M Reset
FAULT
cell external
using the
NAME RF
thereference
BTS HW unit.
Element missing
b.
The
NG
secondary
severity
SCTP of
endpoint
unitthis(ASIx BTS
broken faultManager.
secondary) is the same then as the severity of the original
c. AirScale
toggling subrack
BTS fault.
2. If the ID
FAULT
INSTRUCTIONS problem is still observed after
1899
FAULT
1. :
If the IDEFaultId_2MExtRefMissAl
TRX is locked by BSC, then first unlock the TRX and then unblock
INSTRUCTIONS
7304 : EFaultId_NgSctpEndpointBrokenAl
the
FAULT
1. carrier
Check NAMEthe group faulttoname cancel of thethe fault.
toggling BTS fault.
MEANING
2. If the TRX is unlocked at BSC, then unblock the carrier group to cancel
Inter
The eNB
reference communication failure
clock monitoring has detected a signal loss of 2.048 MHz
MEANING
the
FAULT fault. NAME
2.
The Follow
receivedtransport the instructions
from an
path external
(SCTP) of thethe
reference
for toggling source
connection BTSconnected
fault
between to clearto
gNB the
the problem.
Sync
and AMF In is
GNSS
FAULT receiver
IDof the System signal inaccurate
interface
broken. Module.
This might be caused by an unplugged cable between them.
6284
Note: :Detailed
EFaultId_InterEnbCommunicationFailureAl
information about thetotoggling frequency can beonfound in
There
FAULT isIDno transport path available continue the operation the faulty
the alarm
INSTRUCTIONS
connection history file,
between gNB and AMF. which can be downloaded using the BTS Element
4439
MEANING
Manager. : EFaultId_GnssReceiverSignalInaccurateAl
The the log file is available withlistedSnapshot.
Note: Perform steps below in the order until the alarm
The application has detected a problem with inter-BTS link communication
disappears.
INSTRUCTIONS
MEANING
(SRIO, RP3-01, Ethernet, and so on). Features that depend on the inter-
Note:
The
BTS Perform the
reference
communication, clock steps likebelow
monitoring
the "Inter inhasthe listed
detected
BTS order
Carrier that until
phase theerror
aggregation" alarm of a
feature, are
1. Check
disappears:
reference thesignal cabling from (connected
the external toGNSS
the Sync receiverIn interface).
exceeds 150us, and
disabled.
resets to the GNSS receiver do not resolve the problem.
2. Check if the 2.048 MHz reference source is working normally and the
INSTRUCTIONS
2.048 MHz signal is available.
INSTRUCTIONS
In cases where not enough link throughput has been detected, check the
1.
SFP If another
modulethe synchronization
link speed capabilities reference andisreplacepresent, it ifcheck that itsInphase
necessary. otheris
3. Replace
aligned to the alarming
GNSS module.
signal; check whether the cable delay from the GNSS
cases, no manual
receiver is correctly compensated.
2. Check accuracy of the manually-entered coordinates, if the GNSS
receiver operates in the surveyed mode.
3. If the fault appeared after holdover, check whether the BTS could
FAULT
accumulate NAME error above 150 us.
4. Check if the GNSS signal is spoofed.
5. If the GNSS receiver provides correct phase, restart the BTS.
6. If the GNSS receiver is faulty, replace the receiver. Do not restart the
BTS before the GNSS receiver is replaced.
INSTRUCTIONS
This :alarm is used
BTSOM.
115
FAULT
request
script.
between
This fault
ID
for issuch
the extension
canceled antooperation
EFaultId_CellEnablingFailureAl inform the
baseband
when thetoBTS
operator
be performed).
module
that another BTS fault (the
sees (FBBx/ABIx)
the level of PIM andbeing the radio detected
MEANING
original
4349 fault) is toggling.
: EFaultId_CellShutdownDueToBasebandCapacityLicenseLimitAl
FAULT
module,
2.
by
FPFH Follow
the IDor
EPIMC
Power the inter is ABIO's
instructions
either
distribution Loki
lowerof
unit IQ
the
than
(PDU)links
toggling
the to set
Minor
setup BTS up
has the
fault
threshold, cell
failed,to according
clear
as or it the
the
is to Core
problem.
incorrectly the
Additionally,
FAULT
MEANING
INSTRUCTIONS NAME commissioning additional baseband resources on the
4525
configuration
The :
alarm EFaultId_UnsupportedRadioConnectionConfigurationAl
that requested
EFaultId_ExtPimPerformanceMajorThresholdAl
connected to the secondary
ishave
related in the
toCPICH coresite
the original ofconfiguration
a dual core
faultinishas file
is
BTS. active.
suppressed and the new
where
Double
Cell
MEANING
FAULT
Perform the
enabling oven
NAME
the LCG oscillator
(the
steps setup
below resources
microcontroller
ofinabout
the listedcouldand help
firmware
orderBCH) untilsolving
or
the the disappears:
hardware
failed.
fault issue. failure
d.
Note:
alarm, PRACH Detailed
which resources
isinformation
related to fault 4026: the EFaultId_TogglingAlFault,
toggling frequency can be found is raised. in
The reason
cell
Communication
1.
MEANING
e. Reset
L3 pooltheis might
shut System
resources down be
failure a hardware
because
Module it
or ABIx or a
occupies bus problem,
baseband
module. using the BTS Element or a lack
capacity of
thatDSP. is over
the
All
FAULT alarm
products:
INSTRUCTIONS IDRF history file, which can be downloaded
the
FAULT
2.
Detected
Manager. licensed
Replace NAME The thelimit. System
modules
log file Module
isconnections
available or with
ABIx module.
areSnapshot.
not supported.
See
Disconnect
Toggling
6911
INSTRUCTIONSfault diagram:
alarms the PDUthat
: EFaultId_OcxouCfwOrHwFailureAlhttp://oam.emea.nsn-net.net/
from
are the secondary
related to the core.
original faults are suppressed until
FAULT
ALD
This Port
fault ID power
is also failure
detected when a unit that supported a cell is replaced by
search
the
Note: toggling condition is cleared.
another of:Perform
INSTRUCTIONS
1806
Mix unit, and the steps
EFaultId_CommunicationFailureAl
TDD and FDD
the inunit the might
(GSM/WCDMA/LTE)
new
FaultMgmt_Fault4464EFaultIdExtPIMPerformanceMinorThresholdAl
listed ordernot be until
and
taken the
mMIMO fault
into use is
and resolved.
non-mMIMO
because itsfor
FAULT
MEANING
Add
FAULT licensesNAME
ID to the Centralized License Server to avoid the traffic
connections
hardware
the
The requested
severity differsto
of onefrom
branch.
this baseband
BTS the hardware
fault ismodule
the of
same is
the not
as supported.
previous
the unit
severity (different
of the capacity,
original
Automatic
1. CheckAtmel theAccess
uCother software Class
active Barringfailed,
update is active the accordingly.
SW is corrupted, or the HW is
limitation.
MEANING
4069
type
toggling of: EFaultId_Rs485PowerFailureAl
ports,
BTS and so
fault. on), alarmsor mightand notact be taken into use without a BTS
corrupted.
2.
See
The
FAULT
Radio If there
"Centralized
communication
NAME
module are no other
License
with active Server
the
connection to both ABIA and ABIC alarms, Help"
application or step
document
has 1 does
failed. not
inItNOLS
at hassame
the help,
not reset
forreplied
details.
time is the
tonot
the
reset.
FAULT
All
FAULT products: NAME
NAME
ID
BTS.
message
MEANING
Unknown
supported. that
HW has
resource been sent and/or resent to it.
SW
Repair
5G fallback
BTS
INSTRUCTIONS
6356 orconfiguration
retune the antenna
: EFaultId_AutomaticAccessClassBarringAlfailed system at the site to reduce the amount of
3.
OBSAI
The Replace
fault interface:
is the
also System
detected Module.
for cells with sufficient
PIM
1. Checkproducts
-INSTRUCTIONS
No actions theare being
faultrequired. generated.
name ofWhen the togglingthere isBTS no otherfault.DSP resources, but are
alarms, it indicates
FAULT
INSTRUCTIONS
configured
FAULT
FAULT ID
ID
ID in the same carrier aggregation pool as the cell with missing
MEANING
synchronization
Take the following
The: EFaultId_UnknownUnitType
94 radio module problems.
actions
has detected to clear an the fault: so that
over-current condition in the RS485
Correct
DSP
4489
4539
2. Follow : hardware
resources.
: connection
EFaultId_GnbConfigurationFailed
the instructions of theconfigurations
EFaultId_FallbackDueToAsiConfigurationDataMigrationFailureAl
toggling BTS fault to are
clearsupported
the problem. in
Start
-accordance of
If any port.
IUANT Automatic
alarmwithe with the Access
synchronization Class Barring
fault appears and if: a warning
is reported as for every
fault meaning.
impacted
a.
1. new
Ensure fault cell.
that was thereported
unitdetected
and/or aftermoduleSW update: is properly retry SW update If the unit
MEANING
The
MEANING
Note: fault
Detailedcan be also
information about forthe AirScale
toggling due toconnected.
frequency incorrect can baseband
be pool
b.
FAULT
A otherwise,
and/or
Somemodule
configuration NAME
module
antenna cannot update
if LED
line BTS
does
bedevice
baseband identified with
not last
light
is causing
pooling by its working
up,product
feature the is
overload. SW
unit and/or
code Antenna
activated module
or by line
its is found
faulty.
devices
physical
(actBbpooling
in
device
is
FAULT
Procedures
the alarm
INSTRUCTIONS
Not enough NAME related
history
DSP file,to
capacity plan
which management
tocanset be
upis downloaded
the or configuration
using management
theofBTS Element
Check
powered
address
true). the by unit
(object the
ExtPimPerformanceMajorThreshold
and/or
RS485
ID). module
IUANT that
are out ofcell
causing order the alarm.
because the lack of DC
fails
Manager.
If the
none infault
C-Plane.
of The
is
the log
raised,
above fileit is
means
helps, available that
replace with
thethe Snapshot.
cell is
System about to
Module. enter overloaded
power.
status,
FAULT
2. Check
INSTRUCTIONS and
ID the the fault AChistory.
Bar factors will be broadcasted in SIB2.
FAULT
This fault NAME isbigger
also detected when
FAULT
INSTRUCTIONS
UEs
124
Flexi with
: BTS ID a bar
EFaultId_NotEnoughWspCapasitySetupCellAl
FDD, Flexi factors
BTS TDD, willRP3-01
not be able
AirScale
links to
BTS
between
attach
TDD,
system
to
AirScale the cell modules
BTS until
FDD, the(in
Missing
case
4465
1. of
:
Check and NBAP
FSMF +cell parameters
FSMF)
ExtPimPerformanceMajorThreshold
update or between
the configuration parameters. the system module and its connected
overloaded
CPRI/Ir
Flexi SBTS, interface: status
AirScale is over.
SBTS:
radio
2. Load modulethe correct or between commissioning basebandfile module(ABIA)
to the BTS. and system module (in
MEANING
Replace
FAULT
case ID
of NAME the
AirScale alarming + FSMF) unitBTS. or module.
between baseband module(ABIA) and
MEANING
3.
FAULT
ThereBlock and
is not unblock
enough the
BTS (in baseband
Over-current
baseband
The
4. amount
If activities
case:
module(FBBx)
of PIM beingabove case
measured of capacity
AirScale
by thecontact
to
EPIMC
set up the
+ FSMF) are
is above
cell.
lost.
the user-
Radio
FAULT NAMEmentioned
master conflict don't help Nokia technical support.
defined
INSTRUCTIONS Major threshold.
RF
The
This Module
radio
fault is filter
also input
module has power
detected detectedwhen missing
over-current
there is not enough on the ALD Beam port. Someto
Id range
FAULT
Add
antenna more ID
NAME
linebaseband
device capacity
is causing to the
overload. BTS or, if
Depending the reason
on is
hardware a broken
allocate
INSTRUCTIONS
4038
SIB5-BR : ID the(SIB5 TDDformMIMO CatM) cell to the eCPRI
Information Incomplete TDD MAA/RU.
baseband
FAULT
implementation, NAME unit, replace antenna the line baseband
devices unit.
powered by the RS485 IUANT, or
All products:
1910
powered
Unit
This not: EFaultId_FrFilterInputPowerMissing
fault by
supported
is the
also antenna
by
detected line,
current when are
BTS out
there SW of
are order.
version
not enough carrier component
FAULT NAME IDindicates a potential degradation in the antenna line of the RX
resources
path due
Carrier
6357 : powertofor lose the TDD mMIMO
antenna
measurement
EFaultId_Sib5BRInformationIncompleteAl connection,
does cellnot allocated
water
work intrusion, on eCPRI TDD MAA/RU
damaged cables,-
MEANING
Undercurrent
FAULT case:external structures, or physical damage to the antenna
lightningID
product code.
damage,
The
95
This RF Module alsofilter
: EFaultId_NotSupportedUnit
fault isPassive detected has awhen measured thereinTX are power that iseAxC too low.
assembly.
FAULT
MEANING
FAULT ID
NAME Inter-Modulation thenot antenna enough line cabling addresses
cannot be for
the
103
The TDD
effectively
: mMIMOremoved
EFaultId_MeasurementAl
maximum length cell by allocated
the
of due
SIB5-BRPIM on eCPRI
Cancelling TDD
function MAA/RU on the - product
External code.
PIM
F1 Cell
INSTRUCTIONS
MEANING activation failed to X2islink 936bits
unavailable [3GPP TS 36.331 5.2.1.1].
Cancellation
The eNB omits HW one unitorifmore actExtPIMCancellation
CATMIRFIMs in and
SIB5-BR in order not
1.
An
The Reset
unsupported
faultthe the
can
extPIMCancellingEnabled
MEANING
RF also HW
unitbehasunit.
detectedbeenare detected
for
set a 5G
to true. inFix
cell thedue System
the to: Module.
referenced Thisto line
antenna
exceed
FAULT
typically IDhappens maximum when length
a newradio of SIB5-BR.
unit
a.
The
7100
improper
cabling RF : to
module 5G beamforming
remove the source
carrier
EFaultId_GnbCellActivationFailedX2Al power of theversion
measurement passiveisintermodulation
type. installed
has failed. while an older
interference.
2. If
system
b. the problem
module is
SW, still
not supporting external antenna beamforming which observed does after
not performing
support the step
new 1,
unit replace
version, the
is inRF use.
INSTRUCTIONS
HW unit.
c. not
INSTRUCTIONS
1. supporting external antenna
Remove trivial CATMIRFIM settings to reduce the SIB5-BR size, i.e., do with subsectorization
MEANING
INSTRUCTIONS
d. not supporting
Note:
not
This Perform
configure
fault indicates theantenna
the steps
optional
that module
the
panel
inparameters
the
gNB-CU
split order
listed mode
under until the faultthe
CATMIRFIM. is resolved.
1.
e. Upgrade
configured the system
beamforming cell for nocould
SW. not
beamforming activate RU cell, as the X2
link
f. with
radio the
AHQK LTE eNB
is used radio mapped
forinstances.
external to the NR CELL was not established.
1.
2. Reset
Reduce the alarming
CATMIRFIM unit. antenna beamforming
2.
g. Replace
RU available the unit. memory cache is not enough for requested PIDs
FAULT NAME
2.
RX Ifout
theof faultorder is reported again, replace the optical cables and SFPs used
The
to connectfault can thebe also detected,
alarming radio module for a 5G beamforming
to the cell, in case the
system module/extension
detected
baseband radio is not a 5G O-RAN radio, or it does not
FAULT ID module.
FAULT
1911
FAULT NAME
: EFaultId_FrRxOutOfOrder
3.
RF the NAME
IfModule faultDoes is reported
Not Support again,Classical replace the RF alarming
sharing radio module
Communication
hardware. failure with RNC
MEANING
FAULT
5G
FAULT BTS:ID ID
The
114 :RX path in the RAP is faulty.
EFaultId_RncHoRespAl
AirScale
MEANING BTS FDD, AirScale BTS TDD, AirScale SBTS, Flexi BTS FDD,
FAULT
Flexi NAME
BTS TDD,not
Flexi SBTS:
The
Unit BTS
RNW does receive a response from
The RX RFconfiguration failure
synthesizer of the RF module is not locked.
FAULT ID interface, the received power is low for the RRH.
For SNMP
110 : EFaultId_UnitRnwConfigAl
For CPRI-A interface, the RX path in the FR module is faulty.
INSTRUCTIONS
5G BTS:
Reset the radio module. If the alarm persists, replace
9008 : EFaultId_TmpFault9Al
INSTRUCTIONS
Replace
MEANING expiring vendor certificate with new vendor certificate using
WebEM.
A failureNAME
in the system has been identified.
FAULT
Details
Vendor will
BTSbecertificate
specifiedhas
in release
expirednotes.
INSTRUCTIONS
FAULT ID
To be documented
61616 in release notes.
FAULT: NAME
VENDOR_CERTIFICATE_EXPIRING
CBRS Trust anchor is about to expire or expired
MEANING
Please
This check
fault the fault-specific description below for detailed instructions.
FAULT IDis raised when BTS attempts to perform certificate enrollment
using
61628 CMP
: NAMEinitialization
CBRS request
Trust anchor and detects
is about that
to expire or Vendor
expired BTS certificate
FAULT
has expired.
Temp Fault10
MEANING
INSTRUCTIONS
This alarm
FAULT ID is triggered when CBRS Root CA Certificate stored in BTS as
trust anchor is about to expire in 90 days or has expired.
9009 : EFaultId_TmpFault10Al
INSTRUCTIONS
MEANING
Replace thethe
A failure in expiring
systemtrust
hasanchors with new trust anchors using WebEM.
been identified.
Details will be specified in release notes.
INSTRUCTIONS
To be documented in release notes.
1. Check source fault meaning in O-RU vendor specification.

2. Solve issue manually if possible
1. Check the details from the data provided by the BTS..

2. Solve issue manually if possible.
The operation depends on the type of alarm that is used as external alarm
number 1.
number 2.
number 3.
number 4.
number 5.
number 6.
number 7.
number 8.
number 9.
number 10.
number 11.
number 12.
number 13.
number 14.
number 15.
number 16.
number 17.
number 18.
number 19.
number 20.
number 21.
number 22.
number 23.
number 24.
number 25.
number 26.
number 27.
number 28.
number 29.
number 30.
number 31.
number 32.
number 33.
number 34.
number 35.
number 36.
number 37.
number 38.
number 39.
number 40.
number 41.
number 42.
number 43.
number 44.
number 45.
number 46.
INSTRUCTIONS
24. SYNC.phaseErrorRecoveryThreshold
INSTRUCTIONS is exceeded. BTS reset is
FAULT
LTE NAME Accelerator Fatal Error
Hardware
INSTRUCTIONS
None
INSTRUCTIONS
needed
Correct
RF Sniffing to recover
hardware Data synchronization
connection
Upload Failed phase error.
configurations so that are supported in
1.
ReferUpgrade
to thethe system module
instructions the SW.
formeaning. root BTS fault reported in the alarm on how
accordance
FAULT withe the fault
IDthe failure reported in the alarm.
to
25.
FAULThandle
BTS IDis unable of synchronizing to RRH in CPRI-K RF sharing because
7000
2. : EFaultId_LtefeFatalErrAl
Replace the buffer
unit. underflow or overflow in RX block. A BTS reset is
clock crossing
4502 : EFaultId_NetRfSniffingDataUploadFailedAl
needed
MEANING to synchronize with RRH (radio)
FAULT NAME
MEANING
Fatal
Fault error
signature of LTE for Hardware
crash Accelerator engine detected by Platform
or failure
26.
FAULT
BTS Plan
software.failed activation
NAME to upload is the
stuck RFdue to unknown
Sniffing Data towards reason.the BTS RFresetScanisCollector.
needed
FAULT
to
Non recover. NAME
critical SW Component failure
FAULT
Failure NAME
ID
in optical interface
The operation
INSTRUCTIONS depends on the type of alarm that is used as external alarm
Unit
4590
27. Configuration
: Failure
EFaultId_CrashOrFailureSignatureAl
Carrier Aggregation
number
FAULT
To clear the
Perform
FAULT
47.
IDthis steps
IDduethe belowconfiguration
fault, perform in thethe following
listed orderforsteps:
the existing
until the faultcellsdisappears:
cannot be online
activated
6918
1. Wait
Reset: to cell mapping
EFaultId_NonCriticalSwComponentFailureAl
until next round of on BB
Network-widepools that
RF does
Scan not
Test fit to executed.
is carrier
FAULT
MEANING
3030 IDthe requirements.
System Module or ABIx module.
: EFaultId_FailureInOptical_Rp3Interface
aggregation BTS reset is needed to recover carrier
2.
4559
FaultUser
Replace needs to
the with check
System the
Module
: EFaultId_UnitConfigurationFailureAI
enriched fault status
signature and limitations
or ABIx module. of RF Scan Collector.
aggregation
MEANING
See RF faultScanservice Collector BTS only).raised
(5Gdocumentation Impacted for the
for more 2CCspurpose
or 3CCs
details.
of network-wide
CA
The
system
MEANING operation depends
tracking. on
Provides the type
the of alarm
information that is
about used
the as external
crash or the alarm
failure.
configurations
This alarm notifiesare reported
about in additional
non-critical SW information
component of the alarm.
failure when non-
number
MEANING
Raised
The 48. autonomous
after
AirScale/Flexi BTS unit/BTS
(System recovery
Module) has reset
detectedwhen anthe unit/BTS
abnormal is up
critical process crash has occurred and core dumping has been
Failure
and
operation
INSTRUCTIONS of configuring
running or again.
a failure in theanunit. optical RP3 interface between two modules.
completed.
The
5G failure
BTS,NAME cannot be attributed
AirScale BTS FDD, AirScale to a specific
BTS TDD, module but there
AirScale SBTS, areFlexi
several
FAULT
INSTRUCTIONS
possible fault sources, for example, fiber optical cable, SFP, or individual
BTS FDD,
INSTRUCTIONS
FAULT
LTE NAME
Hardware Flexi BTS TDD,
Accelerator Flexi
Concurrent SBTS: Crash
If FSP
None
module.
Please
Check reset
check
the and/or Site reset
thediagnostic
below do not help,
fault-specific forcollect
description thedetailed
for logs andfault
provide
instructions.
Perform
BTS
them has
to noalarm
the
Nokia
steps
connectionbelowto
support for
inRF information
the listedCollector
Scan
investigation.
order the
untilreason
the faultof disappears:
the report
before
1.
FAULTReset the
ID thereset.
System Please Modulenote that
or ABICcurrently
module. degraded cell setup is not
INSTRUCTIONS
supported.
2.
FAULTReplace ID the System Module or ABIC module.
7001
Refer : EFaultId_LtefeConcurrentCrashErrAl
If BTS:toreset
4501 the instructions
is executed for when theany
EFaultId_NetRfSniffingNoConnectionToCollectorAl rootofBTS the fault
cells reported in the alarm
has availability statuson how
1. handle
to Check the
Degraded, the
the sector
failure
cell which
reported
might not has inthe
be the affected
alarm.
enabled TRX.
after the reset, and will not
Please
MEANING
FAULT
2. Check check
NAMEin the the belowatfault-specific
alarms NetAct or BTS description
Element for detailed
Manager instructions.
where the
provide
MEANING
LTE any
Hardware services.
FAULT
Cell
matching NAME sectorAccelerator
re-deployment id isisvisible
needed module
in for
alarm has
enabling been crashed
inter-eNB
attributes. The alarm by the
FDD-TDD Platform
CA to
id belongs
BTS
software
BTS does not receive
deployed
Integration on ARM
Failure response cores, from RF Scan
because Collector.
of the Fatal Error reported by
range
The
FAULT 7100-7116.
degraded
NAME cells canAccelerator
be also found basedoron active alarms.
another
FAULT
3. Find LTE
ID
fault Hardware
idsector
in thewhichalarmhas andthe followmodule DSP
the instructions core.
mentioned for the
TD-LTE
1. Check
INSTRUCTIONS radio
the disabled affected TRX.
FAULT
5511
fault.
FAULT
If ID
: EFaultId_CellReDeploymentNeededForInterEnbFddTddCaAl
NAME
actCategoryAlarms ==
2.
To Check
clear
INSTRUCTIONS
4594 : in the
this alarms
fault, perform
EFaultId_BtsIntegrationFailureAlatfalse,
NetAct fororeach
the following BTSdegraded
Element Manager
steps: cell, alarmwhere 7654the Cell
Temperature
Operation
FAULT
matching
1. If problemID sector alarm
Degraded id below
occurs is
isafter reported.
visible in alarm attributes. userThe alarm id belongs to
Perform
MEANING the steps infeature
the activation
listed order until needs
the fault todisappears:
check
4530
range
configured
1. Reset: 7100-7116.
EFaultId_TdLteRadioDisabledAl
the IP address.
System Module or ABIC module.
MEANING
During
FAULT
Small BTS
ID startup,
Cell: FDD eNB does not detect the neighbor TDD eNB.
3.
2.
A Find
Wait
Replace
new fault
until
BTS id in
the
the
that the alarm
next
System
shall round
beModule and
ofwith
directly follow
Network-wide
or ABIC
connectedthe instruction
module. RF
and Scan mentioned
Test to is and for the
executed.
FDD
3040
1. User
MEANING
fault.
3.
eNB
: allocates
EFaultId_TemperatureAlarm
Checkneeds the alarm to
the cells
diagnostic
check the status
the
information
and
normal for
limitationstheintegrated
cell deployment
reason
of RF of the
Scan
NetAct
fault
Collector.
isn't
inter-
report
registered
eNB
before FDD-TDD
the properly
reset. CA by
is
Please NetAct
not enabled.
note Manager
thatisthe and
currently therefore
degraded cannot be integrated
cell setup is not
Radio
See RF interface
Scan on TD-LTE
Collector cells
documentation disabled.
for more details.
to NetAct.
Later,
MEANING
supported. FDD IfeNBBTSdetects
reset isthe neighbor
executed TDD
when anyeNB and
cell hasexchanges
availabilityCaData status
A
Thepotential
information.
internalthe
Degraded, reason
FDD
temperaturefor
maythe
celleNB finds
not fault
of the
be canRFthebe
thatenabled aafter
Module faulty
existing NMS
orcell IP and
address
deployment
System
the reset Module in the
willneeds
exceeds
not toBTS
be
provide the
INSTRUCTIONS
plan
replaced
threshold
any (nmsIntegrationIpAddress
services. by CA
value, specific
or the cell
ambient in
deployment.MNL/MNLENT)
temperature of the modules are beyond
If GPS
FAULT is
NAMEconfigured as the reference clock, do the following:
BTS
the
1. reset
specified
Check is needed
the limits.
GPS in order
receiver to deploy the CA specific cell.
installation.
LTE Hardware Accelerator Externally Triggered Crash
The
2.
FAULT degraded
Check NAMEthe GPS receiver status. based on active alarms also.
cells may be found
INSTRUCTIONS
3. Check the connection
Unit
FAULT
A BTS temperature
ID is highinbetween the GPS receiver and the system
Refer
If toreset
actCategoryAlarms
module. is needed
the instructions == fororder
false, the for to redeploy
root BTSdegraded
each thereported
fault LTE/GSM/WCDMAin the7654
cell alarm alarmCell cells
on how
7002
and
to : EFaultId_ExternallyTriggeredLtefeFatalErrAl
take
handle into
the account
failure CA
reported DATA. in theThe number
alarm. of cells that will be
Operation
FAULT ID with CA specific cell deployment depends on the baseband
redeployed
If the TOP signal is configured as the reference clock, check the
2 : EFaultId_UnitOverheatAl
MEANING
resources available.
connection
LTE Hardware to the TOP server.
Accelerator instance crash has been triggered by external
MEANING
script.
The temperature of a unit exceeds the threshold value.
FAULT NAME
Commissioning
INSTRUCTIONS error: <x>
FAULT
FAULTthe NAME
NAME
Check
BTS Reset active fan alarms and the air flow of the BTS.
FAULT
Incompatible ID Cause SW version detected
3060 :
FAULT
FAULT ID ID
4592 : EFaultId_BtsResetCauseAl
23 : EFaultId_IncompatibleSwVersionAl
FAULT
MEANING NAME
MEANING
BTS
The
5G BTS: BTS download
SW has been reset. or activation failed
FSMr3/AirScale
A new unit with an supports
incompatible the following SW might cause haveforbeen
the reset:
inserted into the 5G
“unknown”: Unknown
BTS. Automatic SW update is triggered. cause
"power-on reset": Cold start
"software
AirScale BTS reset": FDD,Software
AirScale BTS TDD, AirScale SBTS, Flexi BTS FDD,
Flexi BTS TDD, Flexi SBTS:
An incompatible software has been detected.
INSTRUCTIONS
Section
1. Check A:the Check connectionon the system
with MME, module side: using
particularly,
the
The
2.
4. alarm
Check
Reset
MEANING IP traffic history
the
the of the
fault
BTS. file, which
user
history. is can
throttled be downloaded
because of awhether
missing thethe BTS M3Element
license. link is
broken.
Manager.
MEANING The log file is available with Snapshot.
The
1.
2. CheckDSS ifbasic configuration
the connector
MME is sealisisincorrect
operational. properlyfor the uplink.
mounted and The firmlyparameters
in place. do
EPIMC
INSTRUCTIONS
AirScale
not match Calibration
BTS between FDD,isthe failed.
AirScalepeer BTS and
cells TDD,the AirScale
dynamic SBTS,
spectrum Flexi sharing
BTS FDD,
3.
FAULT
Read Check the if
NAME the
alarm speed
diagnostic and duplex setting of BTS
information to know when the missing licenseM3 port is consistent with
Flexi
cannot
2. Check BTS if TDD,
operate. the Flexi
Small SBTS:
Form Factor Pluggable (SFP) is properly connected
switch
Low noise
INSTRUCTIONS
was port,
detected which
amplifier is connected
failure directly to the BTS, for example, both
1. Ensure
and/or mountedthatand the at what level
in module
the System is properlythe IP connected.
Module.
traffic is currently
If SFP connection If the modulethrottledLED in relation
and/or mounting does
"Autodetect"
Start
to the EPIMC
peak or both
calibration
rate. "1000 to Mbit/s
cancel Full fault.
the duplex".
not
FAULT
Reason
is light
incorrect, up,
NAME
8007) the module
[feature
readjust is
theLTE4750] faulty.
connection Check
Subcarriers the module
and/or mounting. that is
requested by NR are not causing the
FAULT
alarm. ID
NAME
X2
If interface
adjacent
thislicenses to recovery
(contiguous failure
with) the dynamic area(s). The dynamic areas are
1839
Transport
Add
Note: :fault
Fault
happens
EFaultId_LNAFailureAl
layer
10 connection
todetected
CLS right
to avoid after
on radio
a commissioning
failure
the in S1 limitation.
traffic
module interface
can(connected
be
or a configuration
a consequence of
change,
subcarriers
3. Check
verify that
the iffollowing
the LEDareconfiguration
not reserved
indicates nor
thedata:
faulty blanked.
IPSFPaddress It mayof the occur that multiple
to System
MME.
baseband
FAULT
dynamic
Module). module
IDareas
Replace canthe power
beSFP off.
derived. if itCheck
is faulty. if the baseband module(s) on which
MEANING
FAULT
If licenses
radio is ID are not
connected added,
is(are) the
powered levelIncorrect
will
on. be decreased toNR theUL lowest level,
6303
Reason : EFaultId_X2ResetRetryOut
8008) [feature LTE4750] number
The
6202
FAULT
which
2. CheckRadio NAME
50%
the Module
: isEFaultId_S1SctpEndpointAl
of
fault peak hasrate.
history. detected a malfunction of anofinternal reserved
LNA
areas.
4. Check if the optical cable is properly connected and/or mounted in the
SIB24
3. Retryinformation
MEANING
Reason IPSec [feature
8084) incomplete
connection or use unsecured connection
LTE4750/5GC001856] The NR UL maximum share
SFP.
MEANING
The
is too X2 low interface
to fulfil reset
resources has failed
needed after to several
operate attempts.cell.is This indicates that
FAULT
The
FAULT
a severe
NAME
transport
ID failure path has (SCTP)
occurred. for For
connection
example, thethe
to there MMEis some broken. This
configuration
Reason
5. Clean
Automatic
might be 8085)
the X2optical
because [feature
IPsec of Tunnel
an LTE4750/5GC001856]
connectors Setup
unplugged thatFailure
are connected
cable to the TheMME. UL
to the minimum
There SFP. is sharethe
Reset
no of
6361
problem,
LTE is: EFaultId_Sib24InformationIncompleteAl
too there
low is
to no
fulfil X2 connectivity,
resources needed the adjacent
to operate BTSan has
LTE failed,
cell. and so
RFCheck
1. HW and
transport thatcheck
path the
available if thisto
cables/fibers solves
continue theconnected
are problem.
operation on to thethe correct connectors.with
faulty connection
FAULT
on. NAME
FAULT
the
MEANING
Active MME. ID
users license limitation
INSTRUCTIONS
Section
6326
2. Check B:thatCheck on the
: EFaultId_X2IPsecTunnelSetupFailure
the interface radioat the module
far-end side:interface
The maximum
INSTRUCTIONS
1.Check the DSS length of SIB24
configuration. information dependsis on switched
the cellon and has
bandwidth,
correct
INSTRUCTIONS
configured
FAULT auto-negotiation
SIB
ID the the coding settings.
rate and on all nrCarFrqL instances in NRFIM
Note:
2.
1. Change
Check
MEANING Perform if in steps
configuration
connector seal below in the listed
is parameters
properly order until
depending onthe reasonalarmfrom
Note:
configured
4337
disappears. :Perform the
the steps
cell.
EFaultId_ActiveUsersLimitAl The below
warning in the is listed
reported order until
if one orthemore alarm NR carrier
supplementary
There
3. Check
disappears. is failure
whether alarm
to to setup
there information:
at least
are active one X2 in
alarms IPsec
at the tunnel
far end. using RNL
If there with follow
are, a
frequencies
2.1 Reason need
8007) be
[feature omittedLTE4750] by eNB order
Reconfigure not to
LTE/NR exceed the
parameters
neighbor
the
maximum
MEANING instructions BTSlength detected
for handling
of SIB24. by ANRthose (Automatic
alarms. Neighbor Relation) detection
1. Check the
responsible availability ofreservations:
thefollowing
adjacent reasons: BTS.
functionality
1.
The CheckBTS thefor
enters due UL to areas
connection any of
capacity the
with
limited themodeMME,due accordingly,
to missingbased licenses. on whether
Calls from the
--NR:
a.
4.
S1 IP
To
link version
verify
is mismatch
that
broken. the hardwareof the outer
of the layer
interfaceIPsec workstunnel endpoints
correctly, connect a
INSTRUCTIONS
excess
2. Check users will be rejected
the mismatch
connection except for handover and emergency calls.
--
b. NRCELL-msg1FrequencyStart
loop IP cable
version and check whether ofwith
the the inner adjacent
the alarm
BTS.tunnel
layer disappears.
IPsec CP/UP endpoints
--
c.
2. NRBTS/BWP_PROFILE-locationAndBandwidthUl-cRbStartUl
Insufficient
Check if the IPsec
MME resources
is operational. and
INSTRUCTIONS
3. Disconnect and reconnect the adjacent BTS.
NRBTS/BWP_PROFILE-locationAndBandwidthUl-cRbSizeUl
5.
Add Checklicenses that to the the length/type
Centralized of License
the cable/fiber Serverdoes to avoid not callintroduce
limitation.
--LTE:
Alarm
excessive
3. Check due if to
the the
attenuation
speedfault will
or
and be
that
duplexraised
the initially
cable/fiber
setting of when
is
the cut
BTSthere is
somewhere.
S1 portattempt to setup
is details.
consistent
See
E1
-- "Centralized
interfaces: Check License that Server
the Help"
interface document
type of the in NOLS
far-end for
interface is also
X2
withIPsec the switch tunnelport withthat an is "eNBconnectedcontrolled" neighbor
directly to theeNB. BTS (for example, they
configured
6. to be a framed E1 interface. If this is not the case, reconfigure
areCheck that the Ethernet
both "Autodetect" or both interface
"1000 Mbit/s has correct auto-negotiation settings,
Full duplex").
the
Theinterfaces
fitting alarm
to thewill so
be that
far-end canceledthey match
interface. only after eachallother. failed X2 IPsec tunnels with "eNB
FAULT
controlled" NAME neighbor right eNBs are setup successfully.
If
S1 this fault happens
interface setup failure after a commissioning or a configuration change,
FAULT
7. With NAME
an optical Ethernet
verify
FAULT NAME the IP address of the interface:
MME. Check that the inserted SFP module
Toggling:
INSTRUCTIONS
matches <Fault
the fiber name>
type and wavelength of the GigabitLimit Ethernet link
Cell
FAULT Shutdown Due To Baseband
ID recovery actions are in progress, Capacity License
Autonomous
provided. and if they are not effective,
6308
FAULT
the root: EFaultId_S1SetupRetryOut
ID
cause of IPsec tunnel setup failure should be investigated from
FAULT ID
4026:EFaultId_TogglingA
the
FAULT logs. Also, there could be multiple IPsec tunnel failures with X2
NAME
4349 : EFaultId_CellShutdownDueToBasebandCapacityLicenseLimitAl
MEANING
neighbors.<Fault Depending
Toggling: name>on the reason for failure, if the fault is due to
MEANING
FAULT
mismatch NAME of IPsec policy parameters then the profile needs to be adjusted
MEANING
This alarm is source
used
break,torunning inform
Mains
either
FAULT
The on
cell
power
isthe
ID shut down or targetthe
because
battery
BTS. operator
Ifbackup
it occupies
that another
the reason
baseband is due BTS fault (the
to insufficient
capacity that is over
original
resources, fault)
4026:EFaultId_TogglingA then is toggling.
IPsec policies that are not in use should be deleted to free
the
FAULT licensed ID limit.
up resources
The
37 :
MEANING alarm that is related to the original fault is suppressed and the new
EFaultId_MainsBreakAl
INSTRUCTIONS
alarm,
This
Add alarm is is
which
licenses used
to
related
the
to fault
toCentralized
inform the4026:
operator
License
EFaultId_TogglingAlFault,
that another
Server to avoid BTS the fault is raised.
(the
traffic
MEANING
original fault) is toggling.
limitation.
Toggling
There is aalarms fault inthat theare BTS related
main power to the original
supply. faults The BTS are has suppressed
receiveduntila
See
the
battery "Centralized
toggling backup condition License
alarm, is
and Server
cleared.
the BTS Help"cells document
intelligent inshutdown
NOLS forprocedure details.
The alarm that is related to the original fault is suppressed and the new
has
alarm, started.
which is related to fault 4026: EFaultId_TogglingAlFault, is raised.
The severity of this BTS fault is the same as the severity of the original
toggling
INSTRUCTIONS
Toggling BTS fault.
1. Check alarms the availability that areof related to the original faults are suppressed until
IP connectivity.
Check
the togglingmainthe condition powerissupply cleared. of the base station.
2. Check whether there are active alarms at the far end. If found, follow
INSTRUCTIONS
The
the severity of this
instructions BTS faultthose
for handling is thealarms.
same as the severity of the original
1. Check
toggling the fault
BTS fault.name of the toggling BTS fault.
3.
2. Check
Follow ifthe theinstructions
far end hasofBFD switchedBTS
the toggling ON.fault to clear the problem.
INSTRUCTIONS
Note: Detailed
1. Check information
the fault name of about the toggling
the toggling frequency can be found in
BTS fault.
the alarm history file, which can be downloaded using the BTS Element
Manager. Theinstructions
2. Follow the log file is available with Snapshot.
of the toggling BTS fault to clear the problem.
Note: Detailed information about the toggling frequency can be found in

Manager. The log file is available with Snapshot.
element of the DN). E.g. TRMOD-1.
$INTERFACE indicates the interface on the module following the labeling
1. Clean the cables and connectors.
on the frontplate of the real HW or the corresponding parameter in the
Management Model.
2. Check that the connectors are properly connected to the unit.
E.g. EIF1, IF1
$LOOPTIMEOUT indicates the time period in minutes after which the
3. Check that the cable connected to the interface in question is not
inserted loopback shall terminate automatically.
damaged and is within the specifications.
1. Check thefor
Example(s) availability
alarm text: of IP connectivity.
4.
2. Follow the E1 path
Check whether there in the active
network and check whether
far end. any other alarms
"Interface under test on are
TRMOD-1,alarms IF2 forat2theminutes" If there are, follow
concerning
the instructions the fault are on (such
for handling thoseas Laser End of Life) and signal quality
alarms.
of each individual link. If they are, follow the instructions for handling those
alarms.
INSTRUCTIONS
1. Check that the SFP module is correctly installed and plug-out/plug-in
Switch off the loopback or wait for the timeout to expire which opens the
SFP module.
FAULT
Check NAME
that the configured interface type matches the configured interface
loop and cancels the alarm.
Toggling:
type of the<Fault
far end. name>
If this is the case, the problem is somewhere in the
2. Check that the electrical contacts of the SFP module are clean from
transmission network.
dust,
FAULT dirt,
IDor water.
FAULT NAME
Note that only the SFP might be faulty, and not the entire hardware unit.
Toggling:
Check the<Fault
intermediatename>transmission network for alarms indicating the root
MEANING
cause
This and follow
alarm the instructions for handling these alarms.
FAULT ID is used to inform the operator that another BTS fault (the
original fault) is toggling.
1. Check
FAULT the cabling and network connections to the far end.
NAME
1. Check
None the intermediate transmission network for alarms indicating the
2. Check
Toggling: the Linkname>OAM event theinformation andis the Link OAM state
The
root cause<Fault
alarm
MEANING that
and is related
follow thetoinstructions
originalforfault suppressed
handling and
these alarms. the new
information.
alarm, which is related to fault 4026: EFaultId_TogglingAlFault, is raised.
This
3. alarm
Check
FAULT IDthe is Ethernet
used to inform interface the configuration
operator that at another
the BTS
local andfault (the
remote
1.
2. Inspect
Check
original details
the transmitof
fault) is toggling. the type
hardware, of the critical
connect aevent
loop through
cable andonline
check that no
sides.
Toggling alarms
configuration
alarms appear forthat
thisare
management. related to the original
interface.FAULT NAME faults are suppressed until
4.
the
2. Insert a Link
toggling
Check OAM
condition loopback.
is state
cleared.
The alarmthe
Toggling:
MEANING
<Fault
that Link OAM
isname>
related to the information of the
original fault interface. and the new
is suppressed
3. Check
alarm, whichthe is cabling
related andto network
fault 4026:connections to the far end. is raised.
This
The
4. alarm
severity
Check
FAULT IDthe is of
used thisto
Ethernet BTSinform
faultthe
interface operator
is the same that
configuration another
as the
at BTS
severity
the local of
andfault
the (the
original
remote
original
toggling fault) is toggling.
TogglingBTS
sides. fault.
alarms that are related to the original faults are suppressed until
5.
theInsert a
toggling Link OAM loopback.
condition is cleared.
The alarm that is related
MEANING to the original fault is suppressed and the new
alarm, which
INSTRUCTIONS
This alarm is of is
used related to fault 4026: EFaultId_TogglingAlFault, is raised.
The severity thistoBTSinform
faultthe operator
is the same that another
as the BTS
severity of fault (the
the original
1. Check
original the fault name of the toggling BTS fault.
Replacefault)
toggling
Toggling BTS
the
alarms
is toggling.
fault.
faulty SFP.
that areNote
related thattoonly the SFPfaults
the original is faulty, not the entireuntil
are suppressed
hardware
the toggling
2. Follow unit.
condition is cleared.
The alarmthe thatinstructions
is related to of the
the original
togglingfault
BTSisfault to clear the
suppressed andproblem.
the new
alarm, which is related to fault 4026: EFaultId_TogglingAlFault, is raised.
INSTRUCTIONS
The
Note:severity
Detailedof information
this BTS fault is the
thesame as the severitycan
of the
be original
1. Check
toggling the fault
BTS fault. name of about
the togglingtoggling frequency
BTS fault. found in
Toggling alarms that are related to the original faults are suppressed until
Manager.
the
2. Follow The
toggling
the log file is
condition
instructionsis available
cleared. with Snapshot.
INSTRUCTIONS
The severity of information
this BTS fault is the
Note:
1. Detailed
Check the fault name of about thesame
the toggling
as the
toggling severitycan
frequency
BTS fault.
of the
be original
found in
toggling
the alarmBTS fault.
history file, which can be downloaded using the BTS Element
INSTRUCTIONS
Note: Detailed
1. Check information
the fault name of about the toggling
the toggling frequency can be found in
BTS fault.
Note: Detailed information about the toggling frequency can be found in

Manager. The log file is available with Snapshot.
Check
Check ifthe
thefollowing
negotiatedLocalIPAddress is same as the remoteMru,
parameters status: localMruResult,
configuredLocalIPaddress.
pfcResult, acfcResult. Change the values to the correct ones
accordingly either at the local end or peer.
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
or
peer if there is a mismatch.
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.
Check for LCP failure alarms of the PPP-links belonging to the
SL-PPP/ML-PPP
2.1 Check that theinterface andfully
cables are follow the instructions
plugged of these alarms.
in to the connectors.
Check all PDH related alarms and follow the instructions of these alarms.
2.2 Check that a CAT5e or higher Category cable is used
2.3 Replace
1. Check thethe cable.
cabling.
2. Check the CCM configuration at the remote peer.
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.
1. Check cabling.
2.
3.1Check
Checkthetheconfiguration at the remote
clock mode setting peer. link partner. It should be
of the remote
either "multiport device" or "manual master".
1. Check the network between both BFD peers for physical link failures or
mis-configurations.
3.2 Configure
2. Check if thethe
BFD local clock mode
functionality to "manual
in the slave" forcing
peer is switched on andlocal
thatEthernet
the
interface to operate
configurations of theatBFD
slave clock
local andmode.
remote peers match.
1. Check
Note: Do the
not network
execute between both BFD
this step remote, peers
but only for physical
when being link
localfailures
at site or
as
misconfigurations.
it can cause the Ethernet link to be down. As a result, remote management
2. Check
access if thebe
might BFD
lost.functionality in the peer is switched on and that the
configurations of the BFD local and remote peers match.
1. Check
Note: the whether
Check backhaulrootusage
causeandofif the
other applications
fault with anymore,
is not existing the same is or
1. Check
higher themay
PHB backhaul
compete usage and ifthis
against other applications
TWAMP with thethe
same
sessionauto-negotiation
about or
capacity.
done
higher by a
PHB new
may auto-negotiation
compete against process.
this Retriggering
TWAMP session about the capacity.
An increase
requires in the
manual priority
action by of
theTWAMP
user, (i.e.session or ofEthernet
changing the backhaul capacity
interface
An
may increase
clear theinalarm.
the priority of TWAMP session or of the backhaul capacity
configuration,
may clear the plug out/plug
alarm. in cable, triggering link down/link up).
2. Check if destination is unreachable by IP connectivity test. Send an
2.
ICMPCheck therequest
echo last measured
(ping) toRTT values
the UDP of of
port this
theTWAMP
TWAMP session
reflector andat verify
the
that the configured RTT threshold value is not too close
destination IP.If ICMP echo reply indicates that the destination is to average
measured
unreachable RTT butvalues,
you have so that thisto
access alarm
TWAMPcouldreflector,
be resultyou
of sporadic
can check mis-
its
measurement.
status. If the status is disabled or down try to activate it again and check if
alarm disappears.
3. Check configured PLR threshold. Setting PLR to 0% should be avoided,
because every lost measurement packet will trigger the alarm and it
cannot be cleared again (PLR>=0).
Check the LCP failure alarms of the PPP-links belonging to the ML-PPP
interface and follow the instructions of these alarms.
Check the related PDH alarms and follow the instructions of these alarms.
1.Check for duplicate IPv6 addresses configured in the network element.

2.Change the identified duplicate IPv6 address.
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.
FAULT NAME
Unit
FAULTRNW configuration failure
NAME
RX out of order
FAULT ID
110 : EFaultId_UnitRnwConfigAl
FAULT ID
1911 : EFaultId_FrRxOutOfOrder
MEANING
Unit RNW (Radio Network) configuration or reconfiguration failure.
MEANING
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS TDD, AirScale BTS FDD,
The
Flexifault
Check theisauthentication
SBTS, detected
AirScalefor DSP or CARRIER
credential
SBTS: when
provided it does
by the peernot accept
(certificate).
configuration, configuration failure, or does not respond
The RX RF synthesizer of the RF module is not locked. to a configuration
request.
For SNMP
Check interface,
the IKE profilethe received power
configuration of theisSBTS
low for thethe
and RRH.
peer for proper
INSTRUCTIONS
values.
Note: Perform the steps in the listed order until the fault is resolved.
For CPRI-A interface, the RX path in the FR module is faulty.
1. WCDMA
Small Cell: RAT reset.
2. BTS
Check reset.
The RXthat
paththe
in configurations
the FR modulefor is the peer and the SBTS security policies
faulty.
3.
forCheck the commissioning.
corresponding failure notification.
4. Replace the affected HW.
INSTRUCTIONS
Flexi SBTS, AirScale SBTS:
1. Reset the RF HW unit.
None
2. If the problem continues after resetting the RF HW unit, replace the RF
FAULT
HW unit.NAME
Tx power level too low
Flexi BTS FDD, Flexi BTS TDD:
FAULT
1. ResetIDthe RF HW unit.
125
2. If :the
EFaultId_CellPowerAl
problem continues after resetting the RF HW unit, replace the RF
1.
HW unit. the source address of the remote MEP.
Check
MEANING
2. In
3. If the
caseupdated
of SNMPMAC Address
radio, is incorrect
the only , manually
way to clear configure
the fault MAC
is to reset the
The
Address
radio radio ofoutput power
unit.has
that particular
or replace the dropped.
remote MEP again.
There is a fault in the downlink transmission path.
Small Cell:
INSTRUCTIONS
1. Reset the HW unit.
Operator
Too to signal
check
low problem
Tx DNS measured
level entry for failed FQDNs
in radio andmay
module make besure it resolves
detected due to
2.
to If the
unique IP continues
addresses. after resetting the HW unit, replace the HW
failure
unit. of any unit on the path between the tx antenna line port on radio
module and the DSP. Execute the following actions to recover the fault in
the presented sequence:
1. Reset the alarming radio unit.
2. If previous
In case step hasfailure,
of switchover been executed and fault
operator needs is reported
to recover theagain, reset
defective the
link.
BTS
FAULT NAME
(block
RF / unblock
Module ofBTS).
1.
3. Check theout
If previous
order
availability
steps haveofbeenprimary/secondary
executed and the IPsec
faulttunnel connectivity.
is reported again,
2. Check
replace whether there are active alarms at the far end. If there are, follow
FAULT
the ID
instructions for SFPs
handling those alarms.the alarming radio module to the
optical cables and
1912 : EFaultId_FrOutOfOrder used to connect
system
module
MEANING / extension baseband module.
4. If previous
The RF module steps have
is out been because
of order executedofand fault is reported
a software or hardware again, fault.
replace
INSTRUCTIONS
Perform following steps in the given order. Stop, if the problem
Related Faults Clearing
1817:Oven oscillator heating failure1819:Oven oscillator

1 Automatic
clock missing1839:Low noise amplifier failure1840:Filter tuning failure
103:Carrier power measurement does not work10:No

1 Automatic
connection to unit110:Unit RNW configuration failure125:Tx power level
1931:RF Module blocked4399:One or more carrier1 groups

Automatic
blocked4614:RAT blocked49:Cell blocked50:BTS blocked
1400:[User defined]1401:[User defined]1402:[User1 defined]1403:[User

Automatic defined]1404:[User defined]1405:[User defined]1406:[U
17:BTS RNC interface signalling link failure18:BTS1 RNC

Automatic
interface signalling link failure2412:OMU signaling connection failure
1816:Transmission clock missing1818:BTS master1 clock

Automatic
tuning failure1858:Faulty configuration of system modules1898:PPS
4026:Toggling: <Fault name>4293:IP Traffic Capacity
1 Automatic
Limit4337:Active users license limitation4349:Cell Shutdown Due To Ba
1802:BTS file error1850:SW corrupted1901:RF Module

1 Automatic
critical file not found1902:RF Module file not found1924:Configuration
126:Cell power parameter out of range154:PIC pool

1 Automatic
configuration failure170:Unsupported TX Configuration1807:Invalid freque
1834:Mast Head Amplifier fault above current window1835:Mast

1 Automatic Head Amplifier fault below current window1836:Antenna line
115:Cell enabling failure124:Not enough DSP capacity

1 Automatic
to set up the cell160:One of the Common Transport Channels is delete
10:No connection to unit114:Communication failure

1 Automatic
with RNC1300:Cabinet door open130:Not enough resources for commissi
103:Carrier power measurement does not work10:No

1 Automatic
connection to unit110:Unit RNW configuration failure125:Tx power level
1 Automatic
4026:Toggling: <Fault name>4459:User Account has

1 Automatic
Default Password4640:Netconf SSH algorithm negotiation failure4641:S
9000:Temp Fault19001:Temp Fault29002:Temp Fault39003:Temp

1 Automatic Fault49004:Temp Fault59005:Temp Fault69006:Temp Fau
0 Manual
0 Manual
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
10:No connection to unit16:Unit synchronization failed1802:BTS

1 Automatic file error1806:Communication failure1811:Baseband bus conf

1 Automatic file error1806:Communication failure1811:Baseband bus conf
10:No connection to unit1300:Cabinet door open1517:External

1 Automatic Alarms Misconfigured1518:Second External Alarm Box Detecte

1 Automatic file error1806:Communication failure1807:Invalid frequency ch
1 Automatic file error1806:Communication failure1807:Invalid frequency ch
10:No connection to unit1802:BTS file error1806:Communication

1 Automatic failure1811:Baseband bus configuration was rejected1815:N
1836:Antenna line failure1871:Antenna Line Device

1 Automatic
Operation Failure1872:Antenna Line Device Operation Failure1873:Anten
4026:Toggling: <Fault name>6202:Transport layer1connection

Automatic failure in S1 interface6308:S1 interface setup failure6317:S1 int
4026:Toggling: <Fault name>6150:GTP-U Path Failure62000:XP

1 Automatic connection setup failure-Max Number of XP connections rea
4293:IP Traffic Capacity Limit4337:Active users license

1 Automatic
limitation4349:Cell Shutdown Due To Baseband Capacity License Lim
37:Mains power break, running battery backup 1 Automatic
61022:BFDGRP-$BFDGRPID down 1 Automatic
4026:Toggling: <Fault name>61028:LOF on $UNIT,

1 Automatic
$INTERFACE
4026:Toggling: <Fault name>61029:LOS on $UNIT,

1 Automatic
$INTERFACE
61030:Dead Peer Detected 1 Automatic
61040:Interface under test on $UNIT, $INTERFACE

1 Automatic
for $LOOPTIMEOUT minutes
4026:Toggling: <Fault name>61050:Missing SFP 1

module
Automatic
on $UNIT, $INTERFACE
61075:Link OAM loopback inserted on $UNIT, $INTERFACE

1 Automaticby $PEER
61076:Link OAM link lost on $UNIT $INTERFACE1 Automatic
61077:Link OAM critical link event $E on $UNIT $INTERFACE

1 Automatic
61079:SFP HW Failure on $UNIT, $INTERFACE 1 Automatic
4026:Toggling: <Fault name>61104:EBER on $UNIT,

1 Automatic
$INTERFACE
4026:Toggling: <Fault name>61150:LOMF on $UNIT,

1 Automatic
$INTERFACE
4026:Toggling: <Fault name>61151:AIS on $UNIT,

1 Automatic
$INTERFACE
4026:Toggling: <Fault name>61152:RDI on $UNIT,

1 Automatic
$INTERFACE
61250:IPCP Failure 1 Automatic
61251:LCP failure 1 Automatic

61252:PPP Interface down 1 Automatic
61410:CCM fault level $LEVEL, prio $PRIORITY, 1cause

Automatic
$CAUSE
61411:ETH AIS fault on $UNIT, $INTERFACE, level

1 Automatic
$LEVEL, MAC $MACADDRESS
61605:BFD-$BFDID down in ingress 1 Automatic
61606:BFD-$BFDID down in egress 1 Automatic
61607:Auto-negotiation mismatch on $UNIT, $INTERFACE

1 Automatic
61610:RTT threshold crossed on TWAMP-$TWAMPID

1 Automatic
61611:PLR threshold crossed on TWAMP-$TWAMPID

1 Automatic
61622:MLPPP link Degrade 1 Automatic
61632:Dup Addr detected-$DUPLICATEIPV6ADDRESS

1 Automatic
61639:IPsec emergency bypass active 1 Automatic
61641:IP Traffic Capturing ongoing $UNIT, $INTERFACE,

1 Automatic
$MACADDRESS
61643:IPsec tunnel switchover 1 Automatic

61644:IKE authentication failure 1 Automatic
61645:IKE SA failure 1 Automatic
61646:IPSec SA failure 1 Automatic
61647:IPSec expert mode activated 1 Automatic
61654:IPsec FQDN failure 1 Automatic
61655:CCM MAC mismatch MEP $ID, MDL $LEVEL,

0 Manual
MA $MAID, MAC $MACADDRESS
61657:IPsec Tunnel Endpoint is not unique 1 Automatic
61662:Ethernet link switchover in link aggregation1group

Automatic
$STATUS
61663:PS tunnel Switchover 1 Automatic
71106:TROUBLESHOOTING DATA RECEIVED 1 Automatic

6
4
0
8
3
0
4
0
8
4
0
8
1
6
2
6
4
0
6
3
1
4
1
9
6
7
1
2
5
6
4
9
6
3
4
2
4
2
0
6
2
1
Time to Live Alarm structure changes since 2
5
M
6
4
9
7
previous release o
3
4
3
4
d
2
1
6
i3
1
7
5
f6
9
4
0
8
1
3
4
6
8
2
6
9
1
6
1
7
2
6
4
0
1
1
3
4
New faults: 1 7
6
8
2
3
Modified faults: 17 6
9
1
7
1
Removed faults: 1 7
2
8
6
4
0 0
2
1
8
4
8
8
3
4
6
9
2
1
7
8
6
4
0
4
8
4
9
0
5
New faults: 2 6
4
2
0
1
9
6
4
Removed faults: 10 1
5
4
8
4
0 0
0
1
5
6
1
1
4
7
4
Removed faults: 2 3
4
3
4
0 1
0
7
5
4
3
7
0
3
2
0 2
1
6
9
6
8
7
4
3
2
1
9
8
9
7
5
Removed faults: 5 3
0
0 8
0
5
4
4
5
2
4
Removed faults: 7 9
0 7
1
4
6
3
6
2
2
0
6
2
8
6
6
5
8
4
8
1
2
4
6
3
1
6
3
2
1
7
2
9
9
6
6
2
2
8
1
New faults: 1 2
4
6
3
1
4
2
8
1
2
0 8
###
9
6
8
9
3
8
2
3
2
6
6
3
5
7
6
2
7
3
1
2
8
0
6
8
9
3
6
8
2
New faults: 1 4
6
6
5
6
3
7
4
7
Removed faults: 2 2
4
5
0
6
0 9
5
4
7
8
3
0
2
6
5
0
6
7
5
4
8
0
6
0
5
8
8
2
6
5
1
New faults: 2 6
7
7
6
9
5
0
6
7
Removed faults: 8 0
2
9
8
1
0 6
0
6
5
0
9
7
0
4
1
6
7
1
0
8
1
4
6
5
0
1
8
1
4
2
6
7
1
3
9
5
6
2
0
0 2
8
1
6
2
6
7
4
9
5
6
2
1
8
2
New faults: 3 2
7
3
5
1
0 8
2
6
2
7
6
3
6
1
8
3
2
6
New faults: 12 7
1
3
0 2
1
8
6
8
2
9
New faults: 8 6
0 3
0
4
0
2
6
New faults: 9 4
Removed faults: 2 5
0 9
0
0
0
0
0
0
0
2
7
2
5
6
0
6
9
7
1
4
0
6
5
6
7
2
9
6
0
8
4
7
2
4
0
6
5
7
2
9
6
0
8
5
7
6
3
0 6
0
6
2
8
7
2
5
6
0
8
2
7
4
6
0 0
6
2
9
7
2
6
6
0
8
2
7
8
5
6
0 1
6
2
0
7
2
9
6
0
9
3
8
9
2
6
1
6
0 7
9
7
2
0
6
1
9
6
8
0
7
6
2
6
7
0 3
8
7
0
6
5
0
7
8
4
6
2
6
7
4
8
7
0 0
6
5
0
8
8
5
7
6
2
6
7
5
8
7
0
6
5
0
9
8
6
8
New faults: 2 6
2
6
6
8
7
6
5
0
0
8
7
9
2
6
7
8
7
6
5
1
8
0
New faults: 1 2
6
9
8
2
5
0 8
1
2
2
6
9
6
2
8
2
3
6
New faults: 4 2
1
3
0 3
1
3
6
9
2
1
New faults: 5 6
0 2
2
6
0
6
3
5
7
5
6
0
5
3
0
6
0
6
4
3
7
5
6
New faults: 5 0
2
3
6
0
8
4
0 7
3
6
0
2
3
2
6
0
6
9
8
8
2
6
3
1
3
New faults: 2 0
6
1
9
7
4
Removed faults: 3 8
2
6
0
0 3
2
3
2
1
2
6
6
2
6
8
6
2
3
3
0
2
2
New faults: 2 6
3
6
6
3
Removed faults: 2 3
3
0
0 3
2
8
6
6
3
1
0 2
7
7
6
8
5
0
6
8
0 1
New faults: 1
0
Modified faults: 1
0 ###
Modified faults: 1
0 ###
0
4
0
2
6
0 6
1
0
0 0
Modified faults: 1
0 ###
Modified faults: 1
0 ###
Modified faults: 1
0 ###
Modified faults: 1
0 ###
0
0
Modified faults: 1
0 ###
Modified faults: 1
0 ###
Modified faults: 1
0 ###
Modified faults: 1
0 ###
0
Removed faults: 1
900000 ###
RUs, 5GC002269: HW addition
and removal without service
impact on ABIO, 5GC002589: 5G
RF sharing with two Airscale
System Modules, CB005850:
NR-LTE concurrent operation
with shared FHS for OBSAI,
CB007135: Common SW for
SRAN and 5G classical,
LTE1656: Management support
for legacy Motorola/Fujitsu RF-
Changes between releases Reason for change equipment, LTE3084:
Related feature(s) Remote
correction
SRAN 21A and SRAN 21B FPFH PDU control via AirScale
SM, LTE4032: AirScale Capacity
ABIC, LTE5286: Common SW
load for LTE and SRAN,
SR001498: Support of FSMF +
FSMF with SRAN configurations,
SR001534: SRAN FM combined
service, SR001730: Fronthaul
5GC000316:
switch support5G onNode
SBTSB (LTE-
5GC000174:
Synchronization 5G Mode
Node Support,
B
only configurations), SR002382:
Software
LTE1996: management,
Flexi Zone Controller
SW Support for AirScale
5GC000933:
Application, MDEA fronthaul
LTE5286: Common
Capacity ABIO including
switch
SW forfor
load 5GLTEdeployments,
and SRAN,
Changed Fault implementation changed common ABIO and ABIN
5GC001246:
SR001534: AirScale
SRAN FM Indoor
combined
Platform SW, SR002576: SBTS-
Radio
service,ASiR LTE andSBTS
SR002956: NR
5G concurrent operation with
concurrent
Operability operation,
OBSAI RUs,support for 5G,
SR002951: Basic
5GC001702:
SR002459: NR-LTE/SRAN
SW support for AGIMLSW
Common load for
AI/ML
Changed Fault implementation changed concurrent
LTE and operation with OBSAI
SRAN
PoC HW, SR002956: SBTS
RUs, CB005850: NR-LTE
Operability support for 5G,
concurrent operation with shared
SR003007: Basic SW Support for
FHS for OBSAI, CB006028:
ASOE, SR002459: Common SW
Independent software upgrade
Changed Fault implementation changed load for LTE and SRAN
for shared RU, CB007135:
Common SW for SRAN and 5G
classical, CB007310: One
classical gNB on dual ASIL,
Changed Fault implementation changed LTE1656: Management support
equipment, LTE3397: LTE C-
5GC002589:
Plane in new 5G RF BTS
Single sharing
OAM with
two Airscale System Modules,
architecture, LTE3656: MDEA
CB007135: Common
Fronthaul Switch SW for
Outdoor DC,
LTE4032: AirScale Capacity
CB007310:
ABIC, One classical
LTE5286: CommongNB SW on
dual
load ASIL,
for LTESR003007:
and SRAN, Basic SW
Changed Fault clarification Support
SR001534: for ASOE
SRAN FM combined
service, SR001730: Fronthaul
switch support on SBTS (LTE-
SW Support for AirScale
Capacity ABIO including
common ABIO and ABIN
Platform SW, SR002576: SBTS-
5G concurrent operation with
OBSAI RUs, SR002956: SBTS
5GC001082: Classical gNB
software Management,
5GC002589: 5G RF sharing with
CB007135:
two AirscaleCommon SW for
System Modules,
CB005850: NR-LTE concurrent
LTE5286: Common
operation with sharedSWFHSload
forfor
LTE and SRAN, SR001534:
OBSAI, CB007135: Common SW
SRAN FMand
for SRAN combined service,
5G classical,
SR002956: SBTS
LTE146: LTE SoftwareOperability
support for 5G,LTE5286:
Management, SR002459:
Common
Common SW load for
SW load for LTE
LTE and
and
Changed Fault implementation changed SRAN
SRAN, SR001534: SRAN FM
combined service, SR002956:
SBTS Operability support for 5G,
SR002459:
5GC002589:Common SW load
5G RF sharing for
with
Changed Fault implementation changed LTE and SRAN
operation with shared FHS for
OBSAI, CB007135:
5GC002589: 5G RFCommon SW
sharing with
Changed Fault implementation changed for SRAN and 5G classical
Changed Fault implementation changed
CB007422: 5G BTS Supervision

harmonization - Part II (signature
Changed Fault implementation changed for crash/failure)

Changed Fault implementation changed ASOE
5GC000829: One classical gNB
on dual ASIK, 5GC001082:
5GC000829:
Classical gNBOne classical gNB
software
on
Management, CB007135: HW
dual ASIK, 5GC002269:
addition
Commonand SWremoval
for SRANwithout
and 5G
Changed Fault clarification service impact on ABIO,
classical, LTE5286: Common SW
CB007135:
load for LTECommon
and SRAN,SW for
SR001498: Support of FSMF +
SR003007: Basic SW
FSMF with SRAN Support for
configurations,
service, SR002956: SBTS
SR002459: Common SW load for
Unrestricted


Removed Not implemented
Changed Fault clarification





































5GC000718: F1 cell
management, 5GC000952:
Recovery for Classical gNB,
5GC001400: FA3UA 5G Airscale
SR003007:
mmWave Basic SWModule
Extension Support for
Changed Fault implementation changed ASOE28G, 5GC001702: NR-
n257
LTE/SRAN concurrent operation
with OBSAI RUs, 5GC001866:
Delivery
SR003007: of beam
Basic set
SWrealization
Support for
Changed Fault implementation changed to gNB, CB005850: NR-LTE
ASOE
concurrent operation with shared
FHS for OBSAI, CB006028:
Independent software upgrade
SR003007:
for shared RU,Basic SW Support for
CB006135:
Changed Fault implementation changed ASOE ORAN Profile L1
Docomo
implementation Step 2 (FD
Beamforming), CB006514:
SRAN 21B Resource
SR003007: Basic SW Pooling
Supportfor
for
Changed Fault implementation changed ABIO/N
ASOE stage 2, CB006942: BTS
(Q)SFP+/SFP28 provisioning
enhancements, CB007135:
SR003007: Basic SWOne
classical, CB007310: Support for
classical gNB on dual ASIL,
equipment,
SR003007: LTE168:
Basic SWLTE System
Support for
Changed Fault implementation changed Maintenance,
ASOE LTE1996: Flexi
Zone Controller Application,
LTE3084: Remote FPFH PDU
control via AirScale SM,
ABIC, LTE4898: NB-IoT: Multiple
non-anchor carriers, LTE5240:
BTS Fronthaul SFP+/SFP28
SR003007:
Base Line atBasic
ABIC,SW Support for
LTE5286:
Common SW load for LTE and
SRAN Dynamic
SR003007: Spectrum
Basic SW Support for
Changed Fault implementation changed Sharing
ASOE GSM+LTE, SR002167:
Dynamic Spectrum Sharing
WCDMA+LTE, SR002187:
Automated DSP HW recovery on
SR003007:
ABIA, Basic SW
SR002382: SW Support
Support for
for AirScale Capacity ABIO
including common ABIO and
ABIN Platform SW, SR002546:
Dynamic
SR003007: Spectrum
Basic SWSharing
Support for
Changed Fault implementation changed WCDMA+LTE,
ASOE phase 2,
SR002576: SBTS-5G concurrent
operation with OBSAI RUs,
SR002951: Basic SW support for
AGIML AI/ML PoC HW,
SR002956: SBTS Operability
support for 5G, SR003007: Basic
SW Support for ASOE,
LTE1996:
Controller Flexi Zone Controller
Application, LTE5286:
parameterisation,
Application, SR001534:
LTE3656: MDEA
Common
SRAN SW
FMSwitch load
combined for LTE and
service,
Fronthaul
SRAN, SR001534: Outdoor
SRAN DC,
FM
SR001730:
LTE4032: Fronthaul
AirScale switch
Capacity
combined
support on service,
SBTS SR002382:
(LTE-only
ABIC,
SW LTE4898:
Support NB-IoT: Multiple
for SR002382:
AirScale
configurations),
non-anchor carriers, LTE5286:SW
Capacity
Support ABIO
for including
AirScale Capacity
Common
common SW load
ABIO and for LTE and
ABIN
ABIO
SRAN, including
SR001534: common
SRAN ABIO
FM
Platform
and ABIN SW, SR002956:
Platform SW, SBTS
combined
Operability service,
support SR002160:
forconcurrent
5G,
SR002576:
I/Q SBTS-5G
routing between system
SR002459:
operation Common
with OBSAI SW
RUs,load for
Changed Fault implementation changed modules
LTE and in SBTS running on
SRAN
AS+FSMF, SR002382: SW
support for 5G,
Support for AirScaleSR003007: Basic
Capacity
ABIO including common ABIO
SR002459: Common
and ABIN Platform SW,SW load for


Changed Fault clarification ASOE

2002040: FN2040, 5GC000829:
One classical gNB on dual ASIK,
5GC001167: FDD DL CA up to 3
CCs, 5GC001451: Support of
8T8R RU for 2T2R / 4T4R
antenna deployments below
6GHz, 5GC001849: Support of
8T8R 8 port BF
5GC000933: MDEAantenna with
fronthaul
calibration
switch for 5Gportdeployments,
below 6GHz,
5GC001866:
5GC002589: Delivery of beam
5G RF sharing with
set
two realization to gNB,
Airscale System Modules,
5GC002589:
CB005850: NR-LTE5G RF concurrent
sharing with
two
operation with sharedModules,
Airscale System FHS for
LTE5286: Common Common
OBSAI, CB007135: SW load forSW
LTE and SRAN,
for SRAN and 5GLTE5589:
classical,TDD
massive
LTE5286:MIMOCommon one carrier
SW loadperfor
ABIC,
LTE and SR001498: Support of
SRAN, SR000912:
FSMF
SBTS SW + FSMF with SRAN
Management,
configurations,
SR001534: SRAN SR001534: SRAN
FM combined
FM combined
service, service,
SR001730: Fronthaul
SR001682:
switch supportAirScale
on SBTSCommon
(LTE-
ASIB PIU SBTS support,
SR002160:
Common SW I/Qload
routing between
for LTE and
Changed Fault implementation changed system
SRAN modules in SBTS running
on AS+FSMF, SR002382: SW
Support for AirScale Capacity
and ABIN Platform SW,
Changed Fault clarification LTE and SRAN

OBSAI, CB006135: Docomo
ORAN Profile L1 implementation
Step 2 (FD Beamforming),
Changed Fault implementation changed SRAN and 5G classical




Changed Fault implementation changed operation with shared FHS for
for SRAN and 5G classical,
LTE4824: NR-LTE concurrent
operation for TDD MAA radios
with split mode, LTE5286:
5GC000933:
AirScale CommonMDEA fronthaul
ASIB PIU
switch for 5G deployments,
SBTS support, SR002956: SBTS
CB007135: Common
Operability support forSW
5G,for
SRAN and 5G
SR002459: classical,
Common SW load for
Changed Fault implementation changed LTE2121:
LTE and SRANRadio Unit reset in
BTS SM, LTE5286: Common SW
CB007135: CommonFronthaul
service, SR001730: SW for
switch support on SBTS (LTE-
5GC000933: MDEA fronthaul

switch for 5G deployments,
CB007135: Common SW
equipment, SR001534: for
SRAN
FM combined service,
SR001730: Fronthaul switch
support on SBTS (LTE-only
configurations), SR002956:
Changed Fault implementation changed SBTS Operability support for 5G


LTE5286: Common SW load for
LTE and SRAN, LTE923: TD-
LTE Ir interface support,
service, SR002459: Common
Changed Fault implementation changed SW load for LTE and SRAN


Removed Not implemented LTE5286: Common SW load for
Changed Fault implementation changed 5GC001240: PIM Cancellation



New
New
New
New
New
New


on dual ASIK, 5GC001167: FDD
DL CA up to 3 CCs, 5GC002589:
Changed Fault clarification 5G RF sharing with two Airscale
classical, SR003007: Basic SW
Changed Fault implementation changed Support for ASOE
5GC000318: 1PPS&ToD Sync
from External GNSS Receiver,
5GC000319: Flexible Sync Input
Priority, 5GC000425: TDD lower
Changed Fault implementation changed layer support - 100 MHz cell
bandwidth, LTE1996: Flexi Zone
Controller Application, LTE5286:
Changed Fault implementation changed combined service, SR002956:
on dual ASIK, 5GC001167: FDD
DL CA up toBasic
SR003007: 3 CCs,
SW 5GC002589:
Support for
Changed Fault implementation changed 5G
ASOERF sharing with two Airscale
classical, LTE2442: Preventing
cell activation, LTE4788: ETSI
Changed Fault implementation changed and IC DFS Support for LAA,
LTE4875: LAA Dynamic Power
Control, LTE4955: AirScale
Capacity cards mixed within one
Changed Fault implementation changed eNB, LTE5286: Common SW
SR002382: SW Support for
AirScale Capacity ABIO including
Removed Not implemented Platform SW, SR002956: SBTS


Changed Fault implementation changed OBSAI


Changed Fault implementation changed 5GC000829:
OBSAI One classical gNB
on dual ASIK, 5GC001904: LTE-
NR In-Carrier Dynamic Spectrum
CB005850:
Sharing PhaseNR-LTE concurrent
I, CB007135:
operation with shared
Common SW for SRAN FHS
andfor
5G
classical, LTE5286: Common SW
service, SR002459: Common


from External GNSS Receiver,
5GC000319: Flexible Sync Input
Priority, LTE1996: Flexi Zone
Controller Application, LTE5286:
Changed Fault clarification combined service, SR002956:
SRAN FM combined service,
Changed Meaning changed LTE and SRAN




5GC000933: MDEA fronthaul

Removed Not implemented switch for 5G deployments,
5GC002269: HW addition and
removal without service impact
on ABIO, CB007135: Common
SW for SRAN and 5G classical,
5GC001246:
LTE5286: CommonAirScale
SWIndoor
load for
Radio
LTE and ASiR LTE SR001534:
SRAN, and NR
concurrent operation,service,
SRAN FM combined
5GC002589: 5G RF sharing
SR001730: Fronthaul switch with
two Airscale
support System
on SBTS Modules,
(LTE-only
CB007135: Common
configurations), SW for
SR002956:
LTE4769:
SR002459:3GPPCommonbaseline R14 for
SW load
Changed Fault implementation changed March
LTE and 2018,
SRAN LTE5286: Common
SW load for LTE and SRAN,
service, SR002382: SW Support
Removed Not implemented including common ABIO and





5GC000167: Fault Management
general flow and mechanism,
New SRAN and 5G classical,
LTE2621: eNodeB Limitation
Actions for License Management
in LTE, LTE4090: AirScale ABIC
HW capacity activation license,
Removed Not implemented LTE5286: Common SW load for

Changed
CB007310: One classical gNB on

dual ASIL, LTE5286: Common
Removed Not implemented SW load for LTE and SRAN,
SR001307: Single Logical SBTS
on AirScale + FSMF, SR002459:
Changed Meaning changed SRAN


Changed Fault implementation changed dual ASIL
50160: TCP/IP measurement,
Backplane Interfaces for Subrack
Sharing, CB007135: Common
SW for SRAN and 5G classical,
dual ASIL, LTE2294: FDD TDD
Coexistence within one eNB,
LTE2866: AirScale operation with
2 Core plugins, LTE5286:
SRAN, SR001682: AirScale
Common ASIB PIU SBTS
support, SR002459: Common


5GC000316: 5G Node B
Synchronization Mode Support,
Removed Not implemented 5GC000829: One classical gNB
Recovery for Classical gNB,
dual ASIL, SR002956: SBTS
CB007160: ITSAR compliant

Changed Fault implementation changed hardening

CB006942: BTS (Q)SFP+/SFP28

provisioning enhancements,


New

Changed Meaning changed SRAN and 5G classical

on dual ASIK, CB007135:
classical, SR002956: SBTS
Changed Fault implementation changed Operability support for 5G
Changed
Changed

ABIC, SR002382: SW Support
including common ABIO and
Basic SW support for AGIML
AI/ML PoC HW, SR002956:


Delivery of beam set realization
to gNB, CB007135: Common SW
Changed Fault implementation changed for crash/failure)
for crash/failure), SR003007:
Changed Fault implementation changed Basic SW Support for ASOE
Unrestricted

Unrestricted

on dual ASIK, CB007135:
Changed Fault implementation changed classical

5GC002491: NR ABIO BB cell
sets up to 12 FDD cells,

New
New
New
New
New
New
New

New
New
Changed
New
New
New
Restricted Feature not delivered
New
New
New
New
New
New
New
New
New

LTE5602: TDD Remote

Interference avoidance based on
Changed Fault implementation changed downhill trend

LTE145part1: Radio Network
Configuration via RROM,
LTE1996: Flexi Zone Controller
Application, LTE4898: NB-IoT:
Changed Fault implementation changed Multiple non-anchor carriers,
Changed Fault implementation changed SR002167: Dynamic Spectrum
LTE163: Subscriber and
Sharing WCDMA+LTE,
Equipment
SR002382: Trace, LTE163b:
SW Support for
Subscriber and Equipment
AirScale Capacity Trace
ABIO including
(vendor
commonspecific
ABIO andextensions),
ABIN
Changed Fault implementation changed LTE1996: Flexi
Platform SW, Zone Controller
SR002546:
Application, LTE433-b:
Dynamic Spectrum Basic Cell
Sharing
Trace adaptations,
WCDMA+LTE, phase 2, LTE4996:
BTS Direct Integration
SR002459: Common SW for load
Trace,
for
Changed Fault implementation changed LTE5286: Common SW load for
LTE and SRAN
LTE and SRAN, LTE690-b: LTE
Interface Trace Support, LTE690:
LTE Interface Trace Support,
SR001486: Support for already
Changed Fault implementation changed delivered SRAN16.2/16.10
features, SR002215: BTS Direct
Integration for Trace, SR002459:




5GC000313: Timing over Packet

with Phase Synchronization,
Changed Fault implementation changed 5GC000829: One classical gNB
Delivery of beam set realization
to gNB, CB007135: Common SW
Changed Fault implementation changed for SRAN and 5G classical,
LTE and SRAN, SR002382: SW
Changed Fault implementation changed and ABIN Platform SW,
support for 5G, SR002459:






5GC000718: F1 cell
management, 5GC000829: One
classical gNB on dual ASIK,
5GC000900: Concurrent SA and
NSA operation,
5GC000718: F1CB007135:
cell
Common
management, for
SW SRAN andOne
5GC000829: 5G
classical gNB on dual ASIK,
Changed Fault implementation changed Operability
5GC000900: support for 5GSA and
Concurrent
NSA operation, CB007135:
Changed Meaning changed
New

5GC000742: System Information
Broadcast - intra-NR,
5GC000746: CMAS (Commercial
Mobile Alert System), CB007135:

Unrestricted
Unrestricted
Unrestricted
Unrestricted
Unrestricted
Unrestricted
Unrestricted
Unrestricted
Unrestricted
Unrestricted
New
Changed
Changed
Changed
Changed
5GC000313: Timing over Packet

with Phase Synchronization,
5GC000609: ToP with Phase
Sync Resiliency, 5GC000713:
Timing over Packet (ToP) with
Frequency Synchronization,
5GC001357: ToP Phase
Resiliency with Ethernet
Multicast, LTE1996: Flexi Zone
Controller Application,
SR000384: Timing over Packet
Resilience, SR001799: ToP
Phase Sync Resiliency with
Ethernet Multicast, SR002774:
Support of AirScale SEI port for
primary synchronization input
Changed Fault implementation changed with PTP
5GC000267: IPsec Backup
Tunnel, CB007135: Common SW
for SRAN and 5G classical,
LTE1753: IPSec Backup Tunnel,
LTE3440: LTE Operability
Security Feature Parity with
Single OAM, SR000600: Backup
IPsec Tunnel, SR001664:
Secondary IPsec backup tunnel
Changed Meaning changed for Public Safety network
Changes since previous issue Restriction status Technology
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No
No
No
No
No
No
No
No
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No
No SRAN
No
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No
No
No
No
No 4G
No SRAN
No
No
No
No
No
No
No
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No 4G
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No 4G
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No 4G
No SRAN
No SRAN
No SRAN
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No
No SRAN
No SRAN
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No SRAN
Yes SRAN
Yes SRAN
Yes SRAN
Yes SRAN
No SRAN
No 4G
No 4G
No SRAN
No SRAN
No SRAN
No 4G
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No 4G
No 4G
No SRAN
No SRAN
No 4G
No SRAN
Yes SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No SRAN
No SRAN
Yes SRAN
No SRAN
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 5G
Yes SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No SRAN
No SRAN
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
No
No
No
No
No
No 4G
No
No
No
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No 4G
No
No
No
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No SRAN
No 4G
No 4G
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No 4G
No 4G
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
Yes SRAN
No SRAN
Yes SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No SRAN
No
Fault ID Fault Name
2 Unit temperature is high
6 Unit SW download failed
Difference between BTS master clock and

9 reference frequency
10 No connection to unit
12 Baseband resources mapping to cells failure
13 TUPC configuration failure
16 Unit synchronization failed
17 BTS RNC interface signalling link failure
18 BTS RNC interface signalling link failure
23 Incompatible SW version detected

24 Obsolete SW version detected
Error in file server during file upload or

27 download operation
28 File corrupted in SW download
29 BTS SW download or activation failed
30 BTS SW download or activation failed
37 Mains power break, running battery backup
49 Cell blocked
50 BTS blocked
52 # autonomous reset as recovery action
69 POST test failed
88 Missing NBAP cell parameters
94 Unknown HW resource
95 Unit not supported by current BTS SW version

103 Carrier power measurement does not work
110 Unit RNW configuration failure
114 Communication failure with RNC
115 Cell enabling failure
124 Not enough DSP capacity to set up the cell
125 Tx power level too low
126 Cell power parameter out of range
Not enough resources for commissioned

130 HSUPA
133 Rx signal level failure
134 Rx signal level failure
139 DSP mode change failed
DSP allocation to PIC not possible due to DSP

145 resource unavailable
DSP allocation to PIC not possible because

146 DSP is occupied by some other users
Ten consecutive rejects received from a DSP at
149 DCH setup
154 PIC pool configuration failure
Not enough CCCH Processing Set licenses

157 commissioned
158 Hanging HSPA resources in DSP
One of the Common Transport Channels is

160 deleted
Commissioned HS-RACH resource steps not

162 possible to be allocated [LCG <LCGid>]
Incorrect Carrier Aggregation Configuration

165 [LCG <LCGid>]
Unsupported Carrier Aggregation Group ID

167 change [LCG <LCGid>]
NBIC resource block is not available [LCG

169 <LcgId>]
170 Unsupported TX Configuration
DSS resource block is not available [LCG

171 <LcgId>]
172 Internal failure during WCDMA-LTE DSS
Communication failure detected during

173 WCDMA-LTE DSS
Unutilized hardware baseband resources by
181 WCDMA
214 Flash operation failure
215 Flash operation failure
234 Access panel port(s) enabled
237 BTS power cycle detected
238 Filter clogged
239 Heater defective
240 Subrack Control Board Unit defective
241 Subrack Control Board Sensor board defective
Fault between FSM and FSP because of the

412 lack of RP1 clock
418 Fatal OSE Error
476 Antenna link is down
1300 Cabinet door open

1400 [User defined]
1401 [User defined]
1402 [User defined]
1403 [User defined]
1404 [User defined]
1405 [User defined]
1406 [User defined]
1407 [User defined]
1408 [User defined]
1409 [User defined]
1410 [User defined]
1411 [User defined]
1412 [User defined]

1413 [User defined]
1414 [User defined]
1415 [User defined]
1416 [User defined]
1417 [User defined]
1418 [User defined]
1419 [User defined]
1420 [User defined]
1421 [User defined]
1422 [User defined]
1423 [User defined]
1424 [User defined]
1425 [User defined]

1426 [User defined]
1427 [User defined]
1428 [User defined]
1429 [User defined]
1430 [User defined]
1431 [User defined]
1432 [User defined]
1433 [User defined]
1434 [User defined]
1435 [User defined]
1436 [User defined]
1437 [User defined]
1438 [User defined]

1439 [User defined]
1440 [User defined]
1441 [User defined]
1442 [User defined]
1443 [User defined]
1444 [User defined]
1445 [User defined]
1446 [User defined]
1447 [User defined]
1517 External Alarms Misconfigured
1518 Second External Alarm Box Detected
1802 BTS file error
1806 Communication failure

1807 Invalid frequency channel for the BTS HW
1811 Baseband bus configuration was rejected
1815 Not able to synchronize baseband bus
1816 Transmission clock missing
1817 Oven oscillator heating failure
1818 BTS master clock tuning failure
1819 Oven oscillator clock missing
1834 Mast Head Amplifier fault above current window
1835 Mast Head Amplifier fault below current window
1836 Antenna line failure
1837 VSWR major alarm
1838 VSWR minor alarm
1839 Low noise amplifier failure

1840 Filter tuning failure
1841 Filter unit faulty
1842 RET Antenna control failure
1847 Antenna line device HW failure
1848 Antenna line device missing software
1850 SW corrupted
1858 Faulty configuration of system modules
BTS configuration error (not enough HW for

1868 LCR)
1869 MHA operation degraded

1870 MHA operation failure
1871 Antenna Line Device Operation Failure
1888 Antenna line device configuration failure
1893 Internal delay measurement failure
1898 PPS reference missing
1899 2M external reference missing
1900 RF Module configuring failed
1901 RF Module critical file not found
1902 RF Module file not found
1903 Frame clock missing

1904 RF BB bus synchronization error
1905 RF BB bus configuration error
1906 RF BB bus connection transmission error
1907 TX out of order
1908 RF Module gain adjusting failure
1910 RF Module filter input power missing
1911 RX out of order
1912 RF Module out of order
1918 RF Module power supply output faulty
1920 No feedback signal
1921 Transmission quality deteriorated
1922 Temperature too low (Heating ongoing)
1923 Unit unidentified

1924 Configuration file corrupted
1925 Post test failed
1926 Module Clock faulty
1927 RF Power decreased
1928 FPGA SW update failed
1931 RF Module blocked
1932 No module fan detected
1933 Cooling fan broken
1934 Cooling fan has reduced from the set speed
1936 Unit (module) temperature is high
1937 Unit (module) dangerously overheating
1938 Pipe dangerously overheating
1939 Ambient temperature violation

1942 RF Module overvoltage protection faulty
1948 SFP Failure
Increased BER detected on the optical

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

1956 to Radio Module
1957 Antenna line switched off due to high VSWR
RP3 routing collisions are detected on FR

1958 module
1959 RF Module power input faulty
1960 RRU DPD self test failure
1961 RRU CPU and DSP link failure
1962 DSP loading failure
1963 FPGA R/W error
1964 SFP missing
1965 Abnormal CPRI Interface to Upper Hop

1966 Severe SFP Performance Aggravation
1967 Severe SFP Reception Power Aggravation
1969 Mismatched RRU optical module
1971 Abnormal reception on SFP to Upper Hop
1972 RRU power loss
1973 Abnormal reception on SFP to Next Hop
1974 Abnormal CPRI interface to Next Hop
1975 BTS RF BB energy too high
1976 No downlink baseband data
1980 PA Critical temperature threshold exceeded
1981 FR module reset requested
RF Module External Alarm and Control lines

1982 configuration failed
1983 TX output overdrive

1984 RF Module faulty primary optical link
1985 TX input overdrive
1986 SFP on RF Module faulty or unsupported
Antenna calibration error caused by

1987 transmission path failure
1988 Antenna periodic calibration has failed
Receive diversity expansion module

1989 communication failure
1990 Radio module internal communication failure
1991 Radio module access panel open
Radio module internal hardware configuration

1992 mismatch
Radio module internal hardware assignment

1993 indeterminate
Radio module low optical signal level to upper

1994 hop
Radio module low optical signal level to next

1995 hop
1996 Link frame timing error

1997 RF data setup failure
PIM Performance Measurement Threshold 2

1999 Exceeded
2000 Optical Interface faulty
2001 Optical Interface faulty
2002 Receiving failure in Optical Interface
2004 10b8b coding error in optical interface device
2006 Optical interface data/control/ethernet buffer full
2010 Optical interface data/control/ethernet buffer full
2011 OIC MCU Buffer Full
2016 BB bus reception error (summing device)
2017 BB bus transmission error
2019 Address mismatch in summing
2054 Buffer over/underflow in clock crossing logic

2056 Firmware SW mismatch
2058 Message routing problem in receiver (RX)
2059 Summing not enabled for message type
2060 Transmission rule collision in Muksu
2061 Overload collision in transmitter
2073 SRIO enumeration
2074 SRIO retry stopped
2078 Eeprom read error
2080 SRIO host link down
2087 Critical SW Component failure
2326 SRIO link degradation
2400 TRX initialization failure
2401 TRX control plane link failure

2403 Configuration mismatch between BSC and BTS
RSSI difference between main and diversity

2404 paths exceed the threshold
BCF Power compression feature license

2408 missing
OMU signaling connection failure in Abis

2412 interface
2413 Invalid BTS configuration or timeout from BSC
BSC does not respond to BTS initialization

2414 procedure
TRX added to an antenna hopping sector at

2415 runtime
Mismatch in the commissioned and configured

2416 BCF identifier
Timing accuracy not guaranteed to be within

2417 configured GSM limits for loose HSFN
2419 PMTU BTS to BSC less than configured MTU
Configuration Mismatch Between BSC and

2421 Commissioning for DSS
Peer RAT Communication Failure when DSS

2422 feature is enabled
2423 Configuration mismatch between BSC and BTS

2424 Dynamic Power Pooling not in use
PIM Performance Measurement Out-of-

2900 Correction Range
Hardware and PIM Cancellation Feature

2901 Activation Mismatch
2902 PIM Cancellation Enabling Failed
HW and external PIM cancellation feature

2903 activation mismatch
2907 C/U-plane logical Connection faulty
2908 Interface Fault
2909 Unexpected C/U-plane message content fault
2910 Power Amplifier faulty
2913 Unit (antenna submodule) SW download failure
2915 Antenna module lost
3000 System Module failure
3003 Failure in replaceable baseband unit

3010 RF Module failure
3012 Failure In Optical Interface <optIf ID>
3020 Baseband bus failure
3030 Failure in optical interface
3040 Temperature alarm
3050 Fan failure
3060 Commissioning error: <x>
3070 Configuration error: <x>
3080 BTS reference clock missing
3090 BTS internal SW management problem
3100 Antenna Line Device failure
3120 Mast Head Amplifier fault
4001 BTS reset required

4003 Transmission path failure
4008 Power level not supported
GPS Receiver alarm: control interface not

4011 available
4019 Master unit has lost connection to the slave unit
4025 Internal MTU configuration failure
4026 Toggling: <Fault name>
4030 BTS is uncommissioned
4036 Invalid configuration file
4038 Radio master conflict
4040 Unit initialization failure
4043 Tuning frequency out of range
4044 Incoherency in cell configuration
4045 Antenna line faulty

4046 Antenna line operation degraded
4047 Antenna line device SW download failure
4048 Antenna line device SW download failure
4058 Connection to ToP master missing
4066 SRIO multicast configuration failed
4069 ALD Port power failure
4072 Parallel optical link length mismatch
4073 Fan vendor not detected
4076 Distributed site support not enabled
4077 FSP overheating
4078 Cooling fan broken
4082 SW fallback
4083 SW fallback
4084 Feature activation is missing
4085 SW fallback
4088 File System access failed
4090 Cell power failure
4091 BTS reset time increased
4092 Summing service default initialization failed
4102 Boot configuration inconsistency detected
Power on #smodLogicalId #pwrLineId line

4107 switched off remotely by user
4110 Peer system module connection lost
4114 Synchronization master missing
4122 GPS receiver alarm: not tracking satellites
4123 GPS receiver alarm: survey in progress
4124 GPS receiver alarm: no stored position

4125 GPS receiver alarm: position questionable
4126 GPS receiver alarm: EEPROM invalid
4141 DC voltage administratively disabled
3GPP/AISG communication administratively

4142 disabled
4145 Validation of signed file failed
4153 Reference clock missing in startup
4160 BTS synchronization is missing during startup
4176 Failure in log file gathering
4178 TD-SCDMA major alarm
4179 TD-SCDMA minor alarm
4180 Operation on shared optical port failed
4181 Configuration reset
4182 BTS or unit temperature too high

4183 BTS or Unit temperature too low
4184 BTS startup temperature out of specification.
4185 RF Unit temperature too high
4186 ToP clock tuning failure
4187 Synchronization holdover time expired
4188 Flexi Zone Micro BTS system clock missing
4189 No connection to RP1 interface
4190 BTS power voltage rail failure
Failure in connection to Real-time PM

4203 Collection Entity
4206 MS 1PPS reference missing
4208 Unit initialization failure
4210 External GPS receiver in holdover
Radio slave has taken temporary radio master

4220 role
4238 Antenna line setup failure
4239 Antenna line device operation failure
4253 Shared radio not synchronized to Radio Master
4254 Beamforming cell parameter mismatch
4255 ALD port configuration failure
Fiber delay and antenna round trip delay

4256 exceeded
4258 Z1 Link Failure
4259 SWDistributionFailure
4260 AP blocked
Cell disabled due to unknown problem; logs

4261 collected
4262 SRIO link outage
4265 Configuration Failed
Failure to verify the signature of a signed

4266 software release
4267 Failure to verify a signed software release
Unsigned software release has been

4268 successfully downloaded
Failure to download software due to missing

4269 software signature
4270 LNA in bypass mode
FR not critical functionality not supported or are

4271 not configured correctly.
GPS receiver alarm: recommended firmware is

4272 not in use
Non-recoverable Synchronization Alignment

4273 Fault
Compensation buffer is not enough for RF

4276 module delay difference
Too long optical cable between system module

4277 and radio module
4278 RF module unauthorized
4281 AP Discovery Failure Due to Misconfiguration
4282 Configuration and hardware mismatch
4283 BTS Location Lock failed

4284 BTS Location Lock violation detected
4288 Inter-Site CA SW interface incompatibility
4289 Inter-Site CA incorrect cluster configuration
4290 Inter-Site CA link establishment failure
4291 Inter-Site CA X2 link unavailability
4293 IP Traffic Capacity Limit
Communication Loss on all S1 links and OAM

4295 link
4296 Constellation mode not supported
4297 NTP Server $IP unavailable
4298 ToP reference missing
4299 Synchronous Ethernet reference missing
4300 PDH reference missing
4304 Too long fiber for mDTX activation

Inter eNB carrier aggregation configuration
4305 does not match available baseband HW
4308 Micro DTX configuration failure
4309 Connection Unstable At 6Gbps
4310 Connection Unstable At 3Gbps
4312 toor4nsn Password Update failure
4319 RIBS Synchronization Not Available
4320 Phase error exceeds 50 ns limit
4321 Configuration change rejected by BTS
4322 FZAP Not Connected Successfully
4328 Manual location entry not supported
Radio memory consumption exceeds abnormal

4329 threshold
Radio memory consumption exceeds critical

4330 threshold
4331 FZC LTE time out of sync

4334 Serial console activated
DSP U-Plane computing environment startup

4335 failed
4337 Active users license limitation
U-Plane Computing Environment Container

4339 Failure
Previously downloaded plan [planId] was

4340 overwritten by a new plan [planId]
4341 FSP subunit lost
4342 Optical link speed change failure
4344 Z3 Link Failure
SFN Antenna Discovery Failure Due to

4346 Misconfiguration
4347 SFN Antenna Not Connected Successfully
4348 SFN Antenna blocked
Cell Shutdown Due To Baseband Capacity

4349 License Limit
No connection between primary and BTS

4352 extension system module
4354 SFN Antenna registration failure
4355 SFN Antenna cell setup failure
4356 SFN Antenna cell deletion failure
4357 SFN Antenna cell shutdown failure
4358 SFN Antenna cell reconfiguration failure
4359 SFN Master initialization failure
4362 SFN Antenna Configuration Failed
4363 SFN cell disabled due to feature disable
Inconsistency between primary and extension

4364 system module
Power on #smodLogicalId #pwrLineId line

4365 switched off at the front panel
Ethernet malfunction between BTS primary and

4367 secondary system module
Multiple Radio Sharing Unsupported by Peer

4370 System Module
4373 IP Address Conflict Between Radio Modules

IP Address Conflict Between Peer System
4374 Modules
4375 CPRI-A RF sharing mode conflict
Dynamic Pool Resources Not Sufficient To

4377 Setup Cell
Dynamic Pool Resources Permanently Not

4378 Available
4383 Virtual node not responding
4385 PPS reference from backplane missing.
4387 Frequency configuration error
4389 OTDOA PRS transmission disabled
4391 BTS Mediator connection lost
4392 RAT SW Fallback
Configuration and RF Module mismatch for

4393 Reduced LTE Guard Band
4394 Inter-Site CA link unstable
4395 Cells shutdown due to mains power break

4396 Unable to assign IP Address to radio
4399 One or more carrier groups blocked
4401 Phase error exceeds threshold set by BSC
4403 SRIO Route Configuration Failed
Timing accuracy not guaranteed to be within

4404 configured LTE limits for loose HSFN
4405 No usable time reference available
One or more TRXes did not receive System

4406 Information from BSC
4409 RX gain configuration failure
4410 Measurement of roundtrip delay failed
Leap Seconds value discrepancy on Access

4412 Points
4413 Configured IP Address Mismatch
4419 Power Group shutdown procedure failed
4420 GPS receiver alarm: firmware upgrade ongoing

4421 No more IP addresses available
Internal baseband path configuration failure for

4422 a cell
AP Discovery Failure Due to Lack of S-Plane IP

4425 Address
4439 GNSS receiver signal inaccurate
4452 Phase error exceeds the interference limit
4457 CPRI-A radio with unsupported connection
4458 SSH Login Configuration failed
4459 User Account has Default Password
Sleeping Cell Detection Due To Low RRC

4463 Success Rate
4464 ExtPimPerformanceMinorThreshold
4465 ExtPimPerformanceMajorThreshold
4466 ExtPimCancellationHwLimitsExceeded
4467 BTS Hotel Configuration Error

4468 Inter eNb Connection Loss In BTS Hotel
4469 Inter eNB communication failure in BTS hotel
4470 Southbound Interface Configuration Mismatch
Configuration mismatch between BTS and

4471 controller
Increased BER detected on the optical

4476 connector
4477 ICOM Route Configuration Failed
4478 Antennas assignment not available
4479 Failure detected on assigned antennas
4488 LNA DC Configuration Failure
4489 SW fallback
4491 LAA Configuration Invalid
ASIRMOD configuration and hardware

4492 mismatch
4499 RF Sniffing Request Rejected

4500 RF Test Rejected
4501 BTS has no connection to RF Scan Collector
4502 RF Sniffing Data Upload Failed
Configuration change requiring RAP restart

4520 detected
4521 LAA Cells Power Too Low
4522 LAA Invalid Hardware Configuration
Unsupported radio connection configuration

4525 detected
4527 Radio Diagnostic Files collected
4530 TD-LTE radio disabled
4532 CBRS Power Level Violation
4538 Power distribution unit failure
4539 5G BTS configuration failed
4540 5G cell update failure

Sleeping Cell Detection Due To Abnormal
4546 Antenna RX Power Measurements
Sleeping Cell Detection Due To Degraded

4547 RACH Setup Attempts
Sleeping Cell Detection Due To Degraded RRC

4548 Connection Setup Attempts
4549 External PIM Calibration Needed
4550 Calibration Ongoing
4551 Calibration Failure
4559 Unit Configuration Failure
4560 Power Group Switch ON Procedure Failure
4562 Antenna Carrier Failure
4563 Incompatible Beam Set configuration
4564 Copy SW/config to passive partition failed
Configuration mismatch while commissioning

4565 WCDMA LTE DSS
4567 Shared Bandwidth Usage Failure

The following KPI formulaX has been fulfilled:
4569 <formulaDescriptionX>


















4589 Unit power reset
4590 Fault signature for crash or failure
Band and PLMN configuration mismatch with

4591 RF Module
4592 BTS Reset Cause
4594 BTS Integration Failure
4595 Transport SW crash or critical failure

Blanked PRBs Not Overlap With Radio Filter
4596 Guardband
4597 Fronthaul RRH reference missing
4598 Tilt Offset is out of steering range
Sleeping Cell Detection Due To Abnormal

4599 Antenna TX Power Measurements
Sleeping Cell Detection Due To Degraded S1

4600 Communication
Sleeping Cell Detection Due To Degraded

4601 RACH Preambles
4602 5G cell configuration mismatch
4606 Delay adjustment needed
Inter-eNB or inter-site carrier aggregation

4607 disabled due to hardware limitation
4609 SAS Feature Data Exchange Failure
4610 No connection to radio after protocol change
4613 BSR file missing or incomplete
4614 RAT blocked

KPI triggering formula performance threshold
4635 exceeded
NB-IoT guardband non-anchor carrier

4636 frequency not supported by radio module
NB-IoT carrier performance degradation

4637 possible
NB-IoT guardband anchor carrier frequency not

4638 supported by radio module
Problem sending VES event to ONAP VES

4639 Endpoint
4640 Netconf SSH algorithm negotiation failure
4641 SSH client authentication failure
4642 SSH Server Authentication failure
Netconf SSH server authentication is disabled

4643 at first RU-DU connection
4644 Default Netconf account creation failure
4645 Additional Netconf account creation failure
4647 UTC out of sync
Active RF SW in newer version not aligned with

4651 any BTS
Independent SW upgrade for shared RU
4652 unaligned between BTSs
4654 Ethernet port security is disabled
4655 Service account root access is enabled
4656 Transceiver compliance validation failure
4657 Nokia MN BTS SFP validation failure
4658 Transceiver temperature too low
4660 FHS primary controller conflict
FHS secondary controller has taken temporary

4661 FHS primary controller role
4662 Number of supported O-RU objects exceeded
4663 Baseband card crash has been detected
4664 eCPRI beamforming configuration invalid
4666 APTS data invalid
4667 IPSec On Radio Module Unsupported

4670 RAT reset required
4676 Duplicate PRACH configuration index
Inconsistency of air interface timing offset

4677 configuration
Unsupported radio module type for air interface

4678 timing offset configuration
4683 Autonomous carrier teardow by Radio
4687 CPRI RU Migration to eCPRI Mode Required
Maximum number of 1xRTT neighbor relations

5500 per cell exceeded
Maximum number of 1xRTT NR per cell and

5501 carrier exceeded
5502 SIB15 information incomplete
Invalid NB-IoT inband downlink non-anchor

5510 PRB from host cell
Cell re-deployment is needed for enabling inter-

5511 eNB FDD-TDD CA
5512 SRS Resources Not Configurable
6051 Beamforming calibration failure in RF data path

6053 U-plane overload detected
6112 Phich Power Boost not applied
6117 High interference to UL subframe
6118 High interference to UL special subframe
6124 Remote interference in UL subframe
Clear Channel Assessment Reports Not

6125 Received
Remote Interference eNB identity detected and

6126 own specific sequence is sent
Remote Interference avoidance is active and

6127 DwPTS rollback as SSP5
EN DSS Setup Failure - Incompatible Message

6128 Set
EN DSS Setup Failure - Max EN DSS Counter

6129 Value reached - No DSS Partner Cell

6130 Value reached - No answer from CRM
EN DSS DL Cell Coordination Failure -
Resource Conflict - Cannot change LTE NR
6131 DSS configuration
6132 EN DSS Keep Alive Procedure Time out

Resource Conflict - Non matching resource
6133 reservation configuration
6134 EN DSS De-activated on partner side
EN DSS DL Cell Coordination Failure - DSS

6135 configuration Error
EN DSS UL Cell Coordination Failure -


EN DSS UL Cell Coordination Failure - DSS

6139 EN DSS DL Cell Aperiodic Switch failure
6150 GTP-U Path Failure
Transport layer connection failure in S1

6202 interface
Transport layer connection failure in X2

6203 interface
6204 S1 SCTP path failure

Transport layer connection failure in M3
6205 interface
6206 M3 SCTP path failure
6252 Incorrect radio network parameters
6253 Cell configuration data distribution failed
6257 Cell reconfiguration data distribution failed
Failure in internal BTS connection or

6261 connection to 3rd party tool
6262 BTS vendor-specific file fault
6263 Failure in trace session
6264 No MME capacity assigned by Core Network
Maximum number of neighbor eNBs/cells

6265 exceeded
Maximum number of WCDMA neighbor cells is

6268 exceeded
Maximum number of WCDMA neighbor

6269 relations is exceeded
Maximum number of WCDMA neighbor

6270 relations per cell and carrier is exceeded
6274 Neighbor cell ambiguity detected
6278 MFBI cell configuration conflict
6279 PCI confusion detected
6280 Phase error exceeds 5 us limit
6281 WCDMA PSC confusion detected
Inter eNB CA parameter(s) inconsistency in

6282 between eNBs
Inter eNB SW inconsistency in between cluster

6283 members
6284 Inter eNB communication failure
Overload detected: max number of neighbor

6285 relation objects reached
Overload monitoring: High number of neighbor

6286 related objects
6287 Inter eNB synchronization loss
6290 SRIO topology failure
6291 Carrier aggregation relation configuration error

6292 Resource pool configuration failed
6293 eNB configuration failed
6294 Not enough PUSCH resources for PRACH
6295 PUCCH configuration inconsistency
6296 GTP tunnel setup for inter-site CA failed
Latency of the link for inter-site CA permanently

6297 exceeds threshold
6298 Invalid sidelink transmit pool configuration
Maximum number of 1xRTT neighbor cells

6299 exceeded
6303 X2 interface recovery failure
6304 X2 interface setup failure
6308 S1 interface setup failure
6317 S1 interface recovery failure
6321 S1 eNB configuration update failure

6322 RIM interface timeout
6323 RIM interface error
Maximum number normal call UEs are

6324 connected to the eNB Zone
Maximum number handover/emergency call

6325 UEs are connected to the eNB Zone
6326 Automatic X2 IPsec Tunnel Setup Failure
6327 Setup of X2 connectivity to gNB failed
System information broadcast parameters

6351 overflow
6352 Delayed online parameter modification
Beamforming file not found, corrupted or

6354 incomplete
6355 No PLMN available for cell $ID
6356 Automatic Access Class Barring is active
SIB5-BR (SIB5 for CatM) Information

6357 Incomplete
SIB2-BR (SIB2 for CatM) Information
6358 Incomplete
6450 Diagnostic Files collected
RF Module Does Not Support Classical RF

6452 sharing
6502 High memory consumption
6600 Pdsch Transmission Error
6700 Correctable bit toggling error
6701 Critical bit toggling error
6702 Not critical bit toggling error
6706 DSP platform fatal error
6707 DSP application fatal error
6708 Externally triggered DSP fatal error
6709 DSP concurrent crash error

6710 AIF2 HW data buffer overflow
GPS reference source indicates antenna short

6803 or overcurrent
6814 Inter-core communication failure
6815 Multi-carrier cell disabled
6816 Control Plane IP Address Mismatch
6817 Periodic CAM Report Inconsistency
6818 Periodic CAM Reports Not Received
6819 LTE-U Channel Change Failure
6820 LTE-U Duty Cycle Change Failure
NTP Frequency Synchronization Server Not

6821 Reachable: $IP
NTP Frequency Synchronization OCXO

6822 Calibration Expired
6823 SAS Grant Termination Revocation Failure
6824 SAS Grant Termination Relocation Failure

6825 SAS Grant Suspension Failure
6826 SAS Registration Failure
6827 SAS Spectrum Inquiry Failure
6828 SAS Grant Failure
6829 SAS Heartbeat Failure
6830 SAS Spectrum Relinquishment Failure
6831 SAS Spectrum Deregistration Failure
6832 SAS Server Communication Failure
6833 SAS RSSI Measurement Failure
6834 Periodic MF Report Inconsistency
6835 Periodic MF Reports Not Received
6836 MF Channel Change Failure
6850 M3 interface recovery failure

6851 M3 interface setup failure
MBMS subframe pattern share exceeds

6852 available share
6854 MCE configuration update failure
6855 MCE internal communication failure
MBMS session admission failure - not enough

6856 resources
MBMS session admission - partial admission

6857 only
MBMS session admission failure - overlapping

6858 MBSFN config
6907 High PDU input voltage
6908 Low PDU input voltage
SRIO HW issue detected during sRIO message

6910 receiving
Double oven oscillator microcontroller firmware

6911 or hardware failure
6914 Lower than expected SRIO link width
6915 Corrupted boot flash detected

6916 Degraded boot flash detected
6917 Recovered boot flash detected
6918 Non critical SW Component failure
6920 Incompatibility of booting capabilities
6921 Transceiver power class incompatibility
6922 SFP high power mode activation failure
6924 SRIO link HW failure
6925 Cooling Incompatible Module
7000 LTE Hardware Accelerator Fatal Error
7001 LTE Hardware Accelerator Concurrent Crash
LTE Hardware Accelerator Externally Triggered

7002 Crash
F1 Cell activation failed due to X2 link

7100 unavailable
7101 gNB CpCell configuration update failure

7103 SA cell activation failed
7105 Cells of the TAC barred due to slicing criteria
7300 No X2 link available
F1AP Reset fails upon non response from gNB-

7301 DU
7302 F1AP protocol error detected by gNB-CU
7303 F1 SCTP endpoint in CU
7304 NG SCTP endpoint broken
7305 NG SCTP setup fail
7306 Xn SCTP endpoint broken
7307 Xn SCTP setup fail
Transport layer connection failure in X2

7308 interface
7310 E1 SCTP Endpoint Failure CuCp
7311 No Xn link available

7312 NgGnbInitFullReset
7313 NgGnbInitPartialReset
7314 NgamfInitFullReset
7315 NgamfInitPartialReset
7316 NgSetupFailure
7317 NgSetupStopRetry
7318 NgSetupNoResp
7319 No X2 link available for a specific LTEENB
7320 NgRANConfigUpdateFailure
7321 NgRANConfigUpdateNoResp
7322 NgResetNoResp
7323 NgamfInitErrorInd
7324 Maximum of X2 links reached

F1AP Setup fails upon non response from gNB-
7500 CU
F1AP Reset fails upon non response from gNB-

7501 CU
F1AP Setup fails upon failure response from

7502 gNB-CU
7503 F1AP protocol error detected by gNB-DU
7504 F1 SCTP endpoint in DU
7505 F1 SCTP setup in DU
7506 gNB CpRtCell configuration update failure
EN DSS Setup Failure - Incompatible Message

7507 Set

7508 Value reached - No DSS Partner Cell

7509 Value reached - No answer from CRM

7511 EN DSS Keep Alive Procedure Time out

7513 EN DSS De-activated on partner side
7514 EN DSS Configuration failure
7515 EN DSS XpIf registration failed
7516 Incorrect cell parameter configuration
EN DSS DL Cell Coordination Failure – DSS



EN DSS UL Cell Coordination Failure – DSS

7521 EN DSS DL Cell Aperiodic Switch failure
7523 Cell Activation timeout at gNB-DU
7700 E1 Setup Failure after retries
7701 E1 SCTP Setup Failure
7702 E1 Setup Failure Response after retries

7704 E1 SCTP Endpoint Failure CuUp
7705 UP slice counter configuration update failed
Failure in connection between BTS and 3rd

8000 party tool
8150 NRRELNotConfiguredA3A5
9000 Temp Fault1
9001 Temp Fault2
9002 Temp Fault3
9003 Temp Fault4
9004 Temp Fault5
9005 Temp Fault6
9006 Temp Fault7
9007 Temp Fault8
9008 Temp Fault9

9009 Temp Fault10
61008 User Event Temporay Buffer Over Threshold
61022 BFDGRP-$BFDGRPID down
61028 LOF on $UNIT, $INTERFACE
61029 LOS on $UNIT, $INTERFACE
61030 Dead Peer Detected
Interface under test on $UNIT, $INTERFACE

61040 for $LOOPTIMEOUT minutes
61050 Missing SFP module on $UNIT, $INTERFACE
61074 CRL Update Failure
Link OAM loopback inserted on $UNIT,

61075 $INTERFACE by $PEER
61076 Link OAM link lost on $UNIT $INTERFACE
Link OAM critical link event $E on $UNIT

61077 $INTERFACE
61079 SFP HW Failure on $UNIT, $INTERFACE

61104 EBER on $UNIT, $INTERFACE
61150 LOMF on $UNIT, $INTERFACE
61151 AIS on $UNIT, $INTERFACE
61152 RDI on $UNIT, $INTERFACE
61250 IPCP Failure
61251 LCP failure
61252 PPP Interface down
CCM fault level $LEVEL, prio $PRIORITY,

61410 cause $CAUSE
ETH AIS fault on $UNIT, $INTERFACE, level

61411 $LEVEL, MAC $MACADDRESS
Automatic BTS Operator Certificate retrieval

61510 unsuccessful
61524 SSH enabled
61605 BFD-$BFDID down in ingress
61606 BFD-$BFDID down in egress

Auto-negotiation mismatch on $UNIT,
61607 $INTERFACE
61610 RTT threshold crossed on TWAMP-$TWAMPID
61611 PLR threshold crossed on TWAMP-$TWAMPID
61616 Vendor BTS certificate has expired
BTS and/or peer trust anchor expired or due to

61618 expire
61622 MLPPP link Degrade
SyncE SSM Timed Out on $UNIT,

61623 $INTERFACE
SyncE Quality Level Degraded on $UNIT,

61624 $INTERFACE
CBRS Vendor Certificate is about to expire or

61625 expired
61628 CBRS Trust anchor is about to expire or expired
ToP master service $IP $EIF $RUPortNumber

61631 unusable
Dup Addr detected-

61632 $DUPLICATEIPV6ADDRESS
61639 IPsec emergency bypass active

IP Traffic Capturing ongoing $UNIT,
61641 $INTERFACE, $MACADDRESS
BTS Local OAM user account $A has been

61642 locked
61643 IPsec tunnel switchover
61644 IKE authentication failure
61645 IKE SA failure
61646 IPSec SA failure
61647 IPSec expert mode activated
61648 LMP connectivity detected
61649 LMP access via port $port
61652 R&D Service Port enabled
61654 IPsec FQDN failure
CCM MAC mismatch MEP $ID, MDL $LEVEL,

61655 MA $MAID, MAC $MACADDRESS
61657 IPsec Tunnel Endpoint is not unique

Ethernet link switchover in link aggregation
61662 group $STATUS
61663 PS tunnel Switchover
XP connection setup failure-Max Number of XP

62000 connections reached
Transport layer connection establishment failure

62001 in XP interface
62002 XP connection setup failure - No response
62003 Transport layer connection lost in XP interface
XP connection setup failure - Incompatible

62004 Message Set
71106 TROUBLESHOOTING DATA RECEIVED

Used in Product Detecting Unit
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS 5G BTS, AirScale BTS FDD,
Flexi BTS FDD AirScale BTS TDD, AirScale SBTS,
Flexi BTS TDD Flexi BTS FDD, Flexi BTS TDD,
Flexi SBTS Flexi SBTS: FCT, FSP
5G BTS
AirScale
AirScale SBTS
BTS FDD
Flexi SBTS
AirScale BTS TDD Flexi SBTS, AirScale SBTS: FCT;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS, AirScale (S)BTS, Flexi
Flexi SBTS
AirScale BTS TDD (S)BTS:: FCT;
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD 5G BTS: ASIx; AirScale (S)BTS,
Flexi SBTS Flexi (S)BTS AirScale: FCT
AirScale SBTS AirScale SBTS: FCT (HW rel.4);

Flexi SBTS Flexi SBTS: FCT (HW rel.3);
5G BTS
AirScale BTS FDD
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale SBTS AirScale SBTS: FCT (HW rel.4);

Flexi SBTS Flexi BTS: FCT (HW rel.3)
5G BTS
AirScale
AirScale SBTS
BTS FDD AirScale SBTS: FCT (HW rel.4);
Flexi SBTS
AirScale BTS TDD Flexi BTS: FCT (HW rel.3)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD 5G BTS, AirScale (S)BTS, Flexi
Flexi SBTS (S)BTS:FCT
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD (S)BTS: FCT
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale (S)BTS, Flexi (S)BTS:
Flexi SBTS
AirScale BTS TDD FCT;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale (S)BTS, Flexi (S)BTS:
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD (S)BTS: FCT;
AirScale SBTS
Flexi BTS FDD
Flexi SBTS (S)BTS: FCT;
5G BTS
AirScale
AirScale SBTS
BTS FDD Airscale SBTS: ABIx; Flexi SBTS:
Flexi SBTS
AirScale BTS TDD FSP, FBB
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale SBTS Airscale SBTS: ABIx; Flexi SBTS:
Flexi SBTS FSP, FBB
AirScale SBTS Airscale SBTS: FSP; Flexi SBTS:

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB
Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

Flexi SBTS FSP, FBB

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

Flexi SBTS Flexi SBTS:FSP, FBB;

Flexi SBTS FSP, FBB
AirScale BTS Airscale SBTS: FSP; Flexi SBTS:

Flexi SBTS FSP or FBB

Flexi SBTS FSP or FBB
AirScale SBTS
Flexi SBTS FCT
5G BTS
AirScale SBTS 5G BTS, AirScale SBTS. Flexi
Flexi SBTS SBTS:FCT
5G BTS
AirScale SBTS 5G BTS, AirScale SBTS. Flexi
Flexi SBTS SBTS:FCT
Flexi Zone Access Point

Flexi Zone Micro
Flexi Zone SFN Antenna FZM, FZAP, SFN ANT

Flexi Zone Micro
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS FCT
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS FCT
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS FCT
5G BTS
AirScale BTS FDD
AirScale
AirScale BTS
BTS TDD
FDD 5G BTS: RAU; AirScale (S)BTS:
AirScale
AirScale SBTS
BTS TDD FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FSP, FBB, ABIx
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD Flexi SBTS: FCT(HW rel.3);
Flexi SBTS
AirScale BTS TDD AirScale SBTS:FCT(HW rel.4)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD Flexi SBTS: FCT(HW rel.3);
Flexi SBTS AirScale SBTS:FCT(HW rel.4);
5G BTS
AirScale BTS FDD
AirScale BTS TDD 5G BTS: FCT, RAU; AirScale
AirScale SBTS (S)BTS: FCT
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD (S)BTS: FCT, FR;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi SBTS (S)BTS: FCT, FR;
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
AirScale BTS
AirScale SBTS FCT
AirScale BTS
AirScale
AirScale BTS
BTS FDD
FDD
AirScale
AirScale SBTS
BTS TDD FCT
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS:FCT(HW rel4)Flexi
Flexi SBTS
AirScale BTS TDD SBTS:FCT(HW rel3);
AirScale SBTS
Flexi BTS FDD
Flexi SBTS (S)BTS: FCT
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS, AirScale (S)BTS:FCT,
Flexi SBTS
AirScale BTS TDD ABIx; Flexi (S)BTS:FCT,FSP,FBB;
AirScale SBTS
Flexi BTS FDD
Flexi SBTS (S)BTS: FCT, ASIx
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS:FCT (HW rel.4);
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT(HW rel.3);
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD 5G BTS:ASIx; AirScale (S)BTS,
Flexi
5G BTSSBTS Flexi (S)BTS: FCT
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS:ASIx; AirScale (S)BTS,
Flexi SBTS
AirScale BTS TDD Flexi (S)BTS: FCT;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS: ASIx; AirScale (S)BTS,
Flexi SBTS
AirScale BTS TDD Flexi (S)BTS: FCT
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD RET
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD MHA, RET, RAE
AirScale SBTS 5G BTS: ASIx; AirScale BTS FDD,
Flexi SBTS Flexi SBTS: FCT;
AirScale BTS FDD
AirScale
5G BTS SBTS
Flexi BTSBTS
AirScale FDDFDD Flexi SBTS:FCT(HW rel.3); AirScale
Flexi SBTS
AirScale BTS TDD SBTS:FCT(HW rel.4);
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS: RAU, ASIx, FCT; AirScale
Flexi SBTS
AirScale BTS TDD (S)BTS, Flexi (S)BTS: FCT
AirScale SBTS
Flexi BTS FDD
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
5G BTS
AirScale SBTS 5G BTS, AirScale SBTS, Flexi
Flexi SBTS SBTS: FCT
5G BTS
5G BTS
5G BTS
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FR
5G BTS
AirScale
AirScale SBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD
AirScale
5G BTS SBTS
Flexi BTSBTS
AirScale FDDFDD AirScale SBTS: FCT (HWrel.4);Flexi
Flexi SBTS
AirScale BTS TDD SBTS: FCT(HWrel.3);
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS: ASIx, RU; AirScale
Flexi SBTS
AirScale BTS TDD (S)BTS, Flexi (S)BTS: FCT
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD (S)BTS: FR;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD (S)BTS: FR
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR, FHS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS: RU; AirScale SBTS: FRx,
Flexi SBTS
AirScale BTS TDD LTX; Flexi SBTS: FRx, LTX;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD AirScale SBTS:FR;Flexi SBTS: FR;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS: RU; AirScale (S)BTS, Flexi
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS, AirScale SBTS, Flexi
Flexi SBTS
AirScale BTS TDD SBTS: FR;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD Radio Module
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi BTS FDD
Flexi SBTS (S)BTS: FR;
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD (S)BTS: FR, Flexi SBTS: FR;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS 5G BTS: FR, RU; AirScale BTS
Flexi BTS FDD FDD, AirScale BTS TDD, AirScale
Flexi BTS TDD SBTS, Flexi BTS FDD, Flexi BTS
Flexi SBTS TDD, Flexi SBTS: FR;
5G BTS: FR, FHS, RU; AirScale
5G
5G BTS
BTS BTS FDD, AirScale BTS TDD,
AirScale
AirScale SBTS
BTS FDD AirScale SBTS, Flexi BTS FDD,
Flexi SBTS
AirScale BTS TDD Flexi BTSFR,
5G BTS: TDD, Flexi
FHS, RU;SBTS: FR;
AirScale
AirScale SBTS BTS FDD, AirScale BTS TDD,
Flexi
5G BTSBTS FDD AirScale SBTS, Flexi BTS FDD,
Flexi BTSBTS
AirScale TDDFDD Flexi BTS TDD, Flexi SBTS: FR,
Flexi SBTS
AirScale BTS TDD FHS;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS BTS FDD, AirScale BTS TDD,
Flexi BTS FDD AirScale SBTS, Flexi BTS FDD,
Flexi BTS TDD Flexi BTS TDD, Flexi SBTS: FR,
Flexi SBTS FHS;
BTS FDD, AirScale BTS TDD,
5G
5G BTS
BTS AirScale SBTS, Flexi BTS FDD,
AirScale
AirScale SBTS
BTS FDD Flexi BTS TDD, Flexi SBTS: FR,
Flexi SBTS
AirScale BTS TDD FHS;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS 5G BTS: FR, RU; AirScale BTS
Flexi SBTS TDD, Flexi SBTS: FR;
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
5G BTS
AirScale
AirScale BTS
BTS TDD
FDD
Flexi BTS TDDTDD
AirScale BTS FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS 5G BTS: RU; AirScale BTS FDD,
Flexi SBTS Flexi SBTS: FR;
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD
Flexi BTS TDD FR
AirScale BTS TDD
AirScale SBTS
Flexi BTS TDD
Flexi SBTS FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale
AirScale BTS
BTS TDD
FDD
Flexi BTS TDDTDD
AirScale BTS FR
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD

Flexi BTS TDD FR

Flexi Zone Micro

Flexi Zone Micro

Flexi Zone Micro
5G BTS: FR, RU; AirScale BTS
5G
5G BTS
BTS FDD, AirScale BTS TDD, AirScale
AirScale
AirScale BTS
BTS TDD
FDD SBTS, Flexi BTS FDD, Flexi BTS
Flexi BTS TDDTDD
AirScale BTS TDD, Flexi SBTS: FR;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
AirScale BTS TDD

Flexi BTS TDD FR
AirScale BTS TDD

Flexi
5G BTSBTS TDD FR
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi
5G BTSSBTS FR
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi
5G BTSSBTS FR
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi
5G BTSSBTS FR
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi
5G BTSSBTS FR
AirScale BTS FDD
AirScale
5G BTS SBTS
Flexi BTSBTS
AirScale FDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
AirScale BTS FDD FR

AirScale BTS FDD FR
5G BTS
AirScale BTS FDD
AirScale SBTS FR
5G BTS
AirScale SBTS 5G BTS, AirScale SBTS:ABIx; Flexi
Flexi SBTS SBTS: FCT, FBB
5G
5G BTS
BTS
AirScale
AirScale SBTS
BTS FDD 5G BTS, AirScale SBTS:ABIx; Flexi
Flexi SBTS
AirScale BTS TDD SBTS: FCT, FBB
AirScale SBTS 5G BTS: AirScale BTS FDD,
Flexi BTSBTS
AirScale TDDFDD Flexi BTS FDD, Flexi BTS TDD,
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT, FBB, ABIA;
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD Flexi SBTS: FCT, FBB; AirScale
Flexi SBTS SBTS:ABIA
AirScale SBTS Flexi SBTS: FCT, FBB; AirScale

Flexi SBTS SBTS:ABIA
AirScale
AirScale SBTS
BTS FDD Flexi SBTS: FCT, FBB; AirScale
Flexi SBTS
AirScale BTS TDD SBTS:ABIA
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD Flexi SBTS: FCT, FBB; AirScale
Flexi SBTS
AirScale SBTS
Flexi BTS FDD Flexi SBTS: FCT (HW rel.3), FTM,
Flexi BTSBTS
AirScale TDDFDD FBB; AirScale SBTS: FCT (HW
Flexi SBTS
AirScale BTS TDD rel.4),ABIA
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD Flexi SBTS: FCT, FBB; AirScale
Flexi SBTS
AirScale SBTS
Flexi BTS FDD Flexi SBTS: FCT (HW rel.3),FBB;
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: FCT (HW
Flexi SBTS
AirScale BTS TDD rel.4),ABIA
AirScale SBTS
Flexi BTS FDD AirScale SBTS: FCT (HW
Flexi BTS TDD rel.4),ABIA; Flexi SBTS: FCT (HW
Flexi SBTS rel.3), FBB
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD AirScale SBTS: FCT (HW
Flexi BTSBTS
AirScale TDDFDD rel.4),ABIA; Flexi SBTS: FCT (HW
Flexi SBTS
AirScale BTS TDD rel.3), FBB
AirScale SBTS
Flexi BTS FDD AirScale SBTS:ABIA, FCT (HW
Flexi BTSBTS
AirScale TDDFDD rel.4); Flexi SBTS:FCT (HW rel.3),
Flexi SBTS
AirScale BTS TDD FBB
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD Flexi SBTS: FCT (HW rel.3),
Flexi SBTS
AirScale BTS TDD AirScale SBTS: FCT (HW rel.4)
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD Flexi SBTS: FCT (HW rel.3),
Flexi SBTS AirScale SBTS: FCT (HW rel.4)
5G BTS
AirScale BTS FDD
AirScale BTS TDD FCT, FSP

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

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












5G BTS
AirScale BTS FDD
AirScale SBTS FR
5G BTS
AirScale BTS FDD
AirScale SBTS FCT
5G BTS
AirScale BTS FDD FCT
5G BTS
AirScale SBTS RU
5G BTS
AirScale SBTS RU
5G BTS
AirScale SBTS RU
5G BTS
AirScale SBTS RU
5G BTS
AirScale SBTS RU
5G BTS
AirScale SBTS RU
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD AirScale BTS FDD/TDD: FCT(HW
Flexi BTS TDD rel.4); Flexi BTS FDD/TDD: FSM;
AirScale BTS FDD
AirScale BTS TDD Flexi BTS FDD/TDD: FCT (HW
Flexi BTS FDD rel.3), FBB; AirScale BTS
Flexi BTS TDD FDD/TDD: FCT (HW rel.4), ABIx
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD AirScale BTS FDD/TDD: FCT , FR;
Flexi BTS TDD Flexi BTS FDD/TDD:FSM,FR;
Flexi BTS FDD

Flexi BTS TDD FR
Flexi BTS FDD

Flexi BTS TDD FSM, FR
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD
Flexi BTS TDD FSM, FR, FCT (HW rel.4)
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD
Flexi BTS TDD FSM, FR, FCT (HW rel.4)
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD FSM, FR, FCT (HW rel.4)
AirScale BTS TDD
Flexi BTS FDD
Flexi BTS TDD AirScale BTS FDD/TDD:FCT, FR;
FlexiBTS Flexi BTS FDD/TDD: FSM, FR;
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD AirScale BTS FDD/TDD: FCT; Flexi
Flexi BTS TDD BTS FDD/TDD: FSM;
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS: FCT; Flexi SBTS:
Flexi SBTS
AirScale BTS FDD FSM
AirScale BTS TDD
Flexi BTS FDD
Flexi BTS TDD AirScale BTS FDD/TDD:FCT; Flexi
FlexiBTS BTS FDD/TDD: FSM;
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD FSM, Antenna Line Device itself,
Flexi BTS TDD FCT (HW rel.4)
AirScale BTS FDD
AirScale
5G BTS BTS TDD
Flexi BTSBTS
AirScale FDDFDD
Flexi BTS TDDTDD
AirScale BTS FSM, FR, FCT (HW rel.4)
Flexi SBTS Flexi SBTS:FCT, FZM
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS : FCT (HW Rel4) ,
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT (HW Rel 3);
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale FCT;
AirScale BTS
BTS TDD
FDD
AirScale
AirScale SBTS
BTS TDD
Flexi BTSSBTS
AirScale FDD
Flexi
Flexi BTS TDD
BTS FDD AirScale SBTS: FCT; Flexi SBTS:
Flexi
Flexi SBTS
BTS TDD FSM;
Flexi SBTS
Flexi
5G BTSZone Access Point
Flexi Zone
AirScale Micro
BTS FDD
Flexi Zone SFN
AirScale BTS TDDAntenna FCT;SC:FZM, FZAP, SFN ANT
AirScale SBTS
Flexi BTS FDD
Flexi
5G BTSSBTS (S)BTS: FCT, ASIx
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT
AirScale BTS FDD
AirScale
5G BTS BTS TDD
Flexi BTSBTS
AirScale FDDFDD AirScale FDD/TDD: FCT; Flexi BTS
Flexi BTS TDDTDD
AirScale BTS FDD/TDD: FCT;
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS:FCT(HW rel.4); Flexi
Flexi SBTS
AirScale BTS TDD SBTS :FCT(HWrel.3)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS:FCT(HW rel.4); Flexi
Flexi SBTS SBTS :FCT(HWrel.3)

Flexi Zone Micro
Flexi Zone SFN Antenna SC: FZM,FZAP,SFN ANT
5G BTS
AirScale
AirScale SBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT (HW rel.3), FCT (HW rel.4)
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
5G BTS
5G BTS
5G BTS
AirScale BTS FDD
AirScale BTS TDD
Flexi SBTS Flexi SBTS: FCT;
5G BTS
AirScale
AirScale SBTS
BTS FDD 5G BTS, AirScale SBTS, Flexi
Flexi SBTS
AirScale BTS TDD SBTS: FCT
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
Flexi
5G BTSBTS FDD AirScale BTS TDD, AirScale SBTS,
Flexi BTSBTS
AirScale TDDFDD Flexi BTS FDD, Flexi BTS TDD,
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT, ASIx;
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD FCT (HW rel.3), FCT (HW rel.4),
Flexi SBTS FBB, ABIx

Flexi Zone Micro
Flexi Zone SFN Antenna SC: FZM,FZC,FZAP,SFN ANT
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT (HW rel.3), FCT (HW rel.4)
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD Flexi SBTS:FCT (HW Rel3)
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT (HW rel.3), FCT (HW rel.4)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS : FCT (HW Rel4) ,
Flexi SBTS Flexi SBTS: FCT (HW Rel 3);
5G
5G BTS
BTS
AirScale
AirScale SBTS
BTS FDD 5G BTS, AirScale SBTS, Flexi
Flexi SBTS
AirScale BTS TDD SBTS: FCT;
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi
5G BTSSBTS FCT
AirScale BTS TDD
AirScale
5G BTS SBTS
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT (HW rel.3)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale BTS TDD

Flexi BTS TDD FCT (HW rel.3), FCT (HW rel.4)
AirScale BTS TDD

AirScale SBTS
Flexi BTS FDD
Flexi SBTS FBBC

Flexi Zone Micro

Flexi Zone Micro
Flexi Zone Micro

Flexi Zone Micro

Flexi Zone Micro

Flexi Zone Micro

Flexi Zone Micro

Flexi Zone Micro
Flexi Zone Micro
Flexi Zone SFN Antenna FZM, FZC, FZAP, SFN ANT

Flexi Zone
AirScale Micro
BTS FDD
Flexi Zone SFN
AirScale BTS TDDAntenna FZM, FZAP, SFN ANT
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS:- FCT (HW
Flexi SBTS rel.4)Flexi SBTS:- FCT (HW rel.3);

Flexi Zone Micro FZM, FZAP
5G BTS
AirScale
AirScale SBTS
BTS FDD AirScale SBTS: FCT (HW rel.4);
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT (HW rel.3);
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi
5G BTSSBTS FCT
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FR
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FR
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD AirScale SBTS : FCT (HW Rel4) ,
AirScale BTS TDD

5G BTS
AirScale
AirScale BTS
BTS TDD
FDD
Flexi BTS TDDTDD
AirScale BTS FR
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT

Flexi Zone Controller FZC, FZAP

Flexi Zone Micro FZM, FZC, FZAP
Flexi Zone
AirScale Access
BTS FDD Point
AirScale BTS TDD FZC, FZAP
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT (HW Rel 3)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD Flexi SBTS FCT (HW rel.3);
5G BTS
AirScale BTS FDD
Flexi Zone
AirScale Controller
BTS TDD FZC
AirScale SBTS
Flexi BTS FDD
Flexi SBTS (S)BTS: FCT (HW rel.4);
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
AirScale
AirScale SBTS
BTS FDD
Flexi SBTS
AirScale BTS TDD AISG MHA
AirScale SBTS
Flexi BTS FDD
Flexi
5G BTSSBTS Flexi SBTS: FCT (HW Rel 3);
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD
Flexi BTS TDD FCT

Flexi Zone Micro
AirScale BTS TDD

5G BTS
AirScale
AirScale BTS
BTS TDD
FDD
Flexi BTS TDDTDD
AirScale BTS FCT (HW rel.3), FCT (HW rel.4)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
5G BTS
AirScale BTS FDD
Flexi Zone
AirScale Controller
BTS TDD FZC
AirScale SBTS 5G BTS: FCT, RF; AirScale BTS
Flexi SBTS TDD, Flexi SBTS: FCT;

Flexi Zone Micro
Flexi Zone Micro
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD AirScale BTS FDD/TDD: FCT, Flexi
Flexi BTS TDD BTS FDD/TDD: FCT;
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS TDD BTS FDD/TDD: FCT;
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS TDD BTS FDD/TDD: FCT; SC:FZM
AirScale BTS FDD
AirScale BTS TDD
Flexi BTSBTS
AirScale FDDFDD AirScale BTS FDD/TDD: FCT, Flexi
Flexi BTS TDDTDD
AirScale BTS BTS FDD/TDD: FCT;
AirScale SBTS
Flexi BTS FDD
Flexi Zone Micro FZM

Flexi Zone Micro
Flexi
5G BTSZone SFN Antenna SC:FZM, FZAP, SFN ANT
AirScale BTS TDD
AirScale SBTS
Flexi BTS TDD
Flexi SBTS FCT
5G BTS
AirScale SBTS 5G BTS: ASIx; AirScale SBTS, Flexi
Flexi SBTS SBTS: FCT;
5G BTS
AirScale SBTS
Flexi SBTS FCT
AirScale SBTS
Flexi SBTS Flexi SBTS:FCT(HWrel.3)
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD
AirScale
5G BTS SBTS
Flexi BTSBTS
AirScale FDDFDD AirScale SBTS: FCT (HW rel.4);
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS: FCT (HW rel.4);
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT (HW rel.3)

Flexi Zone Micro FZM, FZC, FZAP
Flexi Zone Micro FZM
Flexi BTS TDD FCT(HW rel.3), FCT(HW rel.4)
AirScale SBTS Airscale SBTS: ASIx, FlexiSBTS:

Flexi SBTS FCT
AirScale BTS FDD

Flexi Zone
AirScale Controller
BTS TDD FZC
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT (HW rel.3), FCT (HW rel. 4)
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FR
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FR
Flexi Zone Controller FZC

5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale
5G BTS SBTS FCT
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi SBTS FCT
AirScale SBTS
5G BTS
Flexi Zone
AirScale Access
BTS FDD Point
Flexi Zone Micro
AirScale BTS TDD FZM, FZAP
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD 5G BTS, AirScale SBTS: FCT (HW
Flexi SBTS
AirScale BTS TDD rel.4); Flexi SBTS: FCT (HW rel.3);
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi
5G BTSSBTS FCT
AirScale BTS FDD
AirScale SBTS Flexi SBTS: FCT (HW rel.3), FBB;
Flexi BTS FDD AirScale SBTS: FCT (HW rel.4),
Flexi SBTS ABIx

Flexi Zone Micro



Flexi Zone Micro
AirScale BTS FDD

AirScale
5G BTS BTS TDD FCT (HW rel.4)
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS FCT (primary or secondary unit in
Flexi SBTS dual core configuration)





Flexi Zone SFN Antenna SFN ANT

Flexi Zone Micro FZM, FZC
5G BTS
AirScale BTS
AirScale BTS FDD ASIx (AirScale primary core in dual
AirScale BTS TDD core configuration)
Flexi BTS FDD

Flexi BTS TDD
Flexi SBTS Flexi SBTS: FCT(HW Rel3)
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS FCT
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD AirScale SBTS : FCT (HW Rel4) ,
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT (HW rel.3), FCT (HW rel. 4)
5G BTS
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT
ASIx (primary unit in dual core

AirScale BTS FDD configuration)
AirScale BTS FDD FCT (HW rel.4)
5G BTS
AirScale BTS FDD
AirScale
AirScale BTS FDD
BTS TDD FCT(HW rel.4)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
5G BTS ASIx (primary unit in dual core

AirScale BTS configuration)
AirScale
AirScale SBTS
BTS FDD Flexi SBTS: FCT (HW rel.3),
Flexi SBTS
AirScale BTS TDD FCT(HW rel 4)
AirScale SBTS
Flexi BTS FDD
AirScale
AirScale SBTS
BTS FDD Flexi SBTS: FCT (HW rel.3),
Flexi SBTS
AirScale BTS TDD AirScale SBTS: FCT (HW rel.4)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS Flexi SBTS:FCT(HW rel.3)
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD AirScale SBTS: FCT (HW rel.4);
5G BTS
AirScale BTS FDD
Flexi Zone
AirScale Micro
BTS TDD FZM
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale SBTS
Flexi SBTS FCT (HW rel.3), FCT (HW rel. 4)
AirScale SBTS
AirScale SBTS

AirScale BTS FDD
AirScale
5G BTS SBTS
Flexi BTSBTS
AirScale FDDFDD AirScale SBTS:FCT(HWrel.4);Flexi
Flexi SBTS
AirScale BTS TDD SBTS:FCT(HWrel.3);
AirScale SBTS
Flexi BTS FDD
AirScale SBTS
AirScale BTS FDD
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi SBTS
AirScale BTS FDD FR
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD FR
Flexi Zone Controller SC:FZC
AirScale BTS FDD

AirScale
5G BTS BTS TDD FCT (HW rel4)
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD
Flexi BTS TDD FCT
5G BTS
AirScale SBTS FCT
AirScale BTS FDD

AirScale SBTS FCT (HW rel.4)
AirScale BTS
Flexi BTS FDD
Flexi BTS TDD FCT
5G BTS
AirScale SBTS ASIx
5G BTS
AirScale BTS FDD
AirScale
AirScale BTS FDD
BTS TDD FCT (HW rel.4)
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale BTS FDD
Flexi BTS FDD rel.3); AirScale BTS FDD/TDD: FCT
Flexi BTS TDD (HW rel.4)


5G BTS
AirScale SBTS Flexi SBTS: FCT, FBB; 5G BTS,
Flexi SBTS AirScale SBTS: FCT
AirScale BTS FDD AirScale BTS FDD/TDD: FCT (HW

AirScale BTS TDD rel.4)
5G BTS
AirScale BTS FDD
5G BTS BTS
AirScale
AirScale
AirScale BTS
BTS FDD
FDD
AirScale
AirScale BTS
BTS TDD
TDD FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
5G BTS
AirScale BTS FDD AirScale BTS: FCT (HW rel.4);
5G BTS
AirScale BTS FDD
AirScale SBTS
Flexi SBTS FCT
AirScale SBTS
Flexi SBTS FCT
AirScale SBTS
Flexi SBTS FCT
AirScale SBTS
Flexi SBTS FCT
5G BTS
AirScale SBTS FCT
AirScale SBTS AirScale SBTS: FCT (HW rel.4)
5G BTS
AirScale SBTS ASIx

Flexi Zone Micro:FZM; AirScale

AirScale BTS TDD BTS TDD: FCT (HW rel.4)
AirScale BTS FCT (HW rel.4)
5G BTS
AirScale SBTS FCT
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
5G BTSBTS FDD Flexi BTS FDD/TDD: FCT (HW
Flexi BTSBTS
AirScale TDDFDD rel.3); AirScale BTS FDD/TDD: FCT
Flexi SBTS
AirScale BTS TDD (HW rel.4)
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD Flexi BTS FDD/TDD: FCT (HW
Flexi BTS TDD rel.3); AirScale BTS FDD/TDD: FCT
Flexi SBTS (HW rel.4)
5G BTS
AirScale SBTS
Flexi SBTS FSP, FSM
AirScale BTS FDD

AirScale BTS TDD
AirScale SBTS FCT
AirScale BTS FSP
5G BTS
AirScale SBTS RAU, ASIx
AirScale SBTS
Flexi SBTS FCT
AirScale SBTS AirScale SBTS:FCT(HW rel4); Flexi

Flexi SBTS SBTS:FCT(HW rel3)
AirScale SBTS AirScale SBTS:FCT(HW rel4); Flexi

Flexi SBTS SBTS:FCT(HW rel3)
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT

AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT
AirScale SBTS FCT

5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS BTS OAM
5G BTS
AirScale BTS FDD
AirScale BTS TDD
5G BTS
AirScale BTS FDD
AirScale
AirScale BTS TDD
BTS TDD FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale SBTS FCT
AirScale BTS FDD

AirScale BTS TDD
AirScale BTS ASIx
5G BTS BTS FDD

AirScale
AirScale
AirScale SBTS
BTS TDD FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT;
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS ASIx
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT
Flexi Zone Micro SC:FZM
5G BTS
AirScale SBTS ASIx
5G BTS BTS FDD

AirScale
AirScale
AirScale SBTS
BTS TDD RAU, ASIx
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale SBTS FCT
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT
AirScale BTS FDD

AirScale SBTS
Flexi BTS FDD FCT
5G BTS
AirScale SBTS FCT
5G BTS
AirScale SBTS FCT, ASxx
5G BTS
5G BTS
AirScale SBTS O-DU
5G BTS
AirScale SBTS O-DU
5G BTS
5G BTS BTS FDD

AirScale
AirScale
5G BTS BTS TDD
AirScale
AirScale SBTS
BTS
Flexi BTSBTS
AirScale FDDFDD
Flexi BTS TDDTDD
AirScale BTS
Flexi SBTS
AirScale SBTS FCT
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS
SBTS RU
5G BTS
AirScale BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDD
Flexi SBTS
AirScale BTS FDD
SBTS
AirScale BTS TDD RU
AirScale SBTS
Flexi BTSBTS
AirScale FDD
Flexi BTS TDDFDD
AirScale BTS
Flexi SBTS
AirScale BTS TDD FCT OAM-TAS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT-OAM
5G BTS
AirScale SBTS FCT
5G BTS
AirScale BTS FCT
5G BTS
AirScale SBTS FCT
5G BTS
AirScale SBTS FCT
5G BTS
AirScale SBTS FCT
5G BTS
AirScale BTS FDD
5G BTS BTS TDD
AirScale O-DU
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
5G BTS
AirScale SBTS FCT
AirScale SBTS AirScale SBTS : FCT (HW Rel4) ,

5G BTS
AirScale SBTS 5G BTS: ASIx; AirScale SBTS: FCT
AirScale SBTS FCT
5G BTS
AirScale SBTS FCT
5G BTS
AirScale SBTS FCT
5G BTS
5G BTS BTS FDD
AirScale
AirScale
AirScale SBTS
BTS TDD FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD 5G BTS: ASIx, RU; AirScale
Flexi SBTS (S)BTS, Flexi (S)BTS: FCT
5G BTS
AirScale BTS FDD
AirScale
AirScale BTS
BTS TDD
FDD
AirScale
AirScale SBTS
BTS TDD 5G BTS, AirScale SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD Flexi SBTS: FCT (HW rel.3);
Flexi SBTS
AirScale BTS TDD AirScale SBTS: FCT (HW rel.4);
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS:- FCT (HW
Flexi SBTS
AirScale BTS TDD rel.4)Flexi SBTS:- FCT (HW rel.3);
AirScale SBTS
Flexi BTS FDD

Flexi Zone Micro FZM,FZC,FZAP
AirScale BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi SBTS FCT
AirScale SBTS FCT

AirScale BTS TDD
AirScale SBTS
Flexi BTS TDD Flexi SBTS: FSP, FBB; AirScale
Flexi SBTS SBTS: ABIx;
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: ABIA; Flexi SBTS:
Flexi SBTS
AirScale BTS TDD FSP;
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT (HW rel.3), FCT (HW rel.4);
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS: ABIx; Flexi SBTS:
Flexi SBTS FSP, FBB;
AirScale BTS TDD
AirScale SBTS
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: ABIx;Flexi SBTS:
Flexi SBTS
AirScale BTS TDD FSP, FBB;
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: ABIA; Flexi SBTS:
Flexi SBTS
AirScale BTS TDD FSP;
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS: ABIA; Flexi SBTS:
Flexi SBTS FSP;
AirScale BTS TDD Flexi BTS TDD: FSP, FBB; AirScale

Flexi BTS TDD BTS TDD: ABIx;
AirScale BTS FDD AirScale BTS FDD: FSP
AirScale BTS TDD Flexi BTS TDD: FSP, FBB; AirScale

AirScale BTS FDD Flexi BTS TDD: FSP, FBB; AirScale

Flexi BTS FDD/TDD: FCT (HW

rel.3); AirScale BTS FDD/TDD:FCT
AirScale BTS FDD (HW rel.4); SC: FZM,FZC
AirScale BTS FDD AirScale BTS FDD
AirScale BTS FDD AirScale BTS FDD
AirScale
AirScale BTS
BTS FDD
FDD
Flexi BTS FDDTDD
AirScale BTS FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: FCT (HW rel.4);
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: FCT (HW Rel4);
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS:- FCT (HW
Flexi SBTS
AirScale BTS TDD rel.4)Flexi SBTS:- FCT (HW rel.3);
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD
AirScale BTS TDD AirScale BTS FDD/TDD: FCT (HW
Flexi BTSBTS
AirScale FDDFDD rel.4); Flexi BTS FDD/TDD: FCT
Flexi BTS TDDTDD
AirScale BTS (HW rel.3);
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT (HW rel.3), FCT (HW rel. 4);
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS, Flexi SBTS:
Flexi SBTS
AirScale BTS TDD LNADJ;
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT (HW rel.3), FCT (HW rel.4);
AirScale SBTS
Flexi BTSBTS
AirScale FDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD Flexi SBTS : FCT (HW rel.3);
AirScale SBTS
Flexi BTS FDD
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD

AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD AirScale BTS FDD/TDD, Flexi BTS
Flexi BTS TDD FDD/TDD:FCT;
AirScale BTS FDD
AirScale SBTS
Flexi BTSBTS
AirScale FDDFDD
Flexi SBTS
AirScale BTS TDD FCT (HW rel.3), FCT (HW rel. 4)
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD Flexi SBTS: FCT (HW rel.3);
Flexi SBTS AirScale SBTS: FCT (HW rel.4);

AirScale BTS FDD
Flexi BTSBTS
AirScale FDDFDD rel.3); AirScale BTS FDD/TDD: FCT
Flexi BTS TDDTDD
AirScale BTS (HW rel.4);
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale BTS TDD Flexi SBTS: FCT (HW rel.3)
AirScale SBTS
Flexi BTS FDD
AirScale
AirScale BTS
BTS FDD
FDD AirScale BTS FDD: ABIA; Flexi BTS
Flexi BTS FDDTDD
AirScale BTS FDD: FSP;
AirScale SBTS
Flexi BTS FDD AirScale BTS FDD/TDD: FCT (HW
Flexi BTS TDD rel.4); Flexi BTS FDD/TDD: FCT
Flexi SBTS (HW rel.3);
5G BTS 5G BTS: RAU, ASIx; AirScale BTS

AirScale BTS FDD FDD: FCT;
AirScale BTS FDD AirScale BTS FDD:FCT (HW
AirScale BTS TDD rel.4);Flexi BTS FDD:AirScale BTS
Flexi BTS FDD TDD:FCT(HW rel.4);Flexi BTS
Flexi BTS TDD TDD:FCT (HW rel.3);
AirScale BTS
FlexiBTS FCT(HW rel.3) FCT(HW rel.4)
AirScale BTS FDD AirScale BTS FDD: FCT (HW rel.4);

Flexi BTS FDD Flexi BTS FDD: FCT (HW rel.3);
AirScale
AirScale BTS
BTS FDD
AirScale
AirScale SBTS
BTS TDD
FlexiBTS
AirScale SBTS FCT(HW rel.3); FCT(HW rel.4);
Cloud BTS AirScale BTS FDD/TDD:FCT(HW
Flexi
5G BTSBTS FDD rel.4);Flexi BTS FDD/TDD:FSP (HW
Flexi BTSBTS
AirScale TDDFDD rel.3);AirScale SBTS:FCT(HW
Flexi SBTS
AirScale BTS TDD rel.4),Flexi SBTS:FSP(HW rel.3)
AirScale SBTS
Flexi BTS FDD
5G BTS
AirScale
AirScale BTS
BTS FDD
FDD
Flexi BTS FDDTDD
AirScale BTS FCT
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
AirScale
AirScale SBTS
BTS FDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS: ABIx; Flexi SBTS:
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: ABIx; Flexi SBTS:
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: ABIx; Flexi SBTS:
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: ABIx, Flexi SBTS:
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS: ABIx, Flexi SBTS:
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD AirScale BTS FDD/TDD: ABIx; Flexi
Flexi BTS TDD BTS FDD/TDD: FSP, FBB;

Flexi Zone Micro
Flexi Zone SFN Antenna SC: FZM,FZAP,SFN ANT

Flexi Zone Micro
Flexi Zone Micro
Flexi Zone SFN Antenna FZM, FZC, FZAP, SFN ANT


AirScale BTS AirScale BTS: FCT (HW rel.4);


Flexi Zone Micro

AirScale BTS TDD AirScale BTS TDD: FCT (HW rel.4);



Flexi Zone
AirScale Access
BTS FDD Point
Flexi Zone Micro
AirScale BTS TDD FZM, FZAP
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: FCT (HW rel.4),
Flexi SBTS
AirScale BTS TDD FCT (HW rel. 3)
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD AirScale SBTS: FCT (HW rel.4),
AirScale BTS FDD
AirScale BTS TDD
Flexi BTS FDD AirScale BTS FDD/TDD: ABIx, Flexi
Flexi BTS TDD BTS FDD/TDD: FSP, FBB
AirScale BTS FDD

AirScale BTS FDD
AirScale BTS TDD AirScale BTS FDD, AirScale BTS
Flexi BTS FDD TDD: - ASIx Flexi BTS FDD, Flexi
Flexi BTS TDD BTS TDD: - FSMF
AirScale BTS FDD
AirScale BTS TDD AirScale BTS FDD/TDD:
Flexi BTS FDD FCT(HWrel.4); Flexi BTS
Flexi BTS TDD FDD/TDD:FCT(HW rel.3);
AirScale BTS FDD
AirScale BTS FDD
5G BTS
AirScale BTS FDD
AirScale BTS FDD

AirScale BTS TDD
AirScale SBTS FCT
5G BTS
AirScale SBTS 5G BTS, AirScale SBTS: FCT, FSP;
Flexi SBTS Flexi SBTS: FCT, FSP, FTIF
5G BTS
AirScale SBTS 5G BTS, AirScale SBTS: FCT, FSP;
Flexi SBTS Flexi SBTS: FCT, FSP, FTIF
AirScale BTS FDD

5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS SMOD
AirScale BTS FDD

AirScale BTS FDD

AirScale BTS FDD

5G BTS
AirScale SBTS FCT
5G BTS
AirScale SBTS FCT
5G BTS
AirScale SBTS RAC
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU, Airscale SBTS: ASIB
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAC
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS FCT
5G BTS
5G BTS
5G BTS
5G BTS
5G BTS
5G BTS
5G BTS
5G BTS
5G BTS
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS AirScale BTS FDD
5G BTS
5G BTS
5G BTS
5G BTS
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
AirScale SBTS RAU
5G BTS
5G BTS BTS FDD
AirScale
AirScale
AirScale SBTS
BTS TDD RAU
AirScale
5G BTS SBTS
Flexi BTSBTS
AirScale FDD
Flexi BTS TDDFDD
AirScale BTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTS TDD
Flexi SBTS FCT
5G BTS
AirScale BTS FDD
AirScale
AirScale BTS
BTS TDD
FDD
AirScale
AirScale SBTS
BTS TDD
Flexi BTSSBTS
AirScale FDD
Flexi
Flexi BTS
BTS TDD
FDD
Flexi
Flexi SBTS
BTS TDD FCT
Flexi SBTS
Flexi
5G BTSZone Micro BTS
Flexi Zone
AirScale Micro
BTS FDD FDD
Flexi Zone Micro
AirScale BTS TDD TDD FCT
AirScale SBTS
Flexi BTS FDD Flexi SBTS: FCT (HW rel.3);
Flexi BTS TDD AirScale SBTS: FCT (HW rel.4
Flexi SBTS onwards)
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD Flexi SBTS: FCT (HW rel.3);
Flexi BTSBTS
AirScale TDDFDD AirScale SBTS: FCT (HW rel.4
Flexi SBTS
AirScale BTS TDD onwards)
AirScale SBTS
Flexi SBTS onwards)
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi SBTS onwards)
Flexi BTS FDD
Flexi BTS TDD
Flexi BTS FDD

Flexi BTS TDD
Flexi BTS FDD

Flexi BTS TDD
Flexi BTS FDD

Flexi BTS TDD
Flexi BTS FDD

Flexi BTS TDD
Flexi BTS FDD

Flexi BTS TDD
Flexi BTS FDD

Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi SBTS onwards)
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
AirScale BTS FDD AirScale BTS FDD/TDD: ASIA,

AirScale BTS TDD ASIAA
5G BTS
AirScale
AirScale BTS
BTS FDD
FDD AirScale BTS FDD/TDD: ASIA,
AirScale
AirScale BTS
BTS TDD
TDD ASIAA
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
AirScale TDDFDD
Flexi SBTS
AirScale BTS TDD FCT, RU
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi SBTS onwards)
5G BTS
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi SBTS onwards)
5G BTS
AirScale
AirScale BTS
BTS FDD
FDD
AirScale
AirScale BTS
BTS TDD
TDD AirScale SBTS: FCT (HW rel.4); FR
AirScale SBTS
Flexi
5G BTSBTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTS FDD
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi SBTS onwards)
AirScale BTS FDD
AirScale BTS TDD
AirScale SBTS
Flexi BTSBTS
Flexi SBTS
AirScale SBTS
Flexi SBTS onwards)
5G BTS AirScale SBTS: FCT (HW rel.4

AirScale BTS FDD onwards)





Flexi Zone Micro None
synchronization is corrected and there is,
again, a difference of 0.2 ppm or more.
The alarm is cancelled whenever the
difference becomes less than 0.2 ppm.
2. The reference frequency fluctuates

continuously
5G BTS: because of a significant
amount of jitter
- A module required or wander in the
in commissioned 5G
transmission network.
BTS configuration has not beenThe alarmdetected
is
continuously
or connectionactivated
to a moduleor cancelled
belonging to
(however, the alarming
the 5G BTS configuration state
hasmight
been lost.
predominate).
-Meaning
In case of eCPRI There is always
RU, a failuresome
mightjitter
Source or wander in the transmission network;
have occurred in IPSec tunnel, if the link
the limits DU
between are and
defined
RU isin not
ITU-Testablished
G.823/824/825.
for a defined time after retrying.
3. If the BTS-integrated
AirScale BTS FDD, AirScale transport
BTS partTDD,
receives the synchronization
AirScale SBTS, Flexi BTS FDD, information
Flexi
through
BTS TDD, theFlexi
2.048 MHz synchronization
SBTS:
SMOD input
- The connection to aasource),
The (external
temperature clock
of unit
module the
thatalarm
exceeds the
BBMOD situation
belongs to the BTS configuration hasof
threshold might
value. be caused by a fault
that
beensignal.
lost. In that case, the alarm
behavior
- In case of notifications
SNMP radios, listedthere
with is thea Iub
AirScale SBTS, Flexi SBTS: signal (see above) are also valid.
- SMOD problem
A software with the optical
update in theinterface
module or orsub-
an
- BBMOD internal
module fault,
has which results in a radio
failed.
4. There is an equipment fault in the BTS.
reset.
5G BTS, Flexi BTS FDD, Flexi BTS TDD,
- BBMOD The equipment
- In case of FHSfaultandis,
AFAAhowever,
CPRI,not the
IPsec
AirScale
- FHS BTS TDD, AirScale BTS FDD, Flexi most common reason. Normally,
failure might have occurred, if security the
SBTS,
- LNA AirScale SBTS: reason is in the
was enabled forIub
theor reference
control and signal
-- SMOD
PDU behavior (see the descriptions
management plane on this interface above).
- RAEU - In case of eCPRI RU, a failure might
- RETU have occurred
A failure in IPSec
is detected when tunnel, if the link
the eNodeB
- RMOD between DU and RU is not
O&M system presents available FSPs to established
- SMOD for a defined
C-plane time in
software after retrying.
order to map FSPs to
a cell. The FSPs related to the faulty
operation cannot be taken into use. The
Flexi SBTS, AirScale SBTS: reason for the failure might be an internal
- WBTS problem in the eNodeB O&M system.
The initialization of control plane part for

- WBTS WCDMA RAT has failed.
- BBMOD
- RMOD The SMOD. BBMOD or RMOD
- SMOD synchronization
A common NBAP has failed.Application
(NodeB
Part - interface between NodeB and
RNC) link failure has occurred that is
Flexi BTS TDD, Flexi BTS FDD, Flexi SBTS: possibly caused by a transmission
- SMOD
WBTS 5G BTS:problem.
network
- BBMOD A new unit with an incompatible SW
- RMOD might have been inserted into the 5G
A dedicated
BTS. AutomaticNBAPSW(NodeB
update Application
is triggered.
5G BTS, AirScale BTS TDD, AirScale BTS Part - interface between NodeB and
-FDD,
WBTSAirScale SBTS: RNC) linkBTS
AirScale failure hasAirScale
FDD, occurred.
BTS TDD,
- SMOD AirScale SBTS, Flexi BTS FDD, Flexi
- BBMOD BTS TDD, Flexi SBTS:
- RMOD An incompatible software has been
- FHS detected.
The BTS cannot obtain a file from the file
server (there is an error in either FTP
open or FTP get): the file server is down,
There
the fileisisan attemptortothe
missing, download an
path is incorrect.
SMOD unsupported SW version.
A possible error in the DCN and Iub, or a
5G BTS, AirScale BTS FDD, AirScale BTS user administration error (an invalid
TDD, AirScale SBTS, Flexi BTS FDD, Flexi username or password, or the user does
BTS TDD, Flexi SBTS: not have access rights to the files) has
- SMOD occurred.
SMOD
BBMOD
5G BTS, AirScale BTS FDD, AirScale BTS The
The download
SW updateisto
corrupted, or the
the BTS has failed.
RMOD
TDD, AirScale SBTS, Flexi BTS FDD, Flexi software is incompatible.
The error might be caused by a unit reset
BTS TDD, Flexi SBTS: during the SW update, a hardware
- BBMOD problem in the unit, cabinet incompatibility
-5GRMOD
BTS, AirScale BTS FDD, AirScale BTS problems with the
The SW update to download, or a
the BTS has failed.
-TDD,
SMODAirScale SBTS, Flexi BTS FDD, Flexi corrupted flash file system.
The error might be caused by a unit reset
BTS TDD, Flexi SBTS: during the SW update, a hardware
- BBMOD problem in the unit, cabinet incompatibility
- RMOD problems with the download, or a
- SMOD corrupted
There is a flash filethe
fault in system.
BTS main power
supply. The BTS has received a battery
backup
5G BTS,alarm, andBTS
AirScale the BTS
FDD,cells
AirScale
intelligent
BTS TDD,
AirScale shutdown
BTSAirScale procedure
TDD, SBTS,
AirScale has
Flexi
BTS BTS
FDD,
SMOD started.
FDD,
AirScaleFlexi BTS Flexi
SBTS, TDD,BTSFlexiFDD,
SBTS: Flexi
- LNCEL The
BTS fault
TDD,informs the operator that the
Flexi SBTS:
- NRCELL BTS is trying to correct
The fault indicates that the a fault situation
user has by
- WNCEL performing a recovery reset on
blocked the cell using the BTS Element the FSP,
- BTS (GSM cell) GNSS,
Manager. baseband card, BBPOOL, SoC,
RAT, Radio, BTS site or the BTS
AirScale BTS TDD, AirScale BTS FDD, The BTS iscore.
secondary blocked with of
In case thea BTS
RadioElement
AirScale SBTS, Flexi BTS FDD, Flexi BTS Manager. The purpose
Module reset in RF chaining is to avoid fault
TDD, Flexi
5G BTS, SBTS: BTS FDD, AirScale BTS
AirScale indications that might be raised during
configuration, the BTS also resets all RF a
-TDD,
MRBTS
AirScale SBTS, Flexi BTS FDD, Flexi BTS maintenance task.
modules that are further in the chain.
BTS TDD, Flexi SBTS:
- SMOD # in fault name indicates what recovery
- BBMOD level is performed, for example "BTS site
-5G
RMOD
BTS, AirScale BTS FDD, AirScale BTS autonomous reset as recovery action".
TDD, AirScale SBTS, Flexi BTS FDD, Flexi
BTS TDD, Flexi SBTS: The unit or module has been tested
- SMOD during the BTS power-on self test
- BBMOD (POST), and a failure has been detected.
NBAP: PRIVATE MESSAGE
(Configuration Data) message from RNC
with valid parameters for a cell was not
-5G WBTS
BTS, AirScale BTS FDD, AirScale BTS received by BTS.
BTS TDD, Flexi SBTS: A module cannot be identified by its
- SMOD product code or by
An unsupported unititshas
physical device in
been detected
-- BBMOD
SMOD address (object ID).
the System Module. This typically
- BBMOD happens when a new unit version is
- LNA installed while an older system module
- RETU SW, which does not support the new unit
- RAEU version, is in use.
Unit RNW (Radio Network) configuration
or reconfiguration failure.
The RF module carrier power
- RMOD measurement has failed.
The fault is detected for DSP or
CARRIER when it does not accept
configuration, configuration failure, or
Airscale SBTS: FSP does not respond to a configuration
Flexi SBTS: FSP, FBB, RX1-n, TX1-n request.
The BTS does not receive a response

- WBTS from the RNC to a cell block request.
Cell enabling (the setup of CPICH and
BCH) has failed.
The reason might be a hardware or a bus
- WCEL problem, or a lack of DSP.
There is not enough BTS baseband

- WCEL capacity to set up the cell.
The radio output power has dropped.

At leastisone
There Local
a fault Celldownlink
in the Group (LCG) in
- RMOD the BTS doespath.
transmission not have enough resources
for
133: the HSUPA minimum capacity
commissioned with the parameter
EFaultId_RxAntennaSignalLevelTooLow
"Number
Al of HSUPA resource steps
The power
reserved forvalues
HSUPA in the cell configuration
- WCEL The RX
data sentsignal
by level
the RNC isusers".
lessout
are than
of -range.
If the LCG
112dBm . has two HSUPA schedulers,
133:
then the sum of the HSUPA Resource
EFaultId_RxAntennaSignalLevelTooLow
Steps that is statically allocated in both
134:
Al
System Modules is compared with the
EFaultId_RxAntennaSignalLevelDifferenc
- WBTS The RX signal level
commissioned is less than -
amount.
eTooHighAl
112dBm .
The difference between the maximum
and
134:minimum power levels of all RX
- ANTL antennas in the same cell and sector
EFaultId_RxAntennaSignalLevelDifferenc
- PHYANT exceeds
eTooHighAl defined limit for a cell.
the
The difference between the maximum
and minimum power levels of all RX
- ANTL antennas in the same cell and sector
- PHYANT exceeds the defined limit for a cell.
1. If there are no DSP resources for
Parallel Interference Cancellation (PIC)
configuration, the PIC configuration is
- SMOD Unsuccessful
rejected. DSP configuration to the
- BBMOD correct mode.
2. PIC not supported when 2 or more
WCDMA radios are connected to 2 or
more ABIAs used by WCDMA in the
- WCEL same core.
Parallel Interference Cancellation (PIC)
configuration cannot be allocated to a
DSP resource because the DSP is in use
- WCEL with some users.
having the same UTRA Absolute Radio
Frequency Channel Number (UARFCN)
are not mapped to the same Parallel
Interference Cancellation (PIC) pool, or
there is another cell in the same LCG with
the same UARFCN outside the PIC pool.
2.The PIC pool configuration (new or

updated) is rejected if either all LCELWs
- SMOD One
in theparticular
same LCG DSP rejects
having a Dedicated
same UARFCN
- BBMOD Channel (DCH) setup repetitively.
do not belong to the same PIC pool, or an
LCELW that does not belong to any PIC
pool has UARFCN that is already
assigned to any PIC pool from the same
- WCEL LCS of an LCELW.
There is not enough Common Control
Channel Processing Set (CCCH
During HSDPA setup:
Processing
The PhysicalSet) licenses
Shared commissioned
Channel
- WBTS to the BTS.
Reconfiguration
HSDPA setup is (PSCR)rejectedrequest
becausefor
setting up new HSPA resources
Physical Shared Channel Reconfiguration is
rejected because
message containsitaisTcell
made on already
value which
- SMOD existing
belongs resources (allocated
to a Tcell group otherinthan
DSPthe
SW
- BBMOD internal databases).
existing cells in MAC-hs scheduler. Tcell
is a parameter that represents frame
There
timing are notofenough
offset a cell. Itbaseband
can be used for
resources
grouping (or they
schedulers aretotemporarily
cells if minimum
One of the
unavailable Common
for HS-RACHTransport Channels
(HighHSDPA
Speed
- WCEL baseband
(PCH, FACH,allocation
RACH) orisshared
released by RNC.
Cell_FACH UL) service) in
scheduler for baseband efficiency LCG (Local
Cell Group)are
scheduler forused.
the commissioned "Min
number of HSUPA resource steps for HS-
RACH
During users
runtime activation:
- WBTS (minNumOfHsRachResourcesStepsRes).
Carrier aggregation functionality for local
cell group is not available because cells
from two different
The carrier Tcell Groups
aggregation are
group ID change
- WBTS already set up in MAC-hs schedulers.
is not acceptable. The carrier aggregation
group ID is changed from a non-zero
value to commissioned
NBIC is another non-zerofor value.
an LCG,Only
but
acceptable
Telecom was not able to, or did notto zero
changes are non-zero
- WBTS value or resources
allocate zero to non-zero value.
for it due to:
1. invalid commissioning parameters for
the LCG relevant to NBIC.
2. resources (DLI pool, DSP device) are
- WBTS not available.
Telecom SW detects that
DSS is commissioned connection
for at least one
types
LCR in an LCG, but Telecom for
of TX carrier resources wasone
notLCR
have both of CPRI and OBSAI. This
able to, or did not allocate resources for it
LCR configuration
due to: is not supported.
1. Resource for prerequisite feature NBIC
is not allocated for the LCG.
2. Resources (advanced link indices,
LCG baseband capacity)
Internal failure are not
detected available.
within the SBTS
system while attempting to communicate
information needed for spectrum sharing
functionality, when WCDMA-LTE dynamic
WNCEL spectrum sharing (DSS) is activated.
Communication Failure between WCDMA
and LTE RAT detected when WCDMA-
LTE dynamic spectrum sharing is
LNCEL enabled.
This fault indicates that the HW baseband
resources allocated for WCDMA are not
fully utilized by the WCDMA LCGs. There
is at least one baseband subunit that
does not have an assigned WCDMA LCG
after Baseband Pooling. The baseband
capacity of WCDMA may be lower than
WBTS expected.
A flash memory operation failure. If this

5G BTS, AirScale SBTS. Flexi SBTS: fault continuously appears, the flash chip
- SMOD might be broken.
A flash
The memoryMicro
FlexiZone operation
BTS, failure. If this
Flexi Zone
5G BTS, AirScale SBTS. Flexi SBTS: fault continuously appears, the flash
Access Point, or Flexi Zone SFN Antennachip
- SMOD might be broken.
has detected that one or more access
panel ports is enabled.
Small Cell: This state of elevated security risk is not

-FSM expected in field conditions.
A power cycle is detected. This fault is

raised at BTS startup after the power
FSP cycle.
Stepper motor broken or moving structure
clogged or at least
Filter is clogged, one heater
differential is broken
pressure
(if installed)
between unitorinside
wholeand
subrack
outsidecontrol
is too
Subrack board
high. is broken.
[AMOC]: 8V or 10V lines are missing at

subrack control board or two temperature
sensors are defective or whole subrack
Subrack Heater
control is degraded
board or broken
is broken.
[AMOD]: Stepper motor broken or moving
structure clogged or at least one heater is
broken(if installed) or whole subrack
Subrack control
Flexi BTSboard
FDD,is broken.
Flexi BTS TDD, AirScale
BTS TDD, AirScale BTS FDD, Flexi
1: AMOD Temperature&humidity sensor
SBTS,
board AirScale
is broken SBTS:
Flexi
The SBTS: system (OSE) goes into
operating
2:
The AMOD Pressure sensor board the is
Subrack the error handler withbetween
broken
synchronization FCM,
a fatal status. This
and/or FCT and FSP is lost.
might be caused of an out-of-memory
situation.
AirScale SBTS:
- BBMOD The synchronization
If only one FSP/ABIxbetween
in the BTSthe FCT
-Flexi
SMOD BTS FDD, Flexi BTS TDD, AirScale BTS and ABIx is lost.
generates this fault, there is a malfunction
TDD, AirScale BTS FDD, Flexi SBTS, AirScale in one of the FSP/ABIx sub-modules.
SBTS:
- BBMOD If all FSPs generate this fault, there is a
- SMOD malfunction in the FCT.
AirScale SBTS, Flexi SBTS: The antenna (RP3) link is down. The
- BBMOD transmitter or receiver drops from
- SMOD synchronization.
The cabinet door is open or the cabinet

Subrack door sensor is faulty.
The state of the external alarm line shows
that an external alarm is notified.
5G BTS, AirScale BTS FDD, AirScale BTS
TDD, AirScale SBTS, Flexi BTS FDD, Flexi The user specifies, during
BTS TDD, Flexi SBTS: commissioning,
The state of the the alarmalarm
external number,
line shows
- SMOD severity, and polarity
that an external alarmthat indicate the
is notified.
-5G
RMOD
BTS, AirScale BTS FDD, AirScale BTS fault.
external number,
line shows
- SMOD severity,
that an external alarm is notified. the
and polarity that indicate
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
BTS TDD, Flexi SBTS: commissioning, the alarm number,
- SMOD severity, and polarity that indicate the
- RMOD fault.
external number,
line shows
is notified.
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
- RMOD fault.
external number,
line shows
is notified.
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
- RMOD fault.
external number,
line shows
is notified.
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
external number,
line shows
- SMOD severity,
-5G
RMOD
EAC_IN lines arethe alarm number,
misconfigured. It means
- SMOD severity,
that: and polarity that indicate the
- RMOD fault.
- port ID above 12 is configured for use,
but EAC box is not detected
- port ID above 24 is configured for use,
but EAC box in RS485/HDLC mode is not
SMOD
5G BTS, AirScale BTS FDD, AirScale BTS detected.
TDD, AirScale SBTS, Flexi BTS FDD, Flexi Second EAC box has been connected to
BTS TDD, Flexi SBTS: single system module through FPFH.
- BBMOD Such deployment is forbidden and means
-SMOD
CABLINK that all EAC lines become disabled.
- FHS
- LNA
SMOD
- LNBTS
BBMOD
- PWRMOD A software download to FSP, DSP, ABIx,
RMOD
- RAEU or FR has failed.
- RETU The communication with the application
- RMOD has failed. It has not replied to the
- SMOD message that has been sent and/or
- SMOD_EXT resent to it.
to support subsectors.
AirScale BTS FDD, AirScale BTS TDD,

AirScale SBTS, Flexi BTS FDD, Flexi
The radio channel that has been
5G BTS, AirScale BTS FDD, AirScale BTS requested in the commissioning file is not
TDD, AirScale SBTS, Flexi BTS FDD, Flexi supported by the detected BTS radio or
BTS TDD, Flexi SBTS: MHA hardware because of an incorrect
LCR
- BBMOD carrier
5G BTS, bandwidth
AirScale or
BTSincorrect center
FDD, AirScale
NRCELL
- CABLINK frequency.
BTS TDD, AirScale SBTS, Flexi BTS
- FHS FDD, Flexi BTS TDD, Flexi SBTS:
- SMOD The baseband-bus-related configuration
-5G
SFP
BTS, AirScale BTS FDD, AirScale BTS has been rejected by the HW SW, DSP,
-RMOD
TDD, AirScale SBTS, Flexi BTS FDD, Flexi RF SW or FHS SW.
5G BTS:
BTS TDD, Flexi SBTS: Master clock frequency is tuned to within
- BBMOD 5% of its minimum or maximum tuning
- CABLINK The
limit.baseband bus synchronization has
- SMOD failed or has been lost.
AirScale SBTS,clock
The reference Fleximonitoring
BTS FDD,has Flexi
AirScale SBTS, Flexi SBTS: BTS
detectedTDD,a Flexi
loss ofSBTS:
signal in the reference
- SMOD The OCXO
received fromadjustment area is reaching
the FT.takes
The OCXO
its limit warm-up
value. too long and
the OCXO does not become
The DAC word value of the OCXO active iswithin
less
a period of eight minutes from
than, or equal to the value of the power-on.
The ambient temperature might also be
parameter
SMOD too low or it changes too fast.
Min.OcxoControlValue.Alarm.Set
5G BTS, AirScale BTS FDD, AirScale BTS specified in BPF, or greater than or equal
TDD, AirScale SBTS, Flexi BTS FDD, Flexi to the value of the parameter
BTS TDD, Flexi SBTS: Max.OcxoControlValue.Alarm.Set
- SMOD specified in BPF.
The output signal of the OXCO is missing
and the system module cannot deliver the
30.72 MHz System Clock required by the
SMOD other units.
The Masthead Amplifier (MHA) does not
work properly. However, the system
cannot determine
The Masthead the impact
Amplifier ondoes
(MHA) the RX
not
LNA signal level.
work properly. Because of the low current
drawn by the device, it is assumed that it
does not provide
The Radio modulegain in the
or filter RXdetected
has signal
path, and therefore, the received
over-current on the antenna line. TheRF
LNA signal level is decreased.
antenna line might be damaged (short-
circuited),
VSWR value or some
aboveantenna
“VSWR linemajordevice is
ANTL causing overload.
threshold” has beenAll antenna
detected. line
LNA The VSWR
devices value
powered exceeds
by the level
the antenna line are
RETU defined
out of as criterion for VSWR Minor
order.
Note:
event.InThe
REL5.1 and REL2.3
impedance RFM/RRH
of the antenna line
5G BTS, AirScale BTS FDD, AirScale BTS unwanted VSWR alarms are suppressed
does not match the impedance required
TDD, AirScale SBTS, Flexi BTS FDD, Flexi when
by theboth
RadiovswrMajorThreshold
Module. and
BTS TDD, Flexi SBTS: vswrMinorThreshold are set to HW
- ANTL specific
Note: In maximum value 3.5.unwanted
REL5.1 RFM/RRH
VSWR alarms are suppressed when both
vswrMajorThreshold and
vswrMinorThreshold are set to HW
ANTL specific maximum value 3.5.
The Radio Module has detected a

RX1-n malfunction of an internal LNA unit.
aggregation pool as the cell with missing
DSP resources.
The fault can be also detected for

AirScale due to incorrect baseband pool
configuration if baseband pooling feature
is
Theactivated (actBbpooling
Radio Module is true).
is unable to tune to a
required sub-band properly (tuning
This faultorisanother
failure), also detected when has
major failure RP3-01
been
links
detected by the Radio Module (unitcase of
between system modules (in
TX1-n, RX1-n FSMF
faulty).+ FSMF) or between the system
module and its connected radio module
or between baseband module(ABIA) and
system module (in case of AirScale +
The radio
FSMF) module has
or between detected an
baseband
RMOD internal filter failure.
module(ABIA) and baseband
module(FBBx)
1845: TILT is not (inconfigured.
case of AirScale +
FSMF) are lost.
Others: Antenna tilting is not possible or
RET This
mightfault
not is also detected
function when there is
correctly.
not enough Beam Id range to allocate the
1845: TILT is not
TDD mMIMO cell configured.
to the eCPRI TDD
MAA/RU.
RET might not is
This fault function correctly.
also detected when there are
not
1845:enough
TILT iscarrier component resources
not configured.
for the TDD mMIMO cell allocated on
eCPRI
Others:TDD MAA/RU
Antenna tilting- is
product code. or
not possible
RET This
mightfault
not is also detected
function correctly. when there are
not enough eAxC addresses for the TDD
1845: TILT is not configured.
mMIMO cell allocated on eCPRI TDD
MAA/RU - product code.
RET might not function correctly.
The fault can also be detected for a 5G
1845:
cell due TILT
to: is not configured.
a. improper 5G beamforming radio type.
Others:
b. Antenna tilting
not supporting externalis not possible or
antenna
RET might not function correctly.
beamforming
c. not supporting external antenna with
- MHA subsectorization
- RAE d. not supporting
A hardware failureantenna
has been panel split by
reported
- RET mode
ALD (RET, MHA).
e. configured beamforming cell for no
The unit is in aRU
beamforming download mode state.
- MHA This fault
f. radio is returned
AHQK is usedwhen an
for external
- RET unsupported procedure
antenna beamforming occurs in the
- RAE download mode.
g. RU available memory cache is not
enough for requested PIDs
SMOD A corrupted SW file in the FLASH is
RMOD The fault can
detected. Thebe also
unit detected,
cannot performfor aa 5G
FHS beamforming
complete start-up. cell, in case the detected
radio is not a 5G O-RAN radio, or it does
The synchronization
not support beamforming. setup between
secondary core (working as sync slave)
and
The primary
fault cancore (working
be also as sync
detected, for a 5G
SMOD master) has failed during BTS
cell when cell allocation is impossible startup.due
BCF/BTS to the fact that the cells are
WCEL commissioned on CPRI-A radios as well
LNCEL as CPRI-N radio cabled in the same ABIL
NRCELL board.
A fault in the Masthead Amplifier (MHA) is

detected. MHA functionality is degraded.
LNA The real impact cannot be determined.
A fault in the Masthead Amplifier (MHA)
has been detected. The MHA is not
LNA working.
- LNA The device is not working properly, the

- RET configuration is not valid, or a given
- RAE parameter is incorrect.



- RET configuration is not
The antenna line valid,isornot
device a given
properly
- RAE parameter
configured.is incorrect.
The antenna line device set-up fails, for

example, due to protocol error or inter-
RET, RAE, MHA operability problem.
An autonomous internal delay
measurement has failed. The internal
delay cannot
5G BTS, be measured
AirScale BTS FDD, forAirScale
a cell for
- BBMOD any
BTS TDD, AirScale SBTS, Flexicertain
of the RAKE receivers in a BTS
- SMOD baseband
FDD, Flexiunit.
5G BTS, AirScale BTS FDD, AirScale BTS The reference clock monitoring has
TDD, AirScale SBTS, Flexi BTS FDD, Flexi detected a loss of PPS signal in the
BTS TDD, Flexi SBTS: reference received from the GPS receiver
- SMOD or
The the SyncHubclock
reference master.
monitoring has
5G BTS:
detected
The RF module/O-RU of
a signal loss 2.048 MHz has
configuration
received
failed because of a HW or reference
from an external SW fault.
source connected to the Sync In interface
SMOD of the System
AirScale Module.
- FHS The RF module configuration has failed
- RMOD because of a HW or SW fault.
A critical configuration file is missing from

RMOD the RF Module.
The RF Module SW has detected that a

RMOD non-critical configuration file is missing.
The System Module clock reference

RMOD differs from the RF Module clock.
The baseband bus between the System
Module and RF Module is out of
RMOD synchronization.
- RMOD The RF or FHS Module baseband bus

- FHS was configured incorrectly.
5G BTS:
The RAP TX path cannot be used.
There is an error in the baseband or
RMOD
5G BTS, AirScale BTS FDD, AirScale BTS optical
AirScalebus.
TDD, AirScale SBTS, Flexi BTS FDD, Flexi AirScale SBTS, Flexi BTS FDD, Flexi
BTS TDD, Flexi SBTS: BTS TDD, Flexi SBTS:
- PHYANT The TX path of the RF module cannot be
-5G
RMOD
BTS, AirScale BTS FDD, AirScale BTS used.BTS: AirScale BTS FDD, AirScale
5G BTS,
TDD, AirScale SBTS, Flexi BTS FDD, Flexi The
BTS RXTDD,path in the RAP
AirScale SBTS,is faulty.
Flexi BTS
BTS TDD, Flexi SBTS: FDD, Flexi BTS TDD, Flexi SBTS:
- RMOD AirScale BTS FDD,
The TX output power AirScale BTS has
adjustment TDD,
- PHYANT AirScale
failed. SBTS, Flexi BTS FDD, Flexi
The RX RF synthesizer of the RF module
is not locked.
- RMOD The RF Module filter has a measured TX
-5G
PHYANT
BTS, AirScale BTS FDD, AirScale BTS power
For SNMPthat interface,
is too low.the received power
TDD, AirScale SBTS, Flexi BTS FDD, Flexi is low for the RRH.
- PHYANT For CPRI-A interface, the RX path in the
-5G
RMOD
BTS, AirScale BTS FDD, AirScale BTS FR module is faulty.
- FHS The unit is out of order because of a
- RMOD software or hardware fault.
AirScale BTS TDD, AirScale BTS FDD, Flexi The power supply supervision has
SBTS, AirScale SBTS: detected an overvoltage, undervoltage, or
- RMOD overcurrent in the RF module.
The feedback signal to predistortion is too

- RMOD weak or missing. The TX performance is
- PHYANT degraded.
Out of order unit status: The radio unit is

too cold for proper operation. Heating of
the module is ongoing.
Antenna line The TX signal adjustment fails.
Working unit status: The radio unit is
below its normal operating temperature
but is still capable of transmitting.
RMOD Problems might occur.
The permanent memory in the RF module
is corrupted, the module product code or
serial number is missing, or the module
RMOD product code is unknown.
5G BTS:
Themodule
RF RF Module SW has
is locked. detected
Fault is detected in
conflicting or corrupted
a radio-sharing configuration
configuration where NR
RMOD data. plays the role of the slave module.
ASIx

AirScale
A power-on SBTS, FlexiofBTS
self-test the FDD, Flexi
RF module
RMOD BTS TDD,at
has failed Flexi SBTS:
start-up.
5G BTS, AirScale BTS FDD, AirScale BTS This fault is detected in a radio-sharing
TDD, AirScale SBTS, Flexi BTS FDD, Flexi configuration where a WCDMA, CDMA or
BTS TDD, Flexi SBTS: a
TheNRhighest
is the master system
temperature onmodule,
pipe (asand
- FHS The
an RF/FHS
LTE
indicated module
FSM/ASIx hastemperature
plays
by designated lostrole
the lockoftothe
the
- RMOD incoming
slave
sensors) clock.
module.
exceedsThispre-defined
fault meanspower that the
FR is blocked.
reduction When an
limit (either 1dBLTE FSM/ASIx
or 3dB) in the
plays the role
RF module. of the master,
Pipe-related or an LTE
temperature
- RMOD system
sensorsmodule
used for shares a CPRI/Ir
Tx power radioare
reduction
- PHYANT module with an SCDMA system module
HW-variant-specific.
(dual mode configuration), and the FR is
blocked, fault 48:EFaultId_UnitBlockedAl
is detected, not 1931.
- FHS The
Note:FPGA software
The fault can beupdate in the when
cancelled,
- RMOD RF/FHS module has failed.
unblock operation will be performed by
master system module accordingly.
If shared technology is fALU CDMA, LTE
RRH blocking may be cleared by a full-
RMOD unconditional restore on CDMA.
- FHS Unit cannot identify the fan vendor or the

- RMOD fan is not installed.
- FHS
- RMOD Fans in the RF/FHS module are not
- ASIRMOD running.
Fans in the RF module are rotating

RMOD slower than requested.
Validated module temperature exceeds or

FR is equal to the predefined maximum value
FHS allowed.
The validated sensor temperature is

- FHS greater than, or equal to the predefined
- RMOD value in the unit property file.
The validated temperature of any PA or
Pipe sensor in the RF module is higher
- RMOD than, or equal to the pre-defined value in
- PHYANT the unit property file.
The calculated ambient temperature

value in the RF module exceeds the
RMOD allowed ambient temperature range.
The RF module overvoltage protection is
RMOD broken.
The optical interface is not working
properly.
The small form-factor pluggable (SFP)
SFP module might
Increased be missing
bit error or been
rate has faulty.
detected on thehigh
An abnormally optical link torate
bit error thehas
radio
- CABLINK module,
been detected on the optical link toLCV
which results in sporadic the
- FHS (line
radiocode violation)
module, whicherrors
resultsinindownlink
permanent
- RMOD baseband
baseband processing.
processing failure. I/Q data
stream cannot be successfully processed
by FRM/FHS. This is caused by the burst
- FHS of consecutive LCV (line code violation)
- RMOD errors.
The Tx in the RF module has been
switched off to protect the radio module
hardware, which might be damaged
- ANTL because of high-reflection (VSWR)
- PHYANTU conditions.
The FR module has detected permanent
RP3 routing collisions in either downlink
(TX), or uplink (RX) transmission
RMOD directions.
Input voltage to the radio unit is out of the
expected range, but the radio unit power
supply can still provide output voltages
RMOD adequate for operation.
The RRU digital pre-distortion (DPD) has

RMOD failed during self test.
RMOD The CPU cannot connect to the DSP.
RMOD DSP loading has failed.
An error has occurred during a read

RMOD and/or write attempt on the FPGA.
properly. The Small Form-factor
Pluggable (SFP) module might be
SFP missing or it might be faulty.
The optical interface does not work

properly. CPRI transmission to the upper
CABLINK hop does not work properly.
properly; performance aggravation is
CABLINK high.

properly. The received power aggravation
CABLINK is high.
The small form-factor pluggable (SFP)

SFP module is mismatched.
properly. There is abnormal signal
reception from the upper hop FR. This
fault is valid only for radio modules in
CABLINK chain configuration.

FR The RRU has lost its power supply.
properly.
This fault is interface
The optical valid onlyisfor
notradio modules in
working
a chain configuration.
properly.
Note: The transmission
The CPRI Optif is from the perspective
is not working of
CABLINK the previous
properly. radio.
This fault is valid only for radio modules in
a chain configuration.
Note: The Optif is from the perspective of
CABLINK the previous radio.
Small Cell:
-FR The RF does not detect downlink
-Antenna Line TX baseband
baseband datapower
whenisattoo high.
least one carrier
is enabled. There might be a problem in
Small Cell: software components which source
-Antenna Line downlink data, or the problem might be a
-FSM configuration-related issue.by the PA is
The temperature reported
beyond the critical temperature and fault
recovery mechanism
The FR module have notaresulted
has detected transientin
a lower temperature - so the
problem or DFE FPGA SW update thatRFSW is
Antenna Line shutting
requires down the PA
a reset recovery.on its own.
1. The configuration of the External Alarm
Or O-RU unit(EAC)
and Control detected
linesaoftransient
the Radio
problem
Module has failed because affects
which significantly of a hardware
operation
or softwarethat requires a reset as a
fault.
RMOD recovery.
OR
2. Number of commissioned EAC lines of
the Radio Module is incorrect, i.e. higher
- RMOD than number of EAC lines supported by
- EAC the detected
Hardware Radio Module.
protection logic in the radio unit
has disabled the TX path to protect the
radio unit because of an overdrive
ANTL condition detected in the power amplifier
RMOD circuitry.
The radio unit has detected a failure on
its optical connection to the system
module
Hardware or protection
an upstream radio
logic unitradio unit
in the
RMOD (chaining case).
has activated overdrive protection on the
TX path to avoid damage to hardware.
Overdrive protection keeps the TX path
operational but with degraded
RMOD performance.
Antenna calibration has failed on at least

The SFP onbecause
3 antennas the radioofunit is either faulty
a transmission
SFP or not supported.
path failure.
The path means all units between the

signaling processor (DSP) and the
RMOD antenna inside the radio module.
The antenna periodic calibration result

does not meet the requirements
The communication radio modulefor
with
RMOD amplitude and/or phase error.
external Receive Diversity Expansion
Module
The fault(RDEM) is lost.
is reported The cable
in radio to the
modules that
external
consist of two separate hardware units or
RDEM module may be broken
disconnected,
connected by an andoptical
external module
cable. The may
near
RMOD have failed.
end Radio Module sub-unit cannot
communicate with the far end sub-unit,
possibly due to failed CPRI link between
the two sub-units, or a failed far end sub-
RMOD unit.
The Radio Module is reporting that the
access door protecting the maintenance
data port is open. The maintenance port
RMOD allows local
The fault control ofbythe
is reported Radio Module.
complex radio
modules with multiple physical units,
where functionality is distributed. An
incompatibility has been found between
RMOD board
The revisions.
The fault
receivedis reported
optical by complex
signal on theradio
link
modules with multiple physical
port is unexpectedly low from upper units hop
where
(towardfunctionality
the system is distributed.
module), An
though
incompatibility has been found
communication is still possible. with the
RMOD identification method.
There is a poor CPRI link connection, bad
CPRI cable, oroptical
The received failingsignal
CPRI ontransceiver
the link at
the previous radio module or system
port is unexpectedly low from the next
module connected
hop (further to the module),
from system cable reported
though
CABLINK as the fault source.
communication is still possible.
There is a unit
The radio poorhasCPRI link connection,
detected bad
that the frame
CPRI
timing on the affected optical port is out at
cable, or failing CPRI transceiver of
the next
range radio to
relative module connected
the clock to the
reference
CABLINK cable reported
source. as faultRF
In a CPRI-A source.
sharing
configuration, the clock circuitry for one or
both of the System Modules connected to
this radio unit is not properly
CABLINK synchronized to its reference source.
The detected Passive InterModulation
(PIM) performance measurement has
A new carrier
exceeded is being
threshold configured
Level 2. by LTE,
or the technology sharing the radio unit,
which
A PIM requires the radio
cancellation unit
fault is antoindication
retune itsof
RF
non-linearity in the antenna system.with
hardware. Note that the alarm This
this
mayfault is automatically
be caused by damage canceled
to the RFonce
the autonomous
feeders, recovery
the antenna actionsorare
assembly,
RMOD completed.
caused from external structures. Damage
may be caused by water intrusion,
crimped coaxial cables, loose connectors,
lightning damage, or physical damage to
ANTL the antenna
A small assembly.
form-factor pluggable (SFP)
malfunction has occurred or the SFP
module is not physically present (no
electrical connection). The SFP is a part
SFP of
A the fiber
small cable package.
form-factor pluggable
The incoming optical signal to (SFP)
the Small
malfunction
Form-Factor has occurred
Pluggable or the
(SFP) is SFP
missing,
The fiberiscable
module not is experiencing
physically present (no
is too weak,
interference; or the fiber cable
data transmission has
is been
faulty.
electrical
detached. connection). The SFP is a part
SFP of the fiber cable package.
A physical connection failure between the
The connection
optical interface between the System
and the summing
Module and the RF
function has occurred. Module is broken, or
the connection between the Baseband
SFP Module and of
The reason thetheRFfault
Module
mightisbebroken.
a low-
quality or polluted SFP, or a low-quality
optical cable used to connect radio
module
The RP3toorsystem module
Ethernet and/or
buffering is not
CABLINK extension baseband module.
working, and the buffer becomes full. The
optical device is malfunctioning. The fault
might be generated because of
synchronization problems
The RP3 or Ethernet or incorrect
buffering is not
CABLINK initialization.
working, and the buffer becomes full. The
optical device is malfunctioning. The fault
might be generated because of
synchronization problems or incorrect
CABLINK initialization.
- BBMOD The
The control
master message traffic
frame in the between the
received
- SMOD modules is malfunctioning.
baseband bus frame is not in the correct
place related to the internally-generated
BBMOD master frame pulse. Either the frame has
CABLINK There
been is ainto
set baseband
the has
wrongbusplace
address
(PI delay)
A decoding
mismatch error
initself been There
the summing. detected
areintwo
SMOD or
thethe data
baseband is in
internal the wrong
link. The place.
data
possible causes:
packet is lost, or the content is corrupted.
1. A configuration error (two different
- BBMOD This situation
baseband also
units occurs when
functioning) thean
- after links
- SMOD are not synchronized with each
acknowledgement, the fault returns.other.
2.
TheData corruption on
clock-crossing the bus
buffer - appears
underflow or
- BBMOD once when an unsynchronized
overflow in the RX block, and thedata is
- SMOD sent by the
received baseband.
data, might be invalid. The fault
is an indication that either there is too
large of a clock drift between the received
signal and the internal clock, or the RX
CABLINK rate setting is wrong.
BTS TDD, Flexi SBTS: The software update to the BTS has
- SMOD failed, or is
Interrupt the BTS software
generated is corrupted.
if a message does
not get routed.
- BBMOD
- CABLINK This is considered normal when DSPs
- SMOD are starting
Summing up, and
checks theRP3 sync of
headers is done.
the
messages to be summed. If the header is
not an allowed type, summing is not
- BBMOD performed and an empty message is sent
- SMOD instead.
The transmitter has detected an RP3

- BBMOD message from a summing coincident with
- SMOD a transmission rule.
The transmitter has detected more data

- BBMOD coming from a summing than the current
- SMOD link rate can support.
The enumeration algorithm has detected

a permanent failure that prevents sRIO
SMOD (serial RapidIO) system maintenance.
Congestion avoidance hardware of the

sRIO (serial RapidIO) switches has been
FSP, FBBx, ABIx triggered.
BMU (Board Management Unit) product
data EEPROM of an extension board
- BBMOD (FSP) or subrack control board/subrack
- CABINET extension board data cannot be read out
- SMOD during a connect event.
It has been detected that the host link,
which is used for the sRIO (serial
RapidIO) system maintenance, is going
SMOD down.
This fault signifies a critical software
component failure, for example when the
- BBMOD user plane computing environment is
- SMOD down.
The error rate is too high in the BTS

Airscale SBTS: ABIx; Flexi SBTS: FSP, FBB internal bus.
O&M software is unable to initialize TRX

BTS (sector) into operational state.
TRX control plane connection has been

BTS(sector) lost.
is
1. higher Feature than the number
Activation Case:of
commissioned
DSS Feature islocal enabledcellsfor at GSM
BTS. sector
2. BSC
at Number andofDSS TRXs configured
Feature is notinenabled
BSC is
higher
for mappedthan the LTEnumberlocal cell of in
commissioned
channel
commissioning groups (scf). under the local cells at
BTS.
The difference of received signal strength
3.
2.
between Number
Peer RAT
theofmain
pathsand
Centre in the
Frequency TRXs Case:
diversity paths of
configured
“DSS CENTRE in
logical TRX at DSP is exceedingBSC does
FREQUENCY” not match with
configured
the
the
for number
DSS GSM
threshold defined by BSC. of commissioned
sector in BSC channels
is not in
BCF the
matching
In
If the channel
LooseRSSI with
Phasegroups
LTE
difference under
andfrequency
Time
betweenthe
Sync local
mode,
main cells
and
BTS(sector) at
commissioned
the
diversity BTS.
fault is is afornegative
RXtriggered mapped
when:value, LTE local
then cell
the
in
-antenna SCF.
during start-up,
hosting the the RXSystem
mainModulepath is has
still
reported no time as information
faulty. Otherwise, after athe 5-minute
3.
timeout
antenna Peer RAT hosting Frequency overlapping
the RX diversity path is
BTS TRX
-reported the downlink
estimated
as faulty.frequency
time errorconfigured
exceeds the in
BSC
allowable for the GSMGSM sector,
limit for looseoverlaps with
Hyper-SFN
The
LTE txPowerPooling feature is enabled in
sync dedicated spectrum in downlink.
Site Configuration File(SCF) and Tx
- there is a 96 h timeout after the last time
power
4. pooling
Flexible GL feature
DSS license is not
case:
information received by the System
BCF enabled
Paired from BSC.
ModuleLTE cell bandwidth is limited by
radio filter (LNCEL_FDD.slimRfFilterDL
has
Management
In another
Phase Sync value
plane
mode, than as""none"")
connection
Sync Hub any
(OMU
shared
Signaling) TRX to reported
BSC
Master, the fault is triggered when: couldin Shared
not be
BCF Frequency
established,
- during start-up, Array
or it is sent
the by BSCModule
broken.
System is locatedhas
outside
still no time radioinformation
filter (usable) aftertransmission
a 5-minute
bandwidth.
timeout
An invalid configuration is received, or
-timeout the estimated time errorprocedure
for configuration exceeds the from
DSS
allowable GSM+WCDMAGSM limit Case:
for loose Hyper-SFN
BCF BSC.
The
syncR fault is reported when DSS mapping
GSM
- theresector is a 96h - WCDMA
timeout localafter cell
losingis all
defined
phase sync in commissioning
sources, and no andlocal
any of the
The
below
holdover BSC does not
conditions
possible respond to BTS
satisfies.
BCF initialization procedure.
1.
In SHS Feature Phase Activation
Sync mode, Case: as Sync Hub
DSS
Slave,Feature the fault is isenabled
triggered for when:
GSM sector
at
-Aduring BSC and DSS
start-up,
TRX is added to an antenna feature
the System is not enabled
Module
hopping has
BTS(Sector) for
still
sector mapped
no without WCDMAlockinglocal
time information after
the cell
a in
sector. SCF
5-minute
timeout
There isRATmismatch between measured
2.
-PMTU Peer
the estimated Centre Frequency
time error exceeds Case:
the
There
“DSS and
is
CENTREa the
mismatch configuredbetween
FREQUENCY” PMTU. the
configured
allowable GSM limit for loose Hyper-SFN
commissioned
for
sync DSS GSM sector and configured
in BSC is BCF not
BCF Reason
Identifier.
matching for theWCDMA
with fault/alarm is packet size
frequency
-mismatch
there is ain96 h timeout
specific after
parameters. poor time
configured
accuracy indication for mapped WCDMAfrom
is received localsync
cell
at
hub RNCmaster
Mismatch between:
-- there
packet issizes
a 96 in h timeout
parameter after losing SHM
SMOD 3.
link, Peer
and RAT
no Bandwidth
local holdover Case:possible
udpMaxDatagramSize
Shared frequencies configured (octets) in BSC for
-dynamic
local MTU packet sharing
spectrum size in parameter
between the
localMtuResult
GSM Sector and (octets)
the WCDMA Cell are
-not
path MTU packet
inside the 3.8MHz. size in parameter
BCF pathMtuResult
The required feature (octets) towards
is not enabled BSC. due
to
4. below
Peer RAT reason Frequency overlapping
- BTS (sector) TRXs uplink frequency configured in BSC
- LNCEL The
for thereason
GSMfor the fault/alarm
sector, overlaps with is
- WCEL mismatch
WCDMA dedicated between BSC spectrumand BTS SCF, it
in uplink.
could be one of the below
When
1. Leandynamic
GSM isspectrum enabled at sharing
BSC but (DSS)
not is
activated, and
commissioned in SCF GSM RAT fails to receive
LNBTS an acknowledgment
2. Lean GSM is not enabled from peer at RAT
BSC for but
WNBTS DSS related
commissioned in SCF message sent to that RAT.
3. CMST is enabled at BSC but not
commissioned in SCF
4. CMST is not enabled at BSC but
BCF commissioned in SCF
This Passive Inter-Modulation (PIM)
cancellation fault is an indication that the
PIM Canceller is unable to remove PIM
as an indicated comparison of PIM power
before cancellation, to PIM power after
This Alarms indicates
cancellation. that Dynamic
The presence of PIM is an
Power
indication of non-linearityenabled
Poling feature is in
in the antenna
commissioning and at BSC, but
system. This may be caused by damage internally
it's notRF
to the in use. No compression
feeders, the antenna is required
assembly,
BTS(Sector) and done by Baseband.
or caused from external structures.
Damage may be caused by water
intrusion, crimped coaxial cables, loose
connectors, lightning damage, or physical
ANTL damage to the antenna assembly.
The
This actPimCancellation
fault is raised by thefeature flag is
eNB when set
there
to true at a radio which does not support
is an attempt to activate the PIM (Passive
RMOD the PIM Cancellation
InterModulation) feature. that is, set
Cancellation,
the pimCancellingEnabled parameter to
"true" on a radio module, but due to some
issues, the radio
The External PIMisCancellation
unable to activate
featurethe
RMOD PIM Cancellation.
activation flag is set to true at EPIMC and
at least one RMOD targeted for External
PIM Cancellation is not on the EPIMC
- FHS support list or the EPIMC HW unit is
- RMOD swapped with an incompatible HW unit.
One of logical C/U-plane connections has

TX1-n, RX1-n a fault, is unstable or broken.
Unit has detected a fault of one of its

O-RU interfaces.
C/U-plane message content was faulty for

TX1-n, RX1-n. an undetermined reason.
One of the power amplifiers in a module

FR; TX1-n is faulty, unstable or broken.
RF SW detected that FPGA software

downloading to antenna submodule has
RMOD failed.
RMOD
AirScale BTS TDD: Antenna
Flexi BTSmodules have
FDD, Flexi been
BTS lost.AirScale
TDD,
- FCT(HW rel.4) BTS TDD, AirScale BTS FDD:
The BTS has detected an abnormal
Flexi BTS FDD, Flexi BTS TDD: operation or a failure in the internal
- FSM functionality of the System Module.
The BTS has detected an abnormal
operation or a failure in the BTS
Flexi BTS FDD/TDD: FBB; replaceable
AirScale BTS FDD/TDD: ABIx baseband unit.
source in this case.
c. AirScale + FSMF: When there is short
SRIO link break and there are baseband
resources reallocation , GSM or WCDMA
RAT RESET is necessary to take
resources into use.
Flexi In
21.2 BTS BTS FDD, runtime Flexi(after BTS U-Plane
TDD, AirScale
BTS TDD, AirScale
deployment calculation), BTS FDD: the BTS O&M
The BTS
system has has detected
detected an abnormal
resources
operation
Flexi BTS or
necessary fora cell
FDD, failure setup,
Flexi in
BTS the internal
forTDD,example Flexi
FR functionality
a. AirScale
SBTS,
The AirScale
optical + of the
AirScale:
interface SBTS: RF Module.
commissioned
is not working
Secondary
This BTS fault
properly. Core (that was
indication is not detected
generated if at
BTS
the start-up)
Thereference
Small Form-factor clock monitoring Pluggable function
(SFP)of
or
the
moduleBTSmight does be notmissing,
receive the faulty,configured
or
The
b. Flexi BTS hasBBMOD
commissioned detected an was abnormal
FR synchronization
mismatched. reference (that signal, or if all
operation/ or
detected a failure in the BTS
the synchronization reference signalsstart-
un-commissioned at BTS are
internal
up). or external BTS
The AirScale/Flexi (optical (Systemlink) baseband
Module)
missing.
bus.
RAT The
resetfailure
has detected in casean cannot of WCDMA
abnormal be operation is or a
attributed
necessary
failure in antoto a specific
take
optical the
RP3 module
resources
interface and intothere
use.
Background information:
FSM, FR, FSP are
WCDMA several
between RAT
two possible
is the fault
modules. fault source
sources. in this
case.
The failure
There cannot be synchronization
is configurable attributed to a
specificlist.
priority module but there are several
22.1.
possible BTS O&M
fault has a late
sources, detectionfiber
for example, of
FSM, FR, ABIx RP3-01
optical
Normally, link
cable, that
SFP,
all temperature was
the BTS sourcesor not available
individual during
module.
The
BTS internal
startup and time before of theare RFnot in
use
Moduleat the
or same
System Module(it deployment
depends
exceeds onthe the
calculation,
network planningwhile synchronization
and BTS source
configuration).
threshold
between
A fan, all value,
cores
the fans,isorprovided
themore
or ambientby
than HDMIone link.
fan
During
temperature BTS start-up,
of the the available
modules arethe beyond
A
in BTS
the
sources reset
same is
fan
are checked needed
group to
are take
rotating
against the slower
FSM, FR, FCT (HW rel.4) the
or specified
affected
faster cells
than limits.
into use. list
requested, areinnot
reference source priority therotating
BTS
AirScale BTS TDD: 22.2.
at all, BTS
or theO&M
commissioning RPM has
file, a late
information
and detection
deviations is not of
AirScale
- FCT (HW BTS TDD:
rel.4) RP3-01
available
regarding linkthethat
for the was not
fans.
missing The available
source reason during
for
generate this
-- FCT FR (HW rel.4)
BTS
fault
faults. startup
can be and
a broken before fan.deployment
The condition
-- FR Antenna Line Flexi BTS FDD, Flexi BTS TDD,
FSM/FAN, FR, FCT (HW rel.4)/FAN calculation,
for alarm activation when RP3-01 link is used for
is HW-dependent.
- LCR FlexiBTS, AirScale BTS TDD, AirScale
GSM
The and WCDMA
source for the IQ data
TRS can routing
be TDM
Flexi
- LCGBTS FDD, Flexi BTS TDD: BTS FDD:
between
interface ABIA
signal and
(for FSMF/FBBx
example, E1,(inT1, and
- FSM Some
Flexi of the
BTS FDD, commissioning
Flexi BTS parameters
TDD, AirScale
AirScale
so on), + FSMF
physical dual
layer core
Synchronous configuration).
-Flexi
FR BTS FDD, Flexi BTS TDD: are
BTS either
TDD, missing
AirScale orBTS faulty,FDD: or there is a
A BTS
Ethernet reset is
(SyncE) signal,needed to take the
-- FT
FSM mismatch
There a between
is cells compatibility them.or application
affected
layer Timing use. problem
into Packet
over (ToP) ininwhich the
-AirScale
FR BTS TDD: BTS HW/SW
the timing versions to
information orBTSs
the HW/HW is
- FCT (HWLine
Antenna rel.4) configuration.
- ABIx
23. not applicable
generated by aAnother ToP to master.
SBTS possibility is that
LCR there
The TRS reference sourceBTS
is a mismatch in the priority
- RF
LCG configuration.
24. SYNC.phaseErrorRecoveryThreshold
AirScale
- DSP SBTS: selection is also user-selectable.
- FCT (HW rel.4) is exceeded. BTS
Furthermore, if a signalreset listed
is needed in thetoTRS
recover
references synchronization
is not received, phase a BASE error.
Flexi BTS FDD, Flexi BTS TDD:
Flexi
- FSMSBTS: STATION
Flexi BTSisFDD, TRANSMISSION Flexi BTS TDD, ALARM is
-- FSM (HW rel.3)
rel.3) 25. BTS
reported. unable of synchronizing to
FCT (HW FlexiBTS,
RRH in CPRI-K AirScale RF BTS sharing TDD, AirScale
because
- FR BTS FDD:
clock crossing buffer underflow or
- FT A software
overflow in update
RX block. to aAmodule
BTS reset or sub-
is
- FSP assembly
needed to has failed, or with
synchronize a corrupted
RRH (radio) SW
- Faraday file has been detected in the FLASH.
26. Plan activation is stuck due to
The
unknownFlexiBTS/AirScaleBTS
reason. BTSorreset has detected
is needed to
The
an System
abnormal Module,
operation, theadevice
or failure, itself,
in the
recover.
has detected an abnormal operation or a
5G Masthead Amplifier (MHA).
FR,BTS,
MHA,AirScale
RET BTS FDD, AirScale BTS failure in the antenna line device.
TDD, AirScale SBTS, Flexi BTS FDD, Flexi 27. Carrier Aggregation configuration for
BTS TDD, Flexi SBTS: Note that thecells
the existing Tower cannot Mountedbe online Amplifier
- BBMOD (TMA)
activated due to cell mapping on BBand is
is synonymous to the MHA,
- LCR used
pools by that the does Antenna not fitInterface
to carrierStandards
FF,
- FRAISG MHA Group (AISG).
aggregation requirements. BTS reset is
- GSM RAT needed to recover carrier aggregation
- WCDMA RAT service (5G BTS only). Impacted 2CCs or
- FHS 3CCs CA configurations are reported in
- NRBTS additional information of the alarm.
FDD,
wrongFlexi schema",BTS TDD, "ValidationAirScale BTS
failed dueTDD,
to
BTS
AirScale TDD, BTSAirScale
FDD: SBTS, Flexi BTS
incompatible data", "no RNW cell
FDD,commissioning
The Flexi BTS TDD, fileFlexi
downloadSBTS:has not
managedObject
Flexi is created", or anAirScale
invalid
1. TheBTS
been power
started
FDD, level
from
Flexi that
the
BTS TDD,
is defined
BTS Element in the
combination
BTS TDD, of the cell
AirScale BTS parameters
FDD, Flexi
radio network
Manager or from (RNW)NetAct part of the site
administrativeState
SBTS, AirScale SBTS: and during auto-
configuration
configuration. file (SCF)
Either the isauto-
not supported
preventCellActivation.
A TX path failure has caused the multiple-
by the HW.
configuration might not be enabled in the
input multiple-output
2. Different power (MIMO)
levels or
for subcells of
NetAct
3. In case or the commissioning
of CBRS featuretoisbe file
used,is notthe
beamforming
combined supercells, as definednot
functionality in the
found.
family of downlink carrier aggregation
operational
RNW part oforthe degraded
SCF file,inare thenot cell that is
features
related tohave
the been TX.
faulty deactivated
This faultbyiseNB not
5G BTS, AirScale BTS FDD, AirScale BTS supported
Small Cell: by HW.
LCR (in order
reported to
in pass the
super cell check
cases. rule,
TDD, AirScale SBTS, Flexi BTS FDD, Flexi 3.
The Any combination of
commissioning file5G TDD cells,
download has not
actDLCAggr and other downlink carrier
BTS TDD, Flexi SBTS: configured
been started in from
n258the band BTS onSitethe Manager
same
aggregation feature activation flags have
- LNCEL RMOD,
or from causes intermodulation
to be setNMS during
to false auto-configuration.
in configuration file in
- NRCELL distortions
The in passive EESS
auto-configuration might23.6 not - 24
very exceptional case, trigged by be eNB's
-5G
RMOD
BTS, AirScale BTS FDD, AirScale BTS GHz
enabled
The band.
BTS inhasthe NMS,
detected the a license is
communication
changing
5G on channel bandwidth).
BTS: or the commissioning file is not
TDD, AirScale SBTS, Flexi BTS FDD, Flexi missing,
problem withtothe
Connection
found. SWGPS entity receiver.
has been lost.
BTS TDD, Flexi SBTS: 4.
This Configuration
alarm is used filetofor eCPRI
inform theTDDoperatorMAA
- GNSSE -The
that
AirScalefault BTS
productCode
another is ignored
BTS - is
FDD, faultuntil
missing
(the
AirScale theoriginal
GPS
in
BTSBTSreceiver
SW or
fault)
TDD,
-5G
GNSSI Flexi
has Zone Access
reached theFlexi Point:
commissioned
BTS, AirScale BTS FDD, AirScale BTS is
The
corrupted
toggling.
AirScale SBTS,
commissioning BTS
file FDD,state.
download Flexi
has not
TDD, AirScale SBTS, Flexi BTS FDD, Flexi BTS
been TDD,
started Flexi
from SBTS:
the Flexi Zone
5. Configuration
The alarm that file forFSPeCPRI TDD MAA
BTS TDD, Flexi SBTS: connection
Controller.
-fault
productCode The is to related
the
discovery
- sub-module
does not
to
of the
or
the
contain
original
DSPFlexi has
- BBMOD been
Zone is suppressed
lost,
Access or the and the new alarm,
reports
Zone an
- SMOD sufficient
which
error. is dataPoint
related
by the Flexi
totoconfigure
fault 4026: commissioned
Controller
TDD mMIMO mightcellnot be successful. This
fault is visible only at the BTSSM is raised. that is
AirScale SBTS, Flexi SBTS, Flexi BTS FDD,
Flexi BTS TDD: connected
The
6. internal
Configuration tomaximum
Flexifile Zone Access.
transfer unit (MTU)
Toggling alarms thatfor are eCPRI
related TDDto the RU -
- BBMOD configuration
productCode
original faults has failed
- issuppressed
are on
missing in BTS the FSP
until SWor or
the
- SMOD Flexi
FBB.
is Zone SFN Antenna:
corrupted.
toggling condition is file
The commissioning cleared.
download has not
5G BTS, AirScale BTS FDD, AirScale BTS been started from
TDD, AirScale SBTS, SBTS,
Flexi BTS 7. Configuration filethe
forFlexi
eCPRIZone
isTDD
Micro
RU -
Flexi SBTS, AirScale FlexiFDD,
BTSFlexi
FDD, The
BTS severity
or
productCodeFlexi of
Zonethis
- of
does
BTS
Access
not
fault
Point.
contain
the same
The
sufficient
Flexi BTS TDD, AirScale BTS TDD, AirScale as the
discovery severity the
of the Flexi original toggling
Zone SFN TDD Antenna
All units data fault.
BTS to configure commissioned
BTS FDD:AirScale BTS FDD, AirScale BTS
5G BTS, by the
mMIMO Flexi Zone Micro BTS or Flexi
-TDD,
SMOD There is cell.
Zone Access a RFPoint
sharing mode
might notconflict
be on
AirScale SBTS, Flexi BTS FDD, Flexi the radio to be shared by two system
BTS TDD, Flexi SBTS: successful.
8. Carrier(SM) This fault isconfiguration
Aggregation visible only at the
Small modules such as: to the Flexi
- BTS Cell: BTSSM
problem
(1) SM1
that
is
is connected
forinnewly
shared commissioned
mode and SM2 cells
is in
-FSM
- MRBTS Zone
due toSFN Antenna.
missing BB resources : 2CCs or
dedicated mode, or
- NRBTS 3CCs
(2) SM1 CAisconfigurations
in master mode failed
andor SM2 also
- LNCEL degraded.
in master mode, This caseor is valid for start-up
- NRCELL or commissioning
(3) SM1 is in dedicated of newmode cellsand
withSM2 in
- WNCEL Carrier Aggregation
master or slave mode, or service configured.
(4) SM1 is in slave mode and SM2 also in
slave mode, or
(5) SM1 is in dedicated mode and SM2
RMOD also in dedicated mode.
AirScale BTS FDD, AirScale BTS TDD,Flexi
BTS FDD, Flexi BTS TDD:
- SMOD
- BBMOD A module initialization has failed.
The Radio Module has detected that the

requested frequency
5G BTS, AirScale does
BTS notAirScale
FDD, fit the
RMOD capabilities offered by the Radio
BTS TDD, AirScale SBTS, Flexi BTS Module.
FDD, Flexi BTS TDD, Flexi SBTS:
The cell configuration is not officially
supported. Too many cells are assigned
LCR to the Tx group of the radio module.
An alarm message has been received

from the antenna line. The antenna line is
ANTL faulty.
only.
running
because(recovery SW
of the lack of update is still
DC power.
In this case, an FSP reset to activate the
supported).
new
Faultversion ofFSP
4082 for SW may cancel
fallback canthe
be fault.
The state of the
canceledinterface:fault is start/cancel
due to SW upgrade on FSP for
CPRI/Ir
FSP
only. SW fallback only.
In this case, an
Over-current case: FSP reset to activate the
4083:
new version of SW may cancel the fault.
The
The source state of unit
the has fault requested
isdetected
start/cancel SW for
- Theradio
fallback mutual module
because length has
of adifference
critical ofover-
problemthe that
An alarm
FSP
current message
SWonfallback
the ALD has
only.
port. been
Some received
antenna
parallel
had RP3-01/CPRI
occurred during links
start-up toward
after one
from
line the antenna line device. The the SW
radiodevice
update module
due
is causing
to isconfiguration
too large overload.
(more data than 60
ANTL antenna lineonoperation
4083:
Depending hardware is implementation,
degraded.
meters in OBSAI
migration failure, RRU,
or the and
SCF146 check meters
tool in in
The
antenna source line unit
devices has requested
powered SW
by the
CPRI
BTS RRU).
OM has The
detectedmain SCF link isfailureconsidered
and
- LNA fallback
RS485
SWaBTS because
IUANT,
download toor of
an aantenna
powered criticalbyproblem the linkthat
line
as
the
had
reference,
occurredcannot and
duringoperatethe secondary
start-up with after that device
SCF.
the SW
is
- RAE antenna
has
compared failed line,
because
to has are out
the detected
main of
of an order.
link. incorrect
If
updateBTS O&M
dueortofile configuration data that the BTS
- RET checksum
can start with theformat.
previously-active
migration
Undercurrent failure, case: or the SCF check SW tool in
- RF sharing
version, BTS has
O&M been
processeddisabledconsistentwith
BTS OM has detected SCF failure and
- LNA master
fallback
SW WCDMA
and
download the because
previously-active
tooperate
an antenna the mutual SW
the BTS
The radio cannot
module has with line
detected that device
SCF.
- RAE length
version
has difference
failedis running
because between
in ofallan HW theunits
incorrect cables
in the of
If BTS O&M has
undercurrent on the detected
ALD that There
port. the BTS is a
- RET the
BTS.
checksum WCDMA
The BTS
or thesystem
file is up module-shared
and running. RF,
can
problem start with
with theformat.
previously-active
ALD port connection. SW
and the LTE
Otherwise, the system module-shared
previously-active SW RF is
version,
Depending
The BTS
reference on O&M
hardware processed
clock monitoring consistent
implementation,
too large.
version
fallback is
and notthe running in all HW has
previously-active units
SWin
antenna
detected line
a lossdevicesof the powered
ToP by the
reference
the
Problem
version BTS, and
is the
detected
is running BTS when
in all is not
HWthe up
response
units and
in the is not
Small Cell: RS485
clock
The IUANT,
signal
additional received or powered
info in from
the alarmby the
master
about
running
received
BTS. (recovery
or
Theline, response
BTSare is upSW is
and update
received
running. is still
with
-FSM antenna
clock.
difference in length outshould
of order. be multicast
delivered in
supported).
unsuccessful
Otherwise, thestatus for SRIO
previously-active SW
the alarm onlyrelated
configuration when LTE messages. is radio master.
version
NETCONF: is not running in all HW units in
4085:
the BTS, and the BTS is not up and
- BBMOD The
Transport
SRIO information
= Serial onconsists
SW RapidIO the source of: unit has
(high-performance
running
The (recovery SW
has update is still
- SMOD Theradio
-interconnect
indicated number module
the of
need physical
technology for
detected
a port onover-
software
between the
fallback.
DSPs).
supported).
current on the ALD port. Depending on
system
If BTS O&M module haswhere detected primary that thelink BTS
starts.
hardware
- Thestart number implementation,
of physical antenna
port on the line
can
4085: with the previously-active SW
devices
system module powered by the
where RS485, ortoo
secondary
version,
Transport BTS SW O&M
onantennaprocessed
the source consistent
powered
long/too by
short thelink starts. line,unit are has
out of
fallback
A fan delivered
indicated andthethe need previously-active
by an
for unknown
a software SW is
vendor
fallback.
RS485 port, RET, RAE, LNA order.
-detected
The difference inmodule
lengths with the
version is running
(system
If BTS O&M has detected that the BTS in all HW units
hardware in the
rel.2),
information
BTS.
or the The
fanwith BTSif
speed the is secondary
up and running.link is too
can start theispreviously-active
too low for successful SW
short
Otherwise,
detection. or tooAnotherlong.
the previously-active
detection SW
version, BTS O&M processedattempt consistent
-occurs
The difference
version is not in
running delays in all in HW units
fallbackafter and the the fan test timer expires
previously-active SWin
OptIF nanoseconds.
the BTS,
(systemismodule and the BTS
hardware is not up and
version running in all HWrel.3). units in the
running
BTS. The (recovery
BTS is(high SW
up and update
running. is still
A long
supported). distance latency) between
This faultand
Otherwise,
the FSM isthe
reported for
previously-active
antenna has both been operational
SW
detected,
and
version
but non-operational
is not running fans
the Distributed Site feature has not in allin hardware
HW units in
SMOD 4489:
detection
the BTS, phase
and the only.
BTS is not up and
been
The enabled
source unit (actDistributedSite
has requested =
running
False). For (recovery
FHCCof SW
modules, update thisisSWstill
fault that
fallback
supported). because a critical problem
means
occurred that therestart-up
during is a long after distance
the SW
between
update due the to FSM ASi and the
configuration customer's data
- CABLINK 4489:
device.
migration failure
The source unit has requested SW or corrupted ASi
configuration
fallback because data. of a critical problem that
If BTS O&M
occurred during start-up has detectedafter thatthe theSW BTS
- BBMOD can start
The temperature
update with the previously-active
due to ASiofconfiguration the FSP/ABIx SW
board
data
- SMOD version
has - BTS O&M processed
migration failure or corrupted ASi value.
exceeded the critical threshold consistent
fallback
configuration and: data.
The
1. thefans do not rotate as
previously-active SW requested
version isbut
If BTS O&M has
temperature is detected
high. that the BTS
running
can start in all HW units in the BTS SW
Fan
2. the notwith
is BTS running
is
up andalthough
running. the control is
SMOD version
higher - BTS
than 0. O&M processed consistent
Otherwise:
fallback and:
1.
1. the
previously-active SW SW version
version is is not
running in all HW
running in all HW units in the BTS units in the BTS
5G BTS, AirScale SBTS, Flexi SBTS: 2.
2. the
the BTS
BTS is is notup and up and running. running
- SMOD (recovery
Otherwise: SW update is still supported).
1. the previously-active SW version is not
running in all HW units in the BTS
5G BTS, AirScale SBTS, Flexi SBTS: 2. the BTS is not up and running
- SMOD (recovery SW update is still supported).
update due to ASi configuration data
migration failure or corrupted ASi
configuration data.
If BTS O&M has detected that the BTS
can start with the previously-active SW
version - BTS O&M processed consistent
fallback and:
1. the previously-active SW version is
Feature activation
running in is missing.
all HW units in the BTS
actRfChaining
2. the BTS is upis and
equal to false in the
running.
RMOD SCF.
Otherwise:
1. the previously-active SW version is not
running in all HW units in the BTS
5G BTS, AirScale SBTS, Flexi SBTS: 2. the BTS is not up and running
Flexi BTS TDD, AirScale BTS TDD, AirScale The file system access operations like file
BTS FDD: system mounting or file opening have
- SMOD failed.
The BTS has detected that an RF module

The Radio Module
connected has detected
to the system module low
is
- LNCELL downlink carrier input power fromand
affected by a power cycle failure the
- NRCEL System Module.
other additional actions performed by the
BTS during reset. Therefore, the BTS
reset lasts longer. This fault notifies the
operator that the BTS reset will be
SMOD extended.
During SW update, the configurations of
the active and passive SW in the HW unit
have been detected to be the same.
- BBMOD The summing
Active service
and passive SWdefault
configurations are
- SMOD configuration has failed.
compared at these periods:
- before SW download
- during SW activation, before active and
passive SW switch
FSP - during start-up
Power feeding for the given radio module
has been remotely switched off using
BTS Element Manager, using front panel
PWRMOD (FPFH only), or WebUI (FPFH only).
Synchronization is lost when the system

- CABLINK The master
module systemas
is working module has lost
a synchronization
- RMOD optical or sync connection to the peer
slave system module. This usually
- SMOD_EXT system module.
indicates that a synchronization master
system module has been reset, or that
there is a problem with the optical cable
- SMOD between the master system module and
-5G
CABLINK
BTS, AirScale BTS FDD, AirScale BTS the slave system module.
- GNSSE The fault indicates poor GPS antenna
- GNSSI installation.
- GNSSE The GPS receiver is running a site/self

- GNSSI survey.
- GNSSE There is no accurate position stored in

- GNSSI the EEPROM.
The feeding voltage is disabled for the
selected antenna line.
If the antenna port or RS485 port are

supplying DC to a configured antenna line
device, the alarm source is RETU, LNA,
or RAEU.
- GNSSE The
The receiver
HDLC link is has
usedbeenin stored position
disabled but
for the
- GNSSI If
hasthe port
been is not
moved providing
to a new DC to any
position.
reporting Antenna Line or IUANT port.
configured antenna line device, the alarm
The
sourceGPS receiver has
is Antenna detected that one
If
orthe
moreantenna
EEPROM port Line or RS485
or RS485
segments port port.
wereare
- GNSSE detected,
corrupted or are supposed to
to be
be detected
The
per alarmat is reset
commissioning
and had
not raised
of against
the
set to
antenna line
-- GNSSI
ANTL their factory
uncommissioned default settings.
device, the alarm antenna
source isline devices.
RETU, LNA or
- RSL RAEU. The antenna line device may be
- RETU LNA can have more
commissioned than one power
or uncommissioned.
- LNA source and can still be powered up even
-ANTL
RAEU with
If thean alarm raised
antenna port oragainst
RS485 it.port was not
RSL detected, or was not supposed to be
RETU detected per commissioning of an
LNA antenna line device, the alarm source is
RAEU Antenna Line or RS485 port.
The system module is expected to

5G BTS, AirScale SBTS, Flexi SBTS: SW file validation
operate against
in the phase its signature
synchronization
- SMOD has failed.
mode according to the BTS configuration,
but the phase reference source didn't
become available during a waiting period
within the start-up procedure, or has been
SMOD lost during fallback mode.
The synchronization source of the BTS is

not available when it works as
- SMOD synchronization slave during start-up.
Gathering logs from the unit has failed,
and one or more log files from a particular
RF module is not available in the BTS
RMOD snapshot.
The Ir router has reported a major
problem with TD-SCDMA. The TD-LTE
performance is affected, and cells are
- SMOD disabled.
The Ir router has reported a minor alarm

that is caused by TD-SCDMA. TD-LTE
- SMOD performance might be affected.
The shared OptIF mode cannot be read

- BBMOD from or changed in the FBBC card.
The Flexi Zone Micro BTS, Flexi Zone
Access Point, or Flexi Zone SFN Antenna
Small Cell: detects that configuration reset has been
-FSM invoked.
The temperature of the Flexi Zone Micro
BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna has exceeded the
FSP predefined threshold.
Zone SFN Antenna has exceeded the
FSP thresholds for operation.
Zone SFN Antenna is not in the specified
FSP range for operation during startup.
The validated sensor temperature on the

PA is higher than the predefined HW
FSP temperature.
The Timing
Access Point,over
or Packet
Flexi Zone (ToP)SFNfrequency
Antenna
adjustment is nearing its tuning
has been operating in the synchronizationlimit. The
Small Cell: DFS frequency
holdover offset is within
mode (because 5% of its
of a continued
-FSM minimum or maximum supported
loss of all configured synchronization range.
reference sources) for a period beyond
which the carrier frequency accuracy or
phase alignment requirements can be
FSP guaranteed.
Flexi Zone Micro, Flexi Zone Access
Point, Flexi Zone SFN Antenna:
Some of the generated
The connection to the RP1 system clock
Transport
signals are missing, or the
(TRSW) or Radio Frequency (RFSW) generated
FSP system
interfaceclocks are not
has been lost.locked.
Flexi Zone Controller:

The connection to RP1 Transport
FSP (TRSW) interface has been lost.
The potential power down condition of the

Flexi Zone Micro BTS or Flexi Zone
FSP Access
A failurePoint.
has occurred in the connection
Flexi SBTS, AirScale SBTS, Flexi BTS FDD, to the configured Real-time Performance
Flexi BTS TDD, AirScale BTS TDD, AirScale Management
The reference(RTPM) entity, foron
clock monitoring example,
the
BTS FDD: the Traffica Network Element Server
Slave Flexi Zone Micro BTS or Flexi Zone
- MRBTS (TNES).
Access Point board has detected a loss
of
5GMaster
BTS: or Slave 1PPS reference clock
signal received
The radio master from the Master
is either missingFlexi
at
Zone Micro
start-up or isBTS
lost or
at Flexi Zone Access
run-time.
FSP Point board.
The radio slave waits for a user-defined
amount of time for the radio master to
become available again before taking a
Flexi SBTS, AirScale SBTS: temporary
The RROMradio TRSmaster role. or
IP configuring
- LNBTS An alarm due has
reconfiguring to the fault is reported when
failed.
the radio master is not available after the
user-defined amount of time, and the
External GPS/GNSS
slave takes a temporary receiver
radio module
master has
lost
role.satellite visibility and is currently
GNSSE operating in a holdover mode.
AirScale BTS FDD, AirScale SBTS, Flexi
BTS FDD, Flexi SBTS:
RF Module is controlled by a Radio Slave
RMOD in Temporary Master role.
An antenna line or antenna line device is
not properly configured.
The antenna line setup and device scan
fails
During because of exceeded
BTS startup or BTStime limit or
too many ALDs detected
recomissioning, the BTSOAM from has
the ALD
port.
detected that:
The
- for radio module
TDD 8T8R reports
cell on CPRIthe RU
faultorwhen
TDD
- RMOD the antenna line starts.
mMIMO cell on CPRI MAA: there are
- LNA wrong combination of values for the
- RAEU beam-forming
The radio module cell indicated
parametersan error upon
- RETU "tddSpecSubfConf",
execution of MHA, RET, RAE related
- RMOD "rxCalibrationConfiguration",
logical operation.
"actReduceWimaxInterference" for the
The
usedradio slave system
beam-forming module
radio module.cannot
use
- For TDD mMIMO cell on CPRI orradio
the shared radio because the eCPRI
master system
MAA: sector module hasprofile
beamforming not provided
defineda
- RMOD reference
for the cellclock
underto the shared radio.
LNCEL_TDD::mMimoSectorBFProfName
is not supported or missing for the
detected radio and configured
- LNCEL LNCEL_TDD::mMimoAntArrayMode.
The
FiberRadio
DelayModule has detected
and Antenna Round switch
Trip
- RMOD configuration mismatch on thecapability
Delay exceeds the supported ALD port.of
the BTS.
- LNCELL For 5G this fault is raised when the fiber
- NRCELL length difference is higher than can be
- RMOD supported by the RU hardware.
The Flexi Zone Controller or Flexi Zone
Micro/Flexi Zone Access Point has failed
The Z1 link the
to upgrade between the respectively
software Flexi Zone on
Controller
the Flexi Zone Access Point orAccess
and the Flexi Zone Flexi Zone
-FSM Point is out of because
SFN Antenna service. of an HTTPD
server configuration error, an error during
startup, or some other internal failure at
Small Cell: the Flexi Zone Access Point or Flexi Zone
-FSM SFN Antenna.
The Flexi Zone Access Point is blocked
by the BTS Site Manager. This is done to
avoid fault indications that might be
raised during a Flexi Zone Access Point
-FSM maintenance task.
The cell state audit detected that the cell
was unintentionally deactivated without
warning. The symptom data is
LNCEL automatically collected.
The Flexi Zone AP is out of order

SRIO
becauselinkoffailure has been detected by
a configuration
- CABINET There
the NE.has been a failure to problem,
validate the
which prevents
software releasethe FZAP from
signature coming
for the
into service. This fault is only
software release that has just been reported for
non-fatal SW errors, that is,
requested to be downloaded to the BTS the Flexi
Small Cell: Zone
systemController
module. SW Thiscan still provide
is because the
-FSM service to other FZAPs
information of either the Hash in this zone.
Container
5G BTS, AirScale BTS FDD, AirScale BTS file or the Hash Container Signature file is
TDD, AirScale SBTS, Flexi BTS FDD, Flexi not present in the downloaded
BTS TDD, Flexi SBTS: TargetBD.xml, or the verification of the
- SMOD software signature files has failed.
There has been a failure to validate the
hash of the questioned SW files for FCT
except of the Hash Container file or the
Hash Container Signature file in the
software release that has just been
requested to be downloaded to the BTS
5G BTS, AirScale BTS FDD, AirScale BTS system module. This is because the hash
TDD, AirScale SBTS, Flexi BTS FDD, Flexi value of the questioned SW file is
BTS TDD, Flexi SBTS: missing, or the BTSOM fails to verify the
- SMOD hash of the questioned
An unsigned SW file.has been
software release
5G BTS, AirScale BTS FDD, AirScale BTS downloaded to a BTS system module that
TDD, AirScale SBTS, Flexi BTS FDD, Flexi is currently
There running
has been a software
a failure release
to validate the
BTS TDD, Flexi SBTS: that implements software signature
software signature for the software
- SMOD checking.
release that has been requested to be
5G BTS, AirScale BTS FDD, AirScale BTS downloaded to the BTS system module
TDD, AirScale SBTS, Flexi BTS FDD, Flexi because there is no software signature
BTS TDD, Flexi SBTS: for the release, and only signed software
- SMOD can
The beMHAinstalled.
was unexpectedly set to
- LNA bypass mode. The fault might be the
- RMOD result of a conflict in MHA management
- RAEU for a device that can be managed from
- RETU more than one BTS at the same time.
FR functions that are not critical for cell
setup are not supported or are not
configured
A software correctly.
update of The the GPSreason or for
GNSS this
FR might
The be an incompatible
transmission delay RFSW
difference
receiver could not be done by the BTS. version.
between
The GPSthe radio module
or GNSS receiverthat needs to
works
be compensated,
correctly but it hasand the radio module
an incompatible
- GNSSE with the maximum
software version transmission
according to thedelay, is
The
bigger Flexi
thanZone Micro
thethat
capacity BTS/Flexi
of the Zone
- GNSSI software
Access build
Point/Flexi is
ZoneloadedSFN to the
AntennaBTS.
compensation buffers. This fault is
has encountered a significant
reported for the maximum transmission
synchronization
delay radio module. alignment fault requiring
that
The transmission delaya includes
the BTS undergo reset to restore
the delay
FSP proper operation in a
in the optical modules of both timely fashion.
the system
module and radio modules, the delay in
the optical fibers and forward delay of the
previous hop radio modules, and the
RMOD RFM/FHS
internal delay product
of theauthorization
radio module. has
failed because of missing RFM/FHS
properties. RFM/FHS is not supported by
The length of
the current BTS thesoftware
optical cablerelease,between
and the
the system module and
BTS did not find relevant hardware the radio module
- RMOD is too long.for the RF module on FSM.
properties
The
The BTS failed
Location to retrieve
Lock has failed. the
corresponding RFM/FHS plug-in module
- FHS from
1. The the Network
BTS was not Management
able to acquire System
- RMOD as well. Lock evidence data after feature
Location
activation. Depending on the configured
- LNA detection methods:the inability to identify
- LNBTS This fault denotes
-the
The BTSbased
FZAP might on time the out while waiting for
information
- LNCELL GNSS coordinates.
-FSM
- RAEU provisioned in APMOD.
- The following network parameters are
- RETU not available: IP address of the first
- BBMOD routing hop, physical subnet address of
- RMOD The detected
the BTS, or MAC hardware
address does not first
of the support
- SMOD the SCF configuration.
routing hop.
2. The BTS has failed to update the

Small Cell: Location Lock evidence file because of a
-FSM flash file system error.
address of the first routing hop) do not
match the values that are stored in the
Location Lock evidence file.
The integrity check of the Location Lock

evidence data has failed after a BTS
reboot.
1. The Location Lock evidence file is
missing.
Small Cell: 2.
AnThe
SWLocation
interfaceLock evidence file
incompatibility hashas
been
-FSM failed P7 signature validation.
detected between an eNB and other
eNBs related by inter-site or inter-eNB
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS Carrier Aggregation
An incorrect relation,
configuration which
of inter-site
TDD, AirScale BTS FDD: prevents the inter-site or inter-eNB
Carrier Aggregation cluster has been Carrier
- LNBTS Aggregation feature from being
detected between an eNB and other enabled.
eNBs related by inter-site Carrier
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS Aggregation relation, which prevents the
TDD, AirScale BTS FDD: inter-site
A dedicatedCarrier Aggregation
link between feature
an eNB andfrom
- LNBTS being enabled.
other eNBs related by inter-site Carrier
Aggregation relation cannot be
AirScale BTS FDD/TDD, Flexi BTS FDD, Flexi established, which prevents the inter-site
BTS TDD: Carrier Aggregation feature from being
- LNBTS enabled.
There is no available X2 link between an
eNB and other eNBs related by inter-site
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS Carrier Aggregation relation, which
TDD, AirScale BTS FDD: prevents the inter-site Carrier
- LNBTS Aggregation feature from being enabled.
AirScale SBTS, Flexi SBTS: CAPLIM The IP traffic of the user is throttled
(LICENSE CAPACITY LIMITATION) because of a missing license.
Small Cell: Communication on all S1 links and OAM

-FSM link has been lost.
The BTS has detected an incompatible

operator-selected constellation mode for
-FSM the GNSS receiver.
Connection to NTP (Network Time

SMOD Protocol) server is lost.
ToP (Timing over Packet) signal is

5G BTS:
- SMOD unavailable
SynchronousorEthernet
unusableisas the reference
unavailable or
- RMOD clock source.
unusable as reference clock source.
AirScale SBTS, Flexi SBTS:

The cableport
Ethernet used between as
configured theasystem
SyncE
SYNCE module
referenceand the operational.
is not radio module exceeds
the maximum supported length for micro
DTX (the maximum supported link delay
is 80 us; if the radio module is directly
PDH is unavailable
connected or unusable
to the system moduleasor the
FCT reference clock source.
extension baseband module, the longest
supported cable length is approximately
16 km). The BTS power saving (that is,
- CABLINK the micro DTX functionality) can no
- LNCEL longer be provided.
The fault indicates that the configured
FCT inter-eNB FDD-TDD carrier aggregation is
LCR not working.
The micro DTX configuration in a radio

RMOD module has failed.
The RP30-1 connection between the
system module and the radio module, or
between an extension baseband module
(FBBx/ABIx) and the radio module, is not
OptIF stable at 6 Gbps.
The RP30-1 connection between the
system module and radio module, or
between the extension baseband module
(FBBx) and the radio module, is not
OptIF stable at 3 Gbps.
The affected FZAPs/SFN ANTs failed to

Small Cell: accept the latest service (toor4nsn)
-FSM account password update.
This fault indicates that the Radio
Interface Based Synchronization (RIBS)
Small Cell: is not available, and is operating in
-FSM synchronization holdover
This fault indicates mode.
that the absolute
phase error between the Oven Controlled
Oscillator (OCXO) output and the
reference phase provided by the CPRI Ir
- SMOD interface exceeds the limit of 50ns.
New configuration
The target file Access
Flexi Zone has been rejected
Point
Airscale SBTS: FCT (HW rel.4), FlexiSBTS: and M-Plane connection is established
(FZAP) has not yet been successfully
FCT (HW rel.3) with fallback
connected toconfiguration.
the Flexi Zone Controller
(FZC). This might mean that the physical
FZAP does not exist, or an FZAP or FZC
fault prevents the FZAP from successfully
-FSM connecting to the FZC.
The BTS has detected that the GNSS

- GNSSE receiver does not support the operator-
- GNSSI selected manual location entry.
Free memory on the radio module is

- RMOD limited.
- RMOD The radio module has no free memory.

The LTE time on the Flexi Zone
Controller is out of sync and might not be
accurate. As a result, the MBMS service
-FSM is disabled on the Flexi Zone Controller.
AirScale BTS TDD, AirScale BTS FDD,
Previously downloaded plan[Id] was
overwritten by a new plan[Id].
DSP U-plane computing environment
- BBMOD The serial
startup hasconsole
failed. is activated in the
- SMOD BTS.
The fault will be triggered following the
DSP U-plane computing environment
scenario:
covers
1. BTS U-plane applications
is operating with planand real-time
X (id=x)
- BBMOD platform services on DSP cores and MCU
activated.
- SMOD cores.
2. Customer downloads new plan Y
(id=y),
The BTS butenters
the activation
capacityprocedure
limited mode is
postponed.
due to missing licenses. Calls from
3. Customer
excess usersdownloads newer
will be rejected plan Zfor
except
CAPLIML (LICENSE CAPACITY LIMITATION) (id=z)
handoverwhich
andoverwrites
emergencypreviously
calls.
downloaded plan Y, triggering:
An error has been detected
-> alarm-notification during
is reported the
to the
Small Cell: start-up or normal run-time operation
Customer, informing about plan Y being of
-FSM the 2CE virtual container.
overwritten by plan Z.
This allows Customer to verify whether

overwriting was intentional or not (e.g.
MRBTS due to an error).
- BBMOD
- SMOD An FSP sub-unit is unavailable (lost).
The optical interface is not operating at

the maximum speed. Not all cell
- CABLINK configurations are supported.
The Z3 link between the Flexi Zone Micro

Small Cell: BTS, or Flexi Zone Access Point, and the
-FSM The
Flexitarget
Zone SFN
SFN Antenna
Antenna has not
is out ofyet been
service.
successfully connected to the Flexi Zone
Micro BTS or Flexi Zone Access Point.
This
This denotes the that
might mean inability
the to identifySFN
physical the
Small Cell: SFN Antenna based on the information
Antenna does not exist; or an SFN
-FSM provisioned in ANTMOD
Antenna fault, Flexi Zoneor APANTMOD.
Micro BTS fault,
or Flexi Zone Access Point fault prevents
the SFN Antenna from successfully
Small Cell: connecting to the Flexi Zone Micro or
-FSM Flexi ZoneZone
The Flexi Access
SFN Point.
Antenna is blocked
by the BTS Site Manager or WebUI. This
is done to avoid fault indications that
Small Cell: BTS
mightisbe
configured or shall
raised during be configured
an SFN Antenna
-FSM to dual core mode.
maintenance task. However, the
extension unit cannot be reached via
internal communication.
The
The cell
faultisisshut down
raised because
in case it occupies
of connection
baseband capacity that is over
issues between the core units, or thewhile
- LNCEL licensed limit.
commissioning, or Startup when the
planned secondary unit cannot be
reached or is already commissioned to
single eNB or is commissioned as primary
SMOD core.
The Flexi Zone Micro BTS or Flexi Zone
Small Cell: Access Point failed to register the Flexi
-FSM Zone SFN Antenna.

Small Cell: Access Point failed to setup the cell on
-FSM the Flexi Zone SFN Antenna.

Small Cell: Access Point failed to delete the cell on
-FSM the Flexi Zone SFN Antenna.

Small Cell: Access Point failed to shut down the cell
-FSM on the Flexi Zone SFN Antenna.

Small Cell: Access Point failed to reconfigure the cell
-FSM on the Flexi Zone SFN Antenna.
The Flexi Zone SFN Antenna is out of
order because of a configuration problem,
which prevents the Flexi Zone SFN
Small Cell: SFN
AntennaMaster
fromPhyProxy module
coming into service. This
-FSP initialization has failed.
fault is only reported for non-fatal SW
errors, that is, the Flexi Zone Micro BTS
or Flexi Zone Access Point SW can still
provide service to other Flexi Zone SFN
-FSM Antennas.
BTS shall work in dual core mode

operation. However, the configuration of
Small Cell: The cell using SFN
the secondary unit isresources is disabled
inconsistent with
-FSM since the feature actSfn is set
configuration of the primary unit. to "false".
This fault is raised in AirScale + FSMF /
AirScale configuration when both cores
are configured as primary units in dual
- MRBTS core mode.
Power feeding for the given radio module

has been switched off by the user from
PWRMOD the front panel of the PDU.
The Ethernet connection between the

primary and secondary system module
SMOD does not work.
LTE BTS is connected to more than one
peer system modules, but one of the peer
system modules does not support
- SMOD_EXT multiple radio sharing.
The shared radio module connected to
the BTS is using the same IP addresses
as other shared radio module connected
- RMOD to the same BTS.
following invalid configurations is
detected:
1.1. The LTE eNB is in stand-alone mode
and the CDMA BTS is in any mode.
1.2. The LTE eNB is in any mode and the
CDMA BTS is in stand-alone mode.
1.3. The LTE eNB and CDMA BTS are
The
both peer system module
in secondary mode. connected to
the BTS
2. If the is
alarm using the same IP addresses
This alarm will additional
be raised information
if inter-RAT
as other peer
contains system
"Incorrect module connected
secondary functions
(LTE-GSM / WCDMA-GSM / LTE-
SMOD_EXT to the same BTS.
configuration for CPRI-A RF Sharing",
WCDMA) RX (UL) or TX (DL) frequency
thenisthe
that LTE eNBinisthe
configured operating
same SBTS in a is
secondary mode, and the SW and/or
overlapping.
AISG management functions is owned by
FR the
TheCDMA
Note: baseband BTS.or C-Plane pool resources
1.
areThere will be no
not available foralarm
a new with fault 4387
or relocated
in case
cell. TheofBTS Dynamic Sharedtries
periodically Spectrum
to find and
feature
allocateisbaseband
activatedor between
C-PlaneGSM and
resources
LCR LTE
to or
the cell.between GSM and WCDMA,
The
whenbaseband
the pairedorGSM C-plane sector dynamic pool
frequencies
resources for a new
overlap with peer RAT dedicated or reallocated cell
are permanently
spectrum. Alarm not withavailable.
fault 2421All is
attempts
reported for to find the resources
the overlapping in for
DSS thecase.
cell
LCR have failed.
2. Overlapping is reported if any cell
- LNBTS transmit
A virtual spectrum
node (software is overlapped
container) bywithin
- NRBTS another
the BTS RAT
has cell/sector.
stopped
Positioning service offered by OTDOA workingE.g. In
or LTE cell
failed to
- WNBTS case
start. If
Theonly guard
symptom banddata
(Observed Time Difference Of Arrival) is
is overlapped
automatically or
- SMOD only blanked
collected when PRBs are overlapped the
feature
BTS hasislost
overlapping thepossible.
unusable.
fault 1PPS
is
PRS
not
(Positioning
reference
reported. signal
Reference
at the 1PPS/ToD Signal)backplane
transmission required
3.
forAlarm
feature with the fault
OTDOA 4387 isinterface.
is disabled. reported
In a
only dual core
for cellsofthat configuration,
share where
SMOD (secondary unit in dual core The reason
backplane sync the failureatmay
between
leastbeone
cores
TX or
iseither
used, of
RX
the antenna port on radio
following: is lost by secondary core. module.
configuration) synchronization
4.
1. For
The WCDMA-GSM
BTS falls back case (that overlapping
is, the BTS is
alarm
currently synchronizedwhen
is reported only to a sync detectedinputin
- BTS RX(UL).
The source For LTE-another
unit
source not allowed for OTDOAhas requested RAT alarm
SW with
- LNCEL overlapping
fallback
operation). becausefault 4387
of a is reported
critical problem both for
that
- WCEL TX(DL)
occurred
2. If BTS and RX(UL).
during
is working RAT start-up
in holdover after the
mode, the
Cell is disabled because the "Reduced
RAT SW update.
estimated
LTE Guard phase
Band"error feature exceedsis enabled the but
If BTS O&MRF has
otdoaPhaseErrorThreshold
the related detected
module does thatofnot the
the BTSthis
last
have
can
sync start
input
capability. with the
source previously-active
allowed for OTDOA SW
LNBTS version
operation. - BTS O&M processed consistent
BTS hasand:
fallback lost connection to the BTS
Scenario
Mediator. A: The "Reduced LTE Guard
1. The is
Band" previously-active
activated, but the SW version isRF
referenced
BTS
running Mediator
in all HW is aunits
unit responsible
in the BTS. for
module
BTS does nottohave
connection the this capability.
Network
2. The BTS is up and running.
- Session Management
Otherwise: System (e.g. NetAct).
Scenario B: The "Reduced LTE Guard
1. The is
Band" previously-active
activated, and the SWRF version
module is
not running in all HW units
has this capability, but the configured in the BTS.
2. The BTSoffset
frequency is notexceeds
up and running its capability.
During cell start-up, cell report critical fault
"Configuration
The link between andeNB
RF and
Module mismatch
other eNB
for Reduced LTE Guard Band" and set
related by Inter-Site Carrier Aggregation
- LNCEL cell operability
relation to 'cell faulty'.
The cellsisare
unstable, which
disabled afterprevents
a the
Inter-Site Carrier Aggregation
preconfigured time period due to thefeature
from beingshutdown
intelligent enabled. procedure.
The Inter-Site Carrier
Small Cell: Aggregation
The fault is also reported also
feature may whenbe the BTS
-FSM degraded.
power supply is available again, but not
all cells are enabled yet. When all
previously shut down cells are enabled
again, the alarm due to this fault is
MRBTS cleared.
timeout.
- the estimated time error exceeds the
allowable LTE limit for loose Hyper-SFN
sync.
- there is a 96-hour timeout after losing all
phase sync sources, and no local
holdover is possible.
In
The SHS
radioPhase
moduleSync mode, disabled
remains as Sync Hub
Slave,
because theBTS
faultOAM
is triggered
could not when:
assign IP
FR -address
during start-up,
to the radiothe module.
System Module has
still no time information after a 5-minute
timeout.
The
- thefault indicates
estimated timethat theexceeds
error user hasthe
blocked one
allowable LTE orlimit
more forGSM
looseTRX of the cell
Hyper-SFN
- BTS using
sync. the BTS Element Manager.
-This
there is aindicates
fault 96-hour thattimeout after a poor
the absolute
time
valueaccuracy indication
of an estimated is received
phase error offrom
a
sync hub master.
BTS which is in holdover has increased
FCT -more
therethan
is a limit
96-hour
set by timeout
BSC. after losing
the SHM link, and no local holdover is
possible.
- BBMOD The configuration
In the of SRIO
runtime cases, (serial rapid
appearance of the
- SMOD IO) routes failed.
fault depends on the status of features
requiring Hyper-SFN synchronization
accuracy (eDRX). The fault is raised only
AirScale SBTS, Flexi SBTS: if the mentioned features are enabled on
SMOD at least one supported cell.
TDD, AirScale SBTS, Flexi BTS FDD, Flexi The BTS is unable to retrieve sufficiently
BTS TDD, Flexi SBTS: accurate time information from any time
- SMOD source within a given time interval.
The fault indicates that the one or more
TRXes in the sector are not on-air at BSC
since System Information is not delivered
- BTS from BSC to TRX.
The Radio Module is not able to configure

- RMOD the commissioned front end gain.
An error was encountered while
measuring the antenna delay, or the
measured delay value does not fall within
- CABLINK the 1 to 500 ns range limit.
The value of the parameter
"IPNO:cPlaneIpAddress",
"IPNO:cPlaneIpv6Address",
Reported value of 'Leap Seconds'
"IPNO:uPlaneIpAddress", or is not
- Flexi Zone Controller Thesame
the optional
on power
all group
Flexi Zoneshutdown
Access Points.
"IPNO:uPlaneIpv6Address" does not
procedure has failed. As a consequence,
match the one
a baseband configured
card in RCP.
did not enter into energy
Each mismatch parameter will raise
savings mode and it still offers full this
Fault with
capacity. specific additional info of the
-FSM parameter.
Power Group is a set of Digital Signalling
Processors (DSP) or System on Chip
(SoC) on the baseband card, which is
- BBMOD powered up independently from other
- SMOD sets of DSPs/SoCs.
- GNSSE The BTS is downloading the firmware

- GNSSI binary to the GNSS receiver.
This fault indicates that the absolute
phase error of the BTS exceeds the limit
of 1.5 us. This can occur when:
LTE BTS (SBTS) can't provide IP address
1) TheFHS
of the absolute value
towards LTEof BTS (SBTS)
measured/estimated
network to NR BTS inphase error of the
NR-LTE/NR-SRAN
FHS BTS has exceeded
OBSAI RF sharing. the limit of 1.5 us,
OR
The BTS fails to configure the internal
baseband
2) The BTSforhas a cell.
lost all phase sync
LCR RP3Streamer
reference sources,configuration
but doesfailed.
not have
sufficient history data for holdover.
OR
This fault indicates the depletion of the S-
3) TheIPBTS
Plane is synchronized
Address to be used by for reference
the new
-FSM which
FZAP has
to be capability
connected. to internal holdover
The
(Syncreference clock monitoring
Hub Master/GNSS) whichhas reports
detected that phase error
the phase error of the provided of a reference
sync
signal
signal.from
The the external
absolute valueGNSS receiver
of estimated
GNSSE exceeds
total phase error in the "slave" sideGNSS
150us, and resets to the
GNSSI receiver
exceeds do not resolve the or
problem.
A CPRI-Athe limit
radio of 1.5
has oneusof thesource
following
reports that itsconnection:
unsupported holdover has expired.
- A CPRI-A radio is connected to a
SMOD Note : In case
baseband of Dual
module Core,
while the fault
the FHS Delay
NRBTS applies to each Core.
Compensation feature is enabled
5G
- BTS, AirScale
A CPRI-A BTS
radio FDD, AirScale
is connected to the
BTS TDD, AirScale
while the Fiber SBTS, Flexi BTS
Link Length
FDD, Flexifeature
Extension BTS TDD, Flexi SBTS:
is enabled but the FHS
- RMOD One
DelayorCompensation
more of the BTS user is
feature accounts
disabled.
has a default password.
5G BTS, AirScale BTS FDD, AirScale BTS This applies to the following BTS user
TDD, AirScale SBTS, Flexi BTS FDD, Flexi Update
accounts: to the configuration of SSH logins
BTS TDD, Flexi SBTS: or the SSH Port number
- Local Operator System to the BTS
Administrator
SECADM platform
(Nemuadmin)has failed.
5G BTS, AirScale BTS FDD, AirScale BTS - Root Service User (toor4nsn)
TDD, AirScale SBTS, Flexi BTS FDD, Flexi - Non-root Service User (serviceuser)
BTS TDD, Flexi SBTS: - Data Collection User (dcuser) [not
- MRBTS applicable in 5G BTS]
A cell is considered as a sleeping cell due

LCR to degraded RRC success rate.
The amount of PIM being measured by
the
TheEPIMC
BTS has is above
detected theone
user-defined
or more
Minor threshold
conflicts outlinedbut has in
below not reached
the the
BTS hotel
- ANTL Major threshold.
configuration. They make inter eNB UL
CoMP feature operation fully or partially
The External PIM Cancellation feature
impossible:
The amount
activation flagof isPIM being measured by
-the
Connection
EPIMC is to aset
above
to true
hotel
the
at EPIMC,
member that
user-defined
and the total
belongs to thenumber of RX
other BTS channels
hotel is
- ANTL Major
targetedthreshold.
for External PIM Cancelation
detected,
exceeds
- Connectionthe limit
to a that
hotelcan be supported
member that has
by
a duplicated hotel membercase
the EPIMC HW unit. In ID hasthebeen
EPIMC
detected, HW unit is "AFAA" type, the level
- EPIMC of
- The numberisof
HW limits 24detected
RX channels
hotel in total.
members
in the BTS hotel does not match the
configured expected number,
- Primary 10GE connection is not
SMOD_EXT available.
had occurred during start-up after the SW
update due to configuration data
migration failure, or the SCF check tool in
BTS OM has detected SCF failure and
the BTS cannot operate with that SCF.
BTS detected
can start with the thatpreviously-active
the UL CoMP related SW
communication
version, BTS O&M processed between BTS cannot
consistent be
established
fallback andistheover one or more
previously-active 10GE links
SW has
eNB,
due which
to: a part of the BTS hotel,
version
detected is10GErunning in all HWloss
connection units(primary
in the
1)
BTS.incompatible
The BTS issoftware
upinand installed on both
running.
SMOD_EXT and/or
BTS secondary)
that caused the the BTS
inter eNBhotel.
Otherwise, the previously-active SW
communication
version
This fault is is notraisedfailure
running when in all
theHW units in
southbound
2)
the failure
BTS,
logical in
and
interface L2/L3
theisBTSaddress is not
configured assignments
up and
(LTE4565
3) wrong
running
activated) switch
(recovery
but configuration
LTE2371SW update Flexi (e.g.
is still
Zone
SMOD_EXT There
mistake is ina mismatch
VLAN assignment)between
supported).
Controller Shared Backhaul Support(BSC -
configuration on BTS and controller
Phase
or RNC). II is not activated. This is an invalid
4085:
configuration, which does not allow
Transport
establishment SW on theZ1
of the source
links unit has
BTS commissioning does notbetween
match the
-FSM indicated
FZC and the need for a software fallback.
FZAPs.
configuration of the controller (BSC or
RNC). i.e. bands commissioned for the
can start with the previously-active SW
cell on BTS do not match bands
version, BTS O&M processed consistent
configured for corresponding sector/cell in
fallback and the previously-active SW
LCR, WCEL, BTS(Sector) BSC or RNC.
version is running in all HW units in the
BTS. The BTS is up and running.
An increased
Otherwise, thebitpreviously-active
error rate (BER)SW has
been detected
version is not runningin the received
in all HWCPRI units in
SFP signal
the on and
BTS, the optical
the BTS connector.
is not up and
running (recovery SW update is still
supported).
Configuration of ICOM route failed on
- BBMOD 4489:
AirScale module.
The
The antennas'
source unitassignmenthas requested for the
SWcell is
not available
fallback
Failure was because due
detected to reasons
of a incritical such
problem
the antennas as lack
that
of
assigned to the cell. It could be due or
configuration
occurred during or misconfiguration
start-up after the SW to
reset
one oftrigger
update viaASi
duefollowing
the to ASiManager.
(1) FPGAThis
configuration data
image fault is
load
LCR only applicable
migration failure to
or a cell using
corrupted
to ASiR-pRRH is in progress, (2) a ASIRMOD.
ASi
configuration
hardware issue, data.(3) configuration issue or
If
(4)BTS O&M has
reset/block of detected
an antenna thatperformed
the BTS
can start
via the with the previously-active
ASiManager. This fault is only SW
LCR version - BTS O&M processed
applicable to a cell using ASIRMOD. consistent
fallback and:
1. the previously-active SW version is
running
AirScale inBTS all HW
FDD: units in the BTS
The
2. DC configuration of the LNA is
LNA There are not enoughrunning.
the
incorrect
BTS is up and Wi-Fi channels
Otherwise:
enabled in the BTS configuration for LAA
1. the previously-active
cell(s). In SW version is not
running in all HW
MRBTS/LNBTS/LNBTS_FDD/LAA/LNUPunits in the BTS
5G BTS, AirScale SBTS, Flexi SBTS: 2. the BTS is not up and
R.uCellChannelSList, in each sub band running
- SMOD (recovery
allowed inSW the update
countryisofstill supported).
operation
number of subsequent selected channels
("1"s) is lower than number of LAA cells
configured on single radio and assigned
LCR to the LNUPR instance.
The detected radio module does not
match the SCF configuration. An
ASIRMOD is detected but it is configured
RMOD as RMOD or vice versa.
BTS requests RF Scan Collector to

perform an RF Scan Test. RF Scan
FCT Collector rejected this request.
Radio rejected BTS’s request to start RF
FR Scan Test.
BTS does not receive response from RF

FCT Scan Collector.
BTS failed to upload the RF Sniffing Data

FCT towards the RF Scan Collector.
This fault notifies the operator that the
OAM has detected a configuration
change
AirScalethatBTSrequires
FDD: DU restart in order
NRDU to be
pMaxLaa taken into use.
calculated
AirScale BTS FDD: by system for LAA
cell(s)
1. Radio formodule
each allowed sub band
configured of band
to support
46
LAA is lower
cell(s) than minimum
is not operationalpower
in level
Detected
supported RFby modules
radio connections
module configuredare
lteUItuRegion
not supported. calculated by eNB basedto
LCR support the LAA
on configured mcccell(s).
(mobile country code).
2. Sub band
Mix of TDD and FDD46B and/or 46C is enabled
in
(GSM/WCDMA/LTE) and radio
uCellChannelSList but mMIMOmodule
and
does not support DFS
non-mMIMO connections to one and no other sub
LCR band is allowed for the LAA
baseband module is not supported. cell.
Radio module connection to both ABIA

AirScale SBTS: and ABIC at the same time is not
- Radio Module supported.
After an RU crash, RU has collected

crash logs. The fault is applicable only for
RMOD radios that are used by 5G cells.
Radio interface on TD-LTE cells is

SMOD
Flexi Zone Micro: disabled.
- Flexi Zone BTS The CBRS power level (which means
maxEirp calculated by eNB for a CBSD
AirScale BTS TDD: cell based on the site configuration file)
- CBSD violates the FCC limitation.
FPFH Power distribution unit (PDU) setup

has failed, as it is incorrectly connected to
FCT the secondary core of a dual core BTS.
Procedures related to plan management

or configuration management fails in C-
NRBTS Plane.
The 5G cell update procedure rejected by

NRCELL C-Plane.
to abnormal antenna RX power
LCR measurements .
- LNCEL A cell is considered as a sleeping cell due

- NRCELL to degraded RACH setup attempts.

to degraded RRC connection setup
LCR attempts.
EPIMC Calibration is needed to be

triggered before EPIMC feature can be
EPIMC enabled.
EPIMC EPIMC Calibration is ongoing.
EPIMC EPIMC Calibration is failed.

The optional power group switch on
procedure has failed. As a consequence,
cells allocated to respective optional
- BBMOD power group are failed.
- SMOD Failure of configuring
Power Group theDigital
is a set of unit. Signalling
Processors (DSP) or System on Chip
(SoC) on the baseband card, which is
BBMOD powered up independently from other
SMOD sets of DSPs/SoCs.
LNCEL Antenna Carrier failure detected.
Basic beam set configuration is not

compatible to the connected radio unit
NRCELL (RU).
Inconsistency detected between

BTS failed to copy SW/config
MRBTS/WNBTS/WNCEL. from active
defaultCarrier
FCT to passive partition.
and 'DL UARFCN sent by RNC' of the
same cell while attempting to configure
LTE and paired WCDMA cell, when
WCDMA-LTE dynamic spectrum sharing
LNCEL and WNCEL (DSS) is activated.
Failure when attempting to enable or
disable shared bandwidth usage at LTE
side, when Dynamic spectrum sharing
LNCEL (DSS) with WCDMA or GSM is activated.
KPI formula defined by Operator is
None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.
None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.

None fulfilled.
Fault enriched with fault signature raised

Power
for the reset
purposeof secondary
of network-widesystemsystem
module
SMOD occurred.
fault tracking. Provides the information
The
about BTS
the has
crashbeen reset. Raised after
or failure.
FSMr3/AirScale
autonomous unit/BTS supports the following
recovery reset
BBMOD cause
when the for unit/BTS
the reset:is up and running
SMOD “unknown”:
again. Unknown cause
"power-on reset": Cold start
"software reset": Software reset
The referenced
"spurious reset":radio
Reset module
reasondoes not
detection
support
failed the requested Band and PLMN
LCR configuration.
"watchdog
A new BTSreset": System
that shall overload
be directly
"Emergency Reset": BTS
connected and integrated to NetAct reset started
isn't
but not finalized after 15 min
registered properly by NetAct Manager
"Emergency
and thereforeSystemd
cannot be Reset": BTS reset
integrated to
SMOD started
NetAct. but not finalized after 31 min
A potential reason for the fault can be a
faulty NMS IP address in the BTS plan
(nmsIntegrationIpAddress in
MRBTS MNL/MNLENT)
Indicates Transport SW crash or critical

failure that can be recovered by
None autonomous site reset
value than "none" it is necessary to
configure LNCEL_FDD.blankedPucch
and
LNCEL_FDD:selectOuterPuschRegion to
overlap totally the selected radio slim
carrier filter guardband. It refers to radio
configured to support the LNCEL_FDD.
The fault is reported when PRBs blanked
by blankedPucch does not overlap totally
the detected radio slim carrier filter
LNCEL guardband.
The BTS has lost all the Timing

reference signal from Fronthaul RRH
RU (CPRI-K).
The commissioned NRCELL-

beamSet.tiltOffset exceeds the Radio’s
NRCELL supported steering range.
Cell is considered as sleeping cell due to

degraded TX Power in all antennas
LCR configured within the cell.
Cell is considered as sleeping cell due to

LCR S1 Communication anomalies.
This fault is detected when the 5G cell

cannot be brought on air, because
Cell is considered
parameters as sleeping
that need to be thecell
sameduefor
to
LCR low PRACH messages reception ratio.
cells within a configuration block do not
match.
This fault is also detected for 5G FDD
cell, when RACH root sequence exceeds
NRCELL the limit supported by BB module.
Delay adjustment
Inter-eNB is needed in(CA
carrier aggregation order for
ABIx the unit to be able to proceed.
partners connected via SRIO) or inter-site
carrier aggregation (CA partners
connected via X2) cannot be activated
based on BTS configuration due to BTS
FCT hardware limitation.
A failure has occurred while performing

Small Cell: the SAS Feature Data Exchange
-CBSD procedure.
The radio unit connected to baseband

module was not detected after radio
RMOD protocol change.
Requested custom beamset configuration

has failed due to a missing or incomplete
LCR BSR package.
BCF RAT is blocked with the BTS Element
LNBTS Manager. The purpose is to avoid fault
NRBTS indications that might be raised during a
WNBTS BTS maintenance task.
During BTS startup and BTS
recommissioning, the BTSOAM has
detected
During cell that the filterorcapability
activation in RF
active cell
module is able to support
reconfiguration, the BTSOAM has guardband NB-
IoT, but is unable to support
detected that the filter capability in RF at least one
of the guardband
module NB-IoT PRB
is able to support positions
NB-IoT, but
of non-anchor
there is a risk carriers.
of NB-IoT performance
The maximum number of alarms raised
degradation
by KPI formula because
has beenthe reached.
position of a
This fault
guardband isor
also detected
inband NB-IoTwhen a unit
downlink
The
that maximum
served a Number
cell is Alarms
replaced byfor KPI
another
None carrier
formulas
- During is too
is
BTS close
80.startup to the band edge. The
unit,
NB-IoT anddownlink
the new unitand
channel
BTS
might not be
power may taken
be
recommissioning
into use because with LTE-NR differs
its hardware DSS, the from
below
BTSOAM configured
hasof power
detected boost
that the +6 dB.
filter
the hardware the previous unit.
capability in RF module is able to support
This fault isNB-IoT,
guardband also detected
but when
is on
not a unit
able to cell.
LCR This
that fault is areported
served cell is only
replaced the
with host
another
support the configured outer guardband
unit,
NB-IoT because new hardware differs from
PRB position.
the hardware
- This fault is also of the previous
detected unit.a unit
when
that served a cell is replaced by another
LCR This
unit, fault
and the is reported
new unitonly onnot
might thebehost cell.
taken
into use because its hardware differs from
the hardware of the previous unit.
- This fault is reported only on the host
None cell.
A failure has occurred while sending the

VES event to the configured ONAP VES
FCT Endpoint.
MRBTS O-DU has detected a failure during SSH

RMOD algorithm negotiation procedure
Client authentication procedure O-DU as

MRBTS SSH client was not successfully
RMOD authenticated by O-RU (SSH server)
Authentication of O-RU as SSH server

O-RU by gNB has failed
O-DU has detected that an unknown RU
is connecting for the first time, and DU
will disable server authentication at first
O-RU connection for it
O-DU has detected a failure during

MRBTS default Netconf account creation
O-DU has detected a failure during

MRBTS additional Netconf account creation or
RMOD provision to O-RU
BBMOD The SMOD/BBMOD UTC synchronization

SMOD has failed.
Active RF SW does not match any of the

BTS sharing radio modules, is in a newer
RMOD version.
Fault informs about different feature
activation statuses on the BTSs sharing
RMOD radio module.
SMOD Ethernet port security is disabled
BTS allows root access on service

account
SECADM - Root service user(toor4nsn)
There is a FHS
The installed sharing mode
transceiver does conflict
not match on
SFP An
withincompliant
the FHS transceiver
to be shared
the Nokia MN BTS is system
installed
bywhitelist.
two It is
modules
therefore (SM) such as:
considered as not qualified.
(1) SM1
There is is in shared
a high mode
risk that andnot
it may SM2 workis in
dedicated
as expected. mode, EMCorregulations of local
SFP (2) SM1
FHSisprimary
authorities
The in
haveprimary
not controller
been
controller mode and
verified.
is either
SM2 is also in primary controller
missing at start-up or is lost at run-time. mode, or
(3) SM1 is in dedicated mode and SM2 is
The
in [Q]SFP+/[Q]SFP28
primary or secondary transceiver
controller has
mode,
The
not FHS secondary
reached its lowest controller
working waits for a
or
user-defined amount of time for the FHS
SFP temperature.
(4) SM1 controller
is in secondary controller mode
primary to become available
and SM2 is also in secondary
again before taking a temporary FHS controller,
or
primary controller role.
(5) SM1 is in dedicated mode and SM2 is
FHS also in dedicated
An alarm due to the mode.
fault is reported when
the FHS primary controller is not available
after the user-defined amount of time,
and the secondary controller takes a
FHS temporary primary controller role.
The number of objects (for example, the
number of external input and output lines)
reported
Baseband bycard
O-RU exceeds
crash the capacity
has been detected.
RMOD of the BTS.
The BTS tried to fix the fault situation by
performing a recovery reset on the faulty
unit. The recovery reset fault 52
EFaultId_UnitAutonomousResetAl could
BBMOD not
Thebe reported eCPRI
connected before RU
the does
reset.not
support features configured in the radio
network (RNW) partisofenabled
APTS functionality the sitebut APTS
configuration file (SCF)
metrics are invalid. OR it does not
NRCELL support configured beamSet.
"The computed APTS metrics validity has
expired.": The computed metrics are older
than 72 hours,
"No APTS metrics are available at all.":
SMOD No metrics are available at all.
The alarm is reported to inform the

operator that the Radio Unit is incapable
RMOD of establishing IPSec connection.
an autonomous reset on its own.
5G RAT: Carrier Aggregation

configuration for the existing cells cannot
be online activated due to cell mapping
on BB pools that does not fit to carrier
aggregation requirements. 5G RAT reset
is needed to recover carrier aggregation
service. Impacted 2CCs or 3CCs CA
configurations are reported in additional
NRBTS information of the alarm.
Slot
Eachofcell
configured PRACH
timing offset configuration
configuration
index
parameter must be set to the by
value is already in use other
same cell
value
NRCELL using the same L1 baseband resource
in all cells on the same baseband card
when the cell timing offset feature is
activated.
If one CPRI Also,
RU the baseband
is phased card
out in where
release
- NRCELL; the
N, cell
Thethen is
cellitwithallocated
hasthe should
be configured
migrated tooffsetssupport the
eCPRI mode
- LNCEL; cell timing offset
immediately.
frameStartOffset If thefeature.
andoperator
sfnOffset stilliskeeps
using
connectedthis CPRI
to a non RU,eCPRIthen: or CPRI-N
-Since release N+1,
capable radio module when BTS willcell
generate the
- NRCELL; fault/alarm
configurations to inform
of timing operator
offsetsthat is this
- LNCEL. CPRI RU has been phased out and
activated.
should be migrated to eCPRI right now.
-Since release N+2 onward, BTS will
One or more
generate the carriers
fault/alarm has/have
to inform been
autonomously torn down
operator that this CPRI RU has been by the radio
RMOD module.
phased out relation,
and MUST be migrated to by
A neighbor which is detected
eCPRI
a UE through measurements due to on
right now, and all cell services
this CPRI ANR
activated RU will be stopped.
features, could not be
This fault doesn't
stored because the maximum apply to RF sharing
numberand of
RMOD
AirScale SBTS: RF chaining
neighbor case.
relations (LNRELX instances)
A neighbor relation, which is detected by
- FCT (HW rel.4) per cell through
the UE is already reached. Neighbor
measurements due to
relation information
activated ANR features needs to be cleaned
is created, but
Flexi SBTS: up
duemanually
to the 3GPP by the limitoperator
of maximum through 32the
-AirScale
FCT (HW rel.3)
SBTS: plan
cells file.
that can be configured per frequency
The maximum length of SIB15
- FCT (HW rel.4) object,
informationor the O&M configured
depends, for example, maximum
on the
number of e1xCSFB target
cell bandwidth, configured SIB (System cells per
Flexi SBTS: frequency,
InformationitBlock) is not coding
provided for and MFBI
rate,
- FCT (HW rel.3) measurement by the
(Multiple Frequency Band Indicator)UEs.
feature activation. The warning is
During
reported BTS startup,
if one or moreFDD eNB(Service
SAIs does not
detect the neighbor
Area Identities) TDD eNB.
are omitted FDD in
by BTS eNB
LCR allocates
order not the cells with
to exceed thethe normal length.
maximum cell
deployment and inter-eNB FDD-TDD CA
The
is notposition
enabled. of NB-IoT inband downlink
non-anchor carrier
Later, FDD eNB detects has athe
collision with the
neighbor
configuration of a slim
TDD eNB and exchanges CaDatacarrier or downlink
LCR interference shaping.
information. FDD eNB finds that the
existing cell deployment needs to be
replaced by CA specific cell deployment.
BTS reset is needed in order to deploy
FCT the CA specific cell.
SRS resources for the TDD mMIMO cell
on eCPRI
Some MAA can't
problems in TXbe
or configured due to
RX path have
missing or not supported raw SRS
caused beam-forming calibration to fail.
FCT pattern.
The path means all units between the
signaling processor (DSP) and the
antenna line that processes the data
transmitted (TX) or received (RX) by the
- LNCEL BTS.
An overload situation has been detected
by
Thethe schedulerPHICH
configured on thetransmission
user plane.
Recovery
power boost actions
cannotarebeinitiated
appliedtoeither
- LNCEL decrease
partly the load
or entirely level. of a lack of
because
Flexi BTS FDD, Flexi BTS TDD, AirScale
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS remaining
BTS TDD, power after
AirScale BTSconsidering
FDD, Flexi
TDD, AirScale BTS FDD, Flexi SBTS, AirScale (boosted)
SBTS, AirScale SBTS: RS power,
cell-specific DL
SBTS: (boosted)
The receivedPCFICH power, power
interference and minimum
(RIP)
- LNCEL reserved power for PDCCH.
value per physical resource block (PRB)
of theBTS
Flexi cell for
TDD,ULAirScale
subframes BTS exceeds the
TDD, Flexi
predefined threshold
SBTS, AirScale SBTS: for at least the
Flexi SBTS, AirScale SBTS: operator-configured parameter
The Received Interference Power (RIP)
- LNCEL alarmThresholdCrossingTime.
value per Physical Resource Block (PRB)
of the cell for UpPTS symbols exceeds
Flexi BTS TDD, AirScale BTS TDD, Flexi the predefined threshold for at least the
SBTS, AirScale SBTS: operator-configured parameter
- LNCEL alarmThresholdCrossingTime.
by the scheduler on the user plane.
Recovery actions are initiated to
- LNCEL decrease the load level.
by the scheduler on the user plane.
Recovery actions are initiated to
- LNCEL decrease the load level.
The
The remote
Licenseinterference in UL(LAA)
Assisted Access subframe
LNCEL has exceeded the defined threshold.
feature is enabled and the system module
does not receive a response for 300
seconds from the radio module for Listen
Before Talk (Clear Channel Assessment)
- LNCEL request on the unlicensed cell.
Remote Interference eNB identity is

detected and current eNB/cell will send its
- LNCEL own RI specific sequence
DwPTS
eNB androllback as special
gNB involved subframe
in LTE NR DSS
configuration
do not use compatible systempurpose
5 (3:9:2) for the of
releases.
LNCEL remote interference avoidance.
Operator has to upgrade either LTE or
NR side for compatible system releases
and/or activate the support of compatible
message sets within the LTE NR DSS
LNCELL configuration.
The CRM Client is not able to establish a
valid EN DSS partnership while the
maximum number of 'EN DSS Setup
LNCELL Request' retransmissions is not reached.
The CRM Client does not receive any
response from the CRM while the number
of 'EN DSS Setup Requests'
LNCELL retransmission is not reached.
expected,
Bandwidths extra blanking
mismatch done inside
between LTE and LTE
higher than NR
LTE5635/CB007788] maxNrDssRatio.
DSS reconfiguration
grid).
NR cells.
Reasondue
failure 1110) [feature
to: NR UL PRB blanking area
Reason
Reason 7004)
3080) [feature
[feature LTE4750] There
LTE4750/5GC001856]
does not match
LTE5635/CB007788] LTE DSS
reservation
NR UL PRB area foris
no common
reconfiguration
NB-IoT (lower DSS DL
failure
than sharing ratio
due to: Required
expected).
blanking
between area
LTE does
and NRnotduematchto NR LTE
minimum
Reason DL subframe
6006) [feature resources
LTE4750] could
DSS
reservation
minNrDssRatio area for
higher NB-IoT
thanto: (lower
LTE than
not be reservedfailure
reconfiguration for NR. due Blanked
expected).
maxNrDssRatio.
Reason
LTE 1111) are
UL PRBs [featurenot blanked by Blanked
NR or
Reason
Reason 7006)
3081) [feature
[feature LTE4750]
LTE4750] Thereonis
LTE4750/5GC001856]
blanked NR UL PRBs DSS
are not blanked
LTE
no UL PRBs
common DSSareDL notsharing
blankedratio by NR or
reconfiguration
LTE (checked failureLTE
within duegridto: Required
only). on
blanked
between NRLTE ULandPRBs NR dueare not blanked
to LTE DSS
minimum
Reason DL subframe
6009) [feature resources
LTE4750] could
LTE
The (checked
DSS
minNrDssRatio basicwithin LTE
configuration
higher than grid
NR only).
isConflicting
incorrect
LNCEL not be reserved
reconfiguration for LTE.
failure due to:
Reason
for the 7009) [feature
downlink.
maxNrDssRatio. LTE4750] do not
The parameters
UL
The PRB
Conflicting reservations
ENbetween
DSS ULKeep
PRB between
Alive procedure
reservations LTE and is
match
Reason
NR. 3110) the
[feature peer cells andbetween
the
interrupted.
LTE
dynamicand NR. The
spectrum
LTE4750/5GC001856] connectivity
sharing to the
cannotDSS
Required
Reason
remote
Reason 6082)
Common
7054) [feature
Resource
[feature LTE4750]
LTE4750]Manager UL
operate.
minimum
reconfiguration DL subframe
failure resources
due to:betweenThere could
isLTE
no
LNCELL (CRM)
Cells has
Bandwidths
not be reserved been lost.
mismatch
forsharing
NR. ratio between
common
and NR cells. DSS UL
Reason
LTE and5040)
3111)
NR due [feature
to NR CB006797]
minNrDssRatio The
The
Reason
featureLTE-NR7055) feature
[feature
configuration is
is deactivated
LTE4750]
not consistent LTEfor cell
the
LTE4750/5GC001856]
higher
partner than
EN LTE maxNrDssRatio.
DSS cell. Required
UL center
between
minimum
The DSS6083) frequency
eNB
DL
basic and
subframe does
gNB.LTE4750]
configuration not
resources match could
is incorrect NR
Reason
cell ULreserved
center [feature
frequency. DSS
LNCEL Reason
not
for be
the 5086)
uplink.
reconfiguration [feature
The for
failure LTE. LTE4750]
parameters
due to: do
ThereThe isNR
not(both
no
In case the
Reason 7082) radio unit
[feature set isto
LTE4750]blocked There
maximum
match
common
DSS between
partner
share
DSS UL
cells
is too
thesharing
arepeerlow cells
ratio
disabled),
fulfill
and thefaultis
between
this
no common
resources
dynamic DSS UL
needed
spectrum to sharing
operate
sharing ratio
the NR cell.
cannot
LTE
might
betweenand NR
be5087)
visible
LTE due
andfor toNRLTE
few minNrDssRatio
seconds
due to NR before
Reason
operate.
higher than NR [feature LTE4750]
maxNrDssRatio. The
it’s
LTE cancelled
minNrDssRatio
minimum during
higher
share cell
is than
toodisable
LTE
low to fulfill
LNCELL Reason
procedure. 6112) [feature
maxNrDssRatio.
resources
Reason 8007)
LTE4750/5GC001856]needed[featureto operate
DSS the LTE
LTE4750]
Reason
cell. 7083)
Subcarriers requested [feature LTE4750]
by NR are There is
reconfiguration
no common DSS failure
UL due
sharing Maxnot
to:ratio UL NR
Reason
adjacent
DSS ratio5100) too[feature
tois(contiguous
low, LTE4750]
with) the
required NR has
dynamic
minimum
between
forbidden LTE
MBSFN and NR due toare LTE
area(s).
UL PRBsThe
minNrDssRatio could notconfiguration
dynamic
higher beareas
reserved
than NR
in
for NR.
LNCEL reserved
subcarriers
Reason subframes
6113) that are
[feature 0,
not 4, 5, 9.
reserved nor
maxNrDssRatio.
blanked. It may occur that multiple
LTE4750/5GC001856]
Reason 7112) DSS
dynamic areas [feature
reconfiguration can
failure be due
derived.
LTE4750/5GC001856]
Reason 8008) [feature Maxto:UL
LTE4750]
Min
NRUL DSS NR
DSS
ratio ratio is
is toonumber too high,
low, required required
minimum minimum
UL
LNCEL Incorrect
UL PRBs could not of be
NRreserved
UL reservedfor LTE.
PRBs
areas. could not be reserved for NR.
Reason
Reason 7113) 8084) [feature
[feature
LTE4750/5GC001856]
LTE4750/5GC001856] Min The UL NRNR UL DSS
ratio
maximum share is too low to fulfil UL
is too high, required minimum
LNCEL PRBs
resourcescould not beto
needed reserved
operatefor theLTE.
cell.
Reason 8085) [feature
LTE4750/5GC001856] The UL minimum
share of LTE is too low to fulfil resources
LNCEL needed to operate an LTE cell.
An emergency
In GTP-U switch was
supervision, triggered,
a network but
element
LNCEL could not be executed.
did not respond to the GTP-U: Echo
Request message within the allotted time.
Fault can be reported against GTP-U
AirScale SBTS, Flexi SBTS: connection towards
The transport S-GW (S1
path (SCTP) link) and
for connection
- GTPU adjacent gNB (X2 link).
to the MME is broken. This might be
because of an unplugged cable to the
MME. There is no transport path available
to
Thecontinue operation
transport on thefor
path (SCTP) faulty
connection
- LNMME connection with the MME.
to an adjacent BTS is broken. This might
Flexi BTS TDD, Flexi BTS FDD, AirScale BTS be because of an unplugged cable to the
TDD, AirScale BTS FDD, Flexi SBTS, AirScale adjacent BTS. There is no transport path
SBTS: available
One of thetotransport
continue paths
operation on the
(SCTP) in
- LNADJ faulty connection with the adjacent BTS.
SCTP connection to the MME has failed.
This is only applicable when SCTP multi-
homing is supported. An alternate
AirScale SBTS, Flexi SBTS: transport path is available to continue
- LNMME operation.
The transport path (SCTP) for connection
to MME has been broken. The reason for
this can be an unplugged cable to MME.
No
Onetransport path is available
of the transport to pursue
paths (SCTP) in
AirScale SBTS, Flexi SBTS: operation on the faulty
SCTP connection to MMEconnection
(which with
- LNM3 the MME.MBMS service) has failed. This
provides
is
Flexi onlySBTS, applicable AirScale when SCTP
SBTS, multi-
Flexi BTS
homing is supported.
FDD, Flexi BTS TDD, AirScale BTS TDD, An alternate
AirScale SBTS, Flexi SBTS: Flexi
transport BTSpath TDD,is AirScaleavailableBTS to pursueTDD,
AirScale
A failure has BTSoccurredFDD: during activation or
- LNM3 AirScale
operation. BTS FDD, Flexi SBTS, AirScale
There was a of
deactivation problem
a trace with
session.a radio This network
SBTS, Flexi BTS FDD:
configuration
failure case atapplicable
the BTS startup or at the
The BTS hasisencountered toasubscriber
few possibly
activation
trace,
BTS raises of
cell trace, the
thisPLMNs,delta
interface
fault configuration
if itwhichtrace
experiences session, abe
misconfigured cannot
AirScale SBTS, Flexi SBTS: related
or
problem PCMD toin(Per
atheproblem
Call
internal with
Measurementthe data Data)
configuration reading
data
used by the BTS for accepting calls from
- LNBTS or
report. inconsistent
distribution (cellconfiguration.
setup)
new UEs, which select to thosethe PLMNs.
C-Plane
and U-Plane SW components.
In
The case
rootofcause
PLMNs subscriber
thatofare trace,
theconsidered
fault might the following
be an
are
incorrect the possible
cell
misconfigured by the BTS are: reasons:
configuration in the site
LNCEL -configuration
- The thoseSubscriber
currently Trace feature
file configured
(scf). at the is not BTS for
enabled
one or morein the BTS.
cells where each cell is of a
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS The
-specific BTS
The IDRAT raises
usedtype this
for the fault if
subscriber it experiences
trace
TDD, AirScale BTS FDD, Flexi SBTS, AirScale a problem in the Flexi "Wideband
internal Lte"
configuration or
session
Flexi
"Narrowband BTS is already
FDD, IoT". in use
BTS forTDD, another AirScale
SBTS: data
active
BTS distribution
TDD,subscriberAirScale (cell
trace
BTSsetup)
session.
FDD, to C-Plane
Flexi
- LNCEL -and thoseU-Planeserved SW by components.
more than one MMEs,
-SBTS,The number
AirScale of subscriber
SBTS:
and therefore, currently broadcasted by trace
sessions
A failure
the cells has in the
of the BTS has
occurred
BTS. in reached
However,the internal none theof BTS
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS maximum
trace connectionnumber
these PLMNs have MMEs serving a or ofin subscriber
the trace trace
FDD, AirScale BTS TDD: sessions
connection
specific RAT supported
between
typeanwith by the
therelative
BTS BTS, and which
third-
capacity is
There
60. has been opening, reading, or
- SMOD party
greater
file tool.
content thanproblem zero. Because with a BTS of this, the
vendor-
-BTS The handover
cannot select in the any BTSof these is ongoing MMEsfor for
specific
the file at BTS startup.
AirScale BTS FDD/TDD, Flexi BTS FDD, Flexi any UE newtoUEs be traced.
attempting registration in
BTS TDD: these
The PLMNs.
fault
In case
Flexi
This BTS
alarm ofisFDD,alsointerface,
cell,
indicates
detectedand
Flexithat
when
BTSa TDD, WCDMAPCMD a vendor-
AirScale
- MRBTS specific
report file
trace, is themissing.
possible reasons are:
BTS
neighbor TDD, AirScale
cell, which
Each MME can be assigned to handle BTS
is FDD,
reported Flexi
by a UE
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS -SBTS,
TheofCell
through
cells Trace
AirScale
ANR-specific
the following feature
SBTS: is notRATenabled
measurements,
given types: in
TDD, AirScale BTS FDD, Flexi SBTS, AirScale the
This
could BTS.
alarm
- Wideband not be indicates
stored
LTE that aused
because
(default, WCDMA
thewhen no
SBTS: -maximum
The
neighbor PCMD
RAT type is report
relation,
number
specified) trace
which isfeature
reported
of LNADJW instances is not
by a
- LNBTS enabled
UE
is due
already to
- Narrowband IoT in the
activated
reached. BTS. UTRAN
The additional ANR feature
alarm
has
info been
holds stored,
- Wideband the LTE UTRAN but at
and CGIleast
Narrowband of one of
the reported
IoTthe
mobility
WCDMAparameters cell, which of couldLNRELW not be stored,
AirScale SBTS, Flexi SBTS: (csfbPsHoAllowed,
in
Allthe form of: registered
previously psHoAllowed,
UEs in these and
- LNBTS srvccAllowed)
"A
PLMNsneighbour remain has
WCDMA been
unaffected. set to
cell which is
This
reportedalarm
"forbidden", by indicates
because
an UE duethat
the tothe
number maximum
activated of ANR
This
number
neighboralarm of indicates
LNADJ,
relations that
LNADJL,
(LNRELW a WCDMA
or both
instances)
feature(s)
neighbor could
relation, not be stored
whichnumber is reported because by a
LNADJ
exceeds
the maximum and the LNADJL
numberobjects
maximum of WCDMA has ofbeen
AirScale SBTS, Flexi SBTS: UE
WCDMA through
exceeded in ANR-specific
theisBTS,
neighbor cells, and measurements,
whichthat the new
might be
neighbour
could not cells
be stored reached.
because WCDMA
the
- LNBTS object
used
neighbourby has the notBTS been in
cell information stored.
measurement needs be
maximum
configurations number (for of neighbor
psHoAllowed relations
or via
cleaned
per up
cell is already manually by the operator
srvccAllowed,
plan file (WCDMA limitreached.
in 3GPP
cell CGIof
The
36.331
{rncId
additional
is
= %d,
alarm
(32); info
for holds
csfbPsHoAllowed the ECGI is the LTE cell
AirScale SBTS, Flexi SBTS: CellId
and the = %d,
UTRAN ecgiPlmnId:
CGI of theMNC= related %s,
- LNBTS LNHOW::maxNumCsfbTargets).
MCC= %d})".
WCDMA
The additional neighbor alarm cellinfoin the
holds form: the
"LTE
ARFCN of the affected carrier =frequency
cell ECGI{ecgiAdjBTSId %d,
ecgiLcrId
as well as the LNCEL and LNRELW%d,
= %d, ecgiPlmnId = { %d,
AirScale SBTS, Flexi SBTS: %d}}
instance , WCDMA numbercell in theCGIform {rncId= of: %d,
- LNBTS CellId= %d, cgiPlmnId
"Affected WCDMA ARFCN carrier = { %d, %d,=%d}}". %d,
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS LTE cell ECGI{ecgiAdjBTSId = %d,
TDD, AirScale BTS FDD, Flexi SBTS, AirScale ecgiLcrId = %d, ecgiPlmnId = { %d, %d,
SBTS: %d}} , WCDMA cell CGI {rncId= %d,
- LNBTS CellId= %d, cgiPlmnId = { %d, %d, %d}}"
limit of 5 us.
-TheTheEARFCN
BTS is inofholdover mode for cell
an LTE neighbor more is a
than 6 hours, which means
mapped EARFCN according to the MFBI- that the
estimated phase error
profile configuration value
(that might not be
is, the
reliable.
requirement for a homogeneous MFBI
It is assumed is
configuration in violated).
this case that the real
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS absolute
A handover valuetarget cell cannot
of phase error isbegreater
uniquely
TDD, AirScale BTS FDD, Flexi SBTS, AirScale than
selected
As a consequence, handover to this are
5 us.because several candidates
SBTS: available
neighbor cell for aiscertain PCI value
not possible, andand
call drop
- LNCEL carrier
- Themight
rate frequency.
BTS increase
is in assisted holdover
if there mode
is no other
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS for morehandover
suitable than 24 hours,
target.which
If themeans
UE-basedthat
TDD, AirScale BTS FDD, Flexi SBTS, AirScale the
ANRestimated
is activated phase
anderror value
the X2 link might
is not
SBTS: be reliable.
available, there will be continuous retries
- LNADJL It
toisresolve
assumed the in this case the real
ECGI.
absolute value of phase error is greater
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS This
than fault
5 us.occurs when CGI
TDD, AirScale BTS FDD, Flexi SBTS, AirScale measurements indicate that two or more
SBTS: cells
- ThethatBTSoperate on the same
is synchronized by afrequency
Sync
- LNCEL use the same PCI.
Master, which reports the phase error of
the provided sync signal.
The absolute value of the estimated total
Flexi SBTS, AirScale SBTS: phase error
This fault in thewhen
occurs SyncCGI
Slave exceeds
- SMOD the 5 us limit.
measurements indicate that two or more
WCDMA cells
that operate on the same carrier
frequency use the same primary
- LNCEL scrambling code (PSC).
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS An inconsistency has been detected
TDD, AirScale BTS FDD, Flexi SBTS, AirScale between
Flexi BTScluster members,
FDD, Flexi whichAirScale
BTS TDD,
SBTS: prevents
BTS TDD, AirScale BTS FDD, Flexifrom
the inter-BTS CA feature
- LNBTS being
SBTS,enabled.
AirScale SBTS:
A SW incompatibility has been detected
between cluster has
The application members, which
detected a problem
AirScale SBTS, Flexi SBTS: prevents the inter-BTS CA feature from
with inter-BTS link communication (SRIO,
- LNBTS being enabled.
RP3-01, Ethernet, and so on). Features
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS that
This depend on the inter-BTS
fault is reported when the BTS
TDD, AirScale BTS FDD, Flexi SBTS, AirScale communication, like the "Inter
detects that the number BTS
of neighbor-
SBTS: Carrier aggregation" feature,
related objects (which represents theare
- LNBTS disabled.
neighboring BTS, andwhen its cells
This fault is reported the with
BTSthe
relationship
detects that the number of neighbor-are
objects) in its database
equal
relatedtoobjects
or above the configured
(which representsvalue
the of
AirScale SBTS, Flexi SBTS: the parameter "maxNumAnrMoiAllowed"
neighboring BTS, and its cells with the
- LNBTS in LNBTS. objects) in its database is
relationship
equal to or above an internal threshold
based on the configured value of the
AirScale SBTS, Flexi SBTS: parameter "maxNumAnrMoiAllowed" in
- LNBTS LNBTS.
BTS is informed about sync loss of
neighbor BTS in the same cluster and as
a consequence needs to deactivate
FCT Carrier Aggregation feature.
Inter BTS SRIO link couldn't be

established due to carrier
BTS has detected DomainIds not being
aggregation
FCT unique
relation misconfiguration. One ortopology.
or other errors in cluster more of
the configured carrier aggregation
relations point towards a cell that does
not exist in any of the BTSs within the
- LNBTS configured carrier aggregation cluster.
1. The pool configuration of the resource
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS DSPs has failed between C-Plane and U-
TDD, AirScale BTS FDD, Flexi SBTS, AirScale plane.
SBTS:
- SMOD 2. The pool configuration of system
- BBMOD module resources has failed.
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS
TDD, AirScale BTS FDD, Flexi SBTS, AirScale Flexi BTS FDD, Flexi BTS TDD, AirScale
SBTS: The
BTS BTS
TDD,configuration
AirScale BTShas failed
FDD, in the C-
Flexi
- LNBTS Plane.
SBTS, AirScale SBTS:
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS The configured PUSCH masking and/or
TDD, AirScale BTS FDD, Flexi SBTS, AirScale PUCCH blanking size for the cell leads to
SBTS: a situation where there are no remaining
- LNCEL resources for the PRACH allocation.
The automatic PUCCH allocation

AirScale SBTS, Flexi SBTS: configuration cannot support the operator
- LNCEL configuration.
The GTP tunnel between two Flexi Zone

-FSM
AirScale BTS FDD/TDD: Access
The linkPoints
betweenis out of service.
eNBs or Flexi Zone
- FCT (HW rel.4) Access Points carrying the time, which is
critical for inter-site Carrier Aggregation
Flexi BTS FDD/TDD: data, permanently exceeds the maximal
- FCT (HW rel.3) allowed limit.
A neighbor cell, which is detected by a
The sidelinkmeasurements
UE through transmit resource duepool
to
configuration is invalid and overlapping
activated ANR features, could not be
with
storedPUCCH
because region, or leavingnumber
the maximum insufficient
of
- LNCEL resource for PRACH.
1xRTT neighbor cells (LNADJX
instances) is already reached. Neighbor
cell information needs to be cleaned up
manually by the operator
The X2 interface reset hasthrough the plan
failed after
FCT file.
several attempts. This indicates that a
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS severe failure has occurred. For example,
TDD, AirScale BTS FDD, Flexi SBTS, AirScale there is some configuration problem,
SBTS: there is no X2 connectivity, the adjacent
- LNADJ Flexi BTSfailed,
BTS has FDD, and
FlexisoBTS
on. TDD, AirScale
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS SBTS, AirScale SBTS:
TDD, AirScale BTS FDD, Flexi SBTS, AirScale There
There is
is no
no X2
S1 connectivity
connectivity to
to an
an adjacent
MME.
SBTS: BTS, the adjacent BTS has failed, and so
- LNADJ on.
The fault is generated if the S1 setup
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS procedure has subsequently been
TDD, AirScale BTS FDD, Flexi SBTS, AirScale attempted but failed the number of times
SBTS: equal
The S1tointerface
the valuereset
of the
hasparameter
failed after
- LNMME "maxS1SetRetry".
several attempts. This indicates that a
The S1 BTS configuration update
severe failure has occurred:
procedure has failed. there is
some configuration problem; there is no
AirScale SBTS, Flexi SBTS: S1
Theconnectivity;
MME could not MME behas failed, about
informed and so
- LNMME on.
the modification of at least one of the
following BTS configuration data:
- BTS Name
AirScale SBTS, Flexi SBTS: - Supported TAs (TAC, PLMN Identities)
- LNMME - Default paging DRX
1. An RIM association could not be
A RIM request
established to the an
because serving BSS has
RIM Error PDU
failed after several attempts.
has been received for an RIM-enabled This means
that
GERAN the System
neighbor Information
cell. at least for the
Flexi SBTS, AirScale SBTS: There
related isGERAN
failure to orsetup
UTRAN neighborone X2
2. An
IPsec RIM
tunnel Application
using RNL Error
withhas
a beencells
neighbor
- LNADJW is not reliable.
detected.
BTS
The detected by ANR (Automatic
operator-configured maximum
The
3. S1operator-configured
Neighborlinks to allconnecting
Relation) configured maximum
detection MMEs are
functionality
number
number of
of UEs
UEs connecting through
through a
anthe
Flexi SBTS, AirScale SBTS: active,
due
normal but
to any
call the
of routing of RIM
the following reasons:
(maxNumClusterUe) PDU hasto been
- LNADJG emergency
RIM-enabled
a. IP version call or
WCDMA
mismatchthrough an
neighbor
of the incoming
celllayer
outer is not
reached.
handover Until one or
(MaxNumClusterUe more of the
+ 10%
- LNADJW available.
IPsec
currentlytunnel endpoints
connected UEs is released,
reserve)
b. has
IP versionUEs been
mismatch reached. Until
of the inner one or
layer
subsequent
more of the that connected
currently attempt to connect
UEs is
IPsec
through tunnel
normal CP/UP
call areendpoints
released
released,
c. Insufficientsubsequent
IPsec UEs
resourcesthat attempt to
immediately
connect through normal call orof the RRC
after completion
-FSM connection
emergency establishment.
Alarm due tocall theare released
fault will be immediately
raised
after completion of RRC
initially when there is attempt connection
to setup X2
establishment,
IPsec tunnel with andanrequests for incoming
"eNB controlled"
inter-eNB
neighbor eNB. or inter-RAT handovers are
-FSM rejected.
The alarm will be canceled only after all
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS failed X2 IPsec tunnels with "eNB
TDD, AirScale BTS FDD: controlled" neighbor eNBs are setup
- LNBTS successfully.
Flexi SBTS, AirScale SBTS: The establishment of the configured X2

- LNADJGNB link towards the adjacent gNB has failed.
The System Information Broadcast-

Flexi SBTS, AirScale SBTS: The
relatedmaximum
parameters length of SIB5
have changedinformation
more
- LNCEL depends,
than
5G BTS: 32 for
times example,
within on
three the cell
hours.
bandwidth,
The fault configured
detected forSIB
is modification coding
5Gessential
cells when rate,
and online
on all IRFIM instancesof configured NB-in
beamforming
IoT SIB parametersweightprocedure
vector file is is delayed
missing
the
on cell. The
the system warning
module. is reported if one or
Flexi BTS FDD, AirScale BTS FDD: because
more carrier it takes time to release
frequencies and all RRC
- LNCEL connected
corresponding NB-IoT UEs in NB-IoT cell.
inter-frequency
AirScale
There is BTS
no PLMNFDD: available forcellcell(s)
neighboring
Beamforming and/or
mappingblacklisted list
due
items toneed
S1 link to failure
be or file
omitted due
by
on
to
eNB
the system
in order
module or the beamforming vector weight
misconfiguration.
not
file to exceed the maximum
on a radio is missing, and length of
LCR If LNBTS-actPlmnUnavailForCellReport
SIB5. is
configuration
configured to of a cell forthis
'disabled', FDD faultmassive
report
MIMO
function radio is not possible.
is disabled;
- MRBTS This fault is also detected when the
If LNBTS-actPlmnUnavailForCellReport is
- NRCELL beamforming
configured to 'cell', this file
mapping faultisiscorrupted
reported or to
- LNCEL has an improper
the affected cell. structure.
$ID in fault name indicates the LNCEL.ID

of the cell for which the fault was
LNCEL detected.
Start of Automatic Access Class Barring

is reported as a warning for every
- LNCEL impacted cell. length of SIB5-BR is
The maximum
936bits [3GPP TS 36.331 5.2.1.1]. The
eNB omits one or more CATMIRFIMs in
Flexi BTS FDD, AirScale BTS FDD: SIB5-BR in order not to exceed the
- LNCEL maximum length of SIB5-BR.
The
The maximum
maximum length
length of SIB2-BR is
After
936bitsa DSP
[3GPP crash,
TS theofBTS
36.331
SIB24collectsThe
5.2.1.1]. core
information
dumps and depends
DSP on the
memory cell from the
dumps
eNB omits one
bandwidth, or moreSIB
configured PLMN-based
coding rate
crashed
ACB DSP.
settings in SIB2-BR in order
and
After on all
anthe
FCT nrCarFrqL
or an FSP instances
crash, in not
the
to
NRFIM
BTS
LCR exceed
configured maximum
in dumps length
the cell.from
Thethe of SIB2-BR.
warning is
collects core crashed
reported
unit. if one or more NR carrier
frequencies
Independentneed of anyto DSP,
be omitted
FCT or byFSPeNB in
order not to exceed the maximum
crash the BTS captures and collects IQ length
LCR
5G BTS, AirScale BTS FDD, AirScale BTS of SIB24.on special events provided that it
samples
TDD, AirScale SBTS, Flexi BTS FDD, Flexi has been configured to do so.
BTS TDD, Flexi SBTS: Fault 6450 notifies the operator that the
- BBMOD logs are stored in the BTS and can be
- SMOD collected in the snapshot.
Detected RF module does not support the

commissioned radio technology
Flexi SBTS, AirScale in BTS
SBTS, Flexi the
RMOD
Flexi SBTS, AirScale SBTS, Flexi BTS FDD, classical RF sharing mode.
FDD, Flexi BTS TDD, AirScale BTS TDD,
Flexi BTS TDD, AirScale BTS TDD, AirScale AirScale BTS FDD:
BTS FDD: The physical memory supervision has
- SMOD detected that memory usage has
- BBMOD exceeded a HW/board
Physical Downlink specific
Shared threshold.
Channel
(PDSCH) transmission error due to
incorrect BCP encoding result.
Note: This may be caused by DSP
FCT
Flexi SBTS, AirScale SBTS, Flexi BTS FDD, related HW issue of Baseband unit.
Flexi BTS TDD, AirScale BTS TDD, AirScale
BTS FDD:
- SMOD A correctable bit toggling error is detected
- BBMOD in DSP memory.
Flexi SBTS, AirScale SBTS, Flexi BTS FDD,
Flexi BTS TDD: Flexi BTS FDD, Flexi
A non-correctable, BTS TDD,
bit-toggling AirScale
error has
- SMOD BTS
beenTDD, AirScale
detected in theBTS FDD,
critical DSP Flexi
-Flexi
BBMOD SBTS,
memory. AirScale SBTS:
SBTS, AirScale SBTS, Flexi BTS FDD, A fatal error of the DSP HWAPI SW has
Flexi BTS TDD, AirScale BTS TDD, AirScale occurred.
BTS FDD: Flexi
A BTS FDD, Flexi
non-correctable BTS TDD,
bit toggling AirScale
error is
- BBMOD BTS TDD,inAirScale
detected the BTS FDD,
non-critical DSP Flexi
memory
If an FSP
SBTS, in the SBTS:
AirScale BTS generates this fault,
-Flexi
SMOD BTS FDD, Flexi BTS TDD, AirScale BTS area.
there is a malfunction in Application
the
A fatal error of the DSP SW
TDD, AirScale BTS FDD, Flexi SBTS, AirScale corresponding
has occurred. FSP sub-module.
SBTS:
- BBMOD If
If all
an FSPs
FSP ingenerate
the BTSthis fault, there
generates this is a
fault,
-Flexi
SMOD malfunction in the FSM.
BTS FDD, Flexi BTS TDD, AirScale BTS there is a malfunction in the
TDD, AirScale BTS FDD, Flexi SBTS, AirScale corresponding FSP sub-module.
SBTS:
- BBMOD If all FSPs generate this fault, there is a
-Flexi
SMOD BTS FDD, Flexi BTS TDD, AirScale BTS malfunction in the
Flexi BTS FDD, FSM.
Flexi BTS TDD, AirScale
TDD, AirScale BTS FDD, Flexi SBTS, AirScale BTS TDD, AirScale BTS FDD, Flexi
SBTS: SBTS, AirScale SBTS:
- BBMOD The BTS has purposely triggered a GPIO
-Flexi
SMOD BTS FDD, Flexi BTS TDD, AirScale BTS reset for the DSP.
TDD, AirScale BTS FDD, Flexi SBTS, AirScale A digital signal processing (DSP)
SBTS: concurrent crash has occurred (a fatal
- BBMOD error was indicated in one of the DSP
- SMOD cores that belong to the same chip).
HW reported loss of UL data due to
permanent data buffer overflow in DSP
caused by the following reasons:
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS - Bus or memory congestion for an
TDD, AirScale BTS FDD, Flexi SBTS, AirScale extended period of time.
SBTS: -The
RATGPSreset or DSPincludes
antenna Reset on
anFDD LTE
active
- BBMOD configurations
amplifier, whichwith OBSAI radios,
is powered due to
over the
- SMOD HW limitation.
antenna cable by the Flexi Zone Micro
Zone SFN Antenna. This alarm means
Small Cell: the GPS antenna is drawing too much
-FSM current.
Small Cell: A failure has been detected in the internal

-FSM communication between cores.
The multi-carrier cell is disabled because

Small Cell: of
Thethe lock of
value or the
block of the other multi-
parameter
-FSM carrier cell.
"IPNO:cPlaneIpAddress" does not match
the
Theone configured
unlicensed in FxP,
feature which is the IP
is enabled
address
(actUnlicensedAcc is unequal toor'off') and
for either the nbcplane
nbmplane
the eNB has interface (the same
not received IP is used
Channel
-FSM for both C and M planes).
Activity Measurement (CAM) reports for
10
Theseconds.
unlicensed A report that
feature is discarded
is enabled
because it is outside of
(actUnlicensedAcc is unequalthe expected
to 'off') and
range is not considered as
the eNB does not receive Channel a missing
LCR report.
Activity
AirScaleMeasurement
BTS: (CAM) reports for
30
Channel frequency switchisofdiscarded
seconds. A report that LAA cell has
because
failed or it is outside of the expected
range is not
LAA cell considered
kick-down as a missing
has failed or
LCR report.
LAA cell kick-up has failed
when LAA feature is enabled
(actUnlicensedAcc is unequal to 'off') and
dynamic power control is enabled
LCR (actLaaDpc = 'true') in the BTS.
The LTE-U feature is enabled (actLteU is
'true') on the eNB and an attempted LTE-
U Duty
This Cycle
fault change
indicates on theBTS
that same
LCR This
channelfaulthas
indicates
failed. that the
the BTS cannot
contact
reference one or morecalibration
oscillator Network Time
has
Protocol (NTP) servers configured by the
expired. The reference oscillator
ntpSyncServers
calibration is used parameter,
to minimizewhere $IP is
the BTS
Small Cell: the IP address
initialization time.of the affected NTP
-FSM server.
When operating with the Network Time
Protocol (NTP) frequency synchronization
reference source, long initialization times
Small Cell: can be required when the reference
-FSM oscillator calibration has expired.
The BTS received an SAS Heartbeat

AirScale BTS TDD: response terminating the current grant of
- CBSD the
TheCBSD.
BTS received an SAS Heartbeat
response terminating the current grant of
the CBSD and containing optional
AirScale BTS TDD: parameters for relocation to another
- CBSD frequency, power, etc.
The BTS received an SAS Heartbeat
AirScale BTS TDD: response suspending the grant of the
- CBSD CBSD.
AirScale BTS TDD: A failure has occurred while performing

- CBSD the SAS registration procedure.

- CBSD the SAS Spectrum Inquiry procedure.

- CBSD the SAS Grant procedure.

- CBSD the SAS Heartbeat procedure.
A failure has occurred while performing

AirScale BTS TDD: the SAS Spectrum Relinquishment
- CBSD procedure.

- CBSD the SAS Deregistration procedure.
AirScale BTS TDD: A failure has occurred while attempting to

- CBSD communicate with the SAS server.
AirScale BTS TDD: A failure

The occurred
MulteFire while
feature is performing
enabled pre-
- CBSD TX RSSI measurements.
(LNBTS_FDD-actMultefire = "true"), and
the eNB has not received MF
Measurement reports for 3 minutes. A
report that is tagged
The MulteFire featureasis"invalid"
enabledis
LCR considered a missing report.
the eNB has not received MF
Measurement reports for 9 minutes. A
report that is tagged as "invalid" is
LCR considered a missing report.
The MulteFire feature is enabled
the eNB attempted
M3 interface MF failed
reset has channelafter several
LCR (frequency) switch has failed.
attempts. This indicates that a severe
failure has occurred. There might be
some configuration problem, there is no
AirScale SBTS, Flexi SBTS: M3 connectivity, MME has failed, and so
- LNM3 on.
configured with maxSubfrPShare,
exceeds the allowed share
subfrPShareAllowed, that is, the
maximum share which is available in the
MBSFN synchronization area considering
the configuration of the MBSFN starting
There
subframe is no M3parameter
with connectivity to an MME,
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS the
mbsfnStartingSF. and so on. If the fault
MME has failed,
TDD, AirScale BTS FDD, Flexi SBTS, AirScale is canceled, autonomous recovery
SBTS: actions (reset) have
3. The MBSFN subframesolved the fault
configuration of
- LNM3 situation.
MBSFNs are overlapping when
MCE configuration update has finally
parameter
Flexi
failed.BTS FDD, mbsfnOverlapAllowed
Flexi BTS TDD, AirScale is set to
"false". In such case,
AirScale SBTS, Flexi SBTS: syncSubfrPShareAllowed
SBTS,
The MME AirScale
could SBTS: of the affected
not be informed about
- LNMCE MBSFNSYNCAREA
An MBMS SESSION
the modification of at least oneinstance
START isofset
REQUESTtheto "0".
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS is received
following by MCE
MCE and cannot
configuration data:be
TDD, AirScale BTS FDD, Flexi SBTS, AirScale admitted
- global MCE because
ID the maximum number
SBTS: of MBMS
- MCE namesessions per MCE is exceeded,
- LNM3 or because the
- supported MBMS resources
serviceareareanotidentities
enough
in any MBSFN supporting the requested
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS Flexi
The
service
BTS has
MCE FDD,
area,
Flexi BTS TDD,
inencountered
which case, an AirScale
theinternal
session
BTS
TDD, AirScale BTS FDD, Flexi SBTS, AirScale failureTDD, AirScale
such asafter BTS
a timeout, FDD, Flexi
unsuccessful
is suspended
SBTS, AirScale the MCE/BTS
SBTS: has
SBTS: outcome
already while
responded communicating
to MME withwith
an lower
- LNMCE An MBMS SESSION START
layers/TRSW/RROM, and so REQUEST
on.
MBMS SESSION
is received by MCE START
and isRESPONSE.
successfully
If
admitted in at least one is
the admission control periodically
MBSFN area, but
performed,
failed to be the warning
admitted dueshall
to not be
resource
An MBMSagain
reported SESSION STARTwould
if theMBSFN
content REQUEST be
constraints
is received in other
and accepted by areas
MCE, but the
LNMCE (HW rel.3), LNMCE (HW rel.4) identical
supporting to the previous
the requested warning.
session admission fails in service
some MBSFN area.
If admission control is performed
area due to other session with higher
periodically,
precedence that the warning
is admittedshalltonot
somebe
reported
other MBSFN area with overlappingbe
again if the content would
LNMCE (HW rel.3),LNMCE (HW rel.4) identical
subframes. to the previous warning.
If admission control is performed
periodically, the warning shall not be
reported again if the content would be
LNMCE identical to the previous warning.
Power distribution unit (PDU) or system

module (SM) input voltage is above the
PWRMOD, FCT threshold.
Power distribution unit (PDU) or system

AirScale BTS FDD, AirScale BTS TDD: module (SM) input voltage is below the
PWRMOD,
- ABIx, K2 FCT threshold.
The platform software detects a hardware
Flexi BTS FDD, Flexi BTS TDD: issue by examining buffer length and
- FSP received message length during SRIO
- FBB (Serial Rapid IO) message receiving.
AirScale BTS FDD, AirScale BTS TDD: The Atmel uC software update failed, the
FCT
- ABIx SW is corrupted, or the HW is corrupted.
Flexi BTS FDD, Flexi BTS TDD: An SRIO link width that is lower than
- FSP expected was noticed after SRIO port
- FBB configuration.
The boot flash in the alarming module in
the BTS is corrupted. No valid copy of
data exists in any of the redundant boot
- BBMOD flash memory areas in the alarming
- SMOD module.
The boot flash in the alarming module in
the BTS is degraded. At least one valid
- BBMOD copy of data still exists in the boot flash
- SMOD memory in the alarming module.
An invalid boot flash was detected in the

- SMOD alarming module in BTS and successfully
- BBMOD recovered.
This alarm notifies about non-critical SW
component failure when the non-critical
- BBMOD process crash has occurred and core
- SMOD dumping has been
BTS Common completed.
plug-in unit and BTS
Capacity plug-in unit are incompatible in
terms of booting capabilities. There is no
common mechanism in both modules to
FSP boot BTS Capacity plug-in unit.
[Q]SFP ([Quad] small form-factor

pluggable) power class is higher than
SFP supported by the host.
SRIO Link between ASIA internal SRIO

switches SPS1616 and CPS1432 goes
Switching SFP (small form-factor
down. Communication over SRIO
SFP pluggable)
towards FSPsto high
and power mode failed.
other subrack from
FCT is broken. This SRIO link between
SRIO switches should never go down if
HW is fine, if link goes down it means HW
FCT is faulty.
Detected BTS Plug-in Unit has type of

SMOD cooling incompatible with detected
BBMOD subrack type.
Fatal error of LTE

LTE Hardware Hardwaremodule
Accelerator Accelerator
has
ASOC, ABIC engine
been crashed by the Platformsoftware.
detected by Platform software
deployed on ARM cores, because of the
LTE FDD, LTE TDD: Fatal Error reported by another LTE
- ASOC Hardware Accelerator module or DSP
- ABIC core.
LTE FDD, LTE TDD:

- ASOC LTE Hardware Accelerator instance crash
- ABIC has been triggered by external script.
This fault indicates that the gNB-CU could
not activate the cell, as the X2 link with
the LTE eNB mapped to the NR CELL
NRCELL was not established.
The gNB configuration update procedure

NRCELL has failed in CU.
This fault indicates that the gNB is not
able to activate a SA cell due to
gNB-CU-CP unavailability of E1 or NG link.
This fault indicates that there is no slice in

gNB-CU-CP common between the TAC and the AMF.
There is no X2-C link for the connection

to the LTE eNB available. No NSA UE
gNB-CU can connect to the gNB
This fault indicates that the F1AP: Reset
procedure initiated by gNB-CU fails after
a few retries upon lack of response from
gNB-CU gNB-DU.
This fault indicates

The transport that a Protocol
path (SCTP) error
for connection
has been detected in a received
between gNB-CU and gNB-DU is broken.F1AP
gNB-CU message
This mightorbeis because
reported of
from
an the gNB-DU.
unplugged
cable between them. There is no
transport
The path path
transport available
(SCTP) to continue
for the the
The SCTPon
operation initiator
the fails
faulty to establish
connection
connection
SCTP between
association gNB
for NG and AMF is
interface
NRBTS between
broken. gNB-CU
This might and
be gNB-DU.
caused by anbe
between gNB and AMF. This might
unplugged
caused by wrong configuration ofThere
cable between them. IP is
no transport path available
address or SCTP port of the peer SCTPto continue
the operation
endpoint, on the
IP route faultyinconnection
broken the network,
SERVEDAMF between gNB and AMF.
shutdown of peer SCTP endpoint, or
firewall blocking.
The transport path The SCTPfor
(SCTP) initiator
the
cannot receive a correct
connection between local gNB and peer
acknowledgement
gNB/ng eNB is broken. for initialization
This might from be
SERVEDAMF the peer SCTP endpoint.
caused by an unplugged cable between
The
them. transport
There ispath (SCTP) for
no transport pathconnection
available
The
to the transport
LTE eNB path (SCTP)This
is broken. for the
might be
continue
connection the operation on the faulty
because
connection of between
an unplugged
between
local gNB
local cableand
gNB
peer
to the
and peer
gNB/ng
eNB. eNBishas
There no failed to be
transport pathestablished.
available
NRADJGNB gNB.
This might be caused by an unplugged
to continue operation on the faulty
cable between
connection withthem. There is no
the eNB.
transport
Note : In SBTS for NSA to
path available continue
internal X2-C the
operation on the faulty connection
interface, breakage could only occur in
NRADJGNB between local gNB
case of internal and peer gNB.
communication failure
between 4G RAT C-plane
application(MeNB) in SBTS and 5G RAT
C-plane application (SgNB) in the same
LTEENB SBTS.
The internal transport path (SCTP) for

connection between gNB-CU-CP and
gNB-CU-CP gNB-CU-UP is broken.
This fault indicates that there is no Xn

connection with the remote gNB. No HO
gNB-CU based on Xn can be done.
This fault indicates that the gNB has
gNB-CU-CP initiated a full NG Reset procedure.
initiated a partial NG Reset procedure
due to a non-UE specific event in the
gNB-CU-CP gNB.

received a full NG Reset message from
gNB-CU-CP the AMF.

received a partial NG Reset message
gNB-CU-CP This
from fault indicates that the NGAP: NG
the AMF.
Setup procedure initiated by gNB-CU-CP
has failed that the NGAP:
after a configured numberNG of
Setup
retries upon non response orgNB-CU-CP
procedure initiated by failure
has failed from
response - the the
reason
AMF. could be any
gNB-CU-CP among the ones
The reason could be: defined in 3GPP.
- any reason among the ones defined in
3GPP.
- there is no slice in common between
SERVEDAMF gNB and AMF.
This fault indicates that the NGAP: NG
Setup procedure initiated by gNB-CU-CP
has failed because of no response from
gNB-CU-CP the AMF.
There is no X2-C link available for the
connection to the LTE eNB. No NSA UE
from this LTE eNB can connect to the
gNB-CU gNB.
received the message RAN
CONFIGURATION UPDATE FAILURE
gNB-CU-CP from the AMF.
This fault indicates that the guard timer
has expired in the gNB waiting for RAN
CONFIGURATION UPDATE ACK from
gNB-CU-CP the AMF.
This fault indicates that the guard timer

has expired in the gNB waiting for NG
gNB-CU-CP RESET ACK from the AMF.

received the message ERROR
gNB-CU-CP INDICATION from the AMF.
This fault indicates that the maximum

NRBTS number of X2 links is reached in the gNB.
This fault indicates that the F1AP: F1
Setup procedure initiated by gNB-DU fails
after a few retries upon lack of response
NRDU, gNB-DU; from gNB-CU.
This fault indicates that the F1AP: Reset
procedure initiated by gNB-DU fails after
a few retries upon lack of response from
gNB-DU gNB-CU.
This fault indicates that the F1AP: Setup
procedure initiated by gNB-DU fails after
a few retries upon failure response from
gNB-DU gNB-CU.

The transport that a Protocol
path (SCTP) error
for connection
has been detected in a received
between gNB-CU and gNB-DU is broken.F1AP
gNB-DU message
This mightorbeis because
reported of
from
an the gNB-CU.
unplugged
cable betweenpath
The transport them. Therefor
(SCTP) is no
connection
transport path available to continue
between gNB-CU and gNB-DU has failed
operation on the faulty
to be established. This connection
might be because
NRDU between
of an unplugged cable gNB-DU.
gNB-CU and between them.
There is no transport path available to
continue operation on the faulty
connection between gNB-CU and gNB-
NRDU DU.
The gNB configuration update procedure

FCT has failed in DU.
eNB and gNB involved in LTE NR DSS

NRCELL do not use compatible system releases.
The setup of EN DSS functionality failed

due to missing or incorrect Partner Cell
NRCELL configuration on partner RAT.
There is no connectivity to the remote

Common Resource Manager (CRM)
NRCELL function.
The CRM could not find a common

denominator for resource sharing based
NRCELL on LTE and/or NR configuration.
The
The connectivity to thetoremote
CRM Client tries changeCommon
the
NRCELL Resource Manager (CRM) hassharing,
cornerstones for the resource been lost.
while DSS was already successful
established and is running however the
CRM cannot find a common denominator
NRCELL for the sharing cornerstones.
The LTE-NR feature is deactivated for the
NRCELL partner EN DSS cell.

due to an internal DSS configuration
NRCELL problem.

due to a internal DSS registration
NRCELL problem.
This fault indicates that the cell parameter

configuration related to NR CELL is
NRCELL wrong.
A
In peer cellThe
Uplink: wasCRM
found, but the
Client triesparameters
to change
NRCELL on each side do not match.
the cornerstones for the resource sharing,
while DSS was already successfully
established and is running, however the
CRM cannot find a common denominator
NRCELL for the sharing cornerstones.
In Uplink: The CRM could not find a
common denominator for resource
sharing based on LTE and/or NR
NRCELL configuration.
A peer cell was found, but the parameters

such as share values or cell pair
NRCELL This fault is raised
configuration by 5G-CP-RT
on each side do noton
match.
expiry of cell activation timer at gNB-DU
(After F1 Setup Response /F1-DU
Configuration update ack message cell
An aperiodic
activation (emergency)
timer is started atswitch
gNB-DUwasto
NRCELL triggered, but could not be executed.
receive F1-CU Configuration update
message. If it is not received/on timeout
of timer this fault is raised). This fault
indicates that the gNB-CU is not ready to
gNB-DU-CP send the cell for activation.
This fault indicates that the E1AP: E1
Setup procedure initiated by gNB-CU-UP
fails after retries upon non response from
gNB-CU-UP gNB-CU-CP.

gNB-CU-UP gNB-CU-UP has failed to be established.
This fault indicates that the E1AP: E1
Setup procedure initiated by gNB-CU-UP
internal fails after receiving E1 Setup
gNB-CU-UP Failure response from gNB-CU-CP.
gNB-CU-UP gNB-CU-UP is broken.
ABIx
FSP
FBB This fault indicates that UP slice counter
gNB-CU-UP
DSP configuration is not updated correctly.
RET
ABIx
FR
FSP A failure has occurred in the trace
ANTL
FBB connection between the BTS and a third-
RAE
TCE
DSP party tool.
LNA
RET
ABIx
FHS
FR
FSP This fault indicates that a neighbor
PDU
ANTL
FBB
Tx reported by UE (NRREL) is not
RAE
gNB-CU-CP
DSP configured in the gNB upon A3/A5 event.
Rx
LNA
RET
AsiR
ABIx
FHS
FR
SFP
FSP
PDU A failure in the system has been
ANTL
OptIF
FBB identified.
Tx
RAE
LCR
DSP
Rx Details will be specified in release notes.
LNA
RET
AsiR
ABIx
FHS
FR
SFP
FSP A failure in the system has been
PDU
ANTL
OptIF
FBB
Tx identified.
RAE
LCR
DSP Details will be specified in release notes.
Rx
LNA
RET
AsiR
ABIx
FHS
FR
SFP
FSP
ANTL
OptIF
FBB identified.
Tx
RAE
LCR
DSP
LNA
RET
AsiR
ABIx
FHS
FR
SFP
PDU
ANTL
OptIF
FBB
Tx identified.
RAE
LCR
Rx
LNA
RET
AsiR
ABIx
FHS
FR
SFP
FSP
ANTL
OptIF
FBB identified.
Tx
RAE
LCR
DSP
LNA
RET
AsiR
ABIx
FHS
FR
SFP
PDU
ANTL
OptIF
FBB
Tx identified.
RAE
LCR
Rx
LNA
RET
AsiR
FHS
FR
SFP
ANTL
OptIF identified.
Tx
RAE
LCR
LNA
AsiR
FHS
SFP
OptIF
Tx identified.
LCR
AsiR
SFP A failure in the system has been
OptIF identified.
LCR Details will be specified in release notes.
ANTL excessively attenuated
RAE - the port at the connected far end node
LNA is switched off
FHS - the advertised technology capabilities
This loss of frame alarm
with auto-negotiation of bothis raised devices when at
PDU the local receiver is unable to detect the
Tx the Ethernet link do not match
frame
- the Ethernet alignment word of the
technology E1 signal.
at both devices All
Rx other transmission alarms related to this
AsiR at the Ethernet link is forced manually
signal
and notare suppressed.
compatible
SFP A failure
$UNIT in the system has been
OptIF -identified.the remote peerthe
indicates of affected
an Ethernet modulelink isfrom
Equipment
not auto-negotiationManagement capable (last element
or hasnotes. of
auto-
LCR Details
the DN). will
E.g.beTRMOD-1.
specified in release
negotiation
The alarm isfunction raised ifdisabled
thethe monitoredby
$INTERFACE
configuration indicates interface on
service
the module is unavailable
following when for example
This
all alarm is
network raised
paths are ifthethelabeling
User Event
unavailable.
on the
This
frontplate
Temporary
A
Probable Link OAM of
causesthe
buffer
PDU real HW
reaches
containing
for PDHBFD or the
configured
asessions
critical link
interfaces:
implies
corresponding that all individual
parameter inthe the of
MRBTS threshold
event
-The
the a cable flagislimit.
respective was received
cut groupor there isonno
represented Ethernet
cable by
Management small form-factor
Model. pluggable (SFP)
interface.
connected
$BFDGRPID
module is Thetowas alarm
the
are
expected is raised
interface
erroneous.
but notinpresent, with theorfirst
A
E.g. dead EIF1, peer IF1 detected one of the
detection
-could the of
electrical
not the flag.
signal
be recognized. is excessively
IPsec
This associations
alarm isforraised ofif the BTS. has
a loopback
The
attenuated
Example(s) following critical
alarm link
text: events
BFDGRP-10 are
There
Example(s) is no response
for alarm to
text: the "LOFrequests
onnode sent
BFDGRP -been
possible:
down
$UNIT
to the
the
configured
port at
indicates
peer, the
either
by
the a
connected management
affected
during the far end
module
IKE from
TRMOD-1,
application
-is Critical
switched IF2"
on
Event: the
offIPsec interface
either an (last mentioned
Errored Symbol in
Equipment
SA setup, Management
the SA setup, element
or during
-the
Period
of
DPD.
alarm
transmit
the DN). text.
Event,
and an Errored
receive
E.g. SMOD-1. cables Frame are Event,
mixed
Probable
$UNIT
an
up Errored cause:
indicates
Frame The
the interface
affected
Period Event, ator
module the anfar
from
$INTERFACE
end is not indicates
configured to be the ainterface
framed on
E1
Equipment
Errored
the module Frame Management
followingSeconds (last
Summary
the labeling element
on theof
Event
PPTT Note:
interface.
the DN).When E.g. IPsec
TRMOD-1. backup tunnel feature
was
Examples
frontplate detected. for alarmrealtext:
is enabled,of the
this alarm HW is not or the raised on
-$INTERFACE
Dying
Ethernet:
corresponding Gasp:
"LOS indicates
either
on the the
SMOD-1,
parameter intointerface
local or the
EIF2"
the
due
the to
module failures when
following trying
the labeling setup on the
remote
or
Management peer has
Model. a fatal error and is about
primary
frontplate IPsec
of the tunnel
real in or the
HW
to
"LOS
E.g. restart.
on
EIF1, IF1TRMOD-1, EIF3"
"Secondary_Active_Probing_Primary"
ETHLK, PPTT -corresponding
PDH:Link "LOSFault: on theparameter
local peerinhas
TRMOD-1, IF2"thedetected a
state.
Management Model.
physical
Probable link
causes:fault in receiving direction,
NOTE:
E.g. EIF1, The IF1alarm is not raised for IPsec
for example,
-tunnels
No SFP a LOS.
module iswith inserted in the SFP-
$LOOPTIMEOUT configured "IKEthe SA
Note:
based
connection slot. indicatesmode"
SFP establishment time
set to
period
In case
-responder in
The SFP only.a minutes
received after
OAMPDU which
module's interface contacts the
has inserted
more
IKEP loopback shallorterminate automatically.
than one critical
are corroded eventpreventing
dirty, flag set, the either
following
read access will to bethe reported
SFP module in the alarm: or
Example(s)
Link
A Fault
loopback bitfor
is set alarm
|Dying
requested
preventing detection of the module. text:Gasp
for anbit set|
Ethernet
"Interface
Critical
interface Eventunder
either test
set| on
bitlocally atTRMOD-1,
Reported the BTS, orIF2 the
PPTT for
Linkx2 minutes"
OAM client
Example(s) for alarm text: of the x
BTS is set into
x
loopback
"Missing mode
SFP Link
by
module theFaultremote
on SMOD-1, Link OAM EIF2"
Thisx
peer. alarm is raised if thex BTS fails to
or
download and store
$UNIT
"Missing indicates
SFP modulethe a
Link Certificate
Fault
affected
on TRMOD-1, module from
Revocation
x
Equipment List
Management(CRL), xor(last the CRL element
ETHLK EIF3"
On an interface for which
revokes
of the DN). a certificate
E.g. Link
SMOD-1. Faultthe
stored onLinkBTS, OAMor
functionality
CRL x content was
has switched
specific x on,
issue. no Link
$INTERFACE
OAM PDUs were indicates
received theduringinterface on
the"CRL
Refer
the to definition
module following Dyingof CM theGasp parameter
labeling on the
period
update
Always of
the 5 seconds.
failure reason" foror acritical
list of failure
frontplate
The SFP oflatest
has thereportedreceived
real HW the
a transmission link
CBRSCRLINFO_R, CRLINFO_R reasons.
event is
corresponding reported. parameter in the
fault
$UNIT condition
indicates and the has disabled the laser
$UNIT
Management
transmitter. indicates Model.the affected
affected module module from from
Equipment
Equipment Management
Management (last
(last element
element
E.g.
$UNIT
of the EIF1 indicates the affected module from
of the DN).
$PEER
Equipment DN). E.g.
E.g. SMOD-1.
indicates
ManagementSMOD-1.
either local (lastorelement
remote
$INTERFACE
$INTERFACE indicates
indicates the
the interface
interface on on
LOAM peer.
of
the the DN).
module E.g.
following SMOD-1. the labeling on the
the module
$INTERFACE following
indicates the labeling
the on
interface on the
frontplate
frontplate of the
the realreal HW or
or the
the moduleoffollowing
corresponding parameter
HW
the labeling
in
the on the
the
corresponding
frontplate of the parameter
real HW or in thethe
Management
Management Model.
Model.
LOAM corresponding
E.g. EIF1 parameter in the
E.g. EIF1
Management Model.
event
E.g. EIF1, $E indicates
IF1 the type of the critical
link event.
E.g:
ProbableCritical Event, Dying Gasp, link fault
causes:
LOAM or a combination
- The SFP is defective. of any of the events.

"SFP HW Failure on SMOD-1, EIF2" or
ETHLK "SFP HW Failure on TRMOD-1, EIF3"
All
-Example: the other
specifiedtransmission
CCMmaximum fault level alarms 5 prio
length related theto
5 cause
of
$INTERFACE
this signal indicates the
are suppressed. interface on
MAID_MISMATCH
cable is exceeded
the module following the labeling on the
3.
-frontplatetheMAID_MISMATCH
connector priority 5:connected A CCM is
$UNIT of theisreal
indicates
notHW
the when
properly
affected or the module from
received
to
This the unit
alarm with is matching
raised MDL a and
remote MAID,
defect
corresponding
Equipment parameter(last
Management in the element of
but
-indication
the the VLAN
receiver membership
or
is received. the far-end of the
transmitterreceived
Management
the DN). E.g. Model. It is sent by the
TRMOD-1.
frame
has
intermediate does
failed not match the VLAN
E.g.
$INTERFACE EIF1, IF1orindicates the far-end equipment
thethe interface on
configuration
-because the accumulated it detects of theBER aaddressed of
serious MA.
end-to-end
fault in the
the
Example:
E1
received module
path issignal. CCM following
too high the labeling
fault level 5 prio 5 cause on the
Probable
frontplate cause:
of the real TheHW interface
or the type has
MAID_MISMATCH
not
correspondingbeen configured to meet the framing
4.
Example(s)
Equipment
of the interface for parameter
REMOTEMEP_NOT_CONFIGURED, alarm
Management
at the text:
far
in
(last
end.
the
"EBER element
For on
E1 of
PPTT Management
priority
TRMOD-1,
the DN).4:E.g. A IF2"CCM Model.
TRMOD-1.is received with known
interfaces,
E.g. EIF1, the configuration
IF1 but the the of the far-end
MDL
$INTERFACE and MAID, MEPID is noton
node should beindicates E1 Multiframe. interface
configured
the moduleinfollowing the Remote MEP liston
the labeling ofthe
the
Probable
MA.
frontplate cause:
of the There
real HW isor a transmission
the
Example(s)
problem somewherefor alarm in text:
thein "LOMF on
Example:
corresponding CCMparameter fault level 5intermediate
prio
the 4 cause
PPTT TRMOD-1,
network along IF2" the E1 path and AIS is
REMOTEMEP_NOT_CONFIGURED
Management Model.
sent
5. instead
WRONG_CCM_INTERVAL,
E.g. EIF1, IF1 of user traffic. priority 4:
A CCM is received with known MDL,
Example(s)
MAID,
Probable andcause: for alarm
MEPID, The but text:
far theend"AIS
CCM has oninterval
a LOS,
PPTT TRMOD-1,
coded in the IF2"
LOF or AIS alarm on its receiving not
received CCM does
match
interface. the interval configured in the BTS.
Ex: CCM fault level 5 prio 4 cause
WRONG_CCM_INTERVAL
Example(s)
When an MEP for receives
alarm text: "RDI ETH-AIS
a valid on
PPTT 6.
frame and AIS is enabled, it will trigger3:an
TRMOD-1, REMOTE_CCM_DEFECT, IF2" priority A
CCM was not
AIS alarm containing the following received for 3.5 intervals
from
information: at least one remote MEP in the MA.
This
Ex: alarm is
is raised
level 5when the
This receivingfault
CCM
-localIPAddressalarm raised
interface if prio
negotiation
local3 cause
and peer ends
with the peer
REMOTE_CCM_DEFECT
disagree
-fails.MD level on the LCP configuration
P3SL; P3ML 7.
leading REMOTE_DEFECT_INDICATION,
toMAC LCP negotiation failure.
SSH
- Source access toaddress
BTS is enabled.
priority
$UNIT indicates 1 (lowest the priority):
affected An module
RDI flagfrom is
detected
The related in the CCM
configuration
Equipment Management (last element of frames from
parameters one are:
remote
acfcTarget,
In
thecase DN).peer.ofE.g. duallocalMruTarget,
core configuration:
TRMOD-1. and
P3LP -Example:
pfcTarget.
if both
$INTERFACE coresCCM arefault level
actively
indicates the5 prio 1 cause
interconnected,
interface
This
A alarm iscertificate
requested
REMOTE_DEFECT_INDICATION
this alarm means
raised
that
if thecould
SSH
PPP not
access beto on is
interface
the
not
retrieved module
operational from following
either
the the
when
certificate labelling
all the
authority on
PPP-the
The
both
front alarm
cores
plate text
is
of provides
enabled;
the real HW following
or the
links
(CA).
additional in theinformation:-
ML-PPP interface are not
corresponding
available,
A requested or the parameter
PPP-link
certificate could in the
supporting
not be the
P3ML, P3SL -$LEVEL
if the Secondary
Management
SL-PPP
indicates
interface Model. is
the maintenance
Core not is disconnected
available.
renewed
domain
from thelevel from the certificate
Primary Core, this alarm means authority
E.g.
(CA). IF1
&PRIORITY
that
$LEVEL SSHindicates access indicatestothe theMD the priority
Primary
level. of the
Core is
A
alarmrequested
enabled, certificate
it does not could not
reflect the setting on be
$MACADDRESS
retrieved because indicates
the number ofisn't valid
$CAUSE
the Secondary
corresponding indicates Core.
'macAddr'theThe fault condition
point
parameter inofthe
OAMMA,OAMMD,MRBTS certificates
the
for alarm
case when received
BTS from
Element the repository
Manager is
object
server model.
(RA)toorSecondary certificate Core authority
connected (see(CA) next
are
point). more than expected.
Example(s)
A requested for alarm text:
certificate
-"ETH
if alarm AIS isfault
displayed
on TRMOD-1, incould
BTS not Element
EIF1,
be
level
stored
Manager on connected to Secondary Coreof
the BTS to keep the amount
OAMMA l,certificates
mac aa:bb:cc:dd:ee:ff" storedCore on BTS within
when
The alarm Secondary is raised if the is disconnected
BFD state
maximum
from PrimaryisCorelimit. Operator cleanup
this means SSH of for
old,
the
unused session trust not AdminDown
chains may be and,
required.
Access
nevertheless, to Secondary no BFD Core packet is Enabled.
is received
A requested certificate is signed using a
CERTH at
weak the local
hash end
algorithm during the
either detection
MD5 time.
The
Note:
$BFDID
alarm
The is raised
SSH access
indicates the
if the
BFD
BFD
to the siteoris MD2.
state
identifier.
of the
session
disabledisbynot AdminDown
default. To mitigate and the the BFD
risk in
packet
field from the SSH
scenarios, far end shouldcontains only the be
Example
diagnostic for codealarm text:
= 'Control Detection
enabled
"BFD-10 for
down limited periods of time onTimean
FCT Expired'
as-needed and noinBFD
basis.
ingress" down Ingress alarm
The source and destination IP addresses
is present.
will be displayed in alarm diagnostic info
field
Example as below: for alarm text:
"Source
"BFD-10IP down addrin$BFDSCRIPADDR,
egress" Dest
BFD IP addr $BFDDESTIPADDR"
The source and destination IP addresses
will be displayed in alarm diagnostic info
field as below:
"Source IP addr $BFDSCRIPADDR, Dest
BFD IP addr $BFDDESTIPADDR"
the module following the labeling on the
frontplate of the real HW or the
corresponding parameter in the
Management Model.
E.g. EIF1, IF1
The RTT threshold alarm is raised in case
Example(s)
the average for alarm
value of thetext:RTT for this
"Auto-negotiation
TWAMP session from the last mismatch on1-min
SMOD-1,
EIF2"
Case or
Unicast (SMOD)
period equals or exceeds the configured
"Auto-negotiation
The
threshold. reference clock mismatch
monitoring on TRMOD-
has
ETHLK 1,
detected
$TWAMPID EIF3" a loss of ToPthe
indicates reference
TWAMP clock
The
signal alarm
received is raisedfromifthe themasterpacket clockloss ratio
session
equals identifier.
behind or $IPexceeds the configured
thresholdThe BTSvalue
-Example(s) does during
not receive the currenta reply from
observation for alarm
interval of text:
15 minutes.
TWAMP ToP
"RTT Master
threshold within a certain
crossed on time (5 sec)
TWAMP-10"
$TWAMPID
in which it has indicates
sent a sync the TWAMP request
session
message. identifier.
- The BTS receives granted message
Example(s)
rates from for alarm text:
TWAMP In
"PLR case theToP
threshold
MasterSynchronization
incoming
crossed
(sync message
on thatTWAMP-10"
rate, delay message
Status Message (SSM) is not rate), does notfor
received
match
This the
fault requested
is raised when rate by
BTS BTS.
attempts
a
NE certain
storestime Root period (configuredasthrough
CA Certificates trust to
-This
performThealarm
"ssmTimeout" BTS is raised
detects
certificate when
failure
enrollment
parameter), ofan Announce,
using
alarm CMP
is
anchors
Synchronization for its own trustMessage
Status chain and(SSM) for
Sync,
initialization
raised. Delay_Response
request and messages
detects from
that
peers.
is enabledWhen and own
theorreceived
any of those SSM
CERTH ToP
Vendor Master.
BTS certificate
$UNIT
certificates
indicates indicates are
lower about
clock tohas
the affected expire
quality
expired.
module
thanor requiredfrom
already
-Equipment
The BTS detects Management unacceptable (last clock of
element
expired,
(configured this alarm
through is sent.
class.
the DN). For example, SMOD-1.
"ssmAcceptanceLevel"
Example for alarm text: parameter).'ToP master
Note: This alarm is only generated for
service
$INTERFACE 10.58.130.251 indicates unusable'
the interface on
CERTH operator
$UNIT TA and
indicates not affected
the vendor TA.
module from
the
Equipmentmodule following
Management the labeling on
(last element of the
Case
front Multicast
plate the(SMOD)
of example,real HW or the
the
This
The DN).
alarm For is
reference clock raised if atSMOD-1.
least
monitoring onehasof the
corresponding parameter in the
PPP-links
detected
Management a belonging
loss of
Model. ToP to the
referenceML-PPP clock
P3ML $INTERFACE
interface
signal is
received not indicates
operational.
from the the
masterinterface
clock on
For
the example,
module EIF1.
behind $EIFfollowing the labeling on the
front Theplate
-Example(s) BTS of the real
detects HW of
failure or the
corresponding for parameter
alarm text:in Announce,
the
Sync,
"SyncE Delay_Response
SSM IP Timed messages from
During
Management
ToP
the
Master. Model.Out
address on TRMOD-1,
configuration,
SYNCE-x EIF3"
before allocation of new IPv6 addresses,
-For
the Theexample,
BTS detects
network
EIF1.
elementunacceptable
tests with DAD clock
class.
(Duplicate Addresstext: Detection) the direct
Example
Example for
for alarm
alarm network
text: 'ToPwhether master
attached
"SyncE transport
Quality Level Degraded on the
service
other EIF1 unusable'
already-configured network
SYNCE-x TRMOD-1, EIF3"
elements on the network use the same
Case Multicast (RU)
IPv6 addresses on their network IP
ToP
This reference
alarm
interfaces including clockthe
is raised signal
when on thevendor
CBRS
Link-Local. The
Ethernet
certificate port
on $RUPortNumber
the BTS
DAD detects those duplicated IPv6 is about toisexpire in
CERTH unusable:
90 days or and
addresses has expired.
prohibits the operation of
-this
Radio
IPv6 Agent
address did in
notthe detect
network any element.
This alarm
acceptable is
ToPtriggered
master when
at the CBRS
Ethernet Root
The
CA Alarm contains
Certificate stored thein corresponding
BTS as trust
port
IPv6 $RUPortNumber
address thetosystem for a predefined
anchor
time, or is about expire attempted
in 90 days to or
CERTH allocate
has expired.based on the manual
-configuration
Radio Agentoptions. failed toIfsynchronize
the alarm isto a
ToP master detected
reported for the IP interface, at the Ethernet
it will show port
$RUPortNumber.
the Link-Local IPv6 address the system
TOP Example for alarm text 'ToP master
failed to allocate.
RMOD service RU eCPRI port #1 unusable'
Example for alarm text: Dup Addr
detected
2001:0db8:85a3:0000:0000:8a2e:0370:7
IPADDRESSV6;IPIF_R 334
BTS has entered IPsec emergency
bypass active state where configured
IPsec policies are ignored, and all traffic
IPSECC is sent unprotected.
- INVALID_MAJOR VERSION
-This
"IP INVALID
Traffic _IKE_SPI
alarmCapturing
will be triggered ongoing when BTS
on SMOD-
has automatically
1, LMP, aa:bb:cc:dd:ee:ff" switched to the
-secondary
"IP
This INVALID_MESSAGE_ID
Traffic
alarmBTS IPsec
Capturing
is raised tunnel. ongoing the on SMOD-
A specific local when operator BTS
account sendshas
1,
or
been EIF2,
receives aa:bb:cc:dd:ee:ff"
locked. the . following
The local notification
operator as a
account
-As
"IP aTraffic
resultto ofan failure
Capturing in at least one
response
could beIPsec
UNSUPPORTED_CRITICAL_PAYLOAD
primary either IKE_AUTH
for
tunnel theongoing
or system
PS
or on TRMOD-
module
tunnel, BTS
1,
CREATE_CHILD_SA
(SM) EIF3, aa:bb:cc:dd:ee:ff"
or for ASiR-sHUB. request message.
or
hasFAILED_CP_REQUIRED automatically switched over to
The
secondary number of failed login attempts for a
Example
The failure
SM/ASiR-sHUB forIPsec
alarm
notifications tunnel
local textoperator orfile
terminating
inincludes mode: the on
account
IPNO -->
secondary
"IP
following: When the BTS
security gateway.
Traffic Capturing sendsongoing" or receives a
has
As aexceeded
failure notification
result the as
of secondary threshold
a response
tunnel andrecovery
the
to an
account
IKE_AUTH
when PShas tunnelbeen
request is lockedmessage.
active on the
and The failure
Primary
-Connection
SM/ASiR-sHUB NO_PROPOSAL_CHOSEN to BTS . No through
further Local
logins will be
notifications
tunnel is failed,include:
BTS has automatically
The
Management
permitted alarmfrom is raised
Port
this when on
(LMP)
account theuntil
IKEthe
either
switched
- TS_UNACCEPTABLE
authentication back credentials
to secondary IPsec
provided tunnel
by the
FCT,FR Primary
account
-terminating INVALID_SYNTAXor
is Secondary
unlocked. Core is
peer on secondary security
established, and the access is granted by
gateway.
-BTS
are INVALID_SYNTAX
not valid,
- INVALID_MAJOR after userBTS sends
authentication.
VERSION or receives
Port
AUTHENTICATION_FAILED
number is the port reported innotification fault name
Note:
-as PS tunnel
INVALID_MAJOR
response is not
to IKE_AUTH supported
VERSION request in
in
-standalone alarm.
INVALID _IKE_SPI
IKEPROTGRP message. 5G classical BTS.
-In
NOTE: INVALID
case The _IKE_SPI
of dual alarm core is configuration:
not raised for IPsec
- INVALID_MESSAGE_ID
-tunnels
R&D if both configured
cores are
Service Ports are enabled,
with "IKE
actively SA
interconnected,
so
-connection
this INVALID_MESSAGE_ID
alarm establishment
means that LMP mode"
access, setvia to
-
testing applications can be connected to
IKEP responder
port reported
UNSUPPORTED_CRITICAL_PAYLOADonly. in faultports. name in alarm, to
BTS
- through those
both
NOTE: coresTheisalarm establish. is not raised for IPsec
UNSUPPORTED_CRITICAL_PAYLOAD
tunnels configured with "IKE SA
-In ifcase
connection the Secondary establishment Core is disconnected
mode"
-from of dual
SINGLE_PAIR_REQUIRED
the Primary
core
Core,
configuration:
this or set
alarm means
to
IKEP -responder
if both
FAILED_CP_REQUIRED coresonly are actively interconnected,
that
this LMP access
alarm means via
that port
R&D reported
Service inPort
fault
NOTE:
name inThe
alarm alarm to is not
the Primaryraised for IPsec
Core is
access
tunnels to both
configured cores is enabled;
established, it doeswith not "IKEreflectSA the access
connection
on the Secondaryestablishment Core. The mode"point set
isn'tto
SECPOL -responder
if the Secondary only. Core is disconnected
valid
This
from alarm for case
the is an
Primary when alert
Core, BTS Element
indication
this alarm that the
means
Manager
that R&D Service Port access to the Core
IPSec is
expert connected
mode has to Secondary
been activated by
(see
BTSEM.
Primary nextCore point).
The IPSec
is enabled, expertit mode does not allows
-reflect
if alarm
advanced theisconfiguration
displayed
setting on the in forBTS Element
testing
Secondary and Core.
IPSECC Manager
The point isn't valid for case when Core
trouble connected
shooting purposes.to Secondary BTS
when
Element Secondary
ManagerCore is disconnected
is connected to
from
This
Secondary Primary
alarm is Core
triggered
Core detects, this
(see next means
when LMP is
ETH-CC
point).
The
Access ASiR-sHUB
via port reported using
in fault carrier
name
enabled
-state,
if alarm that and local
issomeone
displayed MEP receives
isinlocally
BTS Elementa validin
connected
alarm
ETH-CC to Secondary Core is established.
FR Manager
to itsalarm
The LMPframeconnected
port.
is raised
from to remoteSecondary
if primary,
MEP with Corea
secondary
sourceSecondary
when MAC Address Core different
is to its
disconnected
or
If PS tunnel
more
manually than IPsec
one
configured FQDN
session or means isfails to resolve
established
previously
from
or Primary
service Core
provides this
invalid R&Dlearned
response.
via
MAC
Service the LMP
address.
Port at the same time only one
The
alarm alarm
is is Access
reported.raisedThe to Secondary
under alarm theisfollowing Core is
cleared
It contains the following information:
Enabled.
conditions:
FCT when
$ID last session
indicates the remote is terminated. MEP Id with
1. IKEP instances are configured
configured
Note: R&D under
Service
local tunnel end point, remote Maintenance
Ports access on BTS
tunnel
Association(MA).
are disabled by
endpoint FQDN(s) or IP address anddefault, they shall only be
$LEVEL
enabled
2. Local tunnel indicates
for limited andthe periods
remoteMaintanenceof time end
tunnel on as-
FCT Domain
needed
point IP Level (MDL).
basis.
address combination are not
Failed
$MAID FQDN
indicates details will be displayed in
the instances.
Maintenance
unique
alarm across
diagnostic IKEP info field as below:
Association Id.
"Remote tunnel
$MACADDRESS indicates the source Endpoint
MAC address in the CCM frame received
IKEP $remoteTunnelEndpoint2"
from remote MEP.

"CCM MAC mismatch
Non-Unique MEPwill
RTEP details 1111,
be MDL 1,
OAMMA MA 15, MAC aa:bb:cc:dd:ee:ff"
displayed in alarm diagnostic info field as
below:
"Remote tunnel Endpoint
IKEP $remoteTunnelEndpoint2"
The Ethernet link $ETHLK details and
cause $CAUSE will be displayed in alarm
diagnostic info field as below:
" From $PRIMARY_LINK to
$SECONDARY_LINK , $CAUSE".
There
$CAUSE is no XP connectivity
indicates to a or
either "LOS" remote
"LACP
Network
failure". Element, the XP connection
setup to the remote Network Element has
E.g: From
failed as the maximum number of
MRBTS-1/TNLSVC-1/TNL-1/ETHSVC-
supported
1/ETHLK-1XP connections was
to MRBTS-1/TNLSVC-1/TNL-
LAGRP exceeded.
1/ETHSVC-1/ETHLK-2 , LOS
Note:
The transport path (SCTP) for the XP
This
The alarm will
source be triggered
Network Element when
ID (NEID)
connection
automatic has failed
switchover to establish
happens due to
and
SCTP: destination
INIT not IP address
successful. will tobepublic
IKEPROTGRP safety tunnel per IKEPROTGRP.
displayed in alarm diagnostic info field as
below:
Note:
"Source
The source Network
NetworkElement
Element ID ID (NEID)
$SOURCENEID,
The destination
and transport path Destination
(SCTP) for
IP address willIPconnection
Address
be
XPIFREMOTE_R $DESTIP"
to a remote
displayed Network Element info is broken.
There
This is noinbe
might
alarm
XP diagnostic
connectivity
because of antounplugged
field as
a remote
below:
Network
cable
"Source aElement,
or Network the
missingElement XP connection
configuration
ID Networkon the
setup
remote attempts to the
Network Element. remoteThere is no
$SOURCENEID,
Element Destination IP
has failed after several retries. address
XPIFREMOTE_R transport
$DESTIP"path available to continue
operation on the faulty connection with
Note:
the The destination
remote IP address will be
There
displayedis noinNetwork
XP
alarm
Element.
connectivity
diagnostictoinfo a remote
field as
Network
below: Element, the XP connection
Note:
setup The
to the destination
remote NEID and
Network Element has
XPIFREMOTE_R "Destination
destination IPIPaddress
address $DESTIP"
will be displayed
failed due to incompatible message sets.in
alarm diagnostic info field as below:
"Destination
Note: Network Element ID
$DESTNEID,
The source and Destination
destination IPNetwork
address
XPIFREMOTE_R $DESTIP"
Element ID (NEID) will be displayed in
alarm diagnostic info field as below:
"Source Network Element ID
$SOURCENEID, Destination Network
XPIFREMOTE_R Element ID $DESTNEID"
Troubleshooting file is received from the

TBD NE.
State Unit Status
Start / Cancel Working
Start Degraded,Out of order
Start / Cancel Out of order
Start Out of order
Start / Cancel Degraded,Out of order
Start / Cancel Out of order,Working

Start / Cancel Degraded,Working
Start Out of order
Transient Working
Start Out of order
Start / Cancel Degraded
Start Out of order
Start Out of order

Transient Working


Start Working
Start Degraded
Start Degraded
Transient Working




Start Out of order,Working

Start Out of order


Transient Working
Start Out of order
Start Degraded

Start / Cancel Degraded,Out of order,Working
Start Degraded
Start Degraded

Start Working
Start Out of order
Start Out of order
Start Out of order

Transient Working
Start Critical
Start Working
Start Out of order

Start Out of order
Start Working
Start Out of order


Start Degraded,Out of order,Working
Start Out of order
Start Out of order
Start Out of order
Start Degraded


Start / Cancel Degraded,Warning,Working
Start / Cancel Degraded,Warning,Working
Start Degraded
Start / Cancel N/A
Start / Cancel N/A

Start / Cancel N/A
Start N/A
Start / Cancel N/A
Start / Cancel N/A
Start / Cancel N/A
Start / Cancel N/A
Start N/A
Start N/A
Start / Cancel N/A
Start N/A
Start / Cancel N/A
Start / Cancel N/A

Start Out of order
Start / Cancel N/A
Start Working
Start Degraded
Start Out of order

Start Out of order
Start Out of order

Start Out of order
Start Working
Start Out of order
Start Out of order

Start Working
Start Degraded
Transient Working

Start Out of order
Transient Working

Start Degraded
Start Degraded
Start Out of order

Start Working
Start Out of order
Start Degraded
Transient Working

Start Out of order
Start Working
Start Working

Start Degraded
Start Working
Transient Working

Start Out of order
Start Out of order
Start Out of order

Start Out of order
Start Degraded

Start Working
Start Working

Start Out of order
Start / Cancel Major
Start Degraded,Working
Start / Cancel Minor

Start Degraded

Start Out of order
Transient Warning



Transient Working
Transient Working
Start / Cancel Critical
Transient Working
Start Critical
Start Out of order
Start Major

Transient Warning
Start Out of order
Start Working

Transient Working
Transient Out of order,Working

Transient Working
Transient Working
Transient Working
Start Working

Transient Working
Start Out of order

Transient Working

Start Out of order
Transient Working
Transient Working
Transient Working
Transient Working
Transient Working
Transient Working
Transient Working
Transient Working
Transient Working

Start Out of order
Transient Working
Transient Working
Transient Working
Transient Working
Transient Working
Transient Warning
Transient Working
Transient Working
Start Working
Transient Working

Start Out of order

Start Working

Transient Working
Transient Working
Transient Working
Transient Working
Transient Working
Start Degraded
Start Out of order
Start Degraded
Start Degraded
Transient Working
Start Out of order
Start Out of order
Start Out of order
Start Out of order


Transient Working
Transient Working
Transient Working
Transient Working
Transient Working


Transient Warning
Start Out of order
Start Out of order


Active / Cleared Out of order




Start / Cancel Degraded,Warning
Transient Warning
Unit Status Attributes Effect
AirScale BTS TDD, AirScale BTS FDD, Flexi
SBTS, AirScale SBTS:
This fault does not immediately affect the
operations of the BTS, but it is a notification
that the BTS master clock frequency
deviates from the used reference frequency
more than in normal circumstances.
Flexi SBTS, AirScale SBTS: The
If operation
theBTSFSP/ABIx of the BTS decreases.
The masterupdate fails,
clock tuning the BTS
continues
- Out of order (FCT, capacity drops. If the optical
regardless of the alarm, but because theinterface FPGA
FSP/FBB/ABIx when shutdown) SW update fails, communication
BTS master clock adjustment is quite slow to to radio
- Degraded(FSP/FBB/ABIx modules
filter does not work,
the instabilities and
of the the BTSclock
reference is not
otherwise) All products:
operational.
5G BTS, Flexi BTS FDD, Flexi interface,
- The module it takes some time
in question (even
is out several
of use. This
BTS TDD, AirScale BTS TDD, hours)
fault cancels all the active faults for the to be
before the BTS operations start
AirScale BTS FDD, Flexi SBTS, affected.
same module.
AirScale SBTS:
Working Fault impacts
AirScale BTS only
FDD,LTE and NR
AirScale cells.
BTS TDD,
AirScale SBTS, Flexi BTS FDD, Flexi BTS
TDD, Flexi SBTS:
- In case of FHS and AFAA CPRI when
IPsec failure occurres, connection is lost.
5G BTS:
The resources provided by the unit cannot
All cells
be used are
untilnot
anoperational.
automatic SW update is
finished.
Out of order (1. FCT Flexi BTS TDD, AirScale BTS TDD, Flexi
2.FSP/FBB/ABIx when shutdown BTS FDD, AirScale
or when FSP/FBB/ABIx critical The wcdma cells areBTS not FDD, Flexi SBTS,
operational.
AirScale SBTS:
core is faulty 3. FR) The
The BTS capacity
resources possibly
provided by decreases;
the module some
cells might
cannot be disabled.
be used, which means that some
Degraded
5G BTS: Out(FSP/FBB/ABIx
of order features might not work.
otherwise) The BTS is out of order.
Flexi BTS TDD, AirScale BTS Forcells
All FR modules, the resources
are disabled. All ongoing provided
calls areby
TDD, Flexi BTS FDD, AirScale the module
dropped. Newcancalls
be used if critical
are not possible. DNBAP
BTS FDD, Flexi SBTS, AirScale functionality for to
link state is set cell set-up
out is available.
of order to avoid In
SBTS: case of FR modules
redundant alarm reporting.with factory SW loaded,
FCT (HW rel.3), FCT (HW rel.4), other alarms can be reported later for this
ABIx, FSP = Out of order FR module (or FR modules further in the
chain) when the RF modules will be
FR(the cell cannot operate)= Out All cells are
incapable todisabled. All ongoing
provide services calls for
properly are
of order dropped.
the cells. New calls are not possible.
FR(the cell can operate)= Working If the fault is reported for an FR module, the
RF LED and BTSSM LED display status
FHS = Out of order cannot be aligned.
The SW update to this BTS might not be
If the faultwithout
possible is reportedspecial foractions.
the FR module,
The BTS
BTSOM does
continues not knowwith
its operation the real state
the old of the
software.
FR module, and thus, BTSSM keeps the FR
5G
LED BTS:
display
AirScale
The BTSdisabled
SWstatus
update FDD,to this
(grayed).
AirScale
BTS of BTS
might
The reason
TDD,
not be
for the
AirScale inconsistency
SBTS, Flexi BTS the
FDD, Flexi FR LED
BTS is
possible
the without
restriction special actions.
of RP1 communication only to The BTS
TDD,
continuesFlexiitsSBTS:
operation with the old software.
SW
If themanagement
SW download procedures
to any HWinunit case of an
failed,
SW SBTS
the mismatch situation.
continues Therefore,
operating with there
the is
AirScale
no BTS to
possibility FDD,
align AirScale
the RF LEDBTS andTDD,BTS
currently
AirScale running SW version.
SM LED SBTS, display Flexi status. BTS FDD, Flexi BTS
TDD, Flexi SBTS:
If
If the
the SWSW activation
download failed to anyon HW FCT,
unitthe SBTS
failed,
continues
The operating with
the SBTS continues operating with the old
BTS continues its the
operation currently
with the
5G BTS, AirScale BTS FDD, running
file(s) orSW
currently with version.
runningno filesSW fromversion. O-RAN compliant
AirScale BTS TDD, AirScale RU.
SBTS, Flexi BTS FDD, Flexi BTS If If the
the SWSW activation
activation failed failed on on another
FCT, theHW SBTS
TDD, Flexi SBTS: unit (for example, RF unit),
continues operating with the currently the following
Working
5G BTS, -AirScale
if incompatible software events
BTS FDD, running will
SW happen:
version.operations with the old
version has been detected on the The
1. TheBTSSBTScontinues
restarts and operates with the
AirScale BTS TDD, AirScale software.
same unit and corresponding fault new SW
SBTS, Flexi BTS FDD, Flexi BTS If the SW activation version installed.
failed on another HW
23:EFaultId_IncompatibleSwVersio
TDD, Flexi SBTS: 2. Eventually,
unit (for example, RF if the SBTSunit),isthe integrated
followingto
nAl has been already reported. the NetAct,
Working - if incompatible software events will happen: after the automatic recovery SW
update, the SBTS restarts
version has been detected on the 1. The SBTS restarts and operates with the and operates with
Degraded - in any other case. the
same unit and corresponding fault AirScale old
new SW BTS SW version
version TDD, installed.
AirScale BTS FDD,
installed.
23:EFaultId_IncompatibleSwVersio AirScale SBTS,
2. Eventually, Flexi
if the SBTSBTS is FDD, Flexi BTS
integrated to
nAl has been already reported. TDD, Flexi SBTS:
the NetAct, after the automatic recovery SW
The
update,BTSthe doesSBTS not restarts
send any andfaults that are
operates with
The
relatedbattery
to the backup
blocked unit is partly
cell, or the or
modules
Degraded - in any other case. the old
completely SW version
in use. installed.
The intelligent
commissioned to the blocked cell,shutdown
to the
operation has started.
network management system (NMS). If the main power is
Fault-
not restored, the cells,
sending to the BTS Element Manager is sectors, and carriers
are
alwaysshutenabled.
down accordingThe faulttocancellations
the predefined are
parameters.
always sent to the NMS.
Calls through
The BTS doesthe
notblocked
send any.cellfaults,
are other
transferred to another cell. New calls cannot
than the transport faults, to the network
be established through the blocked
management system (NMS) when the cell.
BTS
is blocked. The fault cancellations are sent
to the NMS.
All
TDD,cells are disabled.
The operator
5G BTS, (BTSBTS
AirScale Element
FDD,Manager
AirScale and
BTS
NMS) is informed about the autonomously-
triggered
BTS TDD,recovery reset.
Flexi SBTS:
SMOD is the fault source: BTS startup is
5G BTS, AirScale (S)BTS, Flexi terminated.
(S)BTS: BBMOD is the fault source: FSP is not taken
Out of order into use.
Default
5G BTS,values are BTS
AirScale usedFDD,
for the cell. The
AirScale cell
BTS
operation is not impacted/affected.
BTS TDD, Flexi
Depending on theSBTS:
reported severity, the BTS
Depending on the
capacity might havereported severity,
decreased or thethe BTS
BTS
capacity might have decreased,
might be not operational at all. or the BTS
might not be operational at all.
For resources that are not in use (not
commissioned), lack of support is reported
by minor severity alarm (BASE STATION
NOTIFICATION).
1. The gain control feature is lost, possibly
generating an interference in the network.
2. The NBAP common measurement

message is incorrect because of missing
measurement data from the Radio Module.
3. The cell supported by the radio module,

which is visible as alarm source in the alarm,
is disabled or degraded.
Degraded(FSP/FBB otherwise) If the source is DSP, then the cell supported
Out of order (FSP/FBB when by the DSP might be degraded or disabled.
shutdown) If the the
After source
cell is Rx/Tx,
block then possibly
request, some
RNC should
Out of order (RX/TX) carriers weren't configured.
start handover from the blocked cell to other
cells because NodeB did not receive
response from RNC. Handing traffic over to
another cell might not work. The cell, which
should be blocked, might still be operational.
The cell is disabled.
The cell setup is rejected.
During Cell Setup, Common Transport

The cell supported
Channel Setup, CellbyReconfiguration
radio module, which
and is
visible as alarm source
Common Transport Channel in the alarm, is
disabled or degraded.
Reconfiguration procedures, the request is
rejected. During Cell Reconfiguration and
Common Transport Channel
Reconfiguration,
The minimum HSUPA the cell continues
capacity, to is
which
operate with the previous configuration
based on the commissioning parameters, data.
is
not fully guaranteed. The HSUPA resource
handling still works dynamically in addition to
the partially reserved minimum capacity for
the HSUPA.
Cell capacity is decreased.
Cell capacity is decreased.

Degraded(FSP/FBB/ABIx
otherwise) Some baseband processing resources are
Out of order (FSP/FBB/ABIx when not working, a cell or cells are not
shutdown) operational, or the BTS is not operational.
BTS HSUPA Capability is degraded in the

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

cell where the Parallel Interference
Cancellation (PIC) feature is active.
otherwise) The WCDMA RAT capacity might decrease,
Out of order (FSP/FBB/ABIx when or the WCDMA RAT might go completely out
shutdown) of order.
Out of order: in cell setup phase Cells cannot be set up, or there is no impact
Working: runtime, when new PIC to cell operation if the fault is triggered
pool configuration is ignored. runtime.
Not enough CCCH Processing Set licenses

commissioned to the cell. Affected cells are
disabled.
otherwise)
Out of order (FSP/FBB/ABIx when DSP is not operational and cells supported
shutdown) by
Thethe
cellDSP are disabled.
is temporarily degraded, and all
connected UEs are informed of the status of
During
the cell.HSDPA cell setup:
All ongoing calls are unaffected, but
the UE is unable to establish new calls.
Operator
Otherwise, canthestill
celluse the carrier aggregation
is disabled.
functionality. However, HSDPA cell setup is
rejected.
Some
Duringend-users will not experience
carrier aggregation runtime the
improvement
activation: in the uplink due to HS-RACH.
Operator cannot use carrier aggregation

functionality due to a wrong carrier
aggregation configuration.
Operator can still use the carrier aggregation
functionality. However, new carrier
aggregation group ID is not taken into
account.
NBIC will not be working for the specified

LCG.
DSS will not be working for any LCR in the

specified LCG.
Cell
When visible
WCDMA as alarm
LTE source is disabled.
Dynamic/Static Shared
Spectrum configured the paired LTE cell
uses only its dedicated spectrum and is not
able to use shared part of paired WCDMA
cell spectrum.
Dynamic Spectrum Sharing feature
functionality is restricted. Paired LTE cell
uses dedicated spectrum only and is not
able to share spectrum with paired WCDMA
cell.
uses dedicated spectrum only and is not
able to share spectrum with paired WCDMA
cell
The BTS memory operations (for example,
the software download and parameter
None
updates) are not stable.
The
The In Service
BTS memoryTime Indicator(for
operations (ISTI) value
example,
for HW Repair Center might not be
the software download and parameter correct
or readable.
updates) are not stable.
The In Service Time Indicator (ISTI) value

for HW Repair Center might not be correct
or readable.
None
This fault has no impact. It indicates that the
Flexi Zone Micro BTS, Flexi Zone Access
Point, or Flexi Zone SFN Antenna has been
reset because of a power cycle.
Temperature inside a module may be

raising.
Temperature and humidity cannot be

controlled.
Temperature and humidity cannot be

controlled.
Temperature/humidity inside sub-rack may

be abnormal
Out
FlexiofBTS
order (FSP/FBB/ABIx
FDD, Flexi BTS TDD,
critical core is
AirScale BTS TDD,faulty)AirScale BTS The BTS capacity decreases. The digital
Degraded
FDD, Flexi(FSP/FBB/ABIx
SBTS, AirScale SBTS: signal processing
Flexi BTS (DSP)
FDD, Flexi does
BTS notAirScale
TDD, work
otherwise)
Out of order (FSP/FBB/ABIx correctly.
Flexi BTS TDD, AirScale BTSwhen BTS TDD, AirScale BTS FDD, Flexi SBTS,
shutdown)
TDD, AirScale BTS FDD, Flexi AirScale SBTS:
SBTS, AirScale SBTS, Flexi BTS The BTS capacity decreases, or the BTS is
FDD: not operational. The digital signal processing
otherwise)
Out of order (FSP/FBB/ABIx when (DSP) does
Flexi BTS not work
TDD, correctly.
AirScale BTS TDD, AirScale
shutdown) BTS FDD, Flexi SBTS, AirScale SBTS, Flexi
BTS FDD:
Degraded(FSP/FBB/ABIx The BTS is not operational, or its capacity is
otherwise) degraded.
No direct effect on the BTS operation.
Note that the subrack fan does not stop

even if the door is open.
There is no actual effect to the BTS
functionality: this is user-specific.












































Some configured EAC_IN lines cannot be

used.
5G BTS, AirScale BTS FDD,

AirScale BTS TDD, AirScale No EAC line can be used on this SMOD.
SBTS, Flexi BTS FDD, Flexi BTS
TDD, Flexi SBTS:
Out of order (1. FCT, 2. FTM 3.FR,
Working
4.MHA, 5. if the
RET.fault is notified by
6.FSP/FBB/ABIx
FR,
when shutdown or when cases.
out of order in other The BTS is not operational.
FSP/FBB/ABIx critical core is Some action inside the BTS is interrupted.
faulty) The BTS does not operate normally. The
Degraded (FSP/FBB/ABIx fault is in the unit reported in the fault source
otherwise) field.
The BTS can operate properly for months, or
even a year, when being in the 5% margin
area, but eventually the DAC value reaches
5G BTS,
the AirScale
adjustment limitBTS(0 orFDD, 4095), AirScale
and theBTS
5G BTS, AirScale BTS FDD, TDD,
OCXO AirScale
cannot SBTS,
follow theFlexi BTS FDD,
synchronization Flexi
AirScale BTS TDD, AirScale BTS TDD,
reference Flexi
signal SBTS:
beyond the limit. When the
The
DAC BTS
value capacity
is 0 or might
4095,
SBTS, Flexi BTS FDD, Flexi BTS 5G BTS, AirScale BTS FDD, AirScale BTS decrease.
the effect The cell
depends
TDD, Flexi SBTS: with
on
TDD, the
the incorrect
network
AirScale configuration
Flexi BTSissetting
synchronization
SBTS, not Flexi
FDD,
working.
defined in the
Out of order (FSP/FBB/ABIx when BTS TDD, Flexi SBTS: BTS commissioning.
shutdown, FCT, FR, OptIF, FHS) This fault prevents the BTS from functioning.
Effects
Dependingon Frequency
on <x>, some Synchronization:
processing
Degraded(FSP/FBB/ABIx Assuming
Flexi BTS that
FDD, the
resources, some cells, or BTS
Flexi BTS reference
TDD,
the signal
Flexi
entire BTS has
SBTS,
is
otherwise) the
out correct
AirScale accuracy when the DAC value
SBTS:
of order.
reaches the adjustment
If other references limit of 0 the
are available, or 4095
Flexi BTS FDD, Flexi BTS TDD, (meaning the alarm indication
synchronization reference source changes is real and not
Flexi SBTS, AirScale SBTS: This
causedfault
to anotherbycan an prevent
incorrectthe
source. BTS fromthe air
reference),
Degraded - when no other functioning
interface
Tuning then when
starts to the
follows driftRadio
thisfromnewtheUnit or FHSvalue,
correct
reference. Unit
reference clock sources are is needed for the required
and after a while (weeks or months), the cell configuration.
available accuracy limit is notare
If other references met not anymore.
available, Even
the in
Working - when there is at least that stage, the BTS might
BTS master clock (OCXO) tuning is halted, still be
one more working reference clock operational,
and
The the BTSclock
system
but the system performance
synchronization
frequency dropstotodrift
starts
source available. might
holdoverdrop,mode.affecting, for example, the
and the air interface frequency accuracy
handovers.
starts to degrade. The BTS might work
properly
Effects on forPhase
a few Synchronization:
days without any signs of
a problem, but
When the DAC value the network
reaches performance
the
might start to gradually decrease.
adjustment limit of 0 or 4095, the features,
which require Phase Synchronization
become non-operational because the OCXO
cannot adjust the phase synchronization
anymore.
TXs that go
The BTS through
is not the affected antenna
operational.
line are disabled.
The
The MHA is degraded
following andas
will happen the RX signal
a result:
level
1. The cell that has lost its onlysize
might be decreased. The TX, of
or the
has
cellprimary
no might beTXreduced.
available, is disabled.
2. The cell that still has its primary TX
available,
The MHA is butfaulty,
has lost
andits secondary
the TX, is
RX performance
degraded. Such cell The
might be degraded. alsosize
loses
of its
theMIMO
cell or
5G BTS, AirScale BTS FDD, VAM
mightcapability.
be reduced.
SBTS, Flexi BTS FDD, Flexi BTS Note: For CPRI-A radios, the antenna line is
TDD, Flexi SBTS: not disabled when the Major VSWR alarm is
CPRI-A: Degraded (as long as The antenna
reported. lineradios
These is not have
operating correctly.
internal
VSWR level is below the HW limit The cell capacity might be decreased.
protection mechanisms, so the VSWR alarm
defined in the radio) does not indicate imminent harm to the
Otherwise: Out of order hardware. The TX for the antenna line is
(mandatory resources for the cell marked as degraded, and the associated
are lost) cell
The remains on air.at the antenna is
output power
decreased because of the reflection of the
signal in the TX path. The antenna is not
working optimally. The size of the cell might
be reduced.
The operating performance of the RX path is

decreased.
The signal path is unusable. The cells using
the faulty unit might not work.
The signal path is unusable. The cells using

the faulty unit might not work.
The BTS capacity might be decreased.
The antenna line device does not work

properly. The cell operation is degraded.
Degraded - when fault affects

basic services of the base station The BTS capacity might be decreased.
and cell is working in degraded
mode The unit might be started with an old SW
Out of order - Cell is not version and therefore, is not compatible with
operational. any other units.
Degraded: unit still has enough

available and needed resources to Secondary core startup is halted.
operate. This status applies only
for GSM cells. The BTS capacity is affected. The cell fails if
Out of order: unit cannot provide necessary resources are no longer
service anymore; available, otherwise it is degraded.
The gain of the MHA might be decreased.
The cell performance might also be
decreased. The real level of gain provided
by the MHA cannot be determined.
The MHA does not provide gain in the RX
path. The cell performance might be
decreased. Within the recovery action, the
missing gain is compensated by the
additional gain delivered by the LNA in the
Radio Module.
Some antenna line device functions might

not work properly.
5G BTS:
Some
If otherantenna line are
references device functions
available, the might
not work properly.
synchronization reference source changes
to another source. Tuning then follows this
new reference.
If otherantenna
Some references
line are not functions
device available, might
the
BTS master
not work clock (OCXO) tuning is halted
properly.
and the BTS synchronization drops to
holdover mode.
Some
AirScale antenna
BTS FDD, line device
AirScale functions
BTS TDD, might
not work SBTS,
AirScale properly. Flexi BTS FDD, Flexi BTS
Default
TDD, FlexivaluesSBTS:for the internal delays in the
BB
If other references The
card are used. effects onthe
are available,
functionality include:
synchronization reference source changes
5G BTS, AirScale BTS FDD, 1.
to Cell boundaries
another source; cannot be defined
the tuning follows as
The antenna
accurately as line
with device of use.this
is outinternal
measured delay
AirScale BTS TDD, AirScale new reference.
SBTS, Flexi BTS FDD, Flexi BTS values.
If other references are not available, tuning
TDD, Flexi SBTS: 2.
does3GPPnot Dedicated measurement
follow the external (RTT
reference any
Degraded (there is no other measurement)
more. accuracy is lower than with
available and usable input measured
Clock internal delay values.
If othertuning is halted,
references are and the BTS
available, the
reference source to be selected) continues its operation
synchronization based
reference on the
source internal
changes
Working (SBTS is synchronized oven
to oscillator.
with another input reference 5Ganother source. BTS
BTS, AirScale Tuning
FDD,then followsBTS
AirScale this
new
TDD, reference.
AirScaleonly SBTS,
source) Fault impacts LTEFlexi
cells. BTS FDD, Flexi
Degraded (other clock is not If other
Calls references
are not possible arethrough
not available, the
the affected
available) BTS master clock (OCXO)
cells (BASE STATION SERVICE tuning is halted,
and the BTS synchronization drops to
PROBLEM).
Working (other clock is available) holdover
There might mode.be problems in the calls through
the affected cells (BASE STATION
SERVICE PROBLEM).
There is no impact on the system (BASE
STATION NOTIFICATION).
Calls are not possible through the affected

cells.
The RF Module is configured using defaults,

and the performance is not as expected.

cells. There might be problems in the calls
through the affected cells.
Calls are notBASE
cells (7116 possible through
STATION the affected
SERVICE
cells. There
PROBLEM). might be problems in the calls
through the affected cells.
There can be problems in calls through the
There is cells
affected no impact
(7116on the system.
BASE STATION
SERVICE PROBLEM).
AirScale BTS TDD, AirScale There is no impact on the system (7115
SBTS, Flexi BTS FDD, Flexi BTS BASE STATION NOTIFICATION).
TDD, Flexi SBTS:
Working - when fault does not
affect basic services of the base There might be problems in the phone calls
station through
5G BTS,the affected
AirScale cells,
BTS FDD, or calls might
AirScale BTSnot
Degraded - when fault be possible.
5G BTS, AirScale BTS affects
FDD, TDD, AirScale SBTS, Flexi BTS FDD, Flexi
basic services of the base station
AirScale BTS TDD, AirScale BTS TDD, Flexi SBTS:
and
SBTS,cellFlexi
is working
BTS FDD,in degraded
Flexi BTS Calls are not possible through the affected
mode
TDD, Flexi SBTS: cell(s) or calls are possible but the cell
Out of order
Degraded - otherwise
(TX path is still capacity and performance might decrease.
operational
Working but with degraded The TX and/or RX performance of the cell
5G BTS, -AirScale
performance)
when fault
BTSdoes
FDD,not
might be degraded or calls are not possible
affect basic
AirScale services
BTS(TX TDD, of the
AirScale base
Out of order
station path is out of through the affected cells because of the
SBTS,
service)Flexi BTS FDD, Flexi BTS failure.
Degraded
TDD, Flexi-SBTS:
when fault affects
basic
Working - whenoffault
services the base
does station
not
and cell is working in
affect basic services of degraded
the base
mode
station Calls are not possible through the affected
Out of order
Degraded - otherwise
- when fault affects cells.
basic services of the base station TDD, AirScale SBTS, Flexi BTS FDD, Flexi
and cell is working in degraded BTS TDD, Flexi SBTS:
5G
modeBTS, Flexi BTS FDD, Flexi Calls are not possible, or problems might
BTS
Out ofTDD,
orderAirScale BTS TDD,
- otherwise occur during calls through the affected cells.
AirScale BTS FDD, Flexi SBTS,
AirScale SBTS:
RRU connected over CPRI Ir The TX/RX paths of the module are out of
interface: order, and phone calls through the affected
- Degraded cells are not
5G BTS, possible.
Flexi BTS FDD, Flexi BTS TDD,
Other radio modules - e.g. RFM AirScale BTS TDD, AirScale BTS FDD, Flexi
connected over OBSAI RP1 SBTS, AirScale SBTS:
interface: The TX part is out of power, and calls are
- Out of Order not possible through the affected cells.
There can be problems in the calls through

the affected cells.
There might be problems with calls made

Out of order (The radio unit is too through the affected cells.
cold to properly generate RF) This fault should cancel itself. Heating of the
module is ongoing. During RF startup, the
Working (The radio unit is able to affected cell resources are not reported to
generate RF)
5G BTS, AirScale BTS FDD, RROM.
AirScale BTS TDD, AirScale The RF Module or FHS unit configuration
SBTS, Flexi BTS FDD, Flexi BTS might fail and cause another fault, and there
TDD, Flexi SBTS: can be problems in the calls through the
Degraded affected cells on the alarming device.
TDD, Flexi SBTS:
Out of order - the radio's power-on
self test detected a critical failure The default configuration is used, and the
that prevents the radio from TX and/or RX performance of the cell is
operating. degraded. There might be problems in the
calls through the affected cells on the
Degraded - at least one failure was alarming device.
detected during the radio's power- The TX and/or RX performance of the cell
on self-test, but the unit may still might
5G BTS,be degraded because
AirScale BTS FDD, of the failure,
AirScale BTSor
be functional, though in a calls are not possible through the affected
degraded state cells on theFlexi
BTS TDD, alarming
SBTS:device.
The communication between the System
Module and RF/FHS module might be
corrupted. Calls are not possible through the
affected cells.
The TX power level is decreased, and there

might be problems with phone calls through
It
theis affected
not possible
cells.to establish phone calls
through the locked FR.
The BTS does not send faults that are

There
related might
thebe
tomight problems inRadio
locked calls module
through the
The fault
affected cells. meanFlexi
that fans are not
(FR) to the and/or
connected Network Management
working. System
This might cause
(NMS).
the Faultmodule
RF/FHS sendingtotooverheat.
BTS Element
One fan failed: Module = Working, Manager is always enabled. Fault
Fan group = Degraded cancellations
The fault can are
onlyalways sent to the NMS
be automatically
and BTS Element Manager.
Two or three fans failed: Module = cancelled for RF modules where fans are
Degraded, Fan group = Out Of detected based on speed response
Order (FRM3.x, FRGT from version 102, and
FRGS from version X21). All other RF
Netconf-radios: modules require a reset.
if cooling is severely degraded =
Out of order If the fans do not rotate as required, the
temperature of the module might rise too
otherwise = Degraded high.
Module = Working, Fan group =
Degraded
Calls
If the are
fansnot
do possible
not rotatethrough the affected
as required, the
[AAS]: Working cells.
module temperature might rise too high.
5G BTS, AirScale BTS FDD, AirScale BTS FDD, AirScale BTS TDD,
The RF/FHS
AirScale SBTS, module
Flexi might overheat,
BTS FDD, Flexi but
BTS
AirScale BTS TDD, AirScale there is no immediate effect on the operation
SBTS, Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS:
of
Thethe module.
Fujitsu radio/FHS will reset itself when a
TDD, Flexi SBTS:
Working - when fault does not critical fault is detected. However, the
affect basic services of the base radio/FHS is not enabled upon start-up if the
station condition persists. Once the condition is
Degraded - when fault affects cleared, the radio/FHS is enabled again.
and cell is working in degraded
mode There might be problems with calls made
Out of order - otherwise through the affected cells.
RF module temperature alarms might occur.

A cell that uses the resources of the FR
None
module that has raised the fault is disabled
or degraded (depending on the amount and
type of Tx/Rx resources lost - see also
Calls are not
Reported possible
Alarms through the affected
Description).
cells, or the cell performance is degraded.
Downlink
Calls and signal transmission are
data transmissions on the given
possible
antenna line is quality
with degraded disabledandand the bandwidth
lower
corresponding FR transmitter
because of increased bit errorisrate
unusable.
on the
optical connection.
The overall FR module state is not affected
since the fault is caused by an external
phenomena on the antenna line (that is, an
Calls and data
extremely high transmissions
VSWR level). RF are HW
not and its
possible through the affected cells.
subsystems are not affected by the fault, but
some functions of FR module (for example,
transmitter on the alarming antenna line)
cannot be used as long as the fault remains
active.
The Flexi BTS unit in question is transmitting
5G BTS:
Netconf-radios: or
Input power data
receiving with degraded
to module has a fault, is
Out of order (O-RU report this fault unstable or broken.fault does not trigger
performance. The
with severity, CRITICAL) special actions in the BTS.
Degraded (O-RU report this fault AirScale BTS FDD, AirScale BTS TDD,
with severity, MAJOR) AirScale SBTS, Flexi BTS FDD, Flexi BTS
Working (O-RU report this fault TDD, Flexi SBTS:
with severity, MINOR) Cell performance might be degraded.

cells, or cell performance is degraded.




Cell performance is degraded.



cells.

The RRU or ASiR-sHUB will be disabled

because of power loss.


The TX output power can be too high and

the unit is being shut down to prevent
damage to the rest of the transmitter.
There is no data on the downlink. All calls
within the BTS (for FZM) or within the
related cells (for Zone or Flexi Zone SFN
Antenna) are impacted.
The PA has been shut off and cell is out of

service.

cells.
The
CallsExternal Alarm and
are not possible Controlthe
through lines of the
affected
Radio
cells. Module might not be working
correctly.
Downlink signal transmission on the given
antenna line is disabled, and the
corresponding FR transmitter is unusable.
Hence, the overall FR state is affected.
The TX or RX paths of the RF module are
out of order, and calls through the affected
cells are not possible.
There can be problems with calls through

the affected
Calls are notcells.
possible through the affected
cells (7653 CELL FAULTY).
Problems might occur in calls through the
affected cells (7654 CELL OPERATION
DEGRADED).
Radio module operation is aborted, all Txs

are blocked, and cells on this radio are
disabled.
RRU operation continues in a degraded

state. Beam-forming performance and
calibration
If functionalityalarm
is degraded.
If no
no other
other RX-related
TX or RX related is reported,
alarms on theRX
resources of Receive Diversity
same radio module are reported, cells Expansion
Module
supported(RDEM)
on thisdo not module
radio work optimally.
are still
If other RX-related
operational. alarm is reported, RX
resources
If other TXof orRDEM do not
RX related work.on the
alarms
same radio module are reported, cells
supported on this radio module are
degraded or faulty. Check the other alarms
If
to no other
know theTX or RX
cells related alarms on the
state.
This
samealarm
radioindicates
module are thatreported,
techniciansthe are
cells
accessing
supported connectors
on this radiofor debugging
module or
are still
monitoring
operational.purpose. Alternatively, this would
be a warning that there is an unauthorized
intrusion
If other TXto or
theRXRadio Module.
related alarms on the
same radio module are reported, the cells
supported on this radio module are
degraded or faulty. Check the other alarms
to know the cell's state.
Cells assigned to this RFM remain disabled

or degraded
There until the
is no impact of fault is corrected.
the fault on services
provided by the BTS if the fault is reported
alone. If other faults are reported at the
same time, this fault might be their root
cause.
There is no impact of the fault on services
provided by the BTS if the fault is reported
alone. If other faults are reported at the
same time, the fault might be their root
cause.
There may be interruptions to the

transmission of the non-LTE carriers on the
radio when this alarm is present.
For the primary optical link to the Radio
Module, the cell(s) of the Radio Module
behind the broken connection is/are out of
order
5G BTS: and the Radio Module cannot be used.
For
For the secondary
the primary optical optical
linklink
to theto the Radio
Radio
Module, the cells that are
Module, the cell(s) of the Radio Moduletransmitted
through
behind the thebroken
antenna carrier or is/are
connection have out of
resources
order and the Radio Module cannotlink
allocated via secondary be are
used.
affected.
For the secondary optical link to the Radio
Cells
Module, notthe affected
cells by the
that arefault might still be
transmitted
AirScale
operational.
Calls are BTS
not FDD,
possible AirScale
on the BTS TDD,
affected cell.
through
AirScalethe SBTS,antenna
Flexicarrier
BTS FDD, or haveFlexi BTS
resources
There allocated
is aSBTS,
potential viadegradation
secondary link areRx
TDD, Flexi
AirScale
affected.
SBTS: FlexiforSBTS: in the
path. If
The cells the
traffic PIM
ofbetweencancellation
the RF Module
the system algorithm
behind is
the and
module
Cells
running,
broken not itaffected by
will attempt
connection arethe
to
notfault
remove mightthestillthe
operational; be
the connected
operational. radio module is interrupted.
detected
RF
TheModule PIM.cannot isbefaulty.
cell operation used.
The traffic
AirScale between the
SBTS, Flexi SBTS: baseband module
5G
(for BTS:
example, FBBC) and the connected
The
For traffic
the between
primary the link
optical systemtoThethemodule
Radio and
radio
the module
connected is interrupted.
radio module is cell
interrupted.
Module,
operation the cell(s) of the Radio Module
is faulty.
The
behindcellthe
operation
broken is faulty.
connection is/are out of
The traffic between
order and the Radio Module the baseband cannot module
be used.
(for example, FBBC) and the
For the secondary optical link to the Radio connected
radio
Module, module is interrupted.
the cells The cell
that are transmitted
operation is faulty.
through the antenna carrier or have
resources allocated via secondary link are
affected.
Cells not affected by the fault might still be
operational.
The cell operation is degraded. The optical

interface loses its synchronization if the
amount of errors exceeds the defined limit.
The baseband bus RP3 traffic to the RF

Module is not working; cell operation is
degraded.
The connection to the associated link is lost.
The data is partially
baseband or completely
bus RP3 lost.
traffic to the RFThe
worst-case
Module is notfault effect can
working; cell expand
operation further
is
from the cell level.
degraded.
This fault can prevent BTS operation when

There
the RFismodule
possibly
is no immediate
needed for theeffect on the
required
BTS operation, but
cell configuration. it might cause an optical
interface alarm.
The fault is visible only for the first radio in
the chain. Fault 10 sends for the other FRs
when pooling breaks because of the lost
sync.
Data traffic to the connected RF module is

malfunctioning. The BTS operation is faulty.
The RP3 traffic from the baseband is

malfunctioning. The system module or
FBBx/ABIx module operation is degraded.
Baseband bus RP3/RP3-01 traffic might

work incorrectly. The cell operation is
degraded.
Working - if raised for SSD
firmware update.
Degraded - if raised for Atmel

uController FW update.
Out of order - in any other case. A software update is needed.
The BTS operation is degraded because

some of the BTS resources are not
available.

available.

available.

some of the resources of the BTS are
unavailable.
Either the I2C connections are disturbed or

the
Thissource
BTS isisOut
defective.
of Order since reliable
In case ofcommunication
message an extension board, this
cannot beprevents
granted.
the sRIO system from configuring the new
Out of order(FSP/FBB/ABIx when connected board.
shutdown or critical core is faulty) Some
In casebaseband processing
of a subrack resources
control board, this are
Degraded(FSP/FBB/ABIx not working. A cell (or cells) are not
prevents the system from controlling or
otherwise) operational, or the BTS
monitoring functions thatisthe
notcontrol
operational.
board
provides.
In case of subrack extension board data
reading failure (alarm is reported on SMOD),
the affected cell(s) is out of service.
The BTS is out of order because of

malfunctioning sRIO communication.
The unit is not operational. Basic services

may be affected.
- Out of order (GNCEL state -

when all the channel groups of the The
When cell
allmight enter "sleeping"
the TRXes mode.
of the sector are faulty,
cell are faulty) the sector reported as alarm source is
- Degraded (GNCEL state - when disabled. When a few of the TRXes of the
only few of the channel groups of sector are faulty, the sector capacity is
the cell are faulty) degraded.
Degraded (GNCEL state - when When few or all of the TRXes of the sector
few or all of the channel groups of are degraded, the sector capacity is
the cell are degraded) degraded.
configured
with no TRX and there is
corresponding local cell
commissioned with channel
groups)
- Degraded (BCF state - fault is When all the channel groups of the cell are
reported when local cell is not able faulty, the cell is disabled. When this fault is
to be reported on all the channel groups of the cell
mapped to BTS (sector)) due to mismatch on channel and path, but
- Degraded (BTS (sector) state - not all the channel groups are faulty, then
other cases) the cell capacity is degraded.
- Degraded (Antenna line state -

fault is reported on any of the Capacity of sector supported by antenna line
TRXes of the sector) instance
If the TX reported in alarm
power pooling is degraded.
feature license is not
- This fault is a notification to theenabled from BSC,
If OMU signaling linkthe feature
could will not work.
not be
operator to inform that license for Few TRXs will not be on-air
established during the startup, then as enoughno RF
the TX power pooling feature is resources will not be available,
configuration data would be received by thus
missing.
- Out of order(BCF state - OMU reducing
BTS, andthe capacity.
hence, the alarm source is
Start-up:
signalling could not be established disabled. If OMU signaling link is broken
during the startup) -during
Looseruntime,
Phase syncthen mode:
management interface
The System
- Working(BCF state - OMU towards BSC isbe
Module cannot notinitialized
available,inand hence,
Loose no
Phase
signalling broken during runtime)
- Out of order (BCF state - when OAM operation can be triggered
sync mode. Startup will be continued in from BSC.
the fault is reported during base Frequency mode. The System Module
station startup) cannot
BCF state guarantee
is set asLoose
Out ofHyper-SFN
order whensync
requirements.
- Working (BCF state - when the configuration is rejected, or timeout is seen
fault is reported during runtime) -inPhase sync mode:during
the configuration The System
startup.Module
cannot be initialized in Phase sync mode.
Startup will be continued in Frequency
BCF state is set as Out of order mode. The System Module cannot
when BSC does not respond to Base stationLoose
guarantee is outHyper-SFN
of order and cannot
sync
BTS initialization proecdure provide
GNCEL state is set as degraded requirements. any service.
when a TRX is added to an
antenna hopping sector and newly
added TRX can not be part of any The newly added TRX will remain out of
hopping group Runtime:
service.
- Loose Phase sync mode: The System

No impact
Module on the
cannot working of
guarantee the SBTS,
Loose and
Hyper-SFN
the operator shall refer to the BCF
sync requirements, and eDRX feature isID
- Working (fault is reported at BCF) configured at BSC.
turned off autonomously.
- Phase Sync mode: The System Module

cannot guarantee Loose Hyper-SFN sync
requirements.
Alarm indication means that the GSM

service may be degraded.
All TRXes of fault source sector that is
configured to share spectrum with another
RAT (WCDMA or LTE) and the mapped
peer RAT cells become faulty.
Peer RAT (WCDMA or LTE) starts using

dedicated spectrum for cell impacted by the
fault.
This fault is a notification to the If Lean GSM or CMST feature license is not
operator to inform that license for enabled, the feature will not work. BTS will
TX power pooling or Lean GSM or come up with normal carriers only, thus
CMST feature is missing. reducing the capacity.
Dynamic Power Pooling feature is not in
Working use.
Loss of receiver sensitivity, which results in

reduced range, increases dropped calls,
and/or reduces uplink RF performance.
The PIM Cancellation feature is not

activated at the RMOD.
For BTS:
PIM Cancellation
The PIM is notfeature
Cancellation enabled on the
is not
radio. There is a potential
activated at the FHS. for degradation in
the Rx path as the passive inter-modulations
will
For not be removed.
EPIMC:
The External PIM Cancellation feature
activation flag is set to true, and the reported
Degraded (O-RU report this fault fault prevents the EPIMC feature from
with severity, MAJOR) functioning on the HW unit.
Working (O-RU report this fault
with severity, MINOR)
Warning (O-RU report this fault One of logical C/U-plane connections has a
with severity, WARNING) fault, is unstable or broken.
Out of order (O-RU report this fault
with severity, CRITICAL)
Degraded
Degraded (O-RU
(O-RU report
report this
this fault
fault Unit has detected a fault of one of its
with severity, MAJOR)
with severity, MAJOR) interfaces
Working (O-RU report this fault
with severity, MINOR)
Warning (O-RU report this fault C/U-plane message content was faulty for
with severity, WARNING) undetermined reason.
Degraded when one antenna One of the power amplifiers in a module is

module is out of order. faulty, unstable or broken.
Out of order when all antenna
submodules are out of order or
when reported for Gluon radio
modules.
Degraded - when one (not all) The module in question is out of use.
Antenna module is out of order.
Out of order - when all Antenna
modules are lost or when reported
for Gluon radio modules. The moduleon
Depending in the
question is out
reported of use.
alarms, the BTS
capacity might have decreased (BASE
STATION OPERATION DEGRADED) or the
BTS might be not operational at all (BASE
STATION
DependingFAULTY).
on the reported severity, the BTS
capacity might have decreased (BASE
STATION OPERATION DEGRADED), or the
BTS might not be operational at all (BASE
STATION FAULTY).
Depending on the reported alarms, the BTS
capacity
Depending might
on thehave decreased
reported (CELL
severity, the fault
OPERATION
situation may DEGRADEDcause: or CELL
FAULTY).
a. performance degradation of cells the
(7654
Depending on the reported alarms, fault
CELL OPERATION DEGRADED).
situation might have no impact on the
b. defective
operation cells (7653
(BASE STATION CELL or FAULTY).
CELL
c. no impact
NOTIFICATION), on cells
the (7652
BTS BASE
capacity STATION
might
Depending
Flexi BTS FDD,
NOTIFICATION). on the reported
Flexi BTS TDD, alarms, the
Flexi fault
SBTS,
have decreased
might have no impact on theCELL
situation SBTS: (BASE STATION or
AirScale
OPERATION
operation (BASE DEGRADED,
STATION or CELL
1. If the reported alarm is 7651 BASE
FAULTY),
NOTIFICATION), or the BTS might
the BTS not be might
capacity
STATION OPERATION DEGRADED, the
operational
have decreasedat all (BASE STATION
BTS has no valid(BASE STATION sources
synchronization
FAULTY).
OPERATION
as a referenceDEGRADEDfor tuning theorOCXO, CELL and the
OPERATION
OCXO is: DEGRADED,
Depending on the reported alarms, or CELLthe fault
FAULTY),
a. for phase or the BTS
synchronization
situation might have no impact on might not
modebethe
- in
operational
holdover at
mode, all
operation (BASE STATION a (BASE
special STATION
algorithm is used
FAULTY).
to predict tuning control
NOTIFICATION), the BTS value and minimize
capacity might
phase error.
have decreased (CELL OPERATION
The fault
DEGRADED, situation
or CELLdoesFAULTY),
not affect or thetheBTS BTS
air interface stability, but
might not be operational at all (BASE if the fault situation
lasts
STATION for a FAULTY).
long time, the accuracy starts to
If theslowly.
drift fans are not rotating as expected, the
module
Also,
Depending temperature
features on that or acoustic
require
the reported phase
alarms,noise
thelevels
fault
might rise
synchronization too high.
are For example,
disabled.
situation might have no impact on the a
temperature
b. for frequency
operation faultsynchronization
(BASE might be generated
STATION or CELLmodefrom - in
Depending
the alarming
free-running on the
module.
mode, reported
using thealarms, the fault
last calculated
NOTIFICATION),
situation mightvalue. the BTS capacity
have no impact on the might
tuning
have control
decreased (BASE STATION
operation
The (BASE
fault situation STATION
does not affect
OPERATION
NOTIFICATION), DEGRADED),
the but or thethe
BTSif capacity BTS BTS
might
air
mightinterface stability,
not be operational the fault
at all (BASE situation
have
lasts decreased
for a FAULTY).
long time,(BASE the STATION
accuracy starts to
STATION
OPERATION
drift slowly. DEGRADED or CELL
OPERATION
2. If the reported DEGRADED,
alarm is 7652 or CELL
BASE
FAULTY), or the
STATION NOTIFICATION, the BTS might be BTS
not is using
operational
other available at all (BASE STATION
synchronization source as a
FAULTY).
reference for tuning the BTS master clock
(OCXO).
Depending on the reported alarms, the fault
This doesmight
situation not necessarily
have no impact have on
anythe effect on
the
operation (BASE STATION or CELL the
BTS operations as it depends on
quality of the usedthe
NOTIFICATION), source.
BTS capacity might
have decreased (BASE STATION or CELL
OPERATION
Depending onDEGRADED), or the BTS
the reported alarms, the fault
might
situation might have no impact(BASE
be not operational at all on the
STATION FAULTY).
operation (BASE STATION or CELL
NOTIFICATION), the cell capacity might
have decreased (CELL OPERATION
DEGRADED), or the
Depending on the cell might
reported not be
alarms, the fault
operational at all (CELL FAULTY).
situation might have no impact on the
AirScale BTS TDD, AirScale operation (BASE STATION
SBTS, Flexi BTS FDD, Flexi BTS NOTIFICATION), or the BTS capacity may
TDD, Flexi SBTS: have decreased (BASE STATION or CELL
Working (case 27) OPERATION DEGRADED).
Degraded (case 11, 24, 26)
Degraded / Out of order (case 12,
15, 21) The effect depends on the case when the
Out of order (otherwise) fault is detected. See the "Meaning" field.
5G BTS, AirScale BTS FDD, Any attempt by the operator to configure
AirScale BTS TDD, AirScale modes other than the single TX mode for the
SBTS, Flexi BTS FDD, Flexi BTS cell is unsuccessful.
TDD, Flexi SBTS: 5G
5G BTS,
BTS: AirScale BTS FDD, AirScale BTS
- Out of order : otherwise TDD,
GNSSAirScale
becomes SBTS, Flexi BTS FDD, Flexi
unusable.
- Working : unit services not BTS TDD, Flexi SBTS:
affected
5G BTS, AirScale BTS FDD, The cellsBTS
AirScale remain down.
FDD, AirScale BTS TDD,
AirScale BTS TDD, AirScale AirScale SBTS, Flexi BTS FDD, Flexi BTS
SBTS, Flexi BTS
Out of order FDD, Flexi BTS
(1. FCT, TDD, Flexi SBTS:
TDD, Flexi SBTS:
2.FSP/FBB/ABIx when shutdown The fault has no direct impact on the
Out of order
or when FSP/FBB/ABIx critical operation.
core is faulty)
Degraded (FSP/FBB/ABIx The

FlexiBTS
SBTS,
AirScale resources
SBTS, Flexihave
AirScale SBTS, decreased,
Flexi BTSorFDD,
the
otherwise) BTS is faulty.
Flexi BTS TDD: TDD, AirScale BTS TDD, AirScale
BTS
The FDD:operation is degraded, the cell
BTS
5G BTS,
BTS AirScale BTS FDD, AirScale BTS
AirScale SBTS, Flexi SBTS, Flexi The
operation isis not
TDD, AirScale
commissioned.
degraded or outBTS
SBTS, Flexi of order,
FDD, or the
Flexi
BTS FDD, Flexi BTS TDD: BTS is
5G BTS,
BTS not
TDD, operational
AirScale
Flexi SBTS: (FCT/all FSPs
BTS FDD, AirScale BTS and
Out of order Small
FBB
TDD, Cell:
are faulty).
Depending
The BTS on
isFlexi the reported
not commissioned. alarm, the fault
BTS TDD, SBTS:
situation might not have an impact on the
BTS startup
operation, theis BTS
interrupted,
capacityand the have
might BTS is
Flexi
out ofZone
order.Access Point:
decreased, or the BTS might not be
Out of order: when the problems Flexi Zone Access point is not
operational at all.
commissioned.
prevents BTS to reach operational 5G BTS:
state (wrong or missing RNW Carrier Aggregation problem detected during
data/active commissioning data Flexi Zone SFN
PCell/SCell Antenna: BTS is working,
configuration.
not readable). Flexi Zone SFN
but the affected carrierAntenna is not
aggregation cells
commissioned.
combinations reported in additional alarm
Working: if there have been information work in non-CA mode (failed
problems with commissioning data carrier aggregation cells combinations) or
in SW package but still BTS is work in degraded CA mode (degraded
operational. carrier aggregation cells combinations).
This fault can prevent the BTS from

functioning when the radio unit is needed for
the required cell configuration.
5G BTS, AirScale BTS FDD, The BTS is not operational or is degraded.

AirScale BTS TDD, AirScale 5G BTS, AirScale BTS FDD, AirScale BTS
SBTS, Flexi BTS FDD, Flexi BTS TDD, AirScale SBTS, Flexi BTS FDD, Flexi
TDD, Flexi SBTS: BTS TDD, Flexi SBTS:
'Out of order' if radio module The signal
If minor path is
severity not usable.
alarm The then
is reported cells cell is
reports that the configuration has using the faulty unit might not work.
operational. The cell configuration is
failed. inconsistent with radio module capabilities,
'Working' if radio module does but fault does not prevent cell configuration.
NOT report that the configuration If critical severity alarm is reported then cell
has failed. is disabled and cannot provide any service.
The antenna line is not operating correctly.

The cell is disabled.
The antenna line is not operating correctly.
The cell capacity decreases.
If another
There is noreference
immediateclock is available,
effect on the cellthe
Out of Order: When ALD synchronization reference source
operation. The device continues the changes
commissioned is only powered to the newwith
operation reference clock. Tuning
the previously then
used data.
from the RS485 port. follows this new reference.
- If a DC LOGLINK between port
and ALD unit (LNA, RETU, RAEU) There is noreference
If another immediate effect
clock on the
source cell
is not
exists and this is the only DC operation. The device continues the
available, tuning does not follow the external
LOGLINK connected to that ALD operation
reference with the previously
anymore used
but the clock data.is
tuning
unit (ALD unit is powered from halted and the Flexi Zone Micro BTS, Flexi
single
Working source)
(7652,7115), Zone Access Point, or Flexi Zone SFN
Degraded (7651,7115), Antenna continues its operation based on
Degraded:
Out of OrderOtherwise.
(7650,7108) the
- If DC LOGLINK between port and Theinternal
affectedoven
unit oscillator.
is not operational. In case
ALD unit (LNA, RETU, RAEU) of an FSP fault, the channel capacity is lost
doesn't exist or there is no ALD and cell(s) become unavailable. The
connected to that port, associated cells in the Radio Module
- If a DC LOGLINK between port become faulty.
and ALD unit (LNA, RETU, RAEU)
exists but this ALD unit has also The ALD interface is not operating correctly.
another DC LOGLINK (ALD unit is Communication with TILT devices is not
powered from multiple sources), possible.
Cells are not activated. It relates to cells that
were going to use the radio unit connected
to the system module through the faulty fiber
optic cable.
Fan control is not optimized. The effect to

noise or temperature level is marginal.
The Radio Module connected to this OptIF is

not
Thestarted.
FSP/ABIx resource is shut down, and
the BTS operation is degraded or faulty.
The FCT and possibly other FSPs/ABIx's

Not all fans failed: alarming fan = that are not alarming are kept powered.
out of order, fan group = degraded
All
5G fans
BTS,failed: all fans
AirScale andFlexi
SBTS, fan If the fans do not rotate as requested, the
group
SBTS: = out of order module temperature might rise too high.
- Out-of-order - in case of
inconsistent SW after SW fallback
-5G
Degraded in - case
BTS, AirScale of consistent
SBTS, Flexi
SW after
SBTS: SW fallback Source unit has an inconsistent SW version.
- Degraded in - case of consistent
SW after SW fallback Source unit has an inconsistent SW version.
5G BTS, AirScale SBTS, Flexi TX and RX resources are unusable in the
SBTS: chained radios (position in the chain >=2).
- Out-of-order - in case of Flexi BTS TDD, AirScale BTS TDD, AirScale
inconsistent SW after SW fallback BTS FDD:
- Degraded in - case of consistent 1. Save to file the cause of the SW fallback
SW after SBTS,
AirScale SW fallback
Flexi SBTS, Flexi Source unit has an inconsistent SW version.
on request.
BTS
Out of FDD, Flexi
order - theBTS
cell TDD,
can not
operate because downlink BTS 2. Mount the passive file system, and thus,
carrier
FDD:
which transmits PSS/SSS signals read the cause of the SW fallback on
Out of order
is failed. request from the file.
Degraded - the cell can still The cell is disabled (the downlink carrier that
operate because downlink carrier transmits PSS/SSS signals has failed).
which transmists PSS/SSS signals The cell is degraded (the downlink carrier
is still working. that transmits PSS/SSS signals is working).
The ongoing BTS reset lasts longer.
Flexi Zone Micro, Flexi Zone

Controller: The cell or BTS is not operational or is
Out of order degraded.
The newly downloaded SW overwrites the
Flexi Zone Access Point, Flexi active SW. Thus, SW download and
Zone SFN Antenna: activation are not allowed. The currently-
Working active SW is still running.
1. Other than sync hub configuration, the

The radio
master module
system is powered
module works off. Therefore,
properly.
calls and data transfers cannot be served by
that
2. Inmodule.
sync hub configuration, detection of the
peer system module is still possible through
the shared radio, or the shared radio module
The master system module works might be lost and the cell that supports the
properly. radio module might be down.
The system module is out of order, and the

BTS is out of order.
GNSS becomes unusable.

If the system module affected by the fault is
the primary system module of the BTS, and
the system module has an active time
reference, which is valid for loose-phase
GNSS becomes (e.g.
synchronization unusable.
NTP with defined
UTC/GPS offset), at the startup time, then
the system module performs fallback to the
loose-phase synchronization mode.
Features requiring
GNSS becomes phase synchronization
unusable.
are deactivated.
If the system module affected by the fault is

The DC voltage
the primary is disabled
system module on the BTS,
of the reporting
and
antenna line.
the system module has no active time
reference, which is valid for loose-phase
synchronization (e.g. NTP with defined
If the problem
UTC/GPS has atbeen detected during SW
The HDLCoffset),
activation, linkSW
the bethe startupon
will activation
disabled
and
time,
thethen
the system
reporting moduleLine
Antenna performs fallback
or IUANT port.to the
consequent reset are aborted.
frequency synchronization mode. Features
If the problem
requiring phasehas been detectedorduring
synchronization loose-
Out of order - in BTS startup start-up,
phase synchronization areout
the BTS remains of order. The
deactivated.
customer should request both a rollback to
Working - in BTS runtime the previous
If the system SW and affected
module another SWby thedownload.
fault is
the secondary system module of the BTS,
then the system module expects for
recovery of a phase reference source to
continue the startup.
The start-up procedure stops, and no cells

are set up.
The log file from a particular unit is not

Degraded (configuration consisting included in the BTS snapshot.
of single and dual-mode RRUs)
Out of Order (configuration
consisting of only dual-mode Calls are not possible through the affected
RRUs) cells.
TD-SCDMA has encountered a problem that

might affect TD-LTE performance.
The card may be used (e.g. radio The radio unit connected to port 3 or 4 of the
may be connected to port 1 and FBBC card cannot provide services to the
provide services for some cells) cells, and the cells are degraded or not
and this is why it is "Degraded". If the BTS is in degraded state, cell TX
operational.
performance might be degraded. The calls'
throughput or handoffs from/to the affected
cell(s) on the alarming device might be
Degraded - if the temperature degraded.
exceeded the predefined warning Configuration reset has been invoked.
threshold. If the BTS is in out-of-service state, the Flexi
Out of order - if the temperature Zone Micro BTS, Flexi Zone Access Point,
exceeded the predefined critical or Flexi Zone SFN Antenna is not
threshold. operational.
The Flexi
Access ZoneorMicro
Point, Flexi BTS,
ZoneFlexiSFN Zone
Antenna
Access Point,tooroperate
can continue Flexi Zone SFN for
properly Antenna
an is
not operational.
extended period despite the ToP
synchronization loop requiring tuning within
5%
The of its tuning Micro
Flexi limit. Operation inZone
this area
If
is,the BTSZone
however, is an
in degraded
indication
BTS, Flexicell
state,
of excessive TX Flexi
Degraded - if BM reports Access Point,might
performance or Flexibe Zone SFN Antenna
degraded. The calls'is
Zone
not Micro BTS or Flexi Zone SFN Antenna
operational.
temperature rise above warning throughput
reference or handoffs
oscillator aging from or to the
level This faultcells
affected is the result
might be a or improper
ofdegraded.
prolonged
functioning
interruption of of the IEEE1588-2008
all configured master
synchronization
Out of Order - if BM reports clock (an alarm should be received
temperature rise above critical reference
If the BTS sources
is in out (multiple
servicefaults
of cases). state,infrom
cases
the
the
PA is
master
where clock
the in such
affected Flexi The 1818:
level turned off and
EFaultId_Ov_OscAl the cell is Zone
fault not
will
Micro BTS,
active.
also Zone
likely SFN
be
Flexi Zone Access Point, or Flexi
reported if there has been excessive
Antenna is configured to support more than Flexi
Zone Micro BTS, Flexi
one synchronization Zone Access
reference source).Point,
or Flexi Zone SFN Antenna
Because the RF carrier frequency accuracymaster clock
frequency aging. cannot be guaranteed,
or phase alignment
the Flexi Zone Micro BTS, Flexi Zone
must terminate RF transmissions upon the
reporting of this fault.

stops providing service.
5G BTS:
GNSS accuracy is not guaranteed.
The BTS BTS

AirScale is outFDD,of service
AirScale because
BTS TDD, the RP1
interface
AirScale SBTS,cannot Flexibe used.
BTS FDD, Flexi BTS
TDD, Flexi SBTS:
If another
This indicates synchronization
that the Flexisource is
Zone Micro BTS
available, the BTS starts to
or Flexi Zone Access Point has detected use that for thea
BTS reference,
power-down
5G BTS then there are no effects to
condition.
the
NR BTS
cells air interface
assigned accuracy.
to the shared radio
The
module are working. normal
BTS
system can continue
clock on the Slaveoperation.
FZM or
FZAP board
Alarm enters the
Base Station holdoverdue
Notification mode in
to fault
If there
which
4110 arelast
the
(Peer no othersystem
valid
System synchronization
module clock sources
frequency
connection lost)
The BTS
available, isthe
operational.
external GPS
offset is maintained.
is reported together thisorfault.
If MS_1PPS
with GNSSclock
receiver
signal is module
recovered continues
within the providing
holdover the
reference
period, the for the
fault BTS.
situation
AirScale BTS FDD, AirScale SBTS, Flexi does not affect
The
Flexireceiver
BTS Zone Flexi
FDD, hasSBTS:
Micro a high-performance
BTS or Flexi Zone Access
oscillator,
Point air and
interface
Cells assigned to the therefore,
operation.frequency
shared radio module
synchronization
are working, can
butistheir be maintained
capacity might within
be
Status "degraded" is used for When
the the
defined fault
limits detected
for up to during
several startup,
months,
failure during BTS runtime affected
the BTS because
is not the slave When
operational. systemthe module
fault
and phase
working as synchronization
temporary master �cannot
for up to 24 is
Status "out of order" is used for detected
hours. during runtime, the requested new
failure during BTS startup. configure
transport antenna line devices
configuration is not (for example,
applied.
When,
MHAs and becauseRETs). of the phase drifting, the
phase deviation eventually exceeds the
defined limits,antenna
Additionally, the features, requiring
line device alarms phaseare
synchronization, will become
not visible for the slave (for example, VSWR non-
operational.
alarms).
Alarm Base Station Notification due to fault

4110 (Peer System module connection lost)
is reported together with this fault.
The antenna line device is out of use.
The antenna line device is not operating

correctly.
The radio slave system module cannot use

the shared radio until the radio master
system module is available.
The cell cannot be set up and remains

faulty.
The requested ALD port is inoperable.

cells.
The Flexi Zone Access Point goes through a
reset, and hence, all the cells served by the
access point are disabled. The capacity of
the Flexi Zone Controller is reduced
because of the disabled cells.
The Flexi Zone Access Point does not send
any other faults other than transport faults to
the network management system (NMS)
The
whenFlexi Zone Zone
the Flexi Access Point Point
Access or Flexi
is Zone
SFN Antenna is out of service.
blocked. The fault cancellations are sent to
the NMS.
All the cells under the blocked Flexi Zone

Access Point are disabled.
The cell is out of order.
The NE is in service, but features that use

SRIO connection (for example, Inter-eNB
Carrier Aggregation) do not work.
The Flexi Zone Access Point is out of

service.
Software download has failed and must be

retried.
The unsigned release has been successfully
downloaded, but no signature verification is
possible for the release. If it is downloaded
Software downloadthe
without activation, has failed and
unsigned SWmust
buildbeis
retried.
only downloaded to a 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

retried.
The MHA does not provide gain in RX path.
The cell performance might be decreased.
Within the recovery action, missing gain is
compensated by additional gain delivered by
the LNA in the Radio Module.
The effect depends on the case when the
fault is detected:
This
-FR If thefault is the
diagnostic
functions that result of either
information
are not isa"IQ
critical prolonged
for cell
interruption
compression of
setup cannot be used.orall configured
forced link synchronization
speed incorrect in
reference
site sourcesfile",
configuration (multiple
the BTS faults in cases
startup
where the affected
procedure is terminatedFlexi andZonecells
Micro areBTSnot is
configured to support more than one
enabled.
The fault has no direct impact
synchronization on BTS
- If the diagnosticreferenceinformation source),
is "IQ or a
operation.
hardware problem that has resulted
compression not supported by RadioinHW" a
large
IQ or rapid shift
compression in the system
is enabled time clock
for a radio, or a
phaseinora frequency.
radio chain that does To prevent interference
not support IQ
to other BTSs and
compression, and impacted
minimize cell(s)
recovery aretime,
out- a
BTS reset is performed.
of-service.
- If the diagnostic information is "Down
sampling
The eNB does not supported
not use the by affected
Radio HW" the
radio
cells
module. Calls are not possible through theare
which are using down sampling and
assigned
affected cells.to the radio HW that does not
support it, are out-of-service.
- If the diagnostic information is "Number of
detected
The radioRET module unitsresources
in multiRET is not
cannot be used
consistent
by the BTSwith SWsite configuration
because of unknown file", or its
Cell
RF/FHS capacity
equivalent forisRAE,
hardware degraded.
the operator
capabilities is only
(missing
informed
hardwarethat not all commissioned
properties for the given RFM/FHS ALD
devices
product).are The detected.
radio module cannot be
-recognized
If the diagnostic information
and properly is
configured by the
"Commissioned
BTS software. antenna operating band is
Out of order - TDD - IQ not supported by the ALD.", the operator is
Compression issue only informed that the commissioned
Out of order - FDD - IQ antenna operating band is not supported.
compression (IQC) and/or down- - If the diagnostic information is "Radio’s
sampling (DS) are/is enabled for a FZAP
max numberis unable to be discovered.
of supported streams per
radio that does not support these carrier was exceeded.", the operator is
functions. informed that the cell is not operational due
Working - FDD/TDD - ALD to exceeding radio's capabilities.
commissioning issue There is no other effect.
None
Out Of Order - if Location Lock
violation has been detected and
locationLockConf.automaticDisabl
e configuration flag is set to true.
Out Of Order - if Location Lock If reported with an Out Of Order unit status,
evidence file is missing or failed it prevents the BTS from transmitting. Cells
validation after reboot. stay disabled and the BTS does not go to
Working - in any other case. OnAir state.
Cells and eNBs remain in service, but
features related to "inter-site or inter-eNB
Carrier Aggregation" are taken out of
service.

features related to "inter-site Carrier
Aggregation" are taken out of service.

features related to "inter-site Carrier
Aggregation" are out of service.

features
Customerrelated to "inter-site
IP traffic is limited. Carrier
Aggregation" are taken out of service.
The level of traffic decreases by 5%-6%
every seven days after the missing licenses
have been detected. A new alarm is raised
when the level changes.
No new calls can be set up. Existing calls
may be released.
Management of the BTS from NetAct is not
possible
The
If BTS fault has no direct impact on over
the current
If otherdoesn't
operation references
(BASE
succeed to switch
are available
STATION and to
another
configured, timethen
source
the alarms:
synchronization
NOTIFICATION).
-reference
if there was no time source
source changes to from
anotherthe
beginning
source. Tuning then follows this newan
logs and all reports have
incorrect
reference.time,
Degraded - when there is no other -If else
otherdifference
references of are
BTSnot time and logsthe
available, and
available and usable input all reports time increase.
BTS master clock (OCXO) tuning is halted
reference source to be selected and
If otherin phase mode,are
references theavailable
BTS and
Working - when BTS is synchronization drops to
configured, then the synchronization holdover mode.
synchronized with another input If the source
reference is RMOD
source changesthentocarrier
another
reference source
Degraded - when no other deactivation is triggered
source. Tuning then follows by RMOD.
this new
reference clock source is available reference.
If other references are available and
Working - when there is at least configured, then the synchronization
one more working reference clock If other references
reference source changesare not available,
to anotherthe
source available
Degraded - when no other BTS
source. Tuning then followstuning
master clock (OCXO) is halted.
this new
reference clock source is available reference.
Working - when there is at least
one more working reference clock If other references are not available, the
source available BTS master clock (OCXO) tuning is halted.
The micro DTX functionality (LTE1891) is

not activated on the antenna line.
Inter-eNB FDD-TDD carrier aggregation is
not working on the alarming unit.
The micro DTX functionality is not

successfully activated
The transmission to theorRF
deactivated
module atin6 a
Out of order - link is radio module.
Gbps is lost. Data is not transmitted from or
unsynchronized both at 3Gbps and to the RF module at all, or is transmitted at a
6Gbps lower speed (3 Gbps).
Degraded - link is synchronized at The cells supported by the faulty link are
3Gbps disabled, or the cell
The transmission to operability is degraded.
the RF module at 3
Gbps is lost. Data is not transmitted from or
to the RF module at all. The cells supported
by the faulty link are disabled, or the cell
operability is degraded.
The operator is informed about which of the

subtending
The BTS cannot FZAPs beorinitialized
SFN ANTs or, were
if
unsuccessful
initialized, is forced to operate in password.
in taking the latest
synchronization holdover mode. If RIBS
unavailability persists beyond the rated
holdover interval, LTE call processing is
halted.
LTE cells supported by radio modules
operating in dual mode, that is, connected
both to SCDMA and TD-LTE base stations,
are taken out of service.
The active base station configuration is not

the same as the one requested in the
configuration change.
If the target FZAP exists physically, the

capacity of the Flexi Zone is reduced.
The fault has no direct impact on the current

operation (BASE STATION
NOTIFICATION).
The fault situation has no immediate effect.
Operation of the cells supported by the radio
module might be impacted if memory
consumption continues
Correct operation of theto increase.
radio module is not
guaranteed. Operation of the
cells supported by the radio module are
impacted. The radio module can crash at
any moment.
The LTE time on Flexi Zone Controller is not

accurate and the MBMS service is disabled.
SMOD / BBMOD performance is degraded.
Collisions with synchronization/GPS signal

might happen.
Out of order (when SMOD or when
BBMOD shutdown)
Startup is terminated. The unit is not
Degraded (BBMOD otherwise) operational.
The BTS starts to reject incoming calls
except for a few exceptions including
Handovers, re-establishments, emergency
calls, high priority calls, etc.
The BTS/Flexi Zone Access Point is not

operational and is out of service.
The newly downloaded configuration plan

overwrites the previously downloaded
configuration
If a non-criticalplan.
sub-unit is unavailable (lost),
Out of order (FBB/FSP when cells supported by the faulty sub-unit are not
shutdown or when last FSP is operational.
faulty) If a critical sub-unit is unavailable (lost), cells
Degraded (FBB/FSP otherwise) supported by the FSP are not operational.
Because of the limited optical interface

capacity, not all cell configurations are
supported by the impacted radio.
All cells that are served by this SFN Antenna
are degraded (when there are other ants
serving these cells). Otherwise, all cells are
disabled.
The SFN Antenna cannot be discovered.

The Flexi Zone SFN Antenna does not send
any other faults, other than transport faults,
If
tothe
thetarget SFN
Network Antenna exists
Management physically,
System (NMS)
the
when the Flexi Zone SFN Antenna isor Flexi
capacity of the Flexi Zone Micro
Zone
blocked.Access Pointcancellations
The fault is reduced. are sent to
the NMS.
In a Dual Core configuration the status of
extension
All the cellsunit isn'tthe
under visible to theFlexi
blocked primary unit.
BTS
The staying
extensionin unit
license
maylimited
be mode Zone
offers
SFN
less Antenna
BB are degraded.
capacity/resources for any
- out of order or removed, or
processing purpose comparing
- Syscom connection to BTS
is out of order, or
staying in NOT limited
- commissioned as single eNB. mode.
Cell which occupied
- commissioned baseband
as primary capacity that
core.
is over the limit is disabled.
When the fault is raised while
commissioning, the primary core can still be
successfully commissioned and be in
(degraded) service.
The Flexi Zone SFN Antenna is not
operational.

operational.

operational.

operational.

operational.
The BTS or FZAP is not operational.
The Flexi Zone SFN Antenna is out of

service.
The cell is disabled and is unable to provide

service.
The BTS isn't operating in dual core mode.
The secondary unit cannot be used in dual
core configuration. Cells to be supported by
the secondary unit according to
configuration are not enabled.
The radio module is powered off. Therefore,

calls or data transfers cannot be served by
that module.
Setting up cells on the secondary core fails.
All cells supported by the secondary
baseband modules connected to the
secondary
Connectionunit are disabled.
to fault source peer system
module is disabled. Shared radio modules
connected to the peer system module will
not be used bytoLTE
1. Connection BTS.
peer Cellsmodule
system configured
where
on the radio modules are disabled.
the radio module is connected is disabled.
2. Radio modules connected to the peer
system module are disabled, and cells
configured on the radio modules are
disabled too.
Connection to fault source peer system
module is disabled. Shared radio modules
connected to the peer system module will
not be used by LTE BTS. Cells configured
on the radio modules are disabled.
The affected radio and cell (if

commissioned) is out of service.
The cell is out of order if the failed virtual
node is used by the cell.
The cell is disabled and cannot provide any
Cells in RAT are out of order if the failed
services.
virtual node is used by the RAT.
LNBTS, NRBTS: The BTS core (primary or secondary) is out

Degraded if some cells can The cell ifisthe
of order disabled
failed and cannot
virtual nodeprovide
is used any
by
continue to operate services.
all cells processed on impacted BTS core.
The AirScale is not synchronized (in BTS
runtime).
LNBTS, NRBTS, WNBTS, FCT: The
CellsBTSthat iswere
out supposed
of order if atovirtual node by
be supported
Out of order if all cells cannot failed
the unit according to configuration are is
to start, or the failed virtual node
operate
Working - when fault does not used by all cells.
degraded.
affect basic services of the base In case of dual core scenario with sync via
station, ie no cells are configured backplane, secondary core is not
on BTS secondary unit synchronized and cells configured on
Degraded - otherwise AirScale
secondary BTS TDD,
core are AirScale
degraded. BTS FDD, Flexi
SBTS, AirScale SBTS, Flexi BTS FDD, Flexi
BTS TDD:
The
PRSused additional
transmission is frequency
disabled on might be of
all cells
affected due to existing overlapping
the eNodeB, therefore OTDOA service is
frequency.
disabled. UE requests for inter-frequency
RSTD
Because (Reference Signal Time
BTS connection to BTSDifference)
Mediator
measurement for inter-frequency
and Network Management System OTDOA
(NMS) is
can
lost, still
the be supported.
following Telecom
are not traffic is still
possible:
supported.
1) BTS management operations like e.g.
configuration activation/upload, BTS SW
download/activation/upload
2) alarms and counters reporting from BTS
to NMS
Flexi SBTS:
- Degraded - in case of consistent The source unit has an inconsistent SW
SW after SW fallback version.
Cell is disabled because the "Reduced LTE
Guard Band" feature is enabled but the
related RF module does not have this
capability.
Degraded
- At least one cell is still Cells and eNBs remain in service, but other
operational features related to the Inter-Site Carrier
Also reported when the BTS power Aggregation feature are taken out of service
supply is available again but not all or are degraded.
cells are enabled yet.
Out of order Calls are not possible through the affected

- All cells are disabled cell(s).
AirScale BTS FDD:
Start-up:
-1.Loose Phase sync
Configuration mode: TheConnection
Management System to
Module cannot be initialized
the radio module cannot be established. in Loose Phase
sync
2. mode.
Thethrough Start-up
radio module will be
remains continued in
uninitialized
Calls
Frequency the blocked
mode. The TRX
System are
Module
and disabled.
transferred to another TRX. New callssync
cannot
3. Cellsbeguarantee
configured Loose
on the Hyper-SFN
radiothe
module are
cannot
requirements, established
and eDRX through
feature isblocked
turned
disabled.
TRXes. The BTS does not send any faults to
off autonomously.
BSC,
- Phase syncare
which related
mode: ThetoSystem
the blocked
Module TRX.
- Degraded (GNCEL state - Only Fault 4399 always makes sector
cannot be initialized in Phase sync mode. as
few of the channel groups of a cell Start-up
degraded. willIf be
all continued
TRXes of sector are blocked,
in Frequency
are blocked) alarm
mode. with
The fault
System49 isModule
reported.cannot
guarantee
TDD, AirScale LooseSBTS,Hyper-SFN
Flexi BTS sync
FDD, Flexi
requirements,
BTS TDD, Flexi SBTS: and eDRX feature is turned
off
High autonomously.
accuracy
Start-up: related GSM features, such
as DFCA, will be disabled.
The System module has no accurate time
Runtime:
reference. Real time is not available. Alarms,
-logs,
LooseandPhase sync will
all reports mode: have TheanSystem
incorrect
Module
time. cannot guarantee Loose Hyper-SFN
Cells
sync requirements, and eDRX featureare
supported by the faulty sub-unit is not
operational.
turned off autonomously.
Runtime:
-- Phase
FrequencySyncsyncmode: TheThere
mode: System Module
is reduced
cannot guarantee
accuracy in time stamping.Loose Hyper-SFN sync
requirements, and eDRX feature
- Loose Phase and Time Sync mode: The is turned
off autonomously.
System Module cannot monitor the accuracy
of Loose Hyper-SFN sync.
- Phase Sync mode: The System Module
cannot measure
This is only the phase/time
a notification to showerrorwhy a TRX
against the reference.
or TRXes of the sector are not on-air at
BSC.
This alarm is just notification since it will
allow BSC to send System Information to
TRX and this alarm gets cancelled.
The operating performance of the RX path

supported by the Antenna Line reported as
fault source is decreased.
Roundtrip antenna delay measurements are

not provided to the operator. There is no
impact to service.
LeapSeconds value reporting from
FlexiZone Access Points are not correctly
synchronized. LeapSeconds value is
broadcasted in SIB16 when
actUTCBroadcast flag is set to true.
eNB will be unable to setup cells and any

calls
The BTS cannot perform power group

shutdown for energy savings. The power
group is still
The 1pps consuming
signal power.
might not be available for
synchronization (alarm with fault 4153
[Reference clock missing in startup] or 1898
[PPS reference missing] might be raised in
parallel).
This fault can prevent the BTS from
functioning when the FHS unit is needed for
the required cell configuration.
The unlicensed cell setup failed. The cell is

not able to provide service.
The System Module ignores the signal from

FZAP
the GNSSis unable to be
receiver discovered.
and does not use it as a
- Working (BTS uses another synchronization reference. The System
available reference source) Module switches to another valid reference,
- Degraded (There is no other if any is present. Otherwise, BTS switches to
usable reference source) holdover mode.
Out of order – the radio is

commissioned but cannot support The BTS is not operational.
cells. If the radio is commissioned, the TX or RX
Working – the radio is paths of the CPRI-A radio cannot be used,
uncommisioned so no cells are and calls through the associated cells are
using the radio. not
Thepossible
operatoron those
may not paths.
be able to log into the
BTS as 'serviceuser' or 'toor4nsn' using the
configured SSH Public Keys. In case the
SSH Port number change failed, the user
configured value is not taken into use.
Unwanted users can take advantage of the

situation,
The cell isconnect to BTS
considered and perform
as sleeping based on
undesirable actions.
RRC-related counters and thresholds
defined by the customer. Even if an alarm
due to the fault is reported, the cell may still
All products:
provide
This faultservices buta the
indicates services
potential are
degradation in
degraded.
the antenna line of RX path due to lose
antenna connection, water intrusion,
damaged cables, lightning damage, external
structures, or physical damage to the
antenna assembly.
All products:
There is a potential for degradation in the
antenna line of RX path. If the External PIM
Cancellation algorithm is up and running, it
cannot effectively remove the detected PIM.
All products:
The EPIMC will not perform PIM analysis or
cancellation.
RX data fromThis may
helper degrade
cells site on other
allocated
performance.
problematic BTS (or hotel members) in the
same BTS hotel cannot be used in the
processing of the IQ data streams resulting
in non-maximal RX gain achieved in the BTS
hotel.
Depending on the 10GE connection type
(primary/secondary 10GE link), exchange of
RX data between BTS in a BTS hotel may
be partially or fully impossible.
Exchange of RX data between affected BTS
will be impossible. As a result, reduced gain
from inter eNB UL CoMP feature can be
experienced.
FZC is not be able to establish any Z1 links

and discover FZAPs.
Degraded - BER exceeds major Cells/sectors for which configuration

BER threshold (calls are possible, mismatch is detected cannot be set up and
but there may be some cell are disabled.
problems).
Working - BER exceeds minor Calls and data transmissions are possible
BER threshold but less than major and quality may be degraded because of
BER threshold (no cell problems). increased BER on the optical connection.
Out of order - Cell cannot operate

because there are not enough DSP core configuration failure. Inter-site CA
available and needed resources: may not work but basic cell service isn't
Tx or Rx. impacted.
Degraded
Out of order - Cell can
- Cell still operate
cannot operate
because it still has enough
because there are not enough The affected antenna carrier(s) is(are)
available
available and
and needed
needed resources:
resources: deactivated. The cell is disabled if the
both Tx and
Tx or Rx. Rx. severity is Critical.
Degraded - Cell can still operate
because it still has enough The affected antenna carrier(s) is(are)
available and needed resources: deactivated. The cell is disabled if the
both Tx and Rx. severity is Critical.
5G BTS, AirScale SBTS, Flexi LNA is not working properly since DC

SBTS: configuration is incorrect.
- Degraded in - case of consistent
SW after SW fallback Source unit has an inconsistent SW version.
All LAA cells configured on the radio module

are disabled and cannot be used as Scell in
downlink carrier aggregation.
The cells that are assigned to the radio

module are placed out-of-service or
degraded.
Automated RF Scan Test cannot be

performed now
performed now.

performed now.

performed now.
5GRAP is unavailable.


RF module is not taken into use.
This fault has no effect on the BTS

operation.
Radio interface on TD-LTE cells is disabled.
The configuration of
desiredPmax/antennaGain etc. will result in
the TX power level violating FCC limitation.
The PDU is out of use.
The configuration is failed in C-plane and no

cells are enabled; GNB is not operational
If the update of the cell was not successful,

reconfigured cells are not on air.
The cell is considered as sleeping based on
Antenna RX RTWP counters and thresholds
defined by the customer. Even if an alarm
due to the fault is reported, the cell may still
provide
The cell services but the
is considered asservices
sleepingare
based on
degraded.
RACH Setup Attempt counters and
thresholds defined by the customer. Even if
an alarm due to the fault is reported, the cell
may still is
The cell provide services
considered but the services
as sleeping based on
are degraded.
RRC connection setup attempt counters and
thresholds defined by the customer. Even if
an alarm due to the fault is reported, the cell
may still provide services but the services
are degraded.
All products:
The EPIMC will not perform PIM
Cancellation. This may degrade site
performance.
All products:
EPIMC unit calibration is ongoing and
affected cells are not serving any users.
All products:
EPIMC unit is working but EPIMC feature
cannot be enabled.
The unit is not operational. Some cells might

be
Theout
BTSof service.
cannot perform power group switch
on in order to perform the switch on of the
cell allocated to it. The power group is still
switched off (shutdown) and impacted cell(s)
- Out Of Order = cell doesn’t have are failed.
any working channels.
- Degraded = unit still has enough
available and needed resources to
operate. The affected cell will be degraded or failed.
The cell is not operational.
Software/configuration is not copied from

active to passive partition in the BTS.
LTE cell shall work as in the previous

Both paired
spectrum LTE cell
shared and WCDMA
configuration cell shall
as configured
be disabled and don't provide any
by SBTS OAM or updated from paired service
WCDMA or GSM cell.
This might result in not using shared
spectrum at all or might interfere with the
spectrum used by WCDMA or GSM cell
Depends on KPI formula defined by
operator.

operator.

operator.

operator.

operator.

operator.

operator.

operator.

operator.

operator.

operator.

operator.

operator.
operator.

operator.

operator.

operator.

operator.

operator.

operator.
If fault signature is enabled then an operator

is notified about the power reset of
secondary system
If fault signature is module.
enabled then it is
provided to the Operator in a form of alarm
notification enriched with additional
information about the crash or failure that
had happened.
The RF module could not be on-air; the

affected cell operational state is disabled.
The fault has no further consequences.

NE cannot be integrated to NMS and cannot
start. M-plane connection to NMS isn't
established. BTS cannot be managed
remotely.
Autonomous site reset is triggered if allowed
as recovery action. If fault signature is
enabled (actFaultSignature is true) then fault
holds information about the source of crash.
The LTE cell is disabled and cannot provide
any service.
Degraded (there is no other The BTS master clock (OCXO) tuning is

available and usable input halted , the BTS synchronization drops to
reference source to be selected) holdover mode if possible.
The operator is informed that the
commissioned NRCELL-beamSet.tiltOffset
is not supported by the Radio, meaning the
SLS 6db criteria is not met anymore.
Recovery action is being initiated. Particular

phases can be activated by Operator.

phases can be activated by the Operator.

phases can be activated by Operator.
The cells for which the fault is reported are

not on air.

cells. Problems might occur in calls through
the affected cells.
Small Cell:
The cell is disabled and unable to provide
Carrier Aggregation feature cannot Carrier
service Aggregation
(7653 CELL feature will7116
FAULTY, not be
BASE
be activated. Cells can be activated
STATION SERVICE PROBLEM). can be
at all for the SBTS. Cells
processed only locally. processed only locally.
Flexi Zone Micro: The cell is unable to provide service (7654
- Out of order (7653 or 7116) CELL OPERATION DEGRADED, 7655
- Degraded (7654 or 7116) CELL NOTIFICATION, 7115 BASE
- Working (7655 or 7115) STATION INFORMATION)
All cells belonging to the blocked RAT are in

blocked state with
The impacted radioallmodule
its consequences.
is out of use.
It is not possible to unblock a cell from a
blocked RAT, i.e. RAT unblock must be
used instead.
The BTS does not report to the NMS any
Cell
faultsconfiguration
related to thefailed and RAT
blocked cell isornot
to on
theair.
modules commissioned to the blocked RAT.
Fault-sending to the BTS Element Manager
is always enabled. The fault cancellations
are always sent to the NMS.
All the subsequent KPI formula events are
ignored in current time interval.
The host cell and NB-IoT cell are both

operational.
Neither host performance
The NB-IoT cell, nor guardband NB-IoT cell
of one of
is operational.
guardband or inband NB-IoT downlink
carrier may downgrade because the position
is too close to the band edge. The NB-IoT
downlink channel power may be below
configured power boost +6 dB.
The host cell and guardband NB-IoT cell are

both not operational.
Degraded: This status applies only
for managed object with MRBTS.
O-RU topology is unknown or O-
RU is not identified by O-DU yet. The BTS cannot send the VES events to
Out of order: This status applies ONAP VES Endpoint.
Degraded: This status applies only
only for managed object
for managed object with MRBTS.with
RMOD. O-RU topology
O-RU topology is unknownis already
or O- Netconf SSH setup will fail.
known or O-RU is previously
RU is not identified by O-DU yet. O-DU can not manage O-RU.
identified by O-DU.
Out of order: This status applies O-RU will be out of service
only for managed object with
RMOD. O-RU topology is already Netconf SSH setup will fail.
known or O-RU is previously O-DU can not manage O-RU.
identified by O-DU. O-RU will be out of service.
Netconf SSH setup will fail.

O-DU canwill
Operator notbe
manage
warnedO-RU.
about this abnormal
O-RU
case. will be out of service
O-DU will still pass server authentication.
O-DU SSH connection with O-RU will still be
setup.
Degraded: O-RU will go into service normally.
Degraded: ThisThis status
status applies
applies only
only
for
for managed
managed object
object with
with MRBTS.
MRBTS.
O-DU
O-DU failed to store the
failed to store the default
additional Netconf SSH setup will fail.
"sudo"
"sudo" NetConf
NetConf user
user account
account toto a
a O-DU can not manage O-RU.
secured filesystem storage.
secured filesystem storage. O-RU will be out of service
Out of order: This status applies
only for managed object with Additional Netconf creation or provision to
RMOD. O-RU rejects the O-RU will fail, and it cannot be used to
configuration request from O-DU. improve security.
UTC time is not correct on reported node.
Fault informs operator that active RF SW is

in a newer version than the RF SW active on
BTSs sharing radio.
When the feature activation flag is set to true
on the secondary BTS, and the secondary
BTS raises the fault, then SW upgrade on
shared radio cannot be initiated by
secondary BTS.
No effect on primary BTS.
Malicious users can exploit the situation,

connect to BTS, and perform undesirable
actions.
Malicious users can exploit the situation,

connect to BTS, and perform undesirable
actions.
Transceiver is not compliant with the BTS

host
The installed transceiver could not be
identified as a qualified Nokia MN BTS item.
There is a high risk that it may not work as
expected, hence this SFP may also lead to a
degraded BTS System performance.
[Q]SFP+/[Q]SFP28 transceiver cannot

activate the laser.
This fault can
Baseband cardprevent the recovered
has been BTS from from the
functioning
crash, therewhen
is no the FHSon
impact and
BTSradio unit(s)
services
(connected to it are
reported alarm needed
BASE for the required
STATION
cell configuration.
INFORMATION/BASE STATION
NOTIFICATION with Warning severity)
Baseband card to
Cells assigned has
thebeen
radiodisabled
module(s)without
impact
connectedon BTS
to theservices
shared (reported alarm
FHS are working,
BASE STATION
but their capacityINFORMATION/BASE
might be affected.
STATION NOTIFICATION with Minor
severity)
The
The objects
detectedthat exceed card
baseband the BTS capabilities
crash has
Working - recovery reset counter are not supported.
impact on BTS services. There might be
has not been exceeded problems in the calls through the affected
Out of Order - recovery reset cells (reported alarms BASE STATION
counter has been exceeded, SERVICE PROBLEM/CELL OPERATION
Baseband card shutdown. DEGRADED/CELL FAULTY)
In case the feature is enabled in
'RuProtectEnabled' mode, it reports the
incapability of RU to establish IPSec
connection and the radio module is out of
use.
Cell is not operational.
In case, the feature is enabled in
'RuProtectOptional' mode, it reports the
incapability of RU to establish IPSec
connection and the plain text connection is
No further
allowed actions
with thoseare
RUstaken bydo
which BTS.
not
support IPSec. The operator can manually
disallow the plain text connection per RU
with the parameter
'plainTextConnectionAllowed'.
Carrier Aggregation problem appears due to
incorrect cell mapping on BB pools. Carrier
aggregation service is affected, but the BTS
is working.
The cell in question is out of service
The cell cannot provide service.

The
TDD,cell cannotSBTS,
AirScale provide service.
Flexi BTS FDD, Flexi
Out of order
Working: (In -case
In case all CPRI
of the carriers
RU BTS TDD, Flexi SBTS:
are deactivated
has been phased out in release N, Calls are not
Flexi BTS FDD,possible
Flexi BTSthrough
TDD,theAirScale
affected
Degraded
but still be -used
In case not all
in CPRI carriers
mode in cell(s)
BTS TDD, AirScale BTS FDD, Flexicell
or calls are possible but the SBTS,
are deactivated
release N+1). capacity and
AirScale SBTS: performance might decrease.
Out of order: (In case of the CPRI A neighbor relation, which has been created
RU has been phased out in by ANR,
If the unitisstatus
not used becausetothe
is changed outmaximum
of order
release N, but still be used in CPRI number
by this of cells
fault, thenthat
all can
cell be configured
service on thisper
radio
The fault isobject,
frequency raisedperif a LTE
1xRTT neighbor
CELL exceeds
mode in release N+2 or onward). are stopped.
relation, which
the 3GPP limit is
of detected
the maximum by a UE
of 32through
cells,
measurements due to activated
or the O&M threshold for maximum number ANR
features,
of e1xCSFB could not cells
target be stored because the
per frequency
maximum
(rttMaxNumCsfbTargets). eNB relations
number of neighbor will per
cell is already reached.
nevertheless create the LNRELX instance
but blacklist the corresponding mobility type
(for example: SRVCC, CSFB). The operator
may decide to manually optimize the
neighbor relations.
UEs are not aware of the omitted MBMS

SAIs.
Both the host and its NB-IoT cell are

disabled.
FDD-TDD Carrier Aggregation is not working
Cell cannot be set up.
Cell performance is decreased.

The "Fault ID Name" information field
identifies the type of overload detected:
- TrOne refers to trigger UPOVT1, which is
speech quality-based detection on the user
plane.
- TrTwo refers to trigger UPOVT2, which is
quantity-based detection per TTI on the user
plane.
- TrThree refers to trigger UPOVT3, which is
a long delay-based check of PDSCH on the
user plane.
In case of U-plane overload, the system
initiates actions to decrease the amount of
The
load PHICH transmission
by limiting the traffic power is not
or the functionality
boosted
on enough, or at all, as compared to
the traffic.
the
The operator's
system setting.
performance might
In case of U-plane overload, thebe degraded
system
especially in cases where
initiates actions to decrease the amount of the U-plane
overload
load by limiting countermeasures
the traffic orare
theenabled.
functionality
The
on "Fault
the ID
traffic. Name" information field
-identifies
Cell indicate remote
the
operation type
is interference
of overload
downgraded. happens
detected: and
The
uplink system
channels,performance
including might
SRS on be UpPTS,
degraded
-especially
TrOne refers to trigger
in casesPRACH UPOVT1,
where the which is
PUSCH,quality-based
speech PUCCH, areU-plane
detection impacted.
on the user
overload
-plane. indicate countermeasures
remote interference aremitigation
enabled.
The
functions "Fault ID
will beName" information field
-identifies
TrTwo refers
the totriggered.
type trigger
of
Consequently,
UPOVT2,
overload which is
detected:
Cell operation
following parameters
quantity-based is downgraded.
detectionmight
perbeTTI
temporary
on the user
-configured
TrOne refers to trigger
by the LTE cellUPOVT1,
according which is
to real
plane.
speech quality-based detection on the user
situation:
-plane.
TrThree refers to trigger UPOVT3, which is
>prachPwrRamp
->iniMcsUl
TrTwo refers to trigger UPOVT2, which is
user plane.
quantity-based detection per TTI on the user
>deltaPreMsg3
plane.
>actUlsps
->actUlLnkAdp
TrThree refers to trigger UPOVT3, which is
>actUlMuMimo
user plane.
>ulsSchedMethod
>actTmSwitch
These parameters are dynamically adjusted
by eNB and might be different to online
values before
No channel this faultand
frequency is cleared.
Duty Cycle
changes can be made in the LAA cell.
The eNB disables the unlicensed cell. An
action
Currentfrom the operator
eNB/cell is needed
is disturbed by theto enable
the cell.
identified remote eNBs, and as a
consequence, its ownisRI-specific
The current eNB/cell cosnideredsequence
as a
representing a specific eNB
source of remote interference identity
due toismutual
sent
in DwPTS, which slightly decreases
interference from the identified, remote
downlink throughput.
eNBs, therefore the special subframe will be
temporarily reconfigured to SSF5 (3: 9: 2),
other than online configuration, to avoid
impact on a network that will reduce
downlink throughput by almost 16%.
CELL will work, but without DSS.
CELL will work, but without DSS
CELL will work, but without DSS

The LTE cell works sharing its spectrum with
the peer NR cell in a restricted way. Some of
the online re-configuration changes have
been ignored.
uses dedicated spectrum only, and is not
able to share spectrum with paired NR cell
The
usesLTE cell willspectrum
dedicated work without
only sharing its
and is not
spectrum
able to share spectrum with paired NRcell
which prevents the peer NR cell.
from operating.
In case the radio unit set is blocked (both
DSS partner cells are disabled), this fault
might be visible for few seconds before it’s
cancelled during cell disable procedure.
The LTE cell will work without sharing its

spectrum which prevents the peer NR cell
from operating.
The LTE cell works sharing its spectrum with
the peer NR cell in a restricted way. Some of
the online re-configuration changes have
been ignored.
The LTE cell will work without sharing its

spectrum
Flexi BTS which prevents
FDD, Flexi BTSthe TDD,peer NR cell
AirScale
from operating.
BTS TDD, AirScale BTS FDD, Flexi SBTS,
AirScale SBTS:
For
The S1:
LTEThecelleNB loseswithout
will work the connection
sharing itsto S-
GW. All calls
spectrum using
which the failed
prevents the GTP-U
peer NRdata cell
path
from are released, and new GTP-U data
operating.
Dynamic
tunnels are Spectrum Sharing
not created feature
for the failed GTP-U
functionality
data path until it works again. LTE cell
is available. Paired
could not use requested sharing ratio and
The
LTE S1 interface is unavailable.
messages/broadcast information
For X2: The eNB has lost the connection to
towards
the gNB. UE
All might
SCG be delayed.
split bearers usingforthe
If no other S1 interface is available use,
failed GTP-U data path are released
BTS operation is considered faulty and and no
new
calls GTP-U
can be data tunnels are not created for
set up.
the failed GTP-U data path until it works
again.
If there is at least one other S1 interface
Degraded - there is still at least available for use, BTS operation is
one S1 interface available for use considered degraded but can continue
Out of order - no other S1 interface operation (that is, set up calls) using the
available for use. available S1 interfaces.
The X2 interface is unavailable. Handover of
calls to or from cells of the associated
adjacent BTS is not possible. Base station
(BTS)
One ofoperation is considered
the transport degraded.
paths (SCTP) in SCTP
connection to the MME has failed. This is
only applicable when SCTP multi-homing is
supported. An alternate transport path is
available to continue operation.
AirScale SBTS:
The
One M3 interface
of the is unavailable,
transport paths (SCTP)and
in MBMS
SCTP
service cannot be provided.
connection to MME (which provides MBMS
service) has failed. This is only applicable
when SCTP multi-homing is supported. An
alternate transport path is available to
pursue the operation.
The BTS is not configured according to the
radio network plan file. The BTS is waiting
for the correct radio network configuration
file.
In the case of subscriber trace activation, if

the
Thefailed
cell istrace connection was used for
disabled.
sending the trace reports, the BTS considers
the trace activation for that subscriber as
failed.
The
In thecell is disabled.
case of cell trace and interface trace,
if the failed trace connection was used for
sending the trace reports, the BTS does not
start tracing until the trace connection is
established successfully.

BTS FDD,
startupFlexi SBTS, AirScale
is interrupted, SBTS,
and the BTS Flexi
is
BTS FDD:
not operational.
The BTS cannot accept new UEs of a given
RAT type attempting registration in any of
The trace session
the reported (for subscriber
misconfigured PLMNs.or cell
Such oran
interface or PCMD report) cannot be
attempt by new UEs results in call failure at
activated
the BTS. or deactivated.
The UEs that might have been already

registered in misconfigured PLMNs remain
unaffected.
The fault has no effect on the base station
operation, but the LNADJ, LNADJL, or both
LNADJ and LNADJL objects have not been
stored in the
The fault haseNB.
no effect on the base station
operation, but LNADJW object with the
Flexi BTS FDD,WCDMA
newly-learned Flexi BTS TDD, AirScale
neighbor cell
BTS TDD, AirScale
configuration throughBTS FDD, Flexi SBTS,
ANR-specific
AirScale SBTS:was not stored in the eNB.
measurements
The
The fault
fault has
has no
no effect
effect on
on the
the base
base station
station
operation, but LNRELW object
operation. The WCDMA neighbor with newly-
relation,
learned WCDMA neighbor relation
which is reported by a UE due to activated
configuration
ANR features,through
has beenANR-specific
stored, but at least
measurements was not stored in
one of the mobility parameters of the
the eNB.
LNRELW (csfbPsHoAllowed, psHoAllowed,
and srvccAllowed) has been set to
"forbidden" because it has exceeded the
limit. (Refer to the section "Meaning").
No handover can be performed to cells with
the
If anaffected PCI
X2 link is and frequency.
available, no type of
handover to the neighbor cell is possible at
all.
If the UE-based ANR is activated, there will
be continuous retries to resolve the ECGI.
The following features are deactivated (if

configured to be used):
The handover
- Enhanced failure rate
Inter-eNB for the affected
Interference
cell might
Cancelationincrease.
- Multimedia Broadcast Multicast Service
- Inter-eNB Carrier Aggregation
- Network-Assisted Interference Cancelation
and Suppression
The handover failure rate for the affected

cell
Cellsmight be increased.
and eNBs remain in service, but
features related to "Inter eNB Carrier
Aggregation"
If the maximum that requireofconsistent
number allowed neighbor-
parameters between
related objects is reached, clusterthe members
eNB does arenot
taken
allow
Cells andout of service.
the creation
eNBs remain of additional
in service,neighbor-
but
related
featuresobjects
relatedeither through
to "Inter O&M or X2
eNB Carrier
Setup/X2
Aggregation" Configuration
that requireUpdate.the sameIf aSW
measurement report on
version between cluster members arethe signal power or
taken
quality of the neighbor is received, handover
out of service.
preparation
The eNB continuesis triggered,
normal butoperation,
no new objectand is
created.
automatic A result
neighbor of this might
relation be that no X2
Other
link is features
established related
with to
suchthehandling
"Inter eNB
neighbor,
is not
or that
impacted,
Carrier that is, neighbor-related
Aggregation" feature objectsan
that require
the
can CGI is known
be created for
throughsuch BTS.
inter-eNB link are taken O&M out ofor X2
service.
Setup/X2 Configuration Update.
New
If the objects
numbercan be stored
of objects again
in the when the
database
number of neighbor-related
increases further and reaches, or even objects in the
BTS
exceeds, the configured value of thethe
database is below the value of
parameter
parameter "maxNumAnrMoiAllowed".
"maxNumAnrMoiAllowed",
automatic neighbor-relation functionality is
degraded, and an alarm indicating "Overload
detected: max number of neighbor relation
objects reached" is raised.
'Inter eNB Carrier Aggregation'-related
features requiring cluster-wide phase
synchronization are taken out of service in
the cluster.
SRIO
BTS iscannot be setbut
operational upsystem
and features
level (inter-
requiring SRIO link cannot be activated
BTS) carrier aggregation functionality is in-
between the connected NEs
degraded. Carrier aggregation with the
misconfigured carrier aggregation relations
is not possible. However, carrier aggregation
with the other, properly configured carrier
aggregation relations is working normally.
necessary for L3 application is unavailable.
Cells configured to use the resources cannot
be put into use.
If actForceAutoReset is set "false", an
autonomous reset of LTE RAT will be
performed unless
Flexi BTS FDD, it will
Flexi BTS disable
TDD,any working
AirScale
cell.
If actForceAutoReset
AirScale SBTS: reset is set "true", an
autonomous
The BTS cannot continue RAT
reset of LTE will be All
to operate.
performed. For details, see parameter
cells are disabled.
actForceAutoReset definition.
As long as the number of allowed
autonomous
The cell cannotBTS resetsservice
provide has nottoyet
thebeen
User
exceeded, an autonomous
Equipment (UE). PUSCH masking BTS reset will be
performed in an attempt
activation, together to recover.PUCCH
with automatic
configuration for a cell where the PUSCH
mask area setting, results in not enough
consecutive uplink resource blocks (UL RBs)
for PRACH allocation.
The BTS operates normally, but the number
of active User Equipment (UE) in the cell is
limited to the automatic allocated values
coming from the lookup table.
Features that depend on the GTP tunnel
between two Flexi Zone Access Points like
the Inter Flexi Zone Access Points Carrier
Aggregation are disabled.
Features that depend
The cell cannot provideonservice
the condition
to a UE.ofThe
the
link for inter-site CA, like the Inter-site
activation of ProSe Direct Communication, or
Inter Flexiwith
together Zone Access PUCCH
automatic Points Carrier
Aggregation, are disabled.
configuration, for a cell are such that the
configuration of the sidelink transmit
resource pool overlaps with PUCCH, or
results in insufficient
The alarm is raised ifconsecutive resources
a 1xRTT neighbor cell,
for PRACH allocation.
which is detected by a UE through
measurements due to activated ANR
features, could not be stored because the
maximum number of instances is already
reached.
Handovers from or to the cells of the related

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

BTS are not possible.
Unit status is Degraded if at least
one other S1 interface is
operational, or else the Unit status The S1 interface is not available for call
is Out of order. setup, and existing calls are released.
Unit status is Degraded if at least
one other S1 interface is
operational, or else the Unit status The S1 interface is unavailable, and the BTS
is Out of order is not available for call setup.
If the update of the TAC or PLMN identities
is not successful, the eNB performs S1
setup, which means service loss for the
affected cells.
The System Information for the related
GERAN or UTRAN neighbor cells is not
reliable, and will not be provided to the UEs,
which are released with redirect.
System Information for the related GERAN
or UTRAN neighbor cells is not reliable and
will not be provided to UEs, which are
released with redirect.
UEs that attempt to connect through normal
call are released immediately after
completion of the to
UEs that attempt RRC connection
connect through normal
establishment.
call or emergency call are released
immediately after completion of RRC
connection establishment, and requests for
incoming inter-eNB or inter-RAT handovers
are rejected.
Handovers to cells of the related adjacent

BTS are not possible.
There is no X2 connectivity to gNB and, for

example, mobility features and dual
connectivity
Some of the do notwith
UEs work.
a complete set of
system information of the cell stored that has
left the cell, and has come back within three
hours, might not recognize that there was a
system information change.
Until cancellation of the fault BTS will not
proceed with incoming reconfigurations. The
online modification of NB-IoT parameters
procedure takes long time.
UEs are not aware of the omitted carrier
frequencies and corresponding inter-
frequency neighboring and/or blacklisted cell
list items.
The cell is not operational.

The operation-impacted cell is broadcasted
with 'cell barred' in system information,
which results in the limited support of
ongoing calls and blocking new calls.
Cell is about to enter AC Barring and part of

the UEs with the bigger barring factor cannot
attach to the cell.
Cat-M UEs are not aware of the omitted
carrier frequencies and corresponding inter-
frequency neighboring and/or blacklisted cell
list items.
CatM UEs are not aware of the omitted
PLMN-based ACB settings.
UEs are not aware of the omitted NR carrier

frequencies for cell reselection.
This fault has no effect on the BTS

operation.
RF Module is not used as shared radio

module
There is high memory usage, which might

result in memory outage.
The cell operation is degraded.

BTS FDD:
No impact on FSP operation.

Flexi BTS TDD:
Critical impact on FSP/ABIx operation.

Out of order (FSP/FBB/ABIx when No
BTScritical
TDD, impact onBTS
AirScale FSPFDD,
operation.
Flexi SBTS,
shutdown) AirScale SBTS:
The BTS capacity decreases, or the BTS is
Degraded(FSP/FBB/ABIx not
Flexioperational.
BTS FDD, TheFlexiDigital Signal
BTS TDD, AirScale
otherwise) Processing (DSP) does
Out of order (FSP/FBB/ABIx when BTS TDD, AirScale BTS FDD,not work correctly.
Flexi SBTS,
The BTS capacity decreases, or the BTS is
Degraded(FSP/FBB/ABIx not
Flexioperational.
BTS FDD, TheFlexiDigital Signal
BTS TDD, AirScale
otherwise) Processing (DSP) does
Out of order (FSP/FBB/ABIx when BTS TDD, AirScale BTS FDD,not work correctly.
Flexi SBTS,
AirScale SBTS, Flexi SBTS: The BTS capacity decreases, or the BTS is
Out of order (FSP/FBB/ABIx when not operational. The Digital Signal
otherwise)
shutdown) Processing (DSP) does not work correctly.
AirScale SBTS, Flexi SBTS: The BTS capacity decreases, or the BTS is
Degraded(FSP/FBB/ABIx not operational. The DSP does not work
otherwise) correctly.
Flexi BTS FDD/TDD, AirScale BTS
FDD/TDD:
Out of order (FSP/FBB/ABIx when
shutdown)
Flexi BTS FDD/TDD, AirScale BTS
Flexi BTS FDD/TDD, AirScale BTS FDD/TDD:
The GPS remains in service and is used to
FDD/TDD: The BTS capacity
the maximum decreases,
possible extent. or the short
If the BTS isor
Degraded(FSP/FBB/ABIx not operational.
overcurrent The Digital
is marginal, thenSignal
the effect might
otherwise) Processing
be reduced (DSP) does
detection of not
GPS work correctly.
satellite signal
strength, which at times might lead to
intermittent occurrences of the GPS
unusable as a time synchronization
reference alarm.

Access Point, or Flexi Zone SFN Antenna is
not operational.
The specified multi-carrier cell is disabled

because of the lock or block of the other
multi-carrier cell.
X2 links from neighboring eNBs to this eNB

fails to establish.
Channel frequency and duty cycle changes

cannot be made on the LTE-U/LAA cell.
Channel frequency changes cannot be
made on the LTE-U/LAA cell. The eNB
disables the LTE-U/LAA Cell. Operator
action is needed to enable the cell.
AirScale BTS:
are
Thedisabled.
current LTE-U Duty Cycle is in an
indeterminate state because a change from
the existing Duty Cycle to a new Duty Cycle
has
The failed.
BTS canThestill
eNB disables
realize NTPthe LTE-U Cell.
frequency
Operator action is needed to enable
synchronization unless communication thewith
cell.
all configured servers are not realized. If the
BTS reference oscillator calibration is still
valid, the BTS continues to operate in
synchronization holdover mode.
The BTS takes more time than usual to
come into service when using the Network
Time Protocol (NTP) frequency reference
source.
AirScale BTS TDD:

AirScale BTS TDD: Out of order The cell is not operational.
AirScale BTS TDD: AirScale BTS TDD:

Out of order The cell is not operational.
AirScale BTS TDD:
AirScale BTS TDD: Out of order The cell is not operational.

- Out of order (7653 or 7116) The cell is not operational.

- Out of order (7653 or 7116) The cell is not operational.
AirScale BTS TDD:

AirScale BTS TDD: The cell is disabled and unable to provide
- Out of order (7653 or 7116) service (7653 CELL FAULTY).
AirScale BTS TDD:

- Out of order (7653 or 7116) service (7653 CELL FAULTY).
AirScale BTS TDD:

- Working (7655 or 7115) service (7653 CELL FAULTY).
AirScale BTS TDD: The cell is deregistered with the SAS server,
-- Out
Working (7655
of order or 7115)
(7653 or 7107) and the CBSD will attempt re-registration.
-- Working (7655
Out of order or 7115)
(7653 in case
or 7116) In
of eNB can't get heart
case of PreTxMeasurementbeat
response
response from SAS in time in case
timeout. AirScale BTS TDD:
of
- Working (7115 or state
the "authorized" 7655) If The cell is not operational.
PreTxMeasurement gets NACK AirScale BTS TDD:
response in case that configured The cell is not operational in case of fault
cells under the CBSD get grant severity is critical.
and on transmission No impact in case of fault severity is minor.
Channel frequency changes cannot be

made on frequency
Channel the Multefire cell. cannot be
changes
made on the Multefire cell. The eNB
disables the Multefire Cell, and actions from
the
Theoperator action are
current Multefire neededisto
channel in enable
an the
cell.
indeterminate state because a change from
the existing channel to a new channel has
failed. The eNB disables the Multefire Cell,
and actions from the operator are needed to
enable the cell.
The M3 interface is unavailable, and MBMS

service can no longer be provided.
The warning is triggered by the eNB if the
MME could not be informed about the
modified values through the MCE
configuration update
The M3 interface procedure after
is unavailable, several
and MBMS
retries.
service can no longer be provided.
There
The eNB arestops
insufficient or no
all active resources
MBMS sessionsfor
MBMS session broadcasting. Start of
and waits for new session requests from theMBMS
sessions
MME if the may be suspended
update by MCE
of the global eNB dueID orto
lack of resources.
MBMS service area identities was not
successful.
1. If the update
A failed max number
of theof MBMS
MCE sessions
name is per
MCE is exceeded,
tolerated the MCE/eNB responds
by the eNB.
to MME with MBMS SESSION START
FAILURE.
MBMS
2. If thesession
sessionisissuspended,
suspended which might
because the
cause interference with other eNBs.
resources are not enough in any MBSFN
supporting the requested service area, the
MCE/eNB responds to MME with MBMS
SESSION START RESPONSE indicating
success.
The MBMS session is started in at least one
but
Flexinot
BTSall FDD,
affected MBSFN
Flexi areas.
BTS TDD, AirScale
Nevertheless,
BTS TDD, AirScale BTS FDD, Flexiwith
MCE/eNB responds an
SBTS,
MBMS SESSION
AirScale SBTS: START RESPONSE
indicating
The MBMSsuccess.
session is suspended in at least
one MBSFN areas.
Nevertheless, MCE/eNB responds with an
MBMS SESSION START RESPONSE
indicating success.
The input voltage problem may have an
unknown impact on PDU outputs and
devices that
are connected to them.
The input voltage problem may have an

unknown impact on PDU outputs and
devices that are connected to them.
The BTS does not function correctly. Some
baseband processing resources in the BTS
are out ofuC
DOXCO use. Cells supported
is broken, the initialby faulty FSP
docxo
are disabled.
temperature (after power on) and uptime
cannot be provided, and the DOXCO
temperature is not monitored. BTS
synchronization may be lost, and holdover
operation in runtime could be unsuccessful.
System module
The alarming card or
module Baseband
continues card is
to operate
not operational where the fault is detected,
with the currently installed SW version.
and some/all cells are disabled.
Restarting the alarming module will stop it.
In case the alarming module is FCT,

restarting this module will stop the eNB.
The alarming module continues to operate
Restarting the HW unit during update of the
degraded flash content may stop the
alarming module.
In case the alarming module is FCT,
restarting this module during update of the
degraded flash content may stop the eNB.
The alarming module continues to operate

The unit is not operational. Basic services

may be affected.
The FSP unit is out of use.
[Q]SFP can't be used.
SFP can't be used.
This BTS is Out of Order since reliable

message communication cannot be granted.
The SMOD/BBMOD unit is out of use.
The BTS capacity decreases or BTS is not

operational. LTE Hardware Accelerator
engine does not work correctly.

operational. LTE Hardware Accelerator
engine does not work correctly.

Degraded - Cell can operate in SA operational. LTE Hardware Accelerator
mode only but it is configured for engine does not work correctly.
both (SA+NSA) mode.
For, NSA mode cell also
'Degraded' is raised even though The gNB services are degraded due to a cell
cell is actually
Degraded not
- Cell is operational.
operational not being on air.
either in SA mode only or in NSA
mode only.
Out of order - Cell is not If the update of the cell was not successful,
operational. the reconfigured cells are not on air.
Degraded - Cell can operate in
NSA mode only but it is configured
for both (SA+NSA) mode.
For, SA mode cell also 'Degraded'
is raised even though cell is The gNB services are degraded due to a cell
actually not operational. being not on air.
Cells of the TAC are barred. Cells of the

TAC cannot be selected by a UE in IDLE
mode.
No NSA UE can connect to the gNB.
The cells of gNB which have
NRBTS/NRCELL/cellDepType set to "NSA"
or "Both" shall be impacted.
The gNB services are out of order due to
inconsistent F1AP: Reset management (i.e.
Release of existing F1AP UE contexts)
between gNB-DU and gNB-CU.
The gNB services are out of order. An F1AP

procedure fails due to protocol error
detection.
None All calls over the affected gNB-DU are failed.
None All calls over the affected AMF are failed.
None All calls over the affected AMF are failed.
All Xn based handover over the affected

None gNB peer are failed.
All Xn based handover over the affected

None gNB peer are failed.
NSA calls over the affected eNB are failed.
The gNB services are out of order.
No HO based on Xn can be done.

A gNB initiated Reset has been triggered
because of some event in the gNB. The UE
contexts impacted by the Reset are to be
released.
A gNB initiated Reset has been triggered
released.
An AMF initiated Reset has been triggered
released.
An AMF initiated Reset has been triggered
released.
The gNB services are blocked with this AMF

because of the NG connection towards the
5GC not being established.


No NSA UE can connect to the gNB for this

Degraded LTE eNB.
A gNB initiated RAN Configuration message
has been rejected by the AMF. The gNB
shall either retry the message or not, based
on the CAUSE value in the response.
A gNB initiated RAN Configuration message
has not responded to by the AMF. The gNB
shall retry the message till a configured max
number of retries.
A gNB initiated NG Reset message has not

responded to by the AMF. The gNB shall
locally release the affected UE contexts.
The gNB has received an AMF initiated
Error Indication message. The gNB shall
locally clear all resources related to the
ongoing procedure and mark it as failed.
No additional X2 link setup can be accepted

by gNB
No call can be set up over the gNB-DU even
though cell appears online(due to SW
limitation).
The gNB-DU is not available for calls due to
inconsistent F1AP: Reset management (i.e.
Release of existing F1AP UE contexts)
between gNB-DU and gNB-CU.
No call can be setup over the gNB-DU.

The F1AP procedure fails due to protocol
error detection. The F1 interface is
unavailable and the gNB-DU is not available
for calls.
None All calls over the affected gNB-DU are failed.
No call can be setup over the affected gNB-

None DU.
If the update of the cell was not successful,

the reconfigured cells are not on air.
The cell won't work, as DSS is not working
because the gNB SW and eNB SW are not
compatible, it is not possible for the NR cell
to go to air.
The cell won't work, as no partner cell can
be found. Dynamic Spectrum Sharing
feature functionality is restricted. The NR cell
is not on air.
CELL won't work. Dynamic Spectrum

Sharing feature functionality is restricted.
The NR cell is not on air.
The cell won't work. Dynamic Spectrum

The cell won't work. Dynamic Spectrum

The cell will not work (but its state shall be
degraded due SW limitation). Dynamic
Spectrum Sharing feature functionality is
restricted. The NR cell is not on air.
The cell won't work. As the DSS feature in
Degraded - Cell is on air and [if the remote peer is deactivated, the NR Cell
PsCell_SystemInfoConfigurationR is not on air.
esp is received with status=NOK
and cause!=0 OR with status=OK
and cause!=0 OR CP-RT detects
SIB1 is over SI TBS size limit of The cell won't work.
372 bytes].
Out of order - Cell is not on air and
[PsCell_SystemInfoConfigurationR
esp is received with status=NOK
OR CP-RT detects SIB1 is over SI The cell won't work.
TBS size limit of 372 bytes]. During
cell setup, if nrofRBs calculated for The gNB services are either "out of order" or
CSI-RS for beam management is "degraded". Please see "Unit status
less than 24. attributes" column for details.

Sharing feature functionality in DL is

Sharing feature functionality in UL is


Aperiodic switch couldn't work (e.g. no

emergency warning.)
Cell not on Air. Awaiting activation from CU

for cell to be taken into service.

In the case of subscriber trace activation, if
the
Thefailed trace connection
gNB services are out ofwas used for
order.
sending the trace reports, the BTS considers
the trace activation for that subscriber as
failed.
The UP slices counters are not updated
based on the
In the case of new slice configuration.
cell trace, interface trace &
PCMD, if the failed trace connection was
used for sending the trace reports, the BTS
does not start tracing until the trace
connection is established successfully.
Out of Order - when affected unit A3/A5 event cannot trigger NSA HO and
is not able offering Services SgNB is released immediately.
Degraded - affected unit
capabilities are degraded Possible the BTS capacity will be affected.
Working – affected
Out of Order - whenunit capabilities
affected unit Some cells may be out of order or degraded
are not affected.
is not able offering Services or not affected.
capabilities
Out of Orderare degraded
- when affected unit Possible the BTS capacity will be affected.
is not able offering unit capabilities Some cells may be out of order or degraded
are not
Servicesaffected. or not affected.
capabilities
are not
capabilities
are not
capabilities
are not
capabilities
are not
capabilities
are not
capabilities
are not
Working – affected unit capabilities Some cells may be out of order or degraded
are not affected. or not affected.
Out of Order - when affected unit
is not able offering
Services
Working – affected unit capabilities Some cells may be out of order or degraded
are not affected. or not affected.
Thisdata
No alarm
or is raised
clock if the User
information Event
is exchanged
Temporary buffer reaches threshold limit.
via this interface.
Possible
Possible impact
impact onon the
the connections over this
The
interface: communication linkconnections
between theover localthis
interface:
BTS and the BFD peer is defective. No
-communication
voice calls or data connections are aborted
is possible.
-and no cannot
calls arebepossible
established anymore
The
-- loss interface
of remotecannot be used
management for
access to
remote
transmission. management
The laser connectivity
of the is lost
SFP module
other
and network
cannot elements
be established anymore
cannot
-- loss be switched on.
loss of
of synchronization
synchronization ifif the the interface
interface is is
used
used as a synchronization
as a synchronization source
An Ethernet Link cannot besource successfully
-established
depending since
on use of down.
it is the Ethernet interface,
the
No above
TheEthernet described
possibledata impact
or clock
effects are the can occurisfor
information
following:
the local BTS and/or
exchanged via this interface. other (S)BTS elements
if- No
they are chained via
calls are possible. the Ethernet interface
Possible impact on the connections
- There is loss of remote management over this
interface:
access to other network elements.
- voice
IKE SAscalls or IPsec
and data connections
SAs cannot cannot be be
established or rekeyed.
- remote management connectivity cannot
be established
The
- lossinterface cannot be used
of synchronization if the for
interface is
transmission. It can be
used as a synchronization source used for connectivity
checks
- depending only. on use of the Ethernet interface,
the above described impact can occur for
the local BTS and/or other BTS elements if
they are chained through the Ethernet
interface.
The Certificate Revocation List could not be

The SFP New
updated. is notrevoked
operational.
certificates remain
unknown to the BTS.
The interface of the SFP module cannot be
Normal
used fortraffic is interrupted. Only loopback
transmission.
OAM frames are
The laser of the SFP transmitted
module and received
cannot be
over the interface.
switched on. If the test frame generator
is switched on, test frames are transmitted.
No data or clock information is exchanged
through this interface
The Ethernet interfaceofmight
SFP be module.
out of order,
or the remote peer might be out of order.
The following
Traffic might get arelost.
the possible impact on the
connections over this interface of the SFP
module:
The Ethernet
- Voice calls orinterface is defective,
data connections or thebe
cannot
remote peer
established. is defective. Traffic might get
lost.
- The remote management connectivity
cannot be established.
- There is loss of synchronization if the
interface is used as a synchronization
source.
Possible impact:
- slow management access to the BTS and
other network elements in the network
- poor voice quality and data performance
The performance management data

collected on this on
Possible impact interface becomes invalid.
the connections over the
interface in question:
-Possible
loss of remote
impact management accessover
on the connections to this
other network
interface: elements in the RAN

- loss of remote management access to
other networkimpact
The possible elements in the
on the RAN
connections over
this interface are:
- The SL-PPP/ML-PPP interface is not
available.
-The
Loss of remote
possible management
impact access. over
on the connections
this interface are:
- No calls are possible anymore.
- Loss of remote management access to
other
Impactnetwork
on the elements in the
connections RAN.
over this
interface:
- There is loss of remote management

access.
The transport connection toward the remote

peer might be defective. Traffic might get
lost.
The transport connection towards the

remote peer may be defective. Traffic may
get lost.
The requested service is not available.
SSH to BTS is allowed. It shall be disabled

as
Thesoon as access islink
communication no between
longer needed.
the local
and the remote peer is defective or the peer
is defective.
Transport service may not be available and
calls may be dropped.
The communication link between the BTS
and the BFD peer is defective. Transport
service may not be available and calls may
be dropped.
Possible impact on the connections over this
interface:
- Increased packet delay variation and
increased average delay for all voice/packet
and management connection
- Increase of packet loss due to congestion
- Loss of synchronization/Timing source lost
with Timing over Packet (IEEE1588v2) due
to increased packet delay variation
-This
Loss of synchronization/Timing
alarm is an indication that the source lost
backhaul
with Synchronous
capacity foristraffic Ethernet
with the that
same profile as
This alarm an indication the backhaul
this TWAMP session (DSCP value, packet
capacity for traffic with the same profile as
size) may be session
this TWAMP too small, because
(DSCP thepacket
value,
measurement packets are scheduled
size), may be much too small, because later
than before.
some of the measurement packets seem to
have been thrown away.
The TWAMP measurement packets are lost

because of degraded traffic throughput.
None
Reauthentication of existing and

establishment of new IPsec and TLS
sessions may fail.
The ML-PPP interface operates with

reduced capacity.
SyncE is no longer a working

synchronization source.
SyncE is no longer a working

synchronization source.
There will be a failure of CBRS service if

CBRS vendor certificate subsequently
expires or has expired.
There will be a failure of CBRS service if

additonal trust anchor for SAS server has
already expired.
The local peer will not be able to go "online"

Out of order (when source is TOP) BTS performs
as there switchover
is already to another
a remote ToP
peer operating
Working (RMOD case) master if available.
with the IP address the local peer intended
to go "online".
The remote peers continue their operation

without disruption.
All configured IPsec policies are ignored,

and all the BTS traffic is sent unprotected.
The resulting packet capture files can used
for Expert analysis to identify network
problems and to help determine the best
course of action.
No further logins are permitted for that

account until it is unlocked.
BTS traffic has switched over from the
primary IPsec tunnel to secondary (backup)
IPsec tunnel terminating on secondary
security gateway.
The IKE SA cannot be established.
IKE SA cannot be established and

subsequently no IPsec SAs can be
established.
The related IPsec SA cannot be established

and used.
This alarm alerts technicians to the fact that
the expert mode is active and any expert
mode associated configuration changes may
cause IPsec instability or failure.
None.
User can make configuration change on
BTS or obtain information from BTS via
Local Management Port $port. Operator
should validate that the access is made by
authorized personnel.
Access to BTS from R&D Service Ports is

allowed. It will be disabled as soon as
access is no longer needed.
Given FQDN is not used to connect to the

service or service does not work.
No functional impact.
Unable to send traffic for Ipsec tunnels

which have not been established.
Degraded (Switchover is not The primary link between the local BTS and
successful) the peer is defective. The communication is
possible only through secondary link when
Warning (Switchover is successful) link aggregation switchover is a SUCCESS.
IPsec protected traffic has switched over
from the primary IPsec tunnel or secondary
(backup) IPsec tunnel to public safety
tunnel.
Features, which require the availability of the

XP interface, won't work.


XP connection, won't work.


None
Reported Alarms
7101
7115
7111
7652
7115
7650
7651
7652
7653
7108
7101
7115
7115
7651
7116
7652
7650
7651
7652
7653
7654
7116
7101
7101
7115
7115
7116
7116
7650
7651
7652
7653
7107
7101
7111
7115
7650
7107
7651
7652
7653
7654
7655
7115
7652
7115
7652
7115
7652
7111
7655
7115
7651
7652
7654
7111
7655
7115
7651
7652
7654
7655
7103
7652
7995
7102
7653
7102
7650
7100
7101
7101
7652
7115
7650
7651
7652
7653
7112
7112
7115
7650
7651
7112
7652
7115
7653
7650
7651
7652
7653
7654
7101
7116
7101
7116
7115
7114
7114
7101
7116
7112
7115
7116
7116
7101
7116
7116
7116
7101
7116
7112
7115
7115
7101
7116
7114
7115
7115
7115
7115
7112
7115
7115
7115
7115
7100
7115
7651
7652
7654
7100
7115
7651
7652
7654
7115
7652
7115
7652
7115
7652
7115
7652
7115
7652
7115
7101
7652
7115
7116
7651
7100
7652
7101
7653
7115
7650
7651
7101
7652
7115
7653
7116
7650
7651
7653
7654
7115
7652
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7103
7115
7652
7111
7115
7115
7652
7650
7651
7101
7652
7115
7653
7116
7654
7650
7651
7652
7653
7654
7101
7115
7112
7116
7653
7650
7651
7101
7652
7115
7653
7116
7654
7650
7651
7652
7653
7101
7654
7108
7115
7650
7651
7652
7100
7650
7108
7651
7100
7650
7113
7115
7652
7654
7113
7115
7652
7113
7654
7115
7652
7653
7654
7655
7113
7115
7652
7653
7654
7113
7115
7652
7654
7100
7115
7652
7653
7654
7100
7115
7652
7653
7101
7654
7115
7116
7652
7653
7654
7113
7115
7652
7654
7113
7115
7652
7654
7113
7115
7652
7654
7113
7115
7652
7654
7113
7115
7652
7654
7113
7115
7652
7654
7113
7115
7652
7654
7111
7650
7653
7654
7108
7650
7114
7653
7113
7115
7652
7654
7113
7115
7652
7654
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7113
7115
7652
7654
7115
7108
7115
7650
7651
7652
7108
7115
7101
7651
7115
7652
7116
7652
7653
7654
7101
7655
7111
7115
7652
7653
7654
7111
7115
7652
7101
7654
7115
7116
7652
7653
7654
7101
7115
7116
7652
7653
7101
7654
7115
7116
7652
7653
7654
7101
7116
7115
7654
7116
7652
7653
7654
7101
7655
7115
7116
7652
7101
7653
7115
7654
7116
7652
7653
7101
7654
7115
7655
7116
7652
7653
7654
7101
7655
7115
7116
7652
7653
7101
7654
7115
7116
7652
7653
7654
7115
7116
7652
7654
7115
7116
7652
7115
7654
7116
7652
7653
7654
7655
7100
7115
7652
7653
7654
7111
7115
7652
7100
7654
7101
7115
7652
7653
7101
7654
7115
7116
7652
7653
7654
7115
7116
7652
7654
7111
7115
7652
7654
7102
7115
7652
7653
7654
7115
7652
7115
7652
7115
7652
7115
7652
7115
7116
7652
7653
7115
7654
7116
7652
7653
7654
7655
7115
7652
7115
7652
7100
7115
7652
7653
7654
7115
7116
7652
7654
7101
7655
7115
7116
7652
7653
7654
7113
7115
7652
7653
7654
7115
7652
7115
7116
7652
7654
7655
7100
7115
7652
7653
7654
7115
7116
7652
7653
7654
7115
7116
7652
7653
7100
7654
7101
7115
7652
7653
7654
7100
7115
7652
7653
7654
7115
7116
7652
7654
7115
7116
7652
7653
7654
7115
7116
7652
7653
7654
7112
7115
7652
7653
7654
7115
7116
7652
7653
7654
7115
7652
7655
7115
7116
7652
7653
7654
7115
7116
7652
7653
7654
7116
7650
7101
7116
7650
7116
7653
7101
7115
7652
7653
7654
7115
7652
7101
7655
7115
7116
7652
7653
7654
7101
7115
7116
7652
7653
7654
7115
7116
7652
7654
7112
7115
7652
7101
7653
7114
7654
7115
7116
7652
7653
7654
7114
7654
7101
7115
7652
7655
7101
7115
7652
7655
7115
7652
7655
7115
7652
7101
7655
7115
7116
7652
7653
7654
7115
7652
7655
7115
7652
7655
7115
7655
7115
7116
7653
7654
7115
7655
7100
7115
7652
7653
7654
7100
7115
7652
7653
7654
7115
7116
7652
7653
7654
7115
7116
7652
7654
7115
7116
7652
7654
7115
7116
7652
7654
7100
7115
7101
7652
7115
7655
7650
7651
7652
7653
7654
7100
7115
7651
7652
7653
7112
7115
7651
7652
7654
7115
7116
7652
7654
7111
7115
7650
7101
7651
7115
7652
7116
7653
7650
7651
7652
7653
7654
7115
7116
7651
7652
7654
7115
7116
7651
7652
7654
7115
7116
7651
7652
7654
7100
7101
7650
7101
7651
7115
7652
7116
7650
7651
7652
7100
7653
7115
7650
7651
7652
7653
7101
7116
7650
7101
7651
7115
7652
7116
7650
7651
7652
7653
7115
7116
7651
7652
7654
7101
7116
7114
7112
7116
7115
7107
7115
7112
7115
7112
7112
7115
7115
7112
7112
7115
7115
7115
7113
7115
7652
7654
7115
7655
7115
7655
7115
7655
7115
7116
7115
7116
7115
7116
7101
7115
7116
7111
7650
7100
7651
7652
7653
7654
7650
7655
7651
7652
7653
7654
7655
7652
7653
7654
7652
7653
7650
7654
7651
7652
7653
7654
7655
7650
7651
7652
7653
7650
7654
7651
7652
7653
7654
7655
7652
7650
7651
7650
7652
7651
7652
7653
7654
7655
7651
7652
7650
7651
7652
7654
7655
7652
7653
7654
7655
7101
7115
7652
7116
7654
7650
7651
7652
7653
7654
7100
7103
7107
7115
7108
7655
7110
7111
7112
7113
7112
7114
7653
7115
7116
7220
7101
7115
7650
7115
7652
7651
7116
7652
7650
7653
7651
7101
7654
7652
7115
7655
7653
7116
7656
7650
7657
7651
61028
7652
61029
7653
61050
61104
61150
61151
61152
7115
7652
7112
7115
7650
7652
7653
7101
7112
7115
7653
7116
7650
7651
7652
7653
7112
7115
7652
7653
7654
7112
7115
7653
7655
7113
7653
7654
7113
7115
7652
7654
7115
7652
7655
7115
7652
7655
7108
7115
7650
7651
7652
7101
7116
7113
7115
7652
7654
7112
7115
7652
7653
7654
7115
7652
7112
7653
7654
7115
7116
7650
7651
7653
7111
7115
7115
7652
7650
7651
7652
7111
7653
7115
7654
7650
7651
7652
7653
7654
7112
7111
7653
7115
7654
7650
7651
7652
7653
7654
7111
7115
7650
7652
7653
7116
7653
7654
7101
7115
7115
7652
7116
7650
7651
7652
7653
7111
7115
7650
7652
7115
7652
7115
7652
7101
7108
7650
7652
7101
7115
7652
7101
7115
7652
7101
7115
7652
7101
7115
7652
7115
7652
7113
7115
7652
7654
7655
7113
7115
7652
7654
7111
7115
7650
7652
7653
7108
7651
7108
7650
7115
7652
7101
7116
7650
7651
7115
7115
7652
7116
7651
7652
7653
7654
7115
7652
7101
7116
7650
7651
7116
7650
7116
7650
7116
7650
7651
7108
7651
7108
7650
7101
7108
7650
7115
7116
7652
7653
7115
7652
7115
7652
7100
7651
7112
7650
7651
7115
7652
7116
7651
7115
7652
7113
7115
7652
7654
7115
7116
7652
7653
7654
7112
7653
7113
7115
7652
7116
7653
7654
7101
7107
7650
7111
7650
7102
7650
7114
7653
7116
7651
7112
7650
7115
7652
7115
7652
7115
7652
7115
7652
7113
7115
7652
7654
7115
7652
7655
7115
7652
7101
7108
7650
7112
7115
7652
7653
7112
7654
7112
7115
7652
7653
7654
7115
7112
7652
7115
7650
7652
7653
7655
7115
7652
7115
7220
7650
7652
7111
7651
7112
7651
7107
7651
7107
7651
7110
7658
7101
7107
7650
7115
7652
7108
7115
7650
7651
7652
7108
7115
7650
7651
7652
7108
7115
7650
7651
7652
7108
7115
7650
7651
7652
7115
7655
7112
7114
7651
7654
7115
7655
7100
7115
7652
7653
7654
7100
7115
7652
7653
7654
7220
7651
7108
7651
7108
7653
7115
7652
7115
7652
7115
7652
7115
7652
7655
7115
7116
7652
7654
7115
7652
7115
7116
7651
7652
7654
7101
7116
7652
7653
7110
7658
7101
7116
7650
7101
7115
7115
7652
7116
7650
7651
7652
7653
7115
7652
7101
7107
7650
7115
7652
7115
7652
7102
7650
7110
7658
7101
7115
7116
7652
7653
7114
7650
7114
7650
7114
7650
7114
7650
7114
7650
7101
7116
7650
7112
7650
7114
7653
7112
7115
7652
7653
7115
7652
7115
7116
7652
7653
7112
7115
7652
7653
7112
7115
7652
7653
7112
7115
7652
7653
7112
7115
7652
7653
7114
7653
7114
7101
7653
7115
7116
7650
7652
7653
7108
7115
7652
7654
7115
7655
7115
7652
7115
7652
7111
7651
7112
7653
7107
7651
7116
7650
7651
7112
7115
7652
7653
7102
7101
7115
7115
7116
7650
7651
7652
7653
7115
7652
7115
7652
7115
7112
7654
7115
7655
7115
7652
7112
7651
7115
7652
7115
7652
7112
7114
7653
7112
7651
7108
7115
7651
7652
7101
7108
7114
7112
7115
7652
7653
7115
7652
7220
7101
7114
7652
7654
7113
7654
7113
7654
7115
7655
7115
7652
7107
7651
7107
7651
7112
7651
7112
7115
7116
7652
7654
7655
7116
7654
7114
7653
7654
7114
7653
7654
7100
7115
7111
7652
7115
7654
7650
7651
7652
7653
7654
7114
7653
7112
7653
7654
7115
7652
7115
7652
7115
7652
7115
7652
7101
7114
7653
7114
7653
7112
7115
7652
7653
7654
7115
7114
7653
7115
7655
7116
7650
7101
7116
7114
7101
7114
7652
7654
7101
7114
7652
7654
7101
7114
7652
7654
7115
7655
7116
7654
7101
7115
7115
7655
7116
7650
7651
7652
7653
7101
7115
7116
7652
7653
7114
7653
7654
7114
7115
7652
7114
7115
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7655
7115
7652
7115
7652
7112
7653
7115
7652
7107
7650
7101
7116
7650
7652
7112
7108
7115
7651
7652
7115
7101
7114
7652
7654
7101
7114
7652
7654
7101
7114
7652
7654
7114
7115
7116
7112
7651
7115
7116
7653
7654
7655
7112
7114
7102
7650
7115
7652
7114
7653
7115
7655
7114
7653
7115
7220
7220
7220
7220
7220
7220
7115
7652
7115
7652
7115
7652
7655
7220
7220
7100
7651
7100
7651
7100
7653
7112
7115
7652
7653
7115
7116
7651
7652
7101
7115
7115
7116
7652
7653
7654
7112
7115
7652
7116
7650
7115
7114
7114
7653
7114
7653
7116
7653
7115
7654
7116
7655
7650
7652
7653
7654
7655
7115
7655
7115
7655
7115
7655
7112
7653
7115
7652
7114
7653
7114
7654
7115
7655
7115
7655
7114
7654
7114
7654
7115
7655
7115
7655
7115
7655
7114
7653
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7115
7655
7107
7657
7107
7656
7657
7107
7657
7107
7657
7107
7657
7115
7652
7112
7650
7114
7653
7114
7653
7115
7652
7112
7650
7115
7652
7116
7651
7115
7652
7115
7652
7115
7652
7115
7652
7115
7655
7115
7652
7115
7655
7115
7652
7115
7655
7112
7651
7111
7651
7107
7651
7107
7651
7115
7652
7107
7651
7112
7651
7112
7651
7101
7116
7651
7652
7653
7101
7116
7650
7652
7112
7653
7115
7655
7107
7651
7107
7651
7112
7653
7115
7652
7107
7657
7107
7657
7107
7656
7657
7107
7656
7657
7115
7652
7107
7657
7107
7657
7115
7652
7115
7652
7107
7657
7107
7657
7115
7655
7115
7655
7115
7655
7111
7653
7114
7654
7115
7655
7115
7655
7115
7655
7115
7655
7115
7652
7112
7115
7652
7653
7654
7115
7652
7655
7116
7654
7115
7652
7655
7115
7652
7655
7115
7101
7652
7115
7655
7116
7650
7651
7101
7652
7115
7653
7116
7650
7651
7101
7652
7115
7653
7116
7650
7651
7101
7652
7115
7653
7116
7650
7651
7652
7653
7101
7115
7116
7650
7651
7652
7653
7115
7652
7101
7116
7652
7114
7653
7112
7651
7114
7654
7114
7653
7114
7653
7114
7653
7108
7651
7115
7652
7116
7653
7116
7653
7116
7653
7116
7653
7116
7653
7116
7653
7116
7653
7115
7655
7115
7655
7107
7115
7653
7654
7655
7115
7116
7653
7655
7114
7654
7114
7653
7114
7653
7107
7657
7107
7657
7112
7651
7115
7652
7115
7652
7115
7652
7115
7652
7115
7652
7115
7652
7115
7101
7652
7115
7116
7650
7651
7653
7111
7101
7651
7115
7116
7650
7651
7653
7100
7115
7651
7654
7100
7115
7651
7654
7115
7652
7101
7655
7115
7116
7650
7651
7653
7100
7115
7650
7651
7653
7100
7115
7652
7653
7654
7100
7115
7652
7653
7654
7100
7650
7112
7115
7650
7651
7101
7653
7115
7116
7650
7651
7101
7653
7115
7116
7650
7651
7101
7653
7115
7116
7650
7651
7653
7114
7114
7114
7116
7107
7107
7107
7107
7107
7107
7107
7107
7107
7107
7107
7115
7115
7115
7115
7107
7107
7107
7107
7116
7116
7116
7115
7115
7107
7107
7107
7107
7107
7101
7107
7114
7114
7114
7114
7112
7114
7114
7114
7114
7114
7114
7112
7112
7112
7112
7115
7115
7101
7107
7101
7107
7107
7107
7115
7115
7115
7222
7222
7222
7222
7222
7222
7222
7222
7222
7222
7220
61022
61028
61029
61030
61040
61050
7220
61075
61076
61077
61079
61104
61150
61151
61152
61250
61251
61252
61410
61411
7220
7220
61605
61606
61607
61610
61611
7220
7220
61622
7108
7115
7651
7652
7108
7115
7651
7652
7220
7220
7115
7652
61632
61639
61641
7220
61643
61644
61645
61646
61647
7220
7220
7220
61654
61655
61657
61662
61663
7107
7657
7107
7657
7107
7657
7107
7657
7107
7657
71106
station:
Flexi SBTS, AirScale SBTS, Flexi Zone Access Point,
If
Flexi category
Zone SFN alarms are enabled
Antenna: 7115 (customer
BASE STATION configured
actCategoryAlarms
INFORMATION == true):
- When fault affects basic
when autonomous recovery services
reset of is the
beingbase station:
performed
7116
due toBASE STATION SERVICE PROBLEM
the fault:
-All When fault does
Platforms: 7101not affect
BASE basic services of the base
STATION/UNIT
station:
AUTONOMOUS RESET NOTIFICATION
-If When category autonomous
alarms arerecovery
disabledreset is being performed
(actCategoryAlarms ==
due
false)to the fault:
7101
Flexi
Reported BASE
SBTS, STATION/UNIT
AirScale
Alarms SBTS: AUTONOMOUS RESET
Description
NOTIFICATION
7650 BASE STATION FAULTY (1. FSM; 2. The failure
If
in category FSP/ABIxalarms does not are have
enabled any(customer
impact on configured
the
actCategoryAlarms
If category alarms
functionality of anyare == true):
cell,disabled
but after(actCategoryAlarms
the failure, all ==
7115
false):
FSPs/ABIx's BASE STATIONin the BTSINFORMATION
are already not operational)
7650
7651 BASE STATION FAULTY OPERATION (FT) DEGRADED (The
If
7650 category
BASE alarms
STATION enabled
are disabled
FAULTY (customer configured
(actCategoryAlarms
(The ==
failure
actCategoryAlarms in FSP/ABIx does
== not
true): have anyfaulty
impact FSPonor ABIx
the
false):
is not
functionality mapped to any cell,
of anyfrequency and
cell, and at all FSPs and
least continues: ABIx's
one FSP/ABIx in the
All
7652
BTS products
BASE
are when
STATION
faulty) tuning
NOTIFICATION (for FCT7115(HW
the
BASE BTS is
STATION still operational)
INFORMATION
rel.3),
7651
7653 FCT
BASE
CELL (HW
STATION
FAULTY rel.4), FTMfailure in FSP/ABIx
OPERATION
(The DEGRADED makes(Thethe
All
faulty products
FSP or when frequency
ABIx areis not tuning
mapped toisanypaused:
cell, 7108
and at
cell
If
BASE disabled)
categorySTATION alarms enabled
SYNCHRONIZATION (customer configured
PROBLEM
least
7652 one
actCategoryAlarms BASE other FSP
STATION or NOTIFICATION
== ABIx is operational)
true): (Autonomous
7652
-recovery BASE resetSTATION
is being NOTIFICATION
performed due (FSM
to the FAN,
basefault
If
external
When
category fault
ALD,
affects
alarmsFCT
basic
disabled
[HW
services of the
(actCategoryAlarms
rel.3]/PWR_LINE_IF, ==or
station:
PDU)
fault
7116
false): does
BASE not affect
STATION basic services
SERVICE of the
PROBLEM base station)
-7653
All When CELL
productsfaultFAULTY
does not
when
(FR
affect
frequency
[Thebasiccellservices
tuning
cannot operate
continues:of the base
because
station: it does not have enough available and7652
needed
If
BASE categorySTATION alarmsNOTIFICATION
are enabled (customer configured
resources:
7115 BASETx or Rx; MHA,
STATION TILT, [but the cell is already
actCategoryAlarms
All products when == INFORMATION
true) tuning is paused: 7651
frequency
faulty
--BASE When because
autonomous of other faults])
recovery reset is being performed
-due when
When fault
STATION
fault affects
affects basic
OPERATION
basic services of
of the
DEGRADED base
baseisstation
7653 toCELL
If category the FAULTY
fault:
alarms (The services
enabled faulty
(customerFSP the
or ABIx
configured
station:
mapped
7111 BASE STATION SOFTWARE MANAGEMENT
to
7101 the cell)
BASE
actCategoryAlarms STATION/UNIT== true) AUTONOMOUS RESET
PROBLEM
7116CELL BASEOPERATION
STATION SERVICE PROBLEM
7654
NOTIFICATION
All Products: 7116 DEGRADED (FR, [The cell
- when fault does notBASE
affectSTATION
basic services SERVICEof the base
can
PROBLEM still operate because it still has enough available
station
-and When fault does not affect basic services of the base
If needed
category resources: both Tx and Rx, MHA, TILT])
7115
station: BASEalarmsSTATION are disabled
INFORMATION (actCategoryAlarms ==
-false):
when autonomous recovery reset is being performed
7650
If7115
due toBASE
category STATION
alarms
the fault: FAULTY
disabled (1. FCT; 2. The failure
(actCategoryAlarms == in
FSP/ABIx BASE doesSTATION
not have INFORMATION
any impact on the functionality
false) BASE STATION/UNIT AUTONOMOUS RESET
7101
of any cell, but
-- Small after the failure, all FSPs in the BTS are
When Cell:
NOTIFICATION
already
7650
autonomous
not operational;
BASE STATION
recovery
3. RMOD)reset FAULTY
is being performed
due to
7651 BTS the
BASE fault:
STATION OPERATION DEGRADED (The
Flexi TDD, AirScale BTS TDD, Flexi BTS FDD,
failure
AirScale in BTS
FSP/ABIxFDD, does
Flexi not
SBTS,have any impact
AirScale SBTS: on the
7101 BASE of
functionality STATION/UNIT
anyare and atAUTONOMOUS
cell,disabled least one FSP in RESET
the BTS
If category alarms
NOTIFICATION (actCategoryAlarms ==
is still
false) operational)
7652
7650 BASE BASE STATION
STATION NOTIFICATION
FAULTY (FTM or(Autonomous all FSPs,
recovery reset is being performed due to the fault)
ABIx's)
7653
7651 CELL BASE FAULTY
STATION(The failure in FSP/ABIx
DEGRADED (FSP, ABIx) makes the
cell is disabled)
(uncommissioned FR or uncommissioned FHS)
7653 CELL FAULTY (commissioned FR or FHS,[The
cell cannot operate because it does not have enough
available and needed resources: Tx or Rx.])
7654 CELL OPERATION DEGRADED (commissioned
FHS, [The cell can still operate because it has enough
available and needed resources: both Tx and Rx.])
7655 CELL NOTIFICATION (commissioned FHS, [The
cell can operate; all needed resources available: both Tx
and Rx.])
Please note that in case of FHS, the cell is specified as

the one behind the FHS.
If category alarms enabled (customer configured
actCategoryAlarms
If category alarms are ==enabled
true) (customer configured
7115 BASE
actCategoryAlarms == true) STATION INFORMATION
- when fault affects basic services of the base station
If
If category
7111 BASEalarms
category STATION
alarms disabled (actCategoryAlarms
SOFTWARE
are enabled MANAGEMENT
(customer ==
configured
false)
PROBLEM
actCategoryAlarms == true)
If
7652 category alarms are enabled (customer configured
-7115 whenBASE
actCategoryAlarms BASE STATION
fault does
STATIONnot NOTIFICATION
==affect
true) basic
INFORMATION services of the base
If
station category alarms are enabled (customer configured
-actCategoryAlarms
when fault affects basic services of the base station
== INFORMATION
true)
7115
If
7111 BASE
category
BASEalarms STATION
STATION are disabled
SOFTWARE (actCategoryAlarms
MANAGEMENT==
7115 INFORMATION
false)
PROBLEM
AirScale
7652
-If when BASE BTSdoes
fault FDD,
STATIONnot AirScale BTS services
NOTIFICATION TDD, AirScale SBTS,
Flexi category
BTS alarms
FDD, areaffect
Flexi disabled
BTS
basic
TDD, Flexi SBTS:
of the base
station
false)
If
7115 category
BASEalarms STATION are disabled
7652
false) NOTIFICATION (FCT (HW rel.3),
FCT
7651 (HW
BASE rel.4))
STATION OPERATION DEGRADED
AirScale
7655 CELL BTS FDD, AirScale
NOTIFICATION BTS TDD,
(FR) AirScale SBTS,
(FCM/FCT)
Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS:
7654
If category CELLalarmsOPERATIONare disabledDEGRADED (FR)
7655
false) CELL NOTIFICATION (FR, if incompatible SW
version
7651 BASEhas been
STATIONdetected on a unit)DEGRADED
OPERATION
If category
7652 BASE alarms
STATION enabled (customer configured
NOTIFICATION
(FCM/FCT)
If category alarms are
actCategoryAlarms ==enabled
7654
7103 CELL BASE OPERATION
actCategoryAlarms STATION DEGRADED
== EXTERNAL
true) ALARM(FR)
-7655 when
NOTIFICATION CELL
fault NOTIFICATION
affects basic (FR,
services if incompatible
of the SW
base station
version
7100 BASEhas been
STATIONdetected
7995 MAINS BREAKDOWN WITH BATTERY BACKUP on
HARDWARE a unit) PROBLEM
-7652
iswhen BASE
reported STATION
faulttowards
does not NOTIFICATION
affect
BSC. basic services of the base
station
If
7115 category
BASEalarms STATION are enabled
INFORMATION (customer configured
If category alarms disabled (actCategoryAlarms ==
actCategoryAlarms
-false) when autonomous== true) reset is being performed
recovery
All
-due products:7102
when affectsBASE
faultfault
toBASE
the basicSTATION
services ofRESOURCE
the base station
7652
BLOCKED BYSTATION
USER NOTIFICATION
7112
7101 BASE STATION CONFIGURATION
STATION/UNIT AUTONOMOUS PROBLEM
RESET
-NOTIFICATION
when fault does not affect basic
If category alarms are enabled (customer configured services of the base
station
actCategoryAlarms ==disabled
true) (actCategoryAlarms ==
false)
7115
Flexi BASE STATION
All products: 7102 BASE STATIONBTS
SBTS, AirScale INFORMATION
SBTS, Flexi FDD, Flexi BTS
RESOURCE
All
TDD, products:7653
AirScale
BLOCKED BY USER BTS CELLTDD, FAULTY
AirScale BTS FDD:
AirScale
If category BTS FDD,are
alarms AirScale
disabled BTS TDD, AirScale SBTS,
If
Flexicategory
false) BTS FDD, alarms areBTS
Flexi enabled
TDD,(customer
Flexi SBTS: configured
If category
actCategoryAlarms alarms are disabled
==disabled
If
7650 category
false) BASEalarms STATION are FAULTY (actCategoryAlarms
(1. FSM, 2. FTM, 3.==
All
false)
The products:7101
faulty FSP or BASE
ABIx isSTATION/UNIT
not mapped to any cell, and all
All
If products:
category
AUTONOMOUS 7650
alarms BASE
are
RESET STATION
enabled FAULTY
(customer
NOTIFICATION configured
7650
FSPs BASE
or STATION
ABIx'es
actCategoryAlarms == true) in the FAULTY
BTS are (1. FTM,
faulty) 2. The faulty
FSP/ABIx
7651
-If when BASE is not mapped
STATION
faultalarms
affectsarebasic to any
OPERATION
services cell and all
DEGRADED FSPs/ABIx's
of the base station (The
in category
the BASE
faulty BTS or
FSP are faulty.)
ABIx is notdisabled
mapped (actCategoryAlarms
to any cell, and at ==
7112
false) STATION CONFIGURATION PROBLEM
7652
least
-Allwhen BASE
one other
fault STATION
doesFSPnot NOTIFICATION
oraffect
ABIxbasic
is operational)
services(fault
of does not
the base
7653 products:7652
affect basic
CELL services
FAULTY BASE of
(The STATION
the base
faulty NOTIFICATION
station)
FSP/ABIx is mapped to
station
7651
the BASE
cell) STATION
7115 BASE STATION INFORMATION OPERATION DEGRADED (The
faulty
7652 BASEFSP/ABIx is not mapped
STATION NOTIFICATIONto any cell and at least
(Autonomous
one
If other
recovery
category FSP/ABIx
reset is being
alarms is operational.)
performed
are disabled due to the fault or ==
(actCategoryAlarms
7653
fault CELLnot
false)does FAULTY (2. FSP/ABIx
affect basic services -ofwhen faultystation)
the base
FSP/ABIAx is mapped to the cell)
7650 BASE STATION FAULTY (1. FTM, 2. The faulty
FSP/ABIx is not mapped to any cell and all FSPs/ABIAs
In caseBTS
in the source of the fault is AMxx:
are faulty.)
If category
7651 BASE STATION alarms are enabled
OPERATION (customer configured
DEGRADED (The
actCategoryAlarms == true
faulty FSP/ABIx is not mapped to any cell and at least
7112
one otherBASE STATION
FSP/ABIx is CONFIGURATION
operational.) PROBLEM
If
7652 BASE STATION NOTIFICATION (MHA / RAE ==
category alarms are disabled (actCategoryAlarms /
false)
RET, when the unit is not commissioned)
7650
7653 BASECELL FAULTYSTATION(FSP/ABIx,
FAULTY when a faulty
FSP/ABIx is mapped to the cell)
7654 CELL OPERATION DEGRADED (MHA / RAE /
RET, when a faulty MHA / RAE / RET is mapped to the
cell)
7101 BASE STATION/UNIT AUTONOMOUS RESET
NOTIFICATION (raised only if RESET RECOVERY is
triggered)
When fault affects basic services of the base station:
When autonomous recovery reset is being performed
due to the fault:
NOTIFICATION
7101 RESET NOTIFICATION (when reset is being

performed)
7116 BASE STATION SERVICE PROBLEM (when
reset has not been triggered for any reason)

NOTIFICATION (Raised only if RESET RECOVERY is
triggered.)
7116 BASE STATION SERVICE PROBLEM (When
reset has not been triggered for any reason.)
NOTIFICATION (When reset is being performed.)
7116 BASE STATION SERVICE PROBLEM (When
reset has not been triggered for any reason.)
7112 BASE STATION CONFIGURATION PROBLEM
(At startup when the cell will be out of order.)
7115 BASE STATION INFORMATION (At runtime when
state is working)

NOTIFICATION (when reset is being performed)
7116 BASE STATION SERVICE PROBLEM (when
reset has not been triggered for any reason)

actCategoryAlarms == true):
- When fault affects basic services of the base station:
7100
5G BTS, BASE STATION
AirScale HARDWARE
SBTS. Flexi SBTS:PROBLEM
-If When fault does not affect basic services
category alarms enabled (customer of the base
configured
station:
7115
- When BASE
fault STATION INFORMATION
affects basic services of the base station:
If category
- When faultalarms disabled
does not affect(actCategoryAlarms
basic services of the==base
false):
station:
7651
7115 BASE
BASE STATION OPERATION DEGRADED
STATION INFORMATION
(1.FSM; 2.FSP is not mapped to any cell.)
7654 CELL OPERATION DEGRADED (FSP is mapped
to the
false): cell.)
7652
7651 BASE
BASE STATION
OPERATION DEGRADED(fault does not
affect basic services of the base station)
(1.FSM; 2.FSP is not mapped to any cell.)
7654 CELL OPERATION DEGRADED (FSP is mapped
to the cell.) alarms enabled (customer configured
If category
7652 BASE STATION
actCategoryAlarms == NOTIFICATION
true) (fault does not
affect basic services of
7115 BASE STATION INFORMATIONthe base station)
If
If category
category alarms
enabled (customer configured==
false)
7652
7115 BASE
BASE STATION
INFORMATION
If category alarms disabled enabled (actCategoryAlarms

(customer configured ==
If category alarms are enabled (customer configured
false) true)
7652
If BASE
category STATION
alarms NOTIFICATION
enabled (customer configured
-7115
If When BASEfault STATION
affects
category alarms are
INFORMATION
basic services
enabled of the
(customer base station:
configured
actCategoryAlarms
7100 BASE STATION == true)
HARDWARE PROBLEM
actCategoryAlarms
-If == true)
--If when category
When
category
when
fault
fault
affects
faultalarms
does not
alarms
affects
basic
disabled
enabled
basic
services
affect of the base
(actCategoryAlarms
basic services
(customer
services of the
station
of the
configured
base
==
base
station
7116
false)
station: BASE STATION SERVICE PROBLEM
actCategoryAlarms
7116
-7115 whenBASE STATION
fault does == true)
SERVICE
not affect basic PROBLEM
services of the base
7652 NOTIFICATION
-7115 whenBASE
station BASE STATION
STATION
fault does INFORMATION
INFORMATION
not affect basic services of the base
-station
7115
due toBASE STATION INFORMATION
the fault:
-If
7115
If
7101
category
when BASE
category
BASE
alarms
STATION
autonomous
alarms disabled
enabled
STATION/UNIT
(actCategoryAlarms
INFORMATION
recovery reset is being
(customer
AUTONOMOUS
==
performed
configured RESET
false)
-duewhen
to autonomous
the fault
actCategoryAlarms == true) recovery reset is being performed
NOTIFICATION
7652
7115toBASE
due
7101 the fault
BASE STATION
STATION/UNIT AUTONOMOUS RESET
INFORMATION
7101 BASE
NOTIFICATION STATION/UNIT AUTONOMOUS RESET
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS TDD,
NOTIFICATION
If
If category
AirScale
category BTS alarms
FDD,disabled
alarms Flexi SBTS,
enabled (actCategoryAlarms
AirScale
(customer SBTS: ==
configured
If category
false)
If category alarms
alarms disabled
are (actCategoryAlarms
disabled (actCategoryAlarms == ==
actCategoryAlarms
Flexi
false) SBTS, AirScale ==SBTS,
true) Flexi BTS FDD, Flexi BTS
7652
false):
7115 BASE
BASE STATION
INFORMATION
TDD,
7651 AirScale
BASE BTS TDD,
STATION AirScale BTS
OPERATION FDD:
DEGRADED (The
7650
If BASEalarms
category STATION are FAULTY (actCategoryAlarms
disabled (The failure in FSP or
failure
ABIx in FSP/ABIx
does not have does
any not have
impact on any
the impact on theof==
functionality
If category
false)
functionality alarms
of disabled
anythecellfailure,(actCategoryAlarms
and atallleast one FSP/ABIx ==in the
any
false)
7650 cell,
BASE but STATION FAULTY (The failure in FSPthe
after FSPs or ABIx's in or
BTS
BTS is
are still operational.)
already not any
operational.)
7652
ABIx
7652 BASE
does
BASE STATION
not have
impact on the functionality
NOTIFICATION (autonomous of
7651
any BASE
cell, but STATION
after OPERATION
the failure, all FSPs DEGRADED
or (The
recovery
failure in reset
FSP is ABIx
or being performed
does not have dueanyto ABIx's
the in or
fault
impact on
the
the
BTS
fault are not
does operational.)
notof affect basic services ofone
theFSPbaseorstation)
functionality
7651 BASE any
STATION(Thecell, and
OPERATIONat least DEGRADED ABIx
(The in
7653
the BTSCELL is FAULTY
still operational.) failure in FSP/ABIx makes the
failure
cell in FSP or ABIx does not have any impact on the
isCELL
disabled.)
7653
functionality FAULTY
of any cell,(The and failure in FSP
at least one or ABIx makes
FSP/ABIx in
the cell disabled.)
the BTS is still operational.)
7652
7652 BASE
BASE STATION
NOTIFICATION (autonomous (autonomous
recovery
reset is being performed due due toto the
the fault
fault or
or
fault
fault does not affect basic services of the base station)
does not affect basic services of the base station)
7653 CELL FAULTY (The failure in FSP or ABIx makes
the cell is disabled.)
7654 CELLalarms
If category OPERATION enabledDEGRADED (The failure in
(customer configured
FSP, FBB or ABIx
actCategoryAlarms == true) makes the cell is degraded.)
false)
7652 BASE STATION NOTIFICATION"
7103 BASE STATION EXTERNAL ALARM
NOTIFICATION
If category alarms disabled
actCategoryAlarms == true)(actCategoryAlarms ==
false)
AirScale BTS FDD, AirScale BTS TDD, AirScale SBTS,
NOTIFICATION
If category
7401 - 7447alarms enabled EAC2=7402
(EAC1=7401, (customer configured
etc.)
If category alarms
actCategoryAlarms disabled
== true)(actCategoryAlarms ==
[Small
false) Cell]
7103
7401 BASE
- 7404 STATION EXTERNAL ALARM
AirScale BTS(EAC1=7401,
NOTIFICATION
EAC2=7402,
FDD, AirScale EAC3=7403,
BTS TDD, AirScale SBTS,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
7401 - 7447alarms
If category (EAC1=7401,
disabledEAC2=7402 etc.)
[Small
false) Cell]
7401 - 7404
AirScale BTS(EAC1=7401, EAC2=7402,
EAC4=7404)
7401 - 7447 (EAC1=7401, EAC2=7402 etc.)
[Small Cell]
7401 - 7404 (EAC1=7401, EAC2=7402, EAC3=7403,
EAC4=7404)
NOTIFICATION
false)
NOTIFICATION
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
7401 - 7447alarms
[Small
false) Cell]
7401 - 7404
EAC4=7404)
7401 - 7447 (EAC1=7401, EAC2=7402 etc.)
[Small Cell]
7401 - 7404 (EAC1=7401, EAC2=7402, EAC3=7403,
EAC4=7404)
NOTIFICATION
false)
NOTIFICATION
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
If category
etc.)
If category alarms
[Small
false) Cell]
7103
7401 BASE
NOTIFICATION
EAC2=7402,
EAC4=7404)
7401 - 7447alarms
[Small
false) Cell]
7401 - 7404
EAC4=7404)
7401 - 7447 (EAC1=7401, EAC2=7402 etc.)
[Small Cell]
7401 - 7404 (EAC1=7401, EAC2=7402, EAC3=7403,
EAC4=7404)
NOTIFICATION
false)
AirScale
NOTIFICATION BTS FDD, AirScale BTS TDD, AirScale SBTS,
If
7401 category
- 7447alarms enabled EAC2=7402
etc.)
If category
actCategoryAlarms alarms disabled
== true) (actCategoryAlarms ==
[Small
false) Cell]
7103
7401 BASE
AirScale
NOTIFICATION BTS(EAC1=7401,
BTS TDD, AirScaleEAC3=7403, SBTS,
EAC4=7404)
If category
etc.)
If category
[Small
false) Cell]
7103
7401 BASE
AirScale
EAC4=7404)
If category
etc.)
If category
[Small
false) Cell]
7103
7401 BASE
AirScale
EAC4=7404)
If
7401 category
- 7447alarms enabled EAC2=7402
etc.)
If category
[Small
false) Cell]
7103
7401 BASE
AirScale
EAC4=7404)
If category
etc.)
If category
[Small
false) Cell]
7103
7401 BASE
AirScale
EAC4=7404)
If
7401 category
- 7447alarms enabled
are
(EAC1=7401, enabled (customer
(customer
EAC2=7402 configured
configured
etc.)
If category alarms disabledtrue)(actCategoryAlarms ==
actCategoryAlarms
[Small Cell] == true):
false)
-7103
7401 When BASE fault STATION
- 7404 affects basic EXTERNAL
services ALARM
of theEAC3=7403,
base station:
AirScale
7116
EAC4=7404) BASE STATION SERVICE PROBLEM
-If When
category fault does not affect(customer
basic services of the base
7401
If
If - 7447alarms
category
category alarms
alarms
enabled
(EAC1=7401,
enabled
disabled EAC2=7402
etc.)
configured
station:
[Small
false) Cell]
actCategoryAlarms == INFORMATION
true)
7115
7103 BASE
BASE STATION
STATION EXTERNAL
-7401 when
-AirScale
- 7404
When fault
(EAC1=7401,
BTSaffects
autonomous FDD, basic
AirScale
recovery
EAC2=7402,
services
BTS ofALARM
isthe
TDD,
reset
EAC3=7403,
base
AirScale
being station
SBTS,
performed
NOTIFICATION
EAC4=7404)
FlexitoBTS
due the FDD,
fault: Flexi BTS TDD, Flexi SBTS:
PROBLEM
7401
7101 -BASE
7447alarms(EAC1=7401,
STATION/UNIT EAC2=7402
AUTONOMOUS etc.) RESET
If category
-NOTIFICATION
when fault does not disabled
affect (actCategoryAlarms
basic services of the== base
[Small
false) Cell]
station
7401 - 7404 (EAC1=7401, EAC2=7402, EAC3=7403,
AirScale
7115 BASE BTSSTATIONFDD, AirScale BTS TDD, AirScale
INFORMATION SBTS,
EAC4=7404)
AirScale BTS FDD, AirScale
Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS: BTS TDD, AirScale SBTS,
Flexi
7401 BTS FDD,
- 7447alarms Flexi BTS
(EAC1=7401, EAC2=7402 TDD, Flexi SBTS:
etc.)
If
If category
category alarms disabled
are disabled (actCategoryAlarms
(actCategoryAlarms == ==
[Small
false) Cell]
false):
7401 -BASE
7404 (EAC1=7401,
7650 BASE STATION
actCategoryAlarms
7650 STATION true)EAC2=7402,
== FAULTY
FAULTY (1.
(FCMFSM EAC3=7403,
out2.ofThe faulty
order, FTM
EAC4=7404)
FSP
out of order or the failure in FSP does not have anyBTS
7115 is not
BASE mapped
STATION to any cell,
INFORMATION and all FSPs in the
are
impactfaulty.)
on the functionality of any cell, but after the
7651
If category
failure, BASE
all FSPs STATION
alarms in are OPERATION
the disabled
BTS DEGRADED
(actCategoryAlarms
are (customer
not operational (The
==
already)
If category
faulty FSP alarms
is not are
mapped enabled
to any cell, and configured
at least one
false)
7651 BASE
actCategoryAlarms STATION OPERATION
== true) DEGRADED (The
other
7652
failure FSP
BASE
in FSP isSTATION
operational.)
does notNOTIFICATION
have any impact on the
7115
7652 BASE STATION
BASE STATION INFORMATION
functionality of any cellNOTIFICATION
and at least one(FR, FSPwhen in thethe
BTS
unit
is is not commissioned)
still operational)
If category
7653 CELL alarms are disabled (actCategoryAlarms ==
7652
false) BASE FAULTYSTATION(1.NOTIFICATION
FR [The cell cannot (1. operate
because
Uncommissioned it does not FR;have2. enough
MHA available
or RET workingandfor needed
other
7652
resources: BASETx STATION
or Rx.], NOTIFICATION
2. FSP (when faulty FSP is
BTS; 3. PDU)
mapped
7653 CELL to the cell)) (FR out of order [The cell cannot
FAULTY
7654 CELL OPERATION
operate because it does not DEGRADED
have enough (FRavailable
[The cellandcan
still operate because it still has
needed resources: Tx or Rx.] ot the failure in FSP enough available and
needed
makes the resources: both Tx and Rx.])
cell is disabled)
7654 CELL OPERATION DEGRADED (FR out of order
[The cell can still operate because it has enough
available and needed resources: both Tx and Rx.],
MHA, RET)
If category alarms are disabled (actCategoryAlarms ==
or
false) ABIx, OptIF used for RF-sharing or the failure in FSP
or
7650 ABIx BASEdoesSTATION
not have FAULTYany impact (Theon faulty
the functionality
FSP/ABIx/ of is
any
not cell,
mapped and at
to least
any one
cell FSP
and all or ABIx
FSPs/ABIx's in the BTS
in BTS isare
still
If
If category alarms
category
operational.) alarms are are enabled
enabled (customer
configured
faulty.)
actCategoryAlarms
== NOTIFICATION
true)
7652
7651 BASE
BASE STATION
STATION OPERATION (1.
DEGRADED (The
All products:
-Uncommissioned
when 7112FR;
fault affects BASE
basic2. STATION
services
Optical ofCONFIGURATION
the base
interface that station
is not
faulty
PROBLEM
7108 FSP/ABIx
BASE STATION is not mapped to
SYNCHRONIZATION any cell and at least
PROBLEM
used
one to
other provide
FSP/ABIx transmission for any cell.)
-7653
when fault
CELL does notis(OptIF
FAULTY
operational.)
affect basic
connectedservices of the base
7652
If BASEalarms
category
station STATION are NOTIFICATION
disabled (OptIF The cell
to FR:
cannot
connected operate FRbecause there are not enough available
false)
7115
and BASEtoSTATION
needed
or FHS:
resources: Tx
the faulty
INFORMATION
or Rx. or
optical
the
interface
failure in FSP
is
or
not
All
-ABIx
whenused
products:to provide
7653
autonomous transmission
CELL FAULTY
recovery forisany
reset beingcell.)
performed
7653 makes the cell is disabled.)
due
7654 toCELL
CELL
FAULTY (OptIF connected to FR: The cell
the fault
OPERATION DEGRADED (OptIF available
cannot
7101 operate because there
BASEtoSTATION/UNIT are not enough
AUTONOMOUS RESET
connected
and FR: The cell can still
needed resources: Tx or Rx. or the faulty operate because
FSP/ABIxit
NOTIFICATION
still has enough available and needed resources: both
is mapped to the cell or optIf connected to FHS wherein
Tx
FR and Rx.)
connected
Flexi BTS FDD,toFlexi FHSBTS is mapped
TDD, Flexito the cell.) AirScale
SBTS,
7654
SBTS: CELL OPERATION DEGRADED (OptIF
connected
If category to FR orare
alarms FHS: The cell
disabled can still configured
(customer operate
because it still has
actCategoryAlarms == false) enough available and needed
resources:
7651 BASEboth STATIONTx andOPERATION
Rx.) DEGRADED
(When no other reference clock sources are available.)
7652 BASEalarms
If category STATION NOTIFICATION
are enabled (customer (When there is at
configured
least one more working
actCategoryAlarms == true) reference clock source
available.)
If
If category category alarms
alarms areare disabled (actCategoryAlarms
false)
If category alarms enabled
actCategoryAlarms == true)(customer configured
7650
7108 BASE
actCategoryAlarms BASE STATION
STATION == FAULTY
true)
SYNCHRONIZATION PROBLEM
- When fault affects basic services of the base station
If
7113
If category
BASEalarms
category STATION
alarms enabled
are (customer
ANTENNA
disabled LINE
(customerconfigured
PROBLEM
configured
If category
actCategoryAlarms
-actCategoryAlarms
When alarms
fault does are
==
not enabled
true):
affect (customer
basic services configured
of the base
If category == false)
actCategoryAlarms
When
station
7651 fault alarms
BASE affects
STATION
enabled
== true)
basic (customer
services
OPERATION of theconfigured
base station:
DEGRADED
actCategoryAlarms
7100
7113: BASE
BASESTATION
STATION == HARDWARE
true)
ANTENNA LINE PROBLEM
PROBLEM
7115
- When BASE
affects basic services of the base station
7113
If
When BASE
category STATION
fault alarms
does notare ANTENNA
disabled
affect basic LINE PROBLEM
(actCategoryAlarms
services of the base ==
If
If
-station: category
category
When alarms
alarms
fault does disabled
are
not enabled
(customer
basic of the==
servicesconfigured base
false)
false)
actCategoryAlarms
station
7650 BASE STATION == FAULTY
true)
7115
--7115 When
When BASE
fault
fault STATION
affects
affects INFORMATION
basic
basic services of
services of the
the base
base station
station
7654
All products: CELL OPERATION DEGRADED
7113 BASE STATION ANTENNA LINE
If
-PROBLEM category
When faultalarms disabled
If
false): category alarms disabled (actCategoryAlarms ==
station
-false) When fault does not affect basic services of the base
7652
station BASE STATION NOTIFICATION
-(Uncommissioned
When fault affectssource basic services
or Antenna of the
Linebase
withstation
LNA
All
7654 products:
CELL 7115 BASE STATION
OPERATION DEGRADED INFORMATION
commissioned for other BTS)
-7654 When faultOPERATION
CELL does not affect basic services
DEGRADED of the base
(Otherwise, for
If
stationcategory alarms are disabled (actCategoryAlarms ==
RF
false) using RP1 protocol only)
7652
7653 BASE
CELLFDD, STATION
FAULTY NOTIFICATION
(Otherwise, for RF using IR
Flexi
If categoryBTS alarms Flexi
areBTS TDD,(customer
enabled AirScale BTS FDD,
configured
protocol
AirScale only)
BTS TDD:
actCategoryAlarms
7655
If CELL
category alarms == true)(customer
NOTIFICATION
enabled - In case fault 1836
configured with
7653 CELL
-actCategoryAlarms
when fault FAULTY
affects (mandatory
basic servicesresources
of the that
baseforstation
the cell
severity
are lost) working on commissioned
== true) MHA is affecting
7113
a
-7654 cell BASE
when STATION
fault OPERATION
affects ANTENNA
basic services LINE PROBLEM
of the(the
base stationstill
whenCELL
-7100 fault
BASE does
STATIONnot DEGRADED
affect basic
HARDWARE services
PROBLEMofcell
thecan
base
operate
station because it has enough required resources
-available)
when fault does not affect basic services of the base
7115
station BASE STATION INFORMATION
7652 BASE STATION NOTIFICATION (fault source is
uncommissioned
If category alarmsresource)
are disabled (actCategoryAlarms ==
false)
7652
false) BASE STATION NOTIFICATION (Fault source is
uncommissioned
7653 CELL FAULTY resource)
(All RX CHANNELs used by the
7654 CELL OPERATION
cell are affected.) DEGRADED (Otherwise)
7654 CELL OPERATION DEGRADED (At least one RX
CHANNEL used by the cell is not affected.)
7652 BASE STATION NOTIFICATION (fault source is
an uncommissioned resource)
- when autonomous recovery reset is being performed
If
due category alarms disabled (actCategoryAlarms ==
to the fault
false):
7653
NOTIFICATION CELL FAULTY (The cell cannot remain operational
If category
because alarms
there are enabled
not enough (customer
available configured
RX and/or TX
actCategoryAlarms
resources.) == true)
If
-7654 category
when faultalarms
affectsdisabled (actCategoryAlarms
basic services of the(The
basecell ==
station
false) CELL OPERATION DEGRADED can still
7113
remain BASE STATION
operational ANTENNA
because it still LINE
has PROBLEM
enough available
7653
-If when CELL
faultTX FAULTY
does not (The
affectcell
basic cannot operate
services because
of the base it
RX
does and/or
category
not have resources.)
alarms enabled
enough (customer
available and configured
needed RX and/or
station
7652
actCategoryAlarms BASE STATION == NOTIFICATION
true) (The fault source
TX
7115 resources.)
is
-7654 an uncommissioned
when fault OPERATION
CELL affects unit.)
basic services
DEGRADED of the(The
basecell
station
can still
7113
operate BASE STATION
because it has ANTENNA
enough LINE PROBLEM
available and needed
If
-RX category alarms disabled (actCategoryAlarms of the==
If when
false)
faultTX
and/or
category does not
resources.)
alarms affect (customer
enabled basic services configured base
station
7652 BASE STATION == NOTIFICATION
actCategoryAlarms
7654
7115 CELL
BASE OPERATION
STATION DEGRADED (The
true)
INFORMATION (TILTfault source
failure
is
-affects an uncommissioned
when fault affects unit.)
basic services of the
antenna carrier of a cell within the same BTS.) base station
7113
7652 BASE STATION ANTENNA NOTIFICATION LINE (NoPROBLEM
impact on
If
-cells category
when fault alarms
does disabled
not affect (actCategoryAlarms
basic services of the ==
base
within the same BTS. For
false) example, TILT serves for
station
antennas
actCategoryAlarms used by different
== true) BTS/RAT; uncommissioned
7654
7115 CELL OPERATION DEGRADED (TILT failure
source)
-affects whenBASE
antenna
STATION
fault affectscarrier
INFORMATION
basicof services
a cell within of the
thebase
samestation
BTS.)
7113
impact on
If
-If category
when faultalarms
does disabled
not (actCategoryAlarms
affectFor
basic services of the ==
basefor
cells
false) within
category the same
alarms BTS.
enabled example,
(customer TILT
configuredserves
station
antennas
actCategoryAlarms used by different
== true) BTS/RAT; uncommissioned
7654
7115 CELL
BASE OPERATION
STATION DEGRADED
INFORMATION (TILT failure
source)
-affects when antenna
fault affects basic
carrier of services
a cell within of the
thebase
samestation
BTS.)
7113
impact on
If
-cells category
when faultalarms
does disabled
not (actCategoryAlarms
affectFor
basic servicesTILT
of the ==
basefor
false) within the same BTS. example, serves
station
antennas used by differentDEGRADED
BTS/RAT; uncommissioned
7654
7115 CELL
BASE OPERATION
STATION INFORMATION (TILT failure
source)
affects antenna carrier of a cell within the same BTS.)
If
7652 category
BASEalarmsSTATION enabled (customer configured
NOTIFICATION (No impact
If category
==BTS. (actCategoryAlarms
true)For ==on
cells
false) within the same example, TILT serves for
-antennas
when fault usedaffects
by basic services
different BTS/RAT; of the base station
uncommissioned
7654
7113 CELL
BASE OPERATION
STATION ANTENNA DEGRADED LINE (TILT failure
PROBLEM
source)
affects antenna carrier of a cell within the same
If category
-If when faultalarms
category does not
alarms
areaffect
enabled
enabled basic (customer
(customer services of theBTS.)
configured
configured base
7652 BASE
actCategoryAlarms
station STATION NOTIFICATION
== true) (No impact on
actCategoryAlarms
cells
7111 within
BASEthe same==BTS.
STATION true)For example,
SOFTWARE TILT serves for
MANAGEMENT
7115
-PROBLEM
when fault affects INFORMATION
antennas used by different BTS/RAT; uncommissioned
7113
source) BASE STATION ANTENNA LINE PROBLEM
If category
does notdisabled (actCategoryAlarms
services of the==
category
false) alarms areaffect basic
disabled (actCategoryAlarms base==
station
false)
7652
7115 BASE
BASE STATION
INFORMATION (ALD which is
7650
serving BASE STATION
for different BTS;FAULTY (FTM/FCT (HW
uncommissioned source)rel.3),
FCT
7654 (HW rel.4))
CELLalarmsOPERATION DEGRADED (TILT, MHA)
If category
7653 CELL FAULTY disabled
(FR or(actCategoryAlarms
FHS [The cell cannot ==
false)
operate because there are not enough available and
7652
needed BASE STATION
resources: Tx orNOTIFICATION
Rx.]) (ALD which is
serving
7654 CELL OPERATION DEGRADED (FR source.)
for different BTS; uncommissioned or FHS [The
7654
cell canCELLstill OPERATION
operate because DEGRADED
it still has (MHA,
enoughTILT)
available and needed resources: both Tx and Rx.])
Please note that in case
actCategoryAlarms of FHS, the cell is specified as
== true)
the one behind the FHS.
7108 BASE STATION SYNCHRONIZATION PROBLEM
actCategoryAlarms
If category == true)(actCategoryAlarms ==
alarms disabled
If category
-false)
when faultalarms
affectsare enabled
basic (customer
services configured
of the base station
actCategoryAlarms
7113 == true):
BASE STATION ANTENNA LINE PROBLEM
7650
7114 FAULTY
- whenCELL
fault SERVICE PROBLEM
does not affect basic services of the base
station
If category
7115 BASEalarms
STATIONare disabled (actCategoryAlarms ==
INFORMATION
false):
7653 CELLalarms
If category FAULTY disabled (actCategoryAlarms ==
false)
7652 BASE STATION NOTIFICATION (ALD which is
serving for different BTS, uncommissioned resource)
7654 CELL OPERATION DEGRADED (otherwise)
- when fault does not affect basic services of the base
station
7115
7115 BASE
BASE STATION
STATION INFORMATION
INFORMATIONIf category alarms
enabled (customer configured actCategoryAlarms ==
If
true) category alarms disabled (actCategoryAlarms ==
false)
7652 BASE STATION NOTIFICATION (ALD which is
7115
serving BASE STATION
for different INFORMATIONIf
BTS, uncommissioned category
resource) alarms
If
enabled category alarms disabled
(customer configured (actCategoryAlarms
actCategoryAlarms ====
7654
false) CELL OPERATION DEGRADED (otherwise)
true)
7652
INFORMATION (ALD is working
for different BTS)
7115
7655 BASE
CELLalarmsSTATION INFORMATIONIf
NOTIFICATION (Flexi Filter, category
AISG MHA, alarms
If
enabled category (customerdisabled
configured (actCategoryAlarms
RET)
false)
true)
7652
for different BTS)
7115
7655 BASE
CELLalarmsSTATION INFORMATIONIf
NOTIFICATION (Flexi Filter, category
AISG MHA, alarms
If
enabled category (customerdisabled
configured (actCategoryAlarms
RET)
false)
true)
7652
7115 BASE
BASE STATION
actCategoryAlarms
for different BTS) == true)
If
-7655 category
when faultalarms
CELL affectsare
NOTIFICATION enabled
basic services(customer
(Flexi of the base
Filter, configured
AISG station
MHA,
If category
actCategoryAlarms
7113 BASEalarmsSTATION disabled
true)(actCategoryAlarms
== ANTENNA LINE PROBLEM ==
RET)
false)
- when fault affects basic services of the base
does not affect basic services of the base station
7652
stationBASE
7108 BASE STATION
SYNCHRONIZATION (ALD is working
PROBLEM
for
If
-7115 different
category
whenBASE BTS)
alarms
fault does
STATION are enabled
not affect (customer configured
INFORMATION
7655
stationCELL NOTIFICATION
actCategoryAlarms == true): (Flexi Filter, AISG MHA,
RET)
-7115
If When BASE
categoryfaultalarms
affectsdisabled
INFORMATION of the base station:
7116
false) BASE STATION SERVICE PROBLEM
-AirScale
If When
7652 BASE
categoryfault
BTS does
FDD,not
STATION
alarms are affect
AirScale basic
BTS
NOTIFICATION
enabled services
TDD,
(customer of the
AirScale
(RAE, base
SBTS,
external
configured
station:
Flexi
ALD; BTS FDD, Flexi
uncommissioned
actCategoryAlarms ==BTS TDD, Flexi SBTS:
source)
true)
7115
-If
7654 whenBASE
category
CELL
fault STATION
alarms are
OPERATION
affects INFORMATION
disabled
basic DEGRADED
services(customer
of the configured
(otherwise)
base station
If category
-actCategoryAlarms
When alarms enabled
autonomous recovery(customer
reset is configured
being performed
7111 BASE
actCategoryAlarms STATION ==
== false)
SOFTWARE
true) MANAGEMENT
due
7652 to the fault:
PROBLEM
fault affects
BASE
NOTIFICATION
basic
STATION/UNIT services of the(ifbase
AUTONOMOUS
otherstation
valid
RESET
reference
-7108 whenBASE source
fault does is
STATION available)
not affect basic services of the
SYNCHRONIZATION base
PROBLEM
NOTIFICATION
7651
- whenBASE
station STATION
fault does OPERATION
not affect DEGRADED
basic services (other
of the base
cases)
7115
station BASE STATION INFORMATION
Flexi
-7115 whenBTS FDD, Flexirecovery
autonomous BTS TDD, AirScale
reset is being BTS TDD,
performed
AirScale BASE BTS STATION
FDD, INFORMATION
TDD:
due to the fault
If
7650
7101 category
BASEalarms
BASE STATION are disabled
STATION/UNIT FAULTY (actCategoryAlarms
(Holdover is not
AUTONOMOUS RESET ==
If
false):category alarms disabled (actCategoryAlarms ==
possible)
NOTIFICATION
false)
7652
If BASEalarms
category STATION NOTIFICATION
7652 BASE STATION
(Uncommissioned NOTIFICATION
source) (if other clock is
actCategoryAlarms
AirScale
available) BTS FDD, == true) BTS TDD, AirScale SBTS,
AirScale
If
-7653 category
whenCELL
faultalarms
FAULTY
affects enabled
basic (customer
(Theservices
cell cannot configured
operate
base because
of DEGRADED
the station it
Flexi
7651 BTS
BASE
actCategoryAlarmsFDD, Flexi
STATION ==BTStrue)TDD, Flexi
OPERATION SBTS: (other
does
7116
If not
BASE
category have enough
STATION
alarms are available
SERVICE
disabled and needed
PROBLEM
(actCategoryAlarms resources:
==
case)
-Tx
- when
false)
fault
fault affects
or Rx.)
when does not basic services
affect of the base
basic services station
of the base
7111
7654 BASE
CELL STATION SOFTWARE MANAGEMENT
station
7652
PROBLEM BASE OPERATION DEGRADED
STATION NOTIFICATION (The cell can still
operate
7115 because
BASE STATION
(Uncommissioned it has INFORMATION and needed
source)enough available
--resources:
when
when fault doesTxnot
both
autonomous andaffect
Rx.)
recovery basic services ofperformed
the base
7653
stationCELL FAULTY (The cellreset
cannotis being
operate because it
7655
due
does CELL
tonot
thehave NOTIFICATION (The cell is not
faultenough available and needed resources: impacted.)
7115
Tx or BASE
Rx.) STATION/UNIT AUTONOMOUS RESET
NOTIFICATION
AirScale BTS FDD, AirScale BTS TDD,(The cell can
AirScale still
SBTS,
operate
Flexi because
BTS FDD, it has enough
Flexi BTS TDD, available
Flexi SBTS: and needed
If category
resources: alarms
both Txdisabled
and Rx.)(actCategoryAlarms ==
If category
false) alarms disabled (actCategoryAlarms ==
false)
7652 BASE STATION
source)
(Uncommissioned source)
7653 CELL FAULTY (The cell cannot operate because
7654
there CELL
are notOPERATION
enough availableDEGRADEDand needed (Otherwise)
resources:
Tx or Rx.)
7654 CELL OPERATION DEGRADED (The cell can still
operate because it has enough available and needed
resources: both Tx and Rx.)
SBTS:
- When autonomous recovery reset is being performed
If
If
due category
category alarms
alarms disabled
to the fault: are enabled (actCategoryAlarms
false)
actCategoryAlarms
7101 BASE STATION/UNIT AUTONOMOUS RESET == true)
-7653
NOTIFICATION whenCELLfault FAULTY
affects basic(Theservices
cell cannot operate
of the base because
station
there
7116 are notSTATION
BASE enough available
SERVICE and needed resources:
PROBLEM
If
Tx category
or Rx.) alarms are enabled (customer configured
-If
actCategoryAlarms when
categoryfaultalarms
does not ==affect
disabledtrue) basic services of the==
(actCategoryAlarms base
7654
station
false): CELL OPERATION DEGRADED (The cell can still
-If
operate when
categoryfault affects
because
alarms basic
there
are areservices
enabled enough ofavailable
the base
(customer station
and
configured
7115
7653
7116 BASE
CELL
BASE STATION
FAULTY
STATION INFORMATION
(The cell
SERVICE cannot operate
PROBLEM because
-needed
actCategoryAlarms
-of when resources:
autonomous
insufficient
when fault available
does
both
== true)
notrecovery
Tx and
and
affect needed
basic
Rx.)isresources:
reset being performed
Txbase
or
7652
-due
Rx.) whentoBASE STATION
autonomous
the fault NOTIFICATION
recovery resetservices
is beingofperformed
the
station
If
(Uncommissioned
due category
toBASE alarms
the fault enabled (customer
source)DEGRADED configured
7101
7654
7115 CELL
BASE STATION/UNIT
OPERATION
STATION AUTONOMOUS
INFORMATION RESET
(The cell can still
actCategoryAlarms
7101
NOTIFICATION BASE ==
STATION/UNIT true) AUTONOMOUS RESET
operate
-NOTIFICATION
7116 whenBASE because
autonomous
STATIONit still has
recovery
SERVICE enough
reset available and
is being performed
PROBLEM
needed
If
due category
to resources:
the alarms are
fault both Tx and(customer
enabled Rx.) configured
-actCategoryAlarms
If
7652 when
categoryfaultalarms
BASE does
STATION not
are
== affect
disabled basic
NOTIFICATION
true) services of the base
7101
If
station BASE STATION/UNIT AUTONOMOUS
category alarms disabled (actCategoryAlarms RESET
==
false)
(Uncommissioned
-NOTIFICATION source)
false)
7115
7116 BASE
7652
7654
STATION
STATION INFORMATION
BASE OPERATION
CELL
NOTIFICATION
SERVICE
DEGRADED PROBLEM
--(Uncommissioned when
when fault
fault affects
does basic
source)
not affectservices
basic of the- dedicated
services base
ofLTE
the
radio
station
base
AirScale
resources
7116 BASEBTS
or FDD,
shared
STATION(TheAirScale
radio BTS
resources,
SERVICE TDD, AirScale
where
PROBLEM SBTS,
is
7653
station
Flexi CELLFDD,
BTS FAULTY
Flexi BTS cell cannot operate because it
master
If
does categorySM;
not have theenough
alarmscell can
are stillTDD,
enabled
available
Flexibecause
operate
(customer
and
SBTS:
needed the cell
configured
resources:
7115
If
has BASEalarms
category STATION INFORMATION
disabledtrue)(actCategoryAlarms ==
actCategoryAlarms
If
Tx
-false) orenough
category
when Rx.) available
alarms
autonomous
==required
disabled
recovery
Tx resources.
(actCategoryAlarms
reset is being ==
performed
-false)
7654 whenCELLfault OPERATION
affects basic services
DEGRADED of the(The
basecell
station
can still
due
7652
7116 toBASE
the fault
BASE STATION
SERVICE PROBLEM
-If
operate
7101 when
categoryautonomous
because
BASE alarms itare
STATION/UNITrecovery
still has
enabled reset
enough is being
available
(customer
AUTONOMOUS executed
and
configured
RESET
(Uncommissioned
-due when fault
to the does not
fault source)
affect basicRx.)
needed
actCategoryAlarms
NOTIFICATION
7653 resources:
CELL FAULTY both
==(The Txcell
true) and cannot operate because it
station
7652
7655
-does when BASE
CELL
fault STATION
NOTIFICATION
affects basicNOTIFICATION
(The
services cell is not
of the impacted.)
base station
7115
-Flexi when not
BASEhave enough
STATION
autonomous available
INFORMATION
recovery and
reset is needed
not resources:
being
All
Tx products:
or BTS
Rx.) FDD,7116FlexiBASEBTS STATION
TDD, SERVICE
AirScale BTS TDD,
-PROBLEM
executed when autonomous
due FDD, recovery
to theFlexi
fault SBTS, reset is being performed
AirScale
7654
due CELL
toCELL
theBTS OPERATION
fault DEGRADED AirScale SBTS:
(The cell can stillit
7653
-If when
categoryfault FAULTY
does itnot
alarms are (The
affect cell
disabled cannot
basic operate
services because
of the
(actCategoryAlarms base
operate
7101
does
station
because
BASE
not have has
STATION/UNIT enough
enough available available
AUTONOMOUS and RESET==
needed
and needed resources:
false)
resources:
NOTIFICATION
Tx
All
7652 Rx.) both
or BASE
products:
Tx and Rx.)
7115 BASE
STATION STATION INFORMATION
NOTIFICATION
-7654 whenCELL
(Uncommissioned OPERATION
autonomous recovery
source) DEGRADED (Theperformed
reset is being cell can still
Flexi
operate
due toBTS FDD,
because
the fault Flexi
it has BTS TDD,available
enough AirScale andBTSneeded
TDD,
7653
AirScale CELLBTS FAULTY
FDD, (TheSBTS,
Flexi cell cannot operate
AirScale SBTS: because it
resources:
All
does products:
not haveboth
7101Tx
enough and
BASE Rx.)
STATION/UNIT
available and needed resources:
If
7655
AUTONOMOUScategory
CELL alarms are disabled
NOTIFICATION
RESET (The(actCategoryAlarms
NOTIFICATION cell is not impacted.) ==
Tx
false) or Rx.)
7654
7652 CELL OPERATION
BASEalarms
STATION DEGRADED (The cell can still
NOTIFICATION
If
operate category because itare
has disabled
enough (actCategoryAlarms
available and needed ==
(Uncommissioned
false) source)
resources:
7653 CELLFDD,both Tx and
FAULTY Rx.) cannot operate because it
Flexi
7655 BTS
CELL Flexi (The
NOTIFICATION BTS cellTDD,(TheAirScale
cellneeded BTS
is not FDD,
impacted.)
does
AirScale not BTS
haveTDD: enough available and resources:
If category
Tx Rx.) alarms
or BASE enabled (customer configured
7652
If category
actCategoryAlarms STATION
alarms == NOTIFICATION
enabled true) (customer configured
7654
(Uncommissioned CELL OPERATION source) DEGRADED (The cell can still
actCategoryAlarms
-operate when fault affects
because it ==
basic
has true)
services
enough of the base
available station
and needed
7653
-7116 when CELL
fault
BASE FAULTY
affects
STATION (The
basic cell cannot
services
SERVICE of operate
the
PROBLEM base because
station it
resources:
does not havebothenough
Tx andavailable
Rx.) and needed resources:
7116
-If when BASE STATION
faultalarms
does not SERVICE
affect basic PROBLEM
-Tx category
or Rx.)
when fault does not enabled
affect (customer
basic servicesconfigured
of the base
station
7654
station
7115 CELL
BASE OPERATION
STATION DEGRADED
INFORMATION (The cell can still
-operate
when fault affects
because it
7115 BASE STATION INFORMATION basic
has services
enough of the
available base
and station
needed
7116
resources: BASEboth STATION
Tx and SERVICE
Rx.) PROBLEM
If category
does not disabled
category
station
false)
7652
If
7115 BASE
category
BASE STATION
alarms NOTIFICATION
7652 BASE STATION
(Uncommissioned
actCategoryAlarms STATION INFORMATION
== NOTIFICATION
source)true)
(Uncommissioned
7654
-If when CELL OPERATION
faultalarms source)
affectsdisabled DEGRADED
basic services of the(Otherwise)
base station
category
7653 CELL (actCategoryAlarms ==
7100
false) BASE STATION HARDWARE cannot
FAULTY (When the cell PROBLEM operate
because
-7652
whenBASE it does
fault does not
nothave
affect enough availableofand
basic services theneeded
base
resources: STATION
Tx or Rx.) NOTIFICATION
station
7654
7115 CELL
BASE OPERATION
STATION INFORMATION DEGRADED (When the cell
7654 CELL
can still OPERATION
operate though in DEGRADED
a degraded state (Otherwise)
as it has
enough
AirScaleavailable
BTS FDD, and neededBTS
AirScale resources: both TxSBTS,
TDD, AirScale and
Rx.)
7655 CELLalarms
If category NOTIFICATION (Condition
are disabled detected but ==
(actCategoryAlarms cell
still
false)fully operational.)
7654 CELL OPERATION DEGRADED (Otherwise)
7653 CELL FAULTY
7101
stationBASE STATION/UNIT AUTONOMOUS RESET
NOTIFICATION
AirScale
due to theBTS
faultFDD, AirScale BTS TDD, AirScale SBTS,
AirScale
Flexi BTS BTS
FDD, FDD,
FlexiAirScale
BTS TDD, BTSFlexi
TDD, AirScale SBTS,
SBTS:
7101
Flexi BASE
BTS STATION/UNIT
FDD, Flexi BTS AUTONOMOUS
TDD, Flexi SBTS: RESET
NOTIFICATION
If
false) category alarms are disabled (actCategoryAlarms ==
false)
7652 BASE
AirScale
7652 BASEBTSSTATION
STATION
NOTIFICATION
FDD, AirScale BTS TDD, AirScale SBTS,
NOTIFICATION
(Uncommissioned
Flexi BTS FDD, Flexi source)
(Uncommissioned
7653 CELLalarms
FAULTY source)
If
7654 category
CELL are(During
OPERATION disabled RF(actCategoryAlarms
DEGRADED
start-up if the cell ==
(Otherwise)
cannot
false) operate because it does not have enough
If categoryand
available alarms enabled
needed (customer
resources: Tx configured
or Rx)
7652 BASE STATION
true)
7654 CELL OPERATION
(Uncommissioned source) DEGRADED (During RF start-
-If
up category
when
if thefaultalarms
cell affects
can are
still enabled
basic
operateservices(customer
of the configured
base station
7653 CELL
actCategoryAlarms
7116 BASE FAULTY
STATION ==(Thetrue)cellbecause
SERVICE cannot it has
operate
PROBLEM
enough
because
available
If category and needed
alarms resources:
enabled both
(customer Tx and
configured Rx)
-therewhen are not
fault enough
affects
does not available
basic
affectservicesand
basic ofneeded
the
services ofresources:
base station:
the base
actCategoryAlarms
Tx
7102 or Rx.)
BASE STATION == true)
RESOURCE BLOCK BY USER
station
-7654whenCELLfault OPERATION
affects basic services of the(The
basecellstation
7115 BASE STATION DEGRADED
INFORMATION can still
7111
operate BASE STATION
because it still SOFTWARE
has enough MANAGEMENT
available
- when fault does not affect basic services of the base and
PROBLEM
needed
station: resources:disabled
both Tx and Rx.)
If category
-7115
when faultalarms
does not affect (actCategoryAlarms
false) BASE STATION INFORMATION
station
7652
7115 BASEBASE STATION
INFORMATION
If category
7654 CELLalarms are disabled
OPERATION (actCategoryAlarms ==
If category
false) alarms disabledDEGRADED (Otherwise)
false)
7652 BASE STATION
source)
7653 CELL FAULTY (the cell cannot operate because
7654
there CELL OPERATION
is not enough availableDEGRADED
and needed (Otherwise)
resources: Tx
or Rx)
7654 CELLalarms
If category OPERATION
enabledDEGRADED (the cell can still
operate because it still
actCategoryAlarms == true): has enough available and
needed resources: both
7115 BASE STATION INFORMATION Tx and Rx)
If
If category
category alarms
alarms disabled
are enabled (actCategoryAlarms ==
false):
7652
7115 BASE STATION
BASEalarms
INFORMATION
If category are enabled (customer configured
If category
category affectsare
alarms disabled
basic
services
(customerof the base station==
configured
false):
7116 BASEalarms
STATION
actCategoryAlarms SERVICE
==enabled
true) PROBLEM
If category are (customer configured
-7652
7115whenBASE
fault
BASE STATION
does not
STATION
NOTIFICATION
affect basic
INFORMATION services of the base
station
7115
If BASE STATION INFORMATION
If category
7116 BASEalarms
category STATION
SERVICE
enabled configured==
PROBLEM
(customer
false)
-actCategoryAlarms
when fault does not ==affect
true):basic services of the base
If category
7652
stationBASE alarms
STATIONare disabled (actCategoryAlarms ==
NOTIFICATION
7115
(Uncommissioned source) (actCategoryAlarms ==
false): disabled (actCategoryAlarms ==
7653
false) CELL FAULTY (The cell cannot operate because it
7652
does BASE
not STATION
have enough NOTIFICATION
Tx or Rx.)
7654
7653 CELL
CELL OPERATION
FAULTY (TheDEGRADED (The cell
cell cannot operate can still
because
operate because it has enough available and
there are not enough available and needed resources: needed
resources:
Tx or Rx.) both Tx and Rx.)
7654 CELL OPERATION DEGRADED (The cell can
operate because
If category alarmsitenabled
still has (customer
enough available and
configured
needed resources: both
actCategoryAlarms == true): Tx and Rx.)
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION (The cell is not impacted.)

false):
station
actCategoryAlarms
If category alarms disabled == true)(actCategoryAlarms ==
If
-false) category
when alarms enabled
autonomous recovery (customer configured
reset is being performed
actCategoryAlarms
due toBASE
the fault == true)
true):
7652
fault affects basicNOTIFICATION
services of the basefaulty
(The SFP
station:
7101
works BASE
on STATION
STATION/UNIT
optical interface INFORMATION
thatAUTONOMOUS
is not used to RESET
provide
7116
NOTIFICATION BASE STATION SERVICE PROBLEM
transmission
--If when fault for any cell.)
does
7653 category
when CELL does not
faultalarms
FAULTY not affect
disabled
affectcell
(The
basic
basic services
(actCategoryAlarms
services
cannot
of
of the
operate the base
==
base it
because
station:
false):
station
does
7115 not have enough available
INFORMATION
7652
7115
and BASE
needed STATION
BASEalarms
STATION
resources: NOTIFICATION
INFORMATION
Tx or Rx.)
If category enabled (customer configured
-7654
actCategoryAlarms when fault
CELL affect basic
OPERATION services
DEGRADED of the (The
== true)(actCategoryAlarms base cell
station
can still
If
7116 category
BASE alarms
STATION disabled
SERVICE PROBLEM ==
operate
-false) because it still has
enough
7113
7652 available
BASE STATIONand needed
ANTENNA
NOTIFICATIONresources: both Tx and
LINE PROBLEM
If
Rx.)
-(Uncommissioned category
when faultalarms
does notdisabled
false) source)
station
7654 CELL OPERATION DEGRADED (Otherwise)
7652
7115 BASE
BASE STATION
INFORMATION
7655
(Uncommissioned CELL NOTIFICATIONsource) (commissioned FR, [The
cell
7653 can operate;
CELLalarms
FAULTYall needed
(The cell resources available:
cannot operate both Txit
because
If
and category
Rx.]) disabled (actCategoryAlarms ==
does
false)not have enough available and needed resources:
Tx
7652 or BASE
Rx.) STATION NOTIFICATION
7654
(Uncommissioned CELL OPERATIONsource)DEGRADED (The cell can still
operate
If
7653 CELL FAULTY because
category alarms it still
are hascell
enabled
(The enough available
(customer
cannot and
configured
operate because it
needed
actCategoryAlarms
does resources:
not have enough both Tx
== availableand
true)(customerRx.)
If category alarms enabled configured
-Tx when
actCategoryAlarms fault affects basic
or Rx.) == true) services of the base station
7116
7654
-If when BASE
CELL STATION
OPERATION
faultalarms
affectsenabled SERVICE
DEGRADED
basic services PROBLEM
of the(The
basecell can still
station
-operate category
when fault does not affect (customer
basic configured
services
7100
actCategoryAlarms because
BASE STATION it has enough
== HARDWARE
true) PROBLEM base
available of
and the
needed
station
-resources: when faultboth
does Txnotand Rx.)basic services of the base
affect
7115
If
7115 BASE
category STATION
BASEalarms
STATION enabledINFORMATION
INFORMATION
station
7115
If
-If when BASE
category STATION
faultalarms
affects INFORMATION
disabled
basic (actCategoryAlarms
services == ==
of the base station
category alarms are disabled (actCategoryAlarms
false)
7116
false) BASEalarms
If category enabled
disabled (customer configured
(actCategoryAlarms
7652
-7652 when BASE
fault
BASE
actCategoryAlarms
STATION
does
STATIONnot==
NOTIFICATION
affect basic
NOTIFICATION
true) services of the== base
false)
If
station category alarms source)
(uncommissioned
-7652 whenBASE
fault affects
STATION basic services of the base station
actCategoryAlarms
7115
7654 BASE STATION
CELL OPERATION == NOTIFICATION
true)
INFORMATION
DEGRADED (if not CPRI-A
7116 when fault affects basic servicesPROBLEM
(uncommissioned
-radio) BASE STATION source)SERVICE of the base station
-7100
7653 when fault does
CELLalarms
BASE FAULTY
STATIONnot affect
(The basic
cell
HARDWARE services
cannot of the
operate
PROBLEM base it
because
If
7655
station category
CELL disabled
NOTIFICATION (actCategoryAlarms
(if CPRI-A radio) ==
-does
false) when not have
fault enough
does available
not affect basicand needed
services resources:
of the base
7115
Tx
station or BASE
Rx.) STATION INFORMATION
7654
7115 CELL
BASE OPERATION
(uncommissioned STATION source) DEGRADED (The cell can still
INFORMATION
If
operate category alarms
because itenabled
disabled
has (customer
enough configured
(actCategoryAlarms
available and ==
needed
-7653 whenCELL
autonomous
actCategoryAlarms FAULTY== recovery
(Thetrue)cellreset
cannotis being
operateperformed
because it
false)
resources:
due tonot
the bothenough
fault Tx andavailable
Rx.)
does
-7652 when BASEhave
fault affects
NOTIFICATION and needed
of the baseresources:
station
7101
Tx
7100 or BASE
Rx.)
BASE STATION/UNIT
STATION HARDWARE AUTONOMOUS PROBLEM RESET
(uncommissioned
NOTIFICATION source)
7654
-7653whenCELL
fault OPERATION
CELL does not (The
FAULTY affectDEGRADED
basic
cell (The
services
cannot of cell
operate the can
basestillit
because
operate
station
does because
not have it
enoughhas enough
available available and needed
If category
resources:
7115 BASE alarms
both Txdisabled
STATION Rx.)(actCategoryAlarms ==
andINFORMATION
Tx
false)or Rx.)
7654
If
7652 CELL
category OPERATION
BASEalarms
STATION enabled DEGRADED (The cell can still
NOTIFICATION
If category
operate alarms
because it
actCategoryAlarmssource) disabled
has
(uncommissioned
false)
-enough
whenCELL
7653 available
fault affects
FAULTY and needed
basic
(The cell resources:
services of the
cannot both because
base
operate Tx and it
station
7652
Rx.)
7116 BASE
BASE STATION
SERVICE PROBLEM(The faulty SFP
does
works not
on have enough
optical interface available
that is and
not needed
used to resources:
provide
-Txwhen fault does not affect basic services of the base
or Rx.)
transmission
station for any cell.)
7654
7653 CELL
CELL OPERATION
FAULTY (The DEGRADED (The cell
cell cannot operate can stillit
because
7115
operateBASE STATION
because it has INFORMATION
enough available and needed
does not have enough available
resources:
and neededboth Tx and Rx.)
resources: Tx or Rx.)
7654
false) CELL OPERATION DEGRADED (The cell can still
operate
7652 BASE because it still NOTIFICATION
STATION has (The faulty
enough
optical interface is not used to resources:
available and needed both Tx and
provide transmission for
Rx.)
any cell.)
operate because it still has
enough available and needed resources: both Tx and
Rx.)
If
false) category alarms enabled (customer configured
station
true)
7652
7115 BASE STATION (The faulty
-optical whenBASEfault STATION
affects basic
interface is not used
INFORMATION
services of the
to provide base stationfor
transmission
7112
any BASE STATION CONFIGURATION
cell.) alarms disabled (actCategoryAlarms PROBLEM
If
-7653 category
when fault does not affect basic services of the ==
base it
CELL FAULTY (The cell
false) cannot operate because
station
does not
actCategoryAlarms have enough available
== NOTIFICATION
true)
7652
7115 BASE
BASE STATION
STATION INFORMATION (The faulty
and
-optical needed
when resources:
fault affects
interface is notbasic Txservices
used ortoRx.) of the
provide base stationfor
transmission
7654
7116
any CELL OPERATION
BASE
cell.) STATION SERVICE DEGRADED PROBLEM (The cell can still
If
-operate category
when alarms
because
fault disabled
does itnotstill (actCategoryAlarms
hascell
affect basic services of the ==
base it
7653
false) CELL FAULTY (The cannot operate because
enough
station
does not available
have and
enough needed
available resources: both Tx and
7652
Rx.)
7115 BASE STATION
BASE STATION NOTIFICATION
INFORMATION (The faulty SFP
and
works needed resources:
on optical interface Txthat
or Rx.)
is not used to provide
7654
transmission CELL OPERATION
for any cell.) DEGRADED (The cell can still
If
operate category alarms
because itdisabled
still has (actCategoryAlarms ==
7653
false) CELL FAULTY (The cell cannot operate because it
enough
does not available
have and needed
enough available resources: both Tx and
If
7652
Rx.) category
BASE alarms
STATION enabled (customer configured
NOTIFICATION (The faulty
and
optical needed
actCategoryAlarms resources:
interface is not==used Tx ortoRx.)
true) provide transmission for
7654
-any when CELL
fault OPERATION
cell.) DEGRADED
affects basic services of the(The
basecell can still
station
operate
7116
7653 BASE because it still
STATION(The
CELL FAULTY has
SERVICE PROBLEM
cell cannot operate because it
enough
-does when not available
fault
havedoes and
not
enough needed
affect resources:
basic
available services both
of theTxbase
and
If
Rx.) category alarms enabled (customer configured
station
and neededalarms
actCategoryAlarms resources: Tx or
== true) Rx.)
If
7115 category
BASE STATION enabled (customer
INFORMATION configured
7654 CELL
-actCategoryAlarms OPERATION
when fault affects basic == true) services of the(The
DEGRADED basecell can still
station
operate
7116
7115 BASEbecause
STATIONit still has
SERVICE
INFORMATION PROBLEM
If
enough
- whencategory alarms
available
fault does and disabled
not needed
resources:
basic servicesboth
of theTx==and
base
false)
Rx.)
station
If
7652 category
BASE alarms disabled (actCategoryAlarms ==
7115
false) BASE STATION
INFORMATION (The faulty
optical interface is not used to provide transmission for
7652
any BASE STATION NOTIFICATION
cell.)
If category
(uncommissioned alarms source)
disabled (actCategoryAlarms ==
7653
false) CELL FAULTY (The cell cannot operate because
7655
not it CELLnot
does NOTIFICATION
have enough (commissioned
available and source)
needed
7652 BASE STATION NOTIFICATION (The faulty
resources:
optical interface Tx or isRx.)not used to provide transmission for
7654
any cell.) CELL OPERATION DEGRADED (The cell can still
operate
7653 CELL because
FAULTY still (The
has enough available
cell cannot operateandbecause
needed it
resources:
If category both
alarmsTx and
are Rx.)
enabled (customer
does not have enough available and needed resources: configured
actCategoryAlarms
Tx or Rx.) == true)
-If
7654 when
categoryfault affects
alarms
CELLalarms
OPERATION basic
enabled services
(customer
DEGRADED of the basecell
configured
(The station:
can still
If
7116 category
BASE
actCategoryAlarms STATION enabled
== (customer
SERVICE
true) configured
PROBLEM
operate because it still has enough available and
-actCategoryAlarms
when fault
needed does
affectsnot
resources:
==affect
basic
both
true) basicRx.)
services
Tx and services of the
of the base base
station
7116
station: BASE STATION
7116 BASE STATION SERVICE PROBLEM SERVICE PROBLEM
7115
- whenBASE STATION
autonomous INFORMATION
If
-duecategory
when alarms disabled
autonomous
to the fault recovery (actCategoryAlarms
reset is being performed==
false)
due
7101toBASEthe fault:
7650
7101 BASE STATION/UNIT
BASE
NOTIFICATION STATION FAULTY AUTONOMOUS RESET
NOTIFICATION
actCategoryAlarms
If == true):(actCategoryAlarms ==
If category
category
When
alarms disabled
fault alarms
affects enabled (customer
of the base station:
false)
7116
If BASE
category
7650 STATION
BASEalarms
STATION SERVICE
are disabled
FAULTY PROBLEM
7116
false) BASE
When STATION
fault does not affectSERVICE PROBLEM
station:
If category
7115 BASEalarms
(Uncommissioned STATION disabled (actCategoryAlarms ==
INFORMATION
source)
false)
When
7653 CELL FAULTY (The cellreset
autonomous recovery is being
cannot performed
operate because
7653
due
of to
not CELL
the
enough FAULTY
fault:
available and needed resources: Tx or
If category
7101 BASEalarms enabled (customer
STATION/UNIT AUTONOMOUS configured RESET
Rx.)
NOTIFICATION
7654
7115 CELL
BASE OPERATION
STATION INFORMATION DEGRADED (The cell can still
If category
needed alarms disabled
resources: both Tx and (actCategoryAlarms
Rx.) ==
If category
false): alarms disabled (actCategoryAlarms ==
false)
7652 BASE STATION
source)
7653 CELL FAULTY (The cell cannot operate because it
7655
does notCELL haveNOTIFICATION
enough available (Theand
cellneeded
is not impacted.)
resources:
Tx or Rx.)
actCategoryAlarms
If category == true)(customer configured
alarms enabled
If category
-actCategoryAlarms
when faultalarms
affectsenabled
disabled
basic (customer configured
(actCategoryAlarms
services of the ==
base station
== true)
true)
false):
7116
-- when BASE
fault STATION
affects basic SERVICE
services PROBLEM
of
-7652 when fault
fault affects
whenBASE STATION
does notbasic services
NOTIFICATION
affect of the
the base
basic PROBLEM
services base station
station
of the base
7116
7112 BASE
BASE STATION
STATION SERVICE
CONFIGURATION PROBLEM
(Uncommissioned
station
-- when fault does source)
7653
7115 whenCELL
fault FAULTY
BASE does
STATIONnot (The
affect basic
cell services
cannot
INFORMATION of the
operate base it
because
station
station
does
-7115 not
whenBASEhave enough
autonomous
STATION available and needed resources:
7115
Tx ortoBASE
due Rx.) STATION INFORMATION
the fault INFORMATION
7654
7101
If CELLalarms
BASE
category OPERATION
STATION/UNIT DEGRADED
AUTONOMOUS (The cell can still
RESET
If
operate category
NOTIFICATION alarmsitdisabled
because disabled
has enough
(actCategoryAlarms
==
available and needed
false)
false)
resources:
-7652 whenBASE both
autonomousTx and
STATION Rx.) reset is not being
recovery
NOTIFICATION
7652
performed BASE STATION
due to the NOTIFICATION
fault (The faulty
(Uncommissioned
optical interface is source)
not used to provide transmission for
7114
any cell.) OPERATION DEGRADED (The cell can still
operate
7653 because
CELL FAULTYit has(The enough
cell available
cannot and needed
operate because it
If category
resources: alarms
both Tx disabled
and Rx.)(actCategoryAlarms ==
does
false) not have enough available and needed resources:
Tx
7652 or BASE
Rx.) STATION NOTIFICATION
7654 CELL
(Uncommissioned OPERATIONsource)DEGRADED (The cell can still
operate
If
7653 because
category
CELLalarms
FAULTYit has
enabled
(The enough available
(customer
cell cannot and needed
configured
operate because it
resources:
actCategoryAlarms
does not have enoughboth Tx and Rx.)
== available
true) and needed resources:
-Tx when autonomous recovery reset is being performed
or Rx.)
due
7654 toCELLfault
the OPERATION
If
7101 category
BASEalarms enabledDEGRADED
STATION/UNIT (customer
AUTONOMOUS
(The cell can
configuredRESET
still
If operate
category
alarms it
enabled has
== true) enough
(customeravailable and
configured
NOTIFICATION
needed resources:
actCategoryAlarms both Tx
==PROBLEM
true)and Rx.)
7114
-- when CELL SERVICE
when autonomous
autonomous recovery
recovery reset
reset is
is not
beingbeing
performed
performed
due due
to the fault to the fault
If
7115 category alarms disabled
BASE STATION INFORMATION (actCategoryAlarms ==
7101
false) BASE STATION/UNIT AUTONOMOUS RESET
NOTIFICATION
7654 CELLalarms
OPERATION DEGRADED
If category
does notdisabled (actCategoryAlarms
affect (customer
basic services of the==
base
false)category enabled configured
station
fault affects
(Uncommissioned basicINFORMATION
source) services of the base station
7116
7655 BASE STATION
CELLalarms
NOTIFICATION SERVICE PROBLEM
(Otherwise)
If category
category does notdisabled (actCategoryAlarms
affect (customer
enabled basic services of the==
configured base
false)
station
7652 BASE
7115 BASE STATION
STATION INFORMATION
NOTIFICATION
-(Uncommissioned
when autonomous source)
7655
due
If toCELL
category NOTIFICATION
the fault
alarms disabled (Otherwise)
If category
7101 alarms enabled
BASE STATION/UNIT AUTONOMOUS (customer configuredRESET
false)
NOTIFICATION
7652
7115 BASE
BASE STATION
INFORMATION
If category
7655 CELLalarms disabled (actCategoryAlarms
NOTIFICATION (Otherwise) ==
If category
false)
7652 BASE STATION
source)
7655
operateCELL NOTIFICATION
because (Otherwise)
has enough available
(customer and needed
configured
resources: both Tx and
actCategoryAlarms == true) Rx.)
7653
7115 CELL
BASE FAULTY
STATION(The cell cannot operate because it
INFORMATION
does not have enough available and needed resources:
Tx
If or Rx.)
If category
category alarms
false)
7652
7115 BASE
BASE STATION
INFORMATION
7655 CELLalarms
If category NOTIFICATION (Otherwise)
false)
7652 BASEalarms
7655
7115 CELL
BASE NOTIFICATION (Otherwise)
STATION INFORMATION

false)
station
If
7115 category
BASEalarms STATION are enabled
INFORMATION (customer configured
-If When category faultalarms
affectsdisabled
basic services of the base station:
7100
false) BASE STATION HARDWARE PROBLEM
-7653
If When CELL
category faultalarms
does not
FAULTY affect
are(The
enabled basic
cell cannotservices
(customer operate of the base it
because
configured
station:
does not
actCategoryAlarms == true): have enough available and needed resources:
7115
-Tx or BASE
When Rx) fault STATION
affects basic INFORMATION
services of the base station:
7654
7100
If CELL
BASE
category OPERATION
STATION
alarms are DEGRADED
HARDWARE
enabled (customer (The
PROBLEM cell can still
configured
If
operate category
-actCategoryAlarms
When faultalarms
because
does are
itnot
stilldisabled
has enough
affect basic (actCategoryAlarms
available
services of and
the base ==
If
false): category alarms are == true):
needed
station:
7115 BASEresources:
STATION both Tx and
INFORMATION Rx)
actCategoryAlarms
7653 CELL FAULTY ==(Thetrue):cell cannot operate because it
7115
-does When BASE STATION INFORMATION
notfault
have affects
enough basic services
available andof needed
the baseresources:
station:
If
7116
Tx category
or BASE
Rx.) alarms
SERVICE (actCategoryAlarms
PROBLEM ==
If
-false): category
When faultalarms
does are affect
not disabled basic (actCategoryAlarms
services of the base==
7654
false): CELL OPERATION DEGRADED (The cell can still
7655
station:
operate CELL NOTIFICATION
because it still hascellenough available and
7653
When
7115 CELL
fault
BASE FAULTY
affects
STATION (The
basic services
INFORMATION cannot
of the operate because it
base station:
needed
does not resources:
have both
enough SERVICE Tx and
available and Rx.) needed resources:
7116
7652 BASE STATION PROBLEM
If
Tx
If or BASE
category
Rx.) alarms
category
STATION
alarms
enabled
are
NOTIFICATION
disabled
(customer configured (The faulty SFP
works
actCategoryAlarms on optical interface that is not used to cell
provide
7654
When
false):
transmission
CELL OPERATION
fault does for not==
any
true)
affect
cell.)
DEGRADED
basic services (Theof the can still
base
-operate
station: when fault affects
because basic
it still has services
enoughofavailable the baseand station
7652
When
7116 BASE
fault
BASE STATION
affects
STATION basic NOTIFICATION
services
SERVICE of the (The
PROBLEM basefaulty
station: SFP
needed
7115
works BASE
on resources:
an STATION
optical both Tx
interface and
INFORMATIONIfthat Rx.)
is not category
used to alarms
provide
If
7116
-enabled category
whenBASE fault alarms
STATION
does are enabled
SERVICE
not affect (customer
basic PROBLEM
services configured
of faulty
the base
7652 BASE STATION
(customer
for anyconfiguredNOTIFICATION (The SFP
transmission
actCategoryAlarms
station == true) actCategoryAlarms ==
cell.)
works
true)
7653 on optical interface that is not used to provide
-When
7115 whenCELL
fault FAULTY
faultdoes
affects (The
notbasic
affect cell
services
basic cannotof the
services operate
base
of the because
station
base
-there
7100
station: whenBASE
transmission arefault
BASE
STATION
for
notaffects any
enough
STATION
INFORMATION
cell.)
basic services
available
HARDWARE andofneeded
the base
PROBLEM station
resources:
-7116
Tx
7115
If or BASE
when Rx.)
BASE
category
STATION
faultalarms
does
STATION not SERVICE
affect basic PROBLEM
INFORMATIONIf
disabled services
(actCategoryAlarms of the==
category base
alarms
-7654
station
enabled when fault
CELL (customer configured actCategoryAlarmsbase
does
OPERATION not affect basic
DEGRADED services (The of the
cell can
==still
false)
station
operate
7115
true)
7652 BASE because
STATION
BASE STATION it still has enough
INFORMATION
NOTIFICATION available and
(The faulty
7115
-needed whenBASE STATION
resources:
autonomous both INFORMATION
Tx
recovery and Rx.)
optical fault
interfaceaffectsis notbasic
used toreset
services ofisthe
provide beingbase performed
transmissionstationfor
due
7116
any to the
BASE fault
STATION SERVICE
cell.) alarms disabled (actCategoryAlarms == PROBLEM
If
7101
-7654 category
when BASE STATION/UNIT
fault OPERATION
does not affect AUTONOMOUS
basic services RESET
of faulty
the base
false) CELL DEGRADED (The
NOTIFICATION
station
optical interface is used to provide transmission for any
7652
7115 BASE
BASE STATION
INFORMATION (The faulty
cell.)
optical interface is are
not disabled
used to provide transmission for
If category alarms (actCategoryAlarms ==
any
false) cell.)
7654
7650
false) BASE CELL OPERATION
STATION FAULTY DEGRADED (FSP and (TheFBB,faultyABIx:
optical
The
7652 interface
faulty FSP/ABIx
BASEalarms STATIONis used
is to
not provide
mapped
NOTIFICATION transmission
to any cell
(The faulty for all
and any
If
cell.)category enabled (customer configured
FSPs/ABIx's
optical interface
actCategoryAlarms in the BTS
is enabled
not
==used are faulty.)
to provideconfigured
true)(customer transmission for
If
7651 category
BASE alarms
STATION OPERATION
any
- when cell.)fault affects
actCategoryAlarms basic
== services of DEGRADED
true) the base station (FSP
and
7654
7100 FBB,
CELL ABIx: The
OPERATION
BASE STATION HARDWARE faulty FSP/ABIx
DEGRADED is not
(The
PROBLEM mapped
faulty to
7115
any cell and at least one INFORMATION
other FSP/ABIx is operational.)
optical interface is used to provide
- when fault does not affect basic services of the base transmission for any
7652
cell.)
station BASE STATION NOTIFICATION (Optif -
If category alarms
autonomous recovery disabled
optical (actCategoryAlarms
link == false
7115
7652 BASEalarms STATION INFORMATION
resynchronization is ongoing to cancel the fault) 2. FSP
If category enabledNOTIFICATION
(customer (1. FSM;
configured
on FBB or ABIx
actCategoryAlarms
7653 CELL FAULTY not == mapped
(1.true)
FSP to
andanyFBB,cell.)ABIx: The faulty
If
7655 category
-FSP/ABIx CELL
when fault alarms
NOTIFICATIONdisabled (actCategoryAlarms
(FSP on FBBbase or ABIx ==
false) is affects
mapped basic
to the services
cell; 2. of the
OptIf: The station
cell cannot
mapped
7112
operate BASE to the
because cell.)
STATION it does CONFIGURATION
not have enough PROBLEM
available and
7651 whenBASE
-needed fault STATION
does not OPERATION
affect basic services DEGRADED of the base (FBB,
ABIx: resources: Tx or Rx.)
The faulty FSP/ABIx is not mapped to any cell and
station
7654
If CELL
category OPERATION enabledDEGRADED (OptIf [The cell
at
7115 leastBASEonealarms
other
STATION FSP/ABIx (customer
INFORMATIONis operational.) configured
can still operate
== it
true)
7653 CELL FAULTY (1. FBB, ABIx: The faulty still has enough available
FSP/ABIx
and
-iswhen needed
mapped fault toresources:
affects
the basic
cell; 2. both
Faulty Tx
services and
BTS of Rx.])
the base
secondary station
unit
If category
7116 BASE alarms
STATION disabled
SERVICE (actCategoryAlarms
PROBLEM ==
(FCT)
false) in dual core supports the cell.)
-7652
whenBASE fault does not affect basic services of the base
7651
OPERATION DEGRADED (FSM: Faulty(1.
FSM
FSM; baseband
2. FBB/ABIx resources
when FSPdoes on not
FBB transmit
or ABIx data
is for any
not
7115
cell.) BASE STATION INFORMATION
mapped to any cell.)
7654 CELLalarms
If category OPERATION
disabledDEGRADED (FSP on ==
(actCategoryAlarms FBB,
ABIx
false)is mapped to the cell.)
7652
CELL OPERATION DEGRADED (fault does not
(The faulty
affect basic services of the base station)
optical interface is used to provide transmission for any
cell.)
7652 BASE STATION NOTIFICATION (The faulty
optical interface is not used to provide transmission for
any cell.)
-AirScale When fault BTS affects
FDD, basic services of theAirScale
base station:
The
7116 faulty
BASE FSP is notAirScale
STATION mapped
SERVICE
BTSto anyTDD,
PROBLEMcell and all FSPs SBTS,in
Flexi
the BTS
BTSfault FDD,
are faulty.) Flexi BTS TDD, Flexi SBTS:
-If
If When
category
category does not
alarms
alarms affect(customer
disabled
enabled basic services
(customer of the base
configured
configured
7651
station: BASE STATION OPERATION DEGRADED (FSP
actCategoryAlarms
actCategoryAlarms
and FBB/ABIx: The ==
==
faultyfalse):
true):
FSP is not mapped to any cell
7115
7652
- When BASE fault oneSTATION
affects basicINFORMATION
NOTIFICATION
services of the (1.base
SSDstation:
firmware
and at least other FSP is operational.)
update;
7116
7652 BASE 2. The faulty BTS
STATION secondary
SERVICE
NOTIFICATION PROBLEMunit [FCT] in dual
(autonomous
If
core
-recovery category
When does fault alarms
not support
does disabled
not any
cells.)
basic services the==
offault base
If
false) category reset
alarms is being
enabled performed
(customer dueconfigured
to the or
7653
station:
fault CELLnot
does FAULTY
affect (The services
basic faulty BTS of secondary
the base unit
station)
actCategoryAlarms
7651
[FCT] BASE
in dualFAULTYSTATION == OPERATION
core supports true):the cell.) DEGRADED (1.
7115
-7653 When BASE
CELL STATION
faultfault
affects (1.INFORMATION
basic FSP andconnected
services FBB/ABIx:
of the baseThe faulty
station:
FSM
7650 when
BASE STATIONdetected on
FAULTY port (otherwise)
FSP
7116
to is mapped
BASE
FBB/ABIx STATIONto
and fault the cell;
SERVICE
has 2.
not OptIf: The
PROBLEM
impactDEGRADED
on cell cannot
any cell;== 2.
7651
If
operate BASE
category because STATION
alarms enabledOPERATION
disabled
there are (customer
(actCategoryAlarms
not enough configured
available
-FBB/ABIx
actCategoryAlarmsWhen fault whendoes FSPnot
== affect
on basic
FBB/ABIx
true) services of theand base
false)
needed
If
station: category resources:
alarms Txcell.)
are or Rx.) (customer configured
enabled
is
-7651 not BASE
when mapped to any
fault OPERATION
affects
OPERATION of DEGRADED
the(OptIf:
base The station
(1.
7654
actCategoryAlarms
7115
7652 CELL
BASE STATION == DEGRADED
true):
INFORMATION
NOTIFICATION (FSM when cell
the
FSM
-can 7100
When BASE
when
still fault STATION
fault
operate affectsdetected
because
basic HARDWARE
on
it port
still
services has PROBLEM
connected
enough
of the base available
station:
fault
-to when detected
FBB/ABIx autonomous on
and faultport without
recovery
has not reset
impact isRx.)
being
on anyperformed
cell; 2.
and
7116
If
connection needed
BASE
category resources:
toSTATION
alarmsFBB/ABIxdisabled both
SERVICE
and Tx and
PROBLEM
(actCategoryAlarms
fault has no impact == on any
due
FBB/ABIx
-false) to the fault
when FSP on FBB/ABIx
When fault does not affect basic services of the base
cell.)
7101
is BASE
not BASE
mapped STATION/UNIT
to any cell.) AUTONOMOUS RESET
station:
7651
7654 CELL STATION
OPERATION OPERATION
DEGRADED DEGRADED
(1. FSM (1.
when
NOTIFICATION
7652
7115 BASE
BASE STATION
INFORMATION (FSM when the
FSM has
fault when fault detected
impact on any on 2.FSP
cell; port connected
fault
-on
to When detected
FBB/ABIx autonomous on
andmappedport
fault without
recovery
has reset isonbeing
anyperformed
If
connection FBB/ABIx
category to isFBB/ABIx
alarms disabled tonot
and the impact
cell.)
(actCategoryAlarms
fault has no impact ==
cell; 2.
on any
due
FBB/ABIx
If to the fault:
when FSP on FBB/ABIx
category alarms are enabled (customer configured
false)
cell.)
7101
is
7650 not BASE
actCategoryAlarms mapped
BASE
STATION/UNIT
to any
STATION ==cell.)
true)
FAULTY
AUTONOMOUS RESET
(The failure in FSP or
7654
NOTIFICATION
7652 CELL
BASE OPERATION
STATION DEGRADED
NOTIFICATION (1.
(FSM FSM whenwhen the
-ABIx
fault when does
has fault not
impactdoes
have onnotany
any affectimpact
cell; basic
2.FSP services of the base
fault
station
on thedetected
functionality on port of without
any
If category
connection FBB/ABIx to isFBB/ABIx
alarms mapped
enabled
are tocell,
disabled
and the but
cell.)
(customer
fault
after the failure, all
has configured
(actCategoryAlarms
no impact on any ==
7115
FSPs
actCategoryAlarmsBASE
or ABIx's STATION == INFORMATION
true)
false)
cell.)
-in when fault affects basic
-7650 the BASE
when BTSfaultare already
affects
STATION basic notservices
operational.)
services
FAULTY (The
of
of the
the base
base
failure
station
in station
FSP or
7654
7100
7651 CELL
BASE OPERATION
STATION DEGRADED
HARDWARE
OPERATION (1.
PROBLEM FSM when
7116
ABIx
fault BASE
does
has not
impactSTATION
have on any
any SERVICE
impact
cell; 2.FSP the functionality(The
onPROBLEMDEGRADED of
failure
-any when
cell,inautonomous
FSPafter
but or ABIxthe does not
recovery
failure, all have
resetFSPs is being
or ABIx'sperformed
in the==
on
If
any FBB/ABIx
category
impact on isthe
alarms mapped
are to the
enabled
disabled
functionality cell.)
(customer
of any cell,configured
(actCategoryAlarms and at least
due
BTS to
arethe
actCategoryAlarms notfault
operational)
false)
one
7101 FSP
BASE or ABIx in == OPERATION
STATION/UNIT
true)
AUTONOMOUS RESET
-7651
7650
the when
BTSBASEfault
is
STATION
affects
STATION
still basic
operational.) services
FAULTY (Theof DEGRADED
the base
failure FSP(The
in station or
NOTIFICATION
failure
7116 in
BASE FSP or
STATION ABIx does
SERVICE not have
PROBLEMany impact on of the
ABIx
7652 does
BASE not have any
STATION impact on the functionality
NOTIFICATION (autonomous
functionality
-recovery
any when fault
cell, but of
doesany
after cell,
not
the and
affect
failure, at
basicleast
all FSPs one
services FSPof or
the ABIx
the in
base
If
the category
BTS reset
is alarms
still is being
disabled
operational) performed dueor
(actCategoryAlarms to ABIx's
the fault) in
==
station
BTS are already not operational.)
false)
7652
7115 BASE
BASE STATION STATION NOTIFICATION
INFORMATION (Autonomous
7651
7650 BASE STATION OPERATION
FAULTY (The DEGRADED
failure FSP(The
infault) or
-recovery
If when
failure
categoryin reset
autonomous
FSPalarms
is
or being
ABIx performed
recovery
does
enabled notreset
have
(customer
due
is anyto
beingthe performed
impact
configured on the
ABIx
7653
due does
toCELL not
the fault have
FAULTY any
(The impact
failure in FSP or ABIx makes
functionality
actCategoryAlarms
on the of any cell,
functionality ==any
of and
true) at but
cell, least onethe
after FSP or ABIx
failure, all in
the
7101 cell
BASE is disabled)
-the
FSPs BTS
when is
fault
or ABIx's still operational.)
NOTIFICATION
7652
in the BASE
7116 BASE
BTS are STATION
already NOTIFICATION
STATION SERVICE
not operational.) PROBLEM (fault does not
affect
-7651 basic
whenBASE services
fault doesSTATION of
not affectthe base
OPERATION station)
basic services DEGRADED of the base (The
If category
7653
station CELL alarms
FAULTY are(The
disabledfailure (actCategoryAlarms
in FSP or ABIx makes ==
failure
false) in FSP or ABIx does not have
the
7115
any cell
BASE is disabled.)
STATION INFORMATION
7650impact
BASEon the functionality
STATION FAULTYof(After any cell, and at all
the failure, least
one
FSPs FSP or
or ABIx's ABIx in
in the BTS are already not operational)
If
thecategory
BTS alarms
is still disabled
operational.) (actCategoryAlarms ==
7651
false) BASE STATION OPERATION DEGRADED (At
7652
least BASE
one FSP STATION NOTIFICATION
or ABIx NOTIFICATION (autonomous
in the BTS is still(ifoperational)
7652
recovery BASE reset STATION
is beingNOTIFICATION
performed due to other
the valid
fault)
7652 BASE STATION
reference source is available or When there (autonomous
is at least
recovery
one morereset working is being
primary performed
reference due to the
clock fault or
source
fault does
available) not affect basic services of the base station)
7653 CELL FAULTY (The
7651 BASE STATION OPERATIONDEGRADED (if no failure in FSP or ABIx
disables
other valid thereference
cell) source is available or When there
is no working primary reference source available)
operate
- When fault because affects it still
basic hasservices
enoughof available
the baseand station:
needed resources)
due to the fault:
NOTIFICATION
7115 Base Station Information
7107 BASE STATION CONNECTIVITY PROBLEM
alarm reported during base station startup
7115 BASE STATION INFORMATION alarm reported
during base station runtime
alarm reported during base station startup
7115 BASE STATION INFORMATION alarm reported
during base station runtime
7115 Base Station Information

Case 2
"TrxType is IDD/SDB, Dynamic Power Pooling Feature
is not in usealarms
If category ” are enabled (customer configured
Case
- when3 fault affects basic services of the base station
”Sector
7113 is inSTATION
BASE MOBSS Configuration,
ANTENNA LINE Dynamic Pooling
PROBLEM
Feature is not in use ”
station
Case 4
"BB Hopping Sector is Split Across Multiple Antenna,
Dynamic Pooling
If category alarmsFeature is not (actCategoryAlarms
are disabled in use ” ==
false)
7652 BASEalarms
(uncommissioned source)
7654
7115 CELL
BASE OPERATION DEGRADED (otherwise)
STATION INFORMATION
If
If category
category alarms
alarms are
false):
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
alarms are disabled
false):
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION

false):
7115 BASE
- When fault STATION INFORMATION
7116
7116 BASE STATION SERVICE
BASE STATION SERVICE PROBLEM
PROBLEM
- When fault
AirScale BTSdoes FDD:not affect basic services of the base
When
station:
7650 fault affects
BASE STATION basic services(1.ofThe
FAULTY the System
base station:
Module
7116
INFORMATION PROBLEM
internal communication or synchronization problem. All
signal processors inside the System Module are
-unstable.
When fault Flexidoes
BTS not affect basic
FDD/TDD: services
2. The FSP of onthe base
system
station:
module is faulty, the FSP is not mapped to any cell and
7115
7115 BASE
BASE STATION
STATION INFORMATION
INFORMATION
all FSPs in BTS are faulty.)
7651 BASE STATION OPERATION DEGRADED (1.The
When autonomous
System Module internal recovery reset is being
communication or performed
due to the fault: problem, or the BTS memory operations
synchronization
7101
are not BASE
stable. STATION/UNIT AUTONOMOUS
At least one signal RESET
processor inside the
NOTIFICATION
System Module is working. Flexi BTS FDD/TDD: 2. The
FSP on system module is faulty, the FSP is not mapped
to any cell and at least one FSP in BTS is operational
faulty.)
Reported alarms description: 7650 BASE STATION
7652
FAULTY BASE (The STATION NOTIFICATION
faulty FBB/ABIx (1. Thetoworking
is not mapped any cell
FSP is not mapped to any
and all FSPs/ABIx in BTS are faulty.)cell, 2. Faulty BTS secondary
unit
7651(FCT)
BASEinSTATION
dual core OPERATION
doesn't support any cells). (1.
DEGRADED
7653
The faulty FBB/ABIx is not mapped to any module is
CELL FAULTY (1. The FSP on system
faulty
cell andand at the FSP
least oneisother
mapped to the cell,
FSP/ABIA 2. Faulty BTS
is operational; 2.
secondary unit (FCT) in dual core
The degraded FBB/ABIx is mapped to any cell.) supports the cell).
7654
7652 CELL
BASE OPERATION DEGRADED (The
STATION NOTIFICATION degraded
(Working
FSP is mapped to the cell.)
FBB/ABIx is not mapped to any cell.)
7655
7653 CELL
CELL NOTIFICATION
FAULTY (Faulty (The working
FBB/ABIx FSP is to the
is mapped
mapped
cell.) to the cell.)
7654 CELL OPERATION DEGRADED (Degraded
FBB/ABIx is mapped to the cell.)
7655 CELL NOTIFICATION (Working FBB/ABIx is
mapped to the cell.)
in the System
Module cannotModule internal
be identified bybaseband
its productbus, code 2. but
Theis
faulty
known
Flexi
7651 BTS
BTS by
BASE secondary
its
FDD, physical
Flexi
STATION OPERATION unit
BTS (FCT)
TDD, in dual
AirScale DEGRADEDcore
BTS doesn't
TDD, (A
7650
support
device
AirScale BASE BTSSTATION
any
address cells)
FDD:[by object FAULTY or(The
ID],problems, the number temperature of FSPs in
CRC
measured failure, synchronization or an incorrect
the
7652 BTS
initialization BASE is at too the FSM/ASIx
STATION
in theproperly
optical
is lower than -10°C. The
NOTIFICATION
interface.)
BTS
7653
small, cannot
(Uncommissioned CELL
or a unit start
FAULTY or an unit(The
IP because
RF Module
address
source Tx/Rx the
initialization FSPs/ABIA
internal
filter) has baseband
failed.)
cannot
bus
7653 is be
out powered
of on
synchronization, in too cold
or the conditions.)
cell cannot operate
7652 BASE STATION NOTIFICATION (The controlthe
CELL FAULTY (A critical HW/SW fault inside
because
7652
RF BASE
Module. ittraffic
does
STATION
The isnot
cell have enough
NOTIFICATION
cannot operate available (Anthe
because and needed
unsupported
itSystem
does
message
7652
7651
resources: BASE
BASE TxSTATION
STATION
or
malfunctioning
Rx) INFORMATION
OPERATION between (Fault
DEGRADED has no not
module
have
and RF has been
enough
Modules.) availablefoundand in theneeded resources: Tx or Rx)
impact
(Temperature on cells.) on
BTS.
7654 Typically
CELL thisFSP/ABIA
OPERATION happens board
when aexceeds
DEGRADED new (The critical
module version
7654
threshold
7653 CELL
CELL OPERATION
value.)
faulty BTS (There is unit still
cell can
is
operate
7653 installed
CELL becauseand
FAULTY anit older
still
(Ahas BTS
Small SW
enough
Form-Factor insecondary
is available
use, which and does
Pluggable
abnormal
(FCT) in CPRI
dual coreinterface
supports to upper
the hop.)
cell)
not
needed
(SFP) support the
resources:
malfunction new module
both
occurred Tx version.)
and Rx)
7653
STATION (SFP isorMissing;
NOTIFICATION the SFPAbnormal module
(The System is not
physically
reception
Module onpresent
temperature SFP (no
to electrical
upper
exceeds hop connection
has occurred; exists),
Severe the
7654
7653
incoming CELL OPERATION
FAULTY
optical signal (The RF the
DEGRADED
is missing Module threshold
oroccurred;
too or(There value.)
Filter
weak, is
orathe be
cannot
SFP performance
synchronization aggravation
failure inThe theSystem has
RF Module internalSevere
identified
fiber cable byisits product
detached. Module clock
SFP
7653
baseband reception
CELL FAULTY
bus, power
or the aggravation
(The
cell temperature
can still occurred;
operate inside SFP
because the [by has
code
reference
failed
specific
but
or
is
is
RF
known
differs
mismatched.)
Module
by
from is
its
the
too
physical
RF
high. Module
Or
device
the
address
clock,
cell the
cannot RF it still
has
object_ID],
Module enough lost anavailable
lock to theand needed
incoming resources:
clock, or the cell bothcannotTx
operate
and
RF Rx)
Module because with there
incompatibleare notfrequency
enough available
has been and
operate
needed because it does
resources: Tx or not Rx)have enough available and
detected,
needed resources: both sector Tx or Rx)
7655 CELL
types [A andNOTIFICATION
B] are configured (Datato the corruption
same RF in Module
the RF
7654
Module
in the CELLinternal
two-carrier OPERATIONbaseband DEGRADED
bus.) (The
7654
temperature CELL OPERATION inside DEGRADED (TheisSystem
case,
Module a dual
clock PA RFthe
reference
specific
module differs
RF
hasfrom been Module
the replaced
RF Module
toowith low,a
clock
the
single highestPAofRF temperature
module exceeds the power decrease
in
limit, a part
orcannot
the cellthe RX,
can allor the
stillcells cell
operate can still
because there operate because
are
and
itenoughstillit has enough serve available commissioned
and needed resources: to the RFboth
module, available
or the cell and needed
cannot operateresources:because bothit Tx and
does not
Tx
Rx) and Rx)
have enough available and needed resources: Tx or
Rx.)
7655 BTS
Flexi CELLFDD, NOTIFICATION
Flexi BTS TDD, (Validated
FlexiBTS, RF module
AirScale BTS
Flexi
temperature
TDD, BTS
AirScale FDD, is Flexi
higher
BTS
7654 CELL OPERATION DEGRADED (The Mast BTS
than
FDD: TDD,
the AirScale
pre-defined BTSmaximumTDD, Head
AirScale
allowed
7650
Amplifier BASE BTS
value.)
[MHA] FDD,
STATION Flexi
or TILTFAULTY SBTS,
cannot AirScale SBTS:
7650
(The
be identified BASE
BTS unitSTATION
byproperties
its product FAULTY
data
code is (The
invalid
but issoftware
or missing,
known bydoes not
its the
support
optical the
interface
physical device address new commissioning
FPGA file is file
invalid loaded
or missing,to the a BTS.)
Flash
7651
memory
[by object_ID], BASE STATION
operation FilterOPERATION
the failure has occurred
cannot DEGRADED
be identified in FCM byor itsin(Anall
incorrect
FSPs,
product code the commissioning
BTS-internal parameter
SW update value,
has an
failed, error
or a in the
commissioning
corrupted
but a working SW TX/RX file, or
file hasFilter the transmission
beenexists detected in the parameters
in LCR,
the Flash the Filter have
not
memory
and/or been TILTincommissioned
FCM or in all or properly set.)
FSPs.)
7652 not BASE
is category properly STATION
configured, NOTIFICATION
or the cell can (There
still are
operate
If alarms are enabled (customer configured
problems
7651 BASE with
because it still has == true): commissioning
STATION OPERATION data in SW
DEGRADED package, but
actCategoryAlarms
the
(A BTS
Flash is still
memory operational.)
operation failure has occurred in at
-enough
Flexi When SBTS, available
fault affects
AirScale and needed
basic
SBTS, servicesresources:
Flexi of the
BTS FDD,bothFlexi
base Tx and
station:
BTS
least
Rx.)
7116
7652 one
BASE FSP or DSP,
STATION the BTS-internal
SERVICE
NOTIFICATION PROBLEM SW update
(BTS fault from has
TDD:
-failed,
the When
-detected
or
External
7651 BASE
a
fault corrupted
does
Antenna
STATION not SW
affect
Line file has
basic
Device (ALD
OPERATION
been
services of the
working for (No
DEGRADED base
7655
station:
other CELL
BTS) in is the Flash memory
NOTIFICATION
reported as BTS in
(Externalat least
notification) oneisFSP
Filter missing or
valid
DSP.) reference sources available. The BTS OCXO is in
from
7115
holdover Antenna
BASE mode.) line.)
STATION INFORMATION
-7653When
7652CELL
-7652 autonomous
BASE FAULTY
STATION recovery(cell reset
(RFNOTIFICATION cannot is operate
being
(Some performed
because
due
there toBASE
isthe
commissioned notfault: STATION
enough NOTIFICATION
available
synchronization andsource needed (The
is
SW beingTx
resources:
missing but
downloaded
7101 BASE to FSM is corrupted or incorrectlyRESET formed.)
or
thereRx)) is otherSTATION/UNIT
source available AUTONOMOUS
still. Tuning follows this
NOTIFICATION
new reference.)
7654
7654 CELL CELL OPERATION
OPERATION DEGRADED DEGRADED (The (A HW SW failure
downloading
AirScale
detected BTS by anFDD,to the
antennaRF Module
AirScale has
BTS TDD,
line device. failed.) AirScale SBTS,
Or communication
Flexi
with the BTS FDD, Flexi
application MHABTSorTDD, RETFlexi failed. SBTS:RF (cell can
7655
If category
operate CELL because NOTIFICATION
alarms areenough
has disabled (The SW being
(customer
available downloaded
andconfigured
needed
to FR is corrupted
actCategoryAlarms
resources: or==incorrectly
false):
Tx or Rx)) NOTIFICATION (A fault in the formed.)
7652
7650 BASE BASE STATION STATION FAULTY (FCM / FCT - meaning 4
Mast
and 9;HeadThe faulty Amplifier FSP(MHA) is not is detected.
mapped to anyThecell faultand all
7655
reduces CELL the NOTIFICATION
gain performance (Thebut antenna
maintains lineits device
function. is
FSPs
not in the properly.
working BTS are faulty.) The configuration is not valid, or a
The
7651 alarmingSTATION MHA serves another BTS.)
given BASE parameter is incorrect.) OPERATION DEGRADED (The
faulty FSP is not mapped to any cell and at least one
7654
other CELL FSP isOPERATION operational; FCT DEGRADED- meaning (The11, Mast
24, 26) Head
Amplifier (MHA) does not
7652 BASE STATION NOTIFICATION (FCT - meaning work properly. The received
RF
10; signal
FSP / FBB level -ismeaning
decreased. 12 and The13) alarming MHA serves
this BTS.)
7653 CELL FAULTY (LCR; The faulty FSP is mapped to
the cell; FR)
7653 CELL FAULTY (meaning 4 and 9; The faulty BTS
secondary unit [FCT] in dual core supports the cell.)
7654 CELL OPERATION DEGRADED (LCR; case 15)
7220
faultalarms
does not SECURITY
affect PROBLEM
7110 category
BASE STATION enabledLICENSE (customer configured
LIMITATION
station
actCategoryAlarms == SOFTWARE
true)
7111
7115 BASE STATION INFORMATION MANAGEMENT
-PROBLEM when fault affects basic services of the base station
-7116 whenBASE autonomousSTATION recovery
SERVICE reset is being performed
PROBLEM
If
7112
due category
toBASE
the alarms
STATION
fault enabled (customer
CONFIGURATION configured
PROBLEM
-7113 whenBASE
actCategoryAlarms fault doesSTATION not
== affect
true):
ANTENNA basic services
LINE of the base
PROBLEM
7101
5G
station BTS, STATION/UNIT
AirScale BTS FDD, AUTONOMOUS
AirScale BTS TDD,RESET
5G
All
7114
NOTIFICATION BTS,
products:
CELL AirScale7115
SERVICE BTS
BASE FDD,STATION
PROBLEM AirScale BTS
INFORMATION TDD,
AirScale
AirScale 7115BASEBASE SBTS,
SBTS, Flexi
STATION BTS
Flexi BTS FDD,
FDD, Flexi BTS TDD, Flexi
INFORMATION Flexi BTS TDD, Flexi
7115
SBTS: STATION INFORMATION
-7116
SBTS:
If categorywhen
category autonomous
BASEalarms alarms
STATION recovery
disabled
SERVICE reset is being
(actCategoryAlarms
PROBLEM performed
== ==
If are disabled (actCategoryAlarms
due
If
false):
false)
to the fault
category alarms are enabled
enabled (customer
configured
actCategoryAlarms
7101
actCategoryAlarmsBASE STATION/UNIT == true):
== FAULTY
true) AUTONOMOUS RESET
All
7650
7112 products:
BASE STATION 7655 CELL NOTIFICATION
CONFIGURATION (1.FSM; 2.The PROBLEMfailure in
NOTIFICATION
-If when fault does not affect basic services
FSP/ABIx categorydoes alarms notdisabled
have any on theoffunctionality
(actCategoryAlarms
impact the==base
station
false)
of any cell but after the failureFlexiall(actCategoryAlarms
FSPs/ABIx's in the
If
AirScale
7115 category
BASE SBTS,alarms are
Flexi
STATION disabled
SBTS,
INFORMATION BTS FDD, Flexi BTS ==
All
BTS
false): products:
are already not operational)
TDD:
7650 BASE STATION FAULTY (Level BTS fault is(The
7651
7653
If CELLalarms
category FAULTY OPERATION
disabled DEGRADED
toggling
failure in in the BTS.)
FSP/ABIx are
does disabled
not have(actCategoryAlarms
any impact on the==
false)
7651 BASE STATION
functionality
7650 BASE of any cellOPERATION
STATION and at least one DEGRADED
FSP/ABIx (Level
in the
7652
BTS fault
is stillisoperational)
toggling in FAULTY
the BTS.)(1.FSM;(When
NOTIFICATION 2.The there
faulty is at
FSP
least
7652 is
onenot
BASE moremapped to
primary any cell
working
STATION(1.NOTIFICATION and all FSPs
reference in
clock
(LevelisBTS the BTS
source
fault
7653
are CELL FAULTY
faulty.) The faulty FSP/ABIx mapped
available.)
is
to toggling
the cell; in
2. the
The BTS.)
faulty BTS Secondary Unit (FCT) is
7651
If
7653 BASE
category
CELL STATION
alarms
FAULTY OPERATION
are(Level
enabled BTS faultDEGRADED
is toggling in(The
the
mapped
faulty to a cell)
FSP is not mapped to any cell and at least one
actCategoryAlarms
BTS.) == true)
7652 BASE STATION NOTIFICATION (The faulty BTS
-other
7654 when FSPfault
CELLunit is operational.)
affects
OPERATION basic services
DEGRADED of the(Level
base BTSstation
secondary
7653 CELL FAULTY[FCT] (1.
in dualThe core
faulty does
FSP not
is support fault
mapped any
to
All
is products: 7116
toggling in the BTS.) BASE STATION SERVICE
cells)
the cell; 2. The faulty BTS secondary unitfault
(FCT) in dual
PROBLEM
7655 CELL NOTIFICATION (Level BTS is toggling
-core when
in the BTS.) supports
fault doesthe cell).
7652
7656 BASE STATION CONNECTIVITY LOST (Level NOTIFICATION (The faulty BTS
secondary
Flexi BTS unit
FDD, (FCT)
Flexi
BTS fault is toggling in the BTS.) in
BTS dualTDD, core does
AirScale notBTSsupport
FDD, any
cells.)
AirScale BTS TDD: 7115
7657 BASE STATION CONNECTIVITY DEGRADED BASE STATION
INFORMATION
If
(Level categoryBTSalarms fault is are enabled
toggling in the(customer configured
-actCategoryAlarms
BTS.) when autonomous== recovery
true) reset is being performed
If
due
-7401 category
whento- the alarms
faultfaultaffects enabled
basic AL (customer
services configured
of the base station
7426
actCategoryAlarms EXTERNAL == true): (EAC1=7401, EAC2=7402,
All
7112
etc.) products: 7101 BASE
BASE STATION CONFIGURATION PROBLEMSTATION/UNIT
All
- when products:
AUTONOMOUS fault does 7115RESET
BASE
not affect STATION
NOTIFICATION INFORMATION
station
If
If
7115 category
category
BASEalarms alarms
STATION disabled
INFORMATION (actCategoryAlarms == ==
false):
false)
If
All category
products: alarms
7652 enabled
BASE (customer
STATION configured
NOTIFICATION
Flexi
If category BTS FDD,
actCategoryAlarms alarms Flexi
==BTS
are true)TDD,(actCategoryAlarms
disabled AirScale BTS FDD, ==
AirScale
false) BTS TDD:
7650
7112 BASE
BASE STATION
STATION FAULTY
CONFIGURATION (1.FCM/FCT or ASIx,
PROBLEM
If
5G category
BTS,
2.FSP/ABIA alarms
AirScale are enabled
BTS
[FSP/ABIA FDD,
is not (customer
AirScale
mapped BTS
to configured
anyTDD,cell and all
7652 BASE
-actCategoryAlarms
when fault STATION
doesFlexi
not NOTIFICATION
affect
==BTS true) basicFlexiservices(Unit of is
theworking.)
base
AirScale
FSPs/ABIAs
7653 CELL SBTS, in
FAULTYthe BTS- Whenare FDD,
faulty.]) BTS
reported on CELL_M TDD, Flexi
station
7112
SBTS: BASE STATION CONFIGURATION PROBLEM
7651
7115 BASE
BASE STATION
STATION OPERATION
INFORMATION DEGRADED
If category alarms are enabled
(FSP/ABIA is not mapped to any cell, but not all (customer configured
If category alarms
actCategoryAlarms
FSPs/ABIAs in theare
==disabled
BTS true): (actCategoryAlarms ==
are (actCategoryAlarms
faulty.)
If
-7653category
false)
When alarms
radioFAULTY disabled
module (1 reports that the configuration ==
false) CELL FSP is mapped to a cell, 2. has
7653
failed:
faulty CELL FAULTY
BTS secondary(In unit (FCT)
7653
7112 CELL
BASE FAULTY case
STATION CONFIGURATION cellincannot
dual core remainsupports
PROBLEM
the cell)
operational
-7652
When BASEradiobecausemodulethere
STATION does is
NOT
NOTIFICATION
not report
enough available
that
(Faultythe BTSRX
and/or TX
configuration resources.)
secondary
7654 CELL unithas failed:
(FCT) in dual core does (In notcase
support any
7115
cells.) BASE OPERATION
STATION INFORMATION DEGRADED
regardless to detected issue, the cell is still having
enough
If category available
alarms RX and/or TX (actCategoryAlarms
resources so it can ==
If category
remain alarms are
operational.)
disabled
false):
true)
7652
-7113
When BASE STATION
radioSTATIONmodule reports that the (In case fault
configuration
source BASE
is uncomissioned ANTENNA
unit. LINE PROBLEM has
failed:
7653 CELLalarms
If category FAULTY disabled (actCategoryAlarms ==
-false)
When radio module does NOT report that the
configuration has failed:
7653 CELL FAULTY (The cell cannot operate because
there are not enough available and needed resources:
Tx or Rx.)
operate because there are enough available and
needed resources: both Tx and Rx.)
4489:
In
7113
If case of inconsistent
BASE
category STATION
alarms SW after(actCategoryAlarms
ANTENNA
are disabled fallback:
LINE PROBLEM ==
7650 BASE STATION FAULTY (FCT [HW of
- when fault does not affect basic services
false): rel.4])
the base
station
In
7115
4489: case BASEof consistent
STATIONSW after fallback:
INFORMATION
7651 BASE STATION
In case of inconsistent SW after fallback: OPERATION DEGRADED (FCT
[HW
If rel.4])
If category
7650 BASEalarms
category STATION
alarms disabled
enabledFAULTY (actCategoryAlarms
(customer(FCT [HW rel.4])==
configured
false)
4083
-7652
In
7115
In
case
when
case
BASE
BASE STATION
of consistent
fault affects
STATION
of inconsistent
SW
basic NOTIFICATION
after
services
INFORMATION
SW
fallback:
of the base station
after fallback:
(Uncommissioned
7651
7108 BASE
BASE STATION
STATION source)OPERATION
SYNCHRONIZATION DEGRADED PROBLEM(FCT
If category
7650 BASE alarms
STATION enabledFAULTY (customer(FCT [HW configured
rel.3], FCT
7654
[HW
-If when CELL
rel.4]) OPERATION
faultalarms
does not DEGRADED (Otherwise)
[HW
If category
actCategoryAlarms
rel.4])
category alarms disabled==affect
enabled
(actCategoryAlarms
true):(customer configured
base
station
-false) When fault affects basic services of the base station:
actCategoryAlarms
4083
7115 BASE STATION == INFORMATION
true)
7652
7112
In
7115 case BASE
BASEof STATION
consistent
STATION SW NOTIFICATION
CONFIGURATION
after
INFORMATION fallback: (external
PROBLEM ALD;
In case of inconsistent SW after fallback:
-uncommissioned
7651 When BASE doessource)
fault STATION not affect
OPERATION basic servicesDEGRADED of the base(FCT
7650
If
7655 BASE
category
CELL STATION
alarms FAULTY
disabled
NOTIFICATION (FCT [HW rel.3],==
(actCategoryAlarms
(Otherwise) FCT
station:
[HW
If rel.3],
category FCT [HW rel.4])
[HW
false) rel.4]) alarms disabled (actCategoryAlarms ==
false)
If
7650 category
BASEalarms STATION enabledFAULTY (customer(Holdoverconfigured
is not
4085:
7652
In case BASE STATION
of consistent SW NOTIFICATION
after fallback: (external ALD;
actCategoryAlarms
possible)
If category alarms ==
disabledtrue) (actCategoryAlarms ==
In case
uncommissioned
7651 BASEof inconsistent
STATION source) SW after
OPERATION fallback:
DEGRADED (FCT
-false):
7651 whenBASE fault affects
STATION basic services of DEGRADED
OPERATION the base station
7650
7655
[HW BASE
CELL
rel.3], STATION
NOTIFICATION
FCT [HW rel.4])FAULTY (FCT
(Otherwise) [HW rel.3], FCT
7113
(When
7653rel.4]) BASE
no STATION
other primary ANTENNA
reference
CELL FAULTY - radio sharing is disabled with the LINE
clock PROBLEM
sources are
[HW
-available
WCDMAwhen fault anddoes
system not affect
holdover
module, basic
is possible).
and the services
LTE cell of the base
cannot
4085:
station
7652 BASE STATION NOTIFICATION (When there
operate
In because there areafter
not fallback:
enough available andis at
In case
7115
least case BASE
one
of consistent
ofmore
inconsistent
STATION
primary
SW SW after reference
INFORMATION
working fallback: clock source
needed
7651 BASEresources:
STATION Tx or Rx.
OPERATION DEGRADED (FCT
7650 BASE STATION FAULTY (FCT [HW rel.3], FCT
available).
7654
[HW
7101 CELL
rel.3],
BASE OPERATION
FCT [HW
STATION/UNIT rel.4]) DEGRADED
AUTONOMOUS - radioRESET
sharing is
[HW
If rel.4]) alarms disabled (actCategoryAlarms ==
category
disabled
NOTIFICATION with the(whenWCDMA reset system
is being module,
performed)but the LTE
false)
cell can still operate because there are enough available
7116
In
7652 case BASE
BASE STATION
of consistent
STATION SW SERVICE PROBLEM
after fallback:
NOTIFICATION (when
and
Faults:
reset needed
has4082not resources:
been both Tx
triggered for and
any Rx.
7651 BASE STATION
(Uncommissioned source)OPERATION DEGRADED (FCT
7652
reason) BASE STATION NOTIFICATION:
[HW
1. rel.3], FCT [HWsource.
Uncommissioned rel.4])
1.category
If Radio sharing alarmsisare disabled
enabled with the WCDMA
(customer system
configured
2. RET connected
module, and the radio to radio module with common HDLC
actCategoryAlarms == module
true): that was to be shared is
stack, in radio module
uncommissioned inbasic
LTE startup,
BTS. when fault 4057 or 1836
When
Faults: fault
4082affects services of the base station:
is
2. detected
In the at early
BTSSTATION stage.
startup phase - the cables to the same
7111 BASE SOFTWARE MANAGEMENT
7654
radio CELL OPERATION
module have a too DEGRADED
large mutual (Otherwise)
difference length.
PROBLEM
If
If category
category alarmsalarms enabled
are enabled (customer
configured
3.
When In the BTS
fault
actCategoryAlarms == doesruntime
not phase
affect
== true):
true) -
basic the new
servicescableof connected
the base
actCategoryAlarms
If category
-to
station:
If
Whenwhen
category faultalarms
the radio
fault affectsenabled
module
alarms
affects
has too
basic
enabled
basic
(customer
(customer
services
configured
large aofdifference
services the
of the
in
basestation:
configured
base
length
station
actCategoryAlarms
compared
7115
7116 BASE to other
STATION ==
cables true)connected
INFORMATION
SERVICE to
PROBLEM the radio
actCategoryAlarms
7111
7112 BASE STATION == SOFTWARE
true) MANAGEMENT
whenBASE
module.
-PROBLEM
7115
STATION
fault does
BASE STATION
CONFIGURATION
not affect basic services PROBLEM
INFORMATION of the base
If category
station
When alarms
fault alarms
does not are disabled
affect basic (actCategoryAlarms
services of the base ==
If category
false):
7115 BASEalarms STATION disabled (actCategoryAlarms
INFORMATION ==
If category
station:
false) disabled (actCategoryAlarms ==
In case
false)
7115 BASEof inconsistent
STATION SW after fallback:
INFORMATION
7653
7650
If CELL
BASE
category FAULTY
STATION
alarms (The
FAULTY
disabled cell cannot
(1. FCT
(actCategoryAlarmsoperate because
[HW rel.3], == FCT
7652
there BASE
are not STATION
enough NOTIFICATION
[HW
false)
If rel.4],
category alarms are disabled (actCategoryAlarmscell,
2. The faulty FSP is not mapped to any ==
Tx
and
7650 orallBASE
Rx.)
FSPs in the BTS
STATION are faulty.)
FAULTY (The faulty FSP/ABIx is
false):
7654 CELL OPERATION DEGRADED (The cell can still-
7651
notcase
In BASE
mapped of STATION
to any cellOPERATION
inconsistent SWand after
all FSPs/ABIx'sDEGRADED
fallback: in the BTS(FSP
operate
The
are faulty
faulty.)because
FSP it still
is not mappedhas enoughto(1.anyavailable
cell,[HW and
andrel.3],
at least
7650
needed BASE STATION
resources: bothFAULTY
Tx and Rx.) FCT FCT
one
7651 other FSP is operational.)
[HW rel.4], 2. The faulty FSP is not mapped to any(The
BASE STATION OPERATION DEGRADED cell,
7653
and allCELL
faulty FSPsFAULTY
FSP/ABIx is not
in the BTS(1. FSP
mapped when
are faulty.) to anyfaulty
cell FSP
and at is least
mapped
one
7651 other to the
FSP/ABIx
BASEalarms cell;
STATION 2.
is The faulty
operational.)
OPERATION BTS secondary
DEGRADED unit
If category
[FCT] in dual core enabled
supports (customer
the cell.) configured (FSP -
7653
The CELLFSP
faulty
actCategoryAlarms FAULTYis not ==(The
mapped
true)faulty to FSP/ABIx
any cell, and is mapped
at least to
7652
the
one BASE
cell.)
other FSP STATION
is NOTIFICATION
operational.) (The faulty BTS
7115
secondaryBASE STATION inINFORMATION
7653 CELLunit (FCT)(1.
FAULTY dual
FSP core whendoes faulty notFSPsupport
is any
cells.)
mapped to alarms
the cell;disabled
2. The faulty BTS secondary== unit
If
In category
caseinof consistent SW after (actCategoryAlarms
[FCT]
false) dual core supports thefallback:
cell.)
7651
STATION OPERATION NOTIFICATION DEGRADED
(The faulty (FCT BTS
[HW rel.3], FCT [HW rel.4], FSP)
secondary unit (FCT) in dual core does not support any
cells.)
7654
In case CELL OPERATION
of consistent SW afterDEGRADED fallback:
The faulty BTS secondary
7651 BASE STATION OPERATION unit (FCT)DEGRADED in dual core (FCT
supports the cell.

The faulty BTS secondary unit (FCT) in dual core
supports the cell.
7115
The BASE
faulty FSPSTATION
isFlexi INFORMATION
not SBTS,
mapped to any cell, andFlexi
at least
AirScale
If category SBTS,
alarms are enabled Flexi BTS
(customer FDD,configured BTS
one
TDD, other FSP
AirScale is
BTS operational.)
TDD, AirScale BTS FDD:
actCategoryAlarms
When
7653 autonomous
CELL FAULTY ==(1.true)
recovery
FSPresetwhen isfaulty
beingFSP performed
is
If
-mapped
due category
when fault
to the alarms
affects
fault: are enabled
basic services (customer
of the configured
base station
actCategoryAlarmsto the cell; 2. The faulty
== CONFIGURATION BTS
true) AUTONOMOUS secondary unit
7112
7101
[FCT] BASE
in dual STATION
STATION/UNIT
core supports the cell.) PROBLEM
RESET
NOTIFICATION
7652
7111 BASE
BASEalarmsSTATION
SOFTWARE (The faulty BTS
MANAGEMENT
If category
secondary unit (FCT) disabled
areinenabled
dual (actCategoryAlarms
(customer
core does notconfigured
support any==
PROBLEM
false)
cells.)
-- when fault does
In when
case fault affectsnot
of consistent
affect
basic basic services
services
SW after of the base
fallback:
of the base
station
station
7653
7116 CELL
BASE FAULTY
7651
7115 BASE
BASE STATION
STATION OPERATION
INFORMATION DEGRADED (FCT
-7654
[HW when CELL
rel.3], OPERATION
faultFCT
does not rel.4],
[HW affectDEGRADED
FSP)
station
If
7115 category
BASE alarms
7654
false) CELL OPERATION DEGRADED
-Thewhen autonomous
faulty BTS recovery
secondary unitreset
(FCT) is in
being
dualperformed
core
7650
due
If toBASE
thethe
category STATION
fault
alarms FAULTY
supports
7653 CELL FAULTYcell. (The faulty BTS secondary unit
7101 BASE
actCategoryAlarms STATION/UNIT
== true) AUTONOMOUS RESET
(FCT) in
NOTIFICATION dual core supports
7116 BASE STATION SERVICE PROBLEM the cell.)
secondary
If category unit (FCT)
alarms areindisabled
dual core does not support any
cells.)
false)
7650
7653 BASE- The cellSTATION FAULTY
is disabled because (1. FSM; 2. The faulty
the downlink carrier
FBB/ABIx
that transmitsis not mapped
PSS/SSS to any
signals cell
has and all
failed. FSPs and
If category alarms
FBBs/ABIx's in the enabled
BTS are(customer
faulty.) the configured
7654
If - The alarms
category
actCategoryAlarms cell is degraded
enabled
== true) because
(customer downlink
configured
7651
carrier BASE
that
transmits OPERATION
PSS/SSS
== INFORMATION
true) signals DEGRADED
is (The
still working.
7115
faulty BASE
FBB/ABIx STATIONis not mapped to any cell and at least
one
7111 other
BASE FSP or FBB/ABIx
STATION SOFTWARE is operational.)
MANAGEMENT
If
7653category
CELL alarms
FAULTY disabled
(The (actCategoryAlarms
faulty FBB/ABIx is mapped == to
PROBLEM
false)
the
-7652 cell.)
when fault does not affect basic services of the base
stationCELL FAULTY (The faulty BTS secondary unit
[FCT]
7115 BASE in dual core supports
STATION the cell.)
INFORMATION
secondary
If category unit [FCT]
alarms in dual(actCategoryAlarms
disabled core does not support == any
cells)
false)
Flexi Zone Micro, Flexi Zone Controller:
7650
If category BASEalarms
STATION FAULTY(customer configured
are enabled
Flexi
If Zone
category Access
alarms
actCategoryAlarms == true): Point,
enabled Flexi Zone SFN
(customer Antenna:
configured
7652 BASE
7115 BASE STATION INFORMATION== NOTIFICATION
true)
due
If to the fault
category alarms are
If
7101 category
BASEalarms are disabled
STATION/UNITenabled (actCategoryAlarms
(customer
AUTONOMOUS configured
RESET
==
false):
NOTIFICATION
7115
recovery
category alarms are enabledreset is not being
performed
actCategoryAlarmsdue to the fault
==disabled
true)
If
7108 category alarms are (actCategoryAlarms ==
-false)whenBASE STATION
autonomous SYNCHRONIZATION
recovery PROBLEM
due
7652 toBASE
the fault
If
7101 category
BASE alarms disabled
STATION/UNIT (actCategoryAlarms
AUTONOMOUS ==
RESET
If category alarms enabled (customer
false) configured
NOTIFICATION
actCategoryAlarms == FAULTY
true)
7650
-- when BASE
fault STATION
does notrecovery
affect basic
7652 when autonomous
BASE STATION NOTIFICATION resetservices
is being ofperformed
the base
(autonomous
station
due to thereset
fault
recovery
If
7115 category
BASE is being
alarms
STATION performed
enabled (customer
INFORMATION dueconfigured
to the fault)
actCategoryAlarms == true) AUTONOMOUS RESET
NOTIFICATION
-If when autonomous recovery
-duecategory
when alarms are
autonomous disabledreset
recovery reset
is being performed
(actCategoryAlarms
is not being ==
to the
false) fault
performed
7101 BASEdue to the fault AUTONOMOUS RESET
STATION/UNIT
7652
7115 BASE STATION
INFORMATION
NOTIFICATION
- when autonomous recovery reset is not being
If category due
performed alarms disabled
to the fault (actCategoryAlarms ==
false)

false)
due to the fault
NOTIFICATION
If
- when category alarms are
autonomous enabledreset
recovery (customer configured
is not being
actCategoryAlarms
performed due to the ==fault
true)
7115 BASE STATION INFORMATION (Antenna line
without relation to cell and without ALD, or ALD not
5G
related BTS,toAirScale SBTS,line
cell. Antenna Flexi SBTS:
related to cell without ALD.)
If
7113
If category
BASE
category alarms
STATION
alarms are enabled
ANTENNA (customer
LINE configured(DC
PROBLEM
If category
actCategoryAlarms
voltage alarmsfordisabled
disabled enabled
==
ALD true)
(actCategoryAlarms
(customer
utilized configured==
by cell.)
false)
-7652 whenBASEfault affects
NOTIFICATION
If
7115
7111 category
BASE alarms
STATION
BASEalarms
STATION are enabled
INFORMATION
SOFTWARE (customer configured
MANAGEMENT
If category
actCategoryAlarms are
== disabled
PROBLEM
false)
7115
If
-7652 when BASE
category STATION
faultalarms
does not INFORMATION
disabled
affect (HDLC
(actCategoryAlarms
basic services link
of the ==
base
disabled BASE for STATION
working ALD NOTIFICATION
without relation(Antenna
to the line
cell.)
false)
station
without relation to cell and without ALD, or ALD not
7113
7652
7115 BASE
BASE STATION
STATION ANTENNANOTIFICATION
INFORMATION LINE PROBLEM
related
(HDLC link to cell.)
disabled for working ALD with relation to the
7654
cell.) CELL OPERATION DEGRADED (DC voltage
If category
disabled foralarms are disabled
ALD utilized by cell.)(actCategoryAlarms ==
false)
7655 CELL NOTIFICATION (Antenna line related to cell
If
7650 category
BASE alarms
FAULTY (actCategoryAlarms
(The BTS is faulty ==
without
false) ALD.)
because of a file signature problem. A rollback to the
7654
previous CELL SWOPERATION
is required.) DEGRADED (HDLC link
disabled
7652 BASE STATIONfor working ALD with relation to(1.the
NOTIFICATION Thecell.)
BTS is
working on the current SW. The new SW cannot (HDLC link
be
disabled
activatedfor dueworking
to a fileALD withoutmismatch;
signature relation to2.theThecell.)
faulty
BTS secondary unit [FCT] in dual core does not support
any cells.) alarms are enabled (customer configured
If category
7653 CELL FAULTY==
actCategoryAlarms (The faulty BTS secondary unit
true):
[FCT]
7108 in dual
BASEalarms core
STATION supports the cell.)
If
7108 category
BASEalarms
enabled (customer
(customer
SYNCHRONIZATION configured
configured
PROBLEM
actCategoryAlarms == true) false):
-7651
If when BASE
category STATION
faultalarms
affects basicOPERATION
enabled
disabled services
(customer of DEGRADED
the base station
configured
7116 BASE
actCategoryAlarms
false) STATION == SERVICE
true) PROBLEM
-7650whenBASEfault does
autonomous
STATION notrecovery
affect
FAULTY basic
resetservices
is fault
(This ofperformed
beingleadsthe base
If category
station
due to the alarms
fault enabled (customer configured to this
alarm since losing synchronization
true) AUTONOMOUSmakes the whole
7115
7101
system BASE STATION
STATION/UNIT RESET
7115 BASE STATION INFORMATION slave.)
NOTIFICATION
out of order as synchronization
If category
- when alarms disabled
autonomous recovery (actCategoryAlarms
reset is not being ==
If category due
false)
performed alarms disabled
false)
7653
STATION(Radio SERVICE unit connected
PROBLEMto port #3 or
7652
#4 onBASE
FBBCSTATION
cannot beNOTIFICATION
used because of a problem
related
If category to port #3 or
alarms #4 configuration
disabled on FBBC card
(actCategoryAlarms == and
the
false) cell cannot operate because it does not have
If category
enough alarmsand
available enabled
needed (customer
resources:configured
Tx or Rx.)
7650 BASE
actCategoryAlarms STATION == FAULTY
true) (Out of Order)
7654
7651 CELL
BASE OPERATION
STATION DEGRADED
DEGRADED (Radio unit
(Degraded)
7115
connected BASEtoSTATION
port #3 orINFORMATION
#4 on FBBC cannot be used
because of a problem related to port #3 or #4
If category alarms
configuration on FBBCdisabled
card(actCategoryAlarms ==
but the cell can still operate
false)
because it has enough available and needed resources: configured
7652 BASEand STATION
actCategoryAlarms
both Tx Rx.) == NOTIFICATION
true)
-7652
whenBASEfault affects
STATION basic services of the(Radio
NOTIFICATION base station
unit
7116
connectedBASEtoSTATION
port #3 or SERVICE
#4 on PROBLEM
FBBC is not
If category
-commissioned.)
when alarms enabled
autonomous recovery (customer configured
actCategoryAlarms
due toBASE
the fault == true)
7651
7115 STATION DEGRADED (other case)
7101 BASE
BASE STATION
STATION/UNIT INFORMATION
AUTONOMOUS RESET
NOTIFICATION
false)
7652
false) BASE STATION NOTIFICATION
7650 BASE STATION FAULTY (critical temperature
threshold exceeded)
(warning temperature threshold exceeded)
If
If category
category alarms
false)
7650
7116 BASE
BASE STATION
STATION FAULTY
SERVICE PROBLEM
false)
false)
7650 BASE STATION
actCategoryAlarms == FAULTY,7651
true) BASE STATION
OPERATION DEGRADED
== true)(customer configured==
actCategoryAlarms
If
actCategoryAlarms enabled
==
(actCategoryAlarms
(customer
true) configured
false)
-actCategoryAlarms
when fault affects basic
== services of the base station
true)
-7116
7651 whenBASE
fault affects
BASE STATION
STATION basic servicesPROBLEM
OPERATION
SERVICE of DEGRADED
the base station
7108
7108 BASE STATION SYNCHRONIZATION
PROBLEM
-station
when autonomous recovery reset is being performed
If
due category
toBASE alarms
the fault disabled (actCategoryAlarms ==
7115
false) STATION INFORMATION
7101
-7650 BASE
whenBASE STATION/UNIT
autonomous recovery AUTONOMOUS RESET
NOTIFICATION STATION FAULTY
due to the fault
NOTIFICATION
false)
7650 BASEalarms
If category STATION FAULTY
false)
7652 BASEalarms
enabled (no cell in BTS
can provide service)
7653
7115 CELL
BASE FAULTY
STATION(other cell(s) can provide service)
INFORMATION
If
If category
category alarms
are enabled ==
false)
7652 BASE STATION
All products: 7115 BASENOTIFICATION
STATION INFORMATION
If category alarms are enabled

disabled (customer configured==
(actCategoryAlarms
false)
All products: 7112
7100
PROBLEMBASE STATION HARDWARENOTIFICATION
PROBLEM
If
If category
category alarms
are disabled == ==
(actCategoryAlarms
false)
false)
7651 BASE STATION
All products: 7650 BASEOPERATION DEGRADED
STATION FAULTY
(configuration failure at BTS startup)
All products:
If category 7651 are
alarms BASE STATION
enabled OPERATION
DEGRADED (re-configuration
actCategoryAlarms == true): failure during BTS
runtime)
If
If category
category alarms
alarms are
are disabled (customer configured
actCategoryAlarms == false):
7652
7116 BASE
BASE STATION
SERVICE PROBLEM

false)
If category
affectsenabled (customer
of the base station
category alarms
actCategoryAlarms enabled
== true)(customer configured
7116 BASE STATION
actCategoryAlarms == SERVICE
true) PROBLEM
-- when fault
fault affects
whenBASE does basic
not affectservices of the base
basic services station
of the base
7115
7113 BASE STATION
STATION INFORMATION
ANTENNA LINE PROBLEM
station
-7115
whenBASE
fault does not affect
STATION basic services of the base
INFORMATION
If category alarms
station disabled (actCategoryAlarms ==
false)
7115 BASEalarms
STATION INFORMATION
If category
7652 BASE STATION are disabled (actCategoryAlarms
NOTIFICATION (external RET;==
false)
uncommissioned source)
If category
7652 BASEalarms
STATIONdisabled (actCategoryAlarms ==
NOTIFICATION
false)
7652
7653 BASE STATION(The
CELL FAULTY NOTIFICATION (external
cell cannot operate RET;
because
uncommissioned
there are not enough source)
7654 CELL
available and OPERATION DEGRADED
needed resources: (RET)
Tx or Rx.)
operate
If because
category alarmsitare
stillenabled (customer configured
If
hascategory
enough alarms enabled
available (customer
and needed configured
resources: both Tx
actCategoryAlarms
== true)
true)
and
7112 Rx.)
- whenBASE STATION
fault affects basicCONFIGURATION PROBLEM
services of the base station
7113 BASE STATION ANTENNA
If category alarms are enabled LINE
(customerPROBLEM
configured==
-actCategoryAlarms
when fault does not disabled (actCategoryAlarms
false) ==affect
station
7116 CELL
BASE STATION SERVICE PROBLEM
7653
7115 BASE FAULTY
STATION INFORMATION
If
If category
category alarms
alarms are disabled (actCategoryAlarms
enabled configured== ==
false): disabled (customer
(actCategoryAlarms
actCategoryAlarms
false) == true)
7653
whenCELL
-7652 fault FAULTY
affects (Theservices
basic cell cannot operate
of the base because
station it
does BASE
not haveSTATION
enough NOTIFICATION
Tx or Rx.)
7654
due toCELL OPERATION DEGRADED (The cell can still
the fault
operate because it has enough
7101 BASE STATION/UNIT available and needed
AUTONOMOUS RESET
resources:
NOTIFICATIONboth Tx and Rx.)

false)
7650
PROBLEMBASE STATION FAULTY

false)
7102 BASE STATION RESOURCE BLOCKED BY
7650
USERBASE STATION FAULTY
If
If category
category alarms
are enabled ==
false)
7650 BASE STATION
All products: 7114 CELLFAULTY
SERVICE PROBLEM
If
If category
category alarms
alarms are disabled
false)
All
7116products: 7654 CELL
BASE STATION FAULTYPROBLEM
SERVICE
If
If category
category alarms
false)
7651
7112 BASE
BASE STATION
STATION OPERATION
CONFIGURATIONDEGRADED
PROBLEM
If
If category
category alarms
are enabled ==
false)
7650
7115 BASE
BASE STATION
STATION FAULTY
INFORMATION

false)
If
When category
fault alarms
affects are
basicenabled (customer
services configured
of the base station:
When fault does not affect basic services of the base
If
If category
category alarms
station: alarms are
false)
7115 BASE STATION
true)
7652
If
7115 BASE
category STATION
BASEalarms
INFORMATION
category affectsare
basic services
disabled of the base station==
(actCategoryAlarms
If
7113category
BASE alarms
STATIONenabled (customer
ANTENNA LINE configured
PROBLEM
false)
-7652
whenBASE
fault does not affect
STATION basic services of the base
NOTIFICATION
7115
stationBASE STATION INFORMATION
false)
7652
false) BASE STATION NOTIFICATION
7654 CELL OPERATION
actCategoryAlarms == true)DEGRADED (LNA
commissioned to a cell)
7652 BASE STATION NOTIFICATION (LNA is not
commissioned
If category alarmsto any cell served
disabled by the BTS) ==
(actCategoryAlarms
false)
If
7652 category
BASEalarmsSTATION enabled (customer configured
NOTIFICATION
If category
actCategoryAlarms alarms enabled
(Uncommissioned
actCategoryAlarms FR)
== true):
-If
7655 when faultalarms
CELL
category affectsenabled
basic
NOTIFICATION services of the
(Commissioned
(customer baseFR)
configured station
7115
7108 BASE
BASE STATION
STATION INFORMATION
-- when when autonomous
faultalarms recovery
affectsdisabled
basic resetofisthe
services being
baseperformed
station
If
due category
7112
false): BASE STATION CONFIGURATION PROBLEM
7101
If
-7652 whenBASE
category STATION/UNIT
faultalarms
does areaffect
not enabled AUTONOMOUS
basic(customer RESET
servicesconfigured
of the base
BASE
NOTIFICATION STATION NOTIFICATION
actCategoryAlarms
station == true)
-7115 whenBASE
fault affects
INFORMATION
If category
7112 BASEalarmsSTATION disabled (actCategoryAlarms
CONFIGURATION PROBLEM ==
-false)
when fault does not affect basic services
If category alarms disabled (actCategoryAlarms == of the base
7650
station
false) BASE STATION FAULTY
7115
7653 BASE STATION(There
CELL FAULTY INFORMATION
is a cell configured on the
radio
If module.)
category alarms
If
7652 category alarms enabled
BTS STATION
(customer
areNOTIFICATION
disabled configured
(actCategoryAlarms
(The fault is ==
actCategoryAlarms
If category
false) == true)
alarmsuncommissioned
detected
7112 against radio module.)
actCategoryAlarms STATION == CONFIGURATION
true):
NOTIFICATION PROBLEM
-(Uncommissioned
When fault affectssource)
basic services of the base station:
If
7112category
BASE alarms
STATION
7653 CELL FAULTY (The disabled (actCategoryAlarms
CONFIGURATION
cell cannot operatePROBLEM ==
because it
false)
-does
Whennotfault
have does not affect
enough basicand
available services
needed of resources:
the base
7654
Tx or CELL
Rx.) OPERATION DEGRADED
station:
7115
CELL OPERATION DEGRADED (The cell can still
operate
If categorybecause
alarms it has
If category
enough alarmsand
available are needed
disabled (actCategoryAlarms
resources: both Tx and ==
actCategoryAlarms
false): == true)
Rx.)
7115
7650 BASE
BASE STATION
STATION INFORMATION
FAULTY (FCT)
7652 BASE STATION NOTIFICATION (1. ALD (RET,
If category
RAE, LNA) alarms disabledto(actCategoryAlarms
is not mapped any cell; 2. The faulty == BTS
false)
secondary unit [FCT] in dual core does not support any
7652
cells.)BASE STATION NOTIFICATION
7653 CELL FAULTY (The faulty BTS secondary unit
[FCT] in dual
If category core enabled
alarms supports(customer
the cell.) configured
7655
actCategoryAlarms == true) (ALD (RET, RAE, LNA) is
CELL NOTIFICATION
mapped
7115 BASE to the cell)
STATION INFORMATION

false)
station
If
If category
category alarms
false)
-7111
7650BASE
BASESTATION
STATIONSOFTWARE
FAULTY (Out of Order)
MANAGEMENT
-PROBLEM
7652 BASE STATION NOTIFICATION (Working)
If
If category
category alarms
false)
7651
7112 BASE
BASE STATION
STATION OPERATION
PROBLEM
If
If category
category alarms
are enabled ==
false)
7651
7107 BASE
BASE STATION
STATION OPERATION
CONNECTIVITY DEGRADED
PROBLEM
If
If category
category alarms are disabled (actCategoryAlarms ==
If category alarms
false) alarms enabled (customer
are enabled configured
actCategoryAlarms
== OPERATION
true)
7651
7107 BASE
BASE STATION
STATION CONNECTIVITY DEGRADED
PROBLEM
If category alarms enabled disabled (customer configured==
(actCategoryAlarms
If
If category
category alarms
actCategoryAlarms alarms are ==disabled
true)(customer configured ==
false)
false)
actCategoryAlarms
-7651 whenBASE
fault affects
STATION == OPERATION
basictrue)
services of DEGRADED
the base station
7658
When
-7107 whenBASE
fault
BASE STATION
faultaffects
affects
STATION basicLICENSE
basic servicesLIMITATION
services
CONNECTIVITY ofofthe
thebase
basestation:
PROBLEM station
7108 7108 BASE
BASE STATION
STATION SYNCHRONIZATION
SYNCHRONIZATION
- when autonomous recovery reset is being performed PROBLEM
A
PROBLEM
-If critical
when fault
fault (or faults)
does not hasbasic
occurred in theofbase station
due to the
category fault
alarms
connectivity/interface. areaffect
enabled
Check
services
(customer
the reason
the base
configured
for the fault
station
actCategoryAlarms == true) AUTONOMOUS RESET
from
When
7115
NOTIFICATION the
BASEsupplementary
fault does not
STATION affecttextbasic
fieldservices
INFORMATION of the alarm.of the base
When
-station:When fault affects basic servicesofofthe
fault affects basic services thebase
basestation:
station
7108 7108BASEBASESTATION
STATIONSYNCHRONIZATION
SYNCHRONIZATIONPROBLEM
If 7115 BASE
category STATION INFORMATION
PROBLEM
-If
If When
category
categoryfaultalarms
alarms
alarms
disabled
does not
are affect
enabled
enabled
(actCategoryAlarms
basic
(customer services
(customer of the==
configured
configured base
false)
station
actCategoryAlarms
true)
7650
When
7115 BASE
fault does
BASE not==
STATION
STATION
true)
affect basic(Holdover
INFORMATION services of not
the possible
base
-station:
when fault affects
because of insufficient data basic services
or phaseof the
errorbase station3us)
exceeds
7108
76517115 BASE
BASE STATION
STATION SYNCHRONIZATION
OPERATION
INFORMATION DEGRADED PROBLEM
If category
-(Holdover
when faultalarms
does are
not disabled
disabled
affect basic(actCategoryAlarms
(actCategoryAlarms
services of the ==
base==
If possible or When no other
category alarms enabled (customer configured
false) primary reference
station
clock sources
actCategoryAlarms are available
true)and (Holdover
== FAULTY holdover isnot possible or
7650
7652
7115 BASE
BASE STATION
INFORMATION possible
other
-because cases)
when fault affects basic
of insufficient dataservices
or phaseof the
errorbase station3us)
exceeds
7652
7108
7651 BASE STATION
BASE STATION SYNCHRONIZATION
NOTIFICATION
OPERATION (if other
DEGRADED valid
PROBLEM
If category
reference
-(Holdover
when faultalarms
source
does isare
not disabled
available
affect or
basic(actCategoryAlarms
When
servicesthere of is at
the ==
least
base
false) possible or When no other primary reference
one more
station
clock working
sources primary reference
are available and (Holdover clock
holdover isnot source
possible or
7650 BASE
available)
7115 BASE STATION
STATION FAULTY
INFORMATION possible
other cases)
because of insufficient data or phase error exceeds 3us)
7652
7651 BASE STATION
BASEalarms
OPERATION (if other valid
DEGRADED
If category
reference source disabled (actCategoryAlarms at==
(Holdover
false) possible or When no other primaryisreference
is available or When there least
one
clock more working
sources primary
are available reference
and (Holdoverclock
holdover isnot source
possible or
7650 BASE
available) STATION FAULTY possible
other cases)
because of insufficient data or phase error exceeds 3us)
7652
7651 BASE
BASE STATION
OPERATION DEGRADED (if other valid
reference
(Holdover possible or When no other primaryisreference
source is available or When there at least
one more working primary reference clock
clock sources are available and holdover is possible or source
available)
other cases)
7652 BASE STATION NOTIFICATION (if other valid
reference
If categorysource
alarmsisenabled
available or Whenconfigured
(customer there is at least
one more working primary
available)

false)
If category
- when CA isalarms enabled at
not activated (customer configured
all on BTS:
actCategoryAlarms
7112 BASE STATION == CONFIGURATION
true) PROBLEM
- when fault affects
cell did basic services
not receive of the
CA specific base
cell station
deployment:
7100 BASE STATION
7114 CELL SERVICE PROBLEM HARDWARE PROBLEM
category does not affect (customer
enabled basic services of the base
configured
station
actCategoryAlarms == true) (actCategoryAlarms ==
7115
- whenBASE
7100 CA isSTATION
not activated at all on BTS:
HARDWARE PROBLEM
If category
-7651 alarms disabled (actCategoryAlarmsof the==
If category alarms enabled (customerDEGRADED
when
false)
BASE
fault STATION
does not OPERATION
affect basic services
configured base
-station
when cell did
actCategoryAlarmsnot receive
== CA
true) specific cell deployment:
7652
7654 BASE
7115 CELL STATION
STATION NOTIFICATION:
BASE OPERATION DEGRADED the faulty optical
INFORMATION
interface is not used to
provide transmission
If category for any(actCategoryAlarms
alarms disabled cell ==
7653
false) CELL FAULTY: the cell cannot operate because it
does
7652 not
BASEhave enough NOTIFICATION:
STATION available and needed resources:
the faulty optical
7655
Tx or CELL
Rx NOTIFICATION
interface is not used to
7654
provideCELL OPERATION
transmission DEGRADED:
for any cell the cell can still
operate because it still has
7653 CELL FAULTY: the cell cannot operate because it
enough
does notavailable and needed
have enough resources:
available bothresources:
and needed Tx and
Rx
Tx or Rx
7654 CELL OPERATION DEGRADED: the cell can still
operate because
still has (customer configured
enough
actCategoryAlarms ==needed
available and true): resources: both Tx and
Rx
If
If category
category alarms
false):
7651
7108 BASE
BASE STATION

actCategoryAlarms enabled (actCategoryAlarms
==
false)
actCategoryAlarms ==affect
-7651
whenBASE
fault does not
7108
stationBASE STATION SYNCHRONIZATION PROBLEM
false):
7653
false) CELL FAULTY
7652 BASE STATION NOTIFICATION (if other valid
reference
If categorysource
alarmsisenabled
available or Whenconfigured
(customer there is at least
one more working primary
available)
If
If category
category alarms
are enabled ==
false)
7652
7115 BASE STATION
BASEalarms
INFORMATIONconfigured
If
category enabled (customer configured
actCategoryAlarms
==disabled
true)
If
7115category alarms are (actCategoryAlarms ==
whenBASE
-false) STATION
fault affects INFORMATION
7116
NOTIFICATION PROBLEM
If category
- when faultalarms disabled
does not affect (actCategoryAlarms
base
false)
station
7652
7115 BASE
BASE STATION
INFORMATION
7655 CELLalarms
If category NOTIFICATION (otherwise)
false)
7652 BASEalarms
7654
7115 CELL
BASE OPERATION DEGRADED (otherwise)
STATION INFORMATION

false)
station
7115 BASE STATION
true)
If
due category alarms are disabled (actCategoryAlarms ==
to the fault
false)
7651
NOTIFICATION BASE STATION OPERATIONAL DEGRADED
(FCT;
- whenABIx
If category is not mapped
alarms
autonomous are to any
enabled
recovery cell.)
(customer
reset configured
is not being
7652
actCategoryAlarms BASE
performed due to the fault STATION == NOTIFICATION
true): (fault does not
-affect
7116 When basic
fault services
BASEalarmsaffects
STATION of
basic the base
services
SERVICE station)
of
PROBLEMthe base station:
If
7654
7116 category
CELL
BASE OPERATIONAL
STATION enabled
SERVICE(customer
DEGRADED
PROBLEM configured
(FCT; ABIx is
-actCategoryAlarms
mapped
If When
category to any
fault does == true) basic services of the base
cell.)
not
are affect
7110
station: BASEalarms
STATION disabled
LICENSE(actCategoryAlarms
LIMITATION ==
false)
7115
If
7652 BASE
category STATION
BASEalarms
STATION INFORMATION
If category
-actCategoryAlarms
When alarms
autonomous disabled
recovery (actCategoryAlarms
reset is due
being ==
recovery
false) reset is not== true)
being performed toperformed
the fault)
due
-7653 whentoCELL
the
faultfault:
7658
7101
7116 BASE BASE FAULTY
STATION
STATION LICENSE
STATION/UNIT SERVICE LIMITATION
AUTONOMOUS
PROBLEM RESET
NOTIFICATION
A
due critical
to thefault
fault(or faults) has occurred in the base station
connectivity/interface.
If
7101 category
BASEalarms are Check
STATION/UNIT disabled the(actCategoryAlarms
reason for the
AUTONOMOUS fault==
RESET
from
false):
NOTIFICATION the supplementary text field of the alarm.
5G
7650 BTS,
BASE Flexi BTS FDD,
STATION Flexi BTS
FAULTY (TheTDD, AirScale
failure in FSPBTS
TDD,
[ABIx] AirScale
doesalarms BTS
not have FDD, Flexi
any impact SBTS, AirScale
on the functionalitySBTS:
If
If category
are enabled(actCategoryAlarms
(customer == of
configured
any
false) cell, but after the failure, all FSPs [ABIx's] in the
actCategoryAlarms
BTS are already not== true)
operational.)
7650
All BASE
products: STATION
7115 BASE FAULTY
STATION INFORMATION
7651 BASE STATION OPERATION DEGRADED (The
failure in FSP [ABIx] does not have any impact on the
If category alarms
functionality of anydisabled
cell, and(actCategoryAlarms
at least one FSP [ABIx] == in
false)
All
7652 products: 7652 BASE
BASE STATUIN STATION NOTIFICATION
recovery reset is being performed due to the fault or
If
fault category
does not alarms
affectenabled (customer
of the base station)
If category
actCategoryAlarms alarms enabled
== true) (customer configured
7653 CELL
actCategoryAlarms FAULTY (The
== true) failure in FSP [ABIx] makes
-the when
cell fault affects basic
disabled.) services of the base station
7115
STATION INFORMATION
CONNECTIVITY PROBLEM
If
to the fault
false)
-7101 whenBASE STATION/UNIT
autonomous recoveryAUTONOMOUS RESET
7652
NOTIFICATION BASE STATION NOTIFICATION (all cases)
due to fault
If
If category
category alarms
NOTIFICATION alarms disabled (actCategoryAlarms
-false)when fault does
actCategoryAlarms == true) not affect basic services of the base
7650
7115 BASE STATION INFORMATION FAULTY
affectsdisabled
If category
7116 category
BASEalarms
STATION enabled
SERVICE
(actCategoryAlarms
(customer
PROBLEM configured==
false)
7652
7115 BASE STATION
BASEalarms
INFORMATION
If category are enabled (customer configured
actCategoryAlarms
If category alarms enabled == true)(customer configured
If category
-actCategoryAlarms
when alarms disabled
autonomous == true)(actCategoryAlarms
recovery reset is being performed ==
false)
due to fault
7652
USERBASE
7101 BASE STATION
STATION/UNIT NOTIFICATION
AUTONOMOUS RESET
NOTIFICATION
category affectsdisabled
(actCategoryAlarms
If
7116category
BASEalarms
STATION enabled
SERVICE(customer
PROBLEM configured==
false)
true) basic services of the base
-7650
whenBASEfault does
STATION not FAULTY
7110
station BASE STATION LICENSE LIMITATION
false)
7658
false) BASE STATION LICENSE LIMITATION
7652 BASE STATION NOTIFICATION (BTS secondary
unit does not support any cells.)
7653 CELL FAULTY (All cells supported by the
secondary unit are faulty.)
If
If category
category alarms
false)
7650
CELL SERVICE FAULTY
If
If category
category alarms
false)
7650
CELL SERVICE FAULTY
If
If category
category alarms
false)
7650
CELL SERVICE FAULTY
If category alarms enabled (customer configured==

actCategoryAlarms enabled (actCategoryAlarms
false)
-7650
whenBASE
fault affects
FAULTY
7114
CELL SERVICE SERVICE PROBLEM
If
duecategory alarms disabled (actCategoryAlarms ==
to the fault
false)
NOTIFICATION
If
If category
category alarms
false)
7650
If category
7112 BASE STATION
BASEalarms
STATION FAULTY
category affectsdisabled
If
7112 category
BASE alarms
STATIONenabled (customer
CONFIGURATION configured
PROBLEM
false)
true) basic services of the base
-7650 whenBASEfault does not
STATION FAULTY
7114
station CELL SERVICE PROBLEM
false)
7653
If
false) CELLalarms
category FAULTY enabled (customer configured
actCategoryAlarms
7652 BASE STATION == NOTIFICATION
true): (BTS secondary
When
unit faultnot
does affects basic
support any services
cells.) of the base station:
If
7116 category
BASE alarms
STATIONare enabled
SERVICE (customer
PROBLEM configured
7653
If CELLalarms
category
actCategoryAlarms FAULTY (All
enabled
== cells supported
(customer
true): by secondary
configured
When
unit arefault does not==
faulty.)
actCategoryAlarms affect
true)basic services of the base
7115
station: BASE STATION INFORMATION
7115
7112 BASE STATION
BASEalarms
STATION INFORMATION
If category are disabled (actCategoryAlarms ==
-If when
false): fault does not
category alarms enabled affect basic
(customerservices of the base
configured
station disabled (actCategoryAlarms ==
7652 BASE STATION
actCategoryAlarms
false): == NOTIFICATION
true)
7115
-7652 BASE
whenBASE STATION
fault affects INFORMATION
basic services of the(BTSbasesecondary
station
7112
unit BASE
does notSTATION
support CONFIGURATION
any cells.) PROBLEM
If category
-7653
when faultalarms disabled
does not (actCategoryAlarms
affectsupported
basic services the==
false) CELL FAULTY (Cell by theofsecondary
base
station
unit is faulty.)
7652
7115 BASE
BASE STATION
INFORMATION (Shared radio
modules connected to the fault source peer system
module
If categorydoes not support
alarms disabled any cell.)
7653
false) CELL FAULTY (Shared radio module connected to
the
7652 fault
BASEsource peer system
STATION module supports
NOTIFICATION (Sharedany cell.)
radio
module does not support any cell.)
7653 CELL FAULTY (Shared radio module connected to
the fault source peer system module supports any cell.)
category does not affect (customer
configured
station
7115
faultalarms
affects INFORMATION
category are enabled (customer configured
7112 BASE STATION
actCategoryAlarms == CONFIGURATION
true): PROBLEM
If category alarms
-- when disabled (actCategoryAlarms ==
When fault
false) fault does not
affects affect
services of the
of the base base
station:
station
7652
7115 BASE
BASE STATION
INFORMATION (Shared radio
-module
When fault
does does not affect
not support anybasic
cell.)services of the== base
If category
station: alarms disabled (actCategoryAlarms
7653
false) CELL FAULTY (Shared radio module connected to
7115
the BASE
fault STATION
source peer INFORMATION
system module supports any cell.)
7652 BASE STATION NOTIFICATION (No cell
commissioned
- When autonomouson source.)
7653
due
If CELL FAULTY
to the fault:
category (The cell
alarms enabled cannot configured
(customer operate because it
does
7101 not
BASEhave enough available
STATION/UNIT
actCategoryAlarms == true) and needed
AUTONOMOUS resources:
RESET
Tx or Rx.)
NOTIFICATION

false):
(actCategoryAlarms
false)
actCategoryAlarms
7653 CELL FAULTY== true)
(The cell cannot operate because
7114
the CELL SERVICE PROBLEM
If category alarms are enabledthe
virtual node that supports cell is faulty
(customer and
configured
cannot restart.)
If
7650category alarms disabled
whenBASE
-false) STATION
fault does FAULTY
not affect basic(1.services
The BTS of is faulty
the base
because
station a virtual node failed to start; 2. A virtual node
7653 CELL
supporting FAULTY
7115 BASEallSTATION
cells is faulty and cannot restart.)
INFORMATION
7652
- when fault affects basic services of the(When
BASE STATION NOTIFICATION base station
autonomous
7108 BASE STATIONrecovery reset is not being performed
SYNCHRONIZATION PROBLEMdue
to the fault, but the faulty virtual node is not mapped to
any cell) alarms are disabled (customer configured
If category
actCategoryAlarms == false)
7652 BASEalarms
enabled (When no cells
are configured on BTS secondary
actCategoryAlarms == true) unit.)
7654 CELL OPERATION
All products: DEGRADED
7115 BASE STATION (Otherwise)
INFORMATION
If
If category
category alarms
false)
All
INFORMATION
If
If category
category alarms
false):
7652
All BASE STATION
products: 7115 are
BASENOTIFICATION
STATION INFORMATION
If category
7111 BASEalarms disabled
STATION (actCategoryAlarms
SOFTWARE MANAGEMENT ==
false)
PROBLEM
All products: 7652 BASE STATION NOTIFICATION
false)
7651 BASE STATION
actCategoryAlarms == OPERATION
true) DEGRADED (FCT
[HW rel.3], FCT [HW rel.4])
If
If category
category alarms are disabled (actCategoryAlarms ==
If category alarms
false) alarms enabled
enabled (customer
configured
actCategoryAlarms
== true)
true)
7653
7107 CELL FAULTY
7116 BASE STATION CONNECTIVITY
BASE STATION SERVICE PROBLEM PROBLEM
If
If category
category alarms
alarms disabled
==
false)
false)
7651
7650 BASE
BASE STATION
FAULTY - all cells are shut down.
7651 BASE STATION OPERATION DEGRADED - not
all cells are shut down (shutting down phase or cells
setup phase after power supply is available on BTS
again).
-7116
whenBASE
fault affects
STATION basic servicesPROBLEM
SERVICE of the base station
7112
- When fault does not affect basic servicesPROBLEM
BASE STATION CONFIGURATION of the base
station:
stationBASE STATION INFORMATION
7115
7115
- When BASE STATION
due to the fault:
If category
7101 BASEalarms disabled (actCategoryAlarms
STATION/UNIT AUTONOMOUS RESET ==
false)
NOTIFICATION
7652 BASE STATION NOTIFICATION (The radio
module does
If category not support
alarms any cell.)
are disabled (actCategoryAlarms ==
7653
false) CELL FAULTY (The radio module supports a cell.)
7650 BASE STATION FAULTY (The failure in ABIx
does not have any impact on the functionality of any
cell, but after the failure, none of the ABIx's in the BTS
are already operational.)
failure in ABIx does not have any impact on the
functionality of any cell, and at least one ABIx in the
BTS is still operational.)
7652 BASE STATION NOTIFICATION (autonomous
fault does not
If category affect
alarms basic
are services
enabled of the base
(customer station)
configured
7653 CELL FAULTY (The
actCategoryAlarms == true): failure in ABIx makes the cell
disabled.)
If
If category
category alarms
alarms are disabled
false):
7652
7115 BASE
BASE STATION
INFORMATION

false):

7112 BASE STATION CONFIGURATIO PROBLEM

false):
7654 CELLalarms
If category OPERATION DEGRADED
true): 7115 BASE STATION INFORMATION
FALSE): 7655 CELL NOTIFICATION
If
If category
category alarms
false)
7652
7112 BASE
BASE STATION

false):
If category alarms are enabled (actCategoryAlarms ==
7651
true): BASE STATION OPERATION DEGRADED
false):
7652 BASE STATION
true):
false):
-actCategoryAlarms
when no other valid
==reference
true): clock is available:
7112
7108 BASE SERVICE
7114 BASE
CELL STATION PROBLEM
STATION CONFIGURATION
PROBLEM
-If when another

category valid
alarms reference
disabled clock is available:==
(actCategoryAlarms
If category
7115 BASE alarms enabled
STATION (customer
INFORMATION configured
false):
7653
7112 CELL
BASE FAULTY
STATION CONFIGURATION PROBLEM
If category alarms disabled (customer configured
actCategoryAlarms (actCategoryAlarms ==
== false):
false):
7651
WhenBASE STATION
no other OPERATION
valid reference clock DEGRADED
is available;
true):
When another valid reference clock is available:
7115
NOTIFICATION
7108 BASE STATION
(Uncommissioned SYNCHRONIZATION PROBLEM
source)
(always)
7114 CELL SERVICE
(Commissioned source)PROBLEM (always)
If category alarms
NOTIFICATION (inare enabled
case (customer
recovery configured
reset will be triggered)
If category alarms
==disabled
false):
7115 BASE STATION INFORMATION (Platform error
7652
If
when BASE
category STATION
alarms
updating SSH NOTIFICATION
enabled
service (customer configured
account support, basic
(Uncommissioned
actCategoryAlarms
services not affected) source)
== true):
7653
- When CELL
faultFAULTY (Commissioned
is detected source)
and maintained:
-false)
due
7652toBASE
the fault:
STATION NOTIFICATION (Platform error
7101
when BASE STATION/UNIT
updating AUTONOMOUS
SSH service account support) RESET
NOTIFICATION

false):
-If When faultalarms
category is detected and(customer
enabled maintained:
configured
7654 CELL OPERATION
actCategoryAlarms == true): DEGRADED
-AllWhen autonomous recovery reset is being performed
products:
due
7113 BASEfault:
to the STATION ANTENNA LINE PROBLEM
actCategoryAlarms == true):(actCategoryAlarms ==
false):
All products:
All
7113products:
BASE STATION ANTENNA LINE PROBLEM
false):
All products:
All
7115products:
false):
All products:
7655
true): CELL NOTIFICATION
false):
7650 BASE STATION FAULTY (FCT [HW rel.3], FCT
[HW rel.4])
In case of consistent SW after fallback:

7651 BASEalarms
If category STATION OPERATION
enabled DEGRADED
(actCategoryAlarms ==(FCT
true)
[HW rel.3], FCT [HW rel.4])
4085:
false)
If
7650category
BASE alarms
STATION enabled
FAULTY (actCategoryAlarms
(FCT [HW rel.3],== true):
FCT
7651
7107 BASE
BASE OPERATION
STATION DEGRADED
[HW rel.4])
If
If category
actCategoryAlarms
In alarms
alarms disabled
case of consistent
category ==SW
enabledtrue) (actCategoryAlarms
after fallback:configured==
(customer
-false):
when
7651 fault affects
BASE STATION
actCategoryAlarms basic services
== OPERATION
true): of DEGRADED
the base station:(FCT
7651
7116
[HW
7112 BASE
BASE
rel.3], OPERATION
STATION
FCT [HW rel.4]) DEGRADED
SERVICE PROBLEM
station:
7115
false):BASE
Faults: 4082STATION INFORMATION
If
If category
category alarms
alarms are disabled
are enabled (actCategoryAlarms
enabled (customer
(customer configured==
configured
false):
actCategoryAlarms
actCategoryAlarms == true):== true):
7652
7116 BASE
When BASE STATION
fault affects
STATION basicNOTIFICATION
services PROBLEM
SERVICE of the base (Fault
station:
(Uncommissioned
7111 BASE STATION source)
SOFTWARE MANAGEMENT
affect basic services of the base station. The fault may
7654
impactCELL
PROBLEM one orOPERATION
more DSPsDEGRADEDso that inter-site (commissioned
CA isn't
source,
When BER
fault exceeds
does not major
affect BER
basic
supported by those DSPs. Severity= major) threshold)
7655 CELL NOTIFICATION (commissioned source,
station:
BER
7115 exceeds
BASEalarms
If category minor
STATION BER
are threshold
INFORMATION
disabled but less than major
BER
false):threshold)
If
If category
category alarms enabled (customer configured
7654 CELLalarms
actCategoryAlarmsOPERATIONare disabled
== true) DEGRADED (actCategoryAlarms
(fault does not ==
false):
affect basic services of the cell/base station, but fault
7100
7114
In caseBASE
CELLof STATION PROBLEM
SERVICE
inconsistent HARDWARE
SWinter-site PROBLEM (LNA is
after fallback:
impacts
used by one
a DSP, so that
cell) CA isn't supported
7650
by thisBASE
DSP. STATION
Severity =FAULTY
major) (1. FCT [HW rel.3], FCT
7115
If
[HW BASE
category
rel.4], 2.STATION
alarms INFORMATION
disabled
The faulty FSP (LNAto
(actCategoryAlarms
is not mapped is any
not
== used
cell,
If
by category
a cell)If alarms
category enabled
alarms (customer
enabled configured
(customer
false)
and all FSPs in the BTS
actCategoryAlarms == are faulty.)
true)
configured
7653
7651 CELL
BASE actCategoryAlarms
FAULTY
STATION(for Critical==severity)
OPERATION true):
DEGRADED (FSP -
7114
7100 CELL
BASE SERVICE
STATION PROBLEM
HARDWARE
7654faulty
The CELLFSP OPERATION
is not mapped to anyPROBLEM
DEGRADED (forand
cell, at(LNA
Major least is
used by
severity)
one a
other FSPcell) is operational.)
If category
7115 BASE alarms
STATION disabled (actCategoryAlarms ==
7653
false) CELL FAULTY (1.INFORMATION
FSP when faulty (LNAFSPis isnot used
by a
mappedcell) to the cell; 2.(for
TheCritical
faulty severity)
BTS secondary unit
7653 CELL FAULTY
[FCT]
7654 in dualOPERATION
CELL core supports the cell.) (for Major
DEGRADED
If category
7652 BASEalarms
STATION disabled (actCategoryAlarms
NOTIFICATION (The faulty ==BTS
severity)
false):
secondary unit (FCT) in dual core does not support any
7652
cells.)BASE STATION NOTIFICATION (LNA is not used
by a cell)of consistent SW after fallback:
In case
7654
7651 CELL
BASE OPERATION
STATION OPERATION DEGRADED (LNA is used
DEGRADED (FCTby
a cell)
7654 CELLalarms
If category OPERATION DEGRADED
The
actCategoryAlarms == true)unit (FCT) in dual core
faulty BTS secondary
supports
7114 CELL theSERVICE
cell. PROBLEM
If category alarms is enabled (customer configured
false)
7653 CELL FAULTY
If category alarms is disabled (actCategoryAlarms ==
false)
7653 CELL FAULTY== true):
actCategoryAlarms
7654
7115 CELL
BASE OPERATION DEGRADED
STATION INFORMATION

false):
If
If category
category alarms
alarms are disabled
false):
7652
7115 BASE
BASE STATION
INFORMATION
If
If category
category alarms
are enabled ==
false):
7652
7115 BASE
BASE STATION
INFORMATION

false):
71017112BASE
BASESTATION/UNIT
-actCategoryAlarms
STATION AUTONOMOUS
CONFIGURATION
== true) RESET
PROBLEM
NOTIFICATION
(when (when
fault affects
7114 CELL SERVICE basicreset is being performed)
services of the base station)
PROBLEM
- 7115 7115 BASE STATION INFORMATION (when
fault
If does not affect basic services of the base station)
If category
category alarms
false)
true)
If category
7653 CELL alarms
FAULTY are (actCategoryAlarms ==
7114
false) CELL SERVICE PROBLEM
- 7652 BASE STATION NOTIFICATION
(Uncommissioned module) (actCategoryAlarms ==
false)
- 7653 CELL FAULTY (The cell cannot operate because
7653
it doesCELL FAULTY
not have enough available and needed
resources: Tx or Rx.)
- 7654 CELL OPERATION DEGRADED (The cell can
operate in degraded mode because it does have
enough available and needed resources: Tx and Rx.)

- 7114 CELL SERVICE PROBLEM
If category alarms are disabled (customer configured
true)
actCategoryAlarms
7115 BASE STATION == INFORMATION
false)
- 7653 CELL FAULTY
false)
(Radio module
7116 BASE Rx pathSERVICE
STATION mapped to cell)
PROBLEM

false)
7650
7101 BASE
BASE STATION FAULTY
NOTIFICATION (raised only if RESET RECOVERY is
triggered)
(otherwise)

due to the fault:
7101
- WhenBASE
fault STATION/UNIT
is detected and AUTONOMOUS
maintained: RESET
NOTIFICATION
-If When autonomous
category recovery reset is configured
alarms enabled being performed
due to the fault: disabled (customer
false):
7101
- When BASE
fault STATION/UNIT
maintained: RESET
NOTIFICATION
7114
7654 CELL SERVICE OPERATION PROBLEM
DEGRADED
If
to the fault:
false):
7652
-NOTIFICATIONWhen fault STATION
is detectedNOTIFICATION
and maintained:
-If When autonomous
category recovery
alarms disabled reset is being performed
due
false): to the fault:
7652
-If When BASE STATION
faultalarms
is detected NOTIFICATION
and(customer
maintained:
category enabled configured
7654 CELL OPERATION
actCategoryAlarms == true): DEGRADED
-All When autonomous recovery reset is being performed
products:
If category
due to alarms enabled (customer configured
7115 BASEfault:
the
actCategoryAlarms STATION == INFORMATION
true):
If category
All products: alarms are enabled (customer configured
If category
Base alarms
actCategoryAlarms
7116 Station disabled (actCategoryAlarms
== true):Problem
Service (when there== is
-false): When
service impact)fault affects basic services of the base station:
All
7116 products:
BASEalarms
If
7655 category
CELL are enabled
enabled
NOTIFICATION (actCategoryAlarms
-If
true) When fault
category does
alarms not affect
disabled basic services
(actCategoryAlarms of the==base
actCategoryAlarms
station: == true):
false):
-All When fault affects basic services of the base station:
products:
7115
All
7116 BASE
products:
BASE STATION
STATION INFORMATION
SERVICE PROBLEM
7115
-7654 When Base Station
autonomous Notification
recovery (when
reset is there
being isperformed
no service
-impact) CELL OPERATION
When fault does not affect DEGRADED
basic (for of
services affected
the base
due
cells)to the fault:
station:
7101
BASEalarms
STATION AUTONOMOUS RESET
INFORMATION
If category
NOTIFICATION disabled (actCategoryAlarms ==
-false):
due
All to the fault:
products:
If category
7101 BASE alarms are disabled
STATION/UNIT (actCategoryAlarms
AUTONOMOUS RESET==
7655
false): CELL NOTIFICATION
NOTIFICATION
-7650 base station faulty (asik case)
If category
-7651 Basealarms
stationare enabled(when
degraded (customer
faultyconfigured
fsp)
If category alarms
== disabled
true): (actCategoryAlarms ==
-7653
false) Cell Faulty (when cell are affected)
7114
-7652 CELL
Base SERVICE
Station NotifPROBLEM is reportedon when the
7653
cell isCELL FAULTY
not working (The(when
properly failurenoinimpact
FSP [ABIx] cells)
makes
the cell disabled)
7652 BASEalarms
If category STATUIN NOTIFICATION
are disabled (autonomous==
(actCategoryAlarms
recovery
false): reset is being performed due to the fault or
fault does not affect basic services
7653 CELL FAULTY (The cell cannot operate of the basebecause
station) it
does not have enough available and needed resources.)
resources.)

None

false)

-If there are only BTS level counters in the formula, than
the alarming object is MRBTS and reported alarm is:
- when actCategoryAlarms is false
--Ifwhen thereactCategoryAlarms
are only BTS level is true in the formula, than
counters
7115 BASE STATION
the alarming object is MRBTS and reported alarm is: INFORMATION
-If
- when thereactCategoryAlarms
is at least one CELL
is level
false counter in the formula
-7652 whenBASE
actCategoryAlarms is false
7655
--Ifwhen CELL NOTIFICATION
-7115 thereactCategoryAlarms
when are only BTS level is
actCategoryAlarms is
true in the formula, than
counters
true
the BASE
alarming STATION INFORMATION
object is MRBTS and reported alarm is:
7115
-If BASE STATION
thereactCategoryAlarmsINFORMATION
- when is level
-7652 whenBASE
7655
counters
true
the alarming BASE STATION INFORMATION
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the alarmingBASE STATION INFORMATION
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652
whenBASE
- when actCategoryAlarms is true
-7115
whenBASE
actCategoryAlarms is true
STATION INFORMATION
-If there is at least one CELL level counter in the formula
-If there are only BTS level counters in the formula, than
--Ifwhen thereactCategoryAlarms
are only BTS level is true in the formula, than
counters
-If
- when thereactCategoryAlarms
is at least one CELL is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the alarmingBASE STATION INFORMATION
7115
-If BASE STATION
- when is level
-7652 whenBASE
7655
counters
true
the BASE
7115
-If BASE STATION
- when is level
-7652
whenBASE
-7115
whenBASE
actCategoryAlarms is true
STATION INFORMATION
-If there is at least one CELL level counter in the formula
7655 CELLalarms
If category NOTIFICATION
-actCategoryAlarms
when actCategoryAlarms
== true)is true
7115

false)
If category alarms are enabled (actCategoryAlarms is
true) then the BTS raises 7115 BASE STATION
INFORMATION, otherwise legacy alarm 7652 BASE
STATION
If categoryNOTIFICATION
alarms enabled (actCategoryAlarms == true)
If
If category reset
recovery alarmsis disabled
possible:
false) 7653 CELL FAULTY
actCategoryAlarms
If category alarms == true)
are
If
Allcategory are disabled
alarms BASE
products:7101 enabled (actCategoryAlarms
(customer
STATION/UNIT configured==
false)
AUTONOMOUS
7652 RESET NOTIFICATION
7107 BASE
BASE STATION
false)
false):
All products:7652 BASE STATION NOTIFICATION
If recovery reset is not possible: 7116 BASE STATION
SERVICE PROBLEM (actCategoryAlarms == true) or
7650 BASE STATION FAULTY (actCategoryAlarms ==
false)
station
actCategoryAlarms
If category alarms are ==disabled
true): (customer configured
-actCategoryAlarms
When fault is detected and maintained:
== false)
7114
7652 CELL BASE SERVICE
STATION PROBLEM
NOTIFICATION (When no cells
-are
If When autonomous
configured
category arerecovery
on BTS
alarms reset
secondary
enabled is being
unit.)
(customer performed
configured
due to the fault:
7651 BASE STATION
actCategoryAlarms == OPERATION
true): DEGRADED
7101 BASE
(Otherwise)
- When fault STATION/UNIT
maintained: RESET
NOTIFICATION
- When autonomous recovery enabledreset is being
(customer performed
configured
If
due category
to the alarms are disabled
fault: (actCategoryAlarms ==
false):
7101
7115
- When BASE
fault STATION/UNIT
STATION and AUTONOMOUS
is detectedINFORMATION
maintained: RESET
NOTIFICATION
7114
7654 CELL SERVICE
OPERATION PROBLEM
DEGRADED
If
due category alarms are disabled (actCategoryAlarms ==
to the fault:
false):
7652 When fault STATION
-NOTIFICATION is detectedNOTIFICATION
and maintained:
-If When autonomous
category alarms arerecovery
disabledreset is being performed
due to
false): the fault:
7652
- When BASE
fault STATION
is detectedNOTIFICATION
and maintained:
due to the fault:
When the fault affects basic services of the base station:

7114 CELL SERVICE
SERVICE PROBLEM
When
If the fault does not affect basic services of the
category
Small
base Cell: alarms are disabled (actCategoryAlarms ==
station:
true):
7115
7112 BASE
BASE STATION
STATION INFORMATION
actCategoryAlarms == CONFIGURATION
true): PROBLEM
- 7115 BASE STATION INFORMATION
If category
- 7116 BASE alarms are disabled
STATION SERVICE(actCategoryAlarms
PROBLEM ==
false):
7651 BASEalarms
are disabled DEGRADED ==
(actCategoryAlarms
false):
- 7653 CELL FAULTY
- 7654 CELL OPERATION DEGRADED
- 7655 CELL NOTIFICATION

USER

false)
7652 BASEalarms
-true):
when actCategoryAlarms is true
7115
CELL SERVICE INFORMATION
If category alarms are enabled ( actCategoryAlarms ==

true)
false):
7653 CELL FAULTY
false)
7655 CELL
If category NOTIFICATION
alarms are enabled (customer configured
(Radio module Rx path
actCategoryAlarms mapped to cell)
== true):
false):
7653 CELL FAULTY

7220 BASE STATION
7115 BASE STATION SECURITY
INFORMATIONPROBLEM
If
If category
category alarms
alarms are
false):
7652
7115 BASE
BASE STATION
INFORMATION

false)

false)
(uncommissioned FR)
7655 CELL NOTIFICATION (commissioned FR)
Security for the local Ethernet port is disabled:


Direct service login as
actCategoryAlarms == root
true):user is enabled:
7220
7100 BASE STATION HARDWAREPROBLEM
BASE STATION SECURITY PROBLEM
If
If category
category alarms
alarms are
false):
7651
7100 BASE
BASE STATION
HARDWARE PROBLEM
If category alarms are enabled disabled (customer configured==

(actCategoryAlarms
actCategoryAlarms ==enabled
false):
-If
7651 When faultalarms
BASE
category affectsare
OPERATION
enabled ofDEGRADED
the base
(customer station:
configured
7100
7112 BASE
BASE STATION
STATION HARDWARE
PROBLEM
--If When
When faultalarms
fault
category does not
affects affect
basic
are basic
services
enabled
disabled
services of the
of the base
(customer base
station:
configured
station:
7116 BASE
actCategoryAlarmsSTATION SERVICE
== true) PROBLEM
false):
-7653When faultFAULTY
CELL does
affectsnot affect
services of the
of the base base
station:
station:
If
7115category
- When faultalarms
BASE STATION are affect
does not disabled (actCategoryAlarms
INFORMATION
basic services of the base==
-false)
When
station: autonomous recovery reset is being performed
7653
7115toCELL
due FAULTY
the fault:
7652
7101 BASE
BASE STATION
STATION/UNITNOTIFICATION
AUTONOMOUS RESET
NOTIFICATION
false)
If category
7651 BASEalarms
OPERATION (actCategoryAlarms
DEGRADED ==
false)
- When cell cannot operate because it does not have
enough available and needed baseband resources:
7653 CELL FAULTY
- When cell can still operate because it has enough
7115 BASE
available andSTATION INFORMATION
needed baseband resources:
- When fault does not affect basic services of the base
station:

7112 BASE STATION
INFORMATION PROBLEM
If
If category
category alarms
alarms are
are disabled (customer configured
7652
7116 BASE
BASE STATION
SERVICE PROBLEM

false):
5G classical gNB, AirScale SBTS:
7115: BASE_STATION_INFORMATION (when fault
does not affect basic services of the base station/ Minor
severity)
7116: BASE STATION SERVICE PROBLEM (when fault
If category
affects basicalarms are of
services enabled
the base(customer
station/ configured
( actCategoryAlarms
Critical ==
actCategoryAlarms
true)
severity) == true):
- When fault affects
7114 CELL SERVICE basic services of the base station:
PROBLEM
7116 BASE
AirScale SBTS: STATION SERVICE PROBLEM
If category alarms are disableddisabled
((actCategoryAlarms
==
==
Flexi
false)
false) BTS FDD, Flexi BTS TDD, AirScale BTS TDD,
true)
AirScale BTSFAULTY
FDD, Flexi SBTS, AirScale (when SBTS:there is
-7652:
-If 7653
7114 CELL
BASE_STATION_INFORMATION
CELL SERVICE PROBLEM
no cell service mapped to the RMOD/ Minor severity)==
category alarms are disabled (actCategoryAlarms
false):
7650: BASE STATIONdisabled
FAULTY(actCategoryAlarms
(when there is no cell
If
7653category
CELL alarmsare
FAULTY ==
service
false) mapped to the(The cell cannot
RMOD/ Criticaloperate
severity)because it
does not have enough available and needed resources:
-Tx7653 CELL FAULTY
or CELL
Rx.)
7653 FAULTY (when one or more cell/s is/are
7654
mapped CELL OPERATION
to the RMOD, and DEGRADED
the cell does(The
not cell
havecan still
operate because it has enough available and
enough resource to keep service/ Critical severity) needed
7654 CELL OPERATION DEGRADED (when one or
7655
more CELL NOTIFICATION
cell/s is/are mapped to (The cell is not
the RMOD, andimpacted.)
the cell still
has enough resources to keep service (degraded)/
Critical severity)
actCategoryAlarms == true) (when one or more cell/s
is/are mapped to the
All products: 7115 BASE RMOD/ Minor severity)
STATION INFORMATION
If
If category
category alarms
false)
All
All products:
products: 7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
false)
All
All products:
products: 7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
false)
All
BASE STATION NOTIFICATION PROBLEM
CONFIGURATION
If
If category
category alarms
are enabled ==
false)
7653 CELL FAULTY
All products: 7115 BASE STATION INFORMATION
If
If category
category alarms
alarms are
false)
All
7114products: 7652 BASE
CELL SERVICE STATION NOTIFICATION
PROBLEM
If
If category
category alarms
alarms are
false):
7653
7114 CELL
CELL FAULTY
SERVICE PROBLEM

false)
All products:
Flexi BTS FDD,7115 BASE
Flexi BTSSTATION INFORMATION
TDD, AirScale BTS TDD,
AirScale BTS FDD, Flexi SBTS, AirScale SBTS:
If
If category
category alarms
false)
All
All products:
products: 7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
false):
All
All products:
products: 7655
7114 CELL
CELL NOTIFICATION
SERVICE PROBLEM
If
If category
category alarms
false)
All
All products:
products: 7654
7114 CELL
CELL OPERATION DEGRADED
SERVICE PROBLEM
If
If category
category alarms
false)
All
All products:
products: 7654
7115 CELL
BASE OPERATION DEGRADED
STATION INFORMATION
If
If category
category alarms
false)
All
All products:
products: 7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
are enabled == ==
(actCategoryAlarms
false)
true):
All7115
products:
BASE 7655 CELL NOTIFICATION
STATION INFORMATION
If
If category
category alarms
alarms are disabled
false):
71147655 CELL
CELL NOTIFICATION
SERVICE PROBLEM
If
If category
category alarms
are enabled == ==
( actCategoryAlarms
false):
true)
7653 CELL
7115 BASEFAULTY
STATION INFORMATION
If
If category
category alarms
alarms are
are disabled
enabled ((actCategoryAlarms
==
false)
true)
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
alarms are disabled
false)
71157655 CELL
BASE NOTIFICATION
STATION INFORMATION

false)
If category alarms enabled ( actCategoryAlarms == true)
7655 CELL
7115 BASENOTIFICATION.
STATION INFORMATION

false)
7655BASE
7115 CELL STATION
NOTIFICATION
INFORMATION

false)
true)
If
If category
category alarms
alarms are
are disabled
==
false)
true)
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
alarms are
are disabled
==
false)
true)
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category are alarms
alarms disabled ((actCategoryAlarms
are enabled actCategoryAlarms ==
==
false)
true)
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
alarms are
are disabled
==
false)
true)
7655BASE
7115 CELL STATION
NOTIFICATION
INFORMATION
If
If category
category alarms
alarms are
are disabled
==
false)
true)
7655BASE
7115 CELL STATION
NOTIFICATION
INFORMATION
If
If category
category alarms
alarms are
are disabled
==
false)
true):
7655BASE
7115 CELL STATION
NOTIFICATION
INFORMATION
If
If category
category alarms
alarms are
are disabled
==
false):
true)
7655BASE
7115 CELL STATION
NOTIFICATION
INFORMATION
If
If category
category alarms
alarms are
are disabled
==
false)
true)
7655BASE
7115 CELL STATION
NOTIFICATION
INFORMATION
actCategoryAlarmsenabled
If
Allcategory alarms
products: 7107 are
BASEdisabled (actCategoryAlarms
STATION CONNECTIVITY==
actCategoryAlarms
false) == true)
PROBLEM
If
If category
category alarms
alarms disabled
(customer configured==
false)
All
BASE STATION STATION CONNECTIVITY
CONNECTIVITY LOST
DEGRADED
(Transport path [SCTP] for S1 is broken. No other S1
interface available for use.)
7657 BASE STATION
All products: 7107 BASE CONNECTIVITY DEGRADED
STATION CONNECTIVITY
(Transport
PROBLEM path [SCTP] for S1 is broken but there is at
least one other S1 interface available for use.)
false)
All products: 7107 BASE STATION CONNECTIVITY
PROBLEM
DEGRADED
false)
DEGRADED
PROBLEM

false)
All products: 7657 BASE
actCategoryAlarms STATION CONNECTIVITY
== true)
DEGRADED
false)
All products: 7112 BASE STATION CONFIGURATION
PROBLEM
If
If category
category alarms
are enabled ==
false):
All
All products:
products: 7650
CELL SERVICE FAULTY
If
If category
category alarms
alarms are
false)
All
All products:
products: 7653
7114 CELL
CELL FAULTY
SERVICE PROBLEM
If
If category
category alarms
alarms are disabled
false)
All
All products:
products: 7653
7115 CELL
BASE FAULTY
STATION INFORMATION
false)
PROBLEM
If
If category
category alarms
false)
All
All products:
products: 7650 BASE
BASE STATION
7115 enabledSTATION FAULTY
INFORMATION
If category alarms (customer configured
If
Allcategory alarms
products: 7116 disabled (actCategoryAlarms
BASE STATION SERVICE ==
false)
PROBLEM
false)
== true)
DEGRADED
If
If category
category alarms
false)
All
INFORMATION
If
If category
category alarms
false)
7652
7115 BASE
BASE STATION
INFORMATION
If
If category
category alarms
false)
7652
7115 BASE
BASE STATION
INFORMATION

false)
7652 BASE STATION NOTIFICATION"
If
If category
category alarms
are enabled ==
false)
All
All products:
products: 7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
If
If category
category alarms
alarms are
false)
All
All products:
products: 7652
7115 BASE
BASE STATION
INFORMATION
AirScale SBTS, Flexi BTS FDD, Flexi SBTS:
If
If category
category alarms
alarms are
false)
All
All products: 7655BASE
product: 7115 CELLSTATION
NOTIFICATION
INFORMATION
If
If category
category alarms
alarms are disabled
enabled (customer
configured
All
All product:
products:7652
7115BASE
BASESTATION
INFORMATION
If
Allcategory alarms
BASE STATION ==
CONFIGURATION
false)
PROBLEM
All products: 7655 CELL NOTIFICATION
If
If category
category alarms
false)
All
BASE STATION STATION OPERATION
SOFTWARE MANAGEMENT
DEGRADED
PROBLEM
If
Allcategory alarms
BASE STATION ==
CONNECTIVITY
false)
PROBLEM
false)
All products: 7651 BASE STATION OPERATION
PROBLEM
DEGRADED
false)
== true)
DEGRADED
If
If category
category alarms
false)
All
If
If category
category alarms
false)
7651
7112 BASE
BASE STATION
STATION OPERATION
PROBLEM
If
If category
category alarms
false)
7651
7112 BASE
BASE STATION
STATION OPERATION
PROBLEM

false)
NOTIFICATION
When autonomous recovery
actCategoryAlarms == true) reset is not being
performed due to the fault: reset is being performed
- when autonomous recovery
7116 BASE STATION
due to the fault SERVICE PROBLEM
NOTIFICATION
false):
- when autonomous recovery reset is not being
7652 BASEdue
performed SATION
to the NOTIFICATION
fault (autonomous
recovery reset is not being performed
7116 BASE STATION SERVICE PROBLEM due to the fault)
7653 CELL FAULTY
7651 BASEalarms
are disabled DEGRADED ==
(actCategoryAlarms
false)
7650 BASE STATION
true)
7652 BASE STATION
All products: 7112 BASE NOTIFICATION (autonomous
recovery
PROBLEM reset is being performed due to the fault)
If
If category
category alarms
are enabled ==
false)
All
All products:
products: 7653
7115 CELL
BASE FAULTY
STATION INFORMATION
If
If category
category alarms
alarms are disabled
false)
All
BASE STATION NOTIFICATIONPROBLEM
CONNECTIVITY
If category
AirScale BTSalarms
FDD:disabled (actCategoryAlarms ==
false)
If category alarms enabled (actCategoryAlarms == true):
7651
7107 BASE
BASE STATION
STATION OPERATION
CONNECTIVITY DEGRADED
PROBLEM
If
If category
category alarms
false):
7651
7112 BASE
BASE STATION
STATION OPERATION
PROBLEM
If
If category
category alarms
are enabled ==
false)
actCategoryAlarms ==BTS
true)TDD, AirScale BTS TDD,
Flexi
7653 BTS
CELLFDD, Flexi
FAULTY
All products: 7115 BASE STATION
AirScale BTS FDD, Flexi SBTS, INFORMATION
AirScale SBTS:
false)
If
If category
category alarms
false)
If category
7657 BASE alarms enabled
STATION CONNECTIVITY
7107 BASE STATION
actCategoryAlarms CONNECTIVITY PROBLEM
DEGRADEDE3342.== true)
PROBLEM
false)
If category
7657 BASEalarms enabled
STATION (customer configured
CONNECTIVITY
If category alarms
DEGRADEDE3342.
false)
PROBLEM
LOST (No other S1 interface is operational.)
All products:
If category 7657 disabled
alarms BASE STATION CONNECTIVITY
DEGRADED
false) (Another S1 interface is operational.)
LOST (No other S1 interface is operational.)
All products:
If category 7657 enabled
alarms BASE STATION
(customerCONNECTIVITY
configured
DEGRADED (Another S1
actCategoryAlarms == true)interface is operational.)
false)
PROBLEM
false)
PROBLEM
DEGRADED
false)
== true)
DEGRADED
If
If category
category alarms
false)
7652
7115 BASE
BASE STATION
INFORMATION
false)
false)
7657 BASE STATION
actCategoryAlarms == CONNECTIVITY
true):
DEGRADEDED.
If
If category
category alarms
false):
7657 BASE STATION
All products: 7115 BASECONNECTIVITY DEGRADED
STATION INFORMATION
If
If category
category alarms
alarms disabled
== true)
false):
All products: 7655 CELL NOTIFICATION
If
If category
category alarms
alarms disabled
==
false)
true):
71157655 CELL
BASE NOTIFICATION
STATION INFORMATION
(Radio module Rx path mapped to cell)
If
If category
category alarms
alarms disabled
are enabled(actCategoryAlarms ==
false):
7655
BASEalarms
STATION SOFTWARE MANAGEMENT==
If category
(Radio module Rx are
pathenabled
mapped( actCategoryAlarms
to cell)
PROBLEM
true)
7114 CELL SERVICE PROBLEM (with the indication
If
ofcategory alarms
the impacted cellare disabled (actCategoryAlarms
identification and technology type ==
false):
(Wideband or NB-IoT))
7653 CELLalarms
If category FAULTY are disabled (actCategoryAlarms ==
false)
7654 CELL OPERATION DEGRADED (with the
indication
If categoryofalarms
the impacted
enabledcell identification and == true)
(actCategoryAlarms
technology type (Wideband
7115 BASE STATION INFORMATION or NB-IoT))

true)
false)
false)
(Radio module Rx path mapped to cell)
If category
If category alarmsalarms are disabled
false)
- 7112 7655
7115 CELL
BASE
BASE NOTIFICATION
STATION
INFORMATION PROBLEM
5G
(Radio
(when fault affects BTS, AirScale
module Rx BTS
basicFDD,
path mapped AirScale
services toofcell)
the BTSbase TDD,station)
AirScale
-If 7115 SBTS,
BASE Flexi BTS
STATION FDD, Flexi BTS
INFORMATION TDD,fault
(when Flexi
SBTS: category alarms disabled (actCategoryAlarms ==
does
false) not affect basic services of the base station)
actCategoryAlarms 7655 CELL NOTIFICATION == true)
If
(Radio categorymodule alarms Rx are
pathdisabled
mapped(actCategoryAlarms
to cell) ==
7115
- 7652 BASE STATION NOTIFICATION (faulty object
If
doesn't category impactalarmsanyarecell)disabled (actCategoryAlarms ==
false)
-If 7653 CELL FAULTY (The cell(customer
cannot operate because
7652 category alarms are enabled configured
doesBASE
itactCategoryAlarms not haveSTATION enough NOTIFICATION
== true) available and needed
resources:
7115 BASETx or Rx.) INFORMATION
STATION
- 7654 CELL OPERATION DEGRADED (The cell can
still
If category operatealarms because areit disabled
has enough available and
needed
false) resources: both Tx and Rx.)
-If when fault affects basic services
category alarms are enabled (customer configured of the base station
7652
7116
actCategoryAlarms BASE STATION NOTIFICATION
SERVICE
true) FlexiPROBLEM
==SBTS, (1.FSM. 2.FSP
Flexi
-or FBB
whenSBTS,
is
faultnot AirScale
mapped
does not to
affectany cell)
basic BTS FDD,
services of Flexi
the BTS
base
-TDD,
If when
categoryfaultalarms
AirScale affects basic
TDD, services
BTSenabled (customer
AirScale of
BTS the base
configured
FDD: station:
7655
station
7116 CELL
BASEalarms NOTIFICATION
STATION (FSP or FBB is mapped to
actCategoryAlarms
If category == SERVICE
enabledtrue)(customer PROBLEM configured
the
7115 cell)
-actCategoryAlarms
when fault affects basic == services of the base station
true):
-7116
If when
categoryautonomous
BASE alarms
STATION arerecovery
disabled
SERVICE reset is being performed
(actCategoryAlarms
PROBLEM ==
7115
due
Flexi toBASE
the
SBTS, STATION
fault
AirScale INFORMATION
false):
-If when fault does not affect basic services of the base
7101 category
BASE alarms are enabled
STATION/UNIT (customer configured
AUTONOMOUS
TDD:
7654
station
If CELLalarms
category OPERATION disabled DEGRADED (FaultyRESETDSP is
actCategoryAlarms
NOTIFICATION
If
used
7115 category
to
BASE alarms
process
STATION
==
enabled
affected
true) (customer configured==
(actCategoryAlarms
cell)
INFORMATION
-false): when fault affects basic
actCategoryAlarms == services of the base station
true):
-7652 whenBASE
7116 autonomous
BASE STATION
STATION recovery
NOTIFICATION
SERVICE resetPROBLEM
is being(The performed
affected
Flexi
7115
due BTS
toBASE
the FDD,
STATION
fault Flexi BTS TDD, AirScale
INFORMATION BTS TDD,
Flexi
DSP
-AirScale
whenSBTS,
in fault
FSPBTS AirScale
orFDD,
does FBBnot SBTS,
oraffect
FlexiABIxSBTS, Flexi
is not
basic BTS FDD,
mappedSBTS:
services
AirScale toFlexi
of anybase
the BTS
cell.)
If
7101
TDD, category
BASE
AirScale alarmsare
STATION/UNIT
BTS TDD,enabled (customer
AUTONOMOUS
AirScale BTS configured
FDD: RESET
7655
station
If CELLalarms
category NOTIFICATION
are (The affected DSP in FSP
actCategoryAlarms
NOTIFICATION
If category alarms ==disabled
disabled
enabledtrue)(customer (actCategoryAlarms
(actCategoryAlarms configured==
==
or
7115
false) FBB or
BASE ABIx is
STATION mapped to
INFORMATION any cell.)
-false):
-actCategoryAlarms
7650 whenBASEautonomous
STATION == true):
recovery
FAULTY reset is failure
being performed
7652
7116
Flexi
7115
due
BASE
BTS
toBASE
the
STATION
FDD,
STATION
fault Flexi SERVICE
BTS TDD, (The
NOTIFICATION
INFORMATION PROBLEM
AirScale (TheBTSin FSP
TDD,or
affected
-ABIx
DSP when
AirScaledoes
in FSP
fault notor
does have
FBBnot
BTSSTATION/UNIT any
or impact
ABIx
affect
FDD, Flexi SBTS, is on
not
basic the
mapped
services functionality
AirScale SBTS: to
of any
the of
cell.)
base
7101
any
7655
station BASE
cell,
CELL but after the
NOTIFICATION failure, AUTONOMOUS
all
(The FSPs
affected or ABIx's
DSP RESET
in the
FSP
NOTIFICATION
BTS
or
7115 FBB
false) are ornot
BASE ABIxoperational.)
is mapped
STATION to any cell.)
INFORMATION
false):
7651 BASE STATION OPERATION
-7650
when
7652 autonomous
BASE STATION recovery
FAULTY
NOTIFICATION reset
(The isDEGRADED
being
failure
(The performed
in FSP
affected
(The
or
Flexi
failureBTS
due toin in
the FDD,
FSP
fault or Flexi
ABIx BTS
does TDD,
not AirScale
have any BTS
impact TDD,
on the
ABIx
DSP does
AirScale FSP, not have
FBB,
BTSSTATION/UNIT
FDD, orany
ABIx
Flexiandimpact
is
SBTS, not on the
mapped
AirScale functionality
to
SBTS:any of
cell.)
functionality
7101
any BASE
cell, of
butalarms any
after the cell, at least
AUTONOMOUS one FSP or ABIx
RESET in
7655
If
the CELL
category
BTS
NOTIFICATION is still arefailure,
NOTIFICATION disabled
operational.)
all (actCategoryAlarms
(The FSPs
affected or ABIx's
DSP in the FSP,
==
BTS
FBB,
false) are
or already
ABIx not operational.)
is mapped to any cell.) (autonomous
7652
7651 BASE
BASE STATION
OPERATION DEGRADED (The
7650
recovery
Flexi BASE
BTS STATION
reset
FDD, isFlexi
beingBTSFAULTY
performed
TDD, (Thedueany
AirScale failure
to theBTSinfault
FSP
TDD, oror
failure
ABIx in
does FSP or
notFDD, ABIx
have Flexi
anydoesimpactnot have
on the impact
functionality on the
of
fault does
AirScale
functionality BTSnotof affect
any basic
cell, and services
SBTS, at ofone
AirScale
least the base
SBTS:
FSP orstation)
ABIx
any
7653
If cell,
CELL
category butalarms
after the
FAULTY failure,
are(The all (actCategoryAlarms
failure
disabled FSPs
in FSP or or
ABIx's the==in
ABIxinmakes
the
BTS BTS is
areisnot still operational.)
operational.)
the
7652 cell
false) BASE disabled.)
STATION NOTIFICATION (autonomous
7651
7650 BASE
BASE STATION
STATION OPERATION
failure infault
FSPor(The
or
recovery
failure in reset
FSP is
or being
ABIx performed
does not have due anyto the
impact on the
ABIx
fault does not
does not affect
have anybasic impact
services on theof functionality
the base of
station)
functionality
any cell, of
butFAULTY any cell,
after the (The and
failure, at least
all FSPs one FSP
or or
ABIx's or ABIx
the in
7653
the BTSCELL is still operational.) failure in FSP ABIxinmakes
BTS
the areisnot
cell operational.)
disabled.)
7652
7651 BASE
BASE STATION
OPERATION DEGRADED (autonomous (The
recovery
failure in FSP or ABIx does not have any the
reset is being performed due to impactfaultonorthe
fault does notofaffect
functionality basic
any cell, and services
at leastofone theFSPbaseorstation)
ABIx in
7653 CELL FAULTY
the BTS is still operational.) (The failure in FSP or ABIx makes
the
7652 cell
BASEis disabled.)
STATION NOTIFICATION (autonomous
fault does not affect basic services of the base station)
7653 CELL FAULTY (The failure in FSP or ABIx makes
- When failure in FSP or ABIx does not have any impact
on the functionality of any cell, and at least one FSP or
ABIx in the BTS is still operational:
due to the fault or fault does not affect basic services of
the base station
If
7652 category
BASEalarms
STATIONenabled (customer configured
NOTIFICATION
If category alarms
actCategoryAlarms enabled (customer configured
==ortrue)
-actCategoryAlarms
When failure in FSP == ABIx
true) makes the cell disabled:
-7653
whenCELL
fault FAULTY
7115
7116 BASE
BASE STATION
STATION INFORMATION
SERVICE PROBLEM
If
duecategory alarms disabled (actCategoryAlarms ==
to the fault
false)
NOTIFICATION
If
If category
category alarms
false)
7652
CELL SERVICE NOTIFICATION
If
If category
category alarms
false)
7653
7112 CELL
BASE FAULTY
STATION CONFIGURATION PROBLEM
If
If category
category alarms
false)
7651
CELL SERVICE OPERATION DEGRADED
If
If category
category alarms
false)
7654
7114 CELL
SERVICE PROBLEM
If
If category
category alarms
false)
7653
7114 CELL
CELL FAULTY
SERVICE PROBLEM
If
If category
category alarms
false)
7653
7114 CELL
CELL FAULTY
SERVICE PROBLEM
If
If category
category alarms
false)
7653
7108 CELL
BASE FAULTY
STATION SYNCHRONIZATION PROBLEM
If
If category
category alarms
false)
7651
7115 BASE
BASE STATION
STATION OPERATION
INFORMATION DEGRADED
AirScale BTS TDD:

If
If category
category alarms
are enabled ==
false)
7652
7116 BASE
BASE STATION
SERVICE PROBLEM
AirScale BTS TDD:
If
If category
category alarms
alarms are
false):
7653
7116 CELL
BASE FAULTY

false)
7653 CELL FAULTY
AirScale BTS TDD:
AirScale BTS TDD:
If
If category
category alarms
alarms are
false):
7653
7116 CELL
BASE FAULTY
AirScale BTS TDD:
If
If category
category alarms
alarms are
false):
7653
7116 CELL
BASE FAULTY
AirScale BTS TDD:
If
If category
category alarms
alarms are
false):
7653
7116 CELL
BASE FAULTY
AirScale BTS TDD:
If
If category
category alarms
alarms are
false):
7653
7116 CELL
BASE FAULTY
AirScale BTS TDD:
If
If category
category alarms
alarms are
false):
7653
7115 CELL
BASE FAULTY
STATION INFORMATION
AirScale BTS TDD:
If
If category
category alarms
alarms are disabled (actCategoryAlarms ==
AirScale
false): BTS TDD:are enabled (customer configured
actCategoryAlarms
If category alarms ==enabled
are true): (customer configured
7655
7115 CELL
BASE NOTIFICATION
STATION INFORMATION
- 7107 BASE STATION CONNECTIVITY PROBLEM
If category
- 7115 BASEalarms are disabled
STATION (actCategoryAlarms ==
INFORMATION
false):
AirScale
7655 BTS
CELL TDD:
NOTIFICATION
If
If category
category alarms
alarms are
false):
-7116
7653BASE
CELLSTATION
FAULTY SERVICE PROBLEM
-7115
7654BASE
CELLSTATION
OPERATION DEGRADED
INFORMATION
- 7655 CELL NOTIFICATION
false):
7653 CELL FAULTY== true):
actCategoryAlarms
7655
7114 CELL
CELL NOTIFICATION
SERVICE PROBLEM
If
If category
category alarms
false):
7654
7114 CELL
SERVICE PROBLEM
If
If category
category alarms
false):
7653
7114 CELL FAULTY
CELLalarms
SERVICE PROBLEM
If
Allcategory alarms
BASE STATION CONNECTIVITY==
false):
PROBLEM
7653 CELL FAULTY
false)
DEGRADED
PROBLEM
false)
PROBLEM
DEGRADED
false)
== true)
DEGRADED
If
If category
category alarms
false)
All
All products:
products: 7652
7115 BASE
Flexi BTS FDD, Flexi BTSSTATION INFORMATION
If
If category
category alarms
false)
All
7115products:
BASE 7652 BASE
STATION STATION NOTIFICATION
INFORMATION
If
If category
category alarmsalarms disabled (actCategoryAlarms
false):
If category alarms
actCategoryAlarms == true): enabled (customer configured
7652 BASE
7115 BASE STATION INFORMATION == NOTIFICATION
true):
- When fault affects basic services of the base station :
7116
If BASEalarms
category STATION SERVICE
disabled PROBLEM
-If category
When
false): faultalarms
does are affect
not enabled (customer
basic servicesconfigured
of the base
actCategoryAlarms
station: == true)
7652
All BASE STATION
products: 7115 BASE NOTIFICATION
STATION INFORMATION
If category alarms
- When autonomous recovery enabled (customer
reset is configured
being performed
If
due category
actCategoryAlarms
to the alarms
fault: are
== disabled
If category alarms enabled (customer true): (actCategoryAlarms
configured ==
false)
-7101when fault
BASE affects basic
STATION/UNIT
actCategoryAlarms == true): services of
AUTONOMOUS the base station:
RESET
All
7116 products:
BASE 7652 BASE
BASE STATION
NOTIFICATION
7115 STATION STATION
SERVICE
INFORMATION NOTIFICATION
PROBLEM
station:
If
7115category
false): BASEalarmsSTATION enabled (customer configured
INFORMATION
actCategoryAlarms
-7650
whenBASE autonomous
STATION == true):
recovery
FAULTY reset
(Theis failure
being performed
in FSP or
7652
INFORMATION
due
ABIxtodoes the fault:
not have any impact on the functionality of
7101
any cell,BASE but STATION/UNIT
after the failure, AUTONOMOUS
all FSPs or ABIx's RESET
in the
If category
NOTIFICATION alarms disabled
BTS are already not operational) (actCategoryAlarms ==
false):
7652
If
failure BASE
category
in FSP STATION
alarms NOTIFICATION
disabled
or ABIx does (actCategoryAlarms
not have any impact == on the
false):
functionality of any cell, and at least one FSP or ABIx in
If category
7650 BASE alarms
STATION enabled
FAULTY(customer configured
(The failure in FSP or
the BTS is
actCategoryAlarms still operational)
== true)
ABIx
7653
If does
CELL
category not
alarmshaveenabled
FAULTY any
(The impact
failure in FSP
(customer or ABIx makes
configured
7111
on the BASE STATION
functionality of SOFTWARE
any MANAGEMENT
cell, but after the failure, all
the cell is disabled)
actCategoryAlarms
PROBLEM == true):
FSPs
When or ABIx's
fault affects basic services of the base station:
in
7100the BTS are
BASEalarms already HARDWARE
STATION not operational.) PROBLEM ==
If category
7651 BASE STATION disabled (actCategoryAlarms
OPERATION DEGRADED (The
When
false) fault does not affect basic services of the base
failure
station: in FSP or ABIx does not have
7651
any BASEon STATION OPERATION of anyDEGRADED
7115impact
BASE STATION the functionality
INFORMATION cell, and at least
one FSP or ABIx in
the BTS is still
If category alarmsoperational.)
7653
false): CELL FAULTY (The failure in FSP or ABIx makes
(1.FCT; 2.The failure in FSP or FBBx or ABIx does not
have any impact on the functionality of any cell.)
7654 CELL OPERATION DEGRADED (The failure in
FSP or FBBx or ABIx makes the cell is degraded.)
-When whenfaultfaultdoesaffects notbasic
affectservices of the base
basic services of the station
base
7116
station: BASE STATION SERVICE PROBLEM
-7115 whenBASE fault does
STATION not affect basic services of the base
INFORMATION
station
7115
If category BASEalarms STATION INFORMATION
-false): when autonomous recovery reset is being performed
If
due category
toBASE alarms enabled (customer configured
the fault
7651
actCategoryAlarms STATION == OPERATION
true): AUTONOMOUS DEGRADED
7101
(1.FCT; BASE STATION/UNIT RESET
If
7115
NOTIFICATION BASE STATION INFORMATIONor ABIx
category 2.Thealarmsfailureare in FSP
enabled or FBBx
(customer does not
configured
have any impact on ==
actCategoryAlarms thetrue):
functionality of any cell.)
7654
-If When
If CELL
category OPERATION
faultalarms
affectsdisabled
basic DEGRADED
services of the
(actCategoryAlarms (The
base failure
== in==
station
FSP category
or FBBx alarms
or ABIxare enabled
disabled
makes the(customer
cell is configured
(actCategoryAlarms
degraded.)
7100
false):
actCategoryAlarms BASE STATION == HARDWARE
true): PROBLEM
false)
-7652 When fault does not affect basic services of the base or
-Flexi When BASE
BTS fault
FDD,STATION
affects
Flexibasic NOTIFICATION
BTSservices
TDD, AirScaleof the (1.FCT;
base
BTS FDD, 2.FSP
station:
station
FBB
7100 BASE or ABIX is not mapped to any cell.)
AirScale
7115 BASE BTSSTATION
TDD:
STATION
HARDWARE PROBLEM
INFORMATION
-7655
7650
If category When CELL
BASEfault NOTIFICATION
does
STATION
alarms not affect
FAULTY
are enabled
(FSP
basic or FBB
services
(After
(customer
orofABIX
the all
the configured
failure, is
base
mapped
station:
FSPs to
or ABIx's the cell.)
in the
actCategoryAlarms
If category alarms ==BTS
are true):
disabled are already not operational.)
7115
7651
-false) When BASEfault STATION
affects basic INFORMATION
OPERATION
services ofDEGRADEDthe base station: (At
least
7100
7650 one
BASE FSP or ABIx HARDWARE
STATION in the BTS
FAULTY is still
(The operational.)
PROBLEM
faulty FSP is not
If
7653
-mapped category
CELL
When fault alarms
FAULTY
does are
not disabled
(The
affect failure (actCategoryAlarms
basic inin FSP
services or of
ABIxthefaulty)
base ==
false): to any cell, and all FSPs the BTS are
disables
station:
7651 BASE the cell.)
STATION OPERATION
If
7653
7115
category
CELL
BASE
alarms
FAULTY
STATION
enabled
(The cell
INFORMATION cannotDEGRADED
operate because (The it
faulty
actCategoryAlarmsFSP is not mapped
== to
true)
does not have enough available and needed resources: any cell, and at least one
-other
Tx when FSP
or Rx.)faultisaffects
operational)basic services of the base station
If
7653
All category
CELL
products: alarms
FAULTY
7116 are enabled
disabled
(The
BASE faulty(customer
STATION FSPSERVICE configured
(actCategoryAlarms
is (The
mapped to the==
7654 CELL OPERATION
actCategoryAlarms
false): == DEGRADED
true): cell can still
cell)
PROBLEM
If
--7653 category
When fault alarms
affects enabled
basic (customer
services of configured
the base station
needed whenCELL
actCategoryAlarmsfault FAULTY
does not
resources:
(The cell
==affect
both Tx and
true)
cannot
basic operate
services
Rx.) of thebecause
base it
7112
does
station BASE
not have STATION
enough CONFIGURATION
available and needed PROBLEM
resources:
-7652
Tx when
When BASE
or BTS fault
Rx.)fault STATION
affects
does basic
not NOTIFICATION
affect services of the(The
basicAirScale
services offaulty
base SFP
station
the base
Flexi
works
All on
products: FDD,
optical
7116 FlexiBASEBTS
interface TDD,
that
STATION is not used
SERVICE BTS
to FDD,
provide
station
7654
AirScale CELL BTS OPERATION
TDD: 7115 DEGRADED
BASE STATION (The cell can still
transmission
PROBLEM
7115
operate BASE because for
STATIONany
it cell.)
still INFORMATION
has enough available and
If category
INFORMATION alarms enabled (customer configured
-actCategoryAlarms
when fault does not affect basicRx.) services of the base
-needed
when
station
resources:
autonomous both
== Tx and
true)
If
7652
-due category
when BASE
toBTS alarms
STATION
faultfault
the affects are disabled
basicNOTIFICATION
services (actCategoryAlarms
of the(Thebase faulty SFP
station ==
If category
Flexi
false) alarms
FDD, are
Flexi enabled
BTS TDD, (customer
AirScale configured
BTS FDD,
works
All on
products:
actCategoryAlarmsoptical
7116
7101 interface
BASE
== that
STATION is
STATION/UNIT
true): not used
SERVICE to provide
AirScale
7650
PROBLEM BASE
transmission BTSSTATION
TDD:
for any 7115 BASE (1.
FAULTY
cell.) STATION
failure in SMOD; 2.
AUTONOMOUS
7100:
INFORMATIONBase Station RESETHardware NOTIFICATION
Problem
the failure in BBMOD that
- when fault does not affect basic services does not have any impact
of the base on
-thewhen
station autonomous
functionality of recovery
any cell, butreset
after is being
the performed
failure, all
If
duecategory
toBTS
thein alarms disabled
fault arearedisabled (actCategoryAlarms
(actCategoryAlarms == ==
BBMODs
Flexi
false) FDD,the BTSFlexi BTS faulty)
TDD, AirScale BTS FDD,
false):
All
7651 products:
BASE 7101
STATION BASE STATION/UNIT
OPERATION DEGRADED (the
AirScale
Flexi
7650: BTS
Base BTS
FDD, TDD:
StationFlexi 7115
BTS
Faulty BASE
TDD, STATION
AirScale BTS FDD,
AUTONOMOUS
failure in
INFORMATION BBMOD RESET
does NOTIFICATION
not have any impact on the
AirScale BTS TDD:
functionality
- whenBASE
7650 of any cell,
autonomous
STATION and atreset
recovery
FAULTY least isone
(after theother
being BBMOD
performed
failure, all
If
in
duecategory
the BTS
toorthe alarms
is
faultstill disabled
operational) (actCategoryAlarms ==
FSPs
false) ABIx's
7653
All
in the CELL
products:
BTSFDD, FAULTY
are7101already (the
BASE failure
notSTATION/UNIT in the BBMOD makes
operational)
Flexi
cell BTS
disabled)
AUTONOMOUS Flexi
RESET BTS TDD,
NOTIFICATION AirScale BTS FDD,
7651
TDD: OPERATION DEGRADED (at
least
7650 one
BASE FSP or ABIx FAULTY
STATION in (After the failure,== all
If
thecategory
BTS is alarms
still disabled (actCategoryAlarms
operational)
FSPs
false) or ABIx's
7653
in CELL
theBTSBTSFDD, FAULTY
are already (Thenot failure in FSP or ABIx makes
operational.)
Flexi
the cell is disabled.) Flexi BTS TDD, AirScale BTS FDD,
7651
TDD: OPERATION DEGRADED (At
least one FSP
7650 BASE STATION FAULTY or ABIx in (After the failure, all
the BTS
FSPs or ABIx's is still operational.)
7653
in the CELL
BTS are FAULTY
already (Thenot failure in FSP or ABIx
operational.)
disables the cell.)
7651 BASE STATION OPERATION DEGRADED (At
least one FSP or ABIx in
7653 CELL FAULTY (The failure in FSP or ABIx
disables the cell.)


A fault (or faults) has (have) occurred in the base station
Check the reason for the fault from the supplementary
text field of the alarm.
A fault has occurred in BASE STATION
CONNECTIVITY PROBLEM At
MRBTS/NRBTS/X2linkSupervisionTmr expiry which is
started when the x2LinkStatus goes from "available" to
"unavailable" for an LTEENB.

Check the reason
7101 RESET for the fault from
NOTIFICATION (whenthe supplementary
reset is being
text field
performed) of the alarm.

When autonomous recovery reset is not performed due

to the fault:
When
When autonomous
autonomous recovery
recovery reset
reset is
is being performed
not performed due
due to the fault:
to the fault:
7101
7107 BASE
BASE STATION/UNIT AUTONOMOUS
STATION CONNECTIVITY RESET
PROBLEM
NOTIFICATION
due to the fault:
NOTIFICATION
None
None
None
None
None
None
None
None
category does not affect(customer
configured
station:
None
7115
- When BASE
If category
- When faultalarms disabled
base
false):
station:
-7115When fault STATION
BASE affects basic services of the base station:
INFORMATION
category does not affect(actCategoryAlarms
disabled basic services of the==
base
station:
false):
7652
- When BASE
- When fault does not affect basic services of the base
station:
None

true):
None

false):
None
None
None
None
None
None
None
None
None
None
None
None
None
None

None
7107 BASEalarms
STATION CONNECTIVITY PROBLEM
If
Allcategory alarms
BASE STATION ==
CONNECTIVITY
false)
PROBLEM
7657 BASE STATION CONNECTIVITY DEGRADED.
false)
== true)
DEGRADED
7107 BASEalarms
STATION CONNECTIVITY PROBLEM
If
Allcategory alarms
BASE STATION CONNECTIVITY==
false)
PROBLEM
false)
== true)
DEGRADED

false)
TBD
or cancels) points to instability in the transmission network,
not to a fault in the unit.
4. After the fault situation has been cleared, you might

need to tune the BTS master clock because the BTS
master clock adjustment is quite slow. You can perform the
tuning:
- manually by changing the DAC word (during a site visit).
- with fast tuning, in which the BTS master clock is tuned in

a few minutes automatically near the Iub reference (normal
Instructions
tuning takes Related Faults
To clear this care
fault,of the finethe
perform tuning).
following steps:
Note,
5G BTS:however, that you should only use the fast tuning in
case the Iub reference
1. Make sure signal is
that the module is known toconnected.
properly be a good one.
Check
Otherwise, the BTS
the alarming module. frequency might be tuned into a totally
incorrect value,
Note: Fault causing on
10 detected serious
radioproblems in the
module can be network
a
performance.
consequence of baseband module power off. Check if the
baseband module(s) on which radio is connected is(are)
Background
Check theon. information:
active The principle
fan alarms airisflow
thatofinthe
the mobile
powered
Flexi SBTS,
network, the AirScale SBTS, and
synchronization Flexi
goes
the
Zone
from Micro,
S1 FlexiBTS.
interface, Zone
but in
Temperature alarm
2. Check the fault history.
Controller:
reality, that chain might be broken somewhere and, for
1. Download
example, when theusing
BTS leased
SW again.
lines,TDD,
the BTS mightSBTS,
take the
AirScale
2. Reset BTS
(block FDD,
and AirScale
unblock) BTS
thetheBTS. AirScale BTS internal SW management problem,Failure in
reference
Flexi synchronization
BTS2FDD, from transmission
SBTS: module. ofnetwork
3. If step
another does Flexi
operator. not
This
BTSreplace
help, TDD, Flexi
does not the alarming
harm the system Ifif the the replaceable baseband unit
1. Ensure that the module is properly connected.
synchronization of the leased line service provider
module LED does not light up, the module is faulty. Check is also
accurate or stable enough. The
the module that is causing the alarm. BTS uses the incoming
synchronization signal asona radio
Note: Fault 10 detected reference
modulefor can
the Air
be interface,
a
the accuracy requirement of which is set
consequence of baseband module power off. Check if the by 3GPP.
baseband module(s) on which radio is connected is(are)
powered on. Antenna Line Device failure,Failure in optical
2.
1. Check
Block and the unblock
fault history.
the BTS. interface,Failure in replaceable baseband
3. Retry IPSec connection or use unsecured connection unit,System Module failure
2. Perform
Note: a power-off
perform the stepsreset.
bellow in the listed order until the
fault
1. disappear:
3. Block/lock or unblock/unlock
If steps 1 and the module
2 do not help, replace that is causing
the module that is
the alarm.
causing the alarm. Configuration error: <x>
1. Perform WCDMA RAT Reset.
2.
2. If the faultthe
Replace condition
module persists after the RAT Reset, restart
Note:
the BTS.Perform the stepsthatin theis causing the
listed order alarm.
until the fault is
resolved.
3.
3. Save
In case thefault
snapshot, it should
16 is related containRMOD,
to eCPRI all necessary
check thelogs
to be analyzed.
stability
1. Resetofthe theWCDMA
eCPRI syncSW. master of the RMOD.
5G BTS:
Note:
4.
An In Perform
case
automatic faultthe
SW steps
16 update inisthe
is raised to listed order
eCPRI
ongoing. RMOD until thecanceled
check fault
that is
2. Check
resolved. the transmission links to theFault
RNC.will be
configured CABLINK
after SW update is finished.between BTS (BBMOD or SMOD) Failure in replaceable baseband unit,System
and
NOTE:
3. RMOD
Check matches
If the fault to the real HW connection
BTS 10:EFaultId_NoConnectionToUnitAl
and SW.
RNC transmission settings. setup. is Module failure
1. Reset the WCDMA
also active on the source unit, then the SW update must be
postponed
4. Reset until the fault
2. Check the the SBTS.
transmission links to theisRNC.
10:EFaultId_NoConnectionToUnitAl canceled.
5.
3. Replace
Check the System Module.
Flexi BTSthe BTS
TDD, and RNC
AirScale BTS transmission
TDD, Flexi settings.
BTS FDD,
4. Resetthe
Update theBTS
SBTS.with the compatible SW (check the SW
versions to see the active SW version and update the
5. Replace
active the System
SW version) unlessModule.
it is automatically updated by
NetAct.
In case of RF modules with factory SW loaded, SW update

is a mandatory step.
Update
5G BTS,toAirScale
a compatible SW ofAirScale
BTS FDD, the BTSBTS (check
TDD,theAirScale
SW
versions
SBTS, Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS:the
to see the active SW version, and update
active
Note: SW version)
Perform unless
the steps in itthe
is automatically updated
listed order until by is
the fault the
5G BTS:
NetAct.
resolved.
Retry the SW update.
1. Retry the file update for a few times.
2. Check BTS
AirScale the FTP
FDD,account
AirScaleuser BTS settings.
TDD, AirScale SBTS,
3. Check the file and path names.
4. Check
Note: the administration
Perform the steps in the loglisted
on the file server.
order until the fault is
resolved.
1.
5GRetry
BTS,the SW update.
AirScale BTS FDD, AirScale BTS TDD, AirScale
2.
SBTS, Flexi BTS FDD,and
Save the snapshot check
Flexi BTSthe
TDD,download status from
Flexi SBTS:
the BTS SWDL report in the snapshot file.
Take the following steps to resolve the fault: BTS internal SW management problem
1. Retry the SW update.
2.
5GIfBTS,
otherAirScale
flash memory-related faults are
BTS FDD, AirScale BTSactive
TDD,for the
AirScale
alarming module at the same time, replace the
SBTS, Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS: alarming
module.
Take the following steps to resolve the fault:
1. Retry the SW update.
2. If other flash memory-related faults are active for the
alarming module at the same time, replace the alarming
module.
Check the main power supply of the base station.
Unblock the cell to cancel the fault.

Note: Perform the steps in the listed order until the fault is
resolved.
Unblock
1. Checkthe
theBTS to cancel the(pre-configuration
cell parameters fault. Unblockingunder
the BTS
causes configuration
private a BTS reset. data) in the RNC and the BTS.
2. If thethe
Check parameters configured
fault history toactive
and other the RNC areofcorrect,
faults the unit.lock
and unlock all cells of this BTS. Use the BTS element
manager
Note: Thistofault
trigger
doesparameter sending
not require from theactions.
any (special) RNC to the
BTS again.
1.
3. Reset the alarming
If the parameters unit or module.
configured to the RNC are incorrect,
2. Remove or reinsert the alarming
lock the cells and configure unit or module.
the parameters to the correct Failure in replaceable baseband unit,System
3. Replace the alarming unit or module.
values. Afterwards, unlock the cells. Module failure
4. If the default values for the cell parameters (such as

rampdown time/step) are not appropriate in the BTS,
reconfigure the BTS.

AirScale BTS FDD, Flexi SBTS, AirScale SBTS: Configuration error: <x>,Failure in replaceable
Replace the alarming unit or module. baseband unit
1. Upgrade the system module SW.

Configuration error: <x>,Failure in replaceable
2. Replace the unit. baseband unit
use.
Note: Check
Perform thethe configuration
steps in thepictures listed order of cabling
until the andfault is
investigations.
devices installed.
resolved.
Note: Use the fault-specific troubleshooting instructions
2.
from REMOTE
NOLS;" INVESTIGATIONS
RX Signal levelunit. trouble shooting" document
1.
Check Reset if the alarming
anything hasfor radio
changed
as detailed guidance remoteinand thesite-specific
system, and what
triggered
investigations. the alarm.
2.
- SW If the fault is configuration,
updates, reported again, replace the optical
commissioning or carrier cables
and
power SFPs used
changes, to connect the alarming
RF sharing activation or HW unit swap. radio module to Ifthe
2.
system REMOTE INVESTIGATIONS
module/extension baseband module.
the
Check alarm appeared
if anything has after
changedany changes,
in the system, return to and the what
previous
Note:
triggered status
Performthe is the
alarm.if possible,
steps in and
the see
listed if the
order problem
until the fault is
3.
disappeared.
resolved. If the fault reported again, replace the alarming radio
-module SW updates, hardware. configuration, commissioning or carrier
-power Checkchanges,if the alarm RF depends
sharing on traffic,orcompared
activation HW unit swap.to similar
If
Too
cases
1. low
WCDMA in Tx signal
network,
RAT level
and
reset. howmeasured
often in radio
the problem module occurs may be
(single
the
detected alarm appeared
due to failure afterof anyany changes,
unit return
on theantenna to
path between the the
case,
2.
previous BTSone of few).
reset.
status If there
if possible, are
and anyseeother ifand
the the
problem line device
tx
or
3. antenna
RFM-related
Check line port on radio module
alarms, the root cause can be an external
the commissioning. DSP. Execute
disappeared.
the followingthe actions to recover
one.
4.
-sequence: Replace
Check if the alarm affected depends HW. onthe fault in the presented
traffic, compared to similar
-cases If anyinother network,active alarm
and radio occurs,
how often follow the instructions of
1.
the Reset the alarming
particular alarm. unit. the problem occurs (single
case,
2. one of few). has
If previous If there areexecuted any other antenna isline device
Note: Performstep the stepsbeen in the listed order and fault the
until reported
fault is
or
again, RFM-related alarms,
reset the BTS STATUS INVESTIGATIONSthe root cause can be an external
resolved.
3. COMMISSIONING
one.
Check /the signaling link settings and the RNC connections.
-(block
-3.IfIfany If the unblock
reason
other active is BTS).
a commissioning
alarmbeen occurs, error, check
follow that the
the instructions
1. Check the other
commissioning previous stepsis in have
active
line withalarms
to executed
theand act and
installed the fault is of
accordingly.
configuration
the
reported particular alarm.
2. If values
and thereagain,
areareno replace
other active alarms, or step 1 does not
correct.
optical
help,
-3.IfCOMMISSIONING cables
reset the
the threshold value and
BTS. SFPs ofused to connect"Maximum
the parameter the alarming radio
module to the system STATUS INVESTIGATIONS RX
3.
signal Replace the System Module.
-module If the level
reason difference"
is a commissioning is incorrect,error, the value
checkcan that betheset
from
commissioning 4 to/ extension
15 dB.isThe in
baseband
default
line with to
module.
valuethe isinstalled
7 dB. configuration
4.
-and If previous
Check if the steps have beenpassiveexecuted and fault is
reported values areMHAs
again, correct.
replace
or other devices are non-
commissioned
1.
-Add IfCheck
more
the the cell
baseband
threshold orvalue
if the
parameters values
capacity
of the inhave
to the
theRNC
parameter been wrongly
and
BTS"Maximum
or, ifthe
theBTS. set.
reason
RX is
the
Note:
2. If alarming
The
the Rx radio
parameterspower module
level
configured hardware.
alarms to can
the be
RNC enabled/disabled
are correct, lock
a
signal
5. broken
Ifthe level
previous baseband
difference"
steps unit,
have is replace
incorrect,
been the
executed thebaseband
value
and can
faultunit.be
is set
by
and
from antRxLevelMonitoringEnabled
unlock
4 to again, all cells
15 dB.replace of this BTS
The default value is 7 dB. using parameter.
the OMS element
reported
-manager
the Checksystem ifto
the trigger
MHAsparameter
module or other passive
hardware
sendingdevices
or extension
from the are
baseband
RNC non- to the
4.
BTS RXagain.
commissioned SIGNAL or LEVEL if the SPECIFIC
values have VALUES
been OR set.
wrongly
Note:
module
THRESHOLDS Perform
hardware the steps in the
(depends
INVESTIGATIONS onlisted order until the fault is
3.
Note:
resolved. If theThe parameters
Rx power configured
level module
alarms tocanthe be RNC are incorrect,
enabled/disabled
where
-lock Check the the alarming
which
cells andRx radio
chain
configure is causing
the is connected).
the
parameters problem.to the correct
by the antRxLevelMonitoringEnabled parameter.
-values.
CheckAfterwards,
if the maximum unlock RXthe signal
cells. level difference
1. Check the
threshold value configuration
matches theto make sure that there are
4.
4.
enough If the
RX default
SIGNAL
resources values
LEVEL for for theplanned
SPECIFIC
the minimumcell parameters
VALUES value.
HSUPA OR (such as
capacity.
-THRESHOLDS
Check if the
rampdown commissioning
time/step) is valid for the
are not appropriate
INVESTIGATIONS installed
in the BTS,
configuration,
reconfigure
-2.Check which the for
Rx BTS example,
chain with is theif fixed attenuation
commissioning
causing the problem. differs
wizard.
If theremain
between are not andenough div., then resources,
checklevel addMHA
if the additional or other
-HSUPA
Check iflicence.the maximum RX signal difference
antenna devices are
threshold value matches the planned value. in the configuration.
-- Check
Check if electrical tilting has is anvalid
impact on the case
3. Resetifthe
(possible
theBTS
external
commissioning
to get the minimum
disturbance).
for the
capacity installed
pre-selection
configuration,
for the HSUPAfor in example,
use. if fixed attenuation differs
between main and div., then check if the MHA or other
Note:
antenna Thedevices
Rx Power are Levelin the alarms
configuration.can be enabled/disabled
by the antRxLevelMonitoringEnabled
- Check if electrical tilting has an impact parameter.
on the case Setting
this parameter to
(possible external disturbance). false will disable raising of alarms related
to Rx Power Level Monitoring.
Note:
Note: The Rx Power
Perform the Level the
alarms can be enabled/disabled
Note:
by thePerform the steps
steps in
in the listed
listed order
antRxLevelMonitoringEnabled order until
until the
parameter. the fault
fault is
Setting is
resolved.
resolved.
this parameter to false will disable raising of alarms related
to
1. Rx PowerRAT Level Monitoring.
1. WCDMA reset.
Reduce the number of PIC pools in the BTS
configuration or add new FSP to the BTS. Or reconfigure
2. BTS
radio reset.
connections to no more than 1 ABIA used by
WCDMA are connected to WCDMA radios(e.g. 1 WCDMA
3. Replace
radio the alarming
connected module.
to 1 ABIA used by WCDMA and 1 radio
shared by WCDMA and LTE connected to ABIA used by
LTE)
resolved.
2. BTS reset.
1. Reduce the number of PIC pools in the BTS
configuration or add new FSP to the BTS.
2. Perform a BTS reset.

The lack of CCCH licensed capacity on the BTS (caused by
an insufficient number of commissioned CCCH Processing
When the faultcaused
Set licenses) is detected,
the cell the operator
setup should
with the check the
requested cell
UARFCN configuration
settings to fail. of the cells and the PIC pool
configuration.
If the faulty FSP is in the extension system module, block
One
and/oror unblock
both of thethe following
extension actions
system can be performed
module. to
Otherwise,
The
set operator
up the cell:should change the UARFCN of the cell at the
block
RNC and/or unblock
so theretheareCCCH the
no two BTS.
cells in capacity
the LCG consumption.
with the same
1. Decrease licensed
UARFCN while one is in PIC pool
2. Increase the CCCH Processing Set licensed and the othercapacity
is not. in
The operator should also modify the
BTS commissioning ("CCCH processing set" amount).PIC pool configuration
so that the number of PIC cells is correct (number of RX of
non-PIC
Check that cells
the+BTS2x number
has enoughof RXCCCHof PICProcessing
cells <= 48).Set
licenses loadedthe
Note: Perform or steps
has received a sufficient
in the listed number
order until fromis
the fault
NetAct
1. Checkin order to change the CCCH licensed capacity
Disableifto
resolved.
1.
according
there isaggregation
carrier a high load.inIfthe
the new CCCH Processing
there is, then
affected perform
LCG (Localthe
Set commissioning
following
Cell actions:
Group) by changing the carrier aggregation group ID to
settings.
0.a.WCDMA
1. Wait until
[caGroupId] traffic
RAT decreases.
reset.
b. Re-commission "Min number of HSUPA resource steps
for
2. HS-RACH
2. Set
BTS reset.
the users"
correct Tcell value in RNC for the cell
(minNumOfHsRachResourceStepsRes)
considering the following rules in assignment to a smaller
of Tcellvalue.
group
3. Replace the faulty unit.
and value to a HSDPA Scheduler:
Alternatively:
HSDPA
No Scheduler
manual actionisisCore to Tcell
required fromGroup Mapping:The fault
theinoperator.
2. Check
-just
HSPA if there
Scheduler enough
Core 1: hardware
Tcell Group 1LCG
and to3 allocate
"Min notifies
number the
of operator
HSUPA that the
resource Common
steps for Transport
HS-RACH
-Channel
HSPA Scheduler
is deleted.Core 2: Tcell Group 2 and 4
users". Otherwise, follow one of the steps below:
a. Add
TCell moretohardware
Group baseband (for example, ABIA or
Tcell Mapping:
FBBx) resources to LCG.
- Group 1: Tcell values 0, 1 and 2
- b. Re-commission
Group "Min3,number
2: Tcell values 4 and 5of HSUPA resource steps
for
- Group 3: Tcell values 6, 7 and 8value.
HS-RACH users" to a smaller
- Group 4: Tcell value 9
3. Enablesteps
Execute carrier
in aggregation
the followinginsequence:
an affected LCG by setting
up a non-zero carrier aggregation group ID.
1. Disable carrier aggregation in affected LCG by changing
carrier aggregation group ID to 0. [caGroupId]
2. Re-enable
WCDMA RATcarrier aggregation
reset is needed, asby setting
well the carrier
as changing the
aggregation group ID to the
commissioning for NBIC and PIC.intended non-zero value for the
affected LCG.
Additionally, before triggering WCDMA RAT reset,
commissioning additional baseband resources on the Core
where
Check the LCG haveand
configuration resources might help
radio modules in solving
connected to the
the
issue.
system module or extension baseband module. It is not
allowed to configure WCDMA cell using radio modules that
support
Change various protocols (CPRI,
the commissioning for DSSOBSAI). Hardware
and NBIC, which may
configured
lead to and
WCDMA used
RAT to support
reset or the
site WCDMA
reset cell shall
depending on use
1.
theDouble
same check activation parameters
protocol.
impact assessed by BTSOM.
LCELW.ActWcdmaLteSharedSpectrum and
LCELL.ActWcdmaLteSharedSpectrum, and correct them if
Additionally, commissioning additional baseband resources
anything is wrong.
on the Core where
2. Double check LCELW. the LCG have resources could help and
WcdmaFilteredBandwidthDL in
solving the issue.
correct it if anything is wrong.
3. Double check SharedSpectrumWcdmaCellDN and
correct it if anything is wrong.
4. Reset SBTS and check if the issue is resolved.
5.
1. If problem
Initiate Cellpersists,
block andcontact Nokia
Unblock personnel.
of paired LTE cell.
2. SBTS cancels the alarm notification. If problem persists,
try site restart.
3. SBTS cancels the alarm notification. If problem persists,
contact Nokia personnel.
Execute in the following order:
1.Configure more WCDMA LCGs to fully utilize the HW
baseband resources.
OR
Disable the unused baseband units: uncommission the
unused baseband board and/or disable the unused half of
baseband board.
1. Check the other active alarms. If the ROM disk is
2. Trigger WCDMA
corrupted, RAT
change the reset if module.
alarming needed.
2. Reset the alarming module. There are no recovery

actions,
1. Checktherefore
the otherreset can
active be tried
alarms. once.
If the ROMIf that
diskdoes
is not
help, replace the alarming module.
corrupted, change the alarming module. BTS internal SW management problem
2. Reset the alarming module. There are no recovery

actions, therefore reset can be tried once. If that does not
help, replace the alarming module. BTS internal SW management problem
1. Determine if this event is expected. Investigate audit logs
as necessary.
2. If this action is unexpected, use SSH to disable access
panel port(s) and/or physically inspect site installation.
If
1.the problem
Operator persists,
should verify
monitor the power source
temperature in BTS.of the Flexi
Zone Micro BTS, Flexi Zone Access
2. Operator should replace the Filter in subrack. Point, or Flexi Zone
SFN Antenna.
Operator should check whether heater or stepper motor or
control
This faultboard is abnormal
should and get ifbroken
not be cancelled failureparts replaced.
occurred at the
first place. In case of fault cancel indication, operator
[AMOC]:
should check Operator should
whether replace
subrack the control
control board is and
working
overvoltage
properly. protection board on subrack (in case of voltage
Operator should
lines missing) or replace
whole unit the(inheater
case assembly in subrack.
of temperatures
This fault should not be cancelled
sensors defective or whole unit broken). if failure occurred at the
first place. In case of fault cancel indication,
[AMOD]: Operator should check whether heater or stepping operator
should
motor orcheck whether
control board subrack
is abnormal control
andboard is working
get broken parts
properly.
replaced.
1. Operator should monitor LED status in front cover of
[AMOC/AMOD]:
controller(PDU box) Thistofault
findshould
out whichnot sensor
be cancelled
board ifisfailure
occurred
broken. at the first place. In case of fault cancel indication,
operator should check whether subrack
2. Operator should replace broken sensor board. control board is
working properly.
This fault should not be cancelled if failure occurred at the
Flexi BTS FDD,
first place. In caseFlexi BTS cancel
of fault TDD, AirScale
indication, BTS TDD,
operator
AirScale
should BTS whether
check FDD, Flexi SBTS,control
subrack AirScaleboardSBTS:
is working
1. Block
Note: and/orthe
Perform unblock
steps the
below BTS.in the listed order untiland
the
properly or cable connection between sensor board
fault disappears.
controller is properly.
2. If the BTS block and/or unblock does not help and the
fault
1. is reported
Reset by allModule.
the System FSP/ABIx modules or by FSP
Flexi
module BTSonTDD,
systemAirScale
moduleBTS TDD,
board, AirScale
replace theBTS FDD,
system
Flexi
module.SBTS, AirScale
Otherwise, SBTS,
replace Flexi BTS FDD:
the extension baseband Failure in replaceable baseband unit,System
2.
1. According
Restart thetoBTS.
the fault source, replace either of the
module
following:reporting the fault. Module failure
2. If that does not help, replace the alarming module.

- The System Module
In case the FSP is causing the alarm, replace the FSM Failure in replaceable baseband unit,System
-because
FBBx/ABIx
the module
alarm is related to the fixed FSP inside the Module failure
FSM.
1. Ensure that the cabinet doors are properly closed.
If FBBx or ABIx is causing the alarm, replace the FBBx or Baseband bus failure,Failure in replaceable
ABIx.
2. Check that the door switches function correctly and that baseband unit
they have been adjusted correctly.
Note: this alarm can be enabled or disabled in

commissioning.
[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]
[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]
1. In case EAC box is freshly connected or system starts-

up - wait up to 2 minutes for EAC box autodetection.
[User-defined]
2. In case EAC box is not connected - connect EAC box to
Note:
systemPerform
modulethe following
or to FPFH. steps in the listed order until
the fault
3. For disappears:
FSEE A202 EAC box: check that mode is switched
to RS485/HDLC.
1.
4. Use
ReplaceBTSEACElement
box. Manager to perform a full
commissioning to the BTS using the NetAct backup upload
1.
SCFDisconnect all EAC boxes from SMOD.
file as template.
2. Connect again selected EAC box. You can connect
additional
2. Download EACtwobox to the software
different second SMOD if present,
packages so thatand
the not
already used for another EAC
faulty file is removed from the BTS. box.
Take the following actions to clear the fault:

3. Download the software again.
1. Ensure that the unit and/or module is properly BTS internal SW management problem,Failure in
4.
connected. If the unit and/or module LED does not light up, replaceable baseband unit
Replace the System Module.
the unit and/or module is faulty. Check the unit and/or
module that is causing the alarm. Antenna Line Device failure,Failure in optical
interface,Failure in replaceable baseband
2. Check the fault history. unit,System Module failure
used:the Iub reference signal is known to be a good one.
case
-Otherwise,
If System
alarm diagnosticmodule
the BTSinfo containsmight
frequency "Detected be tuned radio to is a not able
-completely
Radio module
to support subsectors" incorrect value, replace causing the radioserious moduleproblems with Nokiain the
-network
Fronthaul
recommended switch
performance. moduleconfiguration.
subsector (if applicable)
3. Replace the problematic cable.
4. Replace
Check
Background the cell the faulty radio
frequency
information: or fronthaul
configuration
The principle is switch
parameter
that in module.
theagainst
mobile
5.
theReplace
BTS HW
network, thethe system module.
configuration.Check
synchronization goesiffrom the center frequency
S1 interface. But in
value configured
reality that chain might for DLbe and UL in somewhere
broken commissioning and,file foris
AirScale
correct. There
example, BTS
when FDD,
areusing AirScale
different
leased BTS
types
lines,of TDD, AirScale
variations
the BTS mightof the SBTS,
take HW the
Flexi
that BTS
might FDD,
have Flexi
limitationsBTS TDD,
in the
reference synchronization from the transmission network of Flexi
supported SBTS: frequency
Perform
range. operator.
another these actions This in the not
does following
harm the sequence:
system if the Configuration error: <x>
1. Check if the cable
synchronization of theconnecting
leased linethe system
service moduleisand
provider also
radio module, orenough.
accurate/stable the cable The connecting
BTS usesBTS thetheextension
incoming
5G BTS, AirScale
baseband module BTS
and FDD,
radio AirScale
module, or the TDD,
cable AirScale
synchronization
SBTS, Flexi BTS signal
FDD, as a
Flexi reference
BTS TDD, for the
Flexi Air
SBTS: interface, Baseband bus failure,Failure in replaceable
connecting
the accuracy the fronthaul switch
requirement of which moduleis setand radio module is
by 3GPP.
Replace
fixed firmly thetoalarming
the modules. module. baseband unit
2. Replace
AirScale BTS theFDD,
cable. AirScale BTS TDD, AirScale SBTS,
3.
Flexi BTS FDD, Fleximodule
Change the faulty BTS TDD, (FBBx/ABIx,
Flexi SBTS: FR or FHS).
4. If
Note: it
Flexi BTS does
Perform not
FDD,the help,steps
Flexi replace
BTS below the
TDD,inFlexi FCM
the listed/ FCT
SBTS, (system
orderAirScale until the Baseband bus failure,Failure in replaceable
module).
fault
SBTS: disappears. baseband unit
1. Check the other alarms of the
that the signal is being received from the BTS and FCT and act
accordingly.
reference clock source.
2. If therethe
Check areTRS no otherstatus. synchronization-related alarms
active,
3. Check startthethe fast tuning manually.
synchronization settings of the TRS unit.
3. Reset the site. Run fast tuning again.
4. Check the reference signal accuracy by measuring it with
a frequency counter (requires a good timebase for the
counter).
Replace
The reference the alarming
signal can module.
be found from the Sync Out System Module failure
interface of the System Module: the required accuracy is
+/-0.015ppm.
If the
5G BTS, reference
AirScale accuracy
BTS FDD, is correct,
AirScale runBTS fastTDD,tuning. AirScale
5. If thatFlexi
SBTS, does BTSnotFDD,help, Flexireplace BTS theTDD,system Flexi module.
SBTS:
1. Check the antenna cables, connectors, antenna, and
1. Checkline
antenna the devices
antennathat cablescan and connectors
interfere with the toward
RF signal. the
1.
1.
MHA.Block
Check Fixand/or
the unblock
antenna
or replace thelinethe and
broken Systemantenna
parts. Module. line devices. Fix or
replace
2. Check thethe faulty
antenna partsline or devices.
(TX-cable-antenna) impedance System Module failure
2.
2. Replace
Reset the the System
Flexi Radio Module.
(FR) Module to restart the MHA.
matching.
1.
2. Check
For CPRI-A the antenna
radios, cables the faultand may connectors
cancel automaticallytoward the if
MHA.
the faultFix or replace the broken parts.
Note:
Note: Forcondition
This operation
CPRI-A is cleared
affects
radios, theall within
antenna
alarm 1withminute faultofand
lines 1837detection.
cells
is
For
relatedsome
reported to CPRI-A
the
if the FR
the MHA
VSWR radios,
Module value the
and fault
not
exceeds may
just the
the levelfaulty one.
that is If the
2. Restart
cancel automatically by resetting
after the alarming the
fault Flexi
condition Radio (FR)
is cleared
alarm
defined
Module. reappears,
as a criterion replace the
for VSWR major module.
only once. It means Mast Head Amplifier fault
regardless of when the condition
that the alarm is reported because of a short, or is cleared. If theaccidental
fault is
not
peak cancelled
of the automatically,
VSWR value. The it is cancelled
alarm is canceledwhen the
ifcells
the RF
Note:
1. Check
module This is theoperation
antenna
blocked affects
and/or cables, allconnectors,
unblocked, antenna or lines
when and
antenna,RF and or
module
condition
related is cleared atthattheand radio, orjust
if fault 1957 is reported.
antenna
the
In BTStois
addition,
the
line FR Module
devices
reset.
in case of UHED
might not
radio,
cause
if
the
alarm
faulty
interference
is
one.
reported
If the
with the
and Mast Head Amplifier fault
alarm
RF signal. reappears, replace the alarming module.
canceled repeatedly, check also the attenuator.
3. For all other radios, the fault is cancelled when:
2.a)Check
the RFthe antenna
module line (TX-cable-antenna)
is blocked and/or unblocked. impedance
For other
matching. radio types, the alarm is reported if the VSWR
b) when
value exceeds the RF themodule
threshold or the BTS is
in more thanreset.one consecutive
c) by
measurement. switching the
Short DCor OFF
accidental or ON peakfor the
of Antenna
the VSWR Line
Note: For CPRI-A radios, the alarm with fault 1838 is value
is not reflected
reported if VSWR in thevalue alarm.
exceeds To cancel the level the that
alarm, a radio as
is defined
reset, radio disconnection, radio
criterion for VSWR minor only once. It means the alarm is power off, or an explicit
(alarm
reported cancel)
due torequest from userpeak
short/accidental via BTS of VSWRElement value. Manager
is necessary.
For other radio types, the alarm is reported if VSWR value
exceeds the threshold in more than one consecutive
measurements. Short/accidental peak of VSWR value will
not be reflected in the alarm.
Replace the alarming Radio Module. RF Module failure

If “Not enough resources to allocate the TDD cell to the
eCPRI TDD radio” is displayed in the alarm diagnostics
info, TDD cell, allocated on eCPRI TDD RU/MAA radio,
fails due to not enough carrier component resources.
1. Decrease the number of carriers (cells) configured OR
2. Replace the Radio Module with one that supports more
carriers
3. If it does not help, contact Nokia for support with eAxC
mapping
Replace thefile alarming
check. Radio Module and/or MultiRadio
Combiner. RF Module failure
1. Reset
If “Not the radio
enough eAxCmodule.
addresses to allocate the TDD cell to
the eCPRI TDD radio" is displayed in the alarm diagnostics
2. If resetting
info, TDD cell,the radio module
allocated on eCPRIdoes not RU/MAA
TDD help, replace the
radio,
alarming
Perform RET calibration. If that does not help, replace the RF Module failure
fails due radio
to not module.
enough eAxC addresses for
PUxCH/PDxCH/PRACH/SRS.
RET unit.
1. Replace the radio module with one with higher capacity.
2. Contact
In case Nokiasend
of 1845, for support
a validwith eAxC mapping
configuration file to file
the check.
alarming
Perform RETdevice.
calibration. If that does not help, replace the
RET
If “Notunit.
enough Beam Id range to allocate the TDD cell to
the eCPRI TDD radio” is displayed in the alarm diagnostics
In case
info, TDD of cell,
1845, send a valid
allocated configuration
on eCPRI file to the
TDD RU/MAA radio,
alarming
fails
Perform device.
due RET
to notcalibration.
enough beamIDs in eCPRI
If that does MAA
not help, storage.
replace the
1.
RET Replace
unit. the radio module with one with higher capacity.
2. Contact Nokia for max number of beams per cell in
vendor
In case parameters
of 1845, send check ORconfiguration
a valid radio capability
filewith beam ID
to the
storage
alarming checks.
device.
Perform RET calibration. If that does not help, replace the
RET unit.
If "Antenna beamforming type is not supported by radio
In case of 1845, send a valid configuration file to the
module" is displayed in the alarm diagnostic info, the cell is
alarming
Perform device.
RET calibration. If that does
not set up because the radio does notnot help, replace
support theor
integrated
RET unit.antenna which is necessary for configured cell.
external
In“The
If casedetected
of 1845, radio
send is a valid
not aconfiguration
5G O-RAN radio, file toorthe
it does
alarming
not support device.
beamforming.” is displayed in alarm diagnostic
information,
1. Reset the the cellmodule
radio cannottobegivesetaup becausereset
power-off the detected
to the
radio is not an
antenna line devices. O-RAN radio OR it does not support
beamforming.
1.
2. Replace
If step 1the the radio
does module
not help, with an
replace theO-RAN
antenna radio
linemodule
device. Antenna Line Device failure
1.
thatUpload
supports correct
beamforming.SW to the device (if possible) or
perform an ALD power reset (for example, by RF module
reset).
If "Cell allocation is impossible due to the fact that the cells
are commissioned on CPRI-A radios as well as CPRI-N
2. If that
radio doesinnot
cabled thehelp,
samereplace the antenna
ABIL board." line device.
is displayed in alarm
diagnostic
If the fault is information,
reported due theto
cell cannot
a radio be setcorrupted
module up because file,
the cells are commissioned
BTS tries to automatically ondownload
CPRI-N and the CPRI-A
correct SW radios
cabled
versiontoand theusesameit. IfABIL Board:
the automatic SW update fails and
1. Replace
fault or re-cable
is still reported, the radios
a manual SWsoupdate
that only CPRI-N or
is necessary. BTS internal SW management problem
CPRI-A radios are connected to the same ABIL board.
If "Not enough radio hardware due to primary link change"

Check that Primary
is displayed core is
in the alarm connected
diagnostic to the
info, the cell
secondary
might not
core via RP3-01 cable.
be set up because the detected cables do not provide the
required throughput. Identify radio(s) configured to support
the cell. Next check if all cables and SFPs connecting the
radio module(s) to the system module (or to the extension
baseband module - FBBx/ABIx) are working correctly". Configuration error: <x>
Reset the MHA using Radio Module reset. If this does not
help, replace the alarming module. Mast Head Amplifier fault
Instructions are divided into three sections. Execute the
steps from the section chosen based on the best
1. Reset theand
knowledge MHA by using
common radiotomodule
sense reset.
minimize the cost and
time effort.
2.
1. If this does
Check not solve theofproblem,
the functionality replace
the antenna line the alarming
device.
module. A: Check on the system module side:
Section Mast Head Amplifier fault
2. Check the compatibility between the antenna line device
1.
andCheck if the connector seal is properly mounted and
the BTS.
5G BTS,
firmly AirScale BTS FDD, AirScale BTS TDD, AirScale
in place.
SBTS,
1. Check Flexi
theBTS FDD, Flexi
functionality BTSantenna
of the TDD, Flexiline SBTS:
device.
3.
ForCheck
URGA, that the given
URCB, URCC, parameters areradio
in thevariants,
valid range.
2. Check if the Small Form and URKA
Factor Pluggable (SFP) is if the
fault
2. is preceded
Check
properly by and/or
a dualbetween
the compatibility
connected branch failure
mounted the with
antenna
in the any
SystemlineModule.
device
combination
and the BTS. of faults with IDs: 1839, 1907, 1911,
If SFP connection and/or mounting is incorrect, readjust the or 1957,
reset the radio firstmounting.
connection to try to clear the fault before
1. Check theand/orfunctionality of the antenna line device.
proceeding
3. Check that with
thethe following
given steps: are in the valid range.
parameters
3. Check if the LED indicates
2. Check the compatibility between the faulty SFP (connected
the antenna to
line device
For all radio
System variants:
Module). Replace the SFP if it is faulty.
and the BTS.
1.
4. Check the
Confirm ifthefunctionality
the currently of is
theproperly
applied antenna line device.
configuration is
3. Check
Check ifthat optical
the givencable
parameters are connected
in the validand/or
range.
compatible
mounted in with the configured RF HW capabilities.
the SFP.
2. Check the compatibility between the antenna line device
and
In the BTS.
5. LTE-LTE
Clean theor LTE AirScale-WCDMA
optical connectors that are RF sharing, check
connected to the if
the
SFP. Reset the RF HW and check if this solves the shared
configuration of both BTSs is consistent with the
3. Check
radio
problem. that theCorrect
capability. given parameters
the configuration,are in the valid range.
recommission
the BTSs, and reset the radio where fault 1900 is reported.
Radio
Section
1. Check block
B:and/or and correct
Check unblock
on thethe may
radio alternatively
module
antenna side:
line be performed in
configuration.
case of LTE AirScale-WCDMA RF sharing. In both cases,
radio
1.
2. Check reset
If that if or
does radio
connector block
not help, seal and/or unblock
is properly
replace the must
mounted
antenna be
lineand firmly in
device.
performed
5G BTS,
place. from
AirScale the Radio
BTS FDD, Master EM/NMS.
No
2. actionthe
1. Check required at this point. Autonomous recovery
2. Check BTS if theGPS connections
Smallreceiver
Form Factorand commissioning
installation.
Pluggable (SFP) settings.
is
actions are
2. Checkconnected in progress.
the GPS receiver If the alarm occurs multiple
status. in the RF module. times,
properly and/or mounted If
check
3. Block other
and/or active alarms
unblock the to determine
BTS. the root cause.
Note: Perform the steps below in the listed order until thethe
SFPCheck the
connection connection
and/or between
mounting the
is GPS
incorrect, receiver
readjust andthe
FSM/ASIx.
connection
alarm and/or mounting.
disappears.
4. If the
Check HW theconfiguration
cable or connection is confirmed
towards as correct,
a SyncHub this
problem
master
3. Check isif caused
when the by the
operating
optical as
cable BTS SW. Check
SyncHub
is properly slave. other active
connected and/or
1. Check the cabling (connected to the Sync In interface).
alarms.
5. Check in
mounted thethe status
SFP.of the SyncHub master. BTS reference clock missing
5G BTS:
2. Check if the 2.048 MHz reference source is working
4. Clean
Take
normally the the
and optical
followingthe with connectors
actions
2.048 MHz at the
to signal
clear the RF module end.
fault:
is available.
For
Reset FHS themodule
1. Lock/Unlock RF HW theunit
RAPfault
andHW 1900:
check
unit. if this solves the problem.
1.
2. Check
If optical link
the problem connections
is still observed between FHS module and
3. Replace
ABIx. Perform the FHSalarming
reset. module. after performing the first BTS reference clock missing
Section C: Check
step, replace the optical connection:
the RAP.
2.
1. If fault BTS
Check
AirScale is visible
if the after
optical
FDD, correcting
cables
AirScale optical
are not
BTS TDD, overlylinkbent.
AirScaleconnections,
If they
SBTS,
then
are, possible
replace thecaused
optical of the
cables
Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS: problem
since is from
overly eNB
bendingsoftware
the
or hardware.
optical
1. Verify if the HWP1 file is present in the FR module. or
fiber cables damages the cables and can detach
damage
Download thetheconnectors.
file if it is missing. Reset the FR module.
2.
5G If the file
BTS, AirScaleis present,
BTS lock and/or unlock the RF HW unit.
2.
3. OPTIONAL:
If the problem Test theFDD,
continues
AirScale
fiberafter
cable (forBTS
performing
TDD,
example,
step
AirScale
measure
2, replace
SBTS, Flexiattenuation)
the optical BTS FDD, Flexi from theBTSSystem
TDD, FlexiModule SBTS:
end.
1. FR HW unit. RF Module failure
Check the measuring equipment documentation for Upload
Check that the TEMP and CALI files are present.
any missingdetails.
instruction files. Reset the RF Module.
2. If the files are present, reset the FR HW unit.
3.
3. If the problem
OPTIONAL: is still
Test theobserved
fiber cable after
(forperforming step 1,
example, measure
replace
the optical attenuation) from the RF Module end. Check the RF Module failure
the FR HW unit.
measuring equipment documentation for instruction details.
If the alarm still persists after executing the steps from

sections A, B, and C, replace the RF module.
Reset
2. thethe
1. OPTIONAL:
Check RFconnection
HW
Test unit
theand check
fiber
and cable if (for
integrity thisofexample,
solves themeasure
the antenna problem.
the optical attenuation)
connector, cable, and antenna. from the System Module end.
Section
Check
2. For eCPRIC: measuring
the Check
check thethat
optical
equipment connection:
configured documentation
CABLINK between for
instructions.
BBMOD
1. Confirm and RMOD matches to the real HW connection
1. Check if ifthe
setup.
theoptical
existing applied
cables configuration
is/are is within
not overly bent. the
If they
configured
are, replace RF or FHS HW capabilities.
3.
3. OPTIONAL:
Reset the themTest
radio since
module. overly
the fiber bending
If cable
the the optical
(for example
alarm persists, fiber the
measure
replace
cables
the damages them and can detach or damage the
RM.
2. Check BTS connections and commissioning settings. the
optical
connectors.
attenuation) from the RF Module end. Check
measuring equipment documentation for instructions.
AirScale
3. BTS FDD,
Block/unblock theAirScale
BTS. BTS TDD, AirScale SBTS,
2.
If OPTIONAL:
the
Flexi alarmFDD,
BTS Test
is still the
observed
Flexi BTS fiber cable
after
TDD, (forSBTS:
executing
Flexi example,
stepsmeasure
from
the
1. optical
sections
Reset A,attenuation)
B, and
the RF HW unit.C, from
replace thetheSystem
RF Module
module. end.
4. If HW
Check configuration is confirmed, then this problem is
2. If thethe
caused by
measuring
problem
BTS SW.
equipment
continues
Check after
other
documentation
step
active1 has been for
alarms.
instructions.
performed, replace the RF HW unit.
3.
5. In
If case
the of SNMP
problem radio, the
continues only way to clear the fault is
3.
to OPTIONAL:
reset Test
radio the
or unit. fiberafter
replace cable
the
performing
unit.
previous
(for example, steps,
measure
replace
the the
optical RF HW
attenuation)
4. For eCPRI check thatfrom the RF CABLINK
configured Module end. Check the
between
measuring equipment documentation
BBMOD and RMOD matches to the real HW connection for instructions.
setup.
If the alarm is still observed after executing steps from
sections
CPRI-A radios:A, B, and C, replace the RF module.
Faults 1907 (TX out of order) and 1837 (VSWR major
alarm)
5G BTS: may be generated as a result of a high VSWR
condition.
Reset the Check if alarmIfwith
radio module. the fault
alarm1837 is reported,
persists, replaceand
the if
itRM.
5G BTS, AirScale BTS FDD, AirScale BTS TDD, AirScale RF Module failure
is, follow fault 1837 instructions.
AirScale
1. Reset BTS the RFFDD,
HWAirScale
unit. BTS TDD, AirScale SBTS,
Flexi BTS
2. If the FDD, Flexi
problem is stillBTS TDD, Flexi
observed after SBTS:
performing step 1,
1. Reset the RF HW
replace the RF HW unit. unit. RF Module failure
2. If the problem continues after resetting the RF HW unit,
1. Reset theRF
replace RFHWHWunit.unit.
5G BTS,the AirScale BTS FDD, AirScale BTS TDD, AirScale
SBTS,
2. If the Flexi
problemBTSisFDD, Flexi BTSafter
stillBTS
observed TDD,performing
Flexi SBTS:
step 1,
Flexi
Perform BTS FDD, Flexi
following steps TDD:
in the given order. Stop, if the
replace
1. the RF
Reset disappear: HW unit.
the RF HW unit. RF Module failure
problem
2.
1. If the problem
Check the Smallcontinues
Form-Factorafter resetting
Pluggablethe RF HW
(SFP) fromunit,
both
replace the RF HW unit.
ends (the baseband module and the faulty module). The
3. In case
optical of SNMP
interface LEDradio, the only
indicates way toSFP.
the faulty clearReplace
the faultthe
is
to reset the radio
SFP if it is faulty. or replace the unit. RF Module failure
2. Clean the connectors, test the fiber cable, and replace it
if it is faulty.
4.
5GReplace
BTS, Flexi the BTS
RF HW FDD,unit.
Flexi BTS TDD, AirScale BTS RF Module failure
TDD, AirScale BTS FDD, Flexi SBTS, AirScale SBTS:
2. If the problem continues after performing step 1, replace
the RF HW unit. RF Module failure
2. If problem is still observed after performing step 1,

replace the RF HW unit. RF Module failure
1.
WaitLock and/or
until unlock
the alarm is the RF HWThis
canceled. unit.might take up to 30
minutes.
2. If the problem remains after performing the first step,
replace the RF
If the alarm HW
is not unit.
canceled, check if the ambient RF Module failure
temperature is within the design limits for the radio module.
If the ambient temperature is out of limits, then the alarm is

expected and no further
5G BTS, AirScale actions
BTS FDD, are needed.
2. If the problem still persists after performing step 1,
replace the RF HW unit. RF Module failure
4. Clean the optical connectors at the FR/FHS module end.
Reset the FR/FHS HW unit and check if this solves the
problem.
Section C: Check the optical connection:

1. Check if the optical cables are not overly bent. If they
are,
5G BTS, replace the optical
AirScale BTS FDD,cable AirScale
since overly
BTSbending the
TDD, AirScale
optical fiber cables damages the
SBTS, Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS: cables and can detach or
damage the connectors.
2.
1. OPTIONAL:
If problem
Check if the Test
is ambientthe temperature
fiber cable
still observed (for
or example,
after performing measure
step
environmental1,
the
replaceoptical
conditions the attenuation)
RF HW
are within unit. from
theFDD, the
designed System
limits Module's
of the end.
radio RF Module failure
5G
Check BTS,the AirScale BTS
documentation of AirScale
the BTS
measuring TDD, AirScale
equipment for
module.
SBTS, When
Flexi BTS theFDD,
ambientFlexitemperature
BTS TDD, Flexior environmental
SBTS:
instruction
conditions details.
are out of unit.
limits, the alarm is expected and no
1.
3. Reset
OPTIONAL: the RF HW
Testneeded.
the fiber cable (for example, measure
further
2. theactions are
theIfoptical problem continues
attenuation) fromafter performing
the FR/FHS step 1, end.
Module's replace
the
Check RF HW unit.
theif documentation of the measuring equipment RF Module failure
2. Check the air flow is not blocked by some objects. for
instruction
Make sure details.minimum thermal clearances are followed.
Remove any objects that might be blocking the airflow, and
If the alarm
mount continues
the module after executing
according the steps
to instructions andfrom
sections A,
recommendations. B, and C, replace the FR/FHS module.
3. Check if excessive sunlight is causing an overheat.

Install sun shield and follow the mounting instructions and
5G BTS:
recommendations. RF Module failure
No action is needed.
1. Reset BTS
AirScale the RF/FHS HW unit.
FDD, AirScale BTS TDD, AirScale SBTS,
2. If problem is still observed
Flexi BTS FDD, Flexi BTS TDD, after performing
Flexi SBTS: step 1,
replace the RF/FHS HW unit.
No action is needed. The fault can be cancelled, when RF Module failure
unlock operation will be performed by master system
module accordingly.
1.
If Check technology
shared if the fan or isairfALU flow CDMA,
is blockedLTEby any locking
RRH object. may
1. Check any
Remove if the fan connector
objects that might is be
properly mounted.
blocking the fanMount
or air
be
the cleared
fan by
connector a full-unconditional
according to the restore on
guidelines.CDMA.
flow.
2. If the alarm is still observed then reset the alarming unit.
3.
2. If the alarm
Check ifif the isfan
stillconnector
observed,is execute
properlyfan test from
mounted. the
Mount
1. Check
system
1. Check module
if the
the fan
(if or airtemperature/environmental
flow is blocked
supported).
ambient by any object.
the
Remove fan connector
any objects properly.
thatdesign
mightthen
be blocking or air
4. If the alarm
conditions are is still observed
within the replace
limits of thethe fanmodule.
radio module.
1. Check
flow. if the ambient temperature and/or environmental
When
3. If thethe
conditions alarmambient
are persists,
within temperature/environmental
thereset
designthelimits
radioof
module. conditions
For CPRI-A
the radio/FHS
are
radio,
module.out of
reset
Whenlimits,
radio the
in alarm
chassis
the connector is expected
slot 1.
ambient temperature and no
and/or further
2. Checkare
actions if the fan
needed. is properly mounted. Mount
environmental
the fan connector conditions are out of limits, the alarm is
4. If the alarm
expected
properly. and nopersists,
furtherreplace
actionsthe arefan module.
needed. Fan failure
2. Check if the air flow is not blocked by some objects.
Make
2. Checksureif the minimum
air flow is thermal
thecontinues, not clearances
blocked by some are followed.
objects.
3. If the alarm
Remove any objects that reset
might the
be radio
blockingmodule.
the air flow, and
Make
1. Checksureif the
the minimum
ambient thermal clearances
temperature are followed.
or environmental
mount
Remove the
any module according to the instructions and
4. If the alarm
conditions areobjects
recommendations.
thatindicated
continues,
within the might bethe
replace blocking
fanof
limits theradio
module.
the air flow and Fan failure
mount the module according to the instructions
module. When the ambient temperature or environmental and
recommendations.
conditions
3. Check if exceed
excessive thesunlight
limits, the alarm is an
is causing expected
overheat.and no
further
Install actions are
theifsunshield needed.
3. Check excessivefollowing
sunlight the mounting
is causing an instructions
overheat. and
recommendations.
1. Check
Install if the
sunwhether ambient
shield and temperature/environmental
follow
2. Check
conditions thethe
are within flowthe
air design is mounting
not
limitsblocked instructions
for thewith
and
radioobjects
module.
recommendations.
that should not be there. Ensure the minimum thermal
When the ambient temperature/environmental conditions
clearances
are out are
of limits,maintained.
the alarm isRemove
expected anyandobjects that might
no further
4.
be In case
blocking the
thealarm
air is
flow still
and observed
mount theafter executing
module all theto
according
actions
previous are
stepsneeded.
then replace the alarming unit.
the instructions and recommendations.
2. Check if air flow is not blocked by some objects. Make
3. Check
sure whether
minimum excessive
thermal sunlight
clearances arecauses overheating.
followed. Remove If
so, install sun shield and follow the mounting instructions
any objects that might be blocking airflow and mount
and recommendations.
module according to instructions and recommendations.
3. Check if excessive sunlight is causing overheating.

Install a sunshield following mounting instructions and
recommendations.
properly connected and/or mounted in the RF/FHS module.
If the SFP's connection and/or mounting is not correct,
readjust the connection and/or mounting.
Section
3. CheckC:if Check the optical
the optical cable isconnection:
properly connected and/or
mounted in the SFP.
1.
4. Check if the
Clean the optical
optical cables areatnot
connectors theoverly
RF/FHSbent. If theyend.
module
are, replace the optical cables since overly bending
Reset the RF/FHS HW unit and check if this solves the the
optical
problem. fiber cables damages the cables and can detach or
Section C: Check the optical connection:
2.
1. OPTIONAL:
None Test the
Check if the optical fiber cable
cables (for
are not example,
overly bent. measure
If they
the optical attenuation) from the system module
are, replace the optical cables since overly bending end.the
Check
optical fiber cables damages the cables and can detach or
3.
2. OPTIONAL:
OPTIONAL: Test the
the fiber
TestSFP. fiber cable
cable (for
(for example,
example, measure
measure
Replace
the opticaltheattenuation)
faulty from the RF module end.end.
Check
the optical attenuation) from the system module Check
the measuring equipment documentation for instructions.
3. OPTIONAL:
1.the
Thealarm
VSWR Test the fiber
measured cable (for example,exceeds
at executing
the RF (transmitter) measure
If
the optical continues after
attenuation) from the RF/FHS steps from sections
module end.
values
A,B, that are
and acceptable by themodule.
RF module.
Check theC,measuring
replace the RF/FHS
equipment documentation for
instructions.
2. Check the impedance matching of the Antenna Line
System (replace elements that cause mismatch).
If the alarm continues after executing steps from sections
A,B,
3. Toand C, replace
check the RFFHS module.
if the above-mentioned steps have solved the
problem, reset the RF module.
Note: Forcing the RF HW to work under such conditions

might result in permanent damage to the RF HW.
1. Check the BTS connections and commissioning settings.
2. Block and unblock the BTS (using the local BTS Element
Manager connection if a remote connection is not possible). RF Module failure
1. Check the power supply to the affected radio module.
2. If the alarm persists, replace the radio module that is

generating the alarm. RF Module failure
1. Reset the RF Module.

2. If that does not help, replace the RF Module that is
generating the alarm. RF Module failure

2. If that does not help, replace the RF module that is
Execute
generating thethe
following
alarm. steps in the ordered sequence. If any RF Module failure
of the step does not help, execute the next one:
1. Reset the RF module.
1. Reset the radio module behind the cable reported as the
2. If that
fault does not help, replace the RF module that is
source.
generating
2. Reset thethe alarm.module.
system RF Module failure
3. Replace the SFP on the radio module port where the
cable reported as the fault source is terminated.
4.
1. Replace
Reset thethe RFSFP on the system module or the extension
Module.
baseband module
2. If that does port where
not help, the
replace cable
the reported
alarming as the
RF Module.
fault source is terminated.
5. Replace the optical cable reported as the fault source.
6. Replace the radio module behind the cable reported as
the fault source.
Replace the faulty
7. If the actions SFP.
mentioned above do not clear the faulty
situation, replace the extension baseband module (if the
fault is reported on the cable connected to the baseband
module) or the system module (if the fault is reported on
the cable connected to the system module).
1. Check the cables between the System Module, or ABIA,
and RF Module.

1. Check the cables between the System Module or ABIA
3.
andIf those do not help, block and unblock the site.
RF Module.
4.
2. If thosethe
Reset doRF
notModule.
help, replace the RF module that is
causing the alarm.
3. If those do not help, block and unblock the site.
4. If those do not help, replace the RF module that is

causing the alarm. Failure In Optical Interface <optIf ID>
1. Check the cables between the system module and the

Replace
RF module.the faulty SFP.
2. Reset the RF module.
3. If those do not help, block and unblock the site.
4. If those do not help, replace the RF module that is
generating the alarm.
1.
1. Check
Check thethe power
cables connection
between the toRF
themodule
RF module.
that is
2.
reported as the fault source and the RFmodule
If that does not help, replace the RF modulethat
thatisis
generating the alarm.
closer to the system module or ABIA.
2.
1. Reset
Check thethe RF module.
cables between the RF module that is
3. If that does not
reported as the fault help, blockand
source or unblock the site.that is
the RF module
4. If that does not help, replace
closer to the system module or ABIA. the RF module that is
generating
2. Reset the
the RF alarm.
module.
3. If that does not help, block or unblock the site.
resolved.
4. Read
1. If that alarm
does not help, replace
diagnostic info. the RF module that is
causing the alarm, which is connected to the faulty optical
link
If thetodiagnostic
the end farther
info isfrom
"EAC thelines
system module. is reject by
configuration
radio module."
1. Reset the Flexi Zone Micro BTS, Flexi Zone Access
Point, or Flexi Zone SFN Antenna.
2.
2. Confirm thatnot
If that does thehelp,
applied External
replace AlarmZone
the Flexi and Micro
Control line
BTS,
configuration is
Flexi Zone Access Point, or Flexi Zone SFN Antenna.
within the used Radio module's HW capabilities.
3.
1. Check
Validate thethat
External Alarm and
the ambient Control line
temperature connections
is within the
of the BTS andand
specifications, the that no foreign debris has accumulated
None
BTS
on the commissioning
unit. Verify Solarsettings.
shield if it is installed.
2. Reset the Flexi Zone Micro BTS, Flexi Zone Access
4. Reset
Point, the Radio
or Flexi ZoneModule.
SFN Antenna.
3. If that does not help, replace the BTS or Flexi Zone SFN
If diagnostic info is: "Number of commissioned EAC lines is
Antenna.
higher
1. Check thanwhether any other alarms concerning the faulty
the number
unitactions
have been of EAC lines(such
reported supported
asBTS by radio
Input module":
Overdrive or high
No are needed since the recovers
VSWR). If otherIfalarms
independently. the have
alarm been multiple
occurs reported,times,
followcheck
the
1. Correct configuration
instructions of EACalarms.
lines of the radio module.
other active for handling
alarms those
to determine the root cause. RF Module failure
2. Reset the alarming radio unit.
If
3.the problemsteps
If previous persists
haveafter
notthe External
canceled theAlarm
fault and Control
condition,
line configuration, and connections
replace the alarming radio unit hardware. of the Radio modules
have been confirmed and the Radio module is reset, then it
is caused
CPRI-A by the BTS SW. Check the other active alarms.
radios:
Fault 1983 (TX Output Overdrive) may be generated as a
result of a High VSWR condition and fault 1837 (VSWR
major alarm). Check if alarm with fault 1837 is reported,
and if it is, follow fault 1837 instructions.
1. Check the small form-factor pluggable (SFP) from both
ends (the system module and the radio unit) and replace if
one or both is faulty or unsupported.
2.
1. Clean
Confirm the connectors,
if the test the configuration
existing applied fiber cable, and replace
is within the
them if they are faulty.
configured FR HW capabilities.
3.
2. If the previous
Check the BTSsteps do not help,
connections replace the alarming
and commissioning settings.
radio unit hardware.
3. Restart the radio unit.
4. If the fault condition persists after the radio restart,
restart the BTS.
5. If the HW configuration is confirmed, then this problem is
caused by the BTS SW. Check other active alarms.
1. Check
Note: the small
Perform form-factor
the steps below pluggable (SFP)
in the listed orderfrom
untilboth
the
ends (the system
fault is resolved: module and the radio unit) and replace if
one or both
1. Check is faulty
if other or unsupported.
alarms are not reported at the same time.
2. Reset the affected radio unit.
If other alarms are reported, follow the necessary
instructions to clear them.
2. Reset the radio module, which is the fault source.
3. Reset the BTS.
4. Replace the radio module, which is the fault source. RF Module failure
1. Reset the alarming radio module.

No
2. Ifaction
it doesisnot required when this
help, replace thefaultcableis reported.
between the radio RF Module failure
module and the Receive Diversity Expansion Module
(RDEM).
3. If previous steps have not cancelled the alarm reported
resolved.
due
1. to thethe
Reset fault,
radio replace
module thereporting
alarmingthe radio
faultmodule.
(the one with
the blinking red LED display) by blocking and/or unblocking
it.
1. The
Reset
Note: radio
the reporting
Perform alarming
the steps the infault
radio is the order
unit.
the listed one on thethe
until cable
fault is
reported as the fault source.
2. If reset has not canceled the fault condition, replace the
resolved.
2.
1. Reset
Reset the
alarming radio
the system module
unitmodule
radio hardware. or radiothe
reporting on fault
the other
(one endwith of
the cable reported as the fault source.
blinking red LED display) by blocking and/or unblocking it.
3.
The Replace the SFP the
radio reporting on the
faultradio
is themodule
one onport the of the radio
cable
reporting the fault.
reported as the fault source.
4.
2. Replace
Reset thethe SFP on
system the system
module oritradio module,
on the extension
other end of
Check
baseband access
module, dooror and close
radio port ifonopen.
the other end of the
the cable reported as fault source.
cable
3. Replacereported as fault source.
1.
5. Reset
Replace thethe
the
SFP
alarming
optical
onradio
the radio
cable unit. module port of the radio
reported as fault source.
1.
2. Reset
reporting the
the
If a reset the faulty
fault.
does radio
not module unit.
cancel the fault condition, ensure
6.
4. Replace
2. If a reset the
Replace does radio
SFPnotdoes
cancel
on thenot reporting
the
system fault the fault
condition,
module, (the onethat
replace
extension
the
with Primary
blinking subunit
red LED display). have an Alarm Cap on the
one,
baseband
ASIG orALM
both subunits
module,
connector or so
radio
(the that
ALM they
port onare theboth
connector other the
can endsame
have type.
of the
a user
7. If resetting
cable reported the device
as fault at where
source. the cable that is reported as
alarm
the cable
fault sourceor nothing
is terminated all), and
helps, ensure
but thethat the
fault is reported
5. Replace the
Secondary subunitoptical cable
hasor an reported
Alarm Capas on fault source.
the ASIG ALM
again
6. Replaceafter some
the time
radio moduleif the actions
reporting mentioned
the fault: above
one with
connector.
have notred The
cleared secondary radio is the one
the fault situation, replace the extensionthat serves
blinking
antenna ports LED 3 display.
and 4.
baseband
7. If resetting module (if the where
the device fault isthe reported
cable on thatthe cable
is reported as
connected to the baseband module),
the fault source is terminated helps, but the fault is the system module (if
reported
the fault is reported on the cable
again after some time or if the actions mentioned above connected to the system
module),
have not clearedor the radio on the
the fault other end
situation, of thethe
replace cable reported
extension
as fault source.
baseband module (if the fault is reported on the cable
connected to the baseband module), the system module (if
the fault is reported on the cable connected to the system
module), or the radio on the other end of the cable reported
as fault source.
1. Check the clock reference sources on all the System
Modules connected to the radio.
2. If the previous step does not help, reset the radio unit.
3. If the previous steps do not help, replace the radio unit.
1.
1. In a CPRI-A
resolved.
Check RF sharing
for damage to theconfiguration,
cable between thetheCDMA BTS
cabling of
performs the needed recovery actions for this
the Radio Module output and/or damage to the physical fault.
2.
1. If the fault
Reset
antenna does module
the radio
assembly. not clearbehind
within the
20 minutes, then reset
cable reported as the
the
fault radio.
source by blocking and/or unblocking it.
2. Check the connection torque value between the Radio
Module and the bulkhead. If the alarm persists, reset the
2.
RFMReset thenext
at the system module. window.
maintenance
3. A survey of other external PIM sources might be
3. Replace the SFP on the radio module port where the
performed.
cable reported as fault source is terminated.
1.
4. Check
Replace if the
the small
SFP on form-factor pluggable
the system module (SFP) is
or extension
properly connected to the System Module.
baseband module port where the cable reported as fault
1.
2.
sourceCheck
Replace is the status
the SFP of
terminated. the module behind the faulty link
module. Failure in optical interface
(power on, and so on).
2.
5. Check
Replace the Small
the Form-Factor
optical Pluggable
cable reported (SFP)
as fault from both
source.
1.
ends Check(the ifSystemsmall form-factor
Module pluggable
and the (SFP)
module behind is
the faulty
properly
link). The connected
optical to the System
interface LED Module.
indicates the faulty SFP.as
6. Replace the SFP
2. radiomodule.
module behind the cable reported Failure in optical interface
Replace
fault source. the SFP if it is faulty.
3. Clean the connectors, test the fiber cable, and replace it
if7.itIfisthe
faulty.
system module reset helped but the fault is
4.
reportedprevious
If the again after stepssomedo time,
not help,
or ifreplace the module
the actions mentioned
behind the faulty link.
above have not cleared the fault situation, replace the Failure in optical interface
extension
1. Exchange baseband module
the alarming and(ifworking
the faultlinks,
is reported on the
and check
cable connected to the baseband
where the alarm is reported now. module) or the system
module (if the fault is reported on the cable connected to
the
2. Ifsystem module).
the alarming link remains the same, replace the Failure in optical interface
System
1. ExchangeModule.
the alarming and working links, and check
where the alarm is reported now.
3. If the alarming link changes, replace the module behind
that
2. If link.
the alarming link remains the same, replace the Failure in optical interface
System Module.
3. If the alarming link changes, replace the module behind

that link. Failure in optical interface

RF module, the cable between the baseband module and
the RF module, and the cable between the system module Failure in replaceable baseband unit,System
Check
and thethe alarms for
baseband the connected
module module.
and the cable between system Module failure
modules in a 3+3 or 4+3 configuration.
2.
RFReplace
module,the
andunit
thethat causes
cable the alarm
between (system module
the FBBx/ABIx module Baseband bus failure,Failure in optical
or baseband modules).
and the RF module. interface,Failure in replaceable baseband unit
2. Reset the system module.

Baseband bus failure,Failure in replaceable
3. Replace the alarming module (system module). baseband unit
Check the antenna mapping to the local cells in the Baseband bus failure,Failure in replaceable
commissioning file. baseband unit
1. Check the status of the module behind the faulty link
(power on, and so on).
2. Check the alarming fiber connection.

3. Block and unblock the RF Module.
4. Perform a BTS reset.
5. Replace the RF module behind the optical link.
Flexi BTS FDD/TDD:

If FSP is the source:
1. Perform the FSP reset.
5G
2. IfBTS, AirScale
that does BTS FDD,
not help, perform AirScale BTS TDD,
the System Module AirScale
reset.
3. If that does not help, replace the System Module. TDD, Flexi SBTS:
1. Switch to the most recently-active BTS configuration.
2. Retry
Flexi BTS the software update.
FDD/TDD,
1.If "Not enough DSPAirScale
resources BTS FDD/TDD:
available to allocate the
If FBB and/or ABIx is the source:
TRX." is displayed in the alarm diagnostic info, check if the
1.
1. Perform
BTSBlock the
configuration
and ABIx
unblock is reset.
the BTS.
2. If that does
consistent withnot thehelp,
usedperform
hardware. the ItSystem Module
is possible thatreset.
there Baseband bus failure,Failure in optical
3.
2. Check the logs for line code violation (LCV) errors card.
areIf that
not does
enough notFSPhelp, replace
resources the
to FBB
support and/or
cells ABIx
configured interface,Failure in replaceable baseband unit
in BSC.to optical links.
related
Try to:
1.
3. Reduce
Verify thethe No of Trxes
conditions in Sector.
of the Small Form-factor Pluggable
(SFP) transceiver and fiber. Baseband bus failure
2. If "TrxConfig Failed due to Change in Mcpa power
Pooling Status at runtime" is displayed in the alarm
1. Block and
diagnostic unblock
info, the BTS.
it is possible that MCPA feature status is
changed from disabled to Enabled at runtime from BSC or
2. Check
Base Band/theAntenna
configuration.
Hopping is enabled from BSC when Baseband bus failure
MCPA
1. Block feature
and is configured
unblock theinBTS. and is in use.
Note: Perform the steps the listed order until the fault is
Try to:
resolved.
1.Disable
2. Check the the baseband
Antenna/Base Band hopping,if
bus configuration Antenna
related to the
Hopping/Base
RP3 link speeds. Band was enabled. Baseband bus failure
1. Obtain a technical report for further analysis.
2.Reset SBTS Site from SBTS Element Manager,if MCPA
Note: Perform
feature was enabled the steps in the listed order until the fault is
at runtime.
2. Restart system module.
resolved.
3. If "TrxConfiguration failed Due to Base Band Hopping
3.
1. Replace
Obtain a the alarming
technical module.
report
Sector Split Across DSP" is for further in
displayed analysis.
the alarm
diagnostic info. This fault is raised when a Base Band
2. Perform
hopping
Note: Perform a site
enabled thereset.
Sector
steps in at the
BSClistedhas order
too many untilTrx
theto be is
fault
allocated
resolved. in same DSP.
3.
1. Replace
Try to:
Obtain the alarming
technical reportmodule.
for further analysis.
1.Disable
2. If alarming the Base
module Band
is FSPHopping
(alarmingor Reduce
module), thereset
No of Trx
Note:
at BSC Perform
for the the steps
Problematic in the listed order
Sector. until the fault is
respective
resolved. FSP.
3. Reset site.
4.
4. ifReplace
“Trx Reallocation Failed on Available DSP Resources”
1. Obtain a the
is displayed
alarming
technical
in the alarm
module.
report for further
diagnostic analysis.
info, try to execute
GSM
ToRestart RAT
clear the reset from SBTS Element Manager.
2. thefault,
systemperform the following steps in the below
module.
order until the fault is cleared:
This Fault can also come when:
3.
1. Replace the alarming module.
1. When
Check Trx Configuration
IP/IPSec is Rejected
configuration in SCFBy andDSP.
take corrective
2. When
Perform Carrier
the
action if needed. steps Configuration/Activation
below in the listed orderis Rejected
until by
the fault
Radio.
disappears:
3.
1. When
Reset Trx
the Configuration
System module towards DSPcorrective
timed Out.action if
2. Check
Note: configuration
Perform the steps theorlisted
atinBSC Capacity
and ordermodule.
take until the fault is
2. Replace
needed.
resolved. the System module or Capacity module.
Try to Perform below action till fault clears:
1.
3. Customer
Reset shall check
the alarming TRXthe Not BSC.
operational Trx of
1. Block and/or
impacted Sectorunblock thefrom
and perform SBTS.
the Trx Lock/unlock from
BSC.
4. Reset the BCF
2.
2. If that does
Reset not from
the BCF help, BSC.
from replace the faulty module.
BSC.
3.
5. Reset
Reset SBTS
SBTS Site
Site from
from SBTS
SBTS Element
Element Manager.
Manager.
if6.fault stillbackhaul
Verify persist after SBTS Reset, replace system
connectivity:
module.
a. Check whether the cable is properly connected
between BTS and BSC.
b. Replace the cable if the cable is faulty.
7. Replace system module.

c.
parameter
is If the number
cleared: of the radio of paths in BPF. configured for TRX at BSC is
REM
higherAlthoughthan the IPsec number is enabled
of does not automatically
mean
channels
DSS that
GSM+WCDMA the U-plane
for corresponding Case: channel from groupBSC/SEM
commissioned
1. Check hasthen anwhether
IPsec RXDS
tunnel parameter
configured. So, this needs is set
to be
at
to BTS,
a reasonable either
value, delete and extra
taking paths
into for the
account TRXthe on
site BSC
cross-checked.
or commission
1. If alarmindiagnostic additional channel
information for the
shows that channel
the DSS on
group
condition If not, order to
GOTO prevent unnecessary
Alarm_Clearance_PRE_NOIPSEC. alarms.
the base station.
Feature is enabled for GSM sector at BSC but DSS
d.
Feature
2. If theisthat
Check number
not antennas
enabled of paths for configured
aremapped
correctlyPeer forRATTRXlocal
aligned. at BSCcellisin
IF
lower than
commissioning( ipFragmentationAlgorithm
the number
(scf) take channels(IPSECC)
of following =action:
for corresponding
corrective 1 (1 = post-
fragmentation)
channel DSSgroup AND
commissioned at BTS, then either
a.
3. IfReplace Feature
ipSecEnabledif antenna is deactivated
connector
(IPSECC) = or cable
TRUE is faulty.delete the
extra channel
(actDynamicSharedSpectrum= from the commissioning false) on)mapped
for .the baseWCDMA
station
or
cell
4. configure
then enable
Replace an
antenna additional
DSSline Feature path for the TRX in
(actDynamicSharedSpectrum
if it is faulty. BSC.
GOTO
= true) END
b.
5. Modification
Replace the of actDynamicSharedSpectrum
Radio module or Remote Radio requires Head.
Alarm_Clearance_PRE_NOIPSEC:
object locking
6.
IF Replace
Follow (below
MIN system
operation module.
(localMtuResult, until the fault is cleared.
pathMtuResult) > or =
2. If alarm diagnostic information shows that Centre
udpMaxDatagramSize
frequency configured for DSS GSM sector in BSC is not
1.FALSE
= Check
Lock the the) BCF siteat configuration
BSC.frequency at BSC and take corrective
matching with WCDMA configured for mapped
action
SET
2. Enable ifudpMaxDatagramSize
needed.
TX power pooling = MIN
feature (localMtuResult,
WCDMA
Perform cellsteps
the in RNC, below take in one
the of thefor
listed the until
following
order BCF. corrective
the alarm
2. A few features
pathMtuResult)
3. Unlock the BCF. cannot co-exist. Examples:
actions:
disappears:
a. Hopping sectors should not be configured for Extended
a.
1. For
Check mapped WCDMA Cell:
the connection parameters of management
cell.
REM: copyWCDMA lowest local/pathMutResult to
i.connection
Change cell UARFCN (by anylocking followed by
b. Antenna hopping andand
udpMaxDatagramSize
towards BSC correct
Baseband hoppingincorrectshould not
unlocking
parameters WCDMA
if found. Cell at RNC) to the same value as “DSS
be
To enabled
clear the for a sector,
fault,isperform etc.the following
CENTRE
2.Correct
Check ifFREQUENCY”
BSC operational. configured for steps
mapped in the
GSM below
Cell
GOTO
order the
thesite
Alarm_Clearance
until faultconfigurations
is cleared: if such features are
in BSC.
configured.
OR
3. Check whether
Alarm_Clearance_PRE_IPSEC
Check whether theBSC BCFistype operational.
is properly configured at BSC
b. For GSM Sector:
4. Reset the BCF from BSC.
i.according
Change WCDMA to the BTS “DSS hardware.
CENTRE Perform the below steps if
FREQUENCY”
5.
it'sReset
REM SBTSconfigured:
consider Site
IP from SBTS
version Element
tunnel;Manager.
incorrectly
configured in BSC throughofreconfiguration
IPsec to the same
(IF
a. Lock
value IPsecv4
asthe WCDMA Tunnelcell
BCF. Header UARFCN SET of IPsec_Tunnel_Header
the WCDMA cell =
73)
b. Correct BCF
mapped to the GSM Sector. type.
(IF IPsecv6
c. Unlock theTunnelBCF. Header SET IPsec_Tunnel_Header =
93)
2. If
3. Unlock
alarmthe BCF if its
diagnostic locked. shows that the shared
information
frequencies configured in BSC for dynamic spectrum
udpMaxDatagramSize_IPsec
sharing = ( udpMaxDatagramSize +
To clearbetween the fault,the
IPsec_Tunnel_Header performGSM the
)
Sector and the
following WCDMA Cell are
steps:
not
1. Lock inside thethe 3.8MHz, take one of the following corrective
sector.
actions:
1.
2. Check
Unlock the
the configuration
sector. of pathMtuResult)
sync/time reference sources
IF
a. ( MIN (localMtuResult,
Reconfiguration of “DSS Parameters” for GSM > orSector
= in
in the System
udpMaxDatagramSize_IPsec Module.
BSC:
2. Check the status and installation of NTP servers. If they
=
To FALSE
clear
i.failed,
Modify the
(by ) fault,
locking match followed thefailing
commissioned
by unlocking and configured
GSM Cell) “DSS
SET restore the identified
udpMaxDatagramSize = MIN NTP server.
(localMtuResult,
BCF
MINIMUM
3. Check ID. Ifthethere
FREQUENCY”
statusis a mismatch,
and then
and “DSSofMAXIMUM
installation change
GNSS either
or theHub
Sync
pathMtuResult)
commissioned
FREQUENCY” - IPsec_Tunnel_Header
BCF
parametersID or the soconfigured
that Shared BCF ID.
Frequencies
Master.
REM: copyIf they lowest failed, restore the identified
local/pathMutResult failing GNSS or
between
Sync Hub WCDMA
Master. and GSM are inside-3.8 MHz.
IPsec_Tunnel_Header to udpMaxDatagramSize
4. Check the status and installation of BSC time reference
4. If alarm
source. diagnostic
If they failed, information shows that
restore the identified TRXs
failing uplink
BSC time
Alarm_Clearance
frequency of the GSM sector, configured in BSC, overlaps
reference source.
with WCDMA dedicated spectrum, take one of the following
Trigger
actions:the on-demand PMTU measurement.
The
a. changealarm TRX should be cleared
uplink frequency now. of the GSM sector to a
value that does not overlap with WCDMA dedicated
END
spectrum.
Note: When choosing between corrective actions please

consider that DSS Parameters should be consistent across
all sites in cluster.
1. Lock the BCF at BSC if Lean GSM or CMST is not

1. Reset SBTS.
configured at BSC
2.
2. If doesn't
Enable helpGSM
Lean request Nokia feature
or CMST supportfor
forthe
help.
BCF.
3. Unlock the BCF.
OR
1. Recommission the Site if Lean GSM or CMST is not
commissioned in SCF.
Case 1 ==> Disable antenna Hopping and trigger site reset.
case 2 ==> Change TRX type to Normal TRX in BSC and

Recommission the site accordingly.
case 3 ==> Recommission the sector in such way that two

sectors of the BCF will not share the same antenna.
1. Check for damage the cabling of the Radio Module
case
output4 and/or
==> Disable
damage BBtoHopping and trigger
the physical antenna site reset or
assembly.
recommission the sector torque
2. Check the connection so thatvalue
sectorbetween
in not split
thebetween
Radio
multiple
Module andantenna for BB Hopping enabled sector.
the bulkhead.
3. If the alarm persists, reset the RFM at the next
1. Check other
maintenance active alarms on the radio module for
window.
possible problems.
4. A survey of other external PIM sources might be
performed.
2. Enable PIM Cancellation again on the radio. This must
be done in two steps:
a. First, deactivate the PIM Cancellation feature to cancel
the alarm (set the parameter actPimCancellation to false).
Set the actPimCancellation
b. Then, feature on
activate PIM Cancellation activation flag
the radio to the
(set false.
parameters
For BTS: actPimCancellation and pimCancellingEnabled
to
Settrue).
the actExtPIMCancellation feature activation flag to
false.
3. If the alarm appears again, reset the radio module.
For EPIMC:
Move the unsupported RMOD to another Front Haul Switch
HW unit or directly connect to a baseband HW unit (for
example, ABIA).
Check the documentation for O-RU unit provided by the

vendor.

vendor.

vendor.
Address mismatch in summing,Antenna link is
down,BB bus reception error (summing
Check the documentation for O-RU unit provided by the device),BB bus transmission error,BTS file
vendor. error,Baseband bus configuration was
rejected,Communication failure,Critical bit
1. Reset
Note: the RF
Perform HW
the unit.in the listed order until the fault is
steps toggling error,DSP U-Plane computing
Communication
environment startup failure,Critical
failed,DSPbitapplication
toggling fatal
resolved. error,DSP
2. If the problem continues after step 1 has been error,DSP concurrent crash error,DSPconcurrent
application fatal error,DSP platform
performed, crash error,DSP platform fatal DSP
error,Externally
1. Reset thereplace
BTS. the RF HW unit. fatal error,Externally
triggered
triggered fatal
2. Check the SW version. error,FSPDSP fatal error,Fatal
overheating,FSP OSE lost,Fatal
subunit Error,Fault
between
OSE Error,Fault between FSM and FSPlack
FSM and FSP because of the of
because
3. Check the control cable connectivity of the antenna RP1 clock,Internal MTU configuration
module. of the lack of RP1 clock,Internal MTU
failure,Master unit has lost connection
configuration failure,Master to the
unit has lost
4. Replace the faulty unit. slave unit,No connection to unit,OIC MCU Buffer
connection to the slave unit,Message routing
Full,Oven oscillator clock missing,Oven
problem in receiver (RX),No connection to oscillator
Refer to the instructions for the root BTS fault reported in heating
unit,Not failure,POST test failed,Summing
able to synchronize service
baseband bus,OIC
the alarm on how to handle the failure reported in the default initialization failed,Unit synchronization
MCU Buffer Full,Operation on shared optical port
alarm. failed
failed,POST test failed,Summing service default
initialization failed,Unit SW download failed,Unit
Refer to the instructions for the root BTS fault reported in initialization failure,Unit not supported by current
the alarm on how to handle the failure reported in the BTS SW version,Unit synchronization
alarm. failed,Unknown HW resource
signal,Post test failed,RF Module critical file not
found,RF Module file not found,RF Module filter
input power missing,RF Module gain adjusting
failure,RF Module out of order,RF Module power
input faulty,RF Module power supply output
faulty,RF Power decreased,RP3 routing
collisions are detected on FR module,RRU CPU
and DSP link failure,RRU DPD self test
failure,RX out of order,TX out of
Refer to the instructions for the root BTS fault reported in order,Transmission quality deteriorated,Tuning
the alarm on how to handle the failure reported in the alarm frequency out of range,Unit unidentified
Address mismatch in summing,Antenna link is

down,BB bus reception error (summing
Refer to the instructions on how to handle the failure device),BB bus transmission error,Baseband bus
reported in the root BTS fault of the alarm. Severe SFP Reception
configuration was Power Aggravation
rejected,Message routing
,,10b8b coding error in optical interface
problem in receiver (RX),Not able
device,BB bus reception error (summing to synchronize
Refer to the instructions for the root BTS fault reported in baseband bus,Overload failure,Connection
device),Communication collision in
the alarm on how to handle the failure reported in the transmitter,Summing not
Unstable At 3Gbps,Connectionenabled for message
Unstable At
alarm. type,Transmission
6Gbps,Message routing problem inMuksu
rule collision in receiver
(RX),No connection to unit,Optical Interface
Refer to the instructions for the root BTS fault reported in faulty,Optical interface data/control/ethernet
the alarm on how to handle the failure reported in the buffer full,Receiving failure in Optical
alarm. Interface,Synchronization master missing
Refer to the instructions for the root BTS fault reported in

the alarmAirScale
5G BTS, on how to
BTShandle
FDD,the failure BTS
AirScale reported
TDD,inAirScale
the
alarm.
SBTS, Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS: FSP overheating,Unit temperature is high
Check the alarm diagnostic information for the reason of Cooling fan broken,Cooling fan has reduced from
the fault
Refer report
to the before theforreset.
instructions Please
the root BTSnote
faultthat currently
reported in the set speed,Cooling fan is over
degraded
the alarm oncellhow
setup
to is not supported.
handle the failure reported in the speeding,Cooling fan speed decreased,Fan
If BTS reset is executed when any of the cells has
alarm. vendor not detected
availability status Degraded, the cell might not be enabled
after the reset, and will not provide any services. ,BTS configuration error (not enough HW for
Refer to the instructions for the root BTS fault reported in Configuration
LCR),Baseband and hardwaremapping
resources mismatch,Incorrect
to cells
the alarm on how to handle the failure reported in the radio network parameters,Invalid
failure,Beamforming cell parameter configuration
The degraded cells can be also found based on active
alarm. file,Radio master conflict
mismatch,Incoherency in cell
alarms.
configuration,Invalid frequency channel for the
Refer
If to the instructions
actCategoryAlarms == for the for
false, root BTSdegraded
each fault reported
cell, in BTS HW,Power level not supported,Unit
the alarm
alarm 7654 onCell
howOperation
to handleDegraded
the failureisreported
reported.in the initialization failure,Unit not supported by current
alarm. BTS SW version,Unknown HW resource
Small Cell:
1. Check the alarm diagnostic information for the reason of BTS file error,Failure to download software due
the fault report before theforreset. Please to missing software signature,Failure to verify a
Refer to the instructions the root BTSnote
faultthat the in
reported GPS
signedreceiver alarm:
software not trackingtosatellites,PPS
release,Failure verify the
currently degraded cell setup is not supported. If BTS reset
the alarm on how to handle the failure reported in the alarm reference missing
is executed when any cell has availability status Degraded, signature of a signed software release,File
the cell may not be enabled after the reset and will not corrupted in SW download,Flash operation
Refer to the instructions
provide any services. for the root BTS fault reported in failure,SW corrupted,Unit SW download
the alarm on how to handle the failure reported in the failed,Unsigned software release has been
alarm.
The degraded cells may be found based on active alarms successfully downloaded
also.
Refer to the instructions for the root BTS fault reported in
If
theactCategoryAlarms == false,
alarm on how to handle thefor eachreported
failure degraded cell alarm Antenna line device HW failure,Communication
in the
7654
alarm.Cell Operation Degraded is reported. failure,No connection to unit
If actCategoryAlarms == true, please check all active MHA operation degraded,MHA operation
Refer
alarmstoand
thecheck
instructions for IDs
what cell the root BTS faultinreported in
are reported failure,Mast Head Amplifier fault above current
the alarm on how to handle the
degraded_cells alarms attribute. failure reported in the window,Mast Head Amplifier fault below current
alarm. window
Please recover the degraded cell first before you execute
BTS reset.
2. Reset (block and unblock) the BTS.

1.
1. The
Check BTS thebyhasother detected
alarms aofmalfunction
the BTS in the control
be reduced
interface of the 2GPSdBm in order
receiver. A avoidand
to possible act accordingly.
intermodulation
reason is that the
2. If there are
distortions and no other synchronization-related
passive EESS band violation. alarms
Radio
BTS
active, and the
starttothe GPS receiver
fast tuning do
with not
BTS support
Element a common
Manager.
configured
interface. support
Otherwise, the cell
perform is not able
a (remote) to support
power reset the for the
3. Reset
reduced the
pMax" site. Run
perform fast
the tuning
following again. steps:
GPS
4. Replacereceiver.
Check the reference signal accuracyradio by measuring it with
1.
2. Perform aradio (remote) module BTS with siteanother
resetafor module
thetimebase
whole BTS. type
a frequency
that
Flexi is able tocounter
SBTS,a AirScale support (note:
the
SBTS, requires
reduced pMax. good
FDD, Flexi BTS the for
3. Perform
counter). Thepower reference reset for Flexi
signal thecan BTS BTS.
wholebe found from the Sync
OR
TDD,
4. The AirScale
cable BTS
between TDD,the AirScale
GPS receiver BTS FDD:
and the BTS to might
Software
Out
2. If interface
there and
are hardware
of the ifFlexi
another reconfiguration
cellsSystemconfigured Module, oncan thebe made
required
radio in the the
1.
not In beNetAct,
working checkcorrectly.auto-configuration
Check if the pins is enabled
of the and if
setup
accuracy
same where
n258 (onis the
band faulty
+/-0.015ppm.
AND TX is
If
alarm(s) not
the used.
reference
due to fault accuracy
4008 is
andoxide
the required
connectors license and commissioning files arefromavailable.
correct, runinformation
additional fastboth tuning.ends of the
If the
„NRCELL.pMax
cable)
reference are free
accuracy
has to be is not
reduced by
and
Check
correct otherthe
the kind
other
cause ofactive
dirt:
of the
the BTS pinfaults
fault connection
is the and act
reference quality is good.
accordingly.
source the
2dBm
2. The
5. Check in order to
the between avoid
auto-connection intermodulation
the GPSorthe distortions
auto-configuration and
BTS
passive is cable
information tuning
EESS to.
using band Troubleshoot
violation.”
thesituation
BTS Siteand
receiver
are
Element external
reported
andsynchronization
the BTS might
forcable
Manager. thoseif cells:
be faulty.
network Check
to find thethe rootofcause. Other change BTSs the
with the
2.1.
needed. Reduce the pMax other cells for which this is same
alarm
possible
3. can
Load the provide
correct further information about the location of
6.
theThere
root might
cause. be acommissioning
hardware fault file in the to the
GPS BTS.
receiver.
2.2.
Check Lock/unlock
the operation the cell(s)
and change with alarm(s)
the GPS due to fault
module fast if 4008. Configuration error: <x>
5. If
Small the reference
Cell: accuracy is correct and running
needed.
tuning doescheck not help, replace the system module.and if the
1.
7. In
ThereNMS, might be ifaauto-configuration
hardware fault in the is enabled
BTS System
required
AirScale
Module. license
SBTS, the
Check and
Flexi commissioning
SBTS, Flexi
operation and files
BTS FDD,
change are available.
theFlexi
System BTS
AirScale
2.
TDD:Check BTS
the FDD, AirScale BTS
auto-connection or TDD, AirScale
auto-configuration SBTS,
Module
Flexi if needed.
Note:BTS
informationPerform FDD,
usingthe Flexi
the
steps BTS
BTS TDD,
in Site Flexiorder
Manager.
the listed SBTS: until the fault is
Note:
3. Load the correct commissioning file to theorder
resolved. Perform the steps below in the listed BTS.until the
fault disappears.
1.
1. Reset
Flexi
Reset Zone the BTS.
theAccess
System Point:
Module that is causing the alarm. Failure in replaceable baseband unit,System
2.
1.
2. Replace
Check
Replace the the
the faulty
connectivity
System module. of thethat
Module access point tothe
is causing thealarm.Flexi Module failure
1.
ZoneCheck the
Controller. fault name of the toggling BTS fault.
5G BTS, AirScale BTS FDD, AirScale BTS TDD, AirScale
2. Reset
Flexi BTS theFDD,Flexi Zone
Flexi BTS Access Point from the BTSSM
SBTS,
2. Follow
connected
Flexitheto
BTS FDD,
instructions
the FZAP.
FlexiofTDD: BTS
the TDD,
toggling Flexi
BTS SBTS:fault to clear
1. Reset
Check
the the System Module that
and correct the contents of the commissioning
problem. is causing the alarm.file. Failure in replaceable baseband unit,System
3.
In Reset
2. case
Replace ofthe Flexi
the System
configuration ZoneModuleController.
file for eCPRI that is TDD causing MAA/RUthe alarm. - Module failure
4. Contact
product code Nokia.errors, contact Nokia for eAxC mapping file
Note: Detailed information about the toggling frequency can
checks.
be found
Flexi ZoneinSFN the alarmAntenna: history file, which can be downloaded
using
1. Check the BTS Element
the connectivity Manager.
of the Flexi TheZone log file SFN is available
Antenna to
5G
with BTS:
Snapshot.
the Flexi Zone Micro BTS
In case of FDD-FDD CA configuration problem: or Flexi Zone Access Point.
2.
1) Reset
add missing the Flexi BBZoneresourcesSFN Antenna (at least 2 fromBB thepools BTSSM.are
3.
needed for 2CCs CA and 3 BB pools are neededAccess
Reset the Flexi Zone Micro BTS or Flexi Zone for 3CCs
Point.
CA);
4.
2) Contact
trigger Nokia.
Follow theBTS steps or below
5G RAT restart tothe
to resolve remap
fault: the CA cells on
the BB pools as required.
Flexi
OR BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
1. In caseBTS
AirScale of LTE-GSM sharing or LTE-LTE sharing or
3) remove
WCDMA-LTE CA TDD:configuration
or NR-LTE sharing, for affected carrier aggregation
try to configure the RF
cells
sharing combinations
mode correctlyreported
on in
both additional
sides. alarm information. Commissioning error: <x>
1. Block and/or unblock the alarming module.
2. In case RF sharing is not intended, RF sharing should be
disabled
2. If FSP in orSCF.
FBB or ABIA is the fault source, perform FSP
3. Replace
or FBB or ABIA the alarming
reset recovery.unit with If the unit configured
FCM/FCT/ASIx is the in
commissioning
fault source, perform system module reset recovery. If that Commissioning error: <x>
file.
does not help, perform a power-off reset.
3. If steps 1 and 2 do not help, replace the alarming

module. Failure in replaceable baseband unit
The followingthe
Reconfigure instructions
frequencyshould beinperformed
settings the properonway
thewith
master
respect RAT
to theside:
capabilities of the Radio Module. RF Module failure
1. Check the antenna line and antenna line device that

causes the alarm.
Check the
2. Fix or configuration
replace of parts
the faulty the configured cell.
or devices. Configuration error: <x>
3. Perform a radio module reset (only the master RAT in

sharing mode can request for such an operation to be
performed).
Perform the following steps on the MasterRAT side:
1. Check the antenna line and the antenna line device that
is causing
Note: Performthe alarm.
the steps below in the listed order until the
fault disappears.
Note: Perform the steps below in the listed order until the
2.
BTS Fixfault
or replace
disappears. the faulty parts and devices.
1. Check the Ethernet interface functionality used by Timing
Over
1. Check Packet.
the SW Check if other faults related to the Ethernet
package.
interface exist.
2.
BTS Download
fault Timing the SW to the antenna line device again.
disappears.
2. Check Over Packet configuration. Ensure that the
Master clock IP address is configured properly and that the
1. Check
Master the supports
clock SW package. the given parameters.
If
2. the fault is detected tointhe
non-sharing configuration:
3. Download
1. Check the the ALD
MasterSWinterface
clock antenna
and antenna
functionality. line device again. Fix or
line devices.
replace the faulty parts or devices.
1. Block and unblock the radio module where the faulty
4. Check
fiber
Note! cable that
Perform the IP
is connected.
theO-RU connection
steps Pleaseinbetween
below note thatthe
the listed Master
itorder
will untilclock
reset all
the
2.
and For
cells third
Flexi
for Zone
which party Micro
the radio BTSpleaseor
module check
Flexi Zone
provides theAccess
troubleshooting
services. Point or
fault
documentsdisappears. provided Next steps
by the shall be
O-RU vendor. executed only after
Flexi Zone
step didn't help. SFN Antenna is working.
2. If it does not help, replace parallel RP3-01/CPRI fiber
3. Fortoward
links CPRI-A oneradios,
radio the fault so may cancel automatically if
1.
the Reset
CPRI-A Affected
radio RAT.module
reports that
that
Overcurrent
the maximum
on AISG
mutual
port no
length
2. difference the
Block/unblock between
SBTS fibers
or Reset is lessSBTS. than 60 meters in
longer
OBSAI exists.
RRU, If the
or 146 fault
meters is not in canceled
CPRI RRU. automatically, the
5G
3. BTS:
Replace the alarming unit.
fault is canceled when the CPRI-A radio is reset, after BTS
If the BTS is not automatically updated by NetAct, update
Site
If the reset,
fault ortriggered
is BTS is blocked because and/or
of anunblocked.
incorrect RFbefore
sharing
the BTS with the SW version running on the BTS
configuration,
the SW updatecheck causing thatSW thefallback.
RF sharing feature is enabled
4.
on For all other radios,
synchronization the alarm is module.
cancelled only when the
NOTE:
5G Module
BTS: In case BTSmaster Element system
Manager detects an incorrect
RF is reset, or if the BTS is reset.
SW version, the BTS Element
If the BTS is not automatically updated by Manager should
NetAct,be update
If the alarm with fault 4038 (Radio master conflict) is
reconnected.
the BTS with the SW version running on the BTS before
reported at the same time,
the SW update causing SW fallback.
follow theSBTS,
AirScale instruction for
FlexiElement
SBTS:fault 4038 because in some cases,
NOTE: In case BTS Manager detects an incorrect
4038 may be the root cause of fault 4072.
SW version, the BTS Element Manager should be
The BTS start-up was not successful.
reconnected.
1. Checkthe
Perform thestepsfan and below the inconnector.
the listed order and untilthe
theSWfaultis
If the fault
AirScale is reported
SBTS, Flexi with Critical
SBTS: severity
disappears:
not consistent
2. Replace theinfan.the BTS, then NetAct autonomously Fan failure
triggers
The BTS an SW
start-up update
was withsuccessful.
not immediate activation for the
1. Either
BTS to theenable the actDistributedSite
SW version running on BTS. parameter
If this is not or switch
to a shorter
possible, the fiber between
operator must the FSM or
update the ABIx
SW and
update the FR.
If the fault is reported with Critical severity and the SW is
immediate
not consistent activation
in the BTS, for the thenBTS to theautonomously
NetAct SW version running
2.
on Restart
the BTS. theAfter
System module.
successful SW update, the following
triggers an SW update with immediate activation for thewill
occur:
1. Check the fans and ensure
BTS to the SW version running on BTS. If this is not that the ambient temperature
1.
on The BTS
the site
possible, the iswill be onAir
acceptable.
operator must withupdate
the previously-running
the SW update SW.
2. The
immediate SW will be
activation consistent in BTS. running Failure in replaceable baseband
1.
3. Check
The BTS that the
will fan for
report or the BTS
airflow
active SW
to
notthe
is fallback SW version
blockedfault by
butanywith will unit,Temperature alarm
2.
on If
the
object. that does
BTS. not
After help,
successfulreplace SW the alarming
update, the module.
following
major
occur: (not critical) alarm.
1.
2. The
Check BTS that will
thebefan onAir with theispreviously-running
connector properly mounted. SW.
If
2.the
ThefaultSWiswill reported
be consistentwith Major severity
in BTS. and SW is
consistent
3. The BTS inwill
BTS, thenactive
report the operator
SWthe should
fallback faulttrigger SW
but with
If that
update does
for the not
BTS help,
to replace
the requested fan.
SW version. After Fan failure
major (not critical) alarm.
successful SW update, the following will occur:
1. Thefault
If the BTSiswill be onAir
reported withwith
Major requested
severitySW andrunning.
SW is
2. The SW will be consistent in
consistent in BTS, then the operator should trigger SW BTS.
3. SW fallback
update for the BTS fault to and thethe related alarm
requested will be canceled.
SW version. After
1. The BTS will be onAir with requested SW running.
2. The SW will be consistent in BTS.
3. SW fallback fault and the related alarm will be canceled.
immediate activation for the BTS to the SW version running
on the BTS. After successful SW update, the following will
occur:
1. The BTS will be onAir with the previously-running SW.
3. The BTS will report active SW fallback fault but with
Activate RF chaining feature.
or
If the fault is reported with Major severity and SW is
Change
consistentradio HW topology
in BTS, configuration
then the operator so trigger
should that radio
SW
modules are not connected in a chain.
update for the BTS to the requested SW version. After
3. SW fallback fault and the related alarm will be canceled.
1. Check the other active alarms and act accordingly.
AirScale
If FSM is SBTS, Flexi
the fault SBTS,
source, Flexi BTS
perform FDD, Flexi
the following BTS
actions:
TDD, AirScale BTS TDD, AirScale BTS FDD:
2. If that does not help, block and/or unblock the system
Update
1. Resetthe
module. theBTS SW,module.
system unless itNote
is automatically
that all cells updated by
(including
NetAct.
those that are operational) will be reset.
3. a. FSMr2: If that does not help, replace the system
2. If a reset does not resolve the fault-situation, replace the
module.
system
b. If the module.
faulty cell is on the baseband extension module,
replace the extension module.
If FBB/ABIx is the fault source, perform the following

actions:
No
1. Resetmanual theaction
FBB/ABIx is required.
module. Note that all cells (including
those
Flexi Zone that are operational) will be reset.
Perform theMicro:
steps in the listed order until the fault is
1. Block/unblock the Flexi Zone Micro BTS to reset.
resolved.
2.
2. If
If a reset does
blocking not resolve
or unblocking the faultZone situation, replace the Failure in replaceable baseband unit,System
Perform the steps below in the listed Flexi orderMicro BTS
until the does
fault
FBBx/ABIx
not solve the module. Zone Micro Module failure
disappears.
1.
5G Wait
BTS, theproblem,
forAirScale startup BTS
replace
to the faultyif a
be completed
FDD, AirScale BTS
Flexi
synchronization
TDD, AirScale
BTS.
master system module has been reset.
SBTS, Flexi
Survey in progress: BTS FDD, Flexi BTS TDD, Flexi SBTS:
Perform
Flexi
1. Do Zone theAccess
nothing. steps below alarm in
Point, is the
Flexi listed SFN
Zone order until
Antenna: the faultthe
2. If fault
disappears. 1858:The informative
EFaultId_FaultyFcmConfigurationAl only. Normally, is
None
GPS
active,receiver check the runsRP3-01 the survey optical for cable
two reasons:
between the
-Check
somebody
synchronizationthe reported
has master alarms
started theofsurvey
and the peer system
manually,
synchronization module.
slave system
Notthetracking
-module GPS satellites:
and follow the instructions for fault 1858.has
receiver has noticed that the position
Check
changed theand optical
the connection
receiver hasbetween
started theautomatic
an master and peer
survey.
Enable
1. The
system power
most
modules. feeding
common toward
reason the
for radio
this module
fault by switching
indication is that
Note:
3. theThe
onCheck automatic
the alarms survey
in the always
synchronization takes place during the
the
first GPS
RFantenna
start-up.
power ininstallation
BTS Element not done master
was Manager. properly: system
the
module
sky and act accordingly.
In a visibility is not goodwhere
BTS configuration enough. oneRefer system to the
module provides
documentation
PPS
2. If synchronization
the automatic for installations
signal
survey to
takes and
another
place if there
system
every are
now deviations
module
and then,over
4.
withReset
the the synchronization
actual installation, masterthe
reinstall system
GPS module.
antenna. Note
a separate sync cable (sync hub
it might be an indication that the sky visibility is poor and configuration), check all
that
optical even
according and when thethe
tosync GPS antenna
connections
poorly-tracked between has aallgood
satellites, system
the sky modules.
GPS visibility,
receiver
5.
the Reset
problem the slave
might system
be caused moduleby by using
installing theblock
GPS and/or
antenna
concludes
unblock. Notethatthatthe the position
side has
effect changed.
of the In this
slave case,
system
too
check close the to the
activity transmitter
of betheaother antennas
faults of
(BTS the BTS, and
fault reset. this
historyCellsdata)
module
will cause reset might
disturbances toshared
the GPS radio module
receiver.
and if found feasible, reinstall
configured on the master system module, and supported by the GPS antenna.
the
No
2. radio might
stored
There module,
position:be might be temporarily
a malfunction in the disabled.
GPS receiver. Failure in optical interface
3.
One If the GPS
of the(remote) installation
settings of is good
the GPS receiver but the automatic
settings is survey
Perform
still takesaUsing place every power
now reset andSW for the
then, GPS
there receiver.
might be a set
incorrect. the manager of the GPS receiver,
malfunction
the receiver in the
to store GPS receiver.
the position Perform
intoGPS a (remote)
a non-volatile power
3. There
reset for might
the GPS be receiver.
a HW fault in the receiver. Check
memory.
the operation If there andischangeno tick the mark GPSin the position
module storage
if needed. BTS reference clock missing
selection, the GPS receiver runs the site or self-survey
4. If the
every timeactions
the GPS detailedreceiver in the is previous
reset (either steps bydo not
manager
improve
command, by power outage, or by a GPS recoverythe
the situation, there might be a HW fault in GPS
reset).
receiver. Check the operation
This means that if the GPS receiver installation quality is and change the GPS
module,
only an average if needed. - and especially if the installation is a poor
one - the GPS receiver turns the PPS reference OFF every
now and then during the site survey. This means the BTS
master clock drops to holdover mode much easier during
the survey than during the normal operation.
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, and this will cause disturbances to
the GPS receiver.
2. There the
Perform might be a
steps malfunction
below in theorder
in the listed GPSuntil
receiver.
the fault
Perform a
disappears:(remote) power reset for the GPS receiver.
3. There might
EEPROM be a HW fault in the GPS receiver. Check
invalid:
the operation and
1. The GPS receiverchange the GPSamodule
has detected if needed.
malfunction in its
EEPROM memory. Perform a (remote) power reset for the
GPS receiver.
2. There might be an HW fault in the GPS receiver. Check
the operation and change the GPS module if needed.
The DC voltage should be enabled for the reporting

antenna line to revert the changes.
Enable the parameter "hdlcCommunicationAllowed" for the

reporting Antenna Line to revert changes.
Update the BTS to the required SW version.
If 7650 or 7111 is active, immediate activation is

1. Check the cable connection between the synchronization
mandatory.
master and its GPS.
2. Check the alarms in the synchronization master system

Remove rootact
module and cause that prevents
accordingly. Sincethe
theBTS from using
synchronization
configured phase sync reference sources.
master is a separate system from the synchronization
slave, check its own alarms and instructions for recovering
the synchronization.
3. Reset the synchronization master system module.
Restart the faulty unit and retry the BTS snapshot request
using the BTS Element Manager.
Check the TD-SCDMA for active alarms.
Check the TD-SCDMA for active alarms.

Fault 4180 is raised if switch setting is not successful. After
the fourth attempt, group fault 3003 is raised. If there are
other working cells on FBBC, the user can decide whether
to
1. change theifFBBC
Determine card is
this event orexpected.
not. Investigate audit logs Failure in replaceable baseband unit
as necessary.
2. If this action is unexpected, use SSH to disable
maintenance port(s) and/or physically inspect site
installation.
1. Validate if the ambient temperature is within the

specifications and if no foreign debris has accumulated on
the unit.
fault disappears.
1. Check the other alarms of the BTS and IEEE1588-2008

Master Clock, and act accordingly.
None
2. Validate
1. If the 1818: thatEFaultId_Ov_OscAl
the ambient temperature fault isisalso active,
within the it is
likely that the center
specifications and that frequency
no foreign of debris
the Flexi hasZone Micro
accumulated
BTS,
on
1. theFlexi
One unit.
of theZonemost Access
common Point, or Flexi
reasons for Zone
this SFNindication
fault Antenna
1. Validate
reference if the
oscillator ambient
has temperature
demonstrated is within
excessive thedrift
2. Verify
(especially if
specifications the solar
occasional shield is
and if noindications)
foreigninstalled.
is that
debris the GPS or GNSS
forcing
antenna the replacement
installation has ornotrepair
been of thehas
done
accumulated
Flexi Zone
properly, Micro
that
on
is, the
the
BTS, unit.
Flexi Zone
sky
2. visibility
Reset the is notAccess
Flexi
Point, orRefer
good Micro
enough. Flexi to Zone
the SFN Antenna
unit. If there
documentation are noZone
for installations,
BTS, Flexi
other synchronization-related
and if there
Zone
are
Access
alarms
deviations
Point,
active, or Flexi theZone
fast SFN
tuningAntenna.
with thestart
3. If those actual
do not installation,
help, replace
with BTSthe
reinstall Site Manager.
the BTS.GPS or GNSS
antenna. Note that even when the GPS or GNSS antenna
3.
hasReset
goodthe skysite and run
visibility, fast tuning
problem mightagain.
be caused by
installing the GPS or GNSS antenna too close to the
4. If the condition
transmitter
Address antennas
faults persists,
associated replace
of thewith
BTS,anyandthe
and Flexi
this Zone
allwill cause
configuredMicro
BTS, Flexi
disturbances
synchronization Zoneto theAccess Point,
GPS orsources.
reference or Flexi
GNSS receiver. Zone SFN
This fault will clear, Antenna.
and
RF transmissions can resume when the Flexi Zone Micro
2. Check
BTS, Flexithe Zoneother possible
Access alarms
Point, or fault
or Flexi Zone indications
SFN Antenna of
the
has GPS
one (1) or GNSS
or morereceiver
available and the BTS and act
synchronization reference
accordingly.
sources.
3. There might be a malfunction in the GPS or GNSS

receiver. Perform a (remote) power reset for the GPS or
Replace the Flexi Zone Micro BTS, Flexi Zone Access
GNSS
1. Check receiver
power module.
supply.
Point, or Flexi Zone SFN Antenna.
2. Because of the short amount of time, it is possible
4. If thereefforts
(despite is onlytothe alarming
prevent GPS
it) that theorfault
GNSS doesreceiver
not reach
connected
the operator console before the alarming device the
to the GPS or GNSS antenna, check is powered
1. Checkpower
antenna
down. the configuration
feeding setting of TRSW/RFSW.
in the GPS or GNSS
Note:
2. Perform
Replace
receiver the
settings. the steps
faulty
The below
unit.
power in thetolisted
needs be ON order untilcase
in this the
3. Because
fault disappears. of false detection, it is possible (due to time
(while in shared configuration, one receiver
restraints in alarming method) that the fault is raised and feeds the
power
the towards
alarming the antenna, and power feeding setting of
1.
theVerify
other thedevice
ifreceivers is not is
IP address
is OFF).
powered
properlydown. In such
configured at case
the BTS.
when the device has not been reset and the fault is still
reported
2. (every 5 minutes), it shall be ignored on OSS.
5. Verify
Checkifthe theconnection
Real-time Performance
between the GPS Management
or GNSS
(RTPM) entity
receiver module, is operational
and GPS orand GNSS available.
antenna.Note that one
antenna might be shared
1. Perform a (remote) Flexi Zone Micro at the BTS siteBTS
between
or Fleximany
Zone
3.
GPSIf the
Access abovesite
or Point
GNSS have beenand
receivers,
reset. verified, the operator
one receiver mightcanfeedreset
the
the
powerBTS
2. Performto at
the aa power
suitable
antenna. time.
resetTheforfault
theindication
entire Flexi might
ZonebeMicro
caused
by
BTS a failure
or FlexiinZone another
AccessGPSPoint.
or GNSS receiver.
3. There might be an HW fault in the 1PPS connection
6. Perform
between the a Master
local or andphysical
Slavepowerboards. reset for thethe
Replace alarming
Flexi
GPS
Zone or GNSS
Micro BTS receiver
or Flexi module.
Zone Access Point.
Check the transport-related configuration (C-Plane
address, U-Plane
7. There might be address, andinTransport
an HW fault the GPS network
or GNSSID). If
the
antenna and / or possible antenna line splitter, possible and
fault was raised at startup, correct the configuration line
reset the BTS.
amplifier, If the fault
or lightning was raised
or surge during
protector BTS Check
devices. runtime,
the
correct theand
operation configuration
change them andifapply the changes to the BTS. Configuration error: <x>
needed.
8. There might be an HW fault in the GPS or GNSS

receiver module. Check the operation and change the GPS
or GNSS
Check receiver
if the moduleisif powered
radio master needed. on, and that the RP3-
01 cables of the radio master are properly attached. When
the radio master is available, the radio slave will wait for a
user-defined amount of time for the radio master to stay
available before giving up the temporary radio master role.
1. Check or correct the RET device configuration (that is,
the RET connected to the radio module generating the
alarm).
Flexi BTS TDD, AirScale BTS TDD:
2.
1. If that does
Check notofhelp,
values
the antenna replace
theline
the the antenna
parameters
and MHA, line devices.
device.
"TddSpecSubfConf",
RET, RAE
Perform following actions
"rxCalibrationConfiguration", until the problem is solved:
Fix or replace the faulty partsand or devices.
"actReduceWimaxInterference" and the used beam-forming
1. Check
radio the optical
module connection between the radio master
2. Perform
system antype.
RF module startup or BTS reset to cancel the
2. Commission different shared
alarm.
module and the radio.
combination for the mentioned
values, or change to a different beam-forming radio module
2. Check
type theconfiguration.
for the alarms in the radio master system module and
act accordingly.
3.
ForReset
TDD the
mMIMOradiocell
master system
on CPRI module.MAA:
or eCPRI
1. Check if selected mMimoAntArrayMode for the cell is
supported by the radio
2. Change mMimoAntArrayMode for the cell or change the
radio module that supports required mMimoAntArrayMode Configuration error: <x>
1. Confirm if the existing applied configuration is within the
1. Check the
configured FRconfiguration of the ALD port.
hardware capabilities.
2.
2. The alarm
Reduce theislength
cancelled only
of the when
fiber thetoRF
cable Module
a length is is
that
reset, or the BTS is reset.
supported by the BTS and FR combination.
FDD CPRI radios only: If the fault is seen after a reduction

in fiber cable length, then a BTS site reset must be
performed to cancel the fault.
1. When the FZAP or SFN ANT has failed to join the zone,
Check all the alarms
restart HTTPD posted SCLI)
RG (through by theand
Flexithen
Zone Access
reset Point
the failed
prior to the Z1
FZAP or SFN ANT. link failure.
2. When the SW upgrade has failed, retry the software
load.
Flexi BTS FDD,
3. Restart Flexi
the FZC or BTS TDD, AirScale BTS TDD,
FZAP/FZM.
AirScale BTS FDD, Flexi
4. Replace the faulty device. SBTS, AirScale SBTS:
1. Please inform the vendor if this alarm is reported. The
vendor will analyze the automatically-collected symptom
data when the fault was detected. Automatically-collected
symptom data (files) are stored in LSS or NetAct-dedicated
To cancel the fault, unblock the Flexi Zone Access Point.
folder.
NetAct - Operating Documentation (Collecting symptom
data from LTE to NetAct)
2. To try to clear alarm with fault 4261, please block /
unblock the BTS.
Check the cable between the SRIO ports in the BTSs.

Automatic
1. Check all SRIO
alarmslinkposted
establishment retrial
by the Flexi starts
Zone as soon
Access as
Point
the fault has been
prior to this fault. detected.
2. Check the configuration of the FZAP against similarly-
configured FZAPs of the same type.
3. Reset the Flexi Zone Access Point.
4. Reset the Flexi Zone Controller.
Retry the SW update. BTS internal SW management problem

No manual action is needed from the operator. BTS internal SW management problem
If LNA is shared between two BTSs and it supports

separate AISG ports for each BTS, check if the LNA is not
switched to bypass mode by other BTSs.
BTS fault disappears:
Check
1. Reset other
the active
GPS oralarms.GNSS module.
1. Read the diagnostic information of the alarm.
2.
Check Block and unblock the
anyBTS to activate toa any
BTSand reset.
2. If thefor and resolve
diagnostic information faultsis related
"IQ compression orallforced
3. Trigger
configured a software
synchronization update procedure
reference sources. for the GPS
If BTS oris
link speed incorrect in site configuration file", check which
GNSS
unable module
to resume from NMS or BTS Site Manager.
configurations are operation
supportedorbyreliably Nokia,staycorrect in operation
the IQ
4.
when Replace
one orthe morealarming GPS or GNSS
synchronization module.
reference sources are
compression or force link speed value in the Site
available a hardware
Configuration File (SCF), defect andis then
likelyrecommission
present requiring that
the BTS.
theIfaffected
3. the diagnosticFZM be replaced. is "IQ compression not
information
A manual
1. Ensure eNodeB
supported by Radio
that reset
HW"and
the corresponding cell enable
replace the radio
RFM/FM is necessary
modulemodule
plug-in withto a
acquire
radio
has that
been synchronization
supports
installed IQ
on the in the
compression,
networkRIBS
Reduce the length of the cables used to connect the radio configuration.
or
server disable
in NMS IQ (NetAct
compression
SW
module to thefunction,
Archive). system module.and thenIfrecommission
the radio module the works
BTS. Ifin
there are several radios in a chain
the chain, you can also remove the previous radio modules topology, first identify the
radio(s)
2. Update that the are not supporting
corresponding IQ
RFM/FHS
to remove the delay introduced by the previous radio compression
plug-in and
software
change
module
modules. it (them)
in the BTS with radio(s)
and/or BTSthat from supports
NetAct.IQ
Reduce
compression, the length of theIQ
or disable cable used to connect
compression functionthe and radio
then
module
3. Supply the RFM/FHS plug-in software module to BTS in
recommission to the system
the BTS. module. If the radio module works
a
4. chain,
and/orIf theBTSyoulocally
diagnosticcan also remove
information
through BTSthe previous
isElement
"Down radio modules
sampling
Manager not
if NetAct to
remove
supported
connectionby the delay
is Radio introduced by the previous
HW" replace the radio with a radio that
not available. radio
modules.
supports Down sampling, or disable Down Sampling
function
4. Block and and/or then recommission
unblock the BTS.the BTS.
5. If the diagnostic
1. If the BTS cannot acquire info is "Number
GNSSof detected RET units in
coordinates:
multiRET
-Note:
DisableYouthe is not
need consistent
to commission
Location with
Lock feature. site configuration
the radio module before file" or itits
equivalent
can be taken information
into use. for RAE, correct
- Fix the problem with the GNSS receiver. Alternatively, the RET or RAE
configuration
configure to remove the extra entries, and then update
1.
the Verify
BTS. ifthe
thedetection method to a data
APMOD provisioning method have otherbeen than
GNSS.
correctly entered. info is "Commissioned antenna
6. If the diagnostic
-2.Re-enable thesiteID
Location Lock feature.
Verify
operating bandif the is notprovisioned
supported by onthe
theALD."
FZAPrecommission
was entered
correctly.
the
2. IfALD
the BTSsubunit cannot withacquire
supported antenna
network operating band.
configuration
7. If the
parameters: diagnostic information is "Radio’s max number of
supported streams per
- Disable the Location Lock feature. carrier was exceeded.", delete the
alarming cell, create a new
- Fix the problem with network configuration. one and recommission the radio
to the new installed radio.
- Re-enable the Location Lock feature. Commissioning error: <x>
3. If the BTS failed to update the Location Lock evidence:

- Disable and then re-enable the Location Lock feature.
- If the problem persists, replace the faulty device.
alarm is expected.
- If the BTS relocation is authorized, disable the Location
Lock feature and then re-enable it to reacquire the correct
Location Lock evidence.
2. If the BTS detects a missing or corrupted Location Lock
evidence:
- Disable the Location Lock feature and then re-enable it in
order to recover.
- If, during the above operation, the BTS has reported fault
4283:EFaultId_LocationLockFailed, replace the faulty
To clear the fault change configuration of BTSes related by
device.
inter-site Carrier
1. Check if the
Aggregation inter-site
relations soCarrier
that Aggregation feature is
1. Checkon
Upgrade
enabled if the
or inter-site
downgrade
the partner Carrier
SW
eNB. so Aggregation
that samefeature
thecarrier version isis on
(i) each
enabled BTS
on that
the belongs
partner to
eNB. the same aggregation
the eNBs
cluster has related
the same by inter-site or inter-eNB Carrier
2. Check
Aggregation
2. Check ifif network communication
relations.
network communication between
between specific
specific
value
dedicatedof LNBTS ports caClusterId
on the eNB, configured
and its partner eNB used for
dedicated
and ports on the eNB,
inter-site
and CarriereNB
its partner Aggregation
used for proprietary
inter-site interface
(ii) each
messaging, BTSisthat belongs
possible and tonot sameCarrier
theblocked carrier
(for
Aggregation
aggregation
example, by
proprietary
cluster has interface
unique
firewall
messaging, filtering rules).
is possible and not blocked (for example, by
value
3. Makeof LNBTS
sure that caClusterMemberId configured.
there are no other critical or major alarms
firewall filtering rules).
on the eNB and its partner eNB.
4.
3. Restart
Check ifthe thereinter-site
are notCarrier Aggregation
other critical or majorfeature onon
alarms the
eNB and its partner
the eNB and its partner eNB. eNB.
5. Reset the eNB and its partner eNB.
4. Restart
Read the inter-site
the alarm Carrier
diagnostic Aggregation
information feature
to know whenonthe
the
eNB and its partner eNB.
missing license was detected and at what level the IP traffic
is currently throttled in relation to the peak rate.
5. Reset the eNB and its partner eNB.
Add licenses to CLS to avoid the traffic limitation.
If licenses are not added, the level will be decreased to the

lowest level, which is 50% of peak rate.
If this alarm is observed from the BTSSM, check the

backhaul connection of the BTS.
Configure
5G BTS: a valid GNSS constellation mode supported by
the GNSSsynchronous
1. Check receiver to Ethernet configuration
cancel
2. Checkthethe
fault (wait used
cabling for 60toseconds).
provide synchronous Ethernet
signal to BTS
AirScale
1. Check SBTS, Flexi SBTS:
the connectivity to the NTP server.
Scrutinize
2. Check the status
NTPofserver
the Ethernet port configured
configuration at BTS. as a
SyncE reference:
1. Check if the Ethernet port is enabled through
1. Check the cable connectivity on ToP master side.
configuration.
2.
2. Check
Ensurethe thatTOP configuration
result of Ethernet on both the ToP slave
auto-negotiation matches
(BTS or RU) and ToP master sides.
on local and remote ports of the Ethernet link.
3. Exclude Loss of Signal (LoS) on the port.
4. In case of an SFP port, ensure that a compliant SFP
module is installed.
5. TestPerform
Note! if the installed SFP
the steps module
below is listed
in the not failed.
order until the
alarm disappears.
1. Checkthe
Replace thecable
cabling (connected
with to SyncIf In
a shorter cable. theinterface).
radio module
is connected
directly to the system module or the extension baseband
module, the longest supported cable length for micro DTX
is approximately 16 km.
cable
systemconnecting
deployment." module with thethe
extension baseband
radio module, module
or the and the
extension
radio
To clearmodule,
the is
alarm, connected
do any of the
baseband module (FBBx) and the radio module, supports 6following:
firmly
Gbps to the modules.
transmission.
- Provide the necessary HW, configuration, or both, and
3.
2. Replace
then Checkresetifthe theBTS.
the cable.connecting the system module and
cable
the
If the radio
faultmodule,
istheraisedorduring
the cable connecting
micro-DTX the extension
activation, deactivate
4. Change
-baseband
Switch theradio
offmodule module
inter-eNB
and where
theFDD-TDD
radio the
module unstable
carrier link
aggregation
is fixed is to
firmly
the mDTX,
terminated. and then activate it again by recommissioning.
completely.
the modules.
If the fault is raised during micro-DTX deactivation, activate
-5.
3.
the
If this
Replace
Replace
mDTX,
does
thetheHW
and
not help,
(which
cable.
then
replace
has been
deactivate
the FBBx/ABIx
it configured,
again by
ifbut
thefaulty) if
unstable
the HW islink
the isroot.
terminated
recommissioning.
on the FBBx/ABIx.
4. Change the radio module where the unstable link is
terminated.
If
6. If this doesnot
the fault is notcleared because
help, replace theofFCTrepeated
(systemactivation
module). or
deactivation of the micro-DTX, a BTS site reset clears the
5. If this does not help, replace the FBBx if the unstable link
fault.
If
is an alarm with fault 4038 (Radio master conflict) is
terminated
reported
on FBBx.at the same
time, follow the instructions of fault 4038 because in some
cases
6. If this fault
does 4038 notmight
help, replace the FCT (system module).
be the root cause of fault 4309. Failure in optical interface
If an alarm with fault 4038 (Radio master conflict) is
reported at the same time,
follow the instructions of fault 4038, because in some
cases, fault 4038 might be the root cause of fault 4310. Failure in optical interface
Check all the alarms posted by the Flexi Zone Access Point
or SFN ANT. The operator can initiate a password update
request again, which might be successfully accepted by
FZAPs or SFN ANTs clearing the alarm.
1. Check if other alarms are active in the LTE BTS or

Verify
SCDMA that a Stratum-0 TD-LTE BTS is within the reception
BTS.
range
2. Check theaffected
of the target BTS.between the SCDMA and
optical connection
LTE BTS. Replace the optical cable and/or SFPs.
3. If this does not help, reset LTE BTS.
4. If this does not help, reset SCDMA BTS.
5. If this doesofnot
Cancellation help,
this faultreplace FCT.
is automatically performed by the
BTS after a BTS reset. Check which MNL and TNL
parameters
If the target have
FZAPbeen
doeschanged in the exist,
not physically last configuration file
ignore this fault
downloaded to BTS. Correct the parameters to
or clean it up by deleting the target FZAP. Otherwise,enable
connection
perform theto the management
following steps: system.
1. Check all other alarms posted against the target FZAP
on FZC.
2. Check the alarms raised on the FZAP through WebUI or
FZAP BTSSM.
Change the GNSS location mode to automatic to cancel

the fault. The fault is canceled after 60 seconds.
Recovery restart of the faulty radio module is highly

This fault is raised
recommended andifshould
the Flexi
be Zone Controller
scheduled in thehas acquired
nearest
LTE timetime
suitable sync(for
with one of its
example, FZAPs
during lowbefore
traffic but has failed
period).
to maintain the time sync because of one of the following:
1. None of the FZAPs are connected anymore.

Recovery
2. All of itsrestart of theFZAPs
connected faulty radio module
has lost sync is highly
with their time
recommended
source. and should be done as soon as possible.
Perform actions to ensure that the FZAPs are connected to

the FZC and/or recover the time sync with their time
source.
Contact Nokia technical support to decide if the activated
serial console is needed.
If not, please ask Nokia technical support to disable the
console.
If BBMOD is the fault source - reset the BBMOD. If system
module is the fault source - reset BTS to clear the alarm
after
Note:console
Performdeactivation.
the steps below in the listed order until the
fault disappears:
1. Reset the unit according to the fault source.
2. Reset the BTS using block or unblock.
3. Replace the unit according to the fault source. Failure in replaceable baseband unit
Add licenses to the Centralized License Server to avoid call
limitation.
See "Centralized
Perform License
the following Server
steps in theHelp"
listeddocument
order untilinthe
NOLS
fault
for details.
disappears:
1. Reset the Flexi Zone Micro BTS/Flexi Zone Access
Point.
2. Replace the Flexi Zone Micro BTS/Flexi Zone Access
Point.
No action
Note: is required.
Perform the steps below in the listed order until the
fault is resolved:
1. Reset the BTS using block or unblock.
2. In case fault source is BBMOD, replace the extension
baseband module (FBBx) according to the fault source. Failure in replaceable baseband unit
1. Check the optical cable and the SFPs on both ends of
the optical interface and replace hardware if needed.
2. Restart the radio unit connected to the affected optical
interface.
Check all the alarms posted by the Flexi Zone SFN

Antenna prior to the Z3 link failure.
1. Verify that the ANTMOD or APANTMOD provisioning
data
If thehave
targetbeenSFNcorrectly
Antennaentered.
does not physically exist, ignore
2. Verify if the siteID
this fault or clean it up provisioned
by deletingon the
the SFNSFN
target Antenna was
Antenna.
entered correctly.
Otherwise, perform the following steps:
1. Check all other alarms posted against the target SFN
Antenna.
2. Check the alarms raised on the SFN Antenna through
WebUI.
resolved.
1. Execute
Unblock theBTS
Flexiblock
Zoneand/or unblock to
SFN Antenna to reset
cancelthe
theBTS.
fault.
2. Check the connectivity:
Add licenses
AirScale: to the
Ensure Centralized
that the moduleLicense Server
is properly to avoid to
connected the
traffic limitation.
the rack.
See
Flexi:"Centralized
Check the sRIOLicense Server Help"
connection document
between cores. in NOLS
for details.
3. Check that Secondary core is configured in dual core
mode.
4. Check the SW version on Secondary core if it is the
same as Primary core.
5. Replace the faulty unit.
1. Perform a reset of the Flexi Zone SFN Antenna.
2. If step above does not help, perform a reset of the
BTS/FZAP.
3. If steps above do not help, replace the alarming module.
BTS/FZAP.
BTS/FZAP.
BTS/FZAP.
BTS/FZAP.
1. Check all alarms posted by the Flexi Zone SFN Antenna

1. Perform
prior to thisafault.
reset of the BTS or FZAP.
2. If step above does not help,
2. Check the configuration of the replace the alarming
Flexi Zone SFN Antenna
module.
against similarly-configured Flexi Zone SFN Antennas of
the same type.
3. Reset the Flexi Zone SFN Antenna.
4. Reset the Flexi Zone Micro BTS or Flexi Zone Access
Change the configuration for BTS as BTS secondary core.
Point.
1. Check if the secondary core is not configured as the
primary core. Correct the configuration file (scf) for the unit
and commission the unit once again.
2. If configuration of the unit is correct (both cores are
None
configured for dual core operation, primary core is
configured as primary and secondary core is configured as
secondary) block and/or unblock the BTS to reset the BTS.
1.
TheExecute
reasonBTS of theblock
faultand/or
may be unblock to reset
an internal BTSthe BTS.
software
2. If it does not help, ensure that both modules are properly
problem.
connected to the rack.
3. If it does not help, replace the secondary module with a
Enable
new module.power feeding towards the Radio Module by
switching
4. If it does the
notRF power
help, on inback
mount the the
BTSsecondary
Element Manager,
module or
at the front panel of the PDU.
and replace the primary module with a new module.
1.
5. Disconnect
If it does notthe optical
help, cable
replace thefrom the peermodule
secondary systemwith a
module
new module where theis,
(that radio
newmodule
modules visible as the
on both alarm
sides source
of the
is connected.
rack),
2.
6. Ensure
If it doesthatnotWCDMA peer the
help, replace system
rack.module supports
RAN3331.
3. Ensure that no WCDMA peer system modules use the
Check
same IP if the
set.fault source
IP set used WCDMA
by WCDMA peer
peersystem module
system module
supports
is determined by the OptIf in the LTE system module it of
feature RAN3331. If not, update the software is
the peer system
connected module.
to (OptIf 1-3 in the same FBIP uses the same IP
set, and OptIf 4-6 in the same FBIP uses the same IP set).
4. Restart the peer system module where the radio with
changed configuration is connected.
5. Connect the optical cable to the peer system module.
If
theyou same do not wantand
IP set, to wait
OptIffor 4-6the in next attempt
the same FBIP of cell
usessetup
the
CDMA
result: System Modules. The following mode combinations
same
are IP
allowed: set.)
2.
4. Read
Restart thepeerdiagnostic information in the alarm,
1.1. LTE eNB issystem
in secondarymodulemode where and theCDMA
configuration
BTS is in was
changed.
primary mode.
If
5. the
Connectalarm is reported
optical cable because
to peermode the
system baseband
module. resources
1.2. LTE
are unavailable, eNB is in stand-alone
perform one of the following and CDMA BTS is
actions:
disconnected
a. Reconfigure from the radio.
the cell, for example, reduce the bandwidth
For
2. If NR-LTE
the alarm sharing:
additional information contains "Incorrect
of
1. the cell
In case of in order
NR-LTE to reduce
sharing,the capacity
configure of the
the RF baseband
secondary
resources functions
necessary configuration
for the cell. for CPRI-A RFsharing
Sharing",
mode
reconfigure correctly the on
CDMAbothBTS NR and to LTEboth
give side.SW and AISG
b.
2. Try
In case to reallocate
NR-LTE the existing
sharing is not cells to free RF
intended, the sharing
needed
management
resources, thatfunction
is, basebandcontrol to the
cards. secondary controller
should
(LTE be disabled in SCF.
c. TryeNB). to allocate a new cell at other resources.
3. If the previous steps do not help, reset the alarming radio
unit.
If the alarm is reported because
AirScale
1. Read BTS
the TDD,
diagnostic AirScale BTSthe
information FDD,C-Plane
theFlexi
inreset alarm. resources
SBTS, are
4. If the previous
unavailable, perform steps one doofnotthe help,
following the LTE eNB
actions:
AirScale
2. If theCDMA SBTS,
alarm BTS. Flexi BTS FDD, Flexi
is reported because the baseband resourcesBTS TDD:
and/or
a.
areDistribute
Read the alarm
unavailable, the diagnostic
cells
add ABIAequally info.among
extension If the the baseband
diagnostic
card infocards.
or reallocate is "The
the
b. Add
current ASIx
sync card
input
cell to other resources. in case
source that
is nothalf an rack
allowedconfiguration
source is
for
used
If the in
OTDOA the
alarm BTS.
operation
is reportedas configured
because the in otdoaProfileList.",
C-Plane resources are
c. Add
execute
unavailable, a new
followingAirScale
perform steps: in case
one of the offollowing
full rack actions:
configuration.
1.
1. Execute
Distribute
Modify thesitecells
allowed reset manually.
between
sources in both
OTDOA: AirScales (old andcards.
otdoaProfileList new).
to
a. Distribute the cells equally among the baseband
include
b. Add current
ASIxnot card synchronization
in case source.
that half rollback
rack configuration is
2.
2. If
If itthedoesmodificationhelp, execute
in step 1 SW is not possible, to previous
check other
used
version in the BTS.
of the related
SW. to synchronization issues and follow
active
c. Add alarms a new AirScale in case of full rack configuration.
their
Distributeinstructions.
the cells between both AirScales reset (old and new).
3.
3. If
If itthe
In case does
of not help,
previous
single stepexecute
core has been
scenario configuration
executed
check and the
if module and
fault is
providing
recommission
reported again,the
signal is working. and BTS.
if external GPS receiver is used:
a. Checkofthe
In case Dual antenna placement to remove possibility of
Core scenario:
4.
1. If
signal
Waitit does not help, replace
interference.
for Secondary Unit reset.the faulty system module or
BB
b. module.
Replace GNSS unit/cable.
2. If it does not help, replace the unit one by one in the
order below:
If
a.diagnostic
primary unit info is "The
(ASIx estimated phase error at the air
primary)
interface
b. secondary with unit
respect to secondary)
absolute time has exceeded the
Check
configured frequency configured in BSCthen
(ASIx
otdoaPhaseErrorThreshold (when GSM sector
in otdoaProfileList.",
c. AirScale
frequencies subrack
overlaps another RAT cell frequency) orbyin
bring phase error back to below the threshold value
RNC (when WCDMA
doing the following steps: cell frequency overlaps another RAT
cell/sector frequencies) or in SBTS
1. Check if synchronization source is properly connected. (when LTE cell
frequency
2. If the previous overlaps stepanother
has been RATexecuted
cell/sector andfrequencies)
fault is
and correct them in order to avoid
reported again, and if external GPS receiver is used, the overlapping.
perform the following actions:
a. Check antenna placement to remove possibility of signal
interference.
b. Replace GNSS unit/cable.
Check the connection between the system module (master

system module if BTS uses more than one system module)
and
The the
1. This BTS Mediator.
alarm
operator can be trigger
should visible SW
due update
to a maintenance
for the BTS to the
operation
requestedon SWthe network
version. or on
After a partnerSW
successful eNB. In such
update:
case,
1. ThetheBTS alarm willonAir
will be be cancelled
with the shortly
requested(up SW
to 10min) after
running.
the maintenance operations
2. The SW will be consistent in BTS. are finished. Therefore, no
action
3. SW is needed.
fallback fault and the related alarm will be"Reduced
canceled.
1.
2. Confirm
When this if the referenced
alarm is visibleradio HW
permanentlysupports
or occurs without
LTE Guard with
correlation Band" function. operation (see 1.), then the
maintenance
2. If radioactions
following supports "Reduced
should LTE Guard Band" function,
be taken:
configure an acceptable reduced frequency offset
a. Verify the correctness of the configuration that is
of network
within the radio HW capabilities.
devices (hosts, switches, routers) handling X2 traffic
between eNB, and partner eNB, and remove
inconsistencies or errors if any were found.
b. Verify the stability of the partner eNB and correct the
issues basing on the result of the diagnostics.
When the battery backup in the base station is used, check

the root cause of the mains power failure in the base
station.
2. Depending on the case, follow appropriate instructions:
a. When the IP address limit has been reached due to
limitations applying to the above listed radio modules,
proceed with one of the following:
- Replace the radio modules with newer models that do not
fall under limitations and reconnect the failed radio module
to restart the radio module detection process.
- Provide
Note: a newthe
Perform BTS andbelow
steps connect radio
in the modules
listed to it ifthe
order until
replacement
fault of older radio modules is not possible.
is resolved:
b. When the number of radio modules does not exceed
If
1.the
BTSReset GPS theis extension
support configured
limit, restart as
thea BTS
baseband reference
at an clock,
module perform
appropriate
according to the
time.the
following:
fault source.
1. If the TRX is locked by BSC,
1. Check the GPS receiver installation. then first unlock the TRX
and
2. then unblock the carrierstatus.
group to cancel the fault.
2. Check
If itthedoesthenot
GPShelp,receiver
resetatthe BTS using block the
and
3. Check the connection between then
unblock.
TRX is unlocked BSC, unblock
the GPS receivercarrier
and
group
FSM. to cancel the fault.
3. If it does not help, replace the extension baseband

If the TOP
module signal istoconfigured
according as a reference clock,
the fault source.
perform the following:
1.
If Check
the alarmthewith
connection
the fault to the TOP
happens server. please
frequently,
Flexi SBTS, AirScale SBTS, Flexi BTS FDD, AirScale BTS
configure
FDD: the fault to trigger symptom data collection using
5G BTS, AirScale BTS FDD, AirScale BTS TDD,
MRBTS/TRBLCADM/faultSnapshotTriggers. When AirScale
1. Check
SBTS, theBTS
Flexi configuration
FDD, Flexi ofBTS
sync/time
TDD, reference
Flexi SBTS: sources
symptom
in the data
System is collected,
Module. inform Nokia support to
1. Check the
investigate whyconfiguration
the fault is of the sync/time reference
reported.
2. Checkinthe
sources the status
System andModule.
installation of NTP servers. If they
The
failed,fault is
restoreraised
the only when
identified the
failingAntenna
NTP Path Delay
server.
2. Check the status
Measurement feature andis installation
enabled. If of NTP
this servers.
feature notIf Hub
3. Check
failed, the status
restore the and installation
identified failing NTPof GNSS
server.or is
Sync
needed,
Master. then
theythe faultrestore
can bethe cleared by disablingGNSS the
3. CheckIfset
feature: status
the
failed,
and installation
parameter ofidentified
GNSS orfailingSync Hub or
Sync
Master. Hub Master.
If failed, restore the identifiedtofailing GNSS or Sync
actAntennaPathDelayMeasurement FALSE. Otherwise,
Hubfollowing
the Master. perform the following procedure to clear the
4. Check status and installation of BSC time reference
fault:
source. If failed, restore identified failing BSC time
reference
No action source.
1. Increase isthe radioto
needed output
clear power
the fault. to at least
This 5 watts
is only a (37
dBm).
notification to show why a TRX or TRXes of the sector are
not on-air at BSC.
2.
ThisExecute radio
fault gets reset manually.
cleared when SBTS receives the system
information
Update from
commissioned BSC. parameters
3. If it does not help, check antennasoconnections
that LNA::gain then+reset
PASSDEV::additionalRxGain
the radio manually. - ANTL::totalLoss is equal to
or greater than 5 dB. The LNA is connected to the ANTL
with
4. If itLOGLINK
does not of linkModeData.
help, reset the BTS. The PASSDEV is
connected to the ANTL with LOGLINK of linkModeData.
5. If it does not help, execute sw rollback to previous
version of sw.
6. If it does not help, replace the faulty radio module.

1. There might be a malfunction in the GPS or GNSS
receiver. Perform a (remote) power reset for the GPS or
GNSS receiver module of Access Points listed in Additional
Alarm text.
Refer to the additional information to correct the value of
the parameter "IPNO:cPlaneIpAddress",
"IPNO:cPlaneIpv6Address", "IPNO:uPlaneIpAddress," or
GNSS SW Upgrade is ongoing.
"IPNO:uPlaneIpv6Address" In case
to match theGNSS SW
one configured in
Upgrade
RCP. is interrupted, based on GNSS receiver type, BTS
could retrigger the update up to 3 times if needed. After all
attempts are used, alarm due to fault 4272 - GPS receiver
BTS
alarm:restart is needed firmware
recommended in order to
is shutdown
not in use Power Group. If
is reported.
it does not help, contact Nokia support to investigate the
issue.
Note:
For FYGM/AYGM receivers, in case of interruption, BTS
does not retrigger automatic the GNSS SW Upgrade, alarm
due to fault 4272 - GPS receiver alarm: recommended
firmware is not in use is reported directly.
Follow the steps below to resolve the fault:
1. In case of NR-LTE sharing, configure the RF sharing
mode correctly on both NR and LTE side.
2.
If the In case fault NR-LTE
is present sharing
because is not theintended,
FHS Delay RF sharing
should
Compensation
1. Reset the BTS. be disabled feature in SCF.
is enabled and a CPRI-A radio is
directly
1. Check If another connected
if the to
synchronization a baseband
values of the following unit, the
referenceparameters fault
is present, check can be
1.
cleared
that Ensure
its by
phase there
disabling
is is enough
alignedthe FHS
to S-Plane
the Delay
GNSS IP Addresses
Compensation
signal; check allocated
feature
whether
configured
2. IfFZAP
it does to
notcalculate
help, in if thethe
report cellfailure
is sleeping
to Nokia makes the
for
ifthe the feature
cable configured
delay is not
from thethe
needed: GNSSFZC.
setfault Theparameter
the
receiver S-Plane IPsupport
is correctly pool size
false
because alarms the reported:
root cause of the is possibly a software
can be checked using
actFhsDelayComp
compensated. the "show
to FALSE. flexizoneifsplane-ptp-vlan
Otherwise, the FHS Delay
a.
error. autRrcBasedSlCellDetHCheckFreq
ipconf"
Compensation SCLI command.
feature
2. autRrcBasedSlCellDetRrcSuccRateThr
Check accuracy of the manually-entered is needed then disconnect coordinates,the if
b.
2.
CPRI-A If GNSS receiver operates in the surveyed mode. SCLI
not, use
radio
theautRrcBasedSlCellDetRrcVolThrthe
from "setthe flexizone
baseband splane-ptp-vlan
unit. ipconf"
c.
command
3. to update theaftersizeholdover,
of the S-Plane checkIP pool bythe
d. If the fault appeared
autRrcBasedSlCellRecPh1Timer whether
changing
If
BTS the the
fault raised
could start
accumulate address
when error and
a CPRI-A above the stop
radio
150 address.
isus.connected to the
e.
If autRrcBasedSlCellRecPh2Timer
GPS is configured as a Length
reference clock, perform
3.
BTS
4.
f.
Otherwise,
Check while if the
the contact
Fiber
autRrcBasedSlCellRecPh3TimerGNSS Nokia
Linksignal Support.
is Extension
spoofed. feature the is
following:
enabled but FHS Delay provides
Compensation isphase,
disabled, the fault
5.
1. If
Checkthe GNSS
the GPS receiver
receiver installation.correct restart the
can
BTS.
For be cleared
example, by one of the following:
autRrcBasedSlCellDetRrcSuccRateThr is
2.
-100, IfCheck
the the LinkGPSLength receiver status. feature is not needed
6.
3. If
Check orFiber
the GNSS
timers
the receiver
are very short
connection
Extension
isbetween
faulty,
(for replace
example,
thetheGPS the receiver.
2receiver
minutes) and Do
and
the
not
temporary fault
restart can the be BTSclearedbefore by disabling
the GNSS
short-term RRC degradation makes the alarm feature:
receiver is set the
replaced.
ASIx.
parameter actFiberLinkLengthExt1 to FALSE.
reported.
- If the Fiber Link Length Extension feature is needed but
If
the the TOP signal is
is configured asfault
a reference clock, by
2.
perform If,CPRI-A
after the theradio
parameters
following:
not, then are the changed, can thebe cleared
alarm is
disconnecting
reported only thethe
for CPRI-A
single radio
cell, fromalso
and the BTS. for cells
1. IfCheck
-configured
both the theFiberconnection to theExtension
TOP server
on the Link sameLength radio modules, feature the
execute andradiothe
CPRI-A
module radio
reset. are
If itneeded
does
5G BTS, AirScale BTS FDD, AirScale BTS TDD, AirScalenotthenhelp, the fault
execute can FSP be cleared
reset by
(cells
enabling
are supported the FHSby Delay
the FSP).
SBTS, Flexi BTS FDD, Flexi BTS TDD, Flexi SBTS: Compensation
If it does not feature:
help, set
execute the BTS
parameter
This fault isactFhsDelayComp
reset. cancelled when SSH to TRUE.
configurationEnsureisall CPRI-A
updated
radios
correctly on all instances of the LFS platform which areunit.
are connected to a FHS instead of a baseband part
3.
of If, theafter BTS.the parameters are changed, the alarm is also
reported
Manuallyfor other cells
re-apply the SSH configured
configuration on other radio modules.
change.
If
In case of SSH port configuration failure try are
it does not help, execute FSP reset (cells supported
configuring a
by
different
This the FSP).
fault post
is If it
number
canceled does not
in
when help,
range. the execute
BTS sees BTSthe reset.
level of PIM
5G BTS, AirScale BTS FDD, AirScale BTS TDD, AirScale
being
SBTS, detected
Flexi radio BTS byFDD,
the EPIMC Flexi BTSis either
TDD, lower than the Minor
4. If manual
threshold, or the reset and/or FSP resetFlexi and/or SBTS: BTS reset
Set
do the passwords of all BTS
not help, collect the logs and provide them toisNokia user accounts covered by this
EFaultId_ExtPimPerformanceMajorThresholdAl
fault to non-default values that satisfy the password active.
support for investigation. Alternatively, perform the
policies,
Read
following alarmor deactivate
diagnostic
actions to replacefeature.
information
the hardware: and based on this,
All
please products:proceed accordingly.
a.
See Replace
fault diagram:radio modules if the alarm is reported only for
http://oam.emea.nsn-net.net/
All
cells products:
configured on the same radio module.
search
In
This case: fault indicates a potential degradation in theifantenna
b. Replace baseband cards
FaultMgmt_Fault4464EFaultIdExtPIMPerformanceMinorThr and system module the alarm
-line
is connection
of the RX
reported fortopath
hotel
cells duememberto losethat
configured antenna
on belongs
various to other
connection,
radio BTS
modules. water
esholdAl
hotel
intrusion, for
is detected, the requested
damaged check
cables, branch.
if there
lightning is no damage,
mistake in hotel
external
This
member faultinter-connections.
is cancelled if the Iffeature no,tothe activation
of the flag ishotel
set to
structures,
false, or the orsite
physical damage
configuration is theID
updated antenna to fit
BTS
assembly.
within an
All
has
Passive products:
to beInter-Modulation
adjusted in the configuration in the antennaplan linefor the cannot
cabling
EPIMC
Repair FHS
or retune supported
the antenna configuration.
problematic
be effectively BTS.
removed by the system at the site
PIM Cancelling to reduce
function on
the
-the amount
connection
External ofto
PIM PIM
a products
hotel member
Cancellation beingHW with generated.
duplicated
unit if hotel
All
member products: ID has been detected, please check the
actExtPIMCancellation
See and extPIMCancellingEnabled
fault diagram:ofhttp://oam.emea.nsn-net.net/ are
parameterization
set to true. Fix the affected BTS.
referenced antenna line cabling to
search
-remove
the number of detected
the source of the hotelpassive
FaultMgmt_Fault4466EFaultIdExtPimCancellationHwLimits
members in the BTS hotel
intermodulation
does not match the configured expected number, check
interference.
ExceededAl
10GE connections for thebetweenrequested hotelbranch.members and
parameterization of Hotel Member ID as well as make sure
All
thatproducts:
software builds installed on all BTS are compatible.
Reconfigure
- primary 10GE theconnection
site to reduce is not theavailable,
number RX/TX check channels
if:
being targeted for PIM cancellation.
a. configuration with external switch: Connection between
SEI1 port 1 (pigtail 1) to external switch is present.
b. configuration without external switch: Hotel Member
assigned ID 1 is present in the BTS hotel and there is a
10GE link connected to it.
Section B: Check on the radio module side:
1. Check if the connector seal is properly mounted and is
firmly in place.
2. Check if the small form-factor pluggable (SFP) is
properly connected and/or mounted in the RF module. If
the SFP's connection and/or mounting is not correct,
Depending
readjust theon the case: and/or mounting.
connection
1)
3. incompatible
Check if 10GE software
the optical cable installed
is properlyon both BTS - validate
connected and/or
Check
software thebuilds on cable
BTS connection
that are a going
part of through
the BTSthe hotelSEIand
mounted
interface in the
between SFP. BTS working in the same BTS hotel.
align
4. Cleanit withthe problematic
optical BTS correspondingly.
connectors at the RF module end.
Check
2) failure VLAN configuration on the switch,isifdetected BTS hotelrestart
Reset theinRF
configuration
L2/L3
hardware
with
address
the unitassignments
switch and
is in check
use. if this solves -the
the BTS
problem.
3) wrong switch configuration is detected: check if the
10GE
Sectionconnections
C: Check the to external switch ports are correct and,
optical connection:
if needed,
1. Check ifswitch the opticalconfigurations
cables arelike notassigned
over-bent. VLANs
If theytoare,
ports
replace and themake optical sure ports since
cables, are isolated
overly in no other
bending theway.optical
fiber cables damages the cables and can detach or
damage
Enable feature the connectors.
"LTE2371: Flexi Zone Controller Shared
2. OPTIONAL:
Backhaul Support Test- Phase
the fiber II"cable
or remove (for example, measure
the southbound
the
5G optical
BTS:
logical attenuation)
interface (deactivate fromfeature the system LTE4565).module end. Check
measuring
If the BTS is equipment
not automatically documentation updatedforbyinstructions.
NetAct, update
Check
3. OPTIONAL:the parameters Test offiber
the cable
frequencies against the
the BTS with the SWthe version running (foronexample,
the BTSmeasure
before
RNC/BSC
optical configuration.
attenuation) from the RF module end. Check
the SW
AirScale update
BTS causing SW fallback.
FDD: either via recommissioning of the
Mismatch
measuring isequipment
corrected documentation for instructions.
NOTE:
Execute Infollowing
Note:orPerform case BTS
the Element
steps
steps below
to clear Manager
inthethefault: detects
listed orderanuntil
incorrect
the
BTS the controller (RNC or BSC).
SW version,
fault is resolved: the BTS Element Manager should be
If
1.the alarm continues
reconnected.
Reset after executing steps from sections
Check the which BTS sub using
bands block of bandand unblock.
46 are allowed in the
A, B, and
2. If it does C, replace the RF module.
not help, replace the extension baseband Optionally, the minor
country of operation.
and/or
AirScale
module also major
SBTS,
according BER thresholds
Flexi SBTS: can
to the fault source.false be increased
If alarm with turned
or the fault off
Please note actUnlicensedDfs= causes
to avoid the
happens frequently, alarm reporting.
subbands 46B (U-NIIplease 2A) and configure
46C (U-NII the fault
2C) toto be
trigger
The
symptomBTS (cannot
disabled start-up
data collection
bewas notusing
used) successful.
even if they are allowed in the
MRBTS/TRBLCADM/faultSnapshotTriggers.
country. When
If the faultdata
symptom is reported
is collected, with Critical
inform severity
Nokia support and the toSW is
not
2. consistent
investigate
Next execute why in the
the
either BTS,
faultstep is then
reported.NetAct
2aoforthe 2b ASIRMOD autonomously
or 2c.
1. Determine
triggers an SW the Master
update witheNB immediate activationused for thefor the
cell.
BTS
2a.
2. UseIntopart(s)
the SW
ASiManager
version running
representing to must
connect allowed on BTS.
to the subeNB If this ison
band(s) not
identified in step
possible, the operator
MRBTS/LNBTS/LNBTS_FDD/LAA/LNUPR.uCellChannelSL update the SW update
1 and check
immediate faults reported
activation for the in
BTS ASiManager.
to the SW Follow running
version
ist set number
instructions of of subsequent
those faults and "1"s equalthe to fault
or higher than
on the BTS.
1. Determine
number of LAA After
the successful
Master
cells eNB
configured SWofcorrect
update,
the
on theASIRMOD
same
situation.
the radio
following
used and forwill
the
occur:
cell.
assigned to the LNUPR instance (LNCEL_FDD.lnuprId
1.
2. The
Use to
points BTS will beinstance
ASiManager
LNUPR onAir with
to connect the
assigned to previously-running
thetoeNB the LAAidentified SW.
cell). in step
2. Thecheck
1 and SW will be consistent
faults reported ininASiManager. BTS. Follow
3. The BTS of
instructions
2b. willthose
reportfaultsactive and SW fallback
correct thefault
faultbut with
situation.
Reduce the number of LAA cells configured on the same
radio and assigned to the LNUPR instance to make number
If
ofthe fault is reported
subsequent with Major
"1"s in part(s) severity and
representing SW issub
allowed
consistent
band(s) in BTS, then
onconfiguration of the LNA the operator should trigger SW
1. Fix DC
update for the BTS to the requested SW version. After
MRBTS/LNBTS/LNBTS_FDD/LAA/LNUPR.uCellChannelSL
successful
ist is equal SW to orupdate,
higher than the following
number of willtheoccur:
LAA cell.
2.
2c The SW will be consistent in BTS.
3.
You SW can fallback
also set fault"1s" and the related
in each position alarmof will be canceled.
MRBTS/LNBTS/LNBTS_FDD/LAA/LNUPR.uCellChannelSL
ist if it does not matter for you which channels in which sub
bands allowed in the country can be used for LAA cells
assigned to the LNUPR instance.
Check
To clearwhether ASIRMOD
this fault, perform istheconfigured in place of RMOD
following steps:
or vice versa. Correct this configuration,
1. Wait until the next round of Network-wide thenRFrecommission
Scan Test
the BTS or
is executed.correct hardware connection.
2. If the fault still occurs after the next round of RF Scan
Test, user needs to check the limitations of the RF Scan
Collector. See RF Scan Collector documentation for more
details.
To clear this fault, perform the following steps:
1. Wait until the next round of Network-wide RF Scan Test
is
Toexecuted.
clear this fault, perform the following steps:
2.
1. IfIf the fault still
problem occurs
occurs afterafter the next
feature rounduser
activation of RF Scanto
needs
Test,
check user needs to
configured IP replace
address. the Radio Module, then
AirScale
perform
To BTSfault
clearuntil
the FDD:
Network-wide
execute RF the
Rx-sniffing
following Test again.
steps:
2.
ToWaitmake pMaxLaa the next round
value forofLAA
Network-wide RF Scan
cells calculated Testis
by eNB
is
equalexecuted.
or bigger than minimum transmission power level
1.
3. Check
User needsif radio
to module
check hasstatus
the Rm.HW.Country.Code
and
supported
parameter by radio
valueSee module
consistent execute
with onelimitations
or more of
lteUItuRegion.
of the
RF
Scan
following Collector.
actions: RF Scan Collector
To clear this fault, perform the following steps: documentation for
more
-If reducedetails.
value
1.lteUItuRegion of
Wait until the next roundtheof Network-wide RF the
Scan Test
=0 (USA), radio supporting LAA
MRBTS/LNBTS/LNBTS_FDD/LAA/LNUPR.antennaGain
is executed.
cells(s) shall have Rm.HW.Country.Code = 'US'.
(it
2. shall
User be executed
needs to checkfor the
LNUPRstatus instance assignedoftoRF
and limitations the
LAA
Scan cells. LAA cell is assigned to LNUPR
When lteUItuRegion has another value than 0, e.g. 3 for
Collector. See RF Scan Collector instance
documentation when
LNCEL_FDD.lnuprId
more
(ETSI)details. points the
the radio supporting to the LAA LNUPR
cells(s)instance).
shall have the
another value than 'US' of Rm.HW.Country.Code
and/or
Replace
OAM radio module
performs if there ischange.
a configuration inconsistencywill
between
-Rm.HW.Country.Code
reduce number of LAAandcells configuredFault be
on the radio
canceled
module after RAP reset.
MRBTS/LNBTS/LNBTS_FDD/LAA.lteUItuRegion.
and/or
Internal
2. If sub logsbandcollected
46B and/orby this
46Cprocess
is enabledcaninonly be analyzed
-LNUPR.uCellChannelSList
byreplace
Nokia radio
R&D. module with check
radio module supporting to
if radio configured lower
value of transmission power.
support cells assigned to the LNUPR supports DFS i.e. its
Additionally:
parameter Is.Dfs.Ready= true. If the parameter value is
-'false'
Check the alarm
replace history
the radio to confirm
module with the frequency
radio of fault
supporting DFS
4527 in a is
(LAA cell specific gNB.
assigned to LNUPR instance if
-LNCEL_FDD.lnuprId
Check the alarm history fortoother
points alarms in
the LNUPR the same gNB
instance).
that might be related, especially alarms with Radio alarms
If an alarm with fault 4527 frequently occurs in the same

Correct hardware
gNB, alarms connection
with the configurations
same faults mentioned so that are
above are
supported
present in accordance withe the fault meaning.
If GPS isinconfigured
the same gNB,as theorreference
the gNB performance
clock, do the is
degraded,
following: then collect a snapshot and open a case for
Nokia R&D
1. Check thelog analysis.
GPS receiver installation.
2. Check the GPS receiver status.
Each RU the
3. Check crash are reported
connection with own
between 4527receiver
the GPS fault and the
system module.
If the TOP signal is configured as the reference clock,

check the connection to the TOP server.
For CBRS services, adjust desiredPmax and antennaGain

configurations to enable the TX power level meet the FCC
limitation.
Enforce a cell setup to try to recover the cell from the failure
by manual cell
Disconnect locking,
theupdate
PDU fromcell’s
theparameters modification via
secondary core.
1. Check
delta and
configuration theif configuration
plan needed, and parameters.
cell unlocking.
2. Load the correct commissioning file to the BTS.
3. Block
If the and unblock
problem the
persists, BTS. the NRCELL MO and
remove
4. If activities mentioned above
recreate it will appropriate parameters don't help contact Nokia
setting.
technical support.
If the problem still persists, try the following:
1. Check and update the configuration parameters.
3. Block and unblock the BTS.
1. Check
Refer if the
to the values of
LTE4560 the sleeping/ cell
/ 5GC002083 thresholds and
5GC002324
timer values are too short. Parameter settings
customer documentation for detailed explanation may
of cause
each
false alarms to be triggered when intermittent detection
parameter and how each sleeping cell scenario is detected.
occurs. Refer to the LTE4560 customer documentation for
detailed explanation recovery
If the recommended of each parameter
mechanismsandarehowconfigured
each
sleeping cell scenario is detected.
and they do not resolve the sleeping cell, collect the logs
and provide them to Nokia support for investigation.
2. If the recommended recovery mechanisms (baseband
reset
If the and/or BTS siterecovery
recommended reset) domechanisms
not resolve the
are sleeping
not and
1.
cell, Check if the
collect the values
logs andof provide
the sleeping
themcell thresholds
to Nokia support for
configured:
timer values are too short. Parameter settings may cause
investigation.
-false
perform thetoreset of the impacted RMODs; detection
alarms be triggered when intermittent
-occurs.
if previous action din not resolve
Refer to the LTE4560 customer the sleeping cell, perform
documentation for
the reset of the impacted BBU;
detailed explanation of each parameter and how each
-sleeping
if previous
cellaction din is
scenario not resolve the sleeping cell, perform
detected.
the reset of the impacted BTS.
2. If the recommended recovery mechanisms (baseband
reset and/or BTS site reset) do not resolve the sleeping
cell, collect the logs and provide them to Nokia support for
investigation.
This fault is cancelled when calibration is performed

successfully.
If "Concurrency operation is ongoing" is displayed in the

alarm diagnostic info:
The calibration operation could take longer time. It could be
- wait until there is no ongoing SWM operation, CM
aborted manually from WebEM.
operation or BTS reset;
- try to make a new copy via command or wait until next
scheduled sync.
Start
If EPIMC
"Critical calibration
or major alarmtoexists"
cancelisthe fault. in the alarm
displayed
diagnostic info:
- clear the critical or major alarm if present;
-If try
FSPto reset
makeand/or
a new Site
copyreset
via command or wait
do not help, until
collect thenext
logs
scheduled
and providesync.them to Nokia support for investigation.
If "Error due to different active SW version in dual core
Baseband reset/SiteinReset
mode" is displayed is needed
the alarm in order
diagnostic info:to switch on
Optional
- ensure that both cores are detected and have theNokia
Power Group. If it does not help, contact same
support
SW to investigate the issue.
version;
-1.try to make
Lock a new
/ Unlock thecopy
cell. via command or wait until next
scheduled
2. Reset board. sync.
3. If step 1 doesn't solve the issue, contact vendor support
If
team."SW integrity check failure" is displayed in the alarm
diagnostic info copy retry should be forbidden.
1.
ToCheckrecover and
theupdate the configuration
BTS perform parameter
a SW rollback or perform a
NRCELL.beamSet.basicBeamset
SW update with same or different version.
3.
If Activate new plan on theisBTS.
1."Copy
Doubleoperation failure"
check network plandisplayed in the
and correct alarm
either the value
diagnostic info:
of defaultCarrier in SCF or DL UARFCN of paired WCDMA
-cell
ensure
in RNCthere is enough space
configuration, so thatinboth
passive file are
values system;
same.
-2.try
If defaultCarrier parameter value is changed,until
to make a new copy via command or wait next
WCDMA
scheduled sync.
RAT reset and paired LTE cell startup is triggered
automatically.
3. If RNC DL UARFCN is changed, WCDMA cell is
locked/unlocked by RNC automatically and paired LTE cell
startup is triggered automatically.
1. Block/unblock LTE cell

2. If alarm still existing, reset SBTS
1. Disable MNL/MNLENT/FEATCADM/actKpiAlarms;
2.Inside MNL/MNLENT/TRBLCADM/kpiAlarmTriggers
structure, change any parameters related to faultID
(formulaDescription, timeToTrigger, triggeringFormula) or
simply remove
1. Disable entry for faultID;
MNL/MNLENT/FEATCADM/actKpiAlarms;
3. Change
MNL/MNLENT/TRBLCADM/kpiAlarmMutingTime;
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove entry for faultID;
3. Change
1. Disable MNL/MNLENT/FEATCADM/actKpiAlarms;
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove
3. Change
simply remove entry for faultID;
3. Change
None
None
Check whether the cell's frequency band and PLMN are

configured correctly
Alarm with the fault isand are supported
reported to informby the RF module.
customer about
last BTS reset cause and timestamp.
Reset cause and timestamp are available in alarm
additional info.
No additional action is needed due to the fault.
- reregister NE3S
- modify or clear nmsIntegrationIpAddress
None
Correct the LTE cell configuration.
PRBs blanked by LNCEL_FDD.numBlankDlPrbsDown and
LNCEL_FDD.numBlankDlPrbsUp shall overlap totally the
selected radio filter guardband (slimRfFilterDL).
PRBs blanked by LNCEL_FDD.blankedPucch and
LNCEL_FDD.selectOuterPuschRegion shall overlap totally
the selected radio filter guardband (slimRfFilterUL).
1.
Check Check if the values
CPRI-K of the sleeping
cable connectivity cell thresholds
on BBMOD / RMOD and
timer
side, values
and CDMA are tooside. short. Parameter settings may cause
Small Cell:
1. The operator should match the version number sent by
occurs. Refer to the SR002362 customer documentation for
CBSD with the version supported by SAS. If two do not
detailed
1. Check explanation
if the values ofofeach parameter
thetosleeping celland how each
thresholds
match,
Recommission
sleeping
then
cell
either
the connect
scenario
SAS supporting
NRCELL-beamSet.tiltOffset
is detected. to theand
version being
timer
used
Radio’s values
by CBSD
supported areortoo short.Nokia.
contact
steering Parameter
range. settings may cause
2.
occurs. If the Refer
recommended to must
the SR002362 recoverycustomer mechanisms (baseband
2. The operator remove the conditiondocumentation
that led to the for
reset
When
detailed and/or
parameters BTS
explanation site
need reset)
to
ofofeach be do thenot
parameter resolve
same for
and the
allhow5Gsleeping
cells
each
blacklisting
1. Check of the
if the CBSD.
values Thesleeping
the eNB willcell periodically
thresholds retry the
andfor
cell,
within
sleeping collect
a the
configuration
cell logs
scenario andblock
is provide
:
detected. them to Nokia support
Feature
timer valuesData Exchange Request for the failed CBSD and
investigation.
1.
after Check several andare too short.
update
attempts, the Parameter settings
configuration
thebaseband
eNB so that
willintermittent
attempt to
may cause
parameters
deregister
false
If
that all alarms
radios
need to to be
connected
bethen triggered
the same to when
for allthe 5G module
cells within are detection
alostSAS
after
2.
the
occurs. IfCBSD
the Refer
recommended
and to the recovery
re-register
SR002362 mechanisms
CBSD
customer with (baseband
the
documentation for
protocol
configuration change: blocksite match.
reset
Server.
detailed and/or BTS
Ifexplanation
the5GC001698
fault reset)
continues
of each do
to not resolve
occur
parameter forand the
this, the
how sleeping
operator
each
Refer
2. Load to the
the the correct customer
commissioning documentation:
file to
into the BTS.
cell,
should collect
contact logsSAS
the and provideprovider.them Nokia support for
-sleeping
3. Change
Block cell
andthescenario
protocol
unblock ofservice
is
the detected.
baseband
BTS. module to initial value
investigation.
to get radios detected.
3.
-2. The theoperator
If the recommended must configure the missing parameters. logs.If
For
faults
Perform 5G
continue
the
FDD indicated
tocells
occur onrecovery
steps
ABIO mechanisms
towhere
collect and analyze
RACH (baseband
root sequence
reset
-exceeds and/or
Problemthe BTS
found site
and
limitand: the corrected: Repeat the upgrade eNB.
for
reset) the
do CBSD,
not try
resolve resetting
the the
sleeping
If
cell, the reset
collect fails,
the logs and operatorthem is certain thatsupport
all required
scenario
1. Check
parameters
to
and check
are update theprovide
if helps.
configured, configuration
then the
tosoNokia
operatorthatshould
RACH root for
-investigation.
Problem
sequence not corrected: Change the protocol to initial
contact
value. theisSAS within the limit
service supported
provider by BB module. The
or Nokia.
cell parameters that influence root sequence include
NRCELL.
4: The operatorprachConfigurationIndex,
mustconnected
change the NRCELL.
If at least one radio
zeroCorrelationZoneConfig, to invalid
NRCELL. baseband value whichiswill
module
result
detected in a and at least one radio is not detected: SAS
new registration for the CBSD wit the
totalNumberOfRAPreambles
Server. If the5GC001698
fault continues to occur, the operator should
Refer to the customer documentation:
try
- Changeresetting the
thefault eNB.
protocol If
to both of these
initial valuechange methods
to get MISSING fail, and the
radio
To
operatorclear the is certain BTS
that configuration
all required parameters is needed.
are
detected.
Either
configured,
Note: Radio then
unit in thenew operator
protocol should stayscontact
with newtheprotocol.
SAS
1)
servicereduce number
provider or of carrier
Nokia. aggregation partners in CA
-Reset
Perform
cluster the baseband
the
configuration indicated unitsteps
and supporting
restart to collect
the BTStheandimpacted
analyze cells.
logs.
-OR Problem found and corrected: Repeat the upgrade
5. If the CERT_ERROR
scenario to check if helps. fault continues to occur for a
2)
CBSD,switch the offoperator
Dynamic Spectrum
should return Sharing WCDMA-LTE
theprotocol
CBSD totoNokia if
-activated
Probleminnot the corrected:
BTS Change the
(LCLL.actWcdmaLteSharedSpectrum initial with
an indication that Feature Data Exchange Request for the
value.
= true ->
CBSD false)and
failed, andthat restart the BTS
a CERT_ERROR
Note: Until the subfeature 5GC001698-Cwas will received.
be
implemented, eCPRI radio unit cannot be upgraded back to
6. None
CPRI.
7.
If theNo radio
actionmodule is not detected when baseband module
either in CPRI or eCPRI mode:
-- Nokia personnel
An automatic BSRonly: Software
download upgrade
from NMS isvia LMI port.
ongoing. Fault
-will
If Software
be canceled after BSR download is finished User takes
upgrade via LMI port not possible:
the radio
- If the module
fault to Service
still exists Centercheck
then please for software upgrade.
if required BSR
package is staged in NMS and the package name in the
commissioning file is correct.
- Manually download BSR package
- Reconfigure cell with pre-defined beamset
Unblock the RAT from BTS Element Manager.

1) Reduce the number of downlink NB-IoT non-anchor
carriers (numDlNonAnchCarrierNB).
2) For guardband NB-IoT cell, if the number of guardband
NB-IoT downlink non-anchor carriers
(numDlNonAnchCarrierNB) needs to be 2 or 0, configure
the guardband NB-IoT downlink anchor carrier in the side
of LTE carrier which is farther away from band edge, then
second guardband NB-IoT downlink non-anchor carrier will
also be assigned
1. Check formulastoconditions,
the side ofsee
LTEif carrier whichare
any results is farther
away from band edge.
expected.
1)
3) Reduce the numbers
For inband NB-IoTof of uplink
cell, and downlink
configure the inbandguardband
NB-IoT
2. Reduce
NB-IoT the number
non-anchor formulas
carriers and set configured.
them to less than 2.
downlink carrier further from the band edge.
OR
4) Set NBIOT_FDD-dlPwrBoost to value less than +6
2) Replace the current RF module with another RF module
[dB];
that
5) supports the configuration
Change EARFCN with(earfcnDL)
of host cell number oftoNB-IoT non-
the middle
anchor carriers higher than 1.
of operating band to have more distance to the border of
operating band.
6) Replace the RF unit type serving the cell to one that
can support lower distance from band edge.
7)
1) Lock the
Change cell.
configuration of NB-IoT guardband anchor
1. Verify if ONAP VES Endpoint is operational.
carrier position (guardbandIndexDL,
2. Verify if ONAP VES Endpoint IP address guardbandIndexUL)
and port are to
the position radio module can support.
properly configured at the BTS or if FQDN resolves to
2) Change
correct the RF module which supports the configuration
IP address.
of
3. Verify theNB-IoT
required guardband
connectivity anchor
between BTScarrier
and theposition.
configured
ONAP VES Endpoint.
4. Verify the correctness of the certificates used during the
connection establishment between BTS and ONAP VES
Endpoint.
Check whether SSH algorithm name lists are aligned

between O-DU and O-RU
Check whether Netconf client account (user name,

password) is correctly configured for target O-RU.
Check whether connecting O-RU is a legitimate RU.
Be aware that an O-RU without public key provisioned is

connecting
Check whether secure storage of account info (username,

password) is working.
Check whether secure storage of additional Netconf
account info (username, password) is working
Check NETCONF connection between O-DU and O-RU is
working
None
If there are any issues observed on the shared radio,

disable the feature on the primary BTS, and manually reset
shared radio.
Operators sharing radio module should agree upon feature
activation status on both BTSs and set the feature
activation flag to the same value (enable or disable the
feature activation flag).
Enable Ethernet port security.
Replace the [Q]SFP transceiver with a compliant

Disable the service account root access.
transceiver.
The fault can be controlled by
EQM/APEQM/sfpOperatorMode, setting up
sfpOperatorMode to "true"
Replace the transceiver willa bypass
with theBTS
Nokia MN validation and
qualified
avoid the fault.
transceiver (47xxxxx sales item).
The fault can be controlled by
1. Check alarm additional info and perform either of below:
EQM/APEQM/sfpOperatorMode, setting up
a) If alarm additional info contains "eCPRI Beamforming
sfpOperatorMode to "true" will bypass the validation and
configuration invalid":
avoid the fault.
- Disable functionalities of beamforming (set
NRBTS.NRCELL.actBeamforming to false for impacted
Replace
cell)
Follow or the
FDMfaulty [Q]SFP
below with
allocation
steps one with
enhancements
to resolve thelower
(set working
fault:
temperature range
NRBTS.actFdmEnhancedSchedulingor wait until the
1. In case of NR-LTE sharing, try to configure system
to heats
false; up
note:
the to the
this
FHS
working
change temperature
impacts also range
other
sharing mode correctly on both sides. of the
cells) SFP.
OR
2. In case FHS sharing is not intended, FHS sharing should
-be Connect
disabled a in
different
SCF. eCPRI RU product, one that supports
the latest eCPRI
3. Replace the alarming FR1 beamforming
unit with thecapabilities
unit configured in
commissioning
Check if the file.
FHS primary controller"O-RU
is powered
b) If alarm additional info contains beamon, and if
mapping
the RP3-01 cables of the primary controller are properly
error":
attached.
- Reconfigure When thethe FHS primary
beamSet controller
with one supported is available,
by the the
FHS secondary
connected O-RU. controller gives up the temporary FHS
primary controller role.
OR
- Connect O-RU able to support the configured beamSet
OR
- Disable beamforming for the impacted cell(s)
None
c) If alarm additional info contains "O-RU FD Beamforming
unsupported":
- Connect an FD beamforming capable O-RU product
If
OR critical fault has been reported, replace the extension
baseband
- Disable O-RU module FDaccording
beamformingto the fault source.
functionality for the
impacted cell(s)
2. Perform a cell lock and then unlock operation.
APTS warning cause is specified in alarm additional info.

Check GNSS and TOP faults for more details.
To clear this fault, perform the following step:
- disable eCPRI RU M-Plane security by setting the
parameter actEcpriRuMPlaneSecurity to
'RuProtectDisabled'
Check the alarm diagnostic information for the reason of
the fault report before the RAT reset. Please note that
currently degraded cell setup is not supported.
If RAT reset
Activate deltaisnetwork
executed when
plan any of the cells has
modifying
availability status Degraded,
prachConfigurationIndex thecell
of the celltomight
valuenot be an
from enabled
after the reset,
unused slot. and will not provide any services.
Note: Theisalarm
The fault diagnostic
cancelled for theinfo
cellcontains
when: information about
PRACH
- the parameter frameStartOffset iscannot
configuration indexes that be same
set to the used. value in
Example: "Parameter prachConfigurationIndex
all cells on the same baseband card and the parameter for this cell
shall be different than [8, 12, 36, 40, 10, 14, 38,
sfnOffset is set to the same value in all cells on the 42]".
same
baseband card, or
- the cell timing offset feature is deactivated by configuring
MNL/MNLENT/FEATCADM.actCellTimingOffset to value:
false.
The fault is cancelled for the cell when the radio module is
replaced with an eCPRI or CPRI-N capable radio module or
the feature is deactivated by configuring
MNL/MNLENT/FEATCADM.actCellTimingOffset to value:
false.
To get the diagnostic information of the alarm for the lists of

Reset faultysimilar
information radio module.
to the following: RMOD-a/RXb=NOK
(Note: "a", "b" are Arabic numbers in practice and RMOD-a
stands
Changefor RU RMOD_R-a
protocol from instance),
CPRI toif eCPRI
such information
using the is
available.
procedure introduced in feature CB005793 (RRU remote
upgrade
The operatorfrom hasCPRI to to eCPRI)
perform either of the following after
Based on the diagnostic info of the alarm, you can try the
receiving the fault to recover the BTS to full operational
following instructions
state:
to recover from the fault:
1. Manually remove the neighbor object below limit.
1. Check whether the cell is set up under the following
2.
The Reconfigure
operator or manually
should change
do either of thethe threshold
following afterlimit.
scenarios: co-existence with WiMAX in the same band; and
receiving
co-existence the with
fault other
to recover the BTS to
LTE networks theother
from full operational
vendors. If
state:
so, check whether the synchronization between networks is
1. Manually
correctly remove the neighbor objects below limit.
configured.
Reconfigure
2. Check whether or manually
the cell ischange the threshold
set up under a network limit.
using
If actDlSlimCarrier
different LTE TDD eNB = ‘true’ reducereleases.
software the valueIfofso, then
numBlankDlPrbsDown/numBlankDlPrbsUp,
carefully review the calibration configurations or change
Perform reconfiguration
inbandPRBIndexDL, of cells
so that to reduce
closer tosoftware the in
the center
the vendor
number
of theof
files
SAIs among
or different
parameters LTE
related TDD
to eNB
cell broadcast releases.
capability,
system
3. Check bandwidth.the GPS or other synchronization
such that whether
SIB content would be within the maximum length.
sources (for example, synchronization servers) for this cell
If
areactDlIntShaping=true
working as expected. increase the value of
amountBlankedRes,
4. Check whether the cell is set blankingPosition,
or change up under the sharing or change
of
inbandPRBIndexDL
RFM with TD-SCDMA. so that it is farther from the center of
the
If
A so,system
BTS resetbandwidth.
check whether
is needed theincarrier
order configurations
to redeploy thein TD-
SCDMA and TD-LTE
LTE/GSM/WCDMA are and
cells not in conflict.
take into account CA DATA.
5.
The Check
number the of
RP3 links
cells thatstate especially
will be redeployed for the
withSFP
CA as well
specific
as
cellthe fibers connecting
deployment dependsthe on RFMs and the BBUs
the baseband inside the
resources
eNB.
available.
6. Block and unblock the cell.
7. Reset the Baseband module which supports the cell.
1.
8. Check
Reset the SRS configuration under LNCEL_TDD.
BTS.
2. Recommission
9. Examine the antenna the cell. cable connection between the
3. Change the radio.
RFM and the antenna element. (not applicable for mMIMO)
10. Exchange the cable connection between the antenna
and the RFM to check whether the RRU port or the cable is
faulty. (not applicable for mMIMO)
11. Replace the hardware(RRU/BBU).
The system has automatic actions to change the special
subframe to 5 (3:9:2) to avoid remote interference.
The fault is canceled and system is back to regular
operation
The system if the
hasremote
automatic specific
actionssequence detectedthe
by decreasing is traffic
lower
than
or thea functionality
configured threshold, on the traffic.i.e. RIAPR-numThresRIRecov.
No additional action is
If fault is from
required permanently
the operator. visible, the operator should consider
avoidance actions at the detected aggressor eNB side,
The
including system
Physical has
lowering automatic
HARQ Indication
antenna actions byorsending
Channel
downtilt, (PHICH)
change its
to own
another
specific
transmission
working frequency.sequence power for identification
boost can be purpose,
increased via
by that,
reducing the
reciprocity
configured remote boosts for interference
cell-specific relationship
downlink can be
reference signal
detected.
and/or
The following PCFICH. parameters are available in WebEM to
The fault
control fault is canceled and system backs to regular operation
6127 appearance:
if remote specific sequence is lower than a configured
threshold,
The systemi.e.
the LNCEL_TDD RIAPR-numThresRIRecov.
has automatic
parameteractions by decreasing
actRIAvoidance the traffic
to "true"
If
or
and fault
the is permanently
functionality
RIAPR-allowRollDwPts on visible,
the the
traffic. operator
The fault
is set to "true", should
is cancelledconsider
and
Perform network optimization.
avoidance
the system
and actions
backs to
tddSpecSubfConf atregular
detected 7aggressor
operation
is 6, or eNB side,
if remote interference
including
is within acceptable
AND manual reconfiguration
range again. their special subframe to 5
(3:9:2)
If fault ,
is or lowering
permanently
if remote interference specific antenna
visible,downtilt,
the or change
operator
sequence shouldtoconsider
detected another
exceeds
working
redesign frequency.
a configured threshold RIAPR-numThresRIRoll within abase
of the network to avoid interference between
Perform
Administration network optimization.
configured timehints.
stations. window RIAPR-numMinuteRISpecSeqUl,
the fault is raised
The
The following
Administration
system has parameters
automaticare
hints. available
actions in WebEMthe
by decreasing to traffic
control
The
or the
the fault
following 6126 appearance:
parameters
functionalityparameter
LNCEL_TDD are
on the traffic. available in WebEM
No additionaltoaction
actRIAvoidance to is
"true"
control
required
and fault 6124 appearance:
from the operator.
RIAPR-allowRollDwPtsbyRI is set to "true",
the
andLNCEL_TDD parameter
MRBTS/LNBTS/LNCEL/LNCEL_TDD.actRIMitigation
tddSpecSubfConf is 6, oractRIAvoidance
7 to �true-�flag
AND
to activate and/or deactivate TDD Remote Interference
AND
The system
ififMitigation
remote has automatic
interference
feature. specificactions by decreasing
sequence detected the traffica
exceed
or downhill
the duration on
functionality exceeds
the 50%
traffic. of RIAPR-
No additional action is
configured
numMinuteRISpecSeqUl threshold RIAPR-numThresRISpecSeqSending
MRBTS/LNBTS/RIAPR.upperThresRIUpPts within a configured- time valuewindow
of the
required
within
upper a from
configured
threshold theofoperator.
time
remote window RIAPR-
interference (dBm).
RIAPR-numMinuteRISpecSeqUl,
numMinuteRISpecSeqUl,
MRBTS/LNBTS/RIAPR.numSfRIUpPts
the fault is raised - length of
the
monitoringfault of window.
the cell isThe raised.
number of consecutive sub-frames
where
IF Remote
the fault Interference has to be detected to trigger
is raised
IF
the
and the fault of the cell is raised
fault.
AirScale
and BTS FDD:
(1.LNCEL_TDD
Block/unblock actRIAvoidance
the BTS. is "false"
(OR LNCEL_TDD actRIAvoidance is "false"
2. OR If it does not help, report the failure to Nokia support
RIAPR-allowRollDwPts
because the root cause isthe
of set fault
to "false"
is possibly a hardware
remote interference specific sequence detected
OR is lower
failure
than a or software
configured error.
threshold RIAPR-numThresRIRecov
RIAPR-allowRollDwPtsbyRI
within
OR a configured time window RIAPR-
numMinuteRISpecSeqUl
tddSpecSubfConf is set to 5
)OR
the fault of
remote the cell shall
interference be clear
specific sequence detected is lower
than a configured threshold RIAPR-numThresRIRecov
within a configured time window RIAPR-
numMinuteRISpecSeqUl )
the fault shall be cleared
Perform a SW Update either on the 4G or 5G side.
Check, if the cells on both sides are correctly defined.
Check, if the cells on both sides are correctly defined.

-1.Check
chBwDl NRCELL-nbrOfBlankedPRBsHighEdgeUL
the
and DSS configuration.
LNCEL/LNCEL_FDD-dlChBw. or NRCELL-
maxNrDssRatio.
blanking must be equal to NR blanking:- NRCELL-
nbrOfBlankedPRBsLowEdgeUL.
2.
3.8 Parameters
Reason on
3080) both
[featureCRM client
LTE4750] sides must
Reconfigure match.NRIfDL they
3.6
nbrOfBlankedPRBsHighEdgeUL 1110) LTE4750/5GC001856]
or NRCELL-
2.4
do
min
1.Check Reason
not match,
share 7009)
ratio
the DSS change [feature
the LTE4750]
configuration
NRCELL/NRDSSLTE-lteNrDssDlRatio-
configuration. Reconfigure
parameters LTE/NR
Reconfigure
nbrOfBlankedPRBsLowEdgeUL. parameters according to
parameters
depending
minNrDssRatio to reason
on remove
to value UL
from PRB reservation
supplementary
lower than conflicts:
alarm
orReconfigure
equal to
2. Change
LTE4750/5GC001856
2.4 Reason the configuration
6009) features
[feature parameters
specification
LTE4750] soLTE
depending max
on
thatLTE/NR
--NR:
information:
share
reason LNCEL/DSSNR-
from supplementary lteNrDssDlRatio-maxNrDssRatio.
alarm information:
required
parameters minimal
to remove UL PRB reservation conflicts:for NR.
number of DL SF can be reserved
--
2.1 NRCELL-msg1FrequencyStart
3.7 Reason
3.9
2.1
-NR: Reason 5040) 1111) [feature
3081)
8007) [feature CB006797]
LTE4750] ReconfigureLTE/NR
Reconfigure
LTE4750/5GC001856] LTE DL
--
LTE/NR NRBTS/BWP_PROFILE-locationAndBandwidthUl-
to ensure that DSS related
min
parameters
Reconfigure
-- share ratio LNCEL/DSSNR-lteNrDssDlRatio-
responsible
parametersfor
NRCELL-msg1FrequencyStart UL areas
according to reservations:are
functionalities
cRbStartUl
enabled/supported
minNrDssRatio and to NRBTS/BWP_PROFILE-
or disabled/not
value lower than supported
or equal to consistently
NR
--NR:
LTE4750/5GC001856
-- features
NRBTS/BWP_PROFILE-locationAndBandwidthUl- specification so thatmax
locationAndBandwidthUl-cRbSizeUl
on
share
-- both LTE and
NRCELL/NRDSSLTE- NR.
NRCELL-msg1FrequencyStart lteNrDssDlRatio-
required minimal
cRbStartUl number of DL SF can be reserved for
and NRBTS/BWP_PROFILE-
-LTE:
2.2
maxNrDssRatio.
-- Reason 5086) [feature LTE4750] Reconfigure
NRBTS/BWP_PROFILE-locationAndBandwidthUl-
LTE.
locationAndBandwidthUl-cRbSizeUl
--
parameters
3.10
cRbStartUl LNCEL/LNCEL_FDD/APUCCH_FDD-selectPrachRegion
Reason according
and3110) to LTE4750/5GC001856
[feature LTE4750/5GC001856] features
4. Deactivate
-LTE: theNRBTS/BWP_PROFILE-
LTE NR DSS feature.
-- LNCEL/LNCEL_FDD-selectOuterPuschRegion.
specification:
Reconfigure parameters
locationAndBandwidthUl-cRbSizeUl according to
--
2.5 LNCEL/LNCEL_FDD/APUCCH_FDD-selectPrachRegion
Reason 7054) [feature LTE4750] Reconfigure
-LTE4750/5GC001856
--LTE:
-- NRCELL/NRDSSLTE-lteNrDssUlRatio-maxNrDssRatio
features
LNCEL/LNCEL_FDD-selectOuterPuschRegion. specification so thatLTE/NR
to
(NR
required
-- have the
maxminimal same value
share requested)
number for both NRCELL_FDD-chBwUl
of DL SF can
LNCEL/LNCEL_FDD/APUCCH_FDD-selectPrachRegion be reserved forULNR.
2.5 Reason
if the6082) [feature to LTE4750] Reconfigure NR
-Check,
and
3.11
--
min Reason connection
LNCEL_FDD-ulChBw.
responsible for
3111)reservation
[feature
LNCEL/LNCEL_FDD-selectOuterPuschRegion.
share
the
DL CRM
MBSFN works.
LTE4750/5GC001856]
ratio NRCELL/NRDSSLTE-lteNrDssUlRatio- and Check
normal if the
cells
2.6 are correctly
Reason defined.
subframes.
Reconfigure
2.2 Reason 7055)
minNrDssRatio to
[feature
parameters
8008) [feature
value
LTE4750]
according
LTE4750]
lower than to Reconfigure LTE/NR
orReconfigure
equal to LTENR max to
to
2.3 have
Reason
LTE4750/5GC001856
ensure the same value for both
that there is one dynamic areaReconfigure
5087) [feature LTE4750]
features NRCELL_FDD-nrarfcnUl
specificationin the soNRthatreserved
share
and LNCEL/DSSNR-lteNrDssUlRatio-maxNrDssRatio.
LNCEL-earfcnUL.
parameters
required
area
2.6 (if three
Reason according
minimalPRBnumber
6083) areas to LTE4750/5GC001856
[feature ofLTE4750]
DL SF can
requested thenbe only thefeatures
reserved for UL
middle
2.7
LTE.
one Reason
specification:
according 7082)
to [feature
the PRB LTE4750] Reconfigure
numbering Reconfigure
should be
LTE
NR UL
min share
share ratioratio LNCEL/DSSNR-lteNrDssUlRatio-
-min
4. Deactivation
considered):
minNrDssRatio
NRCELL/NRDSSLTE-lteNrDssUlRatio-
LNCEL/DSSNR-lteNrDssUlRatio-minNrDssRatio
of
to LTE
value NR DSSthan
lower feature.
or equal to NR (LTE
max min
minNrDssRatio
share
-share requested) to
NRCELL-msg1FrequencyStart value lower than or equal to LTE max
-share LNCEL/DSSNR-lteNrDssUlRatio-maxNrDssRatio.
responsible
-maxNrDssRatio. for reservation DL MBSFN and normal
2.8 Reason
subframes.
cRbStartUl 7083)
and [feature LTE4750] Reconfigure LTE UL
NRBTS/BWP_PROFILE-
2.7
min Reason
share 6112)
ratio [feature LTE4750/5GC001856]
LNCEL/DSSNR-lteNrDssUlRatio-
2.4 Reason 5100) [feature
locationAndBandwidthUl-cRbSizeUl.
Reconfigure parameters LTE4750]
according to Reconfigure NR
Activate
minNrDssRatio
parameters the feature on the
to value
responsible partner
lower than side.
or equal to NR max
2.3 Reason
LTE4750/5GC001856 8084) features specificationallocation:
[feature for MBSFN pattern
LTE4750/5GC001856] so that
-share
NSA
required
Reconfiguremode:
minimal NRCELL-
parameters
number according
of UL PRBs to can be reserved for
maxNrDssRatio.
type0SearchSpaceConfigurationIndex,
LTE4750/5GC001856 features specification:
NR.
2.9 Reason 7112) [feature LTE4750/5GC001856]
---
2.8SA mode: NRCELL-prachConfigurationIndex.
NRDSSLTE-lteNrDssUlRatio-maxNrDssRatio
Reason 6113) [feature LTE4750/5GC001856] (NR max
Reconfigure
3. Check
share the parameters
requested) parameters according in the MOC to CRMINFO.
Reconfigure
LTE4750/5GC001856 parameters according to
features specification so that
-- NRCELL-msg1FrequencyStart,
LTE4750/5GC001856 features NRBTS/BWP_PROFILE-
specification so that
required minimal number
locationAndBandwidthUl-cRbStartUl of UL PRBs can
and be reserved for
required
NR. minimal number of UL PRBs can be reserved for
1. Check the GTP-U path
LTE. supervision configuration of the
2.10
BTS. Reason 7113) [feature LTE4750/5GC001856]
cRbSizeUl.
3. Check the parameters
Reconfigure parameters according in the MOC to CRMINFO.
2.
2.4Check
Reason if the supervised
8085) [feature network element
LTE4750/5GC001856] is operating
LTE4750/5GC001856
correctly.
Reconfigure parameters features
according specification
to so that
required
LTE4750/5GC001856 features specification: reserved
3. Check minimal
the number
communication of UL PRBs
equipment can be
between the BTS for
LTE.
and the supervised network
-- LNCEL/DSSNR-lteNrDssUlRatio-minNrDssRatio element.
3. Check the parameters in the MOC
-- NRCELL-msg1FrequencyStart, CRMINFO.
NRBTS/BWP_PROFILE-
Note
locationAndBandwidthUl-cRbStartUl, and
For S1: The S-GW might still be reachable although an
alarm caused by
cRbSizeUl.
Note: Perform thefault
steps 6150belowis reported.
in the listed order until the
Check
3. Check
alarm whether other alarms
the parameters in the
disappears. caused
MOCbyCRMINFO. fault 6150 are
disappears:
active and check whether all GTP-U paths to the S-GW are
1. Check other
concerned faults.
or connection
not.
1. Check the
2. parameters with
in thethe MME, accordingly, based
CRM.
If
onyou find that
whether the all
S1GTP-U
link is of paths
broken. to the same S-GW are
3.Check the parameters
faulty, the S-GW is not reachable anymore. the own CRM client.
4. Check the parameters of the remote CRM client.
2. Check if the MME is operational.
For X2: Only one GTP-U path exists between eNB primary
U-plane
3. Check IPif and
the the gNB IP.
speed and duplex setting of order
the BTS S1 port
Note:
Hence, Perform
the gNB steps
isthe
notswitchbelow
reachable in anymore
the listed once the until the
alarm
is
BTS consistent with
fault disappears. port that is connected directly
is
to reported.
the BTS (for example, they are both "Autodetect" or both
"1000
1. Check Mbit/sthe Full duplex").
connection with the adjacent BTS based on
whether the X2 link is broken.
If this fault happens right after a commissioning or a
configuration
2. Check if thechange,
adjacentverify
BTSthe IP address of the MME.
is operational.
If this fault happens right after a commissioning or a

configuration change, verify the IP address of the adjacent
BTS.
1. Check whether the transport path is alive.
2. Check the configuration of transport addresses at MME.

1. Check the connection with MME, particularly, whether
-the"trace reference
M3 link is broken.in use, trace cannot be started": This
problem
2. Checkisif out the of MMEthe is
scope of what can be fixed in the
operational.
BTS,
3. Check but is within
if the the scope
speed of thesetting
and duplex Network Management
of BTS M3 port is
System
consistent (NMS)
with used
switchtoport,
activate
which theissubscriber
connectedtrace. The
directly to
error
the BTS, means that there both
for example, is already an active
"Autodetect" or subscriber
both "1000trace
in the BTS
Mbit/s that is using the same Trace Reference
Full duplex".
Number. A possible solution is to try and deactivate all
subscriber traces and
If this fault happens activate
right after athem again.
commissioning or a
configuration change, verify the following configuration
-data:
"maxIPnumber
address ofofUEthetrace
MME. session reached, trace cannot
Flexi
be SBTS,
started": AirScale
This problem
Flexi BTS FDD, Flexi BTS TDD, SBTS, is Flexi
out BTS
ofAirScale FDD,
the scope BTS Flexi
of what
TDD, BTScan be
TDD,
fixed
AirScale AirScale
in theBTS BTS, BTS
FDD, TDD,
butFlexi AirScale
is within
SBTS, BTS
theAirScale FDD:
scope ofSBTS:the Network
1. Check
Note: whether
Perform the the
stepstransport
below path
in the is alive.order until the
Management
Perform System
the steps (NMS)
bellow in theused forlisted
listed subscriber
order trace
until the fault
BTS fault
activation.
disappear: disappears.
This error indicates that there are already 60
2. Check the configuration of transport addresses at MME.
active subscriber trace sessions, which is the maximum
1.
1. Check
Checkofthe
number and commissioning
active subscriber
update parameters
traces
the configuration supportedwith the BTS
in the
parameters BTS at
related
Element
any
to thepoint Manager
cells. Commissioning Wizard.
in time. Try to stop an already active subscriber
trace session in the NMS before activating any new
2. Load
subscriber
2. Load the correct
traces.
theFDD,correct commissioning
commissioning file
file to
to the
the BTS.
BTS. Commissioning error: <x>
Flexi BTS Flexi BTS TDD, AirScale BTS TDD,
AirScale
-3."Trace BTS FDD,
session Flexibe
cannot SBTS,started AirScale
due to SBTS:
ongoing
Execute
Perform the RAT
stepsReset.
bellow in the listed order untilbe
thestopped
fault
handover for the UE" or "Trace session cannot
disappears:
due to ongoing handover for the UE": This problem is out of Radio network configuration failed
4.
theCheck
scopeand update
of what canthebe configuration
fixed in the BTS. parameters related
This problem is
to the cells.
transient. A possible solution is to try and reactivate the
2. Load
failed the correct
subscriber commissioning
trace in the NMS. file to the BTS.
4. Execute
For failure in RAT
cell,Reset.
interface, or PCMD report trace session Radio network configuration failed
activation or deactivation, based on the error cause
provided
Flexi BTS as part Flexi
of theBTSdiagnostic info for the alarm raised,
Flexi
the BTS FDD,
following FDD,
mustFlexi
be BTS
done:
TDD,
TDD, AirScale
AirScale BTS
BTS TDD,
TDD,
AirScale BTS
AirScale BTS FDD: FDD, Flexi SBTS, AirScale SBTS:
Check
1. Check thethe
connection
other activewith third-party tool.
- "Cell trace feature is not BTS faults.Enable
enabled": the cell trace
2. Resetinthe
feature thesystem module by try
BTS. Afterwards, blocking and unblocking
to activate again the it.
3. Update and activate the SW to the BTS.
required cell or interface trace sessions. The feature flag
4. Check
used the SW files.
for activating the cell trace and interface trace is the
5. Replace
same. the system module.
- "PCMD report trace feature is not enabled": Enable the

PCMD report trace feature in the BTS. Afterwards, try again
to activate
Check and the required
ensure PCMD
that the report
PLMNs trace sessions.
1. Check if the maximum number ofthat have
LNADJ been listed
objects has
with this BTS fault, and that have been configured
been reached. If yes, check if there are LNADJ objects at thethat
BTS
can beformanually
one or more cells,This
deleted. havemakes
more space
than one
for MME
new
serving them, and
LNADJ information. that the relative capacity of that MME is
greater than zero.
2. Check if the maximum number of LNADJL objects has
been reached. If yes, check if there are LNADJL objects
related with the LNADJ object that can be manually
deleted. This makes space for new LNADJ information.
Check if the maximum number of LNADJW was reached. If
so, check if there are LNADJW objects that can be
manually deleted. This makes space for new LNADJW
object.
Check if the maximum number of LNRELW objects has
been reached. If so, check if there are LNRELW objects
that
Checkcanif be
themanually
maximumdeleted.
numberThis makes parameters
of mobility space for new
LNRELW objects.
(either of: csfbPsHoAllowed, psHoAllowed, and
srvccAllowed) of LNRELW per cell and WCDMA carrier
frequency is below the limit (for psHoAllowed or
srvccAllowed, limit in 3GPP 36.331 is (32); for
csfbPsHoAllowed is LNHOW::maxNumCsfbTargets).
If alarm additional info displays 4G neighbor information
(LNADJL) then
Add the LNREL object pointing to the correct neighbor to
allow the handover, or enable the UE-based ANR.
If alarm additional info displays 5G neighbor information
(LNADJGNB) then
Add the LNRELGNBCELL object pointing to the correct
neighbor to allow EN-DC addition of this neighbor.
AirScale
Block andSBTS,
unblockFlexi
theBTS
BTS.FDD, Flexi SBTS:
1. Check
If GPS for E-UTRAN
is configured as cells that operate
the reference on do
clock, thethe
same
frequency
following: layer, and those that are in close vicinity, and
use the same PCI.
1. Check the GPS receiver installation.
2. Check the GPS receiver status.
2.
3. Reassign
Check thePCIs for the between
connection discoveredthecells.
GPS receiver and
system module.
If the TOP
AirScale BTSsignal
FDD,is configured
Flexi SBTS,asAirScale
the reference
SBTS:clock,
check the connection to the TOP server.
1. Check for UTRAN cells that operate on the same
frequency layer and use the same PSC that are in close
vicinity.
2. Reassign PSCs for the discovered cells.
Reconfigure parameters that are related to the "Inter BTS

Carrier Aggregation" feature.
Upgrade or downgrade SW so that the same version is in

all BTSs that have the "Inter BTS Carrier Aggregation"
feature.
In cases where 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.
Remove neighbor-related objects below the value of the

parameter "maxNumAnrMoiAllowed" to bring the BTS to full
operational state.
If collision is detected:
For 'Interneighbor-related
Remove BTS Carrier Aggregation'-related
objects below thefeatures,
internal the
LNBTS.caClusterMemberId
thresholdthe
Perform to steps
turn offbelow parameter
the notification value
in the listedalarm.
orderThemustthebe
BTS
until stays in
BTS
unique
full for each
operational
fault disappears. BTS
state. that belongs to the same cluster
(LNBTS.caClusterId). If not, change this parameter value
so that it is unique for that particular cluster.
Read
In other partner
cases:BTS ID from diagnostic information and
1. Check
check BTSand
alarms commissioning and ensure
synchronization that
status on all theBTS.
partner carrier
For 'Inter BTS
aggregation Carrier
relations Aggregation'-related
are features,
pointing towards the properthe
cell
LNBTS.caClusterId
that exists within theand LNBTS.clusterNumBTS
carrier values or
aggregation cluster. Modify
must
deletebe identical
the for each
mismatching BTS that belongs to the same
relations.
cluster. If not, change the parameter values so that they
are
2. If identical.
an existing cell is totally missing from BTS within the
carrier aggregation cluster, add the cell.
3. If there are no mismatches in the carrier aggregation

relations, reset the BTS.
Adjust PUSCH
Block and masking
unblock and/or PUCCH blanking to reserve
the BTS.
enough place for 6 consecutive UL RBs for PRACH and at
least one additional PRB for Msg3.
Reduce the maximal number of active UE to be supported

Block and unblock
by adjusting the BTS.
parameters
Correct
maxNumActUe,the site configuration file (scf) content and
aPucchMinNumRrcNoDrb,
recommission
aPucchAddAUeRrHo, the BTSaPucchAddAUeTcHo,
by performing one or both and of the
following steps:
aPucchMinNumEmergencySessions
Reduce
1. Adjustthethemaximal
sidelink number of activeif UEs
direct communication
emergency handling
to be supported
transmit pool
is
by active.
adjusting the parameters maxNumActUe,
configuration in the frequency domain in order to:
aPucchMinNumRrcNoDrb,
- not overlap with PUCCH aPucchAddAUeRrHo,
-aPucchAddAUeTcHo,
reserve enough placeand for 6 consecutive UL RBs for
aPucchMinNumEmergencySessions
PRACH and at least one additional PRB if emergency handling
for Msg3 (see
is
Note)active.
2. Reduce the maximal number of active UEs to be
supported by adjusting the following parameters:
-1.maxNumActUe
Reset the faulty Flexi Zone Access Points.
-2.aPucchMinNumRrcNoDrb
Reset the Flexi Zone Controller.
- aPucchAddAUeRrHo, aPucchAddAUeTcHo
- aPucchMinNumEmergencySessions (if emergency
Reduce
handlingthe latency of the network connection between the
is active)
two eNBs or Flexi Zone Access Points to fulfill the
requirements
Note: Sidelinkfor CA.communication configuration across
direct
BTSs on a given carrier has to be identical. Changing
configuration on just one BTS is not recommended and has
to be done across the network where LTE2612 feature is
enabled.
The
Note:operator
Performshould do either
the steps belowofinthe
thefollowing after
listed order until the
receiving
alarm fault to
disappears. recover the BTS to full operational state:
Note: Perform
1. Manually the steps
remove below in the
the neighbor listed
object order
below until the
limit.
alarm
2. disappears.
1. Reconfigure or manually
Check the availability change
of the the threshold
adjacent BTS. limit.
1. Check the connectivity to the related adjacent BTS.

2. Check the connection with the adjacent BTS.
2. Check
alarm other faults.
disappears.
3. Disconnect and reconnect the adjacent BTS.
3.
1. Check
Check the
the parameters
availability ofrelated to the X2 interface of the
the MME.
adjacent BTS.
2. Check other faults on the MME and BTS.
4. Reset the BTS.
3. Check
Note: the parameters
Perform related
the steps below in to
thethe S1 interface
listed in the
order until the
BTS and MME.
alarm disappears.
4.
1. Reset
Check the
the BTS.
availability of the MME.
2. Check
alarm the connection with the MME.
disappears.
3.
1. Disconnect and reconnect
Check the availability of thethe MME.
MME.
2. Check the connection with the MME.
3. Disconnect and reconnect the MME.

GSM or WCDMA network (MME<->SGSN<->BSC).
If many LNADJG or LNADJW objects have the value of
Note that only one
their parameter alarm foras
"rimStatus" one PLMN is raised
Unavailable, checkdue theto the
RIM faults for GERAN, and only one
connectivity to GSM or WCDMA network (MME<->SGSN<-for UTRAN no matter
how
>BSC).many LNADJGs or LNADJWs are affected at a given
time. The alarm is raised for the first LNAJDG or LNADJW
where
Note thattheonly
faultone
is detected.
alarm forTheonealarm
PLMNadditional
is raised due to the
information
RIM faults for GERAN, and only one of
contains the parameters forthe first LNADJG
UTRAN no matteror
LNADJW even if the RIM fault is already
how many LNADJGs or LNADJWs are affected at a given inactive for the
LNADJG
time. The or LNADJW,
alarm butfor
is raised thethe
fault
firstisLNAJDG
still activeorfor other
LNADJW
LNADJG or LNADJW supporting the
where the fault is detected. The alarm additional same PLMN.
information contains the parameters of the first LNADJG or
LNADJW even if the RIM fault is already inactive for the
LNADJG or LNADJW, but the fault is still active for other
LNADJG or LNADJW supporting the same PLMN.
This fault does not require any actions. This alarm clears
automatically when the number of connected UEs remains
below maxNumClusterUe for at least 20 seconds.
Autonomous
If recovery actions
"Missing beamforming mapping are file
in progress,
in the BTS" andisif they
This fault
are not does notthe
effective, requirecause
any actions. This alarm clears
displayed in the alarmroot diagnosticofinfo, IPsec thetunnel
cell is setup
not set up
automatically
failure should when the number
be investigated of connected
frommapping
the logs.file UEs
Also, remains
there
because the proper beamforming is not
below
could bemaxNumClusterUe
multiple IPsec tunnel+ 10% reserve
failures withfor
X2atneighbors.
least 20
available on the system module. BTS SW update is
seconds.
Depending on the reason for failure, if the faultmapping
is due tofile).
necessary (including the proper beamforming
mismatch
Note: Perform the steps below in the listed order untilneeds
of IPsec policy parameters then the profile the
to
If be adjusted
"Beamforming
alarm disappears: either on the
mapping filesource or target
is corrupted or BTS.
it has Ifimproper
the
reason is due
structure" to insufficient
is displayed in theresources,
alarm diagnosticthen IPsec info, policies
the cell
that
is are not in use should be deleted to
1. Check the connectivity to the related adjacent gNB. file
not set up because the proper beamformingfree up resources
mapping
is
2. corrupted
Check other or itfaults.
has improper structure. BTS SW update is
necessary
3. Check the (including
parameters the proper
relatedbeamforming
to the X2 interface mapping file).
of the
adjacent gNB.
If
4."Beamforming
Reset the BTS.mapping file does not contain sufficient
date to configure mMIMO cell" is displayed in the alarm
diagnostic info, the cell is not set up because the content of
beamforming mapping file is incomplete. BTS SW update is
necessary (including the proper beamforming mapping file).
This fault does not require any (special) actions.
If "Missing beamforming vectors weight file in the
connected mMIMO radio" is displayed in the alarm
diagnostic info, the cell is not set up because the proper
beamforming
nothing to do vectors weight file is not available on the
Perform a reconfiguration
mMIMO radio. Radio SW update of cells istorequired
reduce the numberthe
(including of
configured carrier frequencies
beamforming vectors weight file). and corresponding inter-
frequency neighboring and/or blacklisted cell list items,
which shall be broadcasted
If "Beamforming vectors weight through SIB5,not
file does socontain
that the SIB5
content would be within the maximum
sufficient data to configure 5G cell" is displayed in the length limit.
alarm diagnostic info, the cell is not set up because the the
content of beamforming mapping file is incomplete. BTS
SW update is necessary (including the proper beamforming
mapping file).
Check other S1 related alarms and repair failed S1 link

connections
If the fault is or checkit and
raised, repair
means thatthe
theS1
celllink configuration.
is about to enter
overloaded status, and the AC Bar factors will be
broadcasted in SIB2.
UEs with a bigger bar factors will not be able to attach to
the cell untiltrivial
1. Remove the overloaded
CATMIRFIMstatus is over.
settings to reduce the SIB5-
BR size, i.e., do not configure the optional parameters
under CATMIRFIM.
2. Reduce CATMIRFIM instances.

- Check the alarm history to confirm the frequency of fault
6450 in a specific BTS.
- Check the alarm history for other alarms in the same BTS
that might be related especially alarms with:
a. FSP or FBBB alarm source
b. the following fault IDs: 418, 6706-6709, 12, 476, 1806,
1811, 4019
- Check the BTS for any performance issues.
One or more PLMN-based ACBs cannot be broadcasted
If
viaanSIB2-BR
alarm with andfault
must 6450 frequently
be omitted occursthe
because in the same
maximum
BTS,
availablealarms with the
SIB2-BR same
length faultsbe
would mentioned
exceeded.above are
present in the same BTS, or the BTS performance is
Perform
degraded, reconfiguration of cells to reduce number
a caseoffor
Follow
nrCarFrqL the then
stepscollect
instancebelowor
atosnapshot
resolve the
parameters
andfault:
open
related to cell broadcast
Nokia R&D log analysis.
capability such that SIB content would be within the
1. In case length.
maximum of NR-LTE or LTE-LTE CPRI RF sharing, try to
Take
connect notethatif logs
Radiofrom
Unit,different
HW versionDSPs should
of the same
be >=FSP are
Rel 5.1
stored
(NAKHA). in the BTS (only one alarm with fault 6450 is
reported
2. In caseasofrelatedNR-LTE to eCPRI
one DSP). The nexttry
RF sharing, alarm with fault
to connect that
6450
Radio Unit with Supported Technology that containsfrom
related to the next DSP is reported when logs
the
EUTRA first DSP
and 5G. are collected.
3. In case
Flexi SBTS, RFAirScale
sharing SBTS,
is not intended,
Flexi BTSRF sharing
FDD, Flexishould
BTS be
disabled in SCF.
TDD, AirScale BTS TDD, AirScale BTS FDD:
4. Replace the alarming unit with the unit configured in
Source:
commissioning file.
- FCT (HW rel.3)/AIA: Perform BTS reset.
- FSP/FBB/ABIA: Change the cell configuration to decrease

call processing
1. Reset load. unit or module.
the alarming
2. Reset BTS.
3. Replace the alarming unit or module.
Flexi SBTS, AirScale SBTS, Flexi BTS FDD, Flexi BTS

TDD:
The
Note:fault does the
Perform not steps
require any special
below action
in the listed because
order it
until the
was already autonomously
fault disappears. corrected.
Flexi SBTS, AirScale SBTS, Flexi BTS FDD, Flexi BTS

1. Reset
TDD, the System
AirScale and/or
BTS TDD, Baseband
AirScale BTSModule.
FDD:
Note: Perform the steps below in the listed order until the Failure in replaceable baseband unit,System
2. Replace the System and/or Baseband Module.
fault Module failure
Flexi disappears.
BTS FDD, Flexi BTS TDD, AirScale BTS TDD,
1. Reset the
Perform the steps
System and/or
below Baseband
in the Module.
listed order until the fault
disappears:
2. Replace the System and/or Baseband Module.
1. Reset BTS
AirScale the System Module.
FDD, Flexi SBTS, AirScale SBTS:
Perform the steps below in the listed order until the fault
2. Replace the System Module, or FBBx or ABIx module
disappears: Failure in replaceable baseband unit,System
(according to the fault source). Module failure
1. Reset
Flexi BTSthe System
FDD, FlexiModule.
BTS TDD, AirScale BTS TDD,
2. Replace
Perform thethe System
steps belowModule, or FBBx
in the listed or until
order ABIxthe
module
fault Failure in replaceable baseband unit,System
(according
disappears: to the fault source). Module failure

1. Reset BTS
AirScale the System Module.
FDD, Flexi SBTS, AirScale SBTS:
2.
Perform the steps belowModule,
Replace the System or FBBx
in the listed or until
order ABIxthe
module
fault Failure in replaceable baseband unit,System
(according
disappears.to the fault source). Module failure
1. Reset the System Module.

2. Replace the System Module, or FBBx or ABIx module Failure in replaceable baseband unit,System
(according to the fault source). Module failure
Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna and the antenna is causing the
problem.
2. Consider other alarms that might be occurring or

Flexi BTS FDD/TDD,
configuration changesAirScale
that wereBTS FDD/TDD:
made just prior to this
Perform the steps below in the listed
alarm as possible sources for this alarm. order until the fault
disappears:
1.
3. Reset
If therethe
areSystem Module.
no external factors or if the alarm is
2. Replace replace
persistent, the System Module
the Flexi Zoneor Micro
FBBx BTS,
or ABIx module
Flexi Zone
(according to the fault source).
Access Point, or Flexi Zone SFN Antenna GPS Antenna.
4. If not using an external GPS antenna, replace the Flexi

Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone
SFN Antenna.
None
The other multi-carrier cell can be enabled by deleting the

blocked or locked cell.
Correct the value of the parameter

"IPNO:cPlaneIpAddress" to match the one configured in
FxP.
If the issue persists, perform the steps below in the listed
order until the fault disappears.
1. Block/unblock the impacted cell.
2. Reset the Flexi Zone Micro BTS or Access Point.
3. Replace
If the issue the Flexi Zone
persists, Micro
perform the BTS
stepsorbelow
Access Point.
in the listed
1. Block/unblock the impacted cell.
3. Replace
AirScale BTS:the Flexi Zone Micro BTS or Access Point.
1. Change actUnlicensedAcc flag to "OFF" then again to
"LAA".
Perform the steps
2. If it doesn't help below
and the in fault
the listed order until
is detected againthe fault
disappears.
block/unblock the BTS.
If
1.the
Checkissuethepersists,
Ethernet perform
interfacethefunctionality
steps belowusedin thebylisted
the
Network Time Protocol. Check if other faults related to the
1. Block/unblock
Ethernet interface the impacted cell.
exist.
Perform
2. Reset the
the following
Flexi Zone steps
Microin BTS
orderoruntil the fault
Access Point.ensure
2. Check the Network Time
disappears. Protocol configuration;
3. Replace
that the NTP the Flexi Zone Micro BTS or Access Point.
1. Check the Server
Ethernet IPinterface
address functionality
is configuredused
properly.
by
3. CheckTime
Network the Network
Protocol.Time
CheckProtocol server
if other faultsfunctionality.
related to the
4. Check interface
Ethernet that the IP connection between the Network Time
exist.
Protocol server and
2. Check the Network Time Flexi Zone Microconfiguration.
Protocol BTS, Flexi Zone Ensure
Access Point, or Flexi Zone SFN
that the NTP Server IP address is configured Antenna is working.
properly.
3. Check the Network Time Protocol server functionality.
4. Check that the IP connection between the Network Time
Protocol server and Flexi Zone Micro BTS or Flexi Zone
Access
AirScalePoint
BTS is working.
TDD:
This fault is not applicable as this fault is triggered by SAS
server actively due to SAS management requirement such
as the spectrum resource may be not enough at that time.
There is no
AirScale BTS further
TDD:action for user.
This fault is not applicable as this fault is triggered by SAS
server actively due to SAS management requirement such
as the spectrum resource may be not enough at that time.
There is no further action for user.
or invalidthe
contact parameters,
SAS service which will result in a new registration
provider.
certain
attemptthat
supporting for the all required
the version
CBSD with parameters
being theused SASby areCBSD
Server. configured,
Iforthe
contact then the
fault
operator
Nokia.
continues should
to contact the SAS service provider or Nokia.
4. For cert
AirScale BTSfileoccur,
issue,the
TDD: operator
If the CERT_ERROR should try fault resetting
continuesthe
3.
eNB.For blacklisting issue, The Operator must remove the
to
1.
2. ForIfparameter
occur
condition
both
for aofCBSD,
protocol
that led
these
issue,
version
to
methods
the
the
operator
the
issue,
fail and
operator should
the operator
blacklisting of
thereturn
must
the
operator
fill
CBSD.
the
in any
should The
is
CBSD
missing
match eNBthe
certain
to
or Nokia
invalid thatwith all
parameters,required
an sent
indication parameters
which that the
willwith are configured,
Registration
result inversion then
Request
a newIfsupported
registration the
for
version
will
operator number
periodically
should retry
contact by
the CBSD
Registration
the SAS the
service Request.
provider the fault
or Nokia.
the
by CBSD
attempt for
SAS. If to failed,
the
theoccur CBSDand
two versions that
with a
theCERT_ERROR
SAS
do notthe Server.
match, Ifwas
the
then should received.
fault
either
continues for this CBSD, operator
AirScale
continues
connect
contact BTS
to
the tothe
SAS TDD:
occur,
SAS the
service operator
supporting
provider. the should
version try resetting
being used theby
AirScale
2.
5. Forfault BTS
protocol
invalid TDD:
version
spectrum issue,
issue, the
the operator
operator should
can try match changing the
This
eNB.
CBSD
4. If both
or
cert is not
contactof applicable
these
file issue, Nokia. methods
If the as this
fail fault
and is
the triggered
operator by
is SAS
1. For
version
the parameter
number
supportedSpectrumV2 issue, theCERT_ERROR
operator must
configuration fault
fill continues
in any
parameter. missing
This
server
certain
to occur actively
that
for all due tothe
required
a CBSD, SAS management
parameters
operator requirement
areinconfigured,
should theIfthen such
the
or
sent
willinvalid
cause parameters,
byspectrum
CBSD the with
eNB which
theinitiate
to version will result
supported
a Registration areturn
bynew SAS.
Procedure CBSD
registration
thefor
as
3.
to the
operator
For
Nokia should
blacklisting
with an resource
contact
issue,
indication the
themaySAS be
operator
that the not
service enough
must
Registrationprovider
removeatRequest
that
or time.
Nokia.
the for
attempt
two
the CBSD. for Ifthe
versions do
the CBSD
not
fault with the
match,
continues then SAS either
to Server.
occur, connect
the If operator
thetofault
the SAS
There
condition
the CBSD is no that further
failed,led to
andaction
thethat for
a user.
blacklisting
CERT_ERROR of the CBSD.was The
received. eNB
continues
supporting
should try to theoccur,
resetting version the being
operator used should
by CBSD try resetting to the
or contact
2.
will
5.
eNB.For
For
Nokia. Ifprotocol
periodically
other
both retrythe
version
conditions,
of these the eNB.
issue, Ifthe
Registration
please
methods
the
refer
fail
fault
operator
and
continues
toRequest. should
SASoperator
the If the
notebook matchoccur
perthe
isfault
and
versionthe
continues operator
number
to occur is certain
for this that
CBSD, supportedSpectrumV2
the operator should
error
certain
parametercode
thatstoredallaccurate,
isSAS in alarm
required text.
parameters
then Ifoperator
thesupportedit isarestillconfigured,
not resolved,
should thenthen
contact the
the
sent
contact
the by CBSD
the
operator
operator should with
should the
service
contact version
contact provider.
the the
SAS SASserviceservice by provider
providerSAS. If Nokia.
or the
or
3.
SAS
two For blacklisting
service provider
versions issue,
do not match, the
or Nokia. operator must
then either connect to the SAS remove the
Nokia.
condition that led to thebeingblacklisting ofCBSD
the CBSD. The eNB
supporting
4.
2. For
For cert
protocol the
file version
issue,
version If the
issue, used
CERT_ERROR
the by
operator or contact
fault
should continues
match
will
6.
Nokia.
to
periodically
For other
occurnumberfortoaoccur
retry
condition,
CBSD,
the
the
Registration
please
operator refer to
should
Request.
SAS If
notebook
returnshould
the
the CBSD per the
fault
version
continues
error code stored infor
the this CBSD,
alarm text. theIf itoperator
is still not resolved,
to
sentNokia
contact by with
CBSD
the SAS an indication
with the version
service that supported
provider. the Registration by SAS. Request
If the for
then
3.
the For the
CBSD operator
blacklisting
failed, should
issue,
and that contact
thea operator
CERT_ERROR the SAS must service
remove
was provider
theSAS
received.
two
or versions do not match, then either connect to the
Nokia.
condition
supporting that led
the issue, to
version the blacklisting
being of
used by CBSDfault the CBSD. The
or contact eNB
4.
willFor cert file
periodically retry If the
the CERT_ERROR
Registration Request. continues
If the fault
5. For
Nokia.
to other
occur fortoaoccur condition,
CBSD, please
the operator refer to
should SAS notebook
returnshouldthe CBSD per
continues
error code stored infor
thethis CBSD,
is still not resolved,for
to Nokia
contact thewith an indication
SAS service that
provider. the Registration Request
then
3. For the operator
blacklisting should
issue, contact
the
the CBSD failed, and that a CERT_ERROR was received. operator the SAS
must service
remove provider
the
or Nokia.
condition that led to the blacklisting of the CBSD. The eNB
4.
willFor cert file issue,
periodically retry theIf the CERT_ERROR
Registration faultIfcontinues
5. For
AirScale
to occur otherBTS
for acondition,
TDD:
CBSD, theplease
operator refershould to Request.
SASreturn notebook the fault
the CBSD per
continues
error code to occurinfor
stored the this CBSD,
is still should
not resolved,
to Nokiathe
contact with SAS an indication
service that the Registration Request for
provider.
then
If the
the the
faultoperator
CBSD continues
failed, and should
tothat contact
occur, thethe
a CERT_ERROR SAS service
operator should provider
verify
was received.
or Nokia.
that the SAS server information is configured correctly.
4. For cert file issue, If the CERT_ERROR fault continues
5.
to For other
occur for acondition,
CBSD,information
theplease
operator refershould to SASreturn notebook the CBSD per
1. If the
error code SAS server
stored in the alarm text.is configured
If it is still correctly,
not resolved, but
to Nokia
there with
areoperator
other anSAS indication
servers that the Registration
available, theservice
operator Requestshould for
then
the the
CBSD failed, should
and that contact
a CERT_ERROR the SAS was provider
received.
try changing the CBSD to use another server.
or Nokia.
5.
2. For other condition,
If another SAS server please
is notrefer to SAS
available, notebook
and per
the current
error code stored in the alarm text. If it is still not
SAS server information is correct, then the operator should resolved,
then
try tothe
lockoperator should
or unlock contact
of at least onethe SAS
cell service
of the CBSD.provider
If that
or Nokia.
does not solve the issue, the operator should try resetting
the eNB.
If all of these methods fail, the operator should check their

routers or network and/or contact the SAS service provider.
AirScale BTS TDD:

If the problem continues to occur, replace the AirScale BTS
or AirScale
If the BTS Access
issue persists, Point.
perform the steps below in the listed
order until the fault disappears:
1. Block and/or unblock the impacted cell.
2. Reset
If the thepersists,
issue Flexi Zone Microthe
perform BTS or Access
steps Point.
below in the listed
3. Replace the Flexi Zone Micro
order until the fault disappears: BTS or Access Point.
1. Block and/or unblock the impacted cell.

3. Replace
Flexi the FlexiPoint,
Zone Access ZoneFlexi
MicroZone
BTSMicro:
or Access Point.
1. Block
alarm and/or unblock the impacted cell.
disappears.
3.
1. Replace the
Check the Flexi Zone
availability of Micro
MME.BTS or Access Point.
2. Check the connection with MME.
3. Disconnect and reconnect MME.

Note: Perform
1. If MBSFN the steps
areas below inas
are provided the listed order
additional info:until the
alarm disappears.
- increase MBSFNSYNCAREA::maxSyncSubfrPShare
- reduce MBSFN::maxSubfrPShare
1.
A Check event,
recent
- change availability
suchof asMME.
Session Start/Stop/Update of
MBSFN::mbsfnStartingSF
MBMS, resulted in the suspension of the specific session
2.
2. Check
due If to
noan other faults
internal
MBSFN on
areMME
failure/event
areas and
thatBTS.
provided did not take effect.
in additional info: This
condition
- decreasemay not be recoverable. It may cause an
MBSFNSYNCAREA::maxSyncSubfrPShare
3. Check and/or
interference
- disable theinparameters
the end-user
reconfigure related to M3
sessions
features interface
for
that this inusing
MBSFN,
exclude the BTSof
and
either MME.
on this BTS or adjoining BTSs belonging
some subframes for MBMS purpose (for example: OTDOA, to the same
MBSFN.
Liquid Cell,In order
ETWS) to recover from this condition, a session
4.
stopReset the
could beBTS.
attempted from the core to ensure that other
BTSs
Note thatare the
alsoalarm
not transmitting
may also be the specific
raised session.
if MBSFN If this
areas
condition
overlap when persists or happens frequently, please consider
MBSFNSYNCAREA::mbsfnOverlapAllowed
deactivating
is false (in thatand reactivating
case, the MBMSneeds
either overlapping feature.
to be
enabled, or MBSFN areas reconfigured to not overlap).
If the problem happens frequently, please collect symptom
data and deliver them to Nokia Customer Support. To
Flexi
collectBTS FDD, Flexi
symptom data BTS
after TDD, AirScale
fault 6855 BTS TDD,
is detected, add the
AirScale BTS FDD,
fault number (6855) to Flexi SBTS, AirScale SBTS:
No action required.
MNL/MNLE/TRBLCADM.faultSnapshotTriggers.faultNumbe
r
and configure
MNL/MNLENT/TRBLCADM.faultSnapshotTriggers.triggerT
ype = 0 (onFaultDetection).

No action required.
Check whether an MBMS Session suspension with the
reported TMGI is expected in the MBSFN Area that
Flexi BTSwith
overlaps FDD, Flexiother
some BTSMBSFN
Area already containing
MBMS session with earlier absolute time to data transfer.
No action required.
The session with TMGI reported by this BTS Fault is
suspended. To activate the suspended session, either the
session(s) in overlapping should be stopped or MBSFN
Areas reconfigured to not overlap.
1. Check the other mains related active alarms.
2. Check the power source that provides voltage to

problematic input. If it is ok, replace the power cable.
1. Check the other mains related active alarms.
2. Check the power source that provides voltage to

problematic input. If it is alright, replace the power cable.
- No actions are required. When there is no other alarms, it

1. Reset BTS.
indicates synchronization problems.
2.
- IfIfany
it does notwith
alarm help and alarm withfault
synchronization the fault is reported
appears and if:
again, replace faulty hardware.
a. new fault was reported after SW update: retry SW
update
b. otherwise, update BTS with last working SW
If none of the above helps, replace the System Module.
1. Execute FSP reset.

2. If FSP reset does not help, execute Site reset.
3. If reset does not help, replace the faulty hardware.
1. Refrain from requesting any procedure which involves
restarting of the alarming module (for example, SW update)
until alarming module is replaced.
1. Refrain from updating SW in eNB until the alarming
module is replaced.
If alarm due to fault is reported at least three times per

month, then replace the alarming module.
disappears:
1. Reset the System Module or ABIC module.
2. Replace the System Module or ABIC module.
Connect the faulty Capacity module to ASIB and perform

plug-in software update to a version that has booting
capabilities compatible with ASIL.
Replace faulty SFP.
Replace faulty the

Note: Perform SFP.steps in the listed order until the fault is
resolved.
1. Obtain technical report for further analysis.
2. Restart system module.
3. Replace the alarming common module.
Remove BTS Plug-in Unit with incompatilble cooling type.

disappears:
1. Reset the System Module or ABIx module.
2. Replace the System Module or ABIx module.
disappears:
1. Reset the System Module or ABIC module.
2. Replace the System Module or ABIC module.
disappears:
If fault recovery fails, check the nrRelLteId associated with
1.
theReset the System Module or ABIx module.
NR CELL.
2. Replace
Check if LTE theeNB
System Module
provided or ABIx module.
via nrRelLteId is available.
If cell reconfiguration
Check is needed to recover the cell from the
the configuration.
failure,
If cell reconfiguration iscell
then enforce a setuptobyrecover
needed manualthe
cellcell
locking, cell
from the
parameters update via delta configuration plan and cell
failure, then enforce a cell setup by manual cell locking, cell
unlocking.
unlocking.
Further, explicit cell lock/unlock is needed to recover from
failure even, if there is no problem with the cell
configuration.
Check if any E1 is unavailable (e.g.
7700::EFaultId_E1SetupRetryFailGuardTimerAl is visible)
OR
Check if NG is unavailable (e.g.
7316::EFaultId_NgSetupFailureAl is visible).
Note: Perform the steps

If cell reconfiguration below intothe
is needed listed the
recover order
celluntil
fromthe
alarm disappears:
failure, then enforce a cell setup by manual cell locking, cell
1. Check if SCTP association is established from the LTE
unlocking.
eNB.
alarm disappears:
2. Check if the eNB is operational.
1. Check
Check theconfiguration
slice connection between
on both gNB-CU
gNB and and
AMF. gNB-DU.
3.
1. Check
Check ifif EN-DC X2 Setup
SCTP association request message
is established fromfrom
thethe
gNB-
LTE
2.
DU. eNB
Check is
if received
the gNB-CUby gNB.
or gNB-DU is operational.
4.
2. Check
3. Check ifif EN-DC X2and
the speed
gNB-DU Setup Response
is duplex settingmessage
operational. is sent
of the VNF to
F1 port
eNB
is consistent with
3. Check the gNB-DU C-Plane logs to identify the root
the switch port that is connected directly to the VNF (for
cause.
example, they are
4. Reset the gNB-DU.
both "Autodetect" or both "1000 Mbit/s Full duplex").
4. Check
alarm if the speed and duplex setting of the gNB-DU F1
disappears:
Check the gNB-DU
port is consistent and gNB-CU C-Plane logs to identify
with
the protocol error cause.
1. Check the connection with the AMF.
the switch port that is connected directly to the gNB-DU (for
Note: Perform
example, the steps below in the listed order until the
2. Check
alarm ifthey
the are
disappears: AMF is operational.
both
3. "Autodetect" or both "1000 Mbit/s Full
of duplex").
1. Check
Check ifthe theconnection
speed andwith
duplex setting
the AMF. the NG port is
consistent with
Note:
the Perform
switch the
thatsteps below in directly
the listed
to order until(for
the
2. Check
alarm ifport
the AMF
disappears:
isisconnected
operational. the gNB
example, they are
both
3. "Autodetect" or both "1000 Mbit/s Full
of duplex").
1. Check
Check ifthe theconnection
speed andwith
duplex setting
the peer gNB/ngthe eNB.
NG port is
consistent with
Note:
the Perform
switch the
the listed
to order until(for
the
2. Check
alarm ifport
the peer
disappears:
isgNB/ng
connected the gNB
eNB is operational.
example, they are
both
Note:
3. "Autodetect"
Perform
Check ifthe the or both
steps
theconnection
speed and "1000
below inMbit/s
duplex the Full
listed
setting duplex").
of order
Xnuntil
portthe
the eNB. is
1. Check
alarm disappears: with the peer gNB/ng
consistent with
the
2. switch port
Check that isgNB/ng
connected directly to the gNB (for
1. Check ifthe
example,
the peer
theyconnection
are witheNB is operational.
the eNB.
both
3. "Autodetect" or both "1000
duplexMbit/s Full
of duplex").
2. Check
Check ifif the
the speed
eNB is and
operational. setting the Xn port is
consistent with
the switchifport
3. Check that is connected
the speed and duplexdirectly
setting to
of the
the gNB
VNF (for
X2 port
example, they
is consistent with are
Note:
the Perform
switch port the
is connected the listed
to order until(for
the VNF the
alarm disappears:
example, they are
1. Check
both if SCTP association
"Autodetect" is established
or both "1000 from the
Mbit/s Full duplex").
remote gNB.
2. Check if the remote gNB is operational.

gNB tries iftoXn
3. Check solve therequest
Setup problemmessage
internally.
from the remote
gNB is received by gNB.
4. Check if Xn Setup Response message is sent to remote

gNB.
The reason for the gNB initiated Reset needs to be
investigated. This could be because of a
process/container/VM crash. The operator needs to make
sure that whatever
The reason has crashed,
for the gNB is backneeds
initiated Reset in service.
to be
investigated. This should be because of a non-UE specific
event in gNB like process/container/VM crash, Cell delete
etc... The operator needs to investigate the cause for non-
UE specific event.
The reason for the AMF initiated Reset needs to be

investigated. The operator has to check the source of error
on the AMF side and fix it.
The reason for the AMF initiated Reset needs to be

investigated. The operator has to check the source of the
error on the AMF side and fix it.
If "Slice(s) not supported" reason is provided in the alarm
additional info then check slicing configuration on both gNB
If
andfault
AMF recovery fails check
and correct the NG
the issues seenlinkthere.
state and the gNB-
CU-CP logs. Check if the NG link is functional
If additional info was not provided and fault recovery and correct
fails
any issues seen there.
check the NG link state and the gNB-CU-CP logs. Check if
Note:
the NGPerform the steps and
link is functional below in theany
correct listed orderseen
issues untilthere
the
alarm
beforedisappears:
triggering either gNG-C locking&unlocking with this
AMF when NG-C Flex SA mode feature is activated or
1. CheckgNB
manual if SCTP
reset.association is established from the LTE
eNB.
If
2.fault
Checkrecovery failsischeck
if the eNB the NG link state and the gNB-
operational.
CU-CP logs. Check if the NG link is functional and correct
any issuesif seen
3. Check EN-DC there.
X2 Setup request message from the
LTE eNB is received by gNB.
4. Check if EN-DC X2 Setup Response message is sent to

eNB.
The cause value of the RAN Configuration Update Failure

should be investigated.
The reason for no response from the AMF should be

investigated.
The reason for no response from the AMF should be

investigated.
The AMF has reported a protocol error in a message sent

by thePerform
Note: gNB earlier. The reason
the steps forthe
below in thelisted
NG :order
Error until
Indication
the
message from the
alarm disappears: AMF needs to be investigated.
1. Check if NRBTS/maxNumX2Links can be increased
2. Check if eNB can be allocated to another gNB

1. Check if SCTP association is established from the gNB-
DU.
alarm disappears:
2. Check if the gNB-CU operational.
1. Check
Check thethe
F1connection
SCTP statebetween gNB-CU and gNB-DU.
3. Check the gNB-DU and and gNB-CU
gNB-CU C-Plane
C-Plane logslogs.
to identify
Note:
the Perform
root cause. the steps below in the listed order until the
2. Check
alarm if the gNB-CU or gNB-DU is operational.
disappears:
4. Check
3. Reset the gNB-DU
speed ifand
SCTP association ofisand
notVNF F1 port
1. Check ifthe
established.
the
connection duplex
between setting
gNB-CU the gNB-DU.
is consistent with
2. Check if the gNB-CU or gNB-DU is operational.
example,
3. Check ifthey
the are
speed and duplex setting of the VNF F1 port
Check
is consistent with C-Plane logs to identify the root cause.
the gNB-CU
4. Check ifthey
example, the are
speed and duplex setting of the gNB-DU F1
Check the gNB-DU
port is consistent and gNB-CU C-Plane logs to identify
with
the protocol error cause.
the switch port that is connected directly to the gNB-DU (for
example,
4. Check ifthey
the are
speed and duplex setting of the gNB-DU F1
port
Check is consistent with
the configuration.
If cell reconfiguration is needed to recover the cell from the
the switch
failure then:port that is connected directly to the gNB-DU (for
example,
1. Lock the cellare
they manually
2. Apply appropriate parameters setting to the cell via the
both
delta "Autodetect"
configurationorplan both "1000 Mbit/s Full duplex").
3. Unlock the cell manually.
Also, when a cell failure is observed whether or not the cell
configuration is correct, force the manual lock / unlock of
Note:
the cellPerform the steps
to recover from thebelow in the listed order until the
situation.
alarm disappears:
Note:
1. CheckPerform the steps below
the connectivity to theinrelated
the listed
CRM.order until the
alarm disappears:
2. Check other faults.
1.
3. Perform
Check the a SW update either
parameters in the onCRM thelocated
local orremotely.
remote
network
4. Check the parameters of the remote CRM clientSW
element so that they are on a compatible level.
(Partner
Cell
Note:configuration).
Perform the steps below in the listed order until the
5. Check
alarm the local configuration of the partner cell pair is
disappears:
Note:
matchingPerform the steps
the connectivity
remote below in the listed order until the
configuration
1. Check
alarm the
disappears: to the related CRM.
6.
2. Reset
Check the network
other faults. element.
1. Check the connectivity to the related CRM.
3.
2. Check
Check the parameters
other faults. in the CRM located remotely.
4.
3. Check the parameters of
Check the parameters the CRM.
in the remote CRM client (Partner
Cell configuration).
4. Check the parameters of the remote CRM client.
5.
5. Reset
Check the
the network element.
configuration of the remote
Note: Perform the steps below in the listedCRM client
order untiland
the
the CRM.
alarm disappears:
6.
1. Check
Check thethe local configuration
connectivity of the partner
to the related CRM. cell pair is
matching
2. Check the remote
otherthe
faults.configuration
Note:
7. Perform
Reset the steps
network below in the listed order until the
element.
3. Check the
alarm disappears:parameters in the CRM.
4.
1. Check the connectivity of
Check the parameters to the remote CRM.
the related CRM client.
5. Check the configuration
2. Check other faults. of the remote CRM client and
the CRM.
3. Check the parameters in the CRM.
6.
4. Reset
Check thethe network
parameters element.
of the remote CRM client. (e.g. if
LTE physical cell ID matches NR physical cell ID)
5. Check the configuration of the remote CRM client and
the CRM.
6. Fallback to the previous DSS configuration.
Public Warning System SIB. (Cause 0x00050000)
- Invalid number of SI-Messages configured. (Cause
0x00060000)
- SIB1 message exceeds the standard Transport Block
Size (TBS) limit. (Cause 0x00080000)
- Incorrect gscn configuration confliction with PRB blanking
configuration. (Cause 0x00100000)
- nrofRBs calculated for CSI-RS for beam management is
Note:than
less Perform the steps
24. (Cause below in the listed order until the
0x00110000)
alarm
- Incorrectdisappears:
paging slot selection due to
1. Activate the feature on the partner
numPagingOccsnPagingFrame side.
or pagingOffset or
numOfPagingFrames or fPdcchMonOccsnPo or Type2
search space parameters (duration, periodicity, slot offset,
monitoringSymbolsWithinSlot).
Note: Perform the steps below in (Cause 0x20000000)
the listed order until the
-alarmIncorrect configuration
disappears: 1. Lockofand
the unlock the cell
monitoringSymbolsWithinSlot or
Note: Perform the steps below in the listed
firstPDCCHMonitoringOccasionOfPO for theorder untilsearch
paging the
alarm
space. disappears:
(Cause the 1. Check
0x40000000) the configuration of the Xp
Note: Perform
interface. There PCCHsteps
must below
exist in the listed
an instance orderunder
ofreceived
XPIF until the
..\
-alarm
Newdisappears:
modified Config
1. Check has
the DSSbeen
configuration:during
MNLENT\XPAP.
Short Message transmission period of must
last on-line
Parameters on both CRM client sides match modified
the
PCCH Config. (Cause 0x10000000)
parameters - CELL DL Bandwidth, (E-UTRAN DL
-Transmission
Type2 search space is not
Bandwidth, NRconfigured or/and the
DL Transmission Paging
Bandwidth)
is not activated for the Cell with SA mode.
- DL Center Frequency, (EARFCN DL, NRARFCN DL), (Cause
0x50000000)
Center Frequency must be the same, - LTE Physical Cell
ID (NRCELL:
Note: PerformltePhyCellId, LNCEL:
the steps below in thephyCellId), - Number
listed order until the of
TX Antenna Ports (dlMimoMode in LNCEL/NRCELL).
alarm disappears: 1. Check the configuration: Parameters 2. If
they
on both CRM client sides must match the parameters - 3.
do not match, change the configuration parameters.
Check
CELL ULtheBandwidth,
parameters(E-UTRAN
in the MOC ULCRMINFO.
Transmission
Bandwidth,
Note: PerformNRtheUL Transmission Bandwidth), - ULuntil
Center
Note:
FrequencyPerform the steps
(EARFCN steps
UL,
below
below in
in the
NRARFCN the listed
listed
UL) 2.
order
order
If until
they
the
dothenot
alarm
alarm disappears:
disappears: 1. Check the configuration: Parameters
match,
on change
both CRM the configuration
client sides must parameters.
match. 2.on If both3.
they do Check the
notclient
1. Check
parameters theinconfiguration:
the MOC Parameters
CRMINFO. CRM
match,
sides must change
match thethe
configuration
parametersparameters
- CELL UL like the
Bandwidth,
parameters - CELL UL Bandwidth,
(E-UTRAN UL Transmission Bandwidth, NR UL (E-UTRAN UL
Transmission
Transmission Bandwidth,
Bandwidth),NR - ULULCenter
Transmission
Frequency Bandwidth),
-(EARFCN
UL CenterUL, Frequency (EARFCN
NRARFCN UL). UL, NRARFCN UL). 3.
Check the parameters in the MOC CRMINFO.
2. If they do not match, change the configuration
parameters.
3. Check the local configuration of the partner cell pair is
matching the remote configuration
4. Check
Perform in the in
the steps below MOC CRMINFO.
the listed order until the
alarm disappears: 1. Check the connectivity to the related
CRM. 2. Check other faults. 3. Check the parameters in the
CRM. 4.Check the parameters of the owned CRM client. 5.
Check the parameters of the remote CRM client.
1. Check if the cell is provisioned in gNB-CU

2. Check NRCELL configuration in gNB-CU
If fault recovery fails then restart the gNB manually.
If fault recovery fails then restart the gNB manually.
Please check E1 Setup configurations

gNB tries to solve the problem internally.
Check the other alarm(s) reported on the FSP indicated by

this fault for the root cause.
Check the connection with the third-party tool.
The neighbour NRREL reported by UE should be properly

configured in gNB to enable A3/A5 based NSA HO.

1.
1. If
Check
Follow thethe
alarm/fault
that thebelow
steps is nottoexpected,
cables/fibers
clear are check if the
the connected
fault: toUser Event
the correct
Temporary
connectors. buffer threshold is correctly set.
2.
2. Check that
1. Check ifthe
theavailability
overwriting
the interfaceof configuration
at the
IP far-endofinterface
connectivity. the UserisEvent
Temporary
switched onbuffer and has is correctly set.
correct auto-negotiation settings.
3.
2. Check whether there are active alarms at the far end. If
there
found,are, follow follow
the the instructions
instructions for handling
for handling those
those alarms.
alarms.
4. To verify that the hardware of the interface works
correctly,
3. Check ifconnect the far a loop
end hascable
BFDand check ON.
switched whether the
alarm disappears.
E1 interfaces:
5. Check that the Check that the of
length/type interface type of the
the cable/fiber does far-end
not
interface
introduce excessive attenuation or that the cable/fiber is Ifcut
is also configured to be a framed E1 interface.
this is not the case, reconfigure the interfaces so that they
somewhere.
match
6. Check eachthatother.
the Ethernet interface has correct auto-
negotiation settings, fitting to the far-end interface.
1.
7. Check
With anCRL update
optical failure
Ethernet reasonsCheck
interface: by reading the values
that the
of the parameter "updateFailureReason".
inserted SFP module matches the fiber type and
wavelength
1. ofavailability
the Gigabit ofEthernet link provided.
2. Check
Execute the general IP connectivity.
configuration checks:
- Configuration of primary/secondary CRL server IP
2. Checkand
address whetherport there are active alarms at the far end. If
there are, follow
- Configuration of DNS server IP address
the instructions of
- Configuration forIPsec
handling those
policies alarms.remote peers
towards
- Configuration of CRL Download Protocol
1. Check that the SFP module is correctly installed and
plug-out/plug-in
3. Check SFP module.
Switch offremote peers
the loopback and intermediate
or wait network
for the timeout element
to expire
interconnections.
which opens the loop and cancels the alarm.
2. Check that the electrical contacts of the SFP module are
clean fromthe
4. Check dust, dirt, or water.
connection towards the Certificate Revocation
List servers, including primary and secondary servers if
Note that only the SFP might be faulty, and not the entire
applicable.
hardware unit.
5. Check DNS names.
6. Check the size of the file at the Certificate Revocation

List server.
1. Check the cabling and network connections to the far

end.
None
2. Check the Link OAM event information and the Link
OAM statedetails
1. Inspect information.
of the type of the critical event through
3. Check the Ethernet
online configuration interface configuration at the local
management.
and remote sides.
2. Check the Link OAM state information of the interface.
4.
3. Insert
Checkathe
Link OAM and
cabling loopback.
network connections to the far
end.
4. Check the Ethernet interface configuration at the local
and remote sides.
5. Insert a Link OAM loopback.
Replace the faulty SFP. Note that only the SFP is faulty,
not the entire hardware unit.
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 damaged and is within the specifications.
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 of each individual link. If they
are, follow the instructions for handling those alarms.
Check that the configured interface type matches the

configured interface type of the far end. If this is the case,
the problem is somewhere in the transmission network.
Check the intermediate transmission network for alarms

indicating theintermediate
1. Check the root cause and follow the network
transmission instructions for
for alarms
handling these alarms.
indicating the root cause and follow the instructions for
handling these alarms.
2. Check the transmit hardware, connect a loop cable and

check thatif no
1. Check thealarms appear for this interface.
negotiatedLocalIPAddress is the same as
the
CheckconfiguredLocalIPaddress.
the status of the following parameters:
localMruResult, remoteMru, pfcResult, and acfcResult.
2. Change
Check if thethe values
value to the
of the LCPcorrect ones accordingly
configuration parameters either
at the local end or peer.
acfcTarget, localMruTarget, and pfcTarget match with the
peer.
Change the values to the correct ones accordingly either at
the
Checklocal forend
LCP orfailure alarms of the PPP-links belonging to
peer if there
the SL-PPP/ML-PPP is a mismatch.
interface and follow the instructions of
these alarms.
Check all PDH-related alarms and follow the instructions of

these alarms.
1. Check the cabling.

1.
2. Check the CMP
CCM configuration.
configuration at the remote peer.
2. Check if the CA server is reachable.

1.
3. Check
Check cabling.
if the end-entity certificate or any of the CA
2. Check the
certificates in configuration
the chain useata the remote
weak hash peer.
algorithm MD5 or
MD2.
1. Determine if the alarm about enabled SSH access to
4.
BTSIf none of the above work, contact the CA administrator
is expected.
or a Nokia service
2. If the alarm personnel.
is not expected disable SSH access
Note: the SSH access to BTS is disabled by default and

due to security
1. Check reasons
the network it shall be
between enabled
both for limited
BFD peers period
for physical
of time on as-needed basis
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 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.
Note: Do not execute this step remotely, but only when
1. Check
being the at
locally backhaul
the site usage andcause
as it can if other
theapplications
Ethernet linkwith
to
the same or higher PHB may compete against
be down. As a result, remote management access might be this TWAMP
session
lost. about the capacity. An increase in the priority of
1. Check session
TWAMP the backhaulor of theusage and if capacity
backhaul other applications
may clearwiththe
the same
alarm. or higher PHB may compete against this TWAMP
Note: Check whether root cause of the fault
session about the capacity. An increase in the priority of is not existing
anymore,
TWAMP is doneor byofa the
newbackhaul
auto-negotiation process.
2. Check session
Retriggering if destination is unreachable
auto-negotiation requires
capacity
by may clear the
IP connectivity
manual action from
alarm.
test. Send(i.e.an changing
ICMP echo requestinterface
(ping) toconfiguration,
the UDP port of
the user, Ethernet
the
plug TWAMP
out/plug reflector
in cable, attriggering
the destination IP.If ICMP echo
2. Check
reply the last
indicates measured
that RTT link
the destination
down/link
values of this up).
TWAMP
is unreachable, but you
session
have access and verify
to TWAMPthat the configured
reflector, you RTT threshold
can check value
its status.
is
If the status is disabled or down, try to activate it againso
not too close to the average measured RTT values, and
that
check this alarm
if the alarmcould be the result of sporadic
disappears.
mismeasurement.
3. Check configured PLR threshold. Setting PLR to 0%
should be avoided, because every lost measurement
packet will trigger the alarm and it cannot be cleared again
(PLR>=0).
The alarm is only cleared if a vendor certificate is manually

installed in BTS.
Check the LCP failure alarms of the PPP-links belonging to

Update trust interface
the ML-PPP anchors. and follow the instructions of these
alarms.
1. Confirm that SyncE is desired as a synchronization
source.
Check the related PDH alarms and follow the instructions of
these alarms.
2. Confirm that configuration settings for ssmEnabled are
correct.
1. Confirm that SyncE is desired as a synchronization
source.
3. Troubleshoot with Backhaul provider about the reason
for SSM errors.
2. Confirm that BTS configuration settings for ssmEnabled
are correct.
3. Troubleshoot with Backhaul provider about the reason

for SSM errors.
Replace expiring vendor certificate with new vendor

certificate using WebEM.
SMOD case
1. Check the cable connectivity on ToP master side.
2. Check the TOP configuration both in BTS and ToP
Replace the expiring trust anchors with new trust anchors
master sides.
using WebEM.
RU case
1. Check the eCPRI link on RU side.
2. Check the TOP configuration both in RU slave and ToP
master sides.
1.Check for duplicate IPv6 addresses configured in the
network element.
2.Change the identified duplicate IPv6 address.
Start IPsec emergency bypass by making the security

gateway unreachable either by plugging out the cable or
configuring the wrong security gateway address.
Stop IP traffic capture from BTS Element Manager.
Check the validity of the username and password of the

account.
1. Check the availability of IP connectivity.

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 BTS and the peer
for proper values.
Check the configurations for the peer and the BTS security
policies for the corresponding failure notification.
None.
1. Determine if this event is expected: check if a qualified
personnel is utilizing LMP ethernet port cable connection
for diagnostic purposes.
2. Otherwise, it shall be treated as a security warning.
Instructions:
Check that the connection is used by authorized personnel.
1. Determine if this event is expected.
BTS operator to check connectivity to DNS server(s).
2.
DNSIf this event to
operator is check
not expected, disable
the service, R&Dreceived
as BTS Service Port
access.
timeout when resolving FQDN.
DNS operator to check DNS entry for given FQDN, as BTS
received NULL response.
Operator to check local tunnel endpoint IP version and
configure IPsec FQDN entry with matching IP version.
1. Check the source address of the remote MEP.
2. If the updated MAC Address is incorrect , manually
configure MAC Address of that particular remote MEP
again.
1.Operator to check DNS entry for failed FQDNs and make
sure it resolves to unique IP addresses.
2.Operator to check local and remote tunnel end point IP
address configured are unique across IKEP instances.
In case of switchover failure, operator needs to recover the
defective link.
1. Check the availability of primary/secondary IPsec tunnel
connectivity.
there
Note: are, follow the instructions for handling those alarms.
Note: Perform
Perform the
the steps
steps below
below in
in the
the listed
listed order
order until
until the
the
alarm disappears:
alarm disappears:
1. Check the connectivity to the related remote Network
1. On remote Network Element, remove an existing remote
Element.
Note:
peer Perform the steps
configuration below in the listed order until the
(XPIFREMOTE)
2. Check
alarm other faults.
disappears:
3. Check the parameters related to the XP interface of the
remote
1. Check Network Element. to the related remote Network
the connectivity
4. Check
Element. the configuration of the remote Network Element
Note:
5. Perform
Reset the the steps
Network below in the listed order until the
Element.
2. Check
alarm other faults related to XP interface.
disappears:
3. Check the parameters related to the XP interface of the
remote
1. Check Network Element. to the related remote Network
the connectivity
4. Check
Element. the configuration of the remote Network Element
5. Reset the Network
2. Check other faults. Element.
3. Check
Perform related
the steps below in to
thethe Xp interface
listed ofthe
order until the
remote Network
alarm disappears:Element.
4. Check the configuration of the remote Network Element
5.
1. Reset thea Network
Perform Element.
SW update either on the local or remote
Network Element so that they are on the compatible SW
level.
2. Remove the incompatible IP Peer from the source
XP_REMOTE.
Decide if collected troubleshooting is important and if so

copy it to the location available for technical staff.
5GC002350: Phase 1 NR-LTE concurrent
operation for AEHC eCPRI radio
5GC001698: DU (ABIL+RU) remote upgrade
from CPRI to eCPRI
5GC001702: NR-LTE/SRAN concurrent
operation with OBSAI RUs
5GC000933: MDEA fronthaul switch for 5G
deployments
5GC000181: HW addition and removal without
service impact
SR001730: Fronthaul switch support on SBTS
CB007310:
(LTE-only One classical gNB on dual ASIL
configurations)
Related
SR002956: Features
SBTS Operability
SR002459: Common SW loadsupport
for LTEfor and 5G
5GC001146:
SRAN Common OAM on classical gNB
LTE5286:
LTE4032: Common SW load ABIC
AirScale Capacity for LTE and SRAN
SR002459: Common
SR002576: SBTS-5G concurrentSW load foroperation
LTE and with
SRAN
OBSAI RUs
50160: TCP/IP
LTE3236: measurement
Automatic recovery/optical delay
SR001498:
compensation Support of FSMF
of Nokia CPRI IF + FSMF with SRAN
link problems
configurations
SR002286: Automatic recovery/optical delay
SR001534:
compensation
SR002187: SRAN
AutomatedFM combined
of Nokia CPRIHW
DSP service
IF link problems
recovery on on
CB005906: eCPRI based TDD massive MIMO
LTE5286:
ABIA Common SW load for LTE and SRAN
ABIO/N
LTE3084:
LTE1996: Remote
Flexi ZoneFPFH PDUsupport
Controller control for
via 5G
Application
SR003007:
LTE5286: Basic
Common SWSWSupport
load for
for ASOE
LTE and SRAN
AirScale
LTE146:
SR003007: SM
LTE Software
Basic SWSW Management
Support for LTE
ASOE
CB007135:
SR002459: Common for
loadSRAN
for andand5G
SR002696:
SR001534:
CB007135: FHS
SRAN
Common& FM
AFAA CPRI
combined
SW for SRANm-plane
service
and 5Glink
classical
SRAN
protection
classical
CB007310:
5GC000316: One
5G classical
Node gNB on dual ASIL
B Synchronization Mode
5GC002277:One
CB007310: AEQZ AirScalegNBMAA 32T32R
CB005793:
Support RRUclassical
remote upgrade on from
dual ASIL
CPRI to
192AE n78 200W
5GC002589: 5GZone
RF(CPRI)
sharing withApplication
two Airscale
eCPRI
LTE1996: Flexi
SR001498:
System Support
Modules ofController
FSMF + FSMF with SRAN
CB005850:
SR001534: NR-LTE
SRAN FM concurrent
combinedoperation
service with
configurations
SR002382:
shared FHSSW Support for AirScale Capacity
for OBSAI
SR001534:
ABIO includingSRAN FM combined
common ABIO and service
ABIN for
CB006028: Independent software upgrade
LTE2779:SW
Platform CPRI-A
shared RU
LTE1656:
SR002956: Management support for legacy
SW Support support
for AirScale for 5G
Capacity
Motorola/Fujitsu
5GC002350: RF-equipment
Phase 1 NR-LTE concurrent
ABIO including common ABIO and ABIN
operation
LTE505: SW
Platform for AEHC
LTE505 eCPRI radio
Transport Separation for RAN
SR002459:
sharing
SBTS Operability for LTEfor and 5G
SRAN
LTE151: Autonomous
5GC001698: LTE eNB
DU (ABIL+RU) Operability
remote upgrade
LTE4032:
from CPRIAirScale
SR001534: toSRAN
eCPRI Capacity
FM combined ABICservice
5GC000560: eCPRI Sync
5GC001702: NR-LTE/SRAN concurrent Slave RU
LTE5286: with
operation CommonOBSAI SWRUsload for LTE and SRAN
LTE1996:
SR002187: Flexi Zone Controller
Automated DSP HW Application
recovery
5GC000933:
LTE151: MDEA fronthaul
Autonomous LTE eNB switch for 5Gon
Operability
ABIA
deployments
SR001534:
ARAN1163: SRAN
Iu-PS FM combined
Throughput service
Measurement
SR001730: Fronthaul switch support on SBTSfor
GTP Traffic
(LTE-only configurations)
5GC000316:Common
SR002459: 5G NodeSW B Synchronization
load for LTE andMode
Support
SRAN
SR001534:
5GC001246:SRAN FM Indoor
AirScale combined Radio service
ASiR LTE
and NR concurrent operation
LTE4032: AirScale Capacity ABIC
SR002576: SBTS-5G concurrent operation with
OBSAI RUs
LTE5286: Common SW load for LTE and SRAN
LTE3656: MDEA Fronthaul Switch Outdoor DC
5GC000174: 5G Node B Software management
LTE3397: LTE C-Plane in new Single BTS OAM
architecture
SR001534: SRAN FM combined service
LTE2779: CPRI-A
LTE1656: Management support for legacy
Motorola/Fujitsu RF-equipment
SR002956: SBTS Operability support for 5G
LTE5286:
CB007135:Common
CommonSW SWload for LTEand
for SRAN and5GSRAN
SR002459:
classical Common SW load for LTE and
CB007135:
SRAN Common SW for SRAN and 5G
CB005793:
classical RRU remote upgrade from CPRI to
5GC001082:
eCPRI Classical gNB software
5GC002589:
Management 5G RF sharing with two Airscale
SR002956:
System SBTS Operability support for 5G
Modules
LTE146:
LTE5286: LTE Software
Common SW Management
load foroperation
LTE and SRAN
CB005850:
SR001534: NR-LTE
SRAN FMconcurrent
CB007135: Common SW load combined
for SRAN service
andand
5Gwith
SR002459:
shared FHS for OBSAI for LTE
classical
SRAN
SR002956:
5GC002589: SBTS
5G Operability
RF sharing support
with for 5G
two Airscale
5GC001082:
5GC001698: Classical
DU gNB software
(ABIL+RU) remote upgrade
System Modules
Management
from CPRI toNR-LTE
CB005850: eCPRI concurrent operation with
SR001534:
CB007135:
SR002459: SRAN FM
Common combined
SW for forservice
loadSRAN andand
LTE 5G
shared FHS
classical for OBSAI
SRAN
5GC002589:
LTE5286: 5G RF
Common sharing
SW load with
for two and
LTE Airscale
SR002459:
System Common
Modules SW load for LTE andSRAN
SR001534:
SRAN SRAN FM combined service
CB005850:
LTE146: LTENR-LTE concurrent
Software Management operation with
LTE4032:
shared FHS AirScale Capacity
for OBSAI ABIC
LTE5286:
SR002956: Common
SBTS SW load for
Operability LTE and SRAN
SR003007:
LTE1996: Basic
Flexi SW
Zone Supportsupport
Controller for ASOEfor 5G
Application
SR002459:
SBTS Operability for LTEfor
and
SR001534:
SRAN SRAN FM combined service 5G
LTE652: LTE
LTE146: Intelligent FlexiManagement
Software BTS Shutdown
LTE4032:
5GC000613: AirScale Capacity
EAC support onABIC
gNB
LTE5286:
Common SW load for LTE
LTE and
and SRAN
SRAN
SR002459: Common SW load for LTE and Application
SR001534:
LTE146: LTE Software
SR001682: AirScale Management
Common ASIB PIU SBTS
support
SR001486:
SR002956: Support for already
SBTS Operability delivered
support for 5G
SRAN16.2/16.10 features
SR000924:
SR002459: SBTS
CommonIntelligent
SW load shutdown
for LTE and
SRAN
LTE654a:
SR002956: LTE
SBTS Configuration
Operability Management
support for 5G1/2
CB007422:
LTE1996: 5G
Flexi BTS
Zone Supervision
Controller harmonization
Application -
LTE5286:
Part Common
II (signature for SW load for LTE and SRAN
crash/failure)
SR001534:
SBTS Operability for LTEforand5G
SRAN
SR002187: Automated DSP HW recovery on
LTE654a:
ABIA LTE Configuration Management 1/2
CB005906:
LTE1996: eCPRI
Flexi based
Zone TDD massive
Controller MIMO on
Application
LTE5286:
ABIO/N
SR003007: Common
Basic SW SW load forfor
Support LTE
ASOEand SRAN
SR001534:
SR002459: SRAN FMSW combined service
SR002956: Common
SR003007: Basic
SBTS SW loadsupport
Support
Operability for
for LTE
ASOE and
for 5G
SRAN
CB007135: Common SW for SRAN
SR002187: Automated DSP HW recovery and 5Gon
LTE1996:
classical
ABIA Flexi Zone Controller Application
SR001621:
5GC002269: SRAN
LTE5286: Common Cell
SWSets
HW addition Allocation
and
load removal
for LTE andon Full
without
SRAN
AirScale
service
SR002459: Module
impact on ABIO
5GC000829:
SRAN One classical gNB on dual ASIK
SR002382:
LTE4032: SW Support
CB007135:AirScale
Common SWfor
Capacity forAirScale
ABIC
SRAN and Capacity
5G
ABIO including common ABIO and
LTE1996: Flexi Zone Controller Application
classical ABIN
Platform
SR001534:
CB005793: SWRRU
SRANremote
FM combined
upgradeservice
from CPRI to
SR002956:
eCPRI SBTS Operability support for 5G
SR002459:
5GC000829:Common SW load
One classical gNBforonLTE
dualand
ASIK
SRAN
LTE4032:
5GC001476: AirScale Capacity
DU ABIL configs:ABIC
legacy FDD CPRI
SR001534:
LTE5286: SRAN
Common FMSW combined
load service
for LTE and SRAN
Radios (II)
SR001498:
5GC001082:Support of FSMF
Classical + FSMF with SRAN
gNB software
configurations
Management
LTE1996:
SR002459:Flexi Zone Controller
Common SW load for Application
LTE and
SR001534:
SR001498: Support of FSMF + FSMF with SRAN
configurations
SR001534: SRAN FMSpectrum
SR002546: Dynamic combinedSharing
service
WCDMA+LTE, phase 2
SR002167: Dynamic Spectrum Sharing
WCDMA+LTE


SR001171: WCDMA17 new feature
implementation for SBTS17
RAN3280: Dynamic Baseband Configuration for
High Speed Cell_FACH

RAN3067: Carrier Aggregation

RAN3067: Carrier Aggregation
RAN3374: Narrowband Interference Cancellation
RAN3421:
SR002546:WCDMA
DynamicSupport over
Spectrum Nokia CPRI for
Sharing
SBTS
WCDMA+LTE, phase 2
WCDMA+LTE
SR002014: SRAN Dynamic Spectrum Sharing
GSM+WCDMA
WCDMA+LTE,
SR002382: SWphase 2 for AirScale Capacity
Support
SR002167: Dynamic Spectrum
ABIO including common ABIO and Sharing
ABIN
WCDMA+LTE
Platform SW
WCDMA+LTE, phase 2
WCDMA+LTE
SR003007: Basic SW Support for ASOE

LTE4525: AMOD AirScale 5G-compatible

outdoor subrack
5GC001121: AMOD outdoor sub-rack for 5G
SR002203: AMOD AirScale outdoor subrack 5G
full compatible
SR002956:
SR001880-B: SBTS Operability
SR001880-B AMOCsupport for 5G
alarms
SR002956: SBTS
LTE5286: Common Operability
SW load forsupport for 5G
LTE and SRAN
LTE5286:
SR002459: Common SW load for LTE andSRAN
SR002459:
SRAN Common SW load for LTE and
SRAN
SR001880-B:
outdoor subrackSR001880-B AMOC alarms
full compatible
SR001880-B:
LTE4525: AMOD SR001880-B AMOC alarms
AirScale 5G-compatible
outdoor subrack
full compatible
SR002459: Common SW load for LTE and
SRAN
SR001534:
SR002459: SRAN FMSW
Common combined
load forservice
LTE and
SRAN
LTE: 61-p (Technical Log and Memory Dump
LTE1996:
LTE5286: Flexi
CommonZoneSW
Controller
load forApplication
LTE and SRAN
SR001534:
SR002459: Common SW load forservice
SRAN FM combined LTE and
SRAN
LTE1996:
SR002956:Flexi
SBTSZone Controller
Operability Application
support for 5G
LTE168: LTE System Maintenance
outdoor subrack
full compatible
SR001880-B: SR001880-B AMOC alarms
5GC000613: EAC support on gNB
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
5GC000613:AirScale SM SW
EAC support onsupport
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SRAN
SR001494: AirScale SM SW support for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SRAN
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOEand
SRAN
SR001494:
gNB for FSEE
SRAN
CB007310: One classical gNB on dual ASIL
CB005793: RRU remote upgrade from CPRI to
eCPRI
SR003007: Basic SW support
SR002951: Support for for AGIML
ASOE AI/ML
SR002956:
PoC HW SBTS Operability support for 5G
5GC000613:NR-LTE
CB005850: EAC support on gNB
concurrent operation with
LTE5286:
shared FHS Common
for OBSAISW load for LTE and SRAN
SR002459:
SR003007: Common
5GC001866: SWSW
Delivery
Basic of load for
beam
Support set LTE
for and to
realization
ASOE
SRAN
gNB
SR001494:
CB006028: AirScale
5GC000613:Independent SM SW
software
gNBupgradefor FSEE
for
SR001534:
shared RU SRAN FM combined
LTE5286: Common SW load for LTE and SRAN service
SR002382:
Common for AirScale Capacity
SR003007:
ABIO Basic
including SWSW
common
load
Support
ABIO
for
for LTE
and ASOE
ABIN
and
SRAN
SR002956:
Platform
SR001494: SWSBTS Operability support for 5G
5GC000613:AirScale
SR002956:
SM SW
EAC Operability
SBTS support onsupport
gNB for
support
FSEE
for 5G
SR001534:
LTE5286: CommonSRAN FM combined service
5GC002350: Phase SW load forconcurrent
1 NR-LTE LTE and SRAN
SR002459:
SR003007: Basic SW Support for LTE
operation Common
for AEHC SW
eCPRI load
radiofor ASOE and
SRAN
SR002670:
SR002956: eCPRI transport layer
SBTS Operability supportconfiguration
for 5G
SR001494:
5GC000613:AirScale
harmonization between
EAC SMLTE
support SW support
onandgNB 5G w/forPAL
FSEE
SR001534:
architecture SRAN FM combined
5GC001476:
SR002459: DU ABIL configs:
Common legacy FDDand CPRI
SR003007:
Radios (II) Basic SWSW load for
Support for LTE
ASOE
SRAN
SR002956: SBTS Operabilityconcurrent
support for 5G
5GC001702:
AirScale SM SW support
5GC000613:
operation withEAC
OBSAIsupport
RUs on gNB for FSEE
SR001534:
LTE5286: SRAN FM combined service
SR002546:CommonDynamicSW load forSharing
Spectrum LTE and SRAN
SR002459:
WCDMA+LTE,
SR003007: BasicCommon
phase
SW 2 SW load for
Support for ASOE LTE and
SRAN
LTE5240:
SR002956:BTS SBTSFronthaul
OperabilitySFP+/SFP28
support for Base
5G
SR001494:
Line at ABICAirScale
5GC000613: SM SW
gNB for FSEE
SR001534:
SR001783:
LTE5286: CommonSRAN
SRAN FM SWcombined
Dynamic loadSpectrum
for LTEserviceSharing
and SRAN
GSM+LTE
SR002459:
SRAN
SR001494:
gNB for FSEE
5GC000399:
SR001534: eCPRI
SRAN FM Fronthaul
combined interface
service
SR002459:
SR003007: BasicCommon SW5G SW load
Support for LTE
for mmWave
ASOE and
5GC001400: FA3UA Airscale
SRAN
SR002956:ModuleSBTS Operability
Extension n257 28G support for 5G
SR001494:
gNB for FSEE
WCDMA+LTE
SR002459: Common
LTE4898: NB-IoT:
SR003007: Basic SW SW
Multiple load
Support for
for LTE
non-anchorASOE and
carriers
SRAN
5GC000952: Recovery for Classical
SR002956: SBTS Operability support for 5G gNB
SR001494:
SR002576: AirScale
5GC000613:SBTS-5G SM
EAC support SW onsupport
concurrent for FSEE
gNBoperation with
SR001534:
OBSAI RUs SRAN FM combined
5GC000534:
SR002459: Common Digital Beamforming
SW load for LTE for eCPRI
and
based
SRAN RUs
LTE3236:
SR001494:Automatic
AirScale SMrecovery/optical
SW support for delay
FSEE
compensation of Nokia CPRI
SR001534: SRAN FM combined service IF link problems
compensation of Nokia CPRI IF link problems
SR003007:Remote
LTE3084: Basic SWFPFH Support for ASOE
PDU control via
SR003007:
AirScale SMBasic
SR001494: SWSM
AirScale Support for ASOE
SW support for FSEE
SR002382:
SR002187: SW SupportDSP
Automated for AirScale
HW recoveryCapacity
on
ABIO
ABIA including common ABIO and ABIN
Platform
5GC000718: SW F1 cell management
SR003007:
LTE5286: Basic SW
Common SW Support
load forfor ASOE
LTE andlink
SRAN
SR002696:
SR001494: FHS & AFAA
AirScale SM SWCPRI m-plane
support for FSEE
SR002459:
protection Common SW load for LTE and
SRAN
5GC002277: AEQZ AirScale MAA 32T32R
ARAN1163:
192AE n78 200W Iu-PS (CPRI)
Throughput Measurement for
GTP Traffic
SR001534:
SR001534: SRAN SRAN FM FM combined
combined service service
LTE2779: CPRI-A
operation
Platform with OBSAI RUs
SW
LTE4032:
5GC000847: AirScale Capacity CPRI
BTS Fronthaul ABIC 7 - 10GE
SR002956:
LTE4898: SBTS
NB-IoT: Operability
Multiple support for
non-anchor 5G
carriers
SFP+ Dual Fiber
5GC001451: BaseofLine
Support 8T8R RU for 2T2R /
SR002576:
5GC000933: SBTS-5G
MDEA concurrent
fronthaul operation
switch for 5G with
4T4R
OBSAI antenna
RUs deployments below 6GHz
deployments
SR002459: Commonrecovery/optical
SW load for LTE and
LTE3236:
SR002459: Automatic
Common SW load for LTEdelay and
SRAN
SRAN
SR002286:
5GC000399: Automatic
eCPRI recovery/optical
Fronthaul interface delay
ARAN1163:
compensation Iu-PS Throughput
of Nokia CPRIABICIF link problemsfor
Measurement
LTE4032:
GTP AirScale
Traffic Capacity
LTE5286:
LTE4898: Common
NB-IoT: SW load
Multiple for LTE and
non-anchor SRAN
carriers
LTE1996:
LTE3656: Flexi
MDEA Zone Controller
Fronthaul SwitchApplication
Outdoor
LTE3236:
SR001534: Automatic
SRAN FMrecovery/optical
combinedApplication delay DC
service
RAN1671:
SR002286:Enhanced
AutomaticUltraSite Base Band
recovery/optical delay
(EUBB)
RAN20:
SR002160:HSDPA parameterisation
I/Q routing between
LTE5286: Common
SR001534: SRAN FM load for system
SWcombined LTE andmodules
service SRAN
in SBTS running on AS+FSMF
LTE5286:
SRAN Common SW load for LTE and SRAN
LTE3656:
SR001612:MDEA LTE-FDDFronthaul Switch Outdoor
and LTE-TDD eNB in DC
LTE1996: Flexi Zone
SBTS running on AirScale Controller Application
SR001534:
SR003007:FDD
LTE2294: SRAN
Basic FM
SW
TDD combined
Support
Coexistence forservice
ASOEone eNB
within
SR002956:
LTE2464: SBTS Operability
Synchronization support
with Network forTime
5G
SR003007:
SR001612: Basic
LTE-FDDSW and
Support for ASOE
LTE-TDD eNB in
Protocol
SBTS running
LTE1996: Flexion AirScale
Zone Controller Application
LTE5286:
LTE2294: Common
FDD TDD SW load for LTE
Coexistence andone
within SRAN eNB
SR001534:
SR002459: SRAN
Common FM combined
SW load forservice
LTE and
SRAN
SRAN
5GC000316:
LTE5286: Common 5G NodeSWBloadSynchronization
for LTE and SRAN Mode
Support
ARAN1163: Iu-PS Throughput Measurement for
SR001534:
GTP Traffic SRAN FM combined service
5GC000316:
SR003007: Basic 5G Node B Synchronization
SW Support for ASOE Mode
Support
LTE1996:
LTE5286: Flexi
Common ZoneSW Controller
load forApplication
LTE and SRAN
SR001534:
SRAN
5GC000316: 5G Node
LTE5286: Common SWBload
Synchronization Mode
for LTE and SRAN
Support
SR001534:
5GC000980:
SR002956: SBTSALD support
Operabilityin gNB for Nokia
support for 5GCPRI
radio units
LTE2121:
SR002459:Radio Unit reset
Common SW load in BTS SM and
for LTE
SR001534:
SR002956:
SRAN SRAN
SBTS FM combined
Operability service
support for 5G
5GC000980: ALD support in gNB for Nokia CPRI
SR002956:
radio units SBTS Operability support for 5G
LTE5286:
SR002459: Common
Common SWSWloadload for
forLTE
LTE and SRAN
LTE2121:
SR002459: Radio Unit reset
Common SW in BTS
load for SM and
LTE and
SRAN
SRAN
LTE3923: sR&D
5GC000980: ALD support
LTE5286: Common SW load in gNB for Nokia
for LTE CPRI
and SRAN
radio units
SR001486: Support for already delivered
LTE2779: CPRI-Afeatures
SRAN16.2/16.10
SR001534:
LTE1996: SRAN FMController
combinedApplication
service
SR002956:Flexi
SBTSZone
Operability support for 5G
LTE3433:
LTE5286: Support
CommonforSW already
load fordelivered
LTE and SRAN
SR001534:
LTE2779: CPRI-A
radio units SBTS Operability support for 5G
SR002956:
LTE3923:
LTE5286: sR&D
Common SW load for LTE and SRAN
LTE2779:
SR002459:CPRI-A
SR001534:
LTE076-a: Support for legacy MHA
SR002459:
and5G
SRAN
5GC000159: 5G NodeB state management
SR001534: SRAN FM
LTE5286: Common SWcombined service
load for LTE and SRAN
SRAN
LTE2121: Radio Unit reset in BTS SM
SR001534:
SBTS Operability service
support for 5G
SRAN
SR003007:
SR001534: Basic
SRANSW FM Support
combined forservice
ASOE
SR002956:
5GC001167:SBTS FDD Operability
DL CA up tosupport 3 CCs for 5G
LTE5286:
5GC002589: Common
5G RF SW loadwith
sharing for LTE
two and SRAN
Airscale
SR002459:
System ModulesCommon SW load for LTE and
SRAN
5GC001866: Delivery of beam set realization to
SR001534:
SR002956: SRAN
gNB FM combined
support for 5G
5GC000829:
LTE5286: Common One classical
SW load gNB
for on
LTEdualandASIK
SRAN
LTE5111:
SR002459:NR-TDLTE
Common SW concurrent
load foroperation
LTE and for
eCPRI
SRAN radios
SR002382:
SR001534: SW Support for AirScale Capacity
support for 5G
Platform SW
SRAN
5GC002350:
CB007135: Phase 1SW
Common NR-LTE concurrent
for SRAN and 5G
SR001534:
SR002956: SRAN Operability
FM combined service
classical forSBTS
operation AEHC eCPRI radio support for 5G
LTE5286:
5GC001451:
5GC002589: Common
5GC002277: 5G Support
AEQZ SW of load
8T8R
RF AirScale
sharing with for
RU LTE
MAAtwo for and
2T2R SRAN
Airscale
32T32R /
SR002459:
4T4R
Systemantenna Common
Modules SW
deployments
192AE n78 200W (CPRI) load for
below LTE
6GHz and
SRAN
LTE3949:
SR002956:eCPRI/LLS
CB005793: RRU
SBTSremote based TDD
upgrade
Operability massive
from
support 5GMIMO
CPRI
for to
SR001534:
5GC001476:
eCPRI SRAN
DU FM
ABIL combined
configs:
legacy FDD CPRI
Radios (II) NR-LTE
CB005850:
SR002459: Common concurrent
SW loadMAA operation
for LTE andwith
5GC002277:
5GC001849:
shared FHS for AEQZ
Support
OBSAIAirScale
of 8T8R 8 port 32T32R
BF antenna
SRAN
192AE n78 200W (CPRI)
with calibration
5GC001698:
LTE2121: DU
Radio port below
reset6GHz
(ABIL+RU)
Unit inremote
BTS SM upgrade
SR002956:
5GC000918:
from CPRI SBTS
to Operability
Analog
eCPRI Beamforming support for for 5G
eCPRI
SR001534:
LTE5286: SRAN FM
Common SW combined
load for service
LTE and SRAN
based RUs MDEA fronthaul switch for 5G
5GC000933:
SR002459:
SR001682:
deployments Common
AirScale SW
Common load for
ASIB LTE PIUandSBTS
SRAN
support
LTE2121:
SR002459: Radio Unit reset
Common
(LTE-only configurations)SW load in BTS SM and
for LTE
SR001534:
SRAN SRAN FM combined
SR002459: Common SW load for LTE and service
5GC001821:
SRAN 5G DU configurations: additional
cmWave-CPRI
LTE5286: Common SW
LTE5286:
LTE5589: Common
TDD SW load
massive load
MIMO
for LTE
forone and
and SRAN
LTEcarrier SRAN
per
SR000912:
SR002459: SBTS
Common SW SWManagement
load for LTE and
ABIC
SRAN
5GC000534: Digital Beamforming for eCPRI
LTE-435:
based RUs RF sharing WCDMA-LTE
SR001498:
SR002160: Support of FSMF
I/Q routing between + FSMF
systemwith SRAN
modules
configurations
SR001534: SRAN FM
LTE5286: Common SWcombined
load for LTE service
and SRAN
configurations
2002040:
SR002956: FN2040
SBTS Operability support for 5G
SR001534: SRAN FM
load for LTE service
and SRAN
SRAN
SRAN
LTE2121:
5GC002277: Radio
AEQZUnitAirScale
reset in MAABTS SM 32T32R
CB006135:
SR001534: Docomo
SRAN FM ORAN
combinedProfile L1
service
192AE n78 200W (CPRI)
implementation Step 2 (FD Beamforming)
CB007135: Common SW for SRAN support andfor5G
5G
5GC000167:
classical Fault Management general flow
and mechanism
CB005850:
5GC002277: NR-LTE concurrent
AEQZ AirScale MAA operation
32T32Rwith
SR001534:
shared SRAN
FHS200W
192AE n78 FM combined service
for OBSAI
(CPRI)
CB006286:
SR002956: Nokia-CPRI
SBTS Operability FDD Radio
support Unit
for chaining
5G
in 5G
5GC000167: Fault Management general flow
CB006028:
and Independent software upgrade for
mechanism
shared RU SRAN FM combined service
SR001534:
192AE n78 200W (CPRI)
5GC000167: Fault Management general flow
operation for AEHC eCPRI radio
and mechanism
5GC002277: AEQZ AirScale concurrent
MAA 32T32R
5GC001702: NR-LTE/SRAN
SR001534:
192AE n78 SRAN (CPRI)
200W FM combined service
SR002956:LAA
Dynamic Power support
Controlfor 5G
5GC000167: MDEA
fronthaul switch general
for 5Gflow
and mechanism
deployments
SR003007:Common
LTE5286: Basic SW SW Support
load forforLTE
ASOE and SRAN
SR001534:
SR001730:
SR002956: SRAN
SR002459: Fronthaul
SBTS
switch
Operabilityload forservice
supportLTEon
support forSBTS
and5G
(LTE-only
SR001612:
SRAN configurations)
LTE-FDD and LTE-TDD eNB in
SR002459:
SBTS Common
running
LTE1656: SWsupport
on AirScale
Management load forforLTE and
legacy
SRAN
LTE2294: FDD TDD
Motorola/Fujitsu Coexistence within one eNB
RF-equipment
5GC001400:
SR002459: FA3UA
SR001534: Common
SRAN FM5GSW Airscale mmWave
load forservice
combined LTE and
Extension
SRAN Module n257 28G
LTE4898:
LTE5286: NB-IoT:
CommonMultiple
SW load non-anchor
for LTE and carriers
SRAN
LTE5635:
5GC000318: NB-IoT Guardband
1PPS&ToD SyncCoexistence
from External with
NR
GNSS Receiver
SR001534:
SR002576: SRAN
5GC000316:SBTS-5G FM concurrent
5G Node combined service
operationMode
B Synchronization with
OBSAI
SupportRUs
5GC001991:
LTE1996: FlexiAntenna tilt for 2D Application
Zone Controller GoB
LTE5286:
LTE80: GPS Common SW load for LTE and SRAN
Synchronisation
5GC000167:
SR001534: SRANFault FM
Management
combined general
service flow
and mechanism
LTE5286:
LTE3656: Common SW loadSwitch
MDEA Fronthaul for LTE and SRAN
Outdoor DC
SR002459: Common
2002040: FN2040 SW load for LTE and
SRAN
SR001534: SRAN
LTE1996: Flexi FMController
Zone combinedApplication
service
LTE2779: CPRI-A
LTE1656:
SR002956:Management
SBTS Operabilitysupport for legacy
support for 5G
SRAN
LTE1996:
SR002956:Flexi
SBTS Zone Controller
support for 5G
LTE5286: Common SW load for LTE service
and SRAN
SRAN
SR001534: SRAN FM
SRAN
LTE5286:
SR002956:Common SW load for
SBTS Operability LTE and
support SRAN
for 5G
SR002459: Common SW load for LTE
5GC000933: MDEA fronthaul switch for 5G and
SRAN
deployments
LTE2121:
LTE5286: Radio
CommonUnitSW
reset
loadin for
BTS SMand SRAN
LTE
SRAN
CB007135:
SR001730: Common
Fronthaul SW for support
switch SRAN and 5G
on SBTS
classical
SR002956:
SR002956: SBTS
SBTS Operability support for
for 5G
SR001534:
LTE5286: SRAN Operability
FM combined support
service 5G
SR002459: Common SW load for LTE andSRAN
SR002459:
SRAN
LTE2121:
LTE2121: Radio
Radio Unit
Unit reset
reset inin BTS
BTS SMSM
SR001534:
support for 5G
LTE2779: CPRI-A
LTE1656:
SR002459:Management
Common SWsupport load forforLTE
legacy
and
Motorola/Fujitsu
SRAN RF-equipment
LTE2779:
CB007135: CPRI-A
Common SW
CB007135:
LTE2121: Common
Radio SW for
Unit resetfor SRAN and
in SRAN
BTS SM and 5G
5G
classical
classical
LTE1996:
SR002956: Flexi
SBTSZone Controller
support for
SR002956:
SR001534:
5GC000159: SBTS
SRAN Operability
FM
5G NodeB combined support
statefor for 5G
service
management 5G
LTE5286:
SR002459: Common
Common SWSW load
load LTE
for LTE and
andSRAN
5GC000664:
SR002459: AEQD AirScale
Common SW load MAA
for 64T64R
LTE and
SRAN
128AE B43 200W
SRAN
LTE5286: Common SW load for LTE for
and5GSRAN
5GC000933:
LTE2121: MDEA
Radio fronthaul
Unit reset in switch
BTS SM
LTE2121: Radio
deployments Unit reset in BTS SM
SR001534:
LTE1996: SRAN FMController
combinedApplication
service
SR002459:Flexi Zone
SR001534:
LTE2779:
LTE5286: CPRI-A
LTE1656:
5GC000562:Management support
AEQA AirScale MAA for64T64R
legacy
Motorola/Fujitsu
192AE B42 200W RF-equipment
LTE2121:
5GC001163:Radio Unit reset
CPRI-A supportin BTS SM
in gNB-DU
SR001534:
SR002459: SRAN
CommonFMSW combined forservice
loadsupportLTEforand
SR002956:
CPRI-A 5G
SRAN
LTE2779:
SR002459:CPRI-A
LTE2121:
SRAN Radio Unit reset in BTS SM
LTE1996:
5GC000664:Flexi ZoneAirScale
AEQD ControllerMAAApplication
64T64R
SR001534: SRAN
128AE B43 200W FM combined service
5GC000562: AEQA AirScale MAA 64T64R
192AE B42 200W
SR001534:
support for 5G
SRAN
SR001534: SRAN FM
SR002459:
and5G
SRAN
LTE2779: CPRI-A
deployments
SR001534: SRAN FM
SRAN
5GC000664:
SR002956: SBTS AEQD AirScale MAA
Operability 64T64R
support for 5G
128AE
LTE5286:B43Common
200W SW load for LTE and SRAN
5GC000933:
SR002459: MDEA fronthaul
Common switch
SW loadsupportfor LTE forand
5G
SR002956:
deployments SBTS Operability for 5G
SRAN
LTE5286: Common SW load support
for LTE on andSBTS
SRAN
SR001730:
LTE1996: Fronthaul
Flexi switch
Zone Controller Application
SR002459:
(LTE-only Common SW
configurations) load for LTE and
SR001534:
CB007135:
SRAN SRAN FMSW
Common combined
for SRAN service
and 5G
SR002459:
LTE2779:
SRAN CPRI-A
5GC002589:
LTE2121: 5G Unit
Radio RF sharing
reset inwith
BTS two
SMandAirscale
LTE5286:
System Common
Modules SW load for LTE SRAN
LTE1996:
5GC000562: Flexi ZoneAirScale
AEQA Controller MAA Application
64T64R
CB005850:
SR001534: NR-LTE
SRAN FM concurrent
combinedoperation
service with
192AE B42
shared FHS200Wfor OBSAI
LTE2121:
SR003025:RadioInter Unit
eNB reset in BTSwith
RU sharing SM CPRI
LTE1996: Flexi
interface on ABIO Zone Controller Application
SR001534:
5GC001524:
SR002956: SRAN
NR-LTE
SBTS FM concurrent
combined
Operability service
operation
support for for
SR002956:
LTE2779:
eCPRI SBTS
CPRI-A
radios Operability support for 5G
5G
LTE5286:
5GC000933: Common
MDEA SW load for
fronthaul support LTE and
switch for 5G SRAN
SR002956:
SR002459: SBTS
Common Operability
SW load for LTEfor and5G
deployments
SRAN
operation
LTE151: for AEHC eCPRI
Autonomous LTEloadradio
eNB Operability
SR002459:
SR001682: Common
AirScale SW
Common for
ASIBLTEPIU andSBTS
SR001534:
support
SR001730:
SR002459: Fronthaul
Common SW switch
load support
for LTE onandSBTS
CB007135:
(LTE-only
CB007135: Common
SW
configurations) for SRAN and 5G
SRAN
classical
LTE2121:
classical
LTE4824: Radio
NR-LTE Unit reset in BTS
concurrent SM for TDD
operation
SR002956:
SR001534:
SR002956: SBTS
SRAN Operability
FMmodecombined support
servicefor
for 5G
MAA radios SBTS
5GC000933: with
MDEA
Operability
split
fronthaul
support
switch for 5G
5G
5GC002027:
LTE5286: AirScale Indoor Radio
Common SW load for LTE and SRAN ASiR-sHUB
deployments
with hybridNR-LTE
fiber andFDDeCPRI interfaceoperation
(APHG) for
LTE4461:
SR001730: Fronthaul concurrent
switch support on SBTSwith
LTE5454:
CPRI RUs AirScale Indoor Radio ASiR-sHUB
(LTE-only
hybrid fiberconfigurations)
and eCPRI interface (APHG)
SR001534:
SR002459: SRAN FMSW combined forservice
5GC000933:CommonMDEA fronthaul loadswitch LTE forand
5G
SRAN
deployments
LTE5286:
SR001730:Common
Fronthaul SW load support
switch for LTE on andSBTS
SRAN
LTE2121: Radio Unit
(LTE-only configurations) reset in BTS SM
SR001534:
SR002459: SRANCommon FMSW combined
load forservice
LTE and
SRAN
CB007135:
LTE2121:
CB007135:RadioCommon SW
SW for in SRAN and 5G
SR002956:
classical SBTSUnit
Common reset
Operabilityfor BTS
SRAN SM
support andfor5G
5G
SR001534:
classical
LTE5286: SRAN FM
Common SW combined
load for service
LTE and SRAN
SR002956:
SR002956: SBTS
SBTS Operability
Operability support
support for
for 5G
5G
SR002459:
5GC000933: Common
MDEA SW load
fronthaul for LTE and
switchASiR-sHUB
for 5G
5GC002027:
SRAN AirScale Indoor Radio
deployments
with hybridRadio
fiber and
LTE2121:
SR001730: UniteCPRI
Fronthaul reset
switch ininterface
BTS SMon
support
(APHG)
SBTSwith
LTE5454:
SR001534: AirScale
SRAN Indoor
FM Radio
combined ASiR-sHUB
service
hybrid fiber and eCPRI interface (APHG)
SR002459:
5GC000933:Common SW loadswitch
MDEA fronthaul for LTE forand
5G
SRAN
deployments
LTE5286:
SR001730:Common
SRAN
LTE2779: CPRI-A
LTE2779: CPRI-A
LTE1656:
CB007135:Management
Common SWsupport for SRAN for legacy
and 5G
Motorola/Fujitsu
classical RF-equipment
SRAN
CB007135: Common SW for SRAN and 5G
SR001534:
classical SRAN FM combined service
SRAN
classical
SR002956:
SR002956: SBTS
SBTS Operability
Operability support
LTE and
support for
for 5G
SRAN
5G
5GC000933:
SR002459:
5GC000933: MDEA
Common
MDEA SW fronthaul
SW load
fronthaul switch
for
switchLTEfor
for 5G
and
5G
LTE5286:
deploymentsCommon load for LTE and SRAN
SRAN
deployments
LTE5286:
SR001730: Common
SRAN
SRAN
(LTE-only
SR001682: configurations)
AirScale Common ASIB PIU SBTS
SRAN
support
SRAN
LTE923: TD-LTE Ir interface support
LTE3236: Automatic recovery/optical delay
5GC000375:
compensation5G of Performance
Nokia CPRI IFMonitoring for
link problems
CPRI Link
LTE2121: Radio
compensation of Unit
Nokia reset
CPRI in IF
BTS linkSM
problems
and SRAN
5GC000375: 5G Performance Monitoring for
CPRI Link
LTE2121:
SR002956:Radio
SBTSUnit reset in BTS
Operability supportSMfor 5G
SRAN
SR001534:
support for5G
5G
CB007135: Common SW for SRAN and
LTE5286:
classical Common SW load for LTE and SRAN
5GC001163: CPRI-A support in gNB-DULTE and
SRAN
SR001534:
SR002459: SRAN
CommonFMSW combined
load forservice
LTE and
SRAN
LTE2779: CPRI-A
SRAN
SRAN
SRAN
SRAN
SRAN
SRAN
SRAN
LTE2121:
LTE5286: Radio
CommonUnitSW
reset in for
load BTS SMand SRAN
LTE
SRAN
LTE2121:
LTE5286: Radio
CommonUnitSW
reset in for
load BTS SMand SRAN
LTE
SRAN
SR001682: AirScale Common ASIB PIU SBTS
support
SR002459: Common
LTE5454: AirScale SW load
Indoor RadioforASiR-sHUB
LTE and with
SRAN
hybrid fiber and eCPRI interface (APHG)
LTE2121:
SR002489:Radio
PSU Unit reset
alarm in BTS
support for SM
CPRI- L3
RRU
SRAN
SR002459: Common
LTE5317: FDD CPRI-A SW
RFload for LTE
Chaining and on
Configs
SRAN
AirScale
LTE2121:
LTE2956: Radio
CPRI-AUnit
RFreset in BTS SM
chaining
SRAN
CB007135: CommonSW
LTE5286: Common SWload
for SRAN
for LTEand
and5G
SRAN
classical
5GC002413: eCPRI FH synchronization
extension
LTE1996: Flexi ZoneSW
LTE5286: Common Controller
load forApplication
LTE and SRAN
SRAN
5GC001025:
5GC000613: NR-LTE concurrent
EAC support on gNBoperation for
CPRI TDD MAA radios
SRAN
SR000356:
5GC001163:IPsec for BTS
CPRI-A support in gNB-DU
SR001534:
LTE5286: CommonFM
SRAN SWcombined service
SRAN
LTE2779: CPRI-A
SRAN
LTE2779: CPRI-A
5GC001163: CPRI-A support in gNB-DU
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A

SRAN

SR002459:
5GC001163:Common
CPRI-A SW loadinfor
support LTE and
gNB-DU
SRAN
SRAN
LTE2779: CPRI-A
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A
SR001534: SRAN FM
SRAN
LTE2779: CPRI-A

SRAN
CB005906: eCPRI based TDD massive MIMO on
ABIO/N
classical
CB006942:
ABIO/N BTS (Q)SFP+/SFP28 provisioning
5GC001240:
enhancements PIM Cancellation
SR003007:
LTE4721: Basic SW
AirScale Support
Radio, PIM for ASOE and
counters
SR002382:
LTE5286:
CB007135: SW Support
Common
Common SWSW for
load
forAirScale
for
SRAN LTE Capacity
andand5GSRAN
PIM
ABIO cancellation
including alarm enhancements
SR002459:
classical
LTE5286: Common
Common SWSW load
load forfor LTE
LTE andSRAN
and
Platform
SRAN
CB006942: SWBTS (Q)SFP+/SFP28 provisioning
SR002459:
SR003007:
5GC000955: Common
Basic SWSW
SFP/QSFP load for
Support
control for LTE
ASOE and
enhancements
SRAN
CB007135: Common SW for SRAN and
SR002956:
SR002382: SBTS
SW Operability
Support support
for AirScale for5G
5G
Capacity
SR001740:
classical
5GC000847: LTE
BTS feature parity
Fronthaul alignment
CPRI 7 - 10GEto FDD-
ABIO including
LTE17SP
SR002382: on
SW common
Airscale
Support ABIO
for and ABIN
AirScale Capacity
SFP+ Dual
Platform SWFiber Base Line
LTE3368:
ABIO PIM
including
5GC001179: Cancellation
common
BTS ABIO
Fronthaul for
CPRI 7 - radios
CPRI-A
and ABIN
5GC000955:
Platform SW SFP/QSFP control
QSFP+/QSFP28
SR002956: SBTS Base Line support for 5G
Operability
5GC000955:
5GC000848: SFP/QSFP
BTS Fronthaulcontrol
CPRI 7
5GC000847:
SR002956: BTS Fronthaul
SBTS Operability CPRI 7 -- 10GE
support for 5G
SFP+/SFP28
SFP+ Dual
Dual Fiber Fiber Base Line
5GC000847:
SR001534: BTSBase
SRAN FM
Line CPRI 7 - 10GE
Fronthaul
combined service
5GC001179: BTSBase
SFP+ Dual Fiber Fronthaul
Line CPRI 7 -
QSFP+/QSFP28 Base
5GC001179: BTS Fronthaul Line CPRI 7 -
5GC000848:
QSFP+/QSFP28 Base Line CPRI 7 -
BTS Fronthaul
SFP+/SFP28 Dual Fiber
SR002459: Common SWBaseload Line
for LTE and
SR001534:
5GC000848: BTS Fronthaul CPRI 7 -
SFP+/SFP28 Dual Fiber Base Line
SRAN

support

support
SRAN
SRAN
SRAN
SRAN
SRAN
SRAN
5GC001082: Classical gNB software
Management
SR001534: SRAN FM
SRAN
50160: TCP/IP measurement
SRAN
SRAN
SR001534:
SR002459: SRAN FMSW
Common combined
load forservice
LTE and
SRAN
support
SR002951:
SRAN Basic SW support for AGIML AI/ML
SR002187:
PoC HW Automated DSP HW recovery on
SR001534:
ABIA SRAN FM combined service
LTE5286:
SR002459:Common
CommonSW SWload
loadfor
forLTE
LTEand
andSRAN
SR002459:
SRAN
outdoor subrack
full compatible
SR003007:
SR001534: Basic
SRANSW FM Support
combined forservice
ASOE
CB007422: 5G BTS Supervision harmonization -
LTE5286: Common
Part II (signature for SW load for LTE and SRAN
crash/failure)
SR002459: Common SW
5GC000470: AirScale Common load for LTE and
ASIB
SRAN
SR001534: SRAN FM
SRAN
ARAN1219: Latency Statistics for UE Positioning

SR001547: Loose Phase and Time

Synchronization

Platform SW
GSM+LTE
GSM+WCDMA
5GC001240: PIM Cancellation
LTE4721: AirScale Radio, PIM counters and
PIM cancellation alarm enhancements
SR002275: Enhancements
LTE5286: Common SW loadtofor
Flexible MCPA
LTE and SRAN
power pooling
SR002459: for
Common GSMSWRAT in
load SRAN
for LTE and
SRAN
LTE4721: AirScale Radio, PIM counters and
SR001740: LTE feature
PIM cancellation parity alignment to FDD-
alarm enhancements
LTE17SP on Airscale
LTE3368:
SR002459:PIM Cancellation
Common SW loadfor for
CPRI-A radios
LTE and
SRAN
SR001740: LTE feature parity alignment to FDD-
LTE17SP on Airscale
LTE3368:
LTE4721: PIM Cancellation
AirScale for CPRI-A
Radio, PIM countersradios
and
PIM cancellation alarm enhancements
SRAN

SRAN

classical

classical

classical

classical

classical
5GC000169: 5G Node B basic faults indication

classical

LTE656: LTE Fault Management

support

CB007135:
LTE656: LTE Common SW for SRAN and 5G
Fault Management
classical
5GC001167: FDD DL CA up to 3 CCs
5GC002589: 5G RF sharing with two Airscale
System Modules
5GC000829: One classical gNB on dual ASIK
LTE5286: Common for AirScale
SW load for LTE Capacity
and SRAN
ABIO including
SR002459: common
Common SWABIO andLTE
load for ABIN and
LTE1996:
Platform
SRAN SW Flexi Zone Controller Application
LTE656:
SR002956:
SR001612: LTE FaultOperability
SBTS
LTE-FDD Management supporteNB
and LTE-TDD for 5G
in
SR001612: LTE-FDD and
SBTS running on AirScale LTE-TDD eNB in
SBTS running
LTE2294: FDDon AirScale
TDD Coexistence within one eNB
5GC000181:
LTE1996: FlexiHW addition
Zone and removal
Controller without
Application
service impact
LTE5020: LTE/CDMA1X RF Sharing with
URCB/URCC
LTE656:
SR002459: LTE Fault Management
SRAN
based RUs
SR001334:
LTE656: LTE Isolated GSM RAT reset for SBTS on
Fault Management
AirScale
SR002160: I/Q routing between system modules
LTE656:
SR001307: LTE FaultLogical
Single Management
SBTS on AirScale +
FSMF
SR001610: Isolated GSM RAT reset for SBTS on
FSMF
Platform SW
LTE4898: NB-IoT: Multiple non-anchor carriers
SRAN
LTE2578:
SR003007:RRU
SR002382: Basic
SW path
SWfailure
for handling
Support
Support for ASOE
AirScale Capacity
improvement
SR002382:
ABIO includingSWfor TDD
common 8
Support path
for
ABIO beamforming
AirScale
and Capacity
ABIN
SR003007:
LTE1996:
ABIO includingBasic
Flexi SWController
Zone
common Support
ABIO for ASOE
Application
and ABIN
Platform
LTE654:
Platform
SR002956: LTE
SW Configuration
SBTS Operability Management
support for 5G
5GC000319:
SR001534:
SR002956: Flexible
SRAN FM Sync Input
combined
SBTS Operability Priority
service
support for 5G
LTE5286:
SR002459:Common CommonSW SWloadloadfor
forLTE
LTEand andSRAN
SR002459:
SRAN
LTE1996:
5GC000425: Flexi
TDDZone Controller
lower layer Application
support - 100 MHz
SR003007:
5GC000952: Basic SW
Recovery Support
for for ASOE
Classical gNB
SR001534:
cell bandwidth SRAN FM combined service
CB007135:
LTE5286: Common SW load for LTE and5G
Common SW for SRAN and SRAN
5GC000318:
classical 1PPS&ToD
SR002187: Automated DSPSync HW from External
recovery on
GNSS
ABIA Receiver
LTE1996:
5GC002589: Flexi
5G Zone Controller
RFManagement
sharing Application
5GC000167:
CB007135: Common Fault SW for with
SRAN twoand
Airscale
general flow
5G
SR001534:
System SRAN
Modules
and mechanism FM combined service
classical
5GC000829:
5GC000316: One
5GC002589: 5G RF classical
Node gNB
withon
B Synchronization
sharing twodual ASIK
Mode
Airscale
LTE5111:
Support Modules
System NR-TDLTE concurrent operation for
eCPRI
LTE1996: radiosFlexi Zone Controller
CB005850: NR-LTE concurrent operation withApplication
SR002382:
SR002956:
SR001534:
shared FHS SW
SBTS
SRAN Support
FM
for OBSAI for AirScale
Operability
combined support Capacity
servicefor 5G
LTE5286:
ABIO
LTE5286: CommonCommon
including SW
common
SW load
ABIO
load for
andLTE
for LTE and
ABIN
and SRAN
SRAN
SR003025:
SR002459: Inter
Common eNB RU
SW sharing
load for with
LTE CPRI
and
Platform
SR002459:
interface SW
on Common
ABIO SW load for LTE and
SRAN
SR002956:
SRAN SBTS Operability support for 5Gfor
LTE5111:
LTE1996: NR-TDLTE
Flexi Zone concurrent
Controller operation
Application
5GC002350:
5GC000167:
eCPRI radios Phase
Fault 1 NR-LTE
Management concurrent
general flow
SR001534:
operation
and mechanism SRAN
for AEHC FM combined
eCPRI radio service
5GC001524: NR-LTE concurrent operation for
LTE3949:
SR001486:
eCPRI radioseCPRI/LLS
Support forbased
already TDD massive MIMO
delivered
5GC001476:
SRAN16.2/16.10 DU ABIL configs:
features
SR002956: SBTS Operability support for legacy FDD 5GCPRI
Radios
LTE1996: (II) Flexi Zone Controller
5GC002350: Phase 1 NR-LTE concurrent Application
LTE4875:
LTE656:
operation LTELAA
for Dynamic
Fault
AEHC Power
Management
eCPRI radio Control
LTE5286:
SR002459: Common
Common SWSWloadloadfor
forLTE
LTEand andSRAN
5GC001702:
Common SW loadconcurrent
for LTE and
SRAN
SRAN
LTE4788: ETSI and ICconcurrent
DFS Support for LAAfor
5GC001025:
LTE1996: NR-LTE
Flexi Zone operation
Controller Application
5GC001821:
CPRI TDD MAA 5G DU configurations:
radios additional
SR001534:
cmWave-CPRI SRAN FM combined service
5GC000726: NR-LTE FDD concurrent operation
LTE4955:
for CPRI RUs AirScale Capacity cards mixed within
one eNB
LTE5286:
SRAN Common SW load for LTE and SRAN
LTE2442:
SR002576:Preventing
SBTS-5G cell activation
concurrent operation with
OBSAI RUs
LTE447: SW support for RF sharing GSM-LTE
CB007135: Common
SR001682: SW for SRAN
AirScale Common ASIB andPIU 5GSBTS
classical
support
SR002382:
LTE1996: Flexi SW Zone
Support for AirScale
Controller Capacity
Application
ABIO
LTE151:including common
Autonomous LTEABIOeNB and ABIN
Operability
SR002956:
Platform SWSBTS Operability support for 5G
LTE5286:
support SRAN
for 5G
SR002459: Common SW load
LTE5286: Common SW load for LTE and SRANfor LTE and
SRAN
SR001534:
LTE654a: LTE Configuration Management 1/2
2002040:
SR002956: FN2040
SR001534:
LTE5286: Common SRAN FM SWcombined
load for LTEservice
and SRAN
SRAN
LTE-435: RF sharing WCDMA-LTE
LTE5286: Common
5GC002277: AEQZ SW load MAA
AirScale for LTE and SRAN
32T32R
SR002459: Common
192AE n78 200W (CPRI)SW load for LTE and
SRAN
RAN1770: RF Sharing
LTE5286: Common SWinload
WCDMA-GSM
for LTE and SRAN
SR001534:
SR002459: SRAN
CommonFM combined
SW load forservice
LTE and
SRAN
192AE n78 200W (CPRI)
LTE1227:
SR002956:Flexi
SBTSMultiradio BTSsupport
Operability SW Download
for 5G for
Antenna Line Devices
SR001534:
SR002459: SRAN
CommonFMSW combined
load forservice
LTE and
SRAN
LTE1227: Flexi Multiradio BTS SW Download for
Antenna Line Devices

192AE n78 200W (CPRI)
SR001538: WCDMASW
LTE5286: Common Support in new
load for LTE Single BTS
and SRAN
O&M architecture
SRAN
LTE1976:
SR002382:Support for single
SW Support and multi-antenna
for AirScale Capacity
RET
SR001534:
Platform SWSRAN FM combined service
LTE5286:
support SRAN
for 5G
5GC001146: Common OAM on classical gNBfor LTE and
SRAN
SR001534:
SR002459: SRAN
SR003007: Basic
Common FMSW
SW combined
load forservice
Support ASOE
LTE and
CB007422:
SRAN 5G BTS Supervision harmonization -
Part II (signature
FSM3TD57:
CB007310: Common
One for crash/failure)
application
classical SW adaptation
LTE5317:
CB007310: FDD
One CPRI-A
classicalRFgNB
gNB
on dual
Chaining
on
ASIL on
Configs
dual ASIL
for FSM-r3
AirScale Base services
SR002956:
SR001534:
5GC001146: SBTS
SRAN Operability
CommonFM chaining
combined support for 5G
service gNB
OAM on classical
LTE2956:
5GC001146: CPRI-A
CommonRF OAM on classical gNB
5GC001121:
LTE5286: AMODSW
Common outdoor
load sub-rack
for LTE for 5G
and SRAN
LTE5286:
SR002459:Common
CommonSW SWloadloadfor
forLTE
LTEandandSRAN
SR002459:
SRAN
SR001534:
FSM3TD57: SRAN
Common FM application service
SW adaptation
for FSM-r3
outdoor Base services
subrack
SR001498:
SR002203: Support of FSMFoutdoor
AMOD AirScale + FSMF with SRAN
subrack
CB005850:
configurationsNR-LTE concurrent operation with5G
full compatible
shared FHSSRAN for OBSAI
SR001534:
SR001498: FMof combined service
SR002956: Support FSMF +
SBTS Operability FSMF
support with
for 5GSRAN
configurations
SR001534:
Management SRAN FM combined service
CB005850:
FSM3TD57: NR-LTE
Common concurrent
application operation with
SW adaptation
LTE1996:
shared FHSFlexi
for Zone
OBSAI Controller Application
for FSM-r3
LTE1854: Base services
SR002956:-hSBTS (System Upgradesupport
Operability to RL70-
for 5G
consistent SW fallback
LTE882a1:
Management System Upgrade with Backward
Compatibility
LTE1996: Flexi FDD
Zoneconversion
SR001534: SRAN
LTE1854: -h (System FMUpgrade
combined toservice
RL70-
LTE882a1: System Upgrade with Backward
Compatibility FDD conversion
classical
CB006286: Nokia-CPRI FDD Radio Unit chaining
in 5G
LTE5317:
CB005850:FDD CPRI-A
NR-LTE RF Chaining
concurrent Configs
operation withon
AirScale
shared FHS for OBSAI
LTE2956:
SR002956:CPRI-A RF chainingsupport for 5G
SBTS Operability
LTE5286: Common
5GC001082: Classical SWgNBloadsoftware
for LTE and SRAN
SR002459:
Management Common SW load for LTE and
SRAN
LTE977:
LTE1854: RF chaining
CB005850:-hNR-LTE
(Systemconcurrent
Upgrade to RL70- with
operation
LTE882a1: System Upgrade
LTE5286: Common SW load with Backward
for LTE and SRAN
Compatibility
SR002459: FDD
Common conversion
SW load for LTE
CB007135: Common
SR001534: SRAN FMSW for SRAN
combined andand
service 5G
SRAN
classical
LTE1996:
5GC001904: Flexi Zone Controller
LTE-NR In-Carrier Application
Dynamic
LTE882a1:
Spectrum Sharing Phase I with Backward
System Upgrade
Compatibility
LTE5286: CommonFDD conversion
SW load for LTE and SRAN
SR001534: SRAN
SR002459: Common FMSWcombined
load forservice
LTE and
SRAN
LTE2779: CPRI-A
SR001534:
support for 5G
SRAN
SR001534: SRAN FM
SRAN
LTE595-b15: FSMr3b
SRAN
LTE1996: Flexi Zone
LTE3084: Remote Controller
FPFH Application
PDU control via
AirScale SM
LTE3043:
CB005850:Remote
NR-LTEPower Port Control
concurrent for FPFD
operation with
PDU
SR001534: SRAN FM
SRAN
LTE447: SWCommon
SR002459: support for
SW RF sharing
load for GSM-LTE
LTE and
SR003007:
SR001534: Basic
SRAN SW
FM Support
combined forservice
ASOE
SRAN
LTE1815: Clock
5GC000319: SlaveSync
Flexible modeInput
for TD-SCDMA
Priority and
TDLTE dual mode on FSIH
LTE-435:
SR002459:RFCommon
sharing WCDMA-LTE
SW load for LTE and
SR001534:
5GC000318: 1PPS&ToD
SR002956: SBTS Syncsupport
Operability from External
for 5G
GNSS Receiver
5GC000319: Flexible Sync Input Priority
LTE1996:
LTE5286: Flexi
CommonZoneSWController
load forApplication
LTE and SRAN
SR001534:
SR003007: Basic SW Support for LTE
Common SW load for ASOE and
SRAN
5GC000318:
5GC000319: 1PPS&ToD
Flexible Sync Sync
Inputfrom External
Priority
GNSS Receiver
SR001534:
SR002459: SRAN
Common FMSWcombined
load forservice
LTE and
SRAN
5GC000318: 1PPS&ToD Sync from External
GNSS Receiver
SR002459:
SR003007: Common
Basic SWSW load for
Support for LTE
ASOE and
SRAN
LTE2956: CPRI-A RF chaining
5GC000318:
Flexible Sync from
Input External
Priority
GNSS Receiver
SR001534:
SR002459: SRAN
Common FMSWcombined
load forservice
LTE and
SRAN
5GC000318: 1PPS&ToD Sync from External
GNSS Receiver
SR001534:
SR002459: SRAN FMSW
Common combined
load forservice
LTE and
SRAN
radio unitsCommon SW load for LTE and SRAN
LTE5286:
2002040:
SR002459: FN2040
SRAN
5GC000980:
SR002956: ALD support
SBTS in gNB for Nokia
Operability for 5GCPRI
SR003007:
radio units Basic SW Supportsupport
for ASOE
LTE5286:
SR002956: Common
SBTS SW load for
Operability LTE and
support SRAN
for 5G
SR001534:
5GC001028: SRAN FM combined
Backplane Interfacesservice
for Subrack
5GC000422: GNSS firmware upgrade
Sharing
WM0628:
URCB/URCC WM0628
LTE1996:
Common Controller
load forApplication
LTE and SRAN
SR001534:
SRAN
SR001612: LTE-FDD and LTE-TDD eNB in
SBTS running on AirScale
SR001534: SRAN FM
SR002459:
and5G
SRAN
LTE923: TD-LTE
SR002459: Ir interface
Common SW load support
for LTE and
SR001534:

SRAN

SR002459: CommonSW
loadfor
forLTE
LTEand
andSRAN
SRAN
SRAN
LTE1444: FBBC basic start up, auto detection
and transparent mode


SRAN
LTE5286: Common SW load
LTE2054: Measurement for addition
Report LTE andwith
SRAN
PDCP KPI counter subset
LTE1053: Real-time KPI-monitoring with Traffica
SR000919: SBTS Real Time Performance
Monitoring

SR003007:
LTE1919: TDD
CB007135: Basic SWSWSupport
Intra-band
Common for ASOE
Multi-Carrier
for SRAN and 5G
SR002956:
Operation
classical SBTS
for Operability
Two-board FZM support
BTS for 5G
5GC000319:
5GC002589: Flexible
5GZone Sync
RF sharing Input Priority
with two Airscale
LTE1996:
LTE5286: Flexi
Common SWController
load forApplication
LTE and SRAN
System
LTE505: Modules
LTE505 Transport Separation for RAN
SR002459:
CB005850: Common SW load for
NR-LTE concurrent operationLTE and with
sharing
SRAN
shared FHSSRAN
SR001534: for OBSAI
FM combined service
SR001612:
SR003025: LTE-FDD
Inter eNB and LTE-TDD
RU sharing eNB
with in
CPRI
SBTS running on
interface on ABIO AirScale
5GC000318:
SR002956: SBTS 1PPS&ToD Syncsupport
Operability from External
for 5G
GNSS Receiver
SR001534:
SR002459: SRAN
Common FMSWcombined
load forservice
LTE and
SRAN
LTE1710: Temporary Master Role for LTE Radio
Slave
SRAN
Motorola/Fujitsu
LTE5286: Common RF-equipment
SR001534: SRAN
load forservice
LTE and
SRAN
LTE1656:
CB005850:Management support operation
NR-LTE concurrent for legacywith
SR001534: SRAN FM
SRAN
LTE1829: LTE-LTE RF sharing
SR003007: Basic SW
LTE5286: Common SWSupport
load forforLTE
ASOE
and SRAN
SR002956:
SR002459: SBTS
Common Operability
SW loadsupport
for LTEfor
and5G
LTE2956:
SRAN CPRI-A RF chaining
LTE5286:
LTE5317: Common
FDD CPRI-ASW RF
load for LTE Configs
Chaining and SRAN
on
SR002459:
AirScale Common SW load for LTE and
SRAN
LTE1976:
SRAN Support for single and multi-antenna
RET
LTE2779: CPRI-A

LTE654a:
LTE5286: LTE
CommonConfiguration
SW load Management 1/2
for LTE and SRAN
SRAN
LTE4875: LAA Dynamic Power Control
LTE2154:
LTE5286: Cell state SW
Common auditload
alarm
for LTE and SRAN
SR001534:
SRAN
LTE2305: Inter eNodeB Carrier Aggregation for 2
macro eNodeBs
SRAN
LTE1996:
SR001539:Flexi
LTEZone Controller
Security Feature
Parity with Single OAM
Management
LTE790: Signed SW
SRAN
SR001539:
SR002956: LTESBTSOperability
OperabilitySecurity
supportFeature
for 5G
5GC001082: ClassicalSW
SR002459: Common gNB software
load for LTE and
Management
SRAN
LTE790:
SR001539: Signed Operability
SW
SR002956: LTESBTS OperabilitySecurity
supportFeature
for 5G
5GC001082: ClassicalSW
SR002459: Common gNB software
load for LTE and
Management
SRAN
LTE790:
SR001539: Signed SW
LTE Operability Security Feature
Management
LTE790: Signed SW
LTE2099:
LTE5286: Support
CommonforSWharmonized MHA
load for LTE andfamily
SRAN
SRAN
LTE2816: High Memory Consumption Alarm for
Nokia RP1/L3
SR003007: Radio
Basic SWModules
Support for ASOE
SR002956: SBTS Operability service
support for 5G
SRAN

LTE2614: Radio Interface Based
classical
Synchronization
5GC002269: HWfor TDD Flexi
addition and Zone
removalBTSwithout
service impact on ABIO
CB005793: RRU remote
LTE5286: Common SW loadupgrade from
for LTE CPRI
and to
SRAN
eCPRI
SR002956:
SRAN SBTS Operability support for 5G
CB006706:
deploymentsAEQP AirScale MAA 64T64R 192AE
LTE5286:
n78 200W Common
SR001730: (eCPRI SW load support
TD-LTE)
Fronthaul switch for LTE onandSBTS
SRAN
SR002459:
CB007135: Common SW load for
(LTE-only configurations) LTE and
SRAN
classical
5GC002589:
SRAN 5G RF sharing with two Airscale
System
LTE5286: Modules
SR002382:
SR001534: SWSRAN Support for AirScale
FM combined Capacity
service
ABIO including
LTE2779: CPRI-Acommon ABIO and ABIN
Platform SW
SRAN
LTE1996:
5GC001246: Flexi Zone Controller
AirScale Application
Indoor Radio ASiR LTE
LTE4769: 3GPP baseline R14 March 2018
LTE2201: Flexi Zone BTS Location Lock

LTE5286: Common BTS Location
load for LTELock
and SRAN
SRAN
LTE1858: FDD Inter-band/Intra-band CA with
Two Flexi Zone
LTE5286: CommonMicro
SWBTSs
SRAN
LTE1858: FDD Inter-band/Intra-band CA with
Two Flexi Zone Micro BTSs

SR002853:
LTE1858: FDDLTEInter-band/Intra-band
and SRAN License sales items
CA with
harmonization
LTE5286:
LTE4090: Common SW load
AirScale ABIC HW for LTE and
capacity SRAN
activation
SR002459:
license Common SW load for LTE and
SRAN
LTE1858:
SR002459:FDD
CB007135: Inter-band/Intra-band
Common
Common SW
SW for
loadSRAN CA
and
for LTE and with
5G
Two Flexi
classical
SRAN Zone Micro BTSs
CB005740:
SR001033: eCPRI RU Ethernet
SBTS Limitation Multicast
Actions ToP
for License
phase Sync. Resiliency
Management
5GC002413: eCPRICapacity
LTE2417: IP Traffic FH synchronization
extension
SR001799: ToP Phase Sync Resiliency with
Ethernet Multicast
SR002774: Support of AirScale SEI port for
primary synchronization input with PTP
5GC001357: ToP Phase Resiliency with Ethernet
Multicast
SR002956:
5GC000609: SBTS Operability
ToP with Phase support
Sync for 5G
Resiliency
SR002459:
5GC000765: Common
NTP timeSW load for LTE
synchronization and
for DU &
5GC000713:
SRAN Timing over Packet (ToP) with
Classical gNB
Frequency Synchronization
LTE5286:
5GC000560: Common
eCPRI SW load
Sync for LTE
Slave RU and SRAN
SRAN
5GC000313: Timing over Packet with Phase
SR000996: SRAN Clock time management
Synchronization
SR000383: Timing over Packet with phase
synchronization
SR000374: Timing over Packet with Frequency
Sync
5GC000714: Synchronous Ethernet for gNB
SR000375: Synchronous Ethernet
SR000377: Synchronization
LTE5286: Common SW loadfrom PDH
for LTE interface
and SRAN
SRAN
LTE1891: eNode B power saving Micro DTX
LTE5425: Inter eNB LTE FDD and TDD CA
configurations with Airscale
SRAN
LTE2270:
5GC000430: FDD-TDD downlink carrier
Micro discontinuous aggregation
transmission
2CC
(µDTX) for Energy Efficiency
SR001534: SRAN FM
SRAN
LTE1891: eNode B power saving Micro DTX
SRAN
SRAN
LTE2569-F: Flexi Zone Controller Application
LTE2614: Radio Interface Based

Synchronization for TDD Flexi Zone BTS

SRAN

support
SR000929: SBTS Configuration Management

LTE2569:
LTE5286: FZC Legacy
Common SWFDD/TD-LTE15A
load for LTE andand
SRAN
FDD/TD-LTE16
SR002459: Common SWSupport
Feature load for LTE and
SRAN
LTE2645: GNSS Manual Location Entry for
Macro BTSCommon SW load for LTE and SRAN
LTE5286:
SR001534:
SR002459: SRAN
CommonFMSWcombined
load forservice
LTE and
SRAN
Nokia RP1/L3
LTE5286: RadioSW
Common Modules
SR001534: SRAN FM
SR002459: Common SW combined
load forservice
LTE and
SRAN
Nokia RP1/L3 Radio Modules
LTE1117: LTE MBMS

SR002956:
LTE5286:
support SRAN
for 5G
SR002459: CommonSW
loadfor
forLTE
LTEand
andSRAN
SRAN
SRAN
LTE2114: V-e (FSIP/FBIP, FSMr
Supporting: -Plane CE startup

classical
LTE2621:
CB005906:eNodeB
SR001534: SRAN FM
eCPRI Limitation
TDDActions
combined
based forMIMO
service
massive Licenseon
Management
ABIO/N in LTE
LTE4090:
SR003007:AirScale
Basic SWABIC HW capacity
Support for ASOE activation
license
SR002382: SW Carrier
SupportOperation
for AirScale
LTE2629:
LTE5286: Dual
Common SW load on aCapacity
Flexi Zone
ABIO
Micro including
BTS common ABIOfor LTE
and and
ABIN SRAN
SR002459:
Platform SWCommon SW load for LTE and
SRAN
SR002459: Common SW load forgeneral
LTE andflow
and
SRAN mechanism
SR001534: SRAN FM
LTE4032: AirScale combined
Capacity ABICservice
LTE2114: V-h (FSIP/FBIP, FSMr
Supporting:
5GC001163:2CPRI-A
ARM platform
supportCE in crash
gNB-DU
and SRAN
SRAN
LTE2779: CPRI-A
LTE2959: Flexi Zone Single Frequency Network

Support

Support

Support
CB007310: OneZone
LTE2959: Flexi classical gNB
Single on dual ASIL
Frequency Network
SR002338:
Support One logical SBTS with mixed
(ASIA/ASIB) dual common units operation
LTE5286:
SR002459:Common
CommonSW SWload
loadfor
forLTE
LTEand
andSRAN
SR002459:
SRAN
SR001307: Single Logical SBTS on AirScale +
FSMF
LTE2866: AirScale operation with 2 Core plugins
configurations
Support

Support

Support

Support

Support

Support

Support
LTE2959:
CB007310:Flexi
OneZone Single
classical Frequency
gNB Network
on dual ASIL
Support
SRAN
SR001307: Single Logical
LTE5286: Common SW loadSBTS on AirScale
for LTE and SRAN +
FSMF
CB007310: One classical gNB for
on LTE
dual and
ASIL
SRAN
SR002338: One logical SBTS with mixed
LTE3043: Remote
(ASIA/ASIB) Power Port
dual common Control
units for FPFD
operation
PDU
SR001534:
SR002459: SRAN
load forservice
LTE and
SRAN
LTE2866:
SR002459:AirScale
Common operation
SW loadwith 2 Core
for LTE andplugins
SR001621:
SRAN SRAN Cell Sets Allocation on Full
AirScale Module
support
LTE2483:
SR002459:Classical
CommonWCDMA/LTE RF-sharing
SW load for LTE and on
AirScale
SRAN SM Indoor
SR001534:
SR001682: SRAN FMCommon
AirScale combined service
ASIB PIU SBTS
support
LTE2483: Classical WCDMA/LTE RF-sharing on
AirScale SM Indoor
OBSAI RUs
SRAN
support
LTE2483: Classical WCDMA/LTE RF-sharing on
AirScale SM Indoor
SR001534: SRAN FM
SR002459:
SR002382: Common SWfor
SW Support load for LTE
AirScale and
Capacity
SRAN
SR001682:
Platform SWAirScale Common ASIB PIU SBTS
support
SR002459:
SR002382: Common
SW SWfor
Support load for LTE
AirScale and
Capacity
SR003007:
SRAN Basic SW Support for ASOE
ABIO including
CB007310: One common
classicalABIO and
gNB ASIB ABIN
on dual ASIL
SR001682:
Platform SWAirScale Common PIU SBTS
SR002382:
support SW
CB007135:Common Support
CommonSW for
SWload AirScale
for SRAN Capacity
and
LTE5286:
ABIO including common ABIOfor LTE
and and5G
ABIN SRAN
classical
Platform
CB007310: SWOne classical gNB on dual ASIL
SRAN
5GC001028:
SR001682: Backplane
AirScale Interfaces
Common ASIB for
PIUSubrack
SBTS
SR002459:
Sharing Common SW load for LTE and
support
SRAN
LTE5286:
SR001682:Common
AirScaleSW load for
Common LTEPIU
ASIB andSBTS
SRAN
LTE3656:
support MDEA Fronthaul Switch Outdoor DC
LTE2294: FDD TDD Coexistence within one eNB
implementation
SR002459: Commonfor SBTS17
SW load for LTE and
SRAN
LTE2866: AirScale operation with 2 Core plugins

SRAN
LTE3265: GPS outage handling for OTDOA
CB005850: NR-LTE concurrent operation with

SR001536: BTS InfoModel
LTE5286: Common SW loadAdapter
for LTE(IMP)
and SRAN
SRAN
LTE3340: SWM Harmonization
SR001534: SRAN FM
SRAN
LTE1530: Reduced LTE Guard support
Band for 5G
LTE652: Intelligent
SR001534: SRAN FM Flexi BTS Shutdown
combined service
SRAN
LTE1858:
SR001682:FDD Inter-band/Intra-band
AirScale Common ASIB PIU CA SBTS
with
Two Flexi
support Zone Micro BTSs
SR000924: SBTS Intelligent shutdown

LTE5286:
LTE5020: Common
LTE/CDMA1X SW load for LTE with
RF Sharing and SRAN
SR002459:
URCB/URCC Common SW load for LTE and
SRAN
LTE3022:
SR002459: Inter-site carrier aggregation
support and5G
SRAN
5GC000765: NTP time synchronization for DU &
LTE3480: Loose Phase and Time Sync
Classical gNB
SR001547: Loose Phase
LTE5286: Common andfor
SW load Time
LTE and SRAN
Synchronization
SRAN
LTE3480: Loose Phase and Time Sync
SR001547: Loose Phase and Time
Synchronization
SR001534: SRAN FM
SRAN
LTE3086: Legacy ALD management protocol for
CPRI-A
SR001987: SBTS support for Antenna path delay
measurement for CPRI-A radios
SRAN
LTE2372:
SR003007:IPv6 Support
Basic with Cloud
SW Support Flexi Zone
for ASOE
Controller
SRAN
SR002216: Load based Power Saving for
AirScale
SR002956:SMSBTS
for LTE for Energy
Operability Efficiency
support for 5G
SRAN
SR002956:
5GC001702: NR-LTE/SRAN
LTE5286: Common SW load concurrent
for LTE and SRAN
operation with OBSAI
SR002459: Common SW RUsload for LTE and
SRAN
LTE2860: Licensed-Assisted Access
SR001658: LTE 18 new feature implementation
for SRAN
LTE3259: Cloud Flexi Zone Controller LTE

feature
LTE5286:parity
SR003007:Common
Basic SWSW load forforLTE
Support and SRAN
ASOE
SR002459:
CB007135: Common SW for SRAN andand
Common SW load for LTE 5G
SRAN
classical
LTE2294:
CB007310:FDD OneTDD Coexistence
classical gNB on within one eNB
dual ASIL
LTE80: GPS Synchronisation
5GC000952: Recovery for Classical gNB
5GC000316: 5G Node B Synchronization Mode
Support
SRAN
LTE3554:
CB007160:FHS support
ITSAR of 0-23km
compliant fiber length for
hardening
CPRI-A radios in FDD LTE
SR001539:
SR002956: LTESBTSOperability
OperabilitySecurity
supportFeature
for 5G
5GC001048: gNB default password alarm
LTE2647:
SR002174:BTS BTSLINUX
DirectSystem Account
Integration support for
Permissions
Data Collection Control
LTE4926: BTS Direct Integration Support for
Data Collection Control
LTE3455: BTS Default password alarm
SR001543: BTS Default password alarm

SRAN

SRAN

SRAN
LTE5265: Inter-eNB Flexible UL CoMP support

with ASIB&ASIBA
SR002459: CommonSW
loadfor
forLTE
LTEand
andSRAN
SRAN
SRAN
SR002399: Support of flexible LTE UL CoMP in
SRAN
LTE3933: Flexible inter eNB UL CoMP
with ASIB&ASIBA
SRAN
with ASIB&ASIBA
SRAN
LTE3933:
SR002459:Flexible
Common inter
SW eNB ULfor
load CoMP
LTE and
SRAN
SRAN
LTE3933: Flexible inter eNB UL CoMP
LTE4565: Public IP on Logical Interface for cFZC

CB006942: BTS (Q)SFP+/SFP28 provisioning
SR001548:
enhancements SBTS support for new Radio Module
Introduction
SR002433: CPRI link monitoring
5GC000375: 5G Performance Monitoring for
CPRI Link
LTE3320: CPRI link monitoring

SR002459:
and5G
SRAN
SRAN
5GC001246: AirScale Indoor Radio ASiR LTE
CB005850:
SR002459: NR-LTE
Commonconcurrent operation
SW load for LTE andwith
shared
SRAN FHS for OBSAI
Management
LTE1854: -h (System Upgrade to RL70-
LTE882a1: System Upgrade with Backward
Compatibility FDD conversion

LTE4788: ETSI and IC DFS Support for LAA
SRAN
classical
LTE4788: ETSI and IC DFS Support for LAA
LTE4955: AirScale Capacity cards mixed within

LTE4875:
one eNB LAA Dynamic Power Control
LTE4788:
LTE5286: ETSI and SW
Common IC DFS
loadSupport
for LTE for
andLAA
SRAN
SRAN
SBTS running
CB007135: on AirScale
classical
eCPRI
LTE5286: Common support
SW load for for 5G
LTE and SRAN
SRAN
SBTS running on AirScale

SRAN
SRAN
LTE3084: Remote FPFH PDU control via
AirScale SM

5GC000534: Digital Beamforming
CB007135: Common SW for SRANforand
eCPRI
5G
based RUs
classical
based RUs
SRAN
LTE4560:
SR002956:RX Power
SBTS and traffic
Operability based for
support Sleeping
5G
LTE cell detection
SRAN
LTE4560: RX Power and traffic based Sleeping
LTE cell detection
SRAN
LTE4560: RX Power and traffic based Sleeping
LTE cell detection

SR002459: Common
CB005906: eCPRI SW load
based TDD for LTE and
massive MIMO on
SRAN
ABIO/N
CB006114: IPsec forSW
LTE5286: Common eCPRI
loadMforplane
LTE and SRAN
SR002951:
SR002459: Basic
CommonSWSW support
load for
for AGIML
LTE andAI/ML
PoC
SRAN HW
LTE5286:
Platform SW Common SW load for LTE and SRAN
SR002459:
and5G
SRAN
5GC001476: DU ABIL configs: legacy FDD CPRI
Radios (II)
SR002696: FHS & AFAA CPRI m-plane link
protection
SR003007: Basic SW
CB005906: eCPRI Support
based TDD for ASOEMIMO on
massive
SR002216:
ABIO/N Load based Power Saving for
CB007135:
AirScale SMCommon
for LTE SWEnergy
for for SRAN and 5G
Efficiency
SR003007:
classical Basic SW Support for ASOE
SR002382:
5GC001866:SW Support
Delivery for AirScale
of beam Capacityto
set realization
ABIO
gNB including common ABIO and ABIN
Platform
LTE4032:
5GC000534: AirScale
DigitalCapacity ABIC for eCPRI
Beamforming
based RUs
5GC000918: Analog Beamforming for eCPRI
based RUs
SR002269: Continuous update of BTS passive

partition - replaced by CB007335
SR002546:
ABIO includingDynamic
commonSpectrum Sharing
ABIO and ABIN
WCDMA+LTE,
Platform SW phase 2
SR002167:
SR002546: Dynamic
Dynamic Spectrum
Spectrum Sharing
Sharing
WCDMA+LTE
WCDMA+LTE, phase 2
WCDMA+LTE
GSM+LTE
SR002270: KPI triggered alarm and log collection
in BTS

in BTS

in BTS

in BTS

in BTS

in BTS

in BTS

in BTS

in BTS

in BTS

in BTS

in BTS

in BTS
in BTS

in BTS

in BTS

in BTS

in BTS

in BTS
SR002270:
CB007422: 5G KPIBTS
triggered alarm and
Supervision log collection
harmonization -
in BTS
Part II (signature for crash/failure)
SR001825: Fault signature on autonomous BTS
resets and crashes/failures
LTE3981:
CB007422:Fault signature
5G BTS on autonomous
Supervision BTS -
harmonization
SR001825: Fault signature on autonomous BTS
LTE3981: Fault signature on autonomous BTS
LTE5399: AZQC work as B42 and B43 RRH for

Canada Xplornet
CB007422: 5G BTS Supervision harmonization -
SR002580: One click BTS integration to NetAct
LTE3981: Fault signature on autonomous BTS

SR002596: Flexible use of shared spectrum with
GL DSS

URCB/URCC
classical
5GC001991: Antenna tilt for 2D GoB
SR002362: S1 and TX Power based sleeping

LTE cell detection

LTE cell detection

LTE cell detection
classical
5GC002491: NR ABIO BB cell sets up to 12 FDD
cells

LTE4537: Inter-site CA extensions

classical
eCPRI
5GC001698: DU (ABIL+RU) remote upgrade
from CPRI to eCPRI
5GC001866: Delivery of beam set realization to

gNB
SR002236: Web Element Manager

improvements - part 2
in BTS
LTE5635: NB-IoT Guardband Coexistence with

NR
classical
5GC001104: PM to O-RAN O1
5GC000760: gNB registration into O-RAN O1

classical

classical

classical

classical

classical

classical

SR000538: BTS Time Synchronization
CB006028: Independent software upgrade for

shared RU
CB006028: Independent software upgrade for
shared RU
CB005809: Continuous BTS product security

improvements Part 6
CB005809: Continuous BTS product security
improvements PartSW
SR003007: Basic 6 Support for ASOE
LTE2647: BTS LINUX System Account
CB006942: BTS (Q)SFP+/SFP28 provisioning
Permissions
enhancements
SR002109: BTS Fronthaul QSFP+/QSFP28
Base Line Basic SW Support for ASOE
SR003007:
SR002092: BTS (Q)SFP+/SFP28
CB006942: BTS Fronthaul SFP+/SFP28 Base
provisioning
Line
enhancements
SR002109: BTS (Q)SFP+/SFP28
CB006942: BTS Fronthaul QSFP+/QSFP28
provisioning
Base Line
enhancements
SR002092:
SR002109: BTS
BTS Fronthaul
Fronthaul SFP+/SFP28
QSFP+/QSFP28 Base
Line
Base Line
SR002092: BTS Fronthaul SFP+/SFP28 Base
Line
SR001936: Small Form Factor Pluggable
SFP/SFP+/SFP28 slot


CB005906:
CB006135: eCPRI
Docomobased
ORANTDD massive
Profile L1 MIMO on
ABIO/N
implementation Step 2 (FD Beamforming)
classical
CB006064: Long PUCCH for FR1 TDD cells
5GC002357: Renewal of vDU L1 SW: PUSCH
SR000860: Assisted Partial Timing Support for

ToP

ABIO/N
CB006114: IPsec for eCPRI M plane

eCPRI
SRAN
LTE2562: ANR InterRat 1xRTT O&M assisted
SR001534: SRAN FM
SRAN
SR001534: SRAN FM
SRAN
LTE1834: LTE MBMS Service Continuity


LTE3949:
SR002459:eCPRI/LLS
Common SWbased
loadTDD massive
for LTE and MIMO
SRAN
LTE5141: TDD massive MIMO calibration
enhancement
SRAN
LTE2023:
LTE5286: User plane
Common SWoverload
load forhandling
LTE and SRAN
SR001534:
SRAN
LTE430: DL power boosting for control channels
SR001534: SRAN FM
SRAN
SR001534: SRAN FM
SRAN
SR001534: SRAN FM
SRAN
LTE2023: User plane overload handling
SR001534: SRAN FM
SRAN
LTE2023: User plane overload handling

SRAN

SRAN
LTE5726: Remote interference avoidance with
sequence support on 15MHz
LTE5286:
LTE5602: Common
TDD Remote SW Interference
load for LTE avoidance
and SRAN
SR002459: Common SW
based on downhill trend load for LTE and
SRAN
LTE5726: Remote interference avoidance with
sequence support on 15MHz
SRAN
LTE5407: LTE-NR Dynamic Spectrum Sharing

phase I

phase I

phase I
phase I

phase I

phase I

phase I

NR
LTE4750: LTE-NR DSS with CRS Rate Matching

LTE5286:
NR Common SW load for LTE and SRAN
SR002459: Common
LTE4750: LTE-NR DSSSWwith
load for LTE
CRS Rateand
Matching
SRAN
SR001988: LTE-NR Dual Connectivity Option 3X
in SBTS
LTE4750: LTE-NR
LTE1771: Dual DSS IP
U-plane with CRS Rate Matching
addresses
LTE505:
LTE5286:LTE505
Common Transport
SW loadSeparation
for LTE andforSRAN
RAN
sharing
LTE1:
SRAN S1/X2 data path management
SR001534: SRAN
service
LTE505:
LTE5286:LTE505
Common Transport
SW loadSeparation forSRAN
for LTE and RAN
sharing
LTE3:
SRAN S1, X2 and RRC common signaling
SR001534: SRAN
service
LTE505:
LTE5286:LTE505
Common Transport
for LTE and RAN
sharing
LTE3:
SR001534: SRAN
service
LTE505: LTE505 Transport Separation for RAN
sharing
LTE3: S1, X2 and RRC common signaling
SRAN
LTE1117:
SR002382:LTE SWMBMS
SR001534:
ABIO
LTE5286: SRAN
including
Common FMSWcombined
common ABIOfor
load andservice
LTE ABIN
and SRAN
Platform
SR002459:SWCommon SW load for LTE and
LTE4898:
SRAN NB-IoT: Multiple non-anchor carriers
LTE5286:
SR002546: Common
Dynamic SW load forSharing
LTE and SRAN
LTE1117:
SR002459: LTE MBMSSpectrum
WCDMA+LTE,
SR001534: phase
SRAN FM 2combined service
SRAN
LTE1996:
WCDMA+LTE Flexi Zone Controller Application
LTE145part1:
LTE5286: CommonRadioSW Network Configuration
load for LTE and SRAN via
RROM
SR001534:
LTE4996:
SRAN SRAN
BTS FMIntegration
Direct combined service
for Trace
LTE1996: Flexi Zone Controller LTE and
Application
SRAN
LTE145part1: RadioSW Network Configuration via
LTE5286:
SR002215: Common
BTS Direct load for
IntegrationLTE forand SRAN
Trace
RROM
SR002459: CommonSW SWload
loadfor
forLTE
LTEandandSRAN
LTE5286:
SR001534: Common
SRAN FM combined service
SRAN
LTE1996: Flexi Zone
SRAN16.2/16.10 Controller Application
features
LTE145part1: Radio Network
LTE1996: Flexi Zone Controller Configuration
Application via
RROM
LTE163: Subscriber and Equipment Trace
SR001534: SRANCell
LTE433-b: Basic FMTrace
combined service
adaptations
LTE163b: Subscriber and Equipment Trace
(vendor specific extensions)
LTE5286:
LTE690: Common
LTE SWTrace
Interface load for LTE and SRAN
Support
LTE5286:
SR002459: Common
Common SWSWload
loadfor LTE
for LTEandandSRAN
LTE690-b:
SR002459: LTE Interface
Common SW Trace
load Support
for LTE and
SRAN
SRAN
LTE1996: Flexi Zone
SRAN16.2/16.10 Controller Application
features
LTE654c: Configuration of Vendor
LTE1996: Flexi Zone Controller Specific
Application
Parameters
LTE644: Configurable cell trace content
LTE433-b: Basic Cell Trace adaptations
LTE163b: Subscriber and Equipment Trace
(vendor
LTE5286:specific
Common extensions)
LTE163:
SR002459: Commonand
Subscriber SWEquipment
load for LTE Trace
and
SRAN
LTE3071: NB-IoT Inband
LTE1996:
LTE5286: Flexi
CommonZoneSW
Controller
load forApplication
LTE and SRAN
LTE450:
SR002459: Common SW loadchange
MME capacity value for LTE and
SRAN
LTE782: ANR Fully UE based
SR001534: SRAN FM
SRAN
LTE908: ANR Inter-RAT UTRAN Fully UE Based
SR001534: SRAN FM
SRAN
SR001534: SRAN FM
SRAN
LTE5411: ANR for EN-DC
SRAN
SR003007:Common
LTE5286: Basic SWSWSupport
load forforLTE
ASOE
and SRAN
SR001534:
SR002459: SRAN
SR001612: LTE-FDD
Common FMSWcombined
and forservice
LTE-TDD
load eNB
LTE andin
SBTS
SRAN running on AirScale
SR002459: Common
50160: TCP/IP SW load for LTE and
measurement
SRAN
LTE5286:
LTE5286: Common
Common load
load for
SWcombinedfor LTE
LTE and
and SRAN
SRAN
SR001534:
SR002459: SRAN
Common FMSW load for service
LTE and
LTE2554: Network Assisted Interference
SRAN
Cancellation and Suppression
LTE1996:
LTE2007: Flexi ZoneCarrier
Inter eNB Controller Application
Aggregation
LTE: 685-C (Neighbor Relation
LTE2208: eICIC extensions-micro Robustness
SR001534:
SR001534: SRAN
SRAN FMFM combined
combined service
service
LTE1496: eICIC micro
LTE1117: LTE MBMS
LTE2209:
LTE5286: eICIC
Common enhancements
LTE1113: eICIC
SR002459: Common macro
SW load for LTE and
SRAN
LTE2062:
SR002459:IRAT UTRAN
Common SWNeighbor Relation
load for LTE and
Robustness
SRAN
SR001534: SRAN
LTE2305: Inter FM combined
eNodeB service
Carrier Aggregation for 2
macro eNodeBs
LTE1858:
Common SW load for LTECA with
and
Two
SRANFlexi Zone Micro BTSs
SR001534: SRAN
eNodeB service
macro eNodeBs
LTE1858:
Common SW load for LTECA with
and
Two
SRANFlexi Zone Micro BTSs
SR001534: SRAN
eNodeB service
macro eNodeBs
LTE1858:
LTE5286: FDD Inter-band/Intra-band
Common CA with
SR001534:
LTE2029:
LTE5286: Extend
Common amount
SW loadof neighboring
for LTE andcells
SRAN
with overload control in eNB
SRAN
LTE2029: Extend amount of neighboring cells
with overload
LTE5286: controlSW
Common in eNB
SRAN
LTE2007: Inter eNB Carrier Aggregation
SR001534: SRAN FM
SRAN
SR001534: SRAN FM
SRAN
SRAN
LTE2060: Add new frequency or cell without
reset
SR001534:
SR002459: SRAN
CommonFMSWcombined
load forservice
LTE and
SRAN
LTE2060: Add new frequency or cell without
reset
SR001534: SRAN FM
SRAN
LTE1130: Dynamic PUCCH allocation
SR001534: SRAN FM
SRAN
LTE1130: Dynamic PUCCH allocation
LTE2370: Flexi Zone Inter-FZAP Carrier

Aggregation
SRAN
LTE1858:
LTE5286: FDD Inter-band/Intra-band
Common CA with
SRAN
LTE2612: ProSe Direct Communications for
Public Safety
SR001534: SRAN FM
SRAN
LTE2562:
LTE5286: ANR InterRat
Common 1xRTT
SW load forO&M assisted
LTE and SRAN
SRAN
LTE1996:
SR002459:Flexi Zone Controller
Common SW load forApplication
LTE and
LTE3:
SR001534: SRAN
service
LTE505:
LTE5286:LTE505
Common Transport
for LTE and RAN
sharing
LTE3:
SR001534: SRAN
service
LTE505:
LTE5286:LTE505
Common Transport
for LTE and RAN
sharing
LTE3:
SR001534: SRAN
service
LTE505: LTE505 Transport Separation for RAN
sharing
LTE3: S1, Common
LTE5286: X2 and RRC
SW common signaling
SRAN
LTE915: S1 eNB Configuration Update
SRAN
LTE1196:
LTE5286: RIM for WCDMA
LTE498: RAN
SR002459: Information
Common Management
SW load for LTE andfor GSM
SR001534:
LTE1196: RIM for WCDMA
LTE498: RAN Information Management for GSM
LTE2130: Flexi Zone Controller Appllication

Supports 100 AP Configuration
LTE2130: Flexi Zone Controller Appllication

Supports 100 AP Configuration

SR002459: CommonSW
loadfor
forLTE
LTEand
andSRAN
SRAN
SRAN
SR001988: LTE-NR Dual Connectivity Option 3X
CB007135:
in Common SW for SRAN and 5G
SBTS Common
LTE5286:
classical SW load for LTE and SRAN
LTE4087:
SR002459: X2 interfaceSW
Common with NRfor
load gNB and
5GC001866: Delivery of beam set LTE
realization to
SRAN
gNB
LTE1996: Flexi
5GC000829: Zone
One Controller
classical gNB Application
on dual ASIK
LTE550:
SR002382: Radio
SW parameter
Support online
for
LTE5286: Common SW load for LTE changeable
AirScale Capacity
and SRAN
SR001534:
ABIO SRAN
including FM
common combined
ABIO service
and
SR002459: Common SW load for LTE and ABIN
Platform
SRAN SW
SR002956:
AirScale Commonsupport
ASIB PIUfor SBTS
5G
5GC000918:
support Analog Beamforming for eCPRI
based RUsNB-IoT
LTE4063:
SRAN
based RUs
LTE5286: Common SW
LTE5286: Common SW load for LTE
load for LTE and
and SRAN
SRAN
5GC000533: Digital Beamforming for CPRI
based RUs
Synchronization
LTE5286:
LTE5286: Common
Common SW
SW load
load for
for LTE
LTE and
and SRAN
SRAN
SR002459:
SRAN
SRAN
SR002012: Automatic Access Class Barring
Alarms, Counters and Status Enhancement
LTE4487: Automatic Access Class Barring
Alarms, Counters and Status Enhancement
SRAN
LTE3561: Cat-M1
LTE5286:
SR003025:Common
Inter eNBSWRUload for LTE
sharing withand SRAN
CPRI
SR002459:
interface on Common
ABIO SW load for LTE and
SRAN
5GC001524: NR-LTE concurrent operation for
LTE4741: Access Class Barring Support for Cat-
eCPRI radios
CB007156:
SR002956: ITSAR
M1 & SCAS compliant
SBTS Operability support foruser
5Gevent
records
SR003007:
operation forBasic
AEHC SW Support
eCPRI for ASOE
radio
5GC001702: NR-LTE/SRAN concurrentsupport for 5G
LTE5286:
operation Common
with OBSAI SW load for
RUs to 5G SALTE and SRAN
LTE4572:
SR002459: Idle mode mobility
5GC000726: NR-LTE FDD concurrent operation
SRAN
for CPRI RUs
SR001486:
SR002459: Support
Commonfor SWalready delivered
load for LTE and
SRAN16.2/16.10
SRAN features
CB007156:
LTE1996: ITSAR
Flexi Zone& SCAS compliant user event
Controller
SR002576:
records SBTS-5G concurrentApplication
operation with
OBSAI RUs
LTE5286:
SR002459:Common
CommonSW SWload
loadfor
forLTE
LTEandandSRAN
LTE4461:
SRAN NR-LTE FDD concurrent operation for
CPRI RUs
support

SRAN
SR001534: SRAN FM
SRAN
SR001534: SRAN FM
SRAN
LTE1996:
LTE5286: Flexi
CommonZoneSW
Controller
load forApplication
LTE and SRAN
SR001534:
SRAN
LTE1996:
LTE5286: Flexi
CommonZoneSW
Controller
load forApplication
LTE and SRAN
SR001534:
SRAN
LTE1996:
LTE5286: Flexi
CommonZoneSW
Controller
load forApplication
LTE and SRAN
SR001534:
SRAN
LTE1996:
LTE5286: Flexi
CommonZoneSW
Controller
load forApplication
LTE and SRAN
SR001534:
SRAN
ABIA
SRAN

ARAN1163: Iu-PS Throughput Measurement for
GTP Traffic

LTE2424: LTE-U 2CC Support for Dual-Band
Indoor/Outdoor FZ BTS(Pre-Re 13)

Indoor/Outdoor
LTE5286: CommonFZ BTS(Pre-Re
SW load for 13)
LTE and SRAN
SRAN

Indoor/Outdoor FZ BTS(Pre-Re 13)
LTE2464: Synchronization with Network Time

Protocol
LTE2464: Synchronization with Network Time

Protocol

SRAN


SRAN
CB005884: FZM and DP: CBRS Support for

Secondary Domain Proxy

LTE3974: Airscale CBRS
LTE3677-C: Dynamic Channel Selection (DCS)
LTE3677-C: Dynamic Channel Selection (DCS)
LTE3677-C: Dynamic
LTE5286: Common SWChannel
load forSelection
LTE and(DCS)
SRAN
SRAN
LTE1117: LTE MBMS
SRAN
LTE1117:
SR002459:LTE MBMSSW load for LTE and
Common
SR001534:
LTE1117: LTE MBMS
LTE3199: Support for multiple MBSFN and
Synchronization Areas
SR001534: SRAN FM
SRAN
LTE1117:
SR002459:LTE MBMSSW load for LTE and
Common
SR001534:
LTE1117: LTE MBMS
Synchronization
LTE5286: Common Areas
SR001534: SRAN
load forservice
LTE and
SRAN
Synchronization
SR001534: SRAN
load forservice
LTE and
SRAN
Synchronization
SR001534: SRAN
load forservice
LTE and
SRAN
LTE3552: eMBMS capacity enhance. & support
for overlapping of MBSFN Areas

SRAN

SRAN
ABIA
SRAN

SRAN

SRAN
SR003007:
SR002459: Basic
Common SWSW Support ASOE
load for LTE and
CB007422:
SRAN 5G BTS Supervision harmonization -
LTE5286:
LTE5286: Common
Common SW SW load
load for
for LTE
LTE and
and SRAN
SRAN
SR002459:
SRAN
SRAN
SR003007:
5GC001082:Basic SW Support
Classical for ASOE
gNB software
CB006942:
Management BTS (Q)SFP+/SFP28 provisioning
enhancements
SR002109: BTS Fronthaul QSFP+/QSFP28
Base Line
CB005906:
SR002092: eCPRI based TDD
BTS Fronthaul massive MIMO
SFP+/SFP28 Base on
ABIO/N
Line
SR003007: BBP
SR002079: Basicbasic
SW Support
SW for ASOE
SR002382:
CB006942: BTSSW Support forsupport
(Q)SFP+/SFP28 AirScaleforCapacity
ASIL HW
provisioning
enhancements
Platform
SR002092: SWBTS Fronthaul SFP+/SFP28 Base
SR001971:
Line SFP power level compatibility
verification
Platform SW
SR001971: SFP power level compatibility
verification

ABIO/N
SR003271: AirScale Liquid Cooling basic SW
support
SRAN
SRAN
LTE5286:
CB007135:Common
CommonSW SWload for LTEand
for SRAN and5GSRAN
SR002459:
SRAN
LTE4032:
SR002956:AirScale Capacity ABIC
5GC000900: Concurrent
CB007135: Common SWSA
for and
SRANNSAandoperation
5G
5GC000534:
classical Digital Beamforming for eCPRI
based RUs SBTS Operability support for 5G
SR002956:
5GC000718:
5GC000900: F1 cell management
Concurrent SA and NSA operation
based RUs
5GC000718: F1 cell management
5GC000900: Concurrent SA and NSA operation
5GC000742: System Information Broadcast -
intra-NR
5GC001008: Signaling-based NG RAN Slicing

with 5GC
5GC000496: Classical BTS introduction
5GC000474: X2 Management for NSA mode 3x
operation

5GC000481: F1 link management

5GC000309: Support of F1 interface over IPv4 or
IPv6
CB006558: Dual Stack IPv4/IPv6 for NG /Xn
interfaces in 5G-SA deployment
5GC000681: Dual Stack IPv4/IPv6 for NG /Xn
interfaces
CB006558:inDual
SA deployment
Stack IPv4/IPv6 for NG /Xn
interfaces
CB006558:inDual
SA deployment
interfaces
CB006558:inDual
SA deployment
interfaces
SR002672:inTRSSA deployment
Support for 5G NSA interfaces
(X2 and S1-U) over IPv4 / IPv6
5GC000577: TRS Support of NSA interfaces (X2
and S1-U) over IPv4 / IPv6

5GC000637: Xn management for SA Option 2
5GC000638: NG management




5GC000740: NG-C Flex (SA mode)
with 5GC


5GC000474: X2 Management for NSA mode 3x
operation





classical
CB005956: Enhanced X2 Link Supervision
classical



IPv6
IPv6
based RUs Common SW for SRAN and 5G
CB007135:
5GC000718:
classical F1 cell management
5GC001904: LTE-NR In-Carrier Dynamic
Spectrum Sharing Phase I

5GC001904: LTE-NR SW
CB007135: Common In-Carrier Dynamic
for SRAN and 5G
Spectrum
classical Sharing Phase I



classical
5GC000829:
5GC001745: One classical
NR-LTE DSS:gNB on Peak
NR DL dual ASIK
Rate
Increase
classical
SR002956:
SR002956: SBTS
SBTS Operability
Operability support
support for
for 5G
5G
5GC000746: CMAS (Commercial Mobile Alert
Spectrum
System) Sharing Phase I
5GC000742: System Information Broadcast -
intra-NR
5GC000533: Digital Beamforming for CPRI
based RUs

5GC001586: LTE-NR CRS Rate Matching DSS
for FDD EN-DC PSCell








5GC001008:
Cell Trace for NSA
with 5GC
5GC001778: Enhanced Cell trace
5GC001804: Basic PCMD user plane
5GC000376: PCMD Support for 5G NB
5GC001097: Basic PCMD For NSA

5GC002177: A2 based SgNB release

SFP+ CWDM
SR000371: 1000Base-BX Optical GE Interface
SR000365: Electrical 100/1000-Base-T Interface
LTE1864: 1000Base-ZX Optical GE Interface
5GC001179: BTS Fronthaul CPRI 7 -
QSFP+/QSFP28 Base Line
SR000370: 1000Base-ZX Optical GE Interface
LTE1314: Small Form Factor Plugable Slot (SFP
slot)
LTE1313: Electrical 100/1000-Base-T Interface
LTE1865:
SR002956:1000Base-BX
SBTS OperabilityOptical GE Interface
support for 5G
LTE1863: 1000Base-LX Optical GE Interface
LTE1312:
CB007135:Ethernet
Common Termination
SW for SRAN and 5G
5GC000385: 1000Base-SX Optical GE Interface
classical
CB007156: ITSAR
5GC000849: & SCAS compliant
BTSFronthaul
Fronthaul CPRI 7 - 10GEuser event
SR002092: BTS SFP+/SFP28 Base
records
SFP+ Single Fiber
Line
SR000368:
5GC000625:1000Base-SX
classical 10/25GBase-LR Optical GE GE
Optical Interface
LTE1315:
5GC000986:
Interface 1000Base-SX
Fast IP Optical
Rerouting GE Interface
5GC000851:
SR000361: Link
5GC000388: BTSSupervision
FronthaulOptical
1000Base-BX CPRI 7GE
with BFD - 10/25GE
Interface
SFP28
LTE592:Single
5GC000387: Fiber Forwarding
Bidirectional
1000Base-ZX OpticalDetection
GE Interface
SR002025:
5GC000386:Backplane
1000Base-LXInterfaces
OpticalforGESubrack
Interface
Sharing
5GC000381: Small Form Factor Pluggable
SR000350: Ethernet
SFP/SFP+/SFP28 Termination
slot
SR001534:
5GC000624:SRAN FM combined
10/25GBase-SR service
Optical
5GC000380:
SR000357: 10GBase-SR
Symmetrical E1 Optical GEGE
Interface Interface
Interface
5GC000847: BTS Fronthaul CPRI 7 - 10GE
5GC000848:
SFP+ Dual FiberBTSBase
Fronthaul
Line CPRI 7 -
SFP+/SFP28 Dual
5GC000382: 10GBase-LRFiber Base LineGE Interface
Optical
SR000369:
5GC000850: BTS Fronthaul CPRIGE
1000Base-LX Optical 7 - Interface
10GE
SR000357:
SFP+ CWDM Symmetrical E1 Interface
5GC001179: BTS Fronthaul
CB007135: Common SW forCPRISRAN7 and- 5G
QSFP+/QSFP28
classical Base Line
5GC000385:
SR000356: IPsec1000Base-SX
for BTS Optical GE Interface
5GC000849:
5GC000264: BTS IPsecFronthaul
on BackhaulCPRI 7 - 10GE
SFP+ Single Fiber
5GC000851: BTS Fronthaul CPRI 7 - 10/25GE
SFP28 Single Fiber
SR001534:
5GC000624:SRAN FM combined
10/25GBase-SR service
Optical GE
SR000357:
Interface Symmetrical E1 Interface
LTE3030: Revocation List Download with HTTP
5GC000848: BTS Fronthaul
SR001344: Revocation CPRI 7 - with HTTP
list download
SFP+/SFP28 Dual Fiber Base
5GC000952: Recovery for Classical Line gNB
SR000367: Small Form Factor
LTE3440: LTE Operability Security Plugable
FeatureSlot
(SFP slot)
5GC000323: Operator Certificate Management &
Multi Layer of CA
SR000845: SBTS Operator
LTE4146: AirScale CommonCertificate
ASIB PIU SBTS
Management
support
support
SR000358: EthernetCommon
LTE4146: AirScale OAM ASIB PIU SBTS
LTE140:
support Ethernet OAM
support
LTE140:
SR001682:
classical AirScale Common ASIB PIU SBTS
support
5GC000994: IP Transport Network
SR000358:
Measurements Ethernet OAM
LTE140:
SR001534: SRAN OAM
Ethernet FM combined service
SR000360: IP Transport Network Measurements
LTE574: Transport network measurement
SR000367: Small Form Factor Plugable Slot
(SFP slot)
SR000357: Symmetrical E1 Interface



SR000176: MLPPP termination
LTE4146: AirScale Common ASIB PIU SBTS

SR000176:
support MLPPP termination
support
LTE140:
SR001682:
classical AirScale Common ASIB PIU SBTS
support
5GC000952: Recovery forfor
Classical gNB5G
CB007135: Common
SR000358: Ethernet SW
OAM SRAN and
LTE3440:
classical LTE Operability Security Feature
LTE140:
Parity Ethernet
with Single OAM
OAM
5GC000325: Nokia Service Account
5GC000323:
Management Operator
on gNB Certificate Management &
Multi LayerLTE
LTE3440: of CA
Operability Security Feature
SR000845: SBTS OAM
Parity with Single Operator Certificate
Management
LTE2646: Continuous BTS product security
improvements Part 3
SR001063: Continuous BTS product security
improvements Part 3 SW for SRAN and 5G
CB007135: Common
classical
5GC000986: Fast IP Rerouting
SR000361: Link Supervision with BFD
LTE592:
CB007135: Bidirectional
Common SW Forwarding
for SRANDetection
and 5G
classical
5GC000986: Fast IP Rerouting
SR000361: Link Supervision with BFD
LTE592: Bidirectional Forwarding Detection
classical
5GC002375: Selectable
CB007135: Common SWPhysical Port
for SRAN for5G
and debug
tracing
classical
SR001534: SRAN FM
CB006886: TWAMP combined
metrics and service
capacity
SR000365: Electrical 100/1000-Base-T Interface
enhancements
LTE1313:
5GC000994:Electrical 100/1000-Base-T
IP Transport Network Interface
Measurements
SR001534: SRAN FMSW
CB007135: Common combined
for SRANservice
and 5G
SR000360:
classical IP Transport Network Measurements
LTE574:
5GC000994:Transport networkNetwork
IP Transport measurement
Measurements
classical
SR001534:
SR000958: SRAN
SupportFMforcombined
distributedservice
PKI systems
SR000360:
LTE3440: LTE OperabilityNetwork
IP Transport SecurityMeasurements
Feature
LTE574:
Parity Transport
with Single network measurement
OAM
5GC000323:
classical Operator Certificate Management &
Multi Layer of CA
SR000845: SBTS OperatorSecurity
LTE3440: LTE Operability Certificate
Feature
Management
5GC000323: Operator Certificate Management &
Multi Layer of CA
SR000845: SBTS Operator Certificate
Management

classical
5GC000714: Synchronous Ethernet for gNB
SR000375: Synchronous Ethernet
classical
5GC000714: Synchronous
CB005740: eCPRI Ethernet
RU Ethernet for gNB
Multicast ToP
SR000375:
phase Sync.Synchronous
Resiliency Ethernet
SR001799: ToP Phase Sync Resiliency with
Ethernet Multicast
SR002774:
LTE3440: LTE Support of AirScale
Operability SEIFeature
Security port for
primary synchronization
Parity with Single OAM input with PTP
5GC001357: ToP Phase Resiliency with Ethernet
Multicast
5GC000713: Timing over Packet (ToP) with
LTE3440:
FrequencyLTE Operability Security Feature
Synchronization
Parity
5GC000609: ToP OAM
with Single with Phase Sync Resiliency
Synchronization
LTE1996:
CB007135:Flexi Zone Controller
Common SW for SRANApplication
and 5G
SR000384:
classical Timing over Packet Resilience
SR000589: IPv4/IPv6 Transport Stack
LTE1869: IPv4/IPv6 Transport Stack
5GC000307: Transport IPV4/IPv6 stack
enhancement
SR000439: IPSec Emergency Bypass
LTE3440: LTE Operability Security Feature
LTE1390: IPSec Emergency Bypass
classical
5GC002573: Local and
CB007135: Common SW Remote
for SRANIP traffic
and 5G
capturing
classical
SR000465:
LTERLCR-27036:Local and
two Remote IP Traffic from
alarms descoped
Capturing
LTE4500 need to be implemented in release 19
LTE3440:
SR001498:LTE Operability
Support of FSMFSecurity
+ FSMFFeature
with SRAN
configurations
LTE1460:
SR000900: Local
SBTSand Remote
user IP management
account Traffic Capturing
LTE3440:
classical LTE Operability Security Feature
Parity with Single
5GC000267: IPsecOAM
Backup Tunnel
5GC000324:
SR001664: Operator
Secondary Account
IPsec Management
backup tunnel on
CB007135: Common SW
gNB for SRAN and 5G for
Public Safety network
classical
SR000600:
SR000749: Backup
Regular IPsec Tunnel check using
peer certificate
LTE3440: LTE
make before breakOperability Security Feature
LTE2090: Regular peer certificate check using
LTE1753:
make before IPSec Backup Tunnel
break
configurations
SR000356: IPsec for BTS
5GC000264:
classical IPsec on Backhaul
configurations
5GC000264:
classical IPsec on Backhaul
configurations
5GC000264: IPsec on Backhaul

LTE2580:
classical IPsec expert mode
5GC000325: Nokia Service Account
Management
SR002656: WebEMon gNBaccess policy restrictions
LTERLCR-27036:
LTE3440: LTE two alarms
Operability descoped from
Security
CB007135:
LTE4500 Common
need to be SW for SRANinFeature
implemented and 5G 19
release
classical
LTE2646:
5GC000325: Continuous BTS product
Nokia Service Accountsecurity
improvements Part
Management on gNB 3
SR001063:
LTE3440: LTE Continuous BTS
Operability product
Security security
Feature
improvements Part 3
LTE2646: Continuous BTS product security
improvements Part 3
SR001063:
SR001664: Continuous BTS product
Secondary IPsec backup security
tunnel for
improvements Part
Public Safety network3
LTE4242: FQDN Support in BTS for SEG
addressing
SR001974: FQDN Support in BTS for SEG
addressing
SR002058: Automatic MEP MAC address

population
LTE4242: FQDN Support in BTS for SEG
addressing
SR001974: FQDN Support in BTS for SEG
addressing
SR002559: Link Aggregation for BH interface
protection
SR001664: SecondarySW
CB007135: Common IPsec backupand
for SRAN tunnel
5G for
Public Safety
classical network
phase I
for SRAN and 5G
Spectrum
phase I
phase I
for SRAN and 5G
Spectrum
phase I
for SRAN and 5G
Spectrum
phase I
LTE3834: LTE Direct NE3S Support

Ref Bts Alarms and Fault Sran21b Sran21a

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Ref Bts Alarms and Fault Sran21b Sran21a

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ref Bts Alarms and Fault Sran21b Sran21a

Uploaded by

Copyright:

Available Formats

Single RAN, Rel.

SRAN 21B BTS Alarms and Faults

No part of this document may be modified.

n connection with a product purchased or

thout notice. At all times, the controlling version is

NCLUDING BUT NOT LIMITED TO

rporation. Other product names mentioned in this

1.1 Overview of BTS alarms and faults

1.2 Handling of BTS alarms an

BTS transmission alarms

Instructions for solving problems

Blocking and unblocking

The excel report consists of two main sections:

The alarms and faults are listed by numbers in an ascending order.

2.1 Alarm List

7100 BASE STATION HARDWARE PROBLEM

BASE STATION/UNIT AUTONOMOUS

BASE STATION RESOURCE BLOCKED BY

BASE STATION EXTERNAL ALARM

BASE STATION CONNECTIVITY

BASE STATION SYNCHRONIZATION

BASE STATION SOFTWARE

BASE STATION CONFIGURATION

7113 BASE STATION ANTENNA LINE PROBLEM

7114 CELL SERVICE PROBLEM

7115 BASE STATION INFORMATION

7116 BASE STATION SERVICE PROBLEM

7220 BASE STATION SECURITY PROBLEM

7222 TEMPORARY ALARM

ORAN RU VENDOR SPECIFIC

7241 ORAN RU EXTERNAL PROBLEM

7600 BCF FAULTY

7602 BCF NOTIFICATION

7606 TRX FAULTY

7607 TRX OPERATION DEGRADED

7650 BASE STATION FAULTY

7651 BASE STATION OPERATION DEGRADED

7652 BASE STATION NOTIFICATION

7653 CELL FAULTY

7654 CELL OPERATION DEGRADED

7655 CELL NOTIFICATION

7656 BASE STATION CONNECTIVITY LOST

BASE STATION CONNECTIVITY

7658 BASE STATION LICENSE LIMITATION

MAINS BREAKDOWN WITH BATTERY

61022 BFDGRP-$BFDGRPID down

61028 LOF on $UNIT, $INTERFACE

61029 LOS on $UNIT, $INTERFACE

Interface under test on $UNIT, $INTERFACE

Missing SFP module on $UNIT,

Link OAM loopback inserted on $UNIT,

61076 Link OAM link lost on $UNIT, $INTERFACE

Link OAM critical link event $E on $UNIT,

61079 SFP HW Failure

61104 EBER on $UNIT, $INTERFACE

61150 LOMF on $UNIT, $INTERFACE

61151 AIS on $UNIT, $INTERFACE

61152 RDI on $UNIT, $INTERFACE

61250 IPCP failure