0% found this document useful (0 votes)

619 views269 pages

Ref Bts Alarms Faults 5g19

Nokia 5g alarms

Uploaded by

Muhammad Ali Khalid

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as XLS, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

619 views269 pages

Ref Bts Alarms Faults 5g19

Nokia 5g alarms

Uploaded by

Muhammad Ali Khalid

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as XLS, PDF, TXT or read online on Scribd

You are on page 1/ 269

5G, Rel.

5G 19, Operating Documentat

5G BTS Alarms and Faults

DN221890198
Issue 02A
Approval Date 2019-03-29
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein.

This document is intended for use by Nokia customers (“You”) only, and it may not be used except fo
the purposes defined in the agreement between You and Nokia (“Agreement”) under which this docum
is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in a
form or means without the prior written permission of Nokia. If you have not entered into an Agreemen
to the Product, or if that Agreement has expired or has been terminated, You may not use this docum
manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and Yo
assume full responsibility when using it. Nokia welcome Your comments as part of the process of con
development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
and statements without notice. Nokia has made all reasonable efforts to ensure that the content
of this document is adequate and free of material errors and omissions, and Nokia will correct errors t
You identify in this document. But, Nokia's total liability for any errors in the document is strictly limited
correction of such error(s). Nokia does not warrant that the use of the software in the Product will be u
or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO TH
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUEN
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF TH
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS F
DOCUMENT OR ITS CONTENT.

This document is Nokia's proprietary and confidential information, which may not be distributed or dis
to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this docume
may be trademarks of their respective owners, and they are mentioned for identification purposes onl

Copyright © 2019 Nokia. All rights reserved.

Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of
danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
ng Documentation

ults
tware product (“Product”) specified

y, and it may not be used except for

Agreement”) under which this document
oduced, modified or transmitted in any
have not entered into an Agreement applicable
ated, You may not use this document in any
ete any copies thereof.

properly trained personnel, and You

ments as part of the process of continuous

You. Any information or statements

nce of the Product are given solely on
erves the right to change any such information
rts to ensure that the content
sions, and Nokia will correct errors that
ors in the document is strictly limited to the
he software in the Product will be uninterrupted

D, INCLUDING BUT NOT LIMITED TO

, TITLE, NON-INFRINGEMENT,
SE, IS MADE IN RELATION TO THE
E LIABLE FOR ANY DAMAGES,
CT, INCIDENTAL OR CONSEQUENTIAL
PROFIT, REVENUE, BUSINESS
AY ARISE FROM THE USE OF THIS
OF ERRORS IN OR OMISSIONS FROM THIS

which may not be distributed or disclosed

ct names mentioned in this document

oned for identification purposes only.

t, and other sources of

n or otherwise handle this

applicable to this product.

n in the “Legal, Safety and

n set.
1. Introduction
1.1 Overview of BTS alarms and faults
This document describes the handling of base station (BTS) alarms and faults. The base station software uses these alarm
and faults as a basis for internal diagnosis and fault reporting in the 5G BTS Site Manager.

1.2 Handling of BTS alarms and faults

Base station alarm handling is based on unit or module state information. It prevents the sending of unnecessary alarms by
checking and updating unit states. Fault messages come either from hardware devices or software components. The faults
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 5G BTS Site Manager.

In addition NetAct is used for handling the BTS alarms.

The BTS is able to maintain alarm handling after it has been commissioned and is in a configured state. During the start-up
the BTS waits for the real-time clock from the Network Time Protocol (NTP) server, and the fault diagnosis starts after the 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) will be used.

BTS transmission alarms

The base station transmission alarms (7665) are reported towards NetAct. The transmission equipment uses the base stati
interface. Therefore, retrieval of the alarm information is mapped either in the NetAct to distinguish between the alarms by
using the fault ID.

Instructions for solving problems

When starting to solve a problem, first refer to the instructions given in the individual alarm descriptions.

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

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

Blocking and unblocking

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

When a unit or cell is unblocked, all the active alarms related to the unblocked unit, module, or cell are automatically sent to
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
on software uses these alarms

ding of unnecessary alarms by

tware components. The faults are
ch are based on an analysis of the

ured state. During the start-up,

ault diagnosis starts after the time
NTP server, the default time

equipment uses the base station

guish between the alarms by

scriptions.

ion of the modules at the BTS.

et is required to cancel it. If the

'Fault source' and 'Instructions' in

in a blocked state, the 'Start'

or cell are automatically sent to the

and alarm attributes.

Changes between issues 02 Alarm Number
DRAFT and 02A

Changed 7100

Changed 7101

Changed 7104

7105

7106

Changed 7107

7108
7108

7109

New 7111

Changed 7115

7116

7121

7122

Changed 61029

61030

61632

61644

61645
61646
Alarm Name Probable Cause

HARDWARE PROBLEM Indeterminate

RESET NOTIFICATION Indeterminate

CELL SERVICE PROBLEM Indeterminate

RAT BASE STATION PROBLEM Indeterminate

SINGLE RAN BASE STATION PROBLEM Indeterminate

BASE STATION CONNECTIVITY Indeterminate

PROBLEM

BASE STATION SYNCHRONIZATION Indeterminate

PROBLEM
BASE STATION SYNCHRONIZATION Indeterminate
PROBLEM

BASE STATION SECURITY PROBLEM Indeterminate

BASE STATION SOFTWARE Indeterminate

MANAGEMENT PROBLEM

BASE STATION INFORMATION Indeterminate

BASE STATION SERVICE PROBLEM Indeterminate

NODEB FIBER LENGTH DEPLOYMENT Replaceable Unit Problem

EXCEEDED

RU FIBER LENGTH DIFFERENTIAL Replaceable Unit Problem

EXCEEDED

LOS on $UNIT, $INTERFACE Indeterminate

Dead Peer Detected Indeterminate

Dup Addr detected- Indeterminate

$DUPLICATEIPV6ADDRESS

IKE authentication failure Indeterminate

IKE SA failure Indeterminate

IPSec SA failure Indeterminate
Event Type Default Severity

x5 Critical

x4 Warning

x4 Critical

x1 Critical

x4 Critical
x4 Critical

x4 Critical

x4 Minor

x4 Critical

x5 Critical

x1 Critical

x1 Major

x1 Major
x1 Major
Meaning Effect

A hardware fault (or faults) has (have) occurred The effect of the fault on the functioning of the
in the base station. This fault may have an network element depends
impact on the existing cells across RATs. Check on the fault description. For more information,
the reason for the fault from the supplementary see base station fault
text field of the alarm. descriptions in 5G BTS System Libraries.

The device is being reset to recover from a fault The effect of the alarm on the Network Element
(or faults). depends
on the fault description. For more information,
see base station fault
A fault (or faults) has (have) occurred in a unit (or descriptions
The effect of in BTS
the System
fault on theLibraries.
functioning of the
units) belonging to the sector indicated in the network element depends
alarm. Check the reason for the fault from the on the fault description. For more information,
supplementary text field of the alarm. see base station fault
descriptions in BTS System Libraries.

A fault (or faults) has (have) occurred in the RAT The effect of the fault on the functioning of the
base station. Check the reason for the fault from network element depends
the supplementary text field of the alarm. on the fault description. For more information,
see base station fault
descriptions in BTS System Libraries.
A fault (or faults) has (have) occurred in the 5G The effect of the fault on the functioning of the
Node B. Check the reason for the fault from the network element depends
supplementary text field of the alarm. on the fault description. For more information,
see base station fault
descriptions in 5G System Libraries.

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

A fault has occurred in the base station security The effect of the fault on the functioning of the
functionality. network element depends
The problem causes a base station unit/service on the fault description. For more information,
to be degraded or faulty. see base station fault
Check the reason for the fault from the descriptions.
A fault has occurred in the base station software The effect of the fault on the functioning of the
supplementary text field of the alarm.
management, such as software network element depends on the fault
download/update/activate/fallback problem, file description.
consistency problem, file corruption problem, etc.
It may be also reported when base station
A fault has occurred in the base station service The effect of the fault on the functioning of the
software is incompatible with detected hardware.
that does not affect basic services of the base network element depends on the fault
The problem causes a base station unit/service
station, or the operator is notified about description.
to be degraded or faulty.
suggested manual intervention. Each fault with
Check the reason for the fault from the
minor or warning severity (that is, a fault that has
A fault has occurred
supplementary in the
text field of base station service
the alarm. The effect of the fault on the functioning of the
no impact on basic base station services,
that affects basic services of the base station. network element depends on
regardless of whether it is hardware, software,
If a fault may have various root causes,(for the fault description.
configuration, synchronization, etc.) is reported
example, hardware problem, software problem or
as BASE STATION INFORMATION.
configuration problem, etc.), this type of alarm is
The NodeB has detected that the deployed Fiber The Radio Unit (RRH) will not be able to operate
reported because more specific alarm
Length between the RAU & RU has exceeded properly, and cannot provide service while this
assignment is not possible.
the supported distance by the software. The condition exists.
The problem causes a cell service to be
NodeB can automatically detect the fiber length
degraded or faulty.
that has been physically deployed between the
This
Check alarm indicates
the reason forthat
the for
faulta configuration
from the The Radio Unit (RRH) will not be able to operate
RAU and RU. If this exceeds what is supported
where
supplementary two optictext fibers are
field ofdeployed
the alarm.to one RU properly, will not be able to start, nor be able to
by the software, then this alarm is generated.
from a RAU, the maximum separation between provide service until the problem is corrected.
those two fibers is 1 km (1,000 meters, 3,280.84
feet). If this distance is exceeded, the RU cannot
This alarm is raised when either no or an No data or clock information is exchanged via
function properly and the differential fiber length
incompatible signal is received on the interface this interface. Possible impact on the connections
between the two fibers needs to be physically
referenced in the alarm text. over this interface:
reduced. There are configurations where two
optical fibers may be deployed to the same RU
$UNIT indicates the affected module from - voice calls or data connections are aborted and
A
from deadthepeerRAU. was Fordetected
example, ininone of the IPsec
a configuration Possible effects:
Equipment Management (last element of the cannot be established anymore
associations
using two modem of theboards
BTS. to a single RU. The - no calls are possible
DN). E.g. SMOD-1.
There
difference is noinresponse
length of to thethe requests
first fiber withsent
theto the - loss of remote management access to other
$INTERFACE indicates the interface on the - remote management connectivity is lost and
peer,
second neither during the
fiber cannot IKE a maximum
exceed network elements
module following the labeling on the frontplate of cannot be established anymore
SA setup, the
differential IPsec SA
separation setup,
length ofnor
1 km during
(1,000DPD. - IKE SAs and IPsec SAs cannot be established
During
the realthe HWIPoraddress configuration
the corresponding the BTS in
parameter The remote peer to come online with the same IP
Note:
meters, Whenor IPsec backup
3280.84 feet). If tunnel
this featureisis
distance or re-keyed
testsManagement
the the direct attached Model. network, whether address on the same subnet
- loss of synchronization if theas a local peer
interface is used
enabled,
exceeded, this
thealarm is not raised
RU cannot function properly and
another
E.g. EIF1, already
IF1 configured node on the network would just disable their
as a synchronization network interface and
source
due
the to failures fiber
differential whenlength
trying between
to setup primary
the on IPsec
twotheir
fibers
already uses the same IPv6 addresses give an error until the situation is resolved by the
tunnel
needs in
to "Secondary_Active_Probing_Primary"
be physically reduced.
network
With IP interfaces.
an Ethernet The DAD
interface, (Duplicate
the physical Ethernet administrator.
-The
Depending on use beof the Ethernet interface, the
The
state.alarm is raised when the IKE authentication IKE SA cannot established.
address
link is detection)
detected to detects
be down. those
All duplicated
other IPv6
transmission This
above allows the local
described peercan
impact to continue
occur for functioning
the local
credentials provided by the peer
addresses
alarms and to
related prohibits
this the are
signal operation of this
suppressed. without disruption,
SBTS and/or other but completely
(S)BTS breaks
elements IP are
if they base
is not valid.
IPv6 address in the BTS. The Alarm contains the communications for the connected
chained via the Ethernet interface. network.
corresponding
Probable causes IPv6foraddress
Ethernetand the interface on
interfaces:
The
which alarm is raised,
the address
- a cable/fiber is cutwasif IKE
or parameters
configured.
there Forare
each
is no cable/fiber notDAD IKE SA cannot be established and subsequently
matching
event
connected with
a separate
to thetheinterface
peer proposal.
reporting shall be It can happen
indicated. no IPsec SAs can be established.
due
- theto following two failures
electrical/optical signal is excessively
--> When the BTS sends or receives a failure
attenuated
notification
- the port atas theresponse
connected to an
far IKE_SA_INIT
end node is
request
switchedmessage. off The failure notifications
includes:
- the advertised technology capabilities with auto-
-negotiation
NO_PROPOSAL_CHOSEN
of both devices at the Ethernet link do
-not INVALID_SYNTAX
match
- INVALID_MAJOR
the Ethernet technology VERSION at both devices at the
-Ethernet
INVALIDlink _IKE_SPI
is forced manually and not
-compatible
INVALID_MESSAGE_ID
- UNSUPPORTED_CRITICAL_PAYLOAD
the remote peer of an Ethernet link is not or auto-
FAILED_CP_REQUIRED
negotiation capable or has auto-negotiation
--> Whendisabled
function the BTSby sends or receives a failure
configuration
This alarm is raised when the BTS sends or The related IPsec SA can't be established and
receives following notification as response to an used.
IKE_AUTH or CREATE_CHILD_SA request
message.
The failure notifications includes the following:
- NO_PROPOSAL_CHOSEN
- TS_UNACCEPTABLE
- INVALID_SYNTAX
- INVALID_MAJOR VERSION
- INVALID _IKE_SPI
- INVALID_MESSAGE_ID
- UNSUPPORTED_CRITICAL_PAYLOAD
- SINGLE_PAIR_REQUIRED or
FAILED_CP_REQUIRED
Identifying Additional Information Fields Additional Information Fields

1. HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
2. Path(URI) of the impacted hardware unit, when the
impacted unit is FSM, FSP, FBB, FR, FAN, AntennaLine,
FYG, or SFP.

1. HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
2. Path(URI) of the impacted hardware unit, when the
impacted unit is FSM, FSP, FBB, FR, FAN, AntennaLine,
FYG,
1. HWorInventory
SFP. Id (RDN) and Serial Number of the
impacted hardware unit
2. Path(URI) of the impacted hardware unit, when the
impacted unit is FSM, FSP, FBB, FR, FAN, AntennaLine,
FYG, or SFP.

1. HW Inventory Id (RDN) and Serial Number of the

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

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

(i) HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
(ii) Path of the impacted hardware unit.

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

Path of the hardware unit. Serial Number of the hardware unit.

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

FAULT NAME
No connection to unit

FAULT ID
10 : EFaultId_NoConnectionToUnitAl

MEANING
A module required in commissioned 5G BTS configuration has not been
FAULT NAME
detected or connection to a module belonging to the 5G BTS configuration
Unit (module) temperature is high
FAULT
has been NAME lost.
Phase error exceeds the interference limit
FAULT ID
INSTRUCTIONS
1936 : EFaultId_FrTempHigh
FAULT
To clearID this fault, perform the following steps:
4452
FAULT NAME : EFaultId_PhaseErrorExceedsTheInterferenceLimitAl
MEANING
1.
Phase Makeerror sureexceeds that the the module is properly
interference limit connected. Check the alarming
Validated module temperature exceeds or is equal to the predefined
MEANING
module.
maximum value allowed.
This
2.
FAULT fault
Check indicates
IDthe that the absolute phase error of the BTS exceeds the
fault history.
limit
4452 : EFaultId_PhaseErrorExceedsTheInterferenceLimitAl
INSTRUCTIONS
MEANING
of 1.5 us. This can occur when:
Take
A corrupted the following
SW filesteps in thetoFLASH
clear the fault:
is detected. The unit cannot perform a
MEANING
complete start-up.
1)
This The absolute
fault ifindicates value of measured/estimated
that temperature/environmental
the absolute phase error of conditions phase error
the BTSof exceeds
the BTS the has
1. Check the ambient are within
exceeded
FAULT
limit NAME the limit of 1.5 us,
the design limits for the radio module. When the ambient
INSTRUCTIONS
Unit
FAULT
of 1.5(antenna
us.NAME submodule) temperature is high
Update
OR theThis
temperature/environmental SWcan in the occurBTS. when:
conditions exceed the limits, the alarm is
Radio
expected and no further actions RF
Module does not support are sharing
needed.
FAULT
1) The absolute ID value of measured/estimated phase error of the BTS has
2)
2906
FAULT
exceeded The: EFaultId_FrAmTempHighAl
BTS
IDifthe has limitlostofall 1.5phase
us, sync reference sources, but does not have
2. Check airflow is free of foreign objects. Make sure the minimum
sufficient
4515 history data for holdover.
: EFaultId_RadioModuleDoesNotSupportRfSharingAl
thermal
FAULT clearances guidelines are followed. Remove any objects that
NAME
OR
MEANING
OR
might
Failure be blocking the airflow and mount the module according to
FAULT
3)
Validated
MEANING The in NAME
BTS troubleshooting
is synchronized
antenna submodule data collection
bytemperature
reference which is higherhas than
capability to internal
the predefined
instructions
RF Module and
configuringrecommendations.
failed
holdover
maximum
Detected
2) The BTS (Sync
allowed
RFhas Hub
module lost all Master/GNSS)
value.
does
phase not sync
support which reports
commisioned
reference the
sources, phase
RFbut error
sharing
does not of have
type. the
FAULT
provided IDsync signal. The absolute value of estimated total phase error in
sufficient
3. Check
4514
FAULT IDhistory
if excessive data sunlight
for holdover.
: EFaultId_FailureInTroubleshootingDataCollectionAl is causing the unit to overheat. Install the
the "slave"
INSTRUCTIONS
CPRI RF modules side exceeds the limit of 1.5 us or source reports that its
OR
sunshield
1900 followinginthe
: EFaultId_FrConfiguringFailed
NR-LTE
mounting sharing: RM HW
instructions and version should be >= Rel
recommendations.
holdover
Take
5.1
3) the
(NAKHA)
The BTShas
following isexpired. steps to clear
synchronized by the fault: which has capability to internal
reference
MEANING
FAULT NAME
holdover
This faultfan (Sync Hubthat Master/GNSS) which reports the phase error ofan the
MEANING
INSTRUCTIONS
1.
Cooling Check
INSTRUCTIONS
provided ifindicates
sync the
is overambient
signal. speeding
The
a user-configurable
temperature/environmental
absolute value of
BTS fault
estimated
has triggered
conditions
total are within
internal
The
If
the GPS Radio
design snapshotmodule
is configured
limits and
for snapshot
configuration
as to
the a reference
antenna collection
has clock,
sumodule. has
failedperform
because
When failed
the a hardware or in
(partially
ofambient
the
phase
following:or error
Follow
the
FAULT the
"slave" NAME steps
side below
exceeds resolve
the limit the
of 1.5fault:
us or source reports that its
completely).
software
1.
FAULT Check ID fault.
the GPS
temperature/environmental receiver installation.
conditions exceed the limits, the alarm is
holdover
FAULT has
NAME
EFaultId_X2SctpSetupAl expired.
2.
1. Check
expected
4080 In HW the
and GPS
no further
: EFaultId_FanOverSpeedAl
case of NR-LTE receiver status.
actions
sharing, tryare needed. Radio Unit HW version >=
to connect
SFP
INSTRUCTIONS Failure on unit $U, interface $IF
3.
Rel Check
5.1
INSTRUCTIONS the
(NAHKA) connection between the GPS receiver and ASIx.
FAULT
When
Take
2. Checkthe ID
snapshot
following
if airflow is triggered,
actions
is free ofto but
clear
foreign not thecollected,
fault: Make
objects. check
sure the reason
the minimum in the
MEANING
2.
If
FAULT
4446 In case
GPS is NR-LTE sharing
IDconfigured
: EFaultId_X2SctpSetupAl is not intended,
as a reference RF sharing
clock, perform should
the following: be disabled
Alarm:
If
thermal
FAULT
Fan the TOP signal
clearances
NAME
is running fasteris configured
guidelines
than required. as
are a reference
followed. clock,
Remove perform
any the
objects following:
that
in
1.
61079 SCF
Check : SFP the GPS
HW receiver
Failure installation.
-1.
might
Phase New
Confirm
Check snapshot
beerror the if exceeds
blocking the can
existing
connection the be blocked
configuration
to
airflow
the the and if mount
TOP
interference there isisthe
server
limit anmodule
within ongoing snapshotRAP
the configured
according toin process
HW
3.
2.
MEANING Replace
Check the the GPS alarmingreceiver unitstatus.
with the unit planned in 5G BTS planned HW
-capabilities.
Too
instructions
INSTRUCTIONSmany snapshots:
and limit
recommendations. the number of snapshots per Fault ID (+CU or
configuration
3.
MEANING
The Check
transport the (BTS
connection
path profile).
(SCTP) between
for the
connection GPStoreceiver
the LTE and
eNB ASIx.
has failed to be
+DU)
2.
FAULT
ReplaceCheckto 5 theper
IDthe fan. 24
BTS hours
connections and commissioning settings.
The
-3. optical
established.
Snapshot
Reset the transceiver
This
RAP.might
taken too often:has reported
be because
setisthe a transmission
of anthe
minimum unplugged fault
cable
timetointerval condition
to the
per Fault and
eNB.
ID
3.
4452
If Check
the TOP if signal
excessive is sunlight
: EFaultId_PhaseErrorExceedsTheInterferenceLimitAl
configured as causing
a reference unit
clock, overheat.
perform Install
the the
following:
has
There
(+CU disabled
oris
4. Block/Unblock no
+DU) the
transport laser
between
thethe transmitter.
path
BTS. available
snapshots toto15 continue
minutes operation on the faulty
sunshield
1. Check following
thewith connection mounting instructions and recommendations.
connection
-5. Other
FAULTIf the reason
MEANING HW
NAME inthe
configuration eNB.toiscollection
snapshot the TOP server
confirmed, process
it means (collect OAM logs
this problem to resolve
is caused by
Probable
reason)
the 5G BTS causes: SW. Check the other active alarms.
Supervision
This fault failure that the absolute phase error of the BTS exceeds the
indicates
-FAULT
The optical
INSTRUCTIONS
When
NAME
snapshot transceiver
is collected, is defective.
lack of snapshot data can be read from the
limit
FAULT
RF sharing NAME mode conflict
Note:
Alarm.
FAULT
of 1.5 Perform
us.ID This the
can steps
occur below
when: in the listed order until the alarm
Firmware
Note: The SW
disappears: unitmismatch
and interface variables ($U,$IF) will be replaced by
4494
FAULT
FAULT : EFaultId_SupervisionFailureAl
NAME
ID
NAME
appropriate hardware. Example: unit-FSM, interface EIF1.
Unknown
1) The
FAULT
4516
Antennas : absolute
ID HW resource
value of
EFaultId_RfSharingModeConflictAl
assignment notmeasured/estimated
available phase error of the BTS has
1. Check
FAULT
MEANING
exceeded NAMEthetheconnection
limit of 1.5 with us, the eNB.
2056 :
INSTRUCTIONSEFaultId_SwMismatchAl
RF
There
FAULT Module
hasID been critical a BTSfile notresetfound caused by software components supervision
MEANING
5. The cable between the GPS receiver and the BTS might be faulty.
Check the situation and change the cable, if needed.
6. There might be a HW fault in the GPS receiver. Check the operation
and change the GPS module, if needed.
7. ThereNAME
FAULT might be a HW fault in the BTS System Module. Check the
operation
Automaticand
BTSchange theCertificate
Operator System Module,
retrievalif unsuccessful
needed.

FAULT ID
61510 : NO_CERTIFICATE
FAULT NAME
Unit
FAULT (antenna
NAMEsubmodule) SW download failure
MEANING
Master
A requestedhas unit lost connection
certificate could nottobe the slave unit
retrieved from the certificate authority
FAULT ID
(CA).
2913
FAULT : EFaultId_FrAmSwDownloadFailAl
ID
FAULT
A requested NAME certificate could not be renewed from the certificate authority
4019
Radio : EFaultId_KeepAliveStatusErrorAl
(CA). Diagnostic Files collected
MEANING
RF
MEANING SW detected that FPGA software downloading to antenna submodule
FAULT
A requested ID certificate could not be retrieved as the number of certificates
failed.
Connection to repository
SW entity server has been lost.
4527
received : EFaultId_RadioTechnicalLogUploadRecommendedAl
from (RA) or certificate authority (CA) are more
FAULT NAME
than
No expected.
connection between primary and BTS extension system module
INSTRUCTIONS
MEANING
1.
This Resetfault the
is most RF HW likely unit.
the result of astored
BTS hardware problemstorage or a
After
A an RU
requested crash,
certificate RU has could collected
not be crash logs.
in the remaining
FAULT
reference ID source
available
4352 on the BTS. Operator cleanup (e.g. via site manager faulted
that is
: EFaultId_NoConnectionToBtsExtensionUnitAl
being followed by the BTS that is in a or NetAct)
2.
condition, If the problem
therefore continues
producing after step 1 has been performed, replace the
FAULT
INSTRUCTIONS
of old, unused NAME trust chains mayan beinaccurate
required. reference. Perform the
RF
following HW unit. steps tologs isolate the cause
EFaultId_NodebFiberLengthDeploymentExceededAl
Collect technical from the BTS of to the
clear fault:
the alarm raised by this fault.
MEANING
Internal
Note: For logs RAC, collected
this faultby is this process
raised only can
for onlyautomated
the be analyzed by Nokia
operation
Connection
1. Check theto a secondary
other alarms ofunitthe that
BTSbelongsand actto the BTS Dual
accordingly. ASIx
FAULT
R&D.
triggered IDby system, for e.g., automatic CMP key update (KUR). But not
configuration has been lost.
4414
for the : EFaultId_NodebFiberLengthDeploymentExceededAl
manual operations, for e.g., manual CMP IR or CMP KUR triggered
FAULT
2. Ifoperator.
there NAME are no other synchronization-related alarms active, start the fast
Additionally:
by
EFaultId_RuFiberLengthDifferentialExceededAl
INSTRUCTIONS
tuning
- Checkwith
MEANING theBTS alarm Element
history Manager.to confirm the frequency of fault 4527 in a
Note: Perform the steps in the listed order until the fault is resolved.
The
specific
INSTRUCTIONS NodeB eNB. has detected that the deployed Fiber Length between the
FAULT
1. ResetIDthe site.
3. BTS.Run fast tuning again.
RAU
-1. Check
Check & RU the the has
alarm
CMP exceeded
history
configuration. theother
for distance alarms supported
in the same by software.
eNB thatIf might this be
4415
2. Check : EFaultId_RuFiberLengthDifferentialExceededAl
the connectivity:
FAULT
distance
related,
2. Check NAME
isforexceeded,
especially CA serveralarms the RU cannot
with
reach-ability. Radio alarms function and this fault occurs. This
AirScale:
4. Check Ensure
the reference that the module
signal accuracyis properly connected to the rack.
LOS
applies
3.
MEANING
3. If
Check
on to
none $UNIT,Cloud
of
the the
SW
$INTERFACE
BTS and
above
version work, on
5Gcontact
BTS.
Secondary CAby measuring
administrator/Nokia
core if it is the
it with
same
aservice
as
frequency
Primary
counter
If (note: requires a good timebase for the counter). The reference
Inan
personnel
core.
signal
alarm with fault
a configuration
can be found where 4527two
from the
frequently
optic
Sync fibers
Out
occurs
interface
in the same
are deployed of the to eNB,
a RU
Flexi
alarms
from a with
System
FAULT
INSTRUCTIONS
the same IDfaults mentioned above are present in the same eNB, or the
RAU,
4.
Module, Replace thethe maximum
the faultyseparation unit. between those two fibers is 1 kmaccuracy (1,000
61029
To
eNB
FAULT solve thisrequired
: FTM_LOS
performance
NAME problem, accuracy
a technician
is degraded, is
then+/-0.015ppm.
should
collect inspect If the
a snapshot thereference
optic
and fiber a case
open
meters,
is correct, 3,280.84
run fast feet).
tuning. If this
If the distance
reference is exceeded,
accuracy the
is notRU cannot
correct theis
deployment
for
Dead Nokia Peer R&D of the
Detected logfault RU unit in question. This fault occurs when a RU
analysis.
function
cause of and
the this
fault is the is reference
raised. This applies
source the toBTSCloud is BTS and
tuning to. 5G BTS.
MEANING
configured with a
Two
Troubleshoot fibers arethe deployed
external from a single modem
synchronization network board. to find the isroot cause.
This
fiber
Each alarm
optic
RU is raised
cable between whenthe either RAU no or 4527
and an RUincompatible
that
faultphysically signal
exceeds received
the
FAULT
FAULT
Other BTSsIDcrash
NAME
with
are
the
reported
same alarm
with own
can provide further information about the
on
maximum
CRL the interface
Update length Failurereferenced
supported. inThethe alarm
maximum text. length supported will depend
61030
INSTRUCTIONS
location : FTM_DPD
of the root cause.
FAULT
$UNIT
on the 5G NAME
indicates
release the in affected
questionmodule from Equipment Management
(and changes/increases with different(last
To
5.
Dup Ifsolve
the
Addr this problem,
reference accuracy a technicianis correct should
andphysical inspect fast
running the optic tuning fiber
does notbe
element
releases).
FAULT IDofdetected-$DUPLICATEIPV6ADDRESS
the DN).
The physical E.g.connections
SMOD-1. and deployment should
MEANING
deployments
help, replace of
the thesystemRU unit in question. This fault occurs when a RU is
module.
$INTERFACE
checked to see indicates
that these thelengths
interface on the module following the labeling
61074
A dead: peer
configured CRL with Update
has two been failure
fiber detected
optical cables in are
onenot of
to the
exceeded.
oneIPsec modem
The technician
associations
card. The of the
can
FAULT
on
then the reset ID
frontplate
NAME the NodeB of theand realsoftware
HW or the will corresponding
automatically parameter intothe
re-compute see if
Transport Module.
differential between these fiber optical cables must not exceed 1000 m.
61632
Management
the
Remote
MEANING fiber : IPV6_DUPLICATE_ADDRESS_DETECTED
lengths
node Model.
does are not
not within
support the
NR acceptable
RAN Container differential
Extension range. Header of
FAULT
There
The physical NAME
is no response connections to the and requests
physicalsent to the peer
deployment during
should bethe IKE SAto
checked
E.g.
GTP-U
This EIF1
fault isIPsec
raised
IKE
setup,
see authentication
that the these SAiffailure
lengths theare
setup, BTS or cannot
not during
exceeded. update
DPD.Thethe Certificate
technician can Revocation
then resetList
MEANING
(CRL). The failure reasons include the following:
the
FAULT
During NodeB NAME
the and
IP software
address will automatically
configuration, the Ethernet
BTS re-compute
tests theisto see attached
direct if the fiber
With
FAULT
-FAULT Thean LDAP Ethernet
ID
ID binding interface,
fails. the physical link detected to be
Note:
lengths
Toggling: Whenare the
not
<Fault IPSec
within
name> backup
the acceptable tunnel feature
differential is enabled,
range. this alarm should
network
down.
7900
-61644 The : All whether
other theisother
transmission
EFaultId_NrRanContainerExtensionNotSupportedAl
LDAP search empty already
alarms
(no CRL configured
related
found), to node
orthisthe on
signal
LDAP thearenetwork
suppressed.
search uses
contains
not be : IKE_AUTH_FAILURE
raised because of failures when trying to set up primary IPSec
FAULT
already
more than NAME
theone same entry. IPv6 addresses on their network IP interfaces. The DAD
tunnel
FAULT
IKE inID "Secondary_Active_Probing_Primary" state.
(Duplicate
Probable
MEANING
-MEANING TheSA CRL failure address
causes
signature fordetection)
Ethernet detects
validationinterfaces: fails. those duplicated IPv6 addresses
4026
and
-This a
The :
fault
CRLEFaultId_TogglingAl
prohibits
cable/fiber isis the
raised
file is
exceedsoperation
cut or there
when theremoteofisthis
BTS IPv6 address
nostorage
cable/fiber
GTP-U limit.connected
tunnel in the BTS.
endpoint to
(intheThe
non- Alarm
interface
The
Possible alarm reasons: raised when the IKE authentication credentials provided by
FAULT
contains
-standalone the
The BTS IDthe
electrical/optical corresponding
call:
certificate MeNB) issignal
signals
part IPv6
is
of thetoaddress
excessively
SgNB
CRL. and
that itthe
attenuated
does interface
not on which
support "NR the RAN
the
-MEANING a peer are
cable is cutnotorvalid. there is no cable connected to the interface
61645
address
-Container"the port : IKE_SA_FAILURE
wasatGTP-Utheconfigured.
connected
extension For fareachend DAD
header. node It isevent
isrequired
switcheda separate
foroffflowreporting
control between shall
-The theBTS signal Fault,is excessively
whichever attenuated
fault name is mentioned in the Fault name
be
-INSTRUCTIONS
PDCP the
INSTRUCTIONS
-is the
indicated.
advertised
portin SgNB
at the
technology
and
connected RLC in capabilities
MeNB
far end and
node
with
also
is
auto-negotiation
to
switchednotify PDCP
off in of
SgNBboth offield,
MEANING
devices toggling
succesfully
Execute at in
the
general the BTS.
Ethernet
delivered The
PDCP
configuration link toggling
doPDUs.not match
checks: alarm condition is presented to the
Check
user withthe authentication
this new BTS credential
Fault. Toggling providedalarms byare thesuppressed
peer (certificate).
The
INSTRUCTIONS
- the alarm
Ethernet
Configuration is raised,
technology
of if IKE
primary parameters
at
CRL both devices
server are
IP atnot
address thematching
Ethernet
and port. with isuntil
linkthe peer
forced the
INSTRUCTIONS
toggling
proposal. alarm condition is cleared. Severity of this BTS Fault is the same
1.Check
manually
INSTRUCTIONS
-1.Configuration forand duplicate
not DNSIPv6
compatible
of cables server addresses
IP address. configured in the BTS.
Check that the are connected to the correct connectors.
-as
It
Check the
can
the severity
happen
remote
peer peer
(MeNB) of
due the
ofto antoggling
following
Ethernet
configuration BTS
two link Fault.
failures
is not
/ SW version auto-negotiation
to enable capable
support of or
2.
--> Check
When that
the the gNB
5G interface sends at or thereceives
far-end ainterface
failure is switched
notification ason. response
2.Change
has
needed
Check or
auto-negotiation
extension.
remote delete
peers the identified
function
andare disabled
intermediate duplicate by
network IPv6
configuration addresses.
3. Check
INSTRUCTIONS
to an IKE_SA_INIT whether there
request active
message. alarms theelement
atfailure
TheCertificate end.interconnections.
farnotificationsIf there are, follow
Check
the the LDAPfor
instructions connection
handling towards
those the
alarms. Revocationincludes: List
Follow
-Probable the
NO_PROPOSAL_CHOSEN
Workaround:
server. steps
causes below to
for PDH interfaces:
Modification clear the fault:
of SgNB parameter dlDataSplitMode from
-"dlOverX2U"
INVALID_SYNTAX
a cable
Check theissize cut oror there
the fileisat
"dlOverF1UX2U"
of nothe cable toconnected
"dlOverF1U".
Certificate to the
Revocation This interface
disables
List server. data
-1.INVALID_MAJOR
Check
the electrical the fault signal name
VERSION of the toggling
is excessively BTS fault.
attenuated
FAULT NAME
IPSec SA failure

FAULT ID
61646 : IPSEC_SA_FAILURE

MEANING
This alarm is raised when the Network Element sends or receives the
following notification
as a response to an IKE_AUTH or CREATE_CHILD_SA request
message.
The failure notifications includes the following:
- NO_PROPOSAL_CHOSEN
- TS_UNACCEPTABLE
- INVALID_SYNTAX
- INVALID_MAJOR VERSION
- INVALID _IKE_SPI
- INVALID_MESSAGE_ID
- UNSUPPORTED_CRITICAL_PAYLOAD
- SINGLE_PAIR_REQUIRED or FAILED_CP_REQUIRED

INSTRUCTIONS
Check that the configurations for the peer and the Network Element
security policies for corresponding failure notification.
Related Faults Related Features

10 5GC000380: 10GBase-SR Optical GE Interface

94 5GC000167: Fault Management general flow
95 and mechanism
1815 5GC001082: Classical gNB software
1928 Management
1932 5GC000540: 5G18A operability functionality
1936 porting to classical BTS deployment
2906 5GC000381: Small Form Factor Pluggable
2912 SFP/SFP+/SFP28 slot
16
2914 5GC000180:
5GC000382: 5G Node B Temperature
10GBase-LR Optical GE Interface
1806
4026 management
5GC000385: 1000Base-SX Optical GE Interface
1900
4544 5GC000316:
5GC000386: 5G Node B Synchronization
1000Base-LX Mode
Optical GE Interface
1901
4545 Support
5GC000387: 1000Base-ZX Optical GE Interface
4001
61050
23 5GC000718:
5GC000180: F1
5GC000388: 5G cell management
1000Base-BX
Node Optical GE Interface
B Temperature
4019
61079
28 5GC000540:
5GC000624:
management 5G18A operabilityOptical
10/25GBase-SR functionality
GE
4077
94 porting to
Interface classical BTS deployment
5GC000316: 5G Node B Synchronization Mode
4352
95 5GC000496:
5GC000625:
Support Classical BTS introduction
10/25GBase-LR Optical GE
4452
1806 5GC000952:
5GC000718: F1 cell management gNB
Interface Recovery for Classical
4494
1850 5GC000426:
5GC001082: 5G
5GC001179: BTS Transport,
gNB Synchronization
Fronthaul
Classical CPRI 7 - 10/25GE
software and
4520
1900 Security Features
QSFP+/QSFP28
Management rebasing
Base Line on ASIK for
6293
1901 Classical
5GC000847:
5GC000540: 5G NodeB
BTS
5G18A Fronthaul CPRI
operability 7 - 10GE
functionality
6918
1928 5GC000631:
SFP+ Dual ABIL
Fiber &
Base ASIK
Line - new
porting to classical BTS deployment SW
23
1937 deployment
5GC000848:
5GC000718: BTS
5GC000952: Fronthaul
F1 cell
Recovery managementCPRI 7 gNB
for Classical - 10/25GE
28
1981 5GC000371:
SFP+/SFP28
5GC000540: gNB
Dual
5G18A recovery
Fiber Baselog
operability collecting
Line
functionality
5GC000426: 5G Transport, Synchronization and
29
2911 5GC000849:
porting BTS rebasing
SecuritytoFeatures
classical Fronthaul CPRI
BTS deployment
on ASIK7 -for
10GE
29
4001 SFP+ Single
5GC000952: Fiber
Recovery for Classical gNB
Classical 5G NodeB
1806
4077 5GC000850:
5GC000726: BTS NR-LTEFronthaul CPRI 7 - 10GE
FDD concurrent operation
2 5GC000180:
SFP+ CWDM 5G Node B Temperature
1907
4452 for CPRI RUs
24 management
5GC000851: BTS
1911
4478
27 5GC000371:
5GC000579: gNB Fronthaul
recovery CPRI
log 7 - 10/25GE
collecting
4001
4479 SFP28 SingleLong
5GC000418: Fiberfiber
AMOB
support
outdoor
for CPRI
sub-rack for 5G
1811 fronthaul
5GC000418: AMOB outdoor sub-rack for 5Gfor
4515
4495 5GC001025: NR-LTE concurrent operation
2056 5GC000167: Fault Management general flow
4516
4515 CPRI TDD MAA radios
4026 and mechanism
6293
4516 5GC001091:
4073 5GC001082: AirScale
ClassicalIndoor Radio NR
gNB software
4517
4077 operation
Management
6918
4078 5GC000540: 5G18A operability functionality
4026
4079 5GC000474: X2 Management
porting to classical for NSA mode 3x
BTS deployment
4445
4080 operation
5GC000952: Recovery for Classical gNB
4446
4083 5GC000577:
5GC000507: TRS Fault Support
triggeredofsnapshot
NSA interfaces
4447
4083 (X2 and S1-U) over IPv4 / IPv6
4490
4083
9 5GC000167:
5GC000316: Fault Management
5G Node general flow
B Synchronization Mode
4505
4514
16 and mechanism
Support
4506
4523
26 5GC000540:
5GC000318: 5G18A
1PPS&ToD operability functionality
Sync from External
4507
4524
1817 porting to classical
GNSS Receiver BTS deployment
4508
1818 5GC000496:
5GC000313: Classical
Timing overBTS introduction
Packet with Phase
6203
1819 5GC000681:
SynchronizationDual Stack IPv4/IPv6 for NG /Xn
1898 interfaces in SA deployment
5GC000167: Fault Management general flow
4011 5GC000426:
and mechanism 5G Transport, Synchronization and
4019 Security Features
5GC000609: ToP with rebasing onSync
Phase ASIKResiliency
for
4026 Classical 5G NodeB
5GC000540: 5G18A operability functionality
4122 porting to classical BTS deployment
4123 5GC000952: Recovery for Classical gNB
4124 5GC000426: 5G Transport, Synchronization and
4125 Security Features rebasing on ASIK for
9 5GC000316: 5G Node B Synchronization Mode
16 Support
26 5GC000318: 1PPS&ToD Sync from External
1817 GNSS Receiver
1818 5GC000313: Timing over Packet with Phase
1819 Synchronization
1898 5GC000167: Fault Management general flow
4011 and mechanism
4019 5GC000609: ToP with Phase Sync Resiliency
4145
4026 5GC000323:
5GC000540: Operator Certificatefunctionality
5G18A operability Management
4266
4122 & Multi Layer
porting of CABTS deployment
to classical
4267
4123 5GC000324:
5GC000952: Operator
RecoveryAccount Management
for Classical gNB on
4268
4124 gNB
5GC000426: 5G Transport, Synchronization and
4269
4125 5GC001082:
Security Classical
Features gNB on
rebasing software
ASIK for
2913 5GC001082: Classical gNB software
4441
4126 Management
Classical 5G NodeB
Management
4444
4210 5GC000540: 5G18A operability functionality
5GC000540: 5G18A operability functionality
61074
4298 porting to classical BTS deployment
porting to classical BTS deployment
61510
4323 5GC000952: Recovery for Classical gNB
4296
61616
4385 5GC000475: SgNB Addition and Release for
4298
61618
4452 NSA mode 3x operation
4352
61642
61631 5GC000313: Timing over Packet with Phase
4527 Synchronization
7900 5GC000352: GNSS receiver FYGC
4352
8000 5GC000609: ToP with Phase Sync Resiliency
5GC000540: 5G18A operability functionality
porting to classical BTS deployment
5GC000426: 5G Transport, Synchronization and
4414 5GC000579: Longrebasing
Security Features fiber support for CPRI
on ASIK for
fronthaul
Classical 5G NodeB
5GC000540:
5GC000371: 5G18A operability
gNB recovery functionality
log collecting
porting to classical
5GC001097: Basic BTS
PCMD deployment
For NSA
5GC000952: Recovery for Classical gNB
4415 5GC000579: Long fiber support for CPRI
fronthaul
5GC000540: 5G18A operability functionality
porting to classical BTS deployment
5GC000952: Recovery for Classical gNB
61029 5GC000380: 10GBase-SR Optical GE Interface
5GC000381: Small Form Factor Pluggable
SFP/SFP+/SFP28 slot
5GC000382: 10GBase-LR Optical GE Interface
5GC000385: 1000Base-SX Optical GE Interface
61030 5GC000264: IPsec on Backhaul
5GC000386: 1000Base-LX Optical GE Interface
5GC000426: 5G Transport, Synchronization and
5GC000387: 1000Base-ZX Optical GE Interface
Security Features rebasing on ASIK for
5GC000388: 1000Base-BX Optical GE Interface
Classical 5G NodeB
5GC000624: 10/25GBase-SR Optical GE
61632 5GC000307:
Interface Transport IPV4/IPv6 stack
enhancement
5GC000625: 10/25GBase-LR Optical GE
5GC000952:
Interface Recovery for Classical gNB
5GC000426:
5GC001179: 5G BTSTransport,
FronthaulSynchronization
CPRI 7 - 10/25GE and
Security FeaturesBase
QSFP+/QSFP28 rebasing
Line on ASIK for
61644 5GC000264: IPsec on Backhaul
Classical
5GC000847: 5G NodeB
5GC000426: BTS FronthaulSynchronization
5G Transport, CPRI 7 - 10GE and
SFP+ Dual Fiber Base Line
Security Features rebasing on ASIK for
5GC000848: BTS Fronthaul CPRI 7 - 10/25GE
Classical 5G NodeB
SFP+/SFP28 Dual Fiber Base Line
61645 5GC000264:
5GC000849: IPsec on Backhaul
BTS Fronthaul CPRI 7 - 10GE
5GC000426: 5G Transport, Synchronization and
SFP+ Single Fiber
Security
5GC000850:Features
BTS rebasing
Fronthaulon ASIK
CPRI 7 for
- 10GE
Classical
SFP+ CWDM 5G NodeB
5GC000851: BTS Fronthaul CPRI 7 - 10/25GE
SFP28 Single Fiber
61646 5GC000264: IPsec on Backhaul
5GC000426: 5G Transport, Synchronization and
Security Features rebasing on ASIK for
Classical 5G NodeB
Clearing Time to Live Restriction status

1 Automatic 0 No

1 Automatic 0 No
1 Automatic 0 No

1 Automatic 0 No

1 Automatic 0 Yes

0 Manual 0 No

1 Automatic 0 No

1 Automatic 0 No
1 Automatic 0 No
Changes between issues 02 Alarm Number
DRAFT and 02A

Changed 7100

Changed 7101

Changed 7104

7105

7106

Changed 7107
Changed 7107

7108

7109

New 7111

Changed 7115

7116

7120

7121

7122

7123

7124
7125

Changed 61029

61030

61605

61606

61632

61644

61645

61646

New 70074

70158

70161
New 70164

70377

70378

70477

70478

70480

70481

70494
Alarm Name Probable Cause

HARDWARE PROBLEM Indeterminate

RESET NOTIFICATION Indeterminate

CELL SERVICE PROBLEM Indeterminate

RAT BASE STATION PROBLEM Indeterminate

SINGLE RAN BASE STATION PROBLEM Indeterminate

BASE STATION CONNECTIVITY Indeterminate

PROBLEM
BASE STATION CONNECTIVITY Indeterminate
PROBLEM

BASE STATION SYNCHRONIZATION Indeterminate

PROBLEM

BASE STATION SECURITY PROBLEM Indeterminate

BASE STATION SOFTWARE Indeterminate

MANAGEMENT PROBLEM

BASE STATION INFORMATION Indeterminate

BASE STATION SERVICE PROBLEM Indeterminate

ALL RAPS OUT OF SERVICE Replaceable Unit Problem

NODEB FIBER LENGTH DEPLOYMENT Replaceable Unit Problem

EXCEEDED

RU FIBER LENGTH DIFFERENTIAL Replaceable Unit Problem

EXCEEDED

5G BASE STATION SCALING Indeterminate

NOTIFICATION

5G BASE STATION INCOMPLETE VM INIT Response Time Excessive

5G BASE STATION FAILED VM INIT Response Time Excessive

LOS on $UNIT, $INTERFACE Indeterminate

Dead Peer Detected Indeterminate

BFD-$BFDID down in ingress Indeterminate

BFD-$BFDID down in egress Indeterminate

Dup Addr detected- Indeterminate

$DUPLICATEIPV6ADDRESS

IKE authentication failure Indeterminate

IKE SA failure Indeterminate

IPSec SA failure Indeterminate

MAXIMUM THRESHOLD HAS BEEN Threshold Crossed

CROSSED

FILE SYSTEM USAGE OVER LIMIT Threshold crossed

OPERATING SYSTEM MONITORING System call unsuccessful

FAILURE
ETHERNET LINK FAILURE Link failure

SYSTEM CLOCK OUT-OF-SYNC WITH Clock Synchronization Problem

NTP SERVER

CONNECTIVITY LOST TO FORWARDER Loss of Frame

x4 Critical

x1 Critical
x1 Critical

x4 Critical

x4 Minor

x4 Critical

x5 Critical

x4 Minor

x4 Minor
x4 Critical

x1 Critical

x1 Major

x4 Minor

x4 Major

x2 Major
x5 Minor

x5 Critical

x1 Major

x2 Major

x2 Critical

x2 Warning

x2 Major
Meaning Effect

A fault (or faults) has (have) occurred in a unit (or The effect of the fault on the functioning of the
units) belonging to the sector indicated in the network element depends
alarm. Check the reason for the fault from the on the fault description. For more information,
supplementary text field of the alarm. see base station fault
descriptions in BTS System Libraries.

A fault (or faults) has (have) occurred in the RAT The effect of the fault on the functioning of the
base station. Check the reason for the fault from network element depends
the supplementary text field of the alarm. on the fault description. For more information,
see base station fault
A fault (or faults) has (have) occurred in the 5G descriptions
The effect of in BTS
the System
fault on theLibraries.
functioning of the
Node B. Check the reason for the fault from the network element depends
supplementary text field of the alarm. on the fault description. For more information,
see base station fault
descriptions in 5G System Libraries.

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

This alarm is raised when either no or an No data or clock information is exchanged via
incompatible signal is received on the interface this interface. Possible impact on the connections
referenced in the alarm text. over this interface:

$UNIT indicates the affected module from - voice calls or data connections are aborted and
A dead peer was detected in one of the IPsec Possible effects:
Equipment Management (last element of the cannot be established anymore
associations of the BTS. - no calls are possible
DN). E.g. SMOD-1.
There is no response to the requests sent to the - loss of remote management access to other
$INTERFACE indicates the interface on the - remote management connectivity is lost and
peer, neither during the IKE network elements
module following the labeling on the frontplate of cannot be established anymore
SA setup, the IPsec SA setup, nor during DPD. - IKE SAs and IPsec SAs cannot be established
The
the real alarm HW is or
raised if the BFD state
the corresponding for the in
parameter The communication link between the local and
Note: When IPsec backup tunnel feature is or re-keyed
session
the Management is not AdminDown Model. and, nevertheless, no the remote
- loss peer is defective
of synchronization orinterface
if the the peer is is used
enabled, this alarm is not raised
BFD
E.g. EIF1, packetIF1 is received at the local end during defective. Transport service
as a synchronization source may not be available
due to failures when trying to setup primary IPsec
the detection time. $BFDID indicates the BFD and calls may be dropped.
tunnel in "Secondary_Active_Probing_Primary"
identifier.
With Exampleinterface,
an Ethernet for alarmthe text: "BFD-10
physical down
Ethernet -The
Depending on use link
of the Ethernet
The
state.alarm is raised if the BFD state of the communication between theinterface,
BTS andthe
in
link ingress"
is detectedThe to source
be and destination
down. All other IP
transmission above described impact can occur for the local
session is not AdminDown and the BFD packet the BFD peer is defective.Transport service may
addresses
alarms will be this displayed in alarm diagnostic
from therelated far endtocontains signaltheare suppressed.
diagnostic code = SBTS and/or other (S)BTS elements
not be available and calls may be dropped.if they are
info field. Source IP addr $BFDSCRIPADDR chained via the Ethernet interface.
'Control Detection Time Expired' and no BFD
Dest
Probable IP addr $BFDDESTIPADDR
causes for isEthernet
down Ingress alarm present.interfaces:
Example for
During
-alarm the IP address
a cable/fiber is cut or configuration
there the BTS The remote peer to come online with the same IP
text: "BFD-10 down in is no cable/fiber
egress" The source
tests
connected the direct
to theattached
interface network, whether address on the same subnet as a local peer
and destination IP addresses will be displayed in
another
-alarm already configured
the electrical/optical signal node on the network would just disable their network interface and
diagnostic info field asisbelow:
excessively
"Source IP
already
attenuated uses the same IPv6 addresses on their give an error until the situation is resolved by the
addr $BFDSCRIPADDR, Dest IP addr
network
-The portIPatisinterfaces.
thealarm the connected The DADfarIKE
end(Duplicate
node is administrator.
$BFDDESTIPADDR" raised when the authentication The IKE SA cannot be established.
address
switched detection)
off detects those duplicated IPv6 This allows the local peer to continue functioning
credentials provided by the peer
addresses
-isthe and prohibits thecapabilities
operation ofwith thisauto- without disruption, but completely breaks IP base
notadvertised
valid. technology
IPv6
negotiation address of in
boththedevices
BTS. The Alarm
at the contains
Ethernet linkthe
do communications for the connected network.
corresponding
not match IPv6 address and the interface on
The
- thealarm
which Ethernet is raised,
the address was
technology if IKE parameters
configured.
at both devicesForareeachnot
at DAD
the IKE SA cannot be established and subsequently
matching
event
Ethernet withisthe
a separate
link peermanually
reporting
forced proposal.
shall and
beIt cannothappen
indicated. no IPsec SAs can be established.
due
compatible to following two failures
-->
- theWhen remote thepeer
BTSofsends or receives
an Ethernet link is a failure
not auto-
notification
negotiation as response
capable or hasto an IKE_SA_INIT
auto-negotiation
This alarm is raised when the BTS sends or The related IPsec SA can't be established and
request
function message.by The failure notifications
receives disabled configuration
following notification as response to an used.
includes:
IKE_AUTH or CREATE_CHILD_SA request
-Probable
NO_PROPOSAL_CHOSEN
message.causes for PDH interfaces:
- INVALID_SYNTAX
a cable is notifications
cut or there is no cable
The failure includes theconnected
following: to
This
-the alarm indicatesVERSION
INVALID_MAJOR
interface that the maximum threshold The precise effect of this alarm cannot be
- NO_PROPOSAL_CHOSEN
value
- INVALID (based on
_IKE_SPI the threshold rule defined for the determined since the nature of the alarm
- the electrical
TS_UNACCEPTABLE signal is excessively attenuated
measurement
- INVALID_MESSAGE_ID
the port at theresult)
connected has been far detected.
end node The
is depends on the measurement(s) involved in the
- INVALID_SYNTAX
severity
-switched ofoffthis alarm depends upon the or
UNSUPPORTED_CRITICAL_PAYLOAD measurement result.
- INVALID_MAJOR VERSION
measurement(s)
FAILED_CP_REQUIRED
-Thetransmit and that reach(es)
receive cables the defined
- INVALIDavailable disk
_IKE_SPI space on aare mixed
partition isupsmaller There is a risk that some data cannot be written
threshold
--> When value.
the BTS sends or receives a failurecan
than the minimum
- INVALID_MESSAGE_ID requirement. The partition on the disk.
notification
Examples
be filled upfor as response
byalarm
crashing to an IKE_AUTH
text:programs request
(or by large log
- UNSUPPORTED_CRITICAL_PAYLOAD
message.The
Ethernet:
files "LOS failure
on notifications
SMOD-1,
if the rotation of logs is malfunctioning)EIF2" include:
- SINGLE_PAIR_REQUIRED or
-resulting
INVALID_SYNTAX
in large core files.
FAILED_CP_REQUIRED
The fault detector inVERSION the operating system has The state of the named device cannot be
- INVALID_MAJOR
failed
- INVALID to capture
_IKE_SPI the statistics of the usage of a discovered, which may indicate that there are
given resource.
- INVALID_MESSAGE_ID some fundamental problems with it.
- UNSUPPORTED_CRITICAL_PAYLOAD
The node cannot receive or transmit data over Ethernet link is down, the interface cannot
the network. receive or transmit data and lost connectivity to
network.

The local clock is not accurately synchronized When this alarm is raised, the system time is not
with the Network Time Protocol (NTP) time in sync with the NTP server and is noticeable by
sources. This alarm is raised because the time the operator. The system cannot be used for
difference between local and NTP sources is distributed applications that require correctly
longer than one second. synchronized network time (such as IPSEC-VPN
The ntpd application running on the system is not Lost connectivity might lead to not synchronized
establishment). It makes system logs unreliable.
able to sync time with the forwarder/peer ntpd system clock and incorrect system local time.
Incorrect time stamps are done by the system
because:
leading to security vulnerabilities, wrong auditing,
1. The connection is lost with the forwarder.
accounting, authentication and incorrect
2. The ntpd application is rejecting the forwarder
This alarm is raised when the named managed The node isofunavailable
functioning the networkand
fileall the services
system (NFS). An
response because the forwarder is considered to
object has failed. The managed object is a node. running
inaccurateon system
it are disabled.
clock also affects the operator
be not suitable for synchronization at that
Node's system software or the operating system billing system.
moment.
has failed, or the node has been manually
restarted.
This
Suchalarm is raised
forwarders when
would be adeclared
node switchover
as is If there are 2N redundant services with an active
Possible reasons for this alarm are:
initiated by the distributed high availability
unreachable. role in a node and the node is restarted, all the
1. host side action (VM shutdown)
services (DHA). This might be a recovery action active 2N services in the node shall switch over
2. reboot on VM
for a node recovery failure, a result of an to the co-operation node. The services provided
3. unstable network
administrative operation such as shutdown of the by the node indicated in the managed object of
This alarm is raised when the availability status of This alarm indicates that a node is faulty and out
active node, or a result of an active critical this alarm are currently unavailable. The normal
a specific node is changed of use, and the system cannot recover it
service failure. The new active recovery node is operation resumes once the switchover operation
to "FAILED". When the alarm is raised, it automatically.
now starting and being activated. is successful.
indicates that the node is faulty and the system
The following actions can lead to raise this alarm:
cannot recover it automatically. For example, the
This alarm active
1. Original indicates that
node an operation
failed, is initiated
original standby Effect of the alarm depends on the performed
node cannot start for a long time.
on
node a node. The active.
becomes operation includes: restart, operation:
graceful
2. Originallock, forcednode
standby lock becomes
and unlock.active after - restart/graceful-lock/forced-lock/unlock: the
restart. node will be restarted soon
- graceful-lock/forced-lock: the node will not
This alarm indicates that a resource supervised The alarm is a general notification indicating that
provide services excluding ssh server and some
by a specific supervision mechanism has failed. one resource supervised by a specific
troubleshooting services
This is a generic alarm that is used to report supervision mechanism has failed.
- unlock: the node will work normally after it starts
certain essential service failures observed by The impact on the system depends on a service
up.
supported supervision mechanisms. that has failed. You can check its impact in
product documentation or by local customer
Currently supported supervision mechanisms support.
are:
CC&S service supervision:
CC&S provides 2 types of supervision
mechanisms that can result in this alarm being
raised:
- CC&S AaPro service EU(thread) supervision
- CC&S AaStartup service process supervision

Notes: "CC&S" is the abbreviation of "Common

Computing & Support". CC&S provides
commonly used platform level service for Nokia
BTS application software.
Identifying Additional Information Fields Additional Information Fields

1. HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
2. Path(URI) of the impacted hardware unit, when the
impacted unit is FSM, FSP, FBB, FR, FAN, AntennaLine,
FYG, or SFP.

1. HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
2. Path(URI) of the impacted hardware unit, when the
impacted unit is FSM, FSP, FBB, FR, FAN, AntennaLine,
FYG, or SFP.

1. HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
2. Path(URI) of the impacted hardware unit, when the
impacted unit is FSM, FSP, FBB, FR, FAN, AntennaLine,
FYG, or SFP.

1. HW Inventory Id (RDN) and Serial Number of the

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

1. HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
2. Path(URI) of the impacted hardware unit, when the
impacted unit is FSM, FSP, FBB, FR, FAN, AntennaLine,
FYG, or SFP.

(i) HW Inventory Id (RDN) and Serial Number of the

impacted hardware unit
(ii) Path of the impacted hardware unit.

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

Path of the hardware unit. Serial Number of the hardware unit.

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

Serial Number of the impacted hardware unit Alarm is used if manual scaling functionality
was enabled in VNF

Alarm serves as a container for the scaling

instructions. AdditionalText1 shall include the
Configured VM list
parameters in the following format:
Effectively started VM list
Missing VM list
"vnfInstanceId:<vnfInstanceId>;
type:<IN/OUT>;
aspectId:<CPUE/UPUE>;
numberOfSteps:1;
additionalParamsVnfcIdList:<empty>;"
VNFC having no instance

1. The metric name for which the alarm is raised. 2. Reason and information for the alarm.
The metric name is a combination of the omes id and the This field contains the information about
attribute number. minimum threshold reached. It is encoded in
For example: "m2002c001" the following format:
In the above example, m2002 is the omes id and c001 is "<threshold_pct>:<raise_duration>:<clearing_th
1. Mountpoint 2. Mountpoint Information
the attribute number. reshold_pct>:<clear_duration>"
This field shows the upper threshold
For example: "80%:300sec:70%:30sec"
percentage crossed by mountpoint.
The interpretation of this information: This
When surpassed, the alarm will be raised.
alarm is raised because metric indicated in the
The format of the field is "Filesystem <device
1. Failed subsystem 1st additional information field has surpassed
name> (<type of filesystem>) mounted on
2. Failed resource percentage <threshold_pct> for
<mount point> uses > <upper threshold value
Where the values are as: <raise_duration> seconds; the alarm will be
percentage> of the space" e.g. "Filesystem
CPU:Index of the processor cleared automatically when this metric
rootfs (rootfs) mounted on / uses > 90.0% of
FILESYSTEM: Name of the mount point indicated in the 1st additional information field
the space".
has been below percentage
<clearing_threshold_pct> for <clear_duration>
seconds.
Ethernet interface

1. General Information
Possible values:
A) sysPeer not chosen
NTP is unable to select a server.
B) The sync time difference is beyond the
1. Reachable peers
allowed offset
2. Unreachable peers
The time difference between NTP server and
NTP client is greater than the allowed offset.
C) ntpq polling is not successful
Details for fault:of NTP time sync has failed.
Monitoring
1.D)
Fault
NTP type
is syncing
Possible
NTP isvalues:
syncing to this server.
- node_restart
- supervision_failure
1. The managed object name of the new active node.
2. Name of the node that raised this alarm

1. Failure reason
Possible values:
"node_startup_timeout"

2. Name of the node that observed the fault

1. Operation type performed on the node
Possible values are:
"restart"
"graceful-lock"
"forced-lock"
1. Supervised resource identifier. 3. Supervision mechanism specific details.
"unlock"
This field indicates type of the supervised resource (e.g. a This field contains supervision mechanism
process) as well as its identifier. specific information on the failure, and its
Format example: content depends on the supervision
"process:<process_identification_string>". mechanism.
In case of CC&S supervision the following
2. The supervision mechanism that identified the failure. information is indicated in this field:
Possible values in case of CC&S supervision: - Recovery action triggered:
- "CC&S_thread_supervision" resourceRestart/CC&Srestart/VMrestart.
- "CC&S_process_supervision" Example format of the data:
"recovery:resourceRestart"
Instructions

FAULT NAME
No connection to unit

FAULT ID
10 : EFaultId_NoConnectionToUnitAl

MEANING
A module required in commissioned 5G BTS configuration has not been
FAULT NAME
detected or connection to a module belonging to the 5G BTS configuration
Unit (module) temperature is high
FAULT
has been NAME lost.
Phase error exceeds the interference limit
FAULT ID
INSTRUCTIONS
1936 : EFaultId_FrTempHigh
FAULT
To clearID this fault, perform the following steps:
4452 : EFaultId_PhaseErrorExceedsTheInterferenceLimitAl
MEANING
1.
FAULT MakeID sure that the module is properly connected. Check the alarming
Validated module temperature exceeds or is equal to the predefined
MEANING
module.
6293 : EFaultId_EnbConfigurationFailedAl
maximum value allowed.
This
2. Check fault the indicates that the absolute phase error of the BTS exceeds the
fault history.
limit
MEANING
INSTRUCTIONS
FAULT NAME
of
The 1.5BTS us. This can occur
configuration when:
failed in the
Take
Phase the errorfollowingexceeds stepsthe to clear
interference theC-Plane.
fault:
limit
1) The
INSTRUCTIONS absolute value of measured/estimated phase error of the BTS has
1. Check
FAULT ID if the ambient temperature/environmental conditions are within
exceeded
FAULT
Investigate NAME the limit
the fault of 1.5
rootradious,
cause. Lock/Unlock RAP.
the
4452 design limits for the
: EFaultId_PhaseErrorExceedsTheInterferenceLimitAl module. When the ambient
Unit
MEANING (antenna submodule) temperature is high
temperature/environmental conditions exceed the limits, the alarm is
OR
A corrupted SW
expected
MEANING and nofile in theactions
further FLASH areis needed.
detected. The unit cannot perform a
FAULT
complete IDstart-up.
This
2)
2906 The faultBTS indicates
has lostthat
: EFaultId_FrAmTempHighAl the absolute
all phase phase error
sync reference of the but
sources, BTSdoes
exceeds the
not have
2. Check if airflow is free of foreign objects. Make sure the minimum
limit
sufficient
INSTRUCTIONS
FAULT NAMEhistory data for holdover.
thermal
FAULT
of 1.5 us. clearances
NAME This can occur guidelineswhen:are followed. Remove any objects that
OR
MEANING
Update
RAP or the
VM SW in the
unavailable the airflow
BTS.for Cloud
might
Radio be blocking andRF mount the module according to
3)
ValidatedTheModule BTS is does
antenna not support
synchronized
submodule sharing
bytemperature
reference which has than
is higher capability to internal
the predefined
instructions
1) The absolute and recommendations.
value of measured/estimated phase error of error
the BTS has
holdover
maximum
FAULT ID (Sync
allowed Hub Master/GNSS)
value. which reports the phase of the
FAULT
exceeded
provided IDsync the limitsignal. of 1.5The us,
absolute value of estimated total phase error in
4350
3. Check
4515 :: EFaultID_RapOrVmUnavailableAl
if excessive sunlight is causing the unit to overheat. Install the
EFaultId_RadioModuleDoesNotSupportRfSharingAl
the "slave"
INSTRUCTIONS
FAULT NAME side exceeds the limit of 1.5 us or source reports that its
sunshield
OR following the mounting instructions and recommendations.
holdover
Take
Failure
FAULT
MEANING the in has
following
NAME expired.
troubleshooting steps todata clear the fault:
collection
MEANING
RF
In Module
the configuring failed
Detected
2) Thecase
INSTRUCTIONS
1. Check BTS ifRF
Source
module
has
the lost=all
ambient
5GRAU
doesphase not(ASIx
support
sync ): commisioned
reference
temperature/environmental sources, RFbutsharing
does type.
not have
FAULT
5GRAU
sufficient
ID
is not
history available
data for for 5G
holdover. BTS because of the conditions
5GRAU failure, are within
If
the
4514
FAULT
5GRAU GPSdesign is configured
limits for as
the a reference
antenna
: EFaultId_FailureInTroubleshootingDataCollectionAl
ID clock,
sumodule. perform
When the
the following:
ambient
CPRI
OR
1. Check RFelement
modules
the
temperature/environmental
reset
GPS receiver
or Frontsharing:
in NR-LTE Haul breakdown.
installation.
conditions exceed RM HWthe version
limits,should
the alarm be >= is Rel
1900
FAULT : EFaultId_FrConfiguringFailed
NAME
5.1
3)
2.
expected
MEANING (NAKHA)
The
Check BTS the
and is
GPS synchronized
receiver
no further by
status.
actions reference
are needed. which has capability to internal
In
SFP
FAULT
holdovertheHW case Failure
NAME
(Sync Source on=unit
Hub 5GRAC:$U, interface
Master/GNSS) $IF reports the phase error of the
which
3.
This
MEANING
VNFC Check
fault
crashedthe
indicatesconnection
and that
is nota between the
user-configurable
available. GPS receiver
BTS faultand hasASIx.
triggered an
Cooling
INSTRUCTIONS
provided fan
sync is over
signal. speeding
The absolute value of estimated total phase
2.
internal
The
FAULT
Check
Radio if
snapshot
ID steps
airflow
module is
and free of
snapshot
configuration foreign objects.
collection
has failed hasMake sure
failed
because the
(partially
of a hardwareor error
minimum or
in
Follow
the
If
thermal
FAULT the"slave"
completely). TOP the side
signal
clearances
NAME below
exceeds
is to
configured
guidelines resolve
the limit
as
are the
of
a 1.5fault:
us
reference
followed. or source
clock,
Remove reports
perform
any that
the
objects its
following:
that
software
INSTRUCTIONS
61079 : ID
FAULT fault.HW Failure
SFP
holdover
1.
might Check be has
theSource
blocking
EFaultId_F1SctpEndpointAl expired.
connectionthe to the
airflow andTOP server
mount the module according to
In
4080
1. the
In :
casecase
EFaultId_FanOverSpeedAl
of NR-LTE = 5GRAU
sharing, (ASIx try to or RTM):
connect Radio Unit HW version >=
instructions
INSTRUCTIONS
1. Check and recommendations.
the Front Haul connection (between 5G BTS and RAU).
MEANING
Rel 5.1
INSTRUCTIONS (NAHKA)
FAULT
When
Take the IDfollowing
snapshot is triggered,
actions but
toreported
clear notthecollected, checkfault
the condition
reason in and the
2.
The
MEANING
2. Check
In optical
case RAU HW.
transceiver has a fault:
transmission
If
3.
4445
Alarm: GPS
Check ifNR-LTE
is configured
excessive
: EFaultId_F1SctpEndpointAl sharing
assunlight is not
a reference intended,
is causingclock, RF
perform
the unitsharing
tothe shouldInstall
following:
overheat. be disabled
the
has
Fan
in
1. SCFdisabled
is running
Check the the
GPS laser
faster transmitter.
than
receiver required.
installation.
sunshield
- New
1.
In Confirm
the snapshot
case following
the can
ifSource the
=be
existing mounting
RAC:blocked
configuration instructions
if thereisiswithin and
an ongoing recommendations.
snapshotRAP
the configured in process
HW
3.
2.
FAULT
-MEANINGReplace
Check
Too many NAMEthe the GPS alarming
snapshots: receiver unitstatus.
limit withnumber
the the unitofplanned
snapshots in 5Gper BTS
Fault planned
ID (+CU HW or
capabilities.
Check
Probable
INSTRUCTIONS servercauses: HW.
configuration
3.
+DU) Check
EFaultId_F1SctpSetupAl
The transport
to 5 theper (BTS
connection
path
24 profile).
(SCTP)
hours between
for the
connection GPS receiver
between and
gNB-CU ASIx.and gNB-DU
-2.The Check
Replace optical thefan.
the BTS connections
transceiver and commissioning settings.
is defective.
is broken.
-3.Snapshot
Reset the This
taken
RAP. mighttoo be often:because
set theofminimum
an unplugged cable between
time interval per Faultthem. ID
If
(+CUthe TOP
FAULT
There orisID nosignal
+DU) transport is configured
between path as atoreference
available
snapshots to15continue
minutes clock, perform
operation on the
the following:
faulty
4.
Note:Block/Unblock
Thethe unitconnectionthe
and interfaceBTS. variables ($U,$IF) will be replaced by
1.
4447
FAULTCheck
connection : EFaultId_F1SctpSetupAl
NAME to collection
the TOP server
-5.Other
If the
appropriate HWbetween
reason in snapshot
configuration
hardware.
gNB-CU and
is confirmed,
Example:
gNB-DU.
process
unit-FSM, it means (collect
interface OAM logs
this EIF1.
problem to resolve
is caused by
Unknown
reason)
the
FAULT 5G BTS NAME HW SW.resource
Check the other active alarms.
FAULT
MEANING
INSTRUCTIONS
When NAME is collected, lack of snapshot data can be read from the
snapshot
No
FAULT
RF connection
INSTRUCTIONS
sharing NAME between primary and BTS extension system module
The
FAULTPerform
Note:
Alarm. ID mode
transport the conflict
path (SCTP)
steps belowfor connection
in the listedbetweenorder until gNB-CU
the alarmand gNB-DU
4506 : EFaultId_NgSctpSetupAl

MEANING
The transport path (SCTP) for the connection to the AMF has failed to be
established.
FAULT NAME This might be caused by an unplugged cable to the eNB.
There
Phase error exceeds path
is no transport available tolimit
the interference continue the operation on the faulty
connection with the eNB.
FAULT ID
INSTRUCTIONS
4452 : EFaultId_PhaseErrorExceedsTheInterferenceLimitAl
5.
Note: ThePerformcable between the steps thebelow GPS in receiver
the listed andorder the BTS until might
the alarm be faulty.
Check
disappears: the situation and change the cable, if needed.
MEANING
6. There might be a HW fault in the GPS receiver. Check the operation
This fault indicates that the absolute phase error of the BTS exceeds the
and
1. change
Check thethe GPS module,
connection with the if needed.
AMF.
limit
7. There might be a HW fault in the BTS System Module. Check the
FAULT
of 1.5 us. NAME This can occur when:
operation
2. Check ifand thechangeAMF is the System Module, if needed.
operational.
Automatic BTS Operator Certificate retrieval unsuccessful
1) The absolute value of measured/estimated phase error of the BTS has
3.
FAULT
exceeded Check IDifthe thelimit speed of 1.5 andus, duplex setting of the NG port is consistent with
the switch
61510 : NO_CERTIFICATE port that is connected directly to the gNB (for example, they are
FAULT
both NAME
"Autodetect" or both "1000 Mbit/s Full duplex").
OR
Unit (antenna
FAULT NAMEsubmodule) SW download failure
MEANING
Master unit has lost connection to the slave unit
A
2) requested
The BTS certificate could not be retrieved from the certificate authority
FAULT ID has lost all phase sync reference sources, but does not have
(CA).
sufficient history data for holdover.
2913
FAULT : EFaultId_FrAmSwDownloadFailAl
ID
FAULT
A
OR requested NAME certificate could not be renewed from the certificate authority
4019
FAULT
Radio : EFaultId_KeepAliveStatusErrorAl
NAME
(CA).
3)
MEANING TheDiagnostic
BTS is synchronized Files collected by reference which has capability to internal
EFaultId_XnSctpSetupAl
holdover (Sync Hub Master/GNSS) which reports the phase error of the
RF SW detected that FPGA software
MEANING downloading to antenna submodule
FAULT
A
provided requested IDsynccertificate
signal. The could not bevalue
absolute retrieved of as the number
estimated total of certificates
phase error in
failed.
Connection
FAULT IDfrom to SW entity has been lost.
4527
received
the : EFaultId_RadioTechnicalLogUploadRecommendedAl
"slave" side repository
exceeds server
the limit (RA)
of or
1.5 certificate
us or source authority
reports (CA)
that are
its more
FAULT
4508 NAME
: EFaultId_XnSctpSetupAl
than
holdover expected. has expired.
No connection between primary and BTS extension system module
INSTRUCTIONS
MEANING
1.
This
MEANING Resetfault the
is most RF HW likely unit. the result of acrash BTS hardware problem or a
After
A an RU
requested
INSTRUCTIONS crash,
certificate RU has could collected
not be stored logs.
in the remaining storage
FAULT
reference
The ID source
transport path that(SCTP) is being for followed
the connection by the betweenBTS that local is in a gNBfaulted
and peer
available
If
4352 GPS on the BTS.asOperator
isproblem
configured
: EFaultId_NoConnectionToBtsExtensionUnitAla reference cleanup clock, (e.g.
performvia site themanager
following: or NetAct)
2.
condition,
gNB/ng
FAULT If the eNB
NAME therefore
has continues
failedproducingto be after an step
established. 1
inaccurate has been
This reference.
mightperformed,
be Perform
caused replace
the
by anthe
INSTRUCTIONS
of
1. old,
Check unusedthe GPS trustreceiver
chains may be required.
installation.
RF
following
unplugged
All HW
RAPs unit.
steps
Out cable to isolate
between
Of Service thethem. cause There of theis fault:
no transport path available to
Collect
2. Check technical
the GPS logs from the
receiver status. BTS to clear the alarm raised by this fault.
MEANING
continue the operation on the faulty connection between local gNB and
Internal
Note: For logs RAC, collected bybetween
this process can only be analyzed by Nokia
3.
Connection
1.
peer
Check
CheckgNB.
the
thetoother a this
connection
secondaryfault
alarms ofunit
is raised
thethat
onlyGPS
the
BTSbelongs
for the automated
receiver
and acttoaccordingly.the BTS and Dual operation
ASIx. ASIx
FAULT
R&D.
triggered IDby system, for e.g., automatic CMP key update (KUR). But not
configuration has been lost.
4411
for
If thetheTOP: EFaultId_AllRapsOutOfServiceAl
manual signal operations,
is configured for e.g.,as amanual reference CMP clock, IR or CMP KUR
perform triggered
the following:
FAULT
2. NAME
If there are no other synchronization-related alarms active, start the fast
INSTRUCTIONS
Additionally:
by
1. operator.
Check the connection
EFaultId_NodebFiberLengthDeploymentExceededAl to the TOP server
INSTRUCTIONS
FAULT
tuning NAME
with
Note:
MEANING
- Check theBTS
Perform alarm the Element
steps below
history Manager.
to confirm in thethe listed order until
frequency the alarm
of fault 4527 in a
Note: Perform
EFaultId_RapFileTransferFailureAl
disappears: the steps in the listed order until the fault is resolved.
This
specific
INSTRUCTIONS fault eNB.indicates that all of the RAPs (RAU&RU) under the same RAC
FAULT
1.
3. ResetIDthe BTS. site. Run fastfor tuning
have
-1.
4414 Check
Check failed.thethe alarm
CMP history
configuration.
: EFaultId_NodebFiberLengthDeploymentExceededAl otheragain. alarms in the same eNB that might be
2.
FAULT
1. Check
Check ID the
the connectivity:
connection with
This
Note:
related,
2. Checkfault
this needs
fault
especially
for CA to
isserver be addressed
raised
alarms only with inthe
reach-ability. peer
by manual
a multi-RAP
Radio gNB/ng
alarms system.eNB.
investigation from service
AirScale:
4451
4.
provider. Check : Ensure that
EFaultId_RapFileTransferFailureAl
the reference the module
signal accuracyis properly by connected
measuring it withto the a rack.
frequency
3.
FAULT
MEANING
3. If none
Check NAMEtheof the
SW above
version work,on contact
Secondary CA administrator/Nokia
core if it is the same service
as Primary
counter
2.
FAULT Check
INSTRUCTIONS
If an NodeB
alarm (note:
NAMEif the
with requires
peer
fault gNB/ng a
4527mastergood eNB
frequentlytimebase
is for
operational.
occurs the counter).
in theLength same The
eNB, reference
alarms
personnel
Difference
The
core.
MEANING
signal can
between
behas found detected BTS
from that
the theclock
Sync deployed
Out
and reference
interface Fiber of the
frequency
Flexi between
System the with
EFaultId_RuFiberLengthDifferentialExceededAl
1)
the RAPsame having
faults OFFLINE
mentioned asaboveavailability are status:inCheck
present the RAPeNB,
same connections.
or
RAU
4.
File
Module,
3. Check & RU
Replace
transfer the has
the
if the to RAP
requiredexceeded
faulty
speed and the
unit.
failure.
accuracy duplex supported
is +/-0.015ppm.
setting distance
of the If the
Xn by
portthe
reference
is software. Ifthe
accuracy
consistent this
with
eNB
FAULT
FAULT
distance performance
ID
NAME
isrun exceeded, is degraded,
the IfRU then
cannot collect
function a snapshot
and this and
fault open
occurs. a case
Thisare
is
the
FAULT
2) correct,
switch IDR&D port fast
that tuning.
is connected the reference
directly toaccuracy
the gNB is not
(for correct
example, the
they
for
9 : In
Scale-out
applies
case
Nokia RAPlog
EFaultId_DacWordChangeAl
recommended Reset analysis.needed fault is active and RAP status is not offline:
INSTRUCTIONS
cause
both
RAP "Autodetect"
4415: oftothe Cloud faultBTS is
orthe and
both
EFaultId_RuFiberLengthDifferentialExceededAl
reset
5G BTS.
reference
"1000 source
Mbit/s Fullthe BTS is tuning to.
duplex").
1) Check
Troubleshoot the link
the between
external VNF and RAP. network to find the root cause.
synchronization
Each
FAULT
MEANING
FAULT
INSTRUCTIONS RU IDcrash
NAME are reported with own 4527 fault
2)
Other
MEANING
3) Manually
In BTSs
case RAPreset
withReset thesame
the RAP
does tonot
alarm triggercanSW
recover: provide update
Site to the
further
reset RAP.
information about the
CRL
The
4460
To Update
reference
solve Failure
frequency
: EFaultId_ScaleOutRequiredAl
this problem, the that the
technician BTSshould master clock receives
inspect the optic has
fiber changed
location
FAULT
In aabout of
NAME
configuration the root cause.
where two opticequals fibers the are change
deployed to a RU from a
by
deployment 200ppb or
of the accuracyRU more unit (which
inisquestion. Thisrunning
fault occurs magnitude whendoes of
a RU 204 is
5.
5G
RAU,
4) If
In the
BTS the
case reference
incomplete
maximum
Site reset VM
does initialization
separation not correct
between
recover and
RAPs:those two
Replace fast
fibers tuning
the isneeded
1 km (1,000
RAP not
FAULT
DAC
MEANING
configured steps ID or
with more (with
a system module. 12bit DAC)) during the measurement period,
help,
FAULT
meters, replace
NAME the
HW.
61074
compared
Need
fiber : 3,280.84
for
optic CRL to the
Scale-out
cable Update feet).
BTS
between
If this distance
is failure
master
detected the RAU clock and is exceeded, the RU cannot
frequency.
RU that physically exceeds the
E1
FAULT
function Setup IDand
NAME Failure this faultafter isretries
raised. This applies to Cloud BTS and 5G BTS.
maximum
4472 length supported.
: EFaultId_EnbIncompleteVmInitializationAl The maximum length supported will depend
Two
Remote fibers node are deployed
does from a NRsingle modem board.
MEANING
The
INSTRUCTIONS
on the
FAULT
cause 5GID
of the
release innot
alarm support
can
question be: RAN
(and changes/increases Container Extension
with different Header of
GTP-U
This
1.
For
releases).The fault
this is
reference
alarm raisedto be if
frequencythe
cleared, BTS has
itcannotchanged
requires
The physical connections and physical deployment should update a the
because
manual Certificate
of a
intervention fault Revocation
in the an beList
from
4496
MEANING
INSTRUCTIONS
(CRL).
transmission : EFaultId_E1SetupRetryFailGuardTmrAl
The failure
network reasons include
synchronization the following:
(which in turn is caused by an can
operator.
checked
FAULT to see thatand
NAME these lengths are not exceeded. Theand technician
Timeout
To
FAULT
-equipment
Thesolve LDAP IDhappened
this problem,
binding
fault or a fails.the
setting cardinality
technician
error). of configured
Note should that inspect
if the Cplane the optic
network Uplane
fiber VM
synchronization
The
then
Toggling:
MEANING operator
reset<Fault theshould
NodeBname> check
andcompletely
thethesoftware
current resources will automatically at CBAM UI while to
re-compute
instances
deployments
7900 Theif :LDAP
-malfunction have of nottheforbeen
RU unit time,
EFaultId_NrRanContainerExtensionNotSupportedAl
search
lasts isascale-out
empty
long in(no question.
CRL
the metfound),
alarm during
This istypeor the
fault the
cancelled start-up
occurs
LDAP whenwhen phase.
search
thea RU is
contains
BTS
scaling,
see
This the
fault and fiber perform
indicates lengths that are
the notE1AP: on
within aE1 specific
theSetup acceptable
procedure of VNFC.
differential
initiated range.
by gNB-
configured
more
frequency than reaches with
one entry. two fiber optic cables to
the faulty reference synchronization. The alarm one modem card. The differential
can
FAULT
CU-UP IDthese
fails after retries upon non response from gNB-CU-CP.
-INSTRUCTIONS
between
MEANING
also
AlarmThebe CRL
is activated
clearedsignature fiber
if the
for
optic
validation
CPUE faultycables
if the
must
fails.
reference
following
not exceed
synchronization 1000 m. The physical
criteria is met is corrected and
4026
1)
This Check
connections :
faultEFaultId_TogglingAl
ifisfile
theand
raised heatphysical
whenfile thedefinitions
deployment
remote GTP-Uconfigured
should
tunnel during
be checked
endpoint VNF instantiation
(into see
non- that are
-there
o The CRL
is, again, exceeds
a difference
CPU Utilization of <CPUE Scale-out Threshold Instances> BTS
of 0.2 storage
ppm orlimit.
more. The alarm is cancelled
drops below
INSTRUCTIONS
correct
these
standalone
-whenever
The lengths
BTS call:are
certificate
the not isexceeded.
MeNB)
difference signals
part
becomes of thetoTheSgNB
CRL.
less technician
that
than it
0.2 can not
does
ppm. thensupport reset the "NR NodeB
RAN
< MRBTS/MNL/MNLENT/SCALADM
MEANING
If fault / cpueReallocThresholdCpu>
2)
and Maketherecovery
Container" sure
softwareGTP-U that failsthere
will check arethe
automatically
extension enough E1 SCTP
header. HW
re-compute
It is state
resources.
required and
to see restart
for ifflowthethe gNB.
fiber
control lengths
between
Alarm
The BTS is cleared
Fault,the for UPUE fault
whichever if thename following criteria is in
is mentioned met the Fault name field,
are not within acceptable differential range.
FAULT NAME
5G BTS failed VM initialization

configuration

5GC000548: VNF CU capacity and

configuration
Clearing Time to Live Restriction status

1 Automatic 0 No

1 Automatic 0 No
1 Automatic 0 No

1 Automatic 0 No

1 Automatic 0 Yes

1 Automatic 0 No

0 Manual 0 No

1 Automatic 0 No

1 Automatic 0 No
1 Automatic 0 No

1 Automatic 0 No

1 Automatic 0 No
1 Automatic 0 No

1 Automatic 0 No

1 Automatic 15000 No

1 Automatic 0 No
Changes between issues 02 Fault ID
DRAFT and 02A

New 10

Changed 16

New 23

New 28

New 29
New 30

New 94

1806

1811

New 1815

1817

1818

Changed 1819

New 1850

Changed 1898

1900
1901

New 1907

New 1911

1928

New 1932

New 1936

New 1937

New 1981

Changed 2056

New 2906

New 2911

New 2912
New 2913

New 2914

New 4001

Changed 4011

Changed 4019

4026

Changed 4073

4077

4078

4079

4080

4082
4083

4085

Changed 4122

Changed 4123

Changed 4124

4125

Changed 4126

4145

4210

4266

4267

4268
4269

New 4296

Changed 4298

4323

4352

4385

4414

4415

4441

4444

Removed 4445

4446
Removed 4447

4452

New 4478

New 4479

4490

4494

4495

4505

4506

4507

4508

4514
Changed 4515

4516

4517

Changed 4520

4523

4524

New 4527

New 4544

New 4545

6203

6293

New 6918
New 7900

New 8000

Changed 61029

61030

Changed 61050

61074

Changed 61079

61510

New 61616

61618

Changed 61631

61632
61642

61644

61645

61646
Fault Name Used in Product

Unit temperature is high 5G BTS

Difference between BTS master clock and 5G BTS

reference frequency

No connection to unit 5G BTS

Unit synchronization failed 5G BTS

Incompatible SW version detected 5G BTS

Obsolete SW version detected 5G BTS

BTS time not corrected 5G BTS

Error in file server during file download type 5G BTS

File corrupted in SW download 5G BTS

BTS SW download or activation failed 5G BTS

Unknown HW resource 5G BTS

Unit not supported by running SW 5G BTS

Communication failure 5G BTS

Baseband bus configuration was rejected 5G BTS

Not able to synchronize a baseband bus 5G BTS

Oven oscillator heating failure 5G BTS

BTS master clock tuning failure 5G BTS

Oven oscillator clock missing 5G BTS

SW corrupted 5G BTS

PPS reference missing 5G BTS

RF Module configuring failed 5G BTS

RF Module critical file not found 5G BTS

TX out of order 5G BTS

RX out of order 5G BTS

FPGA SW update failed 5G BTS

No module fan detected 5G BTS

Unit (module) temperature is high 5G BTS

Unit (module) dangerously overheating 5G BTS

FR module reset requested 5G BTS

Firmware SW mismatch 5G BTS

Unit (antenna submodule) temperature is high 5G BTS

Unit (antenna submodule) dangerously 5G BTS

overheating

Unit (antenna submodule) power good interrupt 5G BTS

Unit (antenna submodule) SW download failure 5G BTS

Unit (antenna submodule) PLL unlocked 5G BTS

BTS reset required 5G BTS

GPS Receiver alarm: control interface not 5G BTS

available

Master unit has lost connection to the slave 5G BTS

unit

Toggling: <Fault name> 5G BTS

Fan vendor not detected 5G BTS

FSP overheating 5G BTS

Cooling fan broken 5G BTS

Cooling fan speed decreased 5G BTS

Cooling fan is over speeding 5G BTS

SW fallback 5G BTS
SW fallback 5G BTS

SW fallback 5G BTS

GPS receiver alarm: not tracking satellites 5G BTS

GPS receiver alarm: survey in progress 5G BTS

GPS receiver alarm: no stored position 5G BTS

GPS receiver alarm: position questionable 5G BTS

GPS receiver alarm: EEPROM invalid 5G BTS

Validation of signed file failed 5G BTS

External GPS receiver in holdover 5G BTS

Failure in verifying the signature of a signed 5G BTS

software release

Failure in verifying a signed software release 5G BTS

Unsigned software release has been 5G BTS

successfully downloaded
Failure in downloading software due to missing 5G BTS
software signature

Constellation mode not supported 5G BTS

ToP reference missing 5G BTS

ToP configuration mismatch 5G BTS

No connection between primary and BTS 5G BTS

extension system module

PPS reference from backplane missing. 5G BTS

EFaultId_NodebFiberLengthDeploymentExcee 5G BTS
dedAl

EFaultId_RuFiberLengthDifferentialExceededAl 5G BTS

Trust Chain Certificate Installation Failure 5G BTS

Trust Chain Certificate Removal Failure 5G BTS

EFaultId_F1SctpEndpointAl 5G BTS

EFaultId_X2SctpSetupAl 5G BTS
EFaultId_F1SctpSetupAl 5G BTS

Phase error exceeds the interference limit 5G BTS

Antennas assignment not available 5G BTS

Failure detected on assigned antennas 5G BTS

No X2 link available 5G BTS

Supervision failure 5G BTS

gNB configuration update failure 5G BTS

EFaultId_NgSctpEndpointAl 5G BTS

EFaultId_NgSctpSetupAl 5G BTS

EFaultId_XnSctpEndpointAl 5G BTS

EFaultId_XnSctpSetupAl 5G BTS

Failure in troubleshooting data collection 5G BTS

Radio Module does not support RF sharing 5G BTS

RF sharing mode conflict 5G BTS

F1 Cell activation failed due to X2 link 5G BTS

unavailable

Configuration change requiring Site restart 5G BTS

detected

Troubleshooting data available on CU 5G BTS

Troubleshooting data available on External 5G BTS

Server

Radio Diagnostic Files collected 5G BTS

Non approved SFP module on unit $U, 5G BTS

interface $IF

Restricted use SFP module on unit $U, 5G BTS

interface $IF

Transport layer connection failure in X2 5G BTS

interface

5G BTS configuration failed 5G BTS

Non critical SW Component failure 5G BTS

Remote node does not support NR RAN 5G BTS
Container Extension Header of GTP-U

Failure in connection between BTS and 3rd 5G BTS

party tool

LOS on $UNIT, $INTERFACE 5G BTS

Dead Peer Detected 5G BTS

Missing or non-compliant SFP module on unit 5G BTS

$U, interface $IF

CRL Update Failure 5G BTS

SFP HW Failure on unit $U, interface $IF 5G BTS

Automatic BTS Operator Certificate retrieval 5G BTS

unsuccessful

Vendor BTS certificate is about to expire 5G BTS

BTS Trust Anchor due to expire 5G BTS

ToP master service $IP unusable 5G BTS

Dup Addr detected- 5G BTS

$DUPLICATEIPV6ADDRESS
BTS Local OAM user account $A has been 5G BTS
locked

IKE authentication failure 5G BTS

IKE SA failure 5G BTS

IPSec SA failure 5G BTS

Detecting Unit Source

ASIx ASIx
ABIx

ASIx ASIx

ASIx ASIx
ABIx
5GRU

ASIx, ABIx ASIx, ABIx

ASIx 5GRU
ASIx
ABIx

ASIx ASIx

ASIx TIME

ASIx ASIx

ASIx 5GRU
ASIx

ASIx 5GRU
ASIx
ABIx
ASIx 5GRU
ASIx
ABIx

ASIx ABIx
5GRU
AMxx

ASIx ASIx, ABIx, 5GRU

ASIx 5GRU, ASIx, ABIx, RAU

ASIx ABIx

ASIx ABIx
OptIF

ASIx ASIx

ASIx 5GRU

ASIx GNSSE, SYNCHUBBTS

ASIx 5GRU
RU 5GRU

RU 5GRU

RU, RF 5GRU

ASIx ABIx

RU 5GRU

RU 5GRU
RU 5GRU

RU 5GRU

ASIx ASIx, ABIx, RU

ASIx GNSSE

ASIx ASIx, ABIx

RAU RAU, ASIx, ABIx, GNSSE, 5GRU

ASIx FAN

ASIx ABIx

ASIx Fan

ASIx FAN

ASIx Fan

ASIx ASIx
ASIx ASIx

ASIx ASIx

ASIx GNSSE

ASIx ASIx

ASIx GNSSE, SYNCHUBBTS

ASIx ASIx

ASIx ASIx
ASIx ASIx

ASIx GNSSE

ASIx TOP

ASIx (primary unit in Dual ASIx ASIx (secondary unit in Dual ASIx
configuration) configuration)

ASIx (secondary unit in dual core ASIx (secondary unit in dual core configuration)
configuration)

ASIx 5GRU
ABIx

ASIx RAP

RAU NRDU

RAU LTEENB
RAU NRDU

ASIx ASIx

RAU gNB-CU

ASIx ASIx

ASIx, RAU CERTHENT

ASIx SFP

ASIx, RAU CERTHENT

ASIx RAP

ASIx, RAU CERTHENT

ASIx TOP

FCT IPIF
ASIx, RAU gNB

RAU IKEP

RAU SECPOL
Meaning State

The temperature of the unit/module Start / Cancel

exceeds the threshold value.

The reference frequency that the BTS Start / Cancel

master clock receives has changed by
about 200ppb or more (which equals the
change magnitude of 204 DAC steps or
more (with 12bit DAC)) during the
A module required in commissioned 5G Start / Cancel
measurement period, compared to the
BTS configuration has not been detected
BTS master clock frequency.
or connection to a module belonging to
the 5G BTS configuration has been lost.
The cause of the alarm can be:
Meaning can be: frequency has changed
1. The reference Start
1. The 5GofBTS
because is site
a fault level
in the phase
transmission
synchronized only (e.g. via
network synchronization 1PPS/ToD
(which in turn is
sync
caused chain),
by anthe synchronization
equipment fault or Master
a setting
is frequency
error). Note synchronized
that if the networkand has
A new unit with incompatible SW might Start / Cancel
aquired a new arbitrary
synchronization malfunction phase duefor
lasts to a
have been inserted into the 5G BTS. a
reset.
long time, the alarm is cancelled when
the BTS frequency reaches the faulty
2. The 5G synchronization.
reference BTS was at holdover for a can
The alarm
Running
long SWand
period
also be version
activated the is faulty
not able
accumulated
if the tophase
install
reference Start / Cancel
requested
drift SW version.
has exceeded
synchronization +-5 ms. and there is,
is corrected
again, a difference of 0.2 ppm or more.
3.
TheRAP Internal
alarm synchronization
is cancelled wheneverbetween
the
units has
difference failed.
becomes less
BTS RTC initialization, which than is
0.2 ppm.
used to Start / Cancel
synchronize time for all nodes in the
2.
BTS,Thefails.
reference frequency fluctuates
continuously because of a significant
amount of jitter/wander in the
The BTS cannot
transmission obtainThe
network. a file fromisthe file Start / Cancel
alarm
server (error in
continuously FTP open or FTP get or
activated/cancelled
HTTP(S)
(however,GET). The filestate
the alarming server is down,
might
the file is missing,
predominate). There or the path issome
is always incorrect.
There is a
jitter/wander possible
in is
the error in
transmissionthe DCN and
The download corrupted or thenetwork; Start / Cancel
Iub,
the or a user-administration
limits are defined in ITU-T error (an
software is incorrectly produced.
invalid username or password, or the
G.823/824/825.
user does not have access rights to the
files).
3. If the BTS receives the
The 5G BTS SWinformation
<fileTypeNumber>
synchronization updatethat hasis failed.
viaincludedThein Start / Cancel
the 2.048
error
the
MHzfaultmight
or name
1PPS be synchronization
caused by a unit
is a variable reset
parameter,
input
during
which
(external theclock
SW update,
identifies the typeathe
source), hardware
of file
alarmfor which
problem
the in
download
situation thefailure
might unit, cabinet
has been
be caused by a reported.
fault of
incompatibility
that signal. problems with the
download, or a corrupted flash file
system.
4. There is an equipment fault in the
BTS. The equipment fault is, however,
not the most common reason. Normally,
the reason is in the synchronization
reference signal behavior (see the
descriptions above).
The 5G BTS SW update has failed. The Start / Cancel
error might be caused by a unit reset
during the SW update, a hardware
problem in the unit, cabinet
incompatibility problems with the
A module cannot be identified by its Start
download, or a corrupted flash file
product code or its physical device
system.
address (object ID) or Subrack type is not
identified.
An unsupported module has been Start
In case of a Radio Unit (RU), the
detected in the BTS. Typically, it
additional meaning is that RU was found
happens when a new version of a
in the planned HW configuration but is
module is installed and there is an older
connected to the wrong port.
BTS SW in use that does not support the
Communication with the application <x> Start / Cancel
new module version.
has failed. The application has not
replied to the message that has been
sent or re-sent to it.
L1 CPRI configuration was rejected by Start / Cancel
L1 SW.

The baseband bus synchronization has Start / Cancel

failed.

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

the OCXO does not become active within
a period of eight minutes from the power-
on. The ambient temperature can also be
too low or it changes too fast.
Master clock frequency is tuned to within Start / Cancel
5% of its minimum or maximum tuning
limit.

The output signal of the OXCO is missing Start / Cancel

and the ASIx cannot deliver the 30.72
MHz System Clock required by the other
units.
A corrupted SW file in the FLASH is Start
detected. The unit cannot perform a
complete start-up.

The reference clock monitoring has Start / Cancel

detected a loss of PPS signal in the
reference received from the GPS
receiver or from Sync Hub Master.
The Radio module configuration has Start
failed because of a hardware or software
fault.
A critical configuration file is missing from Start
the Radio Module.

The RAP TX path cannot be used. Start

The RX path in the RAP is faulty. Start

The FPGA software update has failed. Start

RF Module cannot identify the fan vendor Start / Cancel

or the fan is not installed.

Validated module temperature exceeds Start / Cancel

or is equal to the predefined maximum
value allowed.

The validated sensor temperature Start / Cancel

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

The FR module has detected a transient Start / Cancel

problem or DFE FPGA SW update that
requires a reset recovery.

The SW update of the AirScale module Start

(ABIx or ASIx) has failed or the SW is
corrupted.

Validated antenna submodule Start / Cancel

temperature is higher than the predefined
maximum allowed value.

The validated sensor temperature for Start / Cancel

antenna submodule exceeds or is equal
to the predefined value on the unit
property file.
There is a malfunction in Start / Cancel
Module/Antenna submodule PA power
supply.
RF SW detected that FPGA software Start / Cancel
downloading to antenna submodule
failed.

Antenna submodule PLL unlocked. Start / Cancel

This fault notifies the operator that the Start

gNB/ASIx/ABIx/RU must manually be
reset to solve a problem that has been
discovered by the O&M system, and that
O&M will not trigger an autonomous reset
The BTS has detected a communication Start / Cancel
on its own.
problem with the GPS receiver.

The fault is ignored until the GPS

receiver has reached commissioned
Connection to SW entity has been lost. Start / Cancel
state.

The BTS Fault, whichever fault name is Start / Cancel

mentioned in the Fault name field, is
toggling in the BTS. The toggling alarm
condition is presented to the user with
this new BTS Fault. Toggling alarms are
Fan speed is too low for a successful Start / Cancel
suppressed until the toggling alarm
detection. Detection is attempted again
condition is cleared. Severity of this BTS
after Fan.Detection.Timer expires.
Fault is the same as the severity of the
toggling BTS Fault.
This fault is reported for both operational
The temperature on the ABIx board Start / Cancel
and non-operational fans in the hardware
exceeds the critical threshold value.
detection phase only.

Fan is not running although the control is Start / Cancel

higher than 0.

Speed of the fan is deviating too much Start / Cancel

from the required control.

Fan is running faster than required. Start / Cancel

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

4083:
Source unit requests SW fallback
because of a critical problem that
occurred during SW update, that is,
configuration data migration failed.

4085:
Transport SW on the source unit
indicates a need for software fallback.
4082: Start
Source unit has reached the maximum
number of reset attempts, that is, the
source unit cannot successfully finish
start-up after the SW update.
4082: Start
Source unit has reached the maximum
4083:
number of reset attempts, that is, the
Source unit requests SW fallback
source unit cannot successfully finish
because of a critical problem that
start-up after the SW update.
The fault during
occurred indicates
SWpoor GPSthat
update, antenna
is, Start / Cancel
installation.
configuration data migration failed.
4083:
Source unit requests SW fallback
4085:
because of a critical problem that
Transport
The SW on the
GPS during
receiver source unit
is update,
running a site/self Start / Cancel
occurred SW that is,
indicates
survey. a need for software fallback.
configuration data migration failed.

4085:
Transport
There is noSW on the position
accurate source unit
stored in Start / Cancel
indicates a
the EEPROM. need for software fallback.

The receiver is used in the stored Start / Cancel

position but has been moved to a new
position.

The GPS receiver detected that one or Start / Cancel

more EEPROM segments were found to
be corrupted at reset and had to be set to
their factory default settings.
SW file validation against its signature Start / Cancel
failed.

External GPS/GNSS receiver module Start / Cancel

has lost satellite visibility and is currently
operating in a holdover mode.

There has been a failure in validation of Start / Cancel

the software release signature for the
software release that has just been
requested to be downloaded to the BTS
system module because information of
There has been a failure in validation of Start / Cancel
either Hash Container file or Hash
the hash of the questioned SW file for
Container Signature file is not present in
FCT, except of Hash Container file or
the downloaded TargetBD.xml, or the
Hash Container Signature file in the
verification of the software signature files
software release that has just been
An
hasunsigned
failed. software release has been Start / Cancel
requested to be downloaded to the BTS
downloaded to a BTS system module
system module. The reason is that the
that is currently running a software
hash value of the questioned SW file is
release that implements software
missing, or SiteOAM fails to verify the
signature checking.
hash of the questioned SW file.
There has been a failure in validating the Start / Cancel
software signature for the software
release that has been requested to be
downloaded to the BTS system module
because there is no software signature
The BTS has detected an incompatible Start / Cancel
for the release, and only signed software
operator-selected constellation mode for
can be installed.
the GNSS receiver.

The ToP (Timing over Packet) signal is Start / Cancel

unavailable or unusable as the reference
clock source.

Configured ToP (frequency/phase) Start / Cancel

doesn't match with configured sync mode
(frequency/phase) and hence, the
requested ToP configuration cannot
proceed.
Connection to a secondary unit that Start / Cancel
belongs to the BTS Dual ASIx
configuration has been lost.

BTS Secondary unit (system module) in Start / Cancel

dual core configuration has lost the 1PPS
reference signal at the 1pps/ToD
backplane interface towards the primary
unit.
The NodeB has detected that the Start
deployed Fiber Length between the RAU
& RU has exceeded the distance
supported by software. If this distance is
exceeded, the RU cannot function and
In a configuration where two optic fibers Start
this fault occurs. This applies to Cloud
are deployed to a RU from a RAU, the
BTS and 5G BTS.
maximum separation between those two
fibers is 1 km (1,000 meters, 3,280.84
feet). If this distance is exceeded, the RU
Installation of an additional operator Start / Cancel
cannot function and this fault is raised.
certificate (not including the RAP's own
This applies to Cloud BTS and 5G BTS.
trust chain) into the trust pool on the
Two fibers are deployed from a single
System Module for the RAP has failed,
modem board.
even though it succeeded on the VNF.
Removal of an additional operator Start / Cancel
certificate (not including the RAP's own
trust chain) from the trust pool on the
System Module for the RAP has failed,
even though it succeeded on the VNF.
The transport path (SCTP) for connection Start / Cancel
between gNB-CU and gNB-DU is broken.
This might be because of an unplugged
cable between them. There is no
transport path available to continue
The transport path (SCTP) for connection Start / Cancel
operation on the faulty connection
to the LTE eNB has failed to be
between gNB-CU and gNB-DU.
established. This might be because of an
unplugged cable to the eNB. There is no
transport path available to continue
operation on the faulty connection with
the eNB.
The transport path (SCTP) for connection Start / Cancel
between gNB-CU and gNB-DU has failed
to be established. This might be because
of an unplugged cable between them.
There is no transport path available to
This fault indicates that the absolute Start / Cancel
continue operation on the faulty
phase error of the BTS exceeds the limit
connection between gNB-CU and gNB-
of 1.5 us. This can occur when:
DU.
1) The absolute value of
The antennas' assignment for the cell is Start / Cancel
measured/estimated phase error of the
not available due to reasons such as lack
BTS has exceeded the limit of 1.5 us,
of configuration or misconfiguration or
reset trigger via ASiManager. This fault is
OR
only applicable to a cell using ASiR-HUB.
Failure was detected in the antennas Start / Cancel
assigned
2) The BTS to has
the cell. It could
lost all phasebesync
a
hardware
reference issue,
sources, configuration
but does not issue or
have
reset/block of an data
sufficient history antenna performed via
for holdover.
the
OR ASiManager. This fault is only
There is no X2-C link for the connection Active / Cleared
applicable
3) The BTS to isa synchronized
cell using ASiR-HUB.
to the LTE eNB available. Noby NSAreference
UE
which has capability
can connect to the gNB. to internal holdover
(Sync Hub Master/GNSS) which reports
the phase error of the provided sync
There
signal.has
Thebeen a BTS
absolute reset
value of caused
estimatedby Start / Cancel
software components
total phase error in thesupervision
"slave" sidefailure.
exceeds the limit of 1.5 us or source
reports that its holdover has expired.
The eNB configuration update procedure Start
has failed.

The transport path (SCTP) for the Start / Cancel

connection between gNB and AMF is
broken. This might be caused by an
unplugged cable between them. There is
no transport path available to continue
The transport path (SCTP) for the Start / Cancel
the operation on the faulty connection
connection to the AMF has failed to be
between gNB and AM.
established. This might be caused by an
unplugged cable to the eNB. There is no
transport path available to continue the
The transport path (SCTP) for the Start / Cancel
operation on the faulty connection with
connection between local gNB and peer
the eNB.
gNB/ng eNB is broken. This might be
caused by an unplugged cable between
them. There is no transport path
The transport path (SCTP) for the Start / Cancel
available to continue the operation on the
connection between local gNB and peer
faulty connection between local gNB and
gNB/ng eNB has failed to be established.
peer gNB.
This might be caused by an unplugged
cable between them. There is no
This fault indicates that a user- Start / Cancel
transport path available to continue the
configurable BTS fault has triggered an
operation on the faulty connection
internal snapshot and snapshot collection
between local gNB and peer gNB.
has failed (partially or completely).
Detected RF module does not support Start / Cancel
commisioned RF sharing type.

CPRI RF modules in NR-LTE sharing:

RM HW version should be >= Rel 5.1
There is a RF sharing mode conflict on Start / Cancel
(NAKHA)
the Nokia CPRI R5.1 radio to be shared
by NR with LTE technology such as :
(1) NR is in shared mode and peer
technology (LTE) is in standalone mode
This fault indicates that the gNB-CU Start / Cancel
or (2) NR in master mode and LTE also
could not activate the cell, as the X2 link
in master mode.
with the LTE eNB mapped to the NR
CELL was not established.
This fault notifies the operator that the Start
OAM has detected a configuration
change that requires ASIK restart in
order to be taken into use.
This fault indicates that a user- Start / Cancel
configurable BTS fault has triggered an
internal snapshot and the snapshot is
available on the node for operator
download.
This fault indicates that a user- Start / Cancel
configurable BTS fault has triggered an
internal snapshot and the snapshot has
been downloaded to an external server.
After an RU crash, RU has collected Start / Cancel
crash logs.

The third-party SFP modules complies Start / Cancel

with the system but it is not an approved
device.
It does not have EMC verification and
temperature range check. Putting it into
The SFP module has performed a limited Transient
operation may be risky.
verification of the part or has approved it
Note: The unit and interface variables
for use with other equipment, but its use
($U,$IF) will be replaced by appropriate
in this application is under restricted
hardware names.
conditions. It is not approved for use in
The transport path (SCTP) for connection Start / Cancel
this application in all conditions. For
to the LTE eNB is broken. This might be
example SFP module does not support
because of an unplugged cable to the
extended temperature range required by
eNB. There is no transport path available
the BTS.
to continue operation on the faulty
The
Note:BTS
Theconfiguration failedvariables
unit and interface in the C- Start
connection with the eNB.
Plane.
($U,$IF) will be replaced by appropriate
hardware names.

This alarm signifies OAM about non Start

Out of order Out-of-order Always with one

Working exception related to impossibility
of upgrade SSD firmware
Working when SSD firmware is
single component that is not
Working
updated

Out of order

Degraded Degraded when one antenna

Out of order module is out of order.
Out of order when all antenna
submodules are out of order.
Degraded Degraded when one antenna
Out of order module is out of order.
Out of order when all antenna
submodules are out of order.
Degraded Degraded when one antenna
Out of order module is out of order.
Out of order when all antenna
submodules are out of order.
Degraded

Degraded Degraded (there is no other

Working available and usable input
reference source to be
selected)
Working (5G BTS is synchronized
Out of order
with another input reference
source

N/A

Working

Degraded

Degraded Not all fans have failed: alarming

Out of order fan = out of order
All fans have failed: all fans = out
of order
Degraded Alarming fan = degraded, fan
group = degraded

Degraded

Out of order
Out of order

Out of order

Degraded Degraded (there is no other

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

Degraded Degraded (there is no other

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

Working

Working
Working

Working

Degraded Degraded (there is no other

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

Out of order

Degraded Degraded (no other ref. source

available)

Major The RU may not be operational

when this fault occurs.

Critical The RU is not operational when

this fault occurs.

Minor

Out of order None

Degraded Degraded
Out of order None

Out of order

Out of order Out of order - Cell cannot operate

because there are not enough
available and needed resources:
Tx or Rx.
Degraded Degraded - Cell can still operate
Out of order because it still has enough
available and needed resources:
both Tx and Rx.
Out of order - Cell cannot operate
Degraded Degraded
because there are not enough
available and needed resources:
Tx or Rx.

Working

Out of order None

Working
Out of order

Out of order

Working

Minor

Warning

Degraded

Out of order

Degraded
Warning

Working

Out of order

Major

Out of order

Major

Out of order

Major

Working Degraded (there is no other

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

Major

Major
Effect Reported Alarms

The BTS operation might be decreased. 7106

This fault does not immediately affect the 7108

operations of the BTS, but it is a notification
that the BTS master clock frequency
deviates from the used reference frequency
more than in normal circumstances.
The module in question is out of use. This 7100
alarm cancels all active alarms for the same
The BTS master clock tuning continues
module.
regardless of the alarm, but because the
BTS master clock adjustment is quite slow
The BTS
to filter thecapacity possibly
instabilities decreases,
of the reference 7101
some cells mightit become
clock interface, takes somedisabled or the
time (even 7108
BTS
severalis out of order.
hours) before the BTS operations
start to be affected.
The resources provided by the unit cannot 7104
be used until automatic SW update is 7105
finished.

Requested SW version cannot be installed 7106

due to the limitations of the running SW
version.

Real time is not available. Alarms, logs, and 7108

all reports have the incorrect time.

When a tuning mode is phase

synchronization, and the alarm occurs
The BTS continues its operation with the old 7106
during start-up, the BTS will not go on Air as
file.
long as the alarm is active.

The BTS continues operation with the old 7104

software. 7105

The SW update to this BTS might not be 7105

possible without special actions. The BTS
continues its operation with the old
software.
The SW update to this BTS might not be 7105
possible without special actions. The BTS
continues its operation with the old
software.
Depending on the reported severity and HW 7100
module for which an alarm is reported, the 7104
BTS capacity might decrease (hardware
problem) or the BTS might not be
operational at all.
The BTS capacity is decreased or BTS 7100
might not be operational at all (HARDWARE 7104
PROBLEM).

Some operations in the BTS are being 7101

interrupted. Depending on the fault source, 7104
the BTS or cell operation is degraded or 7105
faulty.
Processing resources, cells, or the whole 7106
BTS might be out of order.

This fault can prevent the BTS from 7100

functioning when the Radio Unit is needed
for the required cell configuration.

The system clock frequency starts to drift 7108

and the air interface frequency accuracy
starts to degrade. The BTS might work
properly for a few days without any signs of
a problem, but the network performance
The BTS can operate properly for months or 7108
might start to gradually decrease.
even a year when being within the 5%
margin area, but eventually the DAC value
reaches the adjustment limit (0 or 4095) and
the OCXO cannot follow the synchronization
The BTS is not operational. 7108
reference signal beyond the limit. When the
DAC value is 0 or 4095, the effect depends
on the network synchronization setting
defined in the BTS commissioning.
The unit might be started with an old SW 7104
version
Effects inand is therefore
Frequency not compatiblemode:
Synchronization with
any other unit.
Assuming that the BTS reference signal has
correct accuracy when the DAC value
reaches the adjustment
If other references limit 0 or the
are available, 4095 7108
(meaning the alarm indication
synchronization reference source changes is real, not
caused by incorrect reference),
to another source. Tuning then follows thisthe BTS air
interface starts
new reference. to drift from the correct value
and after a while (weeks or months) the
Calls
3GPP are not possible isthroughmetthe
anyaffected 7101
If otheraccuracy
references limit
are not available,
not more.
the
cell(s)
Even 7104
BTS master clock (OCXO) tuning is be
in that stage the BTS might still
operational
halted and the butBTS
the system performance
synchronization drops
might drop,
to holdover mode.affecting, for example, the
handovers.

Effects in Phase Synchronization mode:

When the DAC value reaches the
adjustment limit 0 or 4095, the basic LTE
system operation effects are the same as in
Frequency Synchronization mode but the
LTE feature(s) which require Phase
Synchronization become(s) non-operational
because the OCXO cannot adjust the phase
Calls are not possible. 7101
7104

Calls are not possible through the affected 7105

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

Calls are not possible, or problems might 7105

occur during calls through the affected cells.

There might be problems with calls made 7100

through the affected cell(s) (7104 CELL 7104
SERVICE PROBLEM).
Cell(s) is not affected) (7100 HARDWARE
PROBLEM).
The fault might mean that fans are not 7100
connected/working. This might cause the
RF module to overheat.

The fault can only be automatically

The RF Module might overheat, but there is 7100
canceled for RF modules where fans are
no immediate effect on the module
detected based on speed response. All
operation.
other RF modules require a reset.

Calls are not possible with the affected cells 7104

RF module is not taken into use. Calls are 7104

not possible through the affected cells.

SW update needed. 7106

The antenna submodule may overheat, but 7100

there is no immediate effect on the module
operation.

Validated antenna submodule temperature 7104

is significantly higher than predefined
maximum allowed value. Calls are not
possible with the affected cells.
Calls are not possible through the affected 7100
antenna module.
There might be problems in calls through 7111
the affected cells.

The communication between the System 7100

Module and RF module might be corrupted.
Calls are not possible through the affected
antenna module.
The effect depends on the case when the 7101
fault is detected. 7104
7105

GNSS becomes unusable. 7108

The RAP resources have decreased or the 7101

RAP is faulty. 7108

Depending on the reported alarm, the fault 7100

situation might have no impact on the 7106
operation, the BTS capacity might have 7107
decreased, or the BTS might not be 7108
operational at all.
Fan control is not optimized. The effect of 7106
noise/temperature level is marginal.

FSP DSPs not in use; BTS operation is 7106

degraded or faulty. 7101
7104

If the fans are not rotating as required, there 7106

is a risk that the module temperature is
rising too high.

If the fan(s) is/are not rotating as required, 7106

there is a risk that the module temperature
is rising too high.

If the fans are rotating faster than required, 7106

they create unnecessary noise.

Source unit has inconsistent SW version. 7106

GNSS becomes unusable. 7108

Due to problem detection in Start-up, BTS 7109

remains out of order.

GNSS accuracy is not guaranteed. 7108

Software download has failed and must be 7109

retried.

Software download has failed and must be 7109

retried.

The unsigned release has been 7109

successfully downloaded, but no signature
verification is possible for the release. If it is
downloaded without activation, the unsigned
SW build is only downloaded to passive file
system and the previous SW build is still
used. If it is downloaded with activation after
a BTS reset, the new downloaded unsigned
SW build is used.
Software download has failed and must be 7109
retried.

The fault has no direct impact on the current 7115

operation (BASE STATION
NOTIFICATION).

If other references are available and 7108

configured, then the synchronization 7115
reference source changes to another
source. Tuning, then, follows this new
reference.
5gNB performs switchover to another input 7108
reference clock source if available.
If other references are not available, the
5gNB master clock (OCXO) tuning is halted
and in phase mode, and the 5gNB
The secondary unit
synchronization is out
drops of order or
to holdover mode. 7101
removed, or 40GbE connection is out of 7115
order. All cells supported by the secondary 7116
baseband modules connected to secondary
unit are disabled.
The AirScale secondary unit is not 7108
synchronized by AirScale primary unit (in
BTS runtime),
The AirScale secondary unit goes to
holdover (no other ref. source available),
The RU unit in question may be out-of- 7121
4385 is raised with Degraded.
service and cannot become active.
This fault is detected upon the initial startup
of the NodeB, or connection of the
RU.
The RU unit in question is out-of-service 7122
and cannot become active.

This fault cancels all active faults for the

same unit.
The RAP cannot set up a secure connection 7109
to the entity that the certificate is to be used
This fault is detected upon initial startup of
for.
the NodeB, or connection of the RU.

The RAP may fail to set up a secure 7109

connection to a remote interface because it
is using an outdated or compromised
certificate.
All calls over the affected gNB-DU are 7107
failed.

No NSA calls can be setup over the affected 7107

eNB.
No call can be setup over the affected gNB- 7107
DU.

The BTS is not operational. 7101

7104
7108

The antenna carrier(s) for the cell is(are) 7104

deactivated. The cell is disabled.

Degraded: The availabilityStatus for the cell 7104

is degraded.
Out of order: The antenna carrier(s) for the
cell is(are) deactivated. The cell is disabled.
No NSA UE can connect to the gNB 7107

None 7101

If the update of the cell was not successful, 7104

the reconfigured cells are not on air.

All calls over the affected AMF are failed. 7107

All Xn based handover over the affected 7107

gNB peer are failed.

All Xn based handover over the affected 7107

gNB peer are failed.

Snapshot is cancelled, or collecting of 7106

troubleshooting data continues at all
remaining sources, but the snapshot file
does not contain data from at least one
source.
RF module is not taken into use. 7104
7105

Shared radio cannot be used. 7104

7105

The gNB services are degraded due to a 7104

cell not being on air.

Site Reset. 7101

None 7106

This fault has no effect on the BTS 7115

operation.

The SFP is operational and It has risk to 7100

operate.

The SFP is operational and it is risky to 7100

operate.

NSA calls over the affected eNB are failed. 7107

As long as the number of allowed 7101

autonomous BTS resets has not yet been 7105
exceeded, an autonomous BTS reset will be
performed in an attempt to recover.
The unit is not fully operational. 7101
7104
Data transfer on NSA bearer via X2-U is not 7115
possible with SN terminated split bearer
with the offending MeNB.

Flow control of user plane data is not

In the case of subscriber trace activation, if 7115
possible between the PDCP of SgNB and
the failed trace connection was used for
the RLC of MeNB. After hardcoded time
sending the trace reports, the BTS
without Downlink Data Delivery Status
considers the trace activation for that
(DDDS) from RLC of MeNB (carried within
subscriber as failed.
No
NR dataRANor clock information
Container is exchanged
GTP-U extension 61029
via this interface.
header), SgNB stops data transmission over
In the case of cell trace, interface trace &
X2-U link. After further hardcoded time to
PCMD, if the failed trace connection was
Possible
wait for X2-U impactlinkon the connections
recovery over
(at least one
used for sending the trace reports, the BTS
this
DDDS interface:
received) expires, SgNB release is
Possible
does not effects:
start tracing until the trace 61030
-triggered
voice calls or dataofconnections
because X2-U link are aborted
failure.
-connection
No calls are possible
is established successfully.
and cannot be established anymore
- Loss of remote management access to
- remote management connectivity is lost
other network elements in the RAN
and cannot be established anymore
- Loss of synchronization if the interface is
The
- lossinterface cannot be used
of synchronization if the for
interface is 7100
used as a synchronization source
transmission. The laser of the
used as a synchronization sourceoptical
- IKE SAs and IPSec SAs cannot be
transceiver
- dependingmodule
on use cannot be switched on.
of the Ethernet
established or re-keyed.
interface, the above described impact can
An Ethernet
occur for theLink
local cannot
SBTS be and/orsuccessfully
other not be
The Certificate Revocation List could 7109
established
(S)BTS since ifit they
is down.
updated. New revoked certificates via the
elements are chained
No Ethernet
Ethernet data or clock information is
interface
remain unknown to the 5GNB.
exchanged via this interface.

The
Possibleoptical transceiver
impact on the is not operational.
connections over 7100
this interface:
The
- voice interface
calls orofdata
the connections
optical transceiver
cannot be
module
established cannot be used for transmission.
The
-The lasermanagement
remote of the optical transceiver module
requested service connectivity cannot
is not available. 7109
cannot be switched on.
be established
- loss of synchronization if the interface is
No
used data
as or clock information
a synchronization is exchanged
source
through
- depending this interface
on use ofofthe optical transceiver
Ethernet
None
module.
interface, the above described impact can 7109
occur for the local BTS and/or other BTS
The following
elements areare
if they thechained
possiblethrough
impactthe on the
connections
Ethernet interface. over this interface of the optical
transceiver
No immediate module:
effect. If at all certificate 7109
-expires
Voice calls
without or data connections
any action cannot be
from operator
established.
due to this fault, secure communication to
-remote
The remote
peers management
may fail. connectivity
cannot be established.
5gNB
- Thereperforms
is loss ofswitchover to another
synchronization if theToP 7108
master
interfaceif available.
is used as a synchronization
source.

The remote peer to come online with the 61632

same IP address on the same subnet as the
local peer would just disable their network
interface and give an error until the situation
is resolved by the administrator.

This allows the local peer to continue

functioning without disruption, but
completely breaks IP base communications
for the connected network.
No further logins are permitted for that 7109
account until it is unlocked.

The IKE SA cannot be established. 61644

IKE SA cannot be established and 61645

subsequently no IPsec SAs can be
established.

The related IPsec SA cannot be established 61646

and used.
Reported Alarms Description

7100 HARDWARE PROBLEM

7108 is reported always

7101 reported in a case of autonomous recovery reset

will be performed
7104 CELL SERVICE PROBLEM (in case the source is
5GRU with allocated CELLs)
7105 RAT BASE STATION PROBLEM (in case the
source is 5GRAU (ASIx or ABIx or 5GRU without
allocated CELLs)

7104 CELL SERVICE PROBLEM (in case the source is

5GRU)
7105 RAT BASE STATION PROBLEM (in case the
source is ASIx)
7100 HARDWARE PROBLEM (if cells are not affected)
7104 CELL SERVICE PROBLEM (if cells are affected)

7100 HARDWARE PROBLEM (if cells are not affected)

7104 CELL SERVICE PROBLEM (if cells are affected)

7101 RESET NOTIFICATION

7104 CELL SERVICE PROBLEM (in case the source is
Radio Unit)
7105 RAT BASE STATION PROBLEM (otherwise)
7106 SINGLE RAN BASE STATION PROBLEM

10.01.2017 Detecting and Source unit aligned with

latest SBTS(SBTS16.10)

7101 RESET NOTIFICATION (when reset is being

performed)

When reset has not been triggered for any reason:

7104 CELL SERVICE PROBLEM
7101 RESET NOTIFICATION (when reset is being
performed)

7104 CELL SERVICE PROBLEM (When reset has not

been triggered for any reason)
7105 RAT BASE STATION PROBLEM

7105 RAT BASE STATION PROBLEM

7100 HARDWARE PROBLEM (cell not affected)

7104 CELL SERVICE PROBLEM (cell affected)

7100 HARDWARE PROBLEM

7104 CELL SERVICE PROBLEM (in case the cell

cannot operate because radio requires reset)

7100 HARDWARE PROBLEM

7104 CELL SERVICE PROBLEM

7100 HARDWARE PROBLEM

7111 BASE STATION SOFTWARE MANAGEMENT
PROBLEM

7100 HARDWARE PROBLEM

7104 CELL SERVICE PROBLEM (Source is ABIx, RU)

7105 RAT BASE STATION PROBLEM (Source is ASIx)
7101 RESET NOTIFICATION (if automatic site reset
recovery is performed)

7108 BASE STATION SYNCHRONIZATION PROBLEM

(always)
7101 RESET NOTIFICATION (in case recovery reset
will be triggered)
7100 HARDWARE PROBLEM (Level BTS fault is
toggling in the BTS.)

7106 SINGLE RAN BASE STATION PROBLEM (Level

BTS fault is toggling in the BTS.)

7107 BASE STATION CONNECTIVITY PROBLEM

(Level BTS fault is toggling in the BTS.)

7101
7108 RESET NOTIFICATION
BASE STATION (when reset is being
SYNCHRONIZATION PROBLEM
performed)
(Level BTS fault is toggling in the BTS.)
7104 CELL SERVICE PROBLEM (the faulty FSP is
mapped to the cell)
7106 SINGLE RAN BASE STATION PROBLEM (the
faulty FSP is not mapped to any cell)
7115 BASE STATION INFORMATION

When fault affects basic services of the base station:

7108 BASE STATION SYNCHRONIZATION PROBLEM

When fault does not affect basic services of the base

station:
7115 BASE STATION INFORMATION

when autonomous recovery reset is being performed

due to fault
7101 RESET NOTIFICATION
when fault does not affect basic services of the base
station
The fault affects basic services of the base station
7115 BASE STATION INFORMATION
7108 BASE STATION SYNCHRONIZATION PROBLEM
when fault affects basic services of the base station
7116 BASE STATION SERVICE PROBLEM

7121 NODEB FIBER LENGTH DEPLOYMENT

EXCEEDED

Severity is Major, the RU may not able to come into

A fault (or faults) has(have) occurred in the base station

connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
7108 BASE STATION SYNCHRONIZATION PROBLEM
(always)
7104 CELL SERVICE PROBLEM (always)
7101 RESET NOTIFICATION (in case recovery reset
will be triggered)

A fault has occurred in BASE STATION

CONNECTIVITY PROBLEM At
MRBTS/NRBTS/X2linkSupervisionTmr expiry which is
started when there is no X2-C link available.
When autonomous recovery reset is being performed
due to the fault

7104 CELL SERVICE PROBLEM

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

station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
None
7105 RAT BASE STATION PROBLEM (in case fault
affects basic services of the base station)
7104 CELL SERVICE PROBLEM (in case the cell
cannot operate because it does not have enough
available and needed resources: Tx or Rx)
7105 RAT BASE STATION PROBLEM (in case the fault
affects basic services of the base station)
7104 CELL SERVICE PROBLEM (in case the cell
cannot operate because it does not have enough
available and needed resources: Tx or Rx)

7101 RESET NOTIFICATION (when reset is being

performed)

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

station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
7105 RAT BASE STATION PROBLEM (otherwise)
7101 RESET NOTIFICATION (raised only if RESET
RECOVERY is triggered)

This non critical SW fault is raised whenever the

common unit/capacity unit (RAU) Platform CE non
critical process has crashed.
A fault has occurred where at least one MeNB involved
in non-standalone call with SgNB erroneously does not
support "NR RAN Container" GTP-U extension header
on X2-U interface.
7115 BASE STATION INFORMATION

61030 Dead Peer Detected

61644 IKE authentication failure

61645 IKE SA failure

61646 IPSec SA failure

Instructions

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

Because there are several possibilities for the alarm

activation, a BTS Clock Frequency History feature has
been developed. You can access the stored history data
via WEBUI. You can use the history data as a tool for
finding out the reason for the fault/alarm situation (for
To clear this fault, perform the following steps:
further instructions about the history feature, see the online
help of WEBUI). Depending on the possible reason, follow
1. Make sure that the module is properly connected. Check
the instructions below:
the alarming module.
2. Check the fault history.
If
1.fault does
In case ofnot get in
a fault cancelled:
the transmission network
1. Reset RAP you must correct the network
synchronization,
synchronization. The long-term accuracy of the signal used
If
forfault
syncoccurs after
must be reset(s):
0.015 ppm or better (check the correct
1. Replace
accuracy the failing unit.
Update the BTS with theit).
by measuring No actionsSW
compatible on (check
the BTS are
the SW
necessary.
versions to see the active SW version and update to the
active SW version), unless it is automatically updated by
2. If the basic accuracy of the signal used for synch is
NetAct.
correct, but there is too much instability, that is, the
Update compatible
jitter/wander SWthe
in the BTS.
NOTE: If the is outside
fault acceptable limits, you must is
10:EFaultId_NoConnectionToUnitAl
correct the synchronization of the transmission
also active on the source unit, then the SW update network.
must be
NOTE:
The If also
limits for fault
the 10:EFaultId_NoConnectionToUnitAl
jitter/wander are defined in the ITU-T is
postponed until the fault
active on the source
G.823/824/825. unit, then
No actions on the BTS
SW update should be
are needed.
10:EFaultId_NoConnectionToUnitAl is canceled.
postponed until fault 10:EFaultId_NoConnectionToUnitAl is
1. Check the NTP setting.
canceled.
3.
2. In casethe
Check of astratum
BTS equipment
parameterfault, theNTP
on the location might be:
server.
3. Check if a GNSS is configured and connected.
Transport part:
- Check the alarms of the TRS signal used for
Take the following
synchronization actions
with WEBUI to and
clearact
theaccordingly.
fault:

1.
RAP Check
unit:the file type according to the file type number
below:
- If the TDM reference signal accuracy and the TRS are in
<fileTypeNumber>
order but following
the RAP unit - is
<fileType>
stillclear
alarming, run the fast tuning
Take the steps to the fault:
with 1WEBUI.
- hwConfigurationFile
- Retry the SW update.
2 - configurationPlanFile
3 - alarm
- If the logFileis still active after the fast tuning is finished,
reset 4 the
- swFile
site. If the problem does not disappear in a few
Take 5 the
minutes, following
- licFile
reset steps to resolve the fault:
the site.
6 - measurementFile
1.
- IfRetry the SW not update.
7 - rnwConfigurationPlanFile
that does help, replace the RAP unit.
2. If11other flash memory-related faults in the alarming
- combinedSiteConfigurationPlanFile
module are simultaneously active, replace the alarming
12 - allConfigurationPlanFile
module.
14 - testResultFile
Note 15that- autoConfReport
if the reason is in the transmission network
17 - measurementPlanFile
synchronization, replacing the faulty unit does not solve the
18 - rnwMetadataFile
problem. Furthermore, the alarm activity (frequent
19 - topologyFile
alarms/cancels) points to instability in the transmission
22 - togglingParFile
network, not to a fault in the unit.
23 - troubleShootingData
[...]
Take the following steps to resolve the fault:

1. Retry the SW update.

2. If other flash memory-related faults in the alarming
module are simultaneously active, replace the alarming
Follow the steps below to resolve the fault:
module.
1. In case of a Radio Unit, try to connect that Radio Unit to
a different port.
2. In case of other sources or if the Radio Unit was already
To clear the fault, take the following steps:
checked and connected to all ports indicated in the BTS
profile and the fault is still active, change 5G BTS planned
1. Upgrade BTS software.
HW configuration (BTS profile) to take the module into use.
2. Replace the alarming module.
3. Replace the alarming unit with the unit planned in 5G
Take the following
BTS planned actions to clear
HW configuration theprofile).
(BTS fault:

1. Make sure that the unit/module is properly connected. If

the unit/module LED does not light up, the unit/module is
faulty. Check the alarming unit/module.
1. Download the correct configuration.
2. Check the fault history.
2. Reset the BTS.
3. Replace the alarming unit.

Perform the following actions in order and, after each

action, check if the problem recovers:
1. Manually restart the BTS Site.
2. Check if the problematic cable connecting the baseband
module and radio module is firmly fixed to the modules.
Replace the alarming module.
3. Replace the problematic cable.
4. Change the unsupported or faulty QSFP unit in FBB or
on the Radio Unit side.
5. Change the faulty module (ABIx or the radio unit).
Because there are several possibilities for the alarm
activation, a BTS Clock Frequency History feature has
been developed. You can access the stored history data
via BTS Element Manager. You can use the history data
as a tool for finding out the reason for the fault/alarm
1. Reset RAP
situation (for further instructions about the history feature,
2. Replace RAP.
see the online help of BTS Element Manager). Depending
on the possible reason, follow the instructions below:

Update the SW in the BTS.

1. In case of a fault in the transmission network
synchronization, you must correct the network
synchronization. The long-term accuracy of the signal used
for synch the
1. Check mustGPSbe 0.015
receiver ppm or better (check the correct
installation.
accuracy by measuring it). No
2. Check the GPS receiver status. actions on the BTS are
necessary.
3. Check the connection between the GPS receiver and
ASIx.
4. Check the cable or connection towards a Sync Hub
Take
2. thebasic
If the following actions
accuracy to clear
of the signalthe fault:
master when operating as Sync Hub used
slave.for synch is
correct, but there is too much instability,
5. Check the status of the SyncHub master. that is, the
1. Confirm if the
jitter/wander existingthe
is outside configuration
acceptable is within
limits, youthemust
configured
correct the RAP HW capabilities.
synchronization of the transmission network.
2.
The Check
limitsthe
for BTS connectionsare
the jitter/wander anddefined
commissioning
in the ITU-T
settings.
G.823/824/825. No actions on the BTS are needed.
3. Reset the RAP.
4. Block/Unblock the BTS.
5.
3. If
Inthe
caseHWof configuration
a BTS equipment is confirmed,
fault, theitlocation
means this
might be:
problem is caused by the 5G BTS SW. Check the other
active
Transport alarms.
part:

- Check the alarms of the TRS signal used for

synchronization with BTS Element Manager and act
Take the following actions to clear the fault:
1. Block/Unblock the RAP HW unit.
2. If the problem is still observed after performing the first
step, replace the RAP.
Take the following actions to clear the fault:

1. Check the connection and integrity of the antenna

connector, cable, and antenna.
2. Reset the radio module. If the alarm persists, replace
1. Reset the radio module. If the alarm persists, replace
the RM.
the RM.

1. Block/unblock RF HW unit
2. If the problem persists, replace the RF HW unit

Follow the steps below to clear the fault:

1. Check if the fan or airflow is free of foreign objects.

Remove any objects blocking the fan or the airflow.
2. Check if the fan connector is properly mounted. Mount
Take the following steps to clear the fault:
the fan connector according to the guidelines.
3. Reset the RAP
1. Check if the ambient temperature/environmental
4. If the alarm is still observed, then replace the fan or the
conditions are within the design limits for the radio module.
RAP.
When the ambient temperature/environmental conditions
1. Check if the ambient temperature and environmental
exceed the limits, the alarm is expected and no further
conditions are within the designed limits for the radio
actions are needed.
module. When the ambient temperature and environmental
conditions exceed the limits, the alarm startup is expected
2. Check if airflow is free of foreign objects. Make sure the
and no further actions are needed.
No actionsthermal
minimum are needed since the
clearances BTS recovers
guidelines are followed.
independently.
Remove any objects If the alarm occurs
that might be multiple
blockingtimes, checkand
the airflow
2. Check if air flow is free of foreign objects. Make sure that
other
mountactive alarmsaccording
the module to determine the root cause.
to instructions and
minimum thermal clearance guidelines are followed.
recommendations.
Remove any objects that might be blocking the airflow and
To clear
mount this
the fault: according to instructions and
module
3. Check if excessive sunlight is causing the unit to
recommendations.
overheat.
1. Retry the Install the sunshield following the mounting
SW update.
instructions
2. and recommendations.
3. If the problem
Check is permanent
if excessive contact
sunlight is causingNokia support
the unit to
overheat. Install the sunshield following
Take the following steps to clear the fault: the mounting
instructions and recommendations.
1. Check if the ambient temperature/environmental
conditions are within the design limits for the antenna
sumodule. When the ambient temperature/environmental
1. Check if the ambient temperature and environmental
conditions exceed the limits, the alarm is expected and no
conditions are within the designed limits for the antenna
further actions are needed.
submodule. When the ambient temperature and
environmental conditions exceed the limits, the alarm
2. Check if airflow is free of foreign objects. Make sure the
startup is expected and no further actions are needed.
1. Reset the
minimum RF HW
thermal unit.
clearances guidelines are followed.
Remove any objects that might be blocking the airflow and
2. Check if air flow is free of foreign objects. Make sure
2. If thethe
mount problem
modulecontinues
accordingafter step 1 has been
to instructions and
minimum thermal clearance guidelines are followed.
performed, replace the RF HW unit.
recommendations.
Remove any objects that might be blocking the airflow and
mount the module according to instructions and
3. Check if excessive sunlight is causing the unit to
recommendations.
overheat. Install the sunshield following the mounting
instructions and recommendations.
3. Check if excessive sunlight is causing the unit to
overheat. Install the sunshield following the mounting
instructions and recommendations.
1. Reset the RF HW unit.

2. If the problem continues after step 1 has been

performed, replace the RF HW unit.
1. Reset the FR HW unit and check if this solves the
problem.

2. If the alarm continues after executing steps 1, replace

the RF HW unit.
Check the source of the fault to see the level at which reset
loops have been occuring.
Investigate the fault or alarm history to solve the problem.
Consider resetting on higher level (ex. gNB reset) if fault
source is ASIx, ABIx, RU.
Perform the steps below in the listed order until the fault
disappears. If after autonomous GPS power reset, the fault
does not get canceled, wait for five minutes (from the start
of the fault) prior to performing the actions below.
This fault is most likely the result of a BTS hardware
Control Interface is not available:
problem or a reference source that is being followed by the
1. The BTS has detected a malfunction in the control
BTS that is in a faulted condition, therefore producing an
interface of the GPS receiver. A possible reason is that the
inaccurate reference. Perform the following steps to isolate
BTS and the GPS receiver do not support a common
the cause of the fault:
Follow theOtherwise,
interface. steps below to clear
perform a the fault: power reset for
(remote)
the GPS receiver.
1. Check the other alarms of the BTS and act accordingly.
1.
2. Check
Performthe fault name
a (remote) BTSof the
site toggling
reset forBTS fault. BTS.
the whole
3. Perform a power reset for the whole BTS.
2. If there are no other synchronization-related alarms
2.
4. Follow the between
instructionsthe of the receiver
toggling and
BTSthefault to clear
ToThe
clearcable
active, thisthe
start fault: GPS
fast tuning with BTS Element Manager.
BTS might
the
be problem.incorrectly. Check if the pins of the connectors
working
1. Check the fan and connector.
(onIf both
step ends
2. Reset 1 does of the help,
cable) are free from
fan.oxide and other
3. the site.not
Run fastreplace the
tuning again.
Note:
kind ofDetailed information
dirt, meaning that theabout the togglingquality
pin connection frequency
is
can
good. be found in the alarm history file, which can be
4.
To Check the fault:
clearcable
this reference signal accuracy by measuring it
downloaded
5. The using
between the the
VNFGPSWebUI. The and
receiver log file
theisBTS
available
might
with a frequency counter (note: requires a good timebase
with Snapshot.
be faulty. Check the situation and change the cable, if
for
1. the counter).
Check the fansThe andreference
make sure signal
that can be found from
the ambient
needed.
the Sync
temperature Out interface
on-site of the Flexi System Module, the
6. There might be a isHW acceptable.
fault in the GPS receiver. Check
required
2. accuracy
Ifoperation
that does and is +/-0.015ppm.
not help, replace If the
the alarming reference
the
To clear this fault: change the GPS module, ifmodule.
needed.
accuracy is correct, run fast tuning. If the reference
7. There might be a HW fault in the BTS System Module.
accuracy is not correct the cause of the fault is the
Check
1. Makethe operation
sure the fan and change the System Module, if
reference source the is
BTSnotisblocked.
tuning to. Troubleshoot the
needed.
external synchronization network to find the root cause.
2. Make
Other surewith
BTSs the fan connector is properly mounted.
To clear this fault:the same alarm can provide further
information about the location of the root cause.
3.
5. If that does not help,
the reference replace
accuracy the fan.
is correct and running fast
1. Make sure the fan is not blocked.
tuning does not help, replace the system module.
2. Make sure the fan connector is properly mounted.
Replace the fan.
3. If that does not help, replace the fan.

If the BTS is not automatically updated by NetAct, update

the BTS with the SW version running on the BTS before
the SW update causing SW fallback.
NOTE: In case BTS Element Manager detects an incorrect
SW version, the BTS Element Manager should be
reconnected.
If the BTS is not automatically updated by NetAct, update
the BTS with the SW version running on the BTS before
the SW update causing SW fallback.
NOTE: In case BTS Element Manager detects an incorrect
SW version, the BTS Element Manager should be
If the BTS is not automatically updated by NetAct, update
reconnected.
the BTS with the SW version running on the BTS before
the SW update causing SW fallback.
NOTE: In case BTS Element Manager detects an incorrect
SW version, the BTS Element Manager should be
Perform the steps below in the listed order until the fault
reconnected.
disappears.

Not tracking satellites:

Perform the steps below in the listed order until the fault
1. The most common reason for this fault indication is that
disappears.
the GPS antenna installation has not been done properly,
that is, the sky visibility is not good enough. Refer to the
Survey in progress:
documentation for installations and if there are deviations
1. Do nothing. The alarm is informative only. Normally, the
Perform
from the the steps
actual below in the
installation, listed the
re-install orderGPS until the fault
antenna.
GPS receiver runs the survey for two reasons:
disappears.
Note that even when the GPS antenna has a good sky
- somebody has started the survey manually,
visibility, the problem might be caused by installing the
- the GPS receiver has noticed that the position has
No
GPS stored
antenna position:
too close to the transmitter antennas of the
changed and the receiver has started an automatic survey.
1.
BTS,One of the GPS
causing receiver for
disturbances settings
the GPSis incorrect.
receiver. Using the
Perform
Note: The the steps below
automatic survey in the listed
always order
takes until the
place during faultthe
manager SW of the GPS receiver, set the receiver to store
disappears.
first start-up.
the position
2. There mightintobe aa non-volatile
malfunction memory.
in the GPS receiver.
If there isano
Perform tick mark
(remote) powerin the position
reset for the storage selection, the
GPS receiver.
Position questionable:
2. If the automatic survey takes place every now and then,
GPS receiver runs the site/self survey every time the GPS
1. The GPS
itPerform
might be anreceiver
indication hasthat validtheposition data but
sky visibility it is not
is poor andin
receiver
3. There the
is
mightsteps
reset be below
(either
a HWby inmanager
the
fault inlisted
thefrom order
command,
GPS until
receiver.thepower
by fault
Check
line with the
according to information
the estimated
poorly-tracked satellites, thetheactual
GPS satellite
receiver
disappears.
outage,
the or by a
operation and GPS recovery
change reset).
thefault
GPS This means
module, if needed.that if the
visibility.
concludes Thethatreason for this
the position indication
has changed. Inmight
this case,be that
GPS receiver installation quality is only an average - and
the
check GPS theantenna
activity of installation
the otherhas faults not(BTS beenfault
done properly,
history data)
EEPROM
especially invalid:
if the installation is a poor one - the GPS
that
and is,
if the sky
found visibility
feasible, is not good
reinstall the enough.
GPS Refer to the
antenna.
1. The GPS
receiver turns receiver
the PPS has detectedOFF
reference a malfunction
every now inand
thethen
Trigger SW
documentation update for BTS
for instructions, to theandrequested
if there are SW version.
deviations
EEPROM
during the memory site survey. of theThis GPSmeans receiver.
the BTS Perform
master a (remote)
clock
with
3. the GPS
If the actualinstallation
installation, is reinstall
good butthe theGPS antenna.
automatic survey
power
drops to reset for themode
holdover GPS much receiver.easier during the survey
Note:
still takesEven when
place the GPS
every now and antenna then,has a good
there mightsky be a
than during the normal operation.
visibility,
malfunction thein problem
the GPS might be caused
receiver. Perform by ainstalling
(remote) the
power
2. There might be a HW fault in the GPS receiver. Check
GPS
reset
1. antenna
for the GPStoo close
receiver. to the transmitter antennas of the
theOne of the most
operation and changecommon thereasons
GPS module, for this iffault
needed.indication
BTS, causing disturbances for the
(especially occasional indications) is that the GPS/GNSS GPS receiver.
2.
4. There
antenna might be
If the actions
installation a has
malfunction
detailed in the
not been indone
previousthe GPS steps receiver.
properly,do that
not is,
Perform
improve a (remote) power reset
the sky visibility is not good enough. Refer to the the
the situation, there might for bethe a GPS
HW receiver.
fault in
3.
GPS There might Check
receiver.
documentation be
for ainstallations
HWthefault inand
operation the and
ifGPS receiver.
change
there theCheck
are deviationsGPS
Retry
the
module, theifSW
operation needed.update.
and change the GPS module, if needed.
with the actual installation, re-install the GPS/GNSS
antenna. Note that even when the GPS/GNSS antenna
has good sky visibility, the problem might be caused by
installing the GPS/GNSS antenna too close to the
Retry the SW
transmitter update. of the BTS, causing disturbances to
antenna(s)
the GPS/GNSS receiver.

2. Check the other possible alarms/fault indications of the

GPS/GNSS receiver
No manual action and thefrom
is needed BTS the
andoperator.
act accordingly.

3. There might be a malfunction in the GPS/GNSS

receiver. Perform a (remote) power reset for the
GPS/GNSS receiver module.

4. If there is only the alarming GPS/GNSS receiver

connected to the GPS/GNSS antenna, check the antenna
power feeding setting in the GPS/GNSS receiver settings.
The power needs to be ON in this case (while in shared
configuration, one receiver feeds the power towards the
antenna and power feeding setting of the other receivers is
OFF).

5. Check the connection between the GPS/GNSS receiver

Retry the SW update.

Change the GNSS constellation mode to a constellation

mode supported by the receiver to cancel the fault.

1. Check the cable connectivity on the ToP master side.

2. Check the TOP configuration on both the BTS and ToP
master sides.

Check BTS configuration (sync mode) and TOP

configuration.

Note: Perform the steps in the listed order until the fault is
resolved.
1. Reset the BTS.
2. Check the connectivity:
AirScale: Ensure that the module is properly connected to
1. Wait for Secondary Unit reset.
the rack.
2. If it does not help, replace the unit one by one in the
3. Check the SW version on Secondary core if it is the
below order:
same as Primary core.
a. primary unit (ASIK primary)
4. Replace the faulty unit.
b. secondary unit (ASIK secondary) then
To solve this problem, a technician should inspect the optic
c. AMIA subrack (AirScale)
fiber deployment of the RU unit in question. This fault
occurs when a RU is configured with a
fiber optic cable between the RAU and RU that physically
exceeds the maximum length supported. The maximum
To solve this problem, a technician should inspect the optic
length supported will depend on the 5G release in question
fiber deployments of the RU unit in question. This fault
(and changes/increases with different releases). The
occurs when a RU is configured with two fiber optical
physical connections and physical deployment should be
cables to one modem card. The differential between these
checked to see that these lengths are not exceeded. The
fiber optical cables must not exceed 1000m. The physical
Manually reset
technician the RAP.
can then reset the NodeB and software will
connections and physical deployment should be checked
automatically re-compute to see if the fiber lengths are not
to see that these lengths are not exceeded. The technician
within the acceptable differential range.
can then reset the NodeB and software will automatically
re-compute to see if the fiber lengths are not within the
Manually reset
acceptable the RAP.
differential range.

Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check the connection between gNB-CU and gNB-DU.

Note: Perform the steps below in the listed order until the
2. Check if the gNB-CU or gNB-DU is operational.
alarm disappears:
3. Check if the speed and duplex setting of the VNF F1
1. Check the connection with the eNB.
port is consistent with
2. Check if the eNB is operational.
the switch port that is connected directly to the VNF (for
example, they are
3. Check if the speed and duplex setting of the VNF X2
port is consistent with
both "Autodetect" or both "1000 Mbit/s Full duplex").
the switch port that is connected directly to the VNF (for
4. Check if the speed and duplex setting of the gNB-DU F1
example, they are
port is consistent with
both "Autodetect" or both "1000 Mbit/s Full duplex").
the switch port that is connected directly to the gNB-DU
Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check the connection between gNB-CU and gNB-DU.

If GPS is configured as a reference clock, perform the
2. Check if the gNB-CU or gNB-DU is operational.
following:
1. Check the GPS receiver installation.
3. Check if the speed and duplex setting of the VNF F1
2. Check the GPS receiver status.
port is consistent with
3. Check the connection between the GPS receiver and
1. Determine the gNB of the ASIR-HUB RMOD used for
ASIx.
the cell.
switch port that is connected directly to the VNF (for
2. Use ASiManager
example, they are to connect to the gNB identified in step
If the TOP signal is configured as a reference clock,
1 and check faults reported in ASiManager.
perform the following:
Follow
both instructionsorofboth
"Autodetect" those faultsMbit/s
"1000 and correct the fault
Full duplex").
1. Determine the Master gNB
Check the connection to theofTOP
the ASIR-HUB
server RMOD
situation.
used for the cell.
4.
2. Check if the speedtoand
Use ASiManager duplex
connect to setting
the gNBofidentified
the gNB-DU F1
in step
port is consistent with
1 and check faults reported in ASiManager. Follow
instructions of those faults and correct the fault situation.
Note: Perform
the switch port the
thatsteps below in directly
is connected the listed
to order until the
the gNB-DU
alarm disappears:
(for example, they are

1. Check
both if SCTP association
"Autodetect" is established
or both "1000 from the LTE
Mbit/s Full duplex").
eNB.
The fault will be cleared automatically.
2. Check if the eNB is operational.

3. Check if EN-DC X2 Setup request message from the

Check
LTE theisconfiguration.
eNB received by gNB.

4. Check if EN-DC X2 Setup Response message is sent to

eNB
Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check the connection with the AMF.

Note: Perform the steps below in the listed order until the
2. Check if the AMF is operational.
alarm disappears:
3. Check if the speed and duplex setting of the NG port is
1. Check the connection with the AMF.
consistent with
Note: Perform
the switch port the
thatsteps below in directly
is connected the listed
to order until(for
the gNB the
2. Check if the AMF is operational.
alarm
example,disappears:
they are
both "Autodetect" or both "1000 Mbit/s Full duplex").
3. Check if the speed and duplex setting of the NG port is
1. Check the connection with the peer gNB/ng eNB.
consistent with
Note: Perform
the switch port the
thatsteps below in directly
is connected the listed
to order until(for
the gNB the
2. Check if the peer gNB/ng eNB is operational.
alarm
example,disappears:
they are
both "Autodetect" or both "1000 Mbit/s Full duplex").
3. Check if the speed and duplex setting of the Xn port is
1. Check the connection with the peer gNB/ng eNB.
consistent with
When snapshot
the switch is triggered,
port that but not
is connected collected,
directly to the check
gNB (forthe
2. Check if the peer gNB/ng eNB is operational.
reason
example, in they
the Alarm:
are
-both
New"Autodetect"
snapshot can or be blocked
both "1000 ifMbit/s
thereFull
is an ongoing
duplex").
3. Check if the speed and duplex setting of the Xn port is
snapshot in process
consistent with
- Too many snapshots: limit the number of snapshots per
the switch port that is connected directly to the gNB (for
Fault ID (+CU or +DU) to 5 per 24 hours
example, they are
- Snapshot taken too often: set the minimum time interval
both "Autodetect" or both "1000 Mbit/s Full duplex").
per Fault ID (+CU or +DU) between snapshots to 15
minutes
- Other reason in snapshot collection process (collect OAM
logs to resolve reason)
When snapshot is collected, lack of snapshot data can be
read from the Alarm.
Follow the steps below to resolve the fault:

1. In case of NR-LTE sharing, try to connect Radio Unit

HW version >= Rel 5.1 (NAHKA)
2. In case NR-LTE sharing is not intended, RF sharing
Follow the steps below to resolve the fault:
should be disabled in SCF
3. Replace the alarming unit with the unit planned in 5G
1. In case of NR-LTE sharing, try to configure the RF
BTS planned HW configuration (BTS profile).
sharing mode correctly on both NR and LTE side (NR as
master and LTE as slave)
If fault recovery fails, check the nrRelLteId associated with
2. In case NR-LTE sharing is not intended, RF sharing
the NR CELL.
should be disabled in SCF
Check if LTE eNB provided via nrRelLteId is available.
3. Replace the alarming unit with the unit planned in 5G
BTS planned HW configuration (BTS profile).
OAM performs a configuration change. Fault will be
canceled after Site reset.

Download snapshot from the node. Check which fault has

triggered the snapshot.

Check snapshot on external server. Check which fault has

triggered snapshot.

Collect technical logs from the BTS to clear the alarm

raised by this fault.
Internal logs collected by this process can only be
analyzed by Nokia R&D.
Replace the optical transceiver module with a
Additionally:
recommended module.
- Check the alarm history to confirm the frequency of fault
4527 in a specific eNB.
- Check the alarm history for other alarms in the same eNB
Replace
that mightthe
beoptical transceiver
related, especiallymodule
alarms with
with aRadio
module
alarms
recommended which can support extended temperature.
If an alarm with fault 4527 frequently occurs in the same
eNB, alarms with the same faults mentioned above are
present in the same
Note: Perform eNB,below
the steps or theineNB performance
the listed is the
order until
degraded, then
alarm disappears:collect a snapshot and open a case for
Nokia R&D log analysis.
1. Check the connection with the eNB.
Each RU crash are reported with own 4527 fault
Investigate the fault root cause. Lock/Unlock BTS.
2. Check if the eNB is operational.

3. Check if the speed and duplex setting of the VNF X2

port is consistent with
RAU (ASIx): Site reset
RAU (ABIx):
the switch FSP
port thatreset
is connected directly to the VNF (for
example, they are

both "Autodetect" or both "1000 Mbit/s Full duplex").

Check peer (MeNB) configuration / SW version to enable
support of needed extension.

Workaround: Modification of SgNB parameter

dlDataSplitMode from "dlOverX2U" or "dlOverF1UX2U" to
Check the connection with the third-party tool.
"dlOverF1U". This disables data transmission over X2-U
but it is system wide and disables it also for MeNBs which
would otherwise support it.

1. Check that the cables/fibers are connected to the correct

connectors.
2. Check that the interface at the far-end is switched on
and has correct auto-negotiation settings.
3. Check whether there are active alarms at the far end. If
1. Check that the cables are connected to the correct
there are, follow the instructions for handling those alarms.
connectors.
4. To verify that the hardware of the interface works
2. Check that the interface at the far-end interface is
correctly, connect a loop cable and check whether the
switched on.
alarm disappears.
3. Check whether there are active alarms at the far end. If
1.
5. Check that the optical transceiver
length/type module is does
of the cable/fiber correctly
not
there are, follow the instructions for handling those alarms.
installed
introduceand plug-out/plug-in
excessive attenuation optical transceiver
or that module.
the cable/fiber is
cut somewhere.
2.
6. Check for
thatoptical transceiver
the Ethernet validity
interface has(could
correctbeauto-
the wrong
type) and insert
negotiation a compliant
settings, fitting to optical
the transceiver
far-end module.
interface.
Execute general configuration checks:
7. With an optical
- Configuration of Ethernet
primary CRL interface:
serverCheck that the
IP address and port.
3. CheckSFP
inserted that module
the electrical contacts of the optical
- Configuration of DNS server IP address. and
matches the fiber type
transceiver
wavelength module are clean
of the Gigabit from dust,
Ethernet dirt, or water.
link provided.
Check remote peers and intermediate network element
Replace
4. Replacethethe
faulty optical
optical transceiver.
transceiver Notewith
module thataonly the
module
interconnections.
optical transceiver
recommended is faulty, not the entire hardware unit.
by Nokia.
Check the LDAP connection towards the Certificate
Revocation List server.
Note that only the optical transceiver might be faulty, and
Check the size of the file at the Certificate Revocation List
not
1. the entire
Check hardware
the CMP unit.
configuration.
server.
2. Checkconnectivity
Perform for CA server reach-ability.
checks related to primary CRL
3. If none of the above work, contact CA
servers.
administrator/Nokia service personnel
The customer needs to return the equipment to Nokia for
vendor certificate re-installation

Update trust anchors.

1. Check the cable connectivity on ToP master side.

2. Check the TOP configuration both in BTS and ToP
master sides.

1.Check for duplicate IPv6 addresses configured in the

BTS.

2.Change or delete the identified duplicate IPv6 addresses.

Check the validity of the username and password of the
account.

Check the authentication credential provided by the peer

(certificate).

Check the IKE profile configuration of the Network Element

5GC001082: Classical gNB software

Management

5GC001082: Classical gNB software

Management
5GC001082: Classical gNB software
Management

5GC000352: GNSS receiver FYGC

5GC000313: Timing over Packet with Phase

Synchronization
5GC000609: ToP with Phase Sync Resiliency
5GC000426: 5G Transport, Synchronization and
Security Features rebasing on ASIK for Classical
5GC000313: Timing over Packet with Phase
5G NodeB
Synchronization
5GC000609: ToP with Phase Sync Resiliency
5GC000426: 5G Transport, Synchronization and
Security Features rebasing on ASIK for Classical
5GC000952: Recovery for Classical gNB
5G NodeB

5GC000952: Recovery for Classical gNB

5GC000631: ABIL & ASIK - new SW deployment

5GC000540: 5G18A operability functionality

porting to classical BTS deployment
5GC000507: Fault triggered snapshot

5GC000540: 5G18A operability functionality

porting to classical BTS deployment
5GC000507: Fault triggered snapshot

5GC000540: 5G18A operability functionality

porting to classical BTS deployment
5GC000371: gNB recovery log collecting

5GC001179: BTS Fronthaul CPRI 7 - 10/25GE

QSFP+/QSFP28 Base Line
5GC000847: BTS Fronthaul CPRI 7 - 10GE
SFP+ Dual Fiber Base Line
5GC000848: BTS Fronthaul CPRI 7 - 10/25GE
5GC001179: BTS Fronthaul CPRI 7 - 10/25GE
SFP+/SFP28 Dual Fiber Base Line
QSFP+/QSFP28 Base Line
5GC000849: BTS Fronthaul CPRI 7 - 10GE
5GC000847: BTS Fronthaul CPRI 7 - 10GE
SFP+ Single Fiber
SFP+ Dual Fiber Base Line
5GC000850: BTS Fronthaul CPRI 7 - 10GE
5GC000848: BTS Fronthaul CPRI 7 - 10/25GE
5GC000577:
SFP+ CWDMTRS Support of NSA interfaces (X2
SFP+/SFP28 Dual Fiber Base Line
and S1-U) over
5GC000851: IPv4
BTS / IPv6 CPRI 7 - 10/25GE
Fronthaul
5GC000849: BTS Fronthaul CPRI 7 - 10GE
5GC000426:
SFP28 Single5G Transport, Synchronization and
Fiber
SFP+ Single Fiber
Security Features rebasing on ASIK for Classical
5GC000850: BTS Fronthaul CPRI 7 - 10GE
5G NodeB
5GC000718:
SFP+ CWDMF1 cell management
5GC000540:
5GC000851: 5G18A operability
BTS Fronthaul CPRI functionality
7 - 10/25GE
porting
SFP28 to classical
Single FiberBTS deployment
5GC000952: Recovery for Classical gNB
5GC000540: 5G18A operability functionality
porting to classical BTS deployment
5GC000952: Recovery for Classical gNB
5GC000371: gNB recovery log collecting
5GC000475: SgNB Addition and Release for
NSA mode 3x operation

5GC001097: Basic PCMD For NSA

5GC000380: 10GBase-SR Optical GE Interface

5GC000848: BTS Fronthaul CPRI 7 - 10/25GE
SFP+/SFP28 Dual Fiber Base Line
5GC000624: 10/25GBase-SR Optical GE
Interface
5GC000264: IPsec on Backhaul
5GC000388: 1000Base-BX Optical GE Interface
5GC000426: 5G Transport, Synchronization and
5GC000851: BTS Fronthaul CPRI 7 - 10/25GE
Security Features rebasing on ASIK for Classical
SFP28 Single Fiber
5G NodeB
5GC000385: 1000Base-SX Optical GE Interface
5GC000380:
5GC000387: 10GBase-SR
1000Base-ZX Optical
Optical GE
GE Interface
Interface
5GC000848:
5GC000849: BTS Fronthaul CPRI 7 - 10/25GE 10GE
SFP+/SFP28 Dual Fiber Base Line
SFP+ Single Fiber
5GC000624:
5GC000381: 10/25GBase-SR
Small Form Factor Optical GE
Pluggable
Interface
SFP/SFP+/SFP28 slot
5GC000323: Operator Certificate Management
5GC000388:
5GC000386: 1000Base-BX Optical
Optical GE
GE Interface
Interface
& Multi Layer 1000Base-LX
of CA
5GC000851:
5GC000625: BTS Fronthaul CPRI
10/25GBase-LR 7 - 10/25GE
Optical GE
5GC000540: 5G18A operability functionality
SFP28 Single Fiber
Interface
porting to classical BTS deployment
5GC000385:
5GC001179: 1000Base-SX Optical
CPRI 7GE Interface
5GC000952: BTS Fronthaul
Recovery for Classical - 10/25GE
gNB
5GC000380:
5GC000387:
QSFP+/QSFP28 10GBase-SR
Base LineOptical
1000Base-ZX Optical GE
GE Interface
Interface
5GC000848:
5GC000850: BTS Fronthaul CPRI 7 - 10/25GE
5GC000849: 10GE
SFP+/SFP28
SFP+ Single Dual Fiber Base Line
CWDMFiber
5GC000624:
5GC000382: 10/25GBase-SR
5GC000381: Small Form Factor
10GBase-LR Optical
GE GE
Pluggable
Optical Interface
Interface
SFP/SFP+/SFP28
5GC000847: BTS slot
Fronthaul CPRI 7 - 10GE
5GC000323: Operator Certificate Management
5GC000388:
5GC000386:
SFP+ 1000Base-BX
1000Base-LX Optical GE
Base Line Optical GE Interface
Interface
& MultiDual
LayerFiber
of CA
5GC000851:
5GC000625: BTS Fronthaul CPRI
10/25GBase-LR 7 - 10/25GE
Optical GE
5GC000540: 5G18A operability functionality
SFP28 Single Fiber
Interface
porting to classical BTS deployment
5GC000385:
5GC001179: 1000Base-SX Optical
CPRI 7GE Interface
5GC000952: BTS Fronthaul
Recovery for Classical - 10/25GE
gNB
5GC000323:
5GC000387:
QSFP+/QSFP28 Operator
Base Certificate
1000Base-ZX Management
Line Optical GE Interface
& Multi Layer BTS
5GC000849:
5GC000850: of CAFronthaul CPRI 7 - 10GE
5GC000540:
SFP+ Single 5G18A operability functionality
CWDMFiber
porting to classical
5GC000381:
5GC000382: Small BTS
Formdeployment
10GBase-LR Factor Pluggable
Optical GE Interface
SFP/SFP+/SFP28
5GC000847: BTS slot
Fronthaul CPRI 7 - 10GE
5GC000540: 5G18A operability functionality
5GC000386:
SFP+ Dual 1000Base-LX
Fiber Base Line Optical
porting to classical BTS deployment GE Interface
5GC000625: 10/25GBase-LR Optical
5GC000323: Operator Certificate ManagementGE
Interface
& Multi Layer of CA
5GC001179:
5GC000952: BTS Fronthaul
Recovery CPRI 7 gNB
for Classical - 10/25GE
5GC000609:
QSFP+/QSFP28 ToPBase
with Phase
Line Sync Resiliency
5GC000313:
5GC000850: Timing over Packet
BTS Fronthaul CPRIwith Phase
7 - 10GE
Synchronization
SFP+ CWDM
5GC000426:
5GC000382: 5G Transport,Optical
10GBase-LR Synchronization
GE Interfaceand
Security Features
5GC000847: BTS rebasing
Fronthaul on ASIK
CPRI 7 for
- Classical
10GE
5GC000952: Recovery for Classical gNB
5G
SFP+NodeB
Dual Fiber Base Line Synchronization and
5GC000426: 5G Transport,
Security Features rebasing on ASIK for Classical
5G NodeB
5GC000307: Transport IPV4/IPv6 stack
enhancement
5GC000324: Operator Account Management on
gNB
5GC000540: 5G18A operability functionality
porting to classical BTS deployment
5GC000264: IPsec on Backhaul
5GC000426: 5G Transport, Synchronization and
Security Features rebasing on ASIK for Classical
5G NodeB
5GC000264: IPsec on Backhaul
5GC000426: 5G Transport, Synchronization and
Security Features rebasing on ASIK for Classical
5G NodeB
5GC000264: IPsec on Backhaul
5GC000426: 5G Transport, Synchronization and
Security Features rebasing on ASIK for Classical
5G NodeB
Restriction status

No
No

Yes

No
Yes

Yes

No
No

No
Changes between issues 02 Fault ID
DRAFT and 02A

Changed 16

Changed 23

Changed 28

29
30

Changed 94

Changed 95

1806

1811

1815

1817

1818

1819

1850

Changed 1898

1900
1901

1907

1911

1928

1932

1936

1937

New 1981

Changed 2056

New 2906

New 2911

New 2912
New 2913

New 2914

4001

4011

Changed 4019

4026

Changed 4073

4077

4078

4079

4080

4082
4083

4085

4122

4123

4124

4125

4126

4145

Changed 4210

4266

4267

4268
4269

New 4296

New 4298

New 4323

Changed 4350

4352

4385

4411

4414

4415

Changed 4440

4441
4444

4445

4446

Changed 4447

4449

4450

New 4451

4452

4454

4455

4456

4460
4461

4472

4473

New 4478

New 4479

4490

4495

New 4496

New 4497

New 4498

4505

4506
4507

4508

4514

4515

4516

4517

4520

4523

4524

New 4527

New 4544

New 4545
6203

6293

New 6918

New 7309

New 7702

New 7703

New 7900

New 8000

Changed 61029

New 61030

Changed 61050

61074
Changed 61079

61510

61605

61606

New 61616

61618

New 61631

61632

61642

New 61644

New 61645

New 61646
Fault Name Used in Product

Unit temperature is high 5G BTS

Difference between BTS master clock and 5G BTS

reference frequency

No connection to unit 5G BTS

Unit synchronization failed 5G BTS

Incompatible SW version detected 5G BTS

Obsolete SW version detected 5G BTS

BTS time not corrected 5G BTS

Error in file server during file download type 5G BTS

File corrupted in SW download 5G BTS

BTS SW download or activation failed 5G BTS

Unknown HW resource 5G BTS

Unit not supported by running SW 5G BTS

Communication failure 5G BTS

Baseband bus configuration was rejected 5G BTS

Not able to synchronize a baseband bus 5G BTS

Oven oscillator heating failure 5G BTS

BTS master clock tuning failure 5G BTS

Oven oscillator clock missing 5G BTS

SW corrupted 5G BTS

PPS reference missing 5G BTS

RF Module configuring failed 5G BTS

RF Module critical file not found 5G BTS

TX out of order 5G BTS

RX out of order 5G BTS

FPGA SW update failed 5G BTS

No module fan detected 5G BTS

Unit (module) temperature is high 5G BTS

Unit (module) dangerously overheating 5G BTS

FR module reset requested 5G BTS

Firmware SW mismatch 5G BTS

Unit (antenna submodule) temperature is high 5G BTS

Unit (antenna submodule) dangerously 5G BTS

overheating

Unit (antenna submodule) power good interrupt 5G BTS

Unit (antenna submodule) SW download failure 5G BTS

Unit (antenna submodule) PLL unlocked 5G BTS

BTS reset required 5G BTS

GPS Receiver alarm: control interface not 5G BTS

available

Master unit has lost connection to the slave 5G BTS

unit

Toggling: <Fault name> 5G BTS

Fan vendor not detected 5G BTS

FSP overheating 5G BTS

Cooling fan broken 5G BTS

Cooling fan speed decreased 5G BTS

Cooling fan is over speeding 5G BTS

SW fallback 5G BTS
SW fallback 5G BTS

SW fallback 5G BTS

GPS receiver alarm: not tracking satellites 5G BTS

GPS receiver alarm: survey in progress 5G BTS

GPS receiver alarm: no stored position 5G BTS

GPS receiver alarm: position questionable 5G BTS

GPS receiver alarm: EEPROM invalid 5G BTS

Validation of signed file failed 5G BTS

External GPS receiver in holdover 5G BTS

Failure in verifying the signature of a signed 5G BTS

software release

Failure in verifying a signed software release 5G BTS

Unsigned software release has been 5G BTS

successfully downloaded
Failure in downloading software due to missing 5G BTS
software signature

Constellation mode not supported 5G BTS

ToP reference missing 5G BTS

ToP configuration mismatch 5G BTS

RAP or VM unavailable for Cloud 5G BTS

No connection between primary and BTS 5G BTS

extension system module

PPS reference from backplane missing. 5G BTS

All RAPs Out Of Service 5G BTS

EFaultId_NodebFiberLengthDeploymentExcee 5G BTS
dedAl

EFaultId_RuFiberLengthDifferentialExceededAl 5G BTS

F1AP Setup fails upon non response from 5G BTS

gNB-CU

Trust Chain Certificate Installation Failure 5G BTS

Trust Chain Certificate Removal Failure 5G BTS

EFaultId_F1SctpEndpointAl 5G BTS

EFaultId_X2SctpSetupAl 5G BTS

EFaultId_F1SctpSetupAl 5G BTS

F1AP Reset fails upon non response from 5G BTS

gNB-DU

F1AP Reset fails upon non response from 5G BTS

gNB-CU

EFaultId_RapFileTransferFailureAl 5G BTS

Phase error exceeds the interference limit 5G BTS

F1AP Setup fails upon failure response from 5G BTS

gNB-CU

F1AP protocol error detected by gNB-DU 5G BTS

F1AP protocol error detected by gNB-CU 5G BTS

Scale-out recommended 5G BTS

Scale-in recommended 5G BTS

5G BTS incomplete VM initialization 5G BTS

5G BTS failed VM initialization 5G BTS

Antennas assignment not available 5G BTS

Failure detected on assigned antennas 5G BTS

No X2 link available 5G BTS

gNB configuration update failure 5G BTS

E1 Setup Failure after retries 5G BTS

E1 SCTP Endpoint Failure 5G BTS

E1 SCTP Setup Failure 5G BTS

EFaultId_NgSctpEndpointAl 5G BTS

EFaultId_NgSctpSetupAl 5G BTS
EFaultId_XnSctpEndpointAl 5G BTS

EFaultId_XnSctpSetupAl 5G BTS

Failure in troubleshooting data collection 5G BTS

Radio Module does not support RF sharing 5G BTS

RF sharing mode conflict 5G BTS

F1 Cell activation failed due to X2 link 5G BTS

unavailable

Configuration change requiring RAP restart 5G BTS

detected

Troubleshooting data available on CU 5G BTS

Troubleshooting data available on External 5G BTS

Server

Radio Diagnostic Files collected 5G BTS

Non approved SFP module on unit $U, 5G BTS

interface $IF

Restricted use SFP module on unit $U, 5G BTS

interface $IF
Transport layer connection failure in X2 5G BTS
interface

5G BTS configuration failed 5G BTS

Non critical SW Component failure 5G BTS

gNB-CU-CP initiated E1AP Reset failure due 5G BTS

Timer Expiry

E1 Setup Failure Response after retries 5G BTS

gNB-CU-UP initiated E1AP Reset failure due 5G BTS

Timer Expiry

Remote node does not support NR RAN 5G BTS

Container Extension Header of GTP-U

Failure in connection between BTS and 3rd 5G BTS

party tool

LOS on $UNIT, $INTERFACE 5G BTS

Dead Peer Detected 5G BTS

Missing or non-compliant SFP module on unit 5G BTS

$U, interface $IF

CRL Update Failure 5G BTS

SFP HW Failure on unit $U, interface $IF 5G BTS

Automatic BTS Operator Certificate retrieval 5G BTS

unsuccessful

BFD-$BFDID down in ingress 5G BTS

BFD-$BFDID down in egress 5G BTS

Vendor BTS certificate is about to expire 5G BTS

BTS Trust Anchor due to expire 5G BTS

ToP master service $IP unusable 5G BTS

Dup Addr detected- 5G BTS

$DUPLICATEIPV6ADDRESS

BTS Local OAM user account $A has been 5G BTS

locked

IKE authentication failure 5G BTS

IKE SA failure 5G BTS

IPSec SA failure 5G BTS

Detecting Unit Source

ASIx ASIx
ABIx

ASIx ASIx

ASIx ASIx
ABIx
5GRU

ASIx, ABIx ASIx, ABIx

ASIx 5GRU
ASIx
ABIx

ASIx ASIx

ASIx TIME

ASIx ASIx

ASIx 5GRU
ASIx

ASIx 5GRU
ASIx
ABIx
ASIx 5GRU
ASIx
ABIx

ASIx ABIx
5GRU
AMxx

ASIx ASIx, ABIx, 5GRU

RAC, ASIx 5GRU, ASIx, ABIx, RAC

ASIx ABIx

ASIx ABIx
OptIF

ASIx ASIx

ASIx 5GRU

ASIx GNSSE, SYNCHUBBTS

ASIx 5GRU
RU 5GRU

RU 5GRU

RU, RF 5GRU

ASIx ABIx

RU 5GRU

RU 5GRU
RU 5GRU

RU 5GRU

RAC RAC, ASIx, ABIx, RU

ASIx GNSSE

ASIx ASIx, ABIx

RAC 5GRAC
ASIx
ABIx
GNSSE
5GRU
ASIx FAN

ASIx ABIx

ASIx Fan

ASIx FAN

ASIx Fan

ASIx ASIx
ASIx ASIx

ASIx ASIx

ASIx GNSSE

RAC gNB-CU

RAC gNB-CU
RAC gNB-CU

RAC RAC

ASIx ASIx

RAC gNB-CU

RAC, ASIx RAC, RAP

RAC, RAU gNB-CU-UP

RAC, RAU gNB-CU-CP, gNB-CU-UP

RAC, RAU gNB-CU-UP

RAC SERVEDAMF

RAC SERVEDAMF
RAC GNBADJGNB

RAC GNBADJGNB

RAC, RAU, RU TRBLCADM

ASIx 5GRU

ASIx ASIx

RAC, ASIx gNB-CU

RAC NRDU

RAC, RAU, RU TRBLCADM

ASIx ASIx

RAU,RU SFP

RAU,RU SFP
RAC LTEENB

RAC, ASIx RAC, RAP

RAU, ASIx, ABIx RAU

RAC, RAU gNB-CU-CP

RAC, RAU gNB-CU-UP

RAC gNB-CU-UP

RAC, RAU RAC, RAU

ASIx ETHLK,SFP

RAC, RAU IKEP

ASIx SFP

ASIx, RAC CERTHENT

ASIx SFP

ASIx, RAC CERTHENT

RAC BFD

ASIx RAP

ASIx, RAC CERTHENT

ASIx TOP

FCT IPIF

ASIx, RAC gNB

RAC, RAU IKEP

RAC, RAU SECPOL

Meaning State

The temperature of the unit/module Start / Cancel

exceeds the threshold value.

The reference frequency that the BTS Start / Cancel

The baseband bus synchronization has Start / Cancel

failed.

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

The output signal of the OXCO is missing Start / Cancel

and the ASIx cannot deliver the 30.72
MHz System Clock required by the other
units.
A corrupted SW file in the FLASH is Start
detected. The unit cannot perform a
complete start-up.

The reference clock monitoring has Start / Cancel

The RAP TX path cannot be used. Start

The RX path in the RAP is faulty. Start

The FPGA software update has failed. Start

RF Module cannot identify the fan vendor Start / Cancel

or the fan is not installed.

Validated module temperature exceeds Start / Cancel

or is equal to the predefined maximum
value allowed.

The validated sensor temperature Start / Cancel

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

The FR module has detected a transient Start / Cancel

problem or DFE FPGA SW update that
requires a reset recovery.

The SW update of the AirScale module Start

(ABIx or ASIx) has failed or the SW is
corrupted.

Validated antenna submodule Start / Cancel

temperature is higher than the predefined
maximum allowed value.

The validated sensor temperature for Start / Cancel

Antenna submodule PLL unlocked. Start / Cancel

This fault notifies the operator that the Start

The fault is ignored until the GPS

receiver has reached commissioned
Connection to SW entity has been lost. Start / Cancel
state.

The BTS Fault, whichever fault name is Start / Cancel

Fan is not running although the control is Start / Cancel

higher than 0.

Speed of the fan is deviating too much Start / Cancel

from the required control.

Fan is running faster than required. Start / Cancel

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

4083:
Source unit requests SW fallback
because of a critical problem that
occurred during SW update, that is,
configuration data migration failed.

4085:
Transport
There is noSW on the position
accurate source unit
stored in Start / Cancel
indicates a
the EEPROM. need for software fallback.

The receiver is used in the stored Start / Cancel

position but has been moved to a new
position.

The GPS receiver detected that one or Start / Cancel

more EEPROM segments were found to
be corrupted at reset and had to be set to
their factory default settings.
SW file validation against its signature Start / Cancel
failed.

External GPS/GNSS receiver module Start / Cancel

has lost satellite visibility and is currently
operating in a holdover mode.

There has been a failure in validation of Start / Cancel

the software release signature for the
software release that has just been
requested to be downloaded to the BTS
system module because information of
There has been a failure in validation of Start / Cancel
either Hash Container file or Hash
the hash of the questioned SW files for
Container Signature file is not present in
FCT, except of Hash Container file or
the downloaded TargetBD.xml, or the
Hash Container Signature file in the
verification of the software signature files
software release that has just been
An
hasunsigned
failed. software release has been Start / Cancel
requested to be downloaded to the BTS
downloaded to a BTS system module
system module. The reason is that the
that is currently running a software
hash value of the questioned SW file is
release that implements software
missing, or SiteOAM fails to verify the
signature checking.
hash of the questioned SW file.
There has been a failure in validating the Start / Cancel
software signature for the software
release that has been requested to be
downloaded to the BTS system module
because there is no software signature
The BTS has detected an incompatible Start / Cancel
for the release, and only signed software
operator-selected constellation mode for
can be installed.
the GNSS receiver.

The ToP (Timing over Packet) signal is Start / Cancel

unavailable or unusable as the reference
clock source.

Configured ToP (frequency/phase) Start / Cancel

doesn't match with configured sync mode
(frequency/phase) and hence, the
requested ToP configuration cannot
proceed.
In the case Source = 5GRAU (ASIx ): Start
5GRAU is not available for 5G BTS
because of the 5GRAU failure, 5GRAU
element reset or Front Haul breakdown.
Connection to a secondary unit that Start / Cancel
In the case Source = 5GRAC:
belongs to the BTS Dual ASIx
VNFC crashed and is not available.
configuration has been lost.

BTS Secondary unit (system module) in Start / Cancel

dual core configuration has lost the 1PPS
reference signal at the 1pps/ToD
backplane interface towards the primary
unit.
This fault indicates that all of the RAPs Start / Cancel
(RAU&RU) under the same RAC have
failed.
Note: this fault is raised only in a multi-
RAP system.
The NodeB has detected that the Start
deployed Fiber Length between the RAU
& RU has exceeded the supported
distance by the software. If this distance
is exceeded, the RU cannot function and
In a configuration where two optic fibers Start
this fault occurs. This applies to Cloud
are deployed to a RU from a RAU, the
BTS and 5G BTS.
maximum separation between those two
fibers is 1 km (1,000 meters, 3,280.84
feet). If this distance is exceeded, the RU
This fault indicates that the F1AP: F1 Start / Cancel
cannot function and this fault is raised.
Setup procedure initiated by gNB-DU
This applies to Cloud BTS and 5G BTS.
fails after a few retries upon lack of
Two fibers are deployed from a single
response from gNB-CU.
modem board.
Installation of an additional operator Start / Cancel
certificate (not including the RAP's own
trust chain) into the trust pool on the
System Module for the RAP has failed,
even though it succeeded on the VNF.
Removal of an additional operator Start / Cancel
certificate (not including the RAP's own
trust chain) from the trust pool on the
System Module for the RAP has failed,
even though it succeeded on the VNF.
The transport path (SCTP) for connection Start / Cancel
between gNB-CU and gNB-DU is broken.
This might be because of an unplugged
cable between them. There is no
transport path available to continue
The transport path (SCTP) for connection Start / Cancel
operation on the faulty connection
to the LTE eNB has failed to be
between gNB-CU and gNB-DU.
established. This might be because of an
unplugged cable to the eNB. There is no
transport path available to continue
The transport path (SCTP) for connection Start / Cancel
operation on the faulty connection with
between gNB-CU and gNB-DU has failed
the eNB.
to be established. This might be because
of an unplugged cable between them.
There is no transport path available to
This fault indicates that the F1AP: Reset Transient
continue operation on the faulty
procedure initiated by gNB-DU fails after
connection between gNB-CU and gNB-
a few retries upon lack of response from
DU.
gNB-CU.
This fault indicates that the F1AP: Reset Transient
procedure initiated by gNB-DU fails after
a few retries upon lack of response from
gNB-CU.
File transfer to RAP failure. Start

This fault indicates that the absolute Start / Cancel

phase error of the BTS exceeds the limit
of 1.5 us. This can occur when:

1) The absolute value of

This fault indicates that the F1AP: Setup Start / Cancel
measured/estimated phase error of the
procedure initiated by gNB-DU fails after
BTS has exceeded the limit of 1.5 us,
a few retries upon lack of response from
gNB-CU.
OR
This fault indicates that a Protocol error Transient
has been
2) The detected
BTS has lostinall
a phase
received F1AP
sync
message
reference or is reported
sources, from not
but does the have
gNB-
CU.
sufficient history data for holdover.
OR
This fault indicates that a Protocol error Transient
3)
hasThe
beenBTS is synchronized
detected in a receivedby reference
F1AP
which
message or is reported from theholdover
has capability to internal gNB-
(Sync
DU. Hub Master/GNSS) which reports
the phase error of the provided sync
Need for
signal. Scale-out
The absoluteisvalue
detected
of estimated Active / Cleared
total phase error in the "slave" side
exceeds the limit of 1.5 us or source
reports that its holdover has expired.
Need for Scale-in is detected Active / Cleared

Timeout happened and cardinality of Start / Cancel

configured Cplane and Uplane VM
instances have not been completely met
during the start-up phase.
Timeout happened and cardinality of Start
configured Cplane and Uplane VM
instances have not been met during the
start-up phase.
The antennas' assignment for the cell is Start / Cancel
not available due to reasons such as lack
of configuration or misconfiguration or
reset trigger via ASiManager. This fault is
only applicable to a cell using ASiR-HUB.
Failure was detected in the antennas Start / Cancel
assigned to the cell. It could be a
hardware issue, configuration issue or
reset/block of an antenna performed via
the ASiManager. This fault is only
There is no X2-C link for the connection Active / Cleared
applicable to a cell using ASiR-HUB.
to the LTE eNB available. No NSA UE
can connect to the gNB.

The eNB configuration update procedure Start

has failed.

This fault indicates that the E1AP: E1 Active / Cleared

Setup procedure initiated by gNB-CU-UP
fails after retries upon non response from
gNB-CU-CP.
The transport path (SCTP) for connection Active / Cleared
between gNB-CU-CP and gNB-CU-UP is
broken.

The transport path (SCTP) for connection Active / Cleared

between gNB-CU-CP and gNB-CU-UP
has failed to be established.

The transport path (SCTP) for the Start / Cancel

connection between gNB and AMF is
broken. This might be caused by an
unplugged cable between them. There is
no transport path available to continue
The transport path (SCTP) for the Start / Cancel
the operation on the faulty connection
connection to the AMF has failed to be
between gNB and AM.
established. This might be caused by an
unplugged cable to the eNB. There is no
transport path available to continue the
operation on the faulty connection with
the eNB.
The transport path (SCTP) for the Start / Cancel
connection between local gNB and peer
gNB/ng eNB is broken. This might be
caused by an unplugged cable between
them. There is no transport path
The transport path (SCTP) for the Start / Cancel
available to continue the operation on the
connection between local gNB and peer
faulty connection between local gNB and
gNB/ng eNB has failed to be established.
peer gNB.
This might be caused by an unplugged
cable between them. There is no
This fault indicates that a user- Start / Cancel
transport path available to continue the
configurable BTS fault has triggered an
operation on the faulty connection
internal snapshot and snapshot collection
between local gNB and peer gNB.
has failed (partially or completely).
Detected RF module does not support Start / Cancel
commisioned RF sharing type.

CPRI RF modules in NR-LTE sharing:

RM HW version should be >= Rel 5.1
There is a RF sharing mode conflict on Start / Cancel
(NAKHA)
the Nokia CPRI R5.1 radio to be shared
by NR with LTE technology such as :
(1) NR is in shared mode and peer
technology (LTE) is in standalone mode
This fault indicates that the gNB-CU Start / Cancel
or (2) NR in master mode and LTE also
could not activate the cell, as the X2 link
in master mode.
with the LTE eNB mapped to the NR
CELL was not established.
This fault notifies the operator that the Start
OAM has detected a configuration
change that requires DU restart in order
to be taken into use.
This fault indicates that a user- Start / Cancel
configurable BTS fault has triggered an
internal snapshot and the snapshot is
available on the node for operator
download.
This fault indicates that a user- Start / Cancel
configurable BTS fault has triggered an
internal snapshot and the snapshot has
been downloaded to an external server.
After an RU crash, RU has collected Start / Cancel
crash logs.

The third-party SFP modules complies Start / Cancel

with the system but it is not an approved
device.
It does not have EMC verification and
temperature range check. Putting it into
The SFP module has performed a limited Transient
operation may be risky.
verification of the part or has approved it
Note: The unit and interface variables
for use with other equipment, but its use
($U,$IF) will be replaced by appropriate
in this application is under restricted
hardware names.
conditions. It is not approved for use in
this application in all conditions. For
example SFP module does not support
extended temperature range required by
the BTS.
Note: The unit and interface variables
($U,$IF) will be replaced by appropriate
hardware names.
The transport path (SCTP) for connection Start / Cancel
to the LTE eNB is broken. This might be
because of an unplugged cable to the
eNB. There is no transport path available
to continue operation on the faulty
The BTS configuration failed in the C- Start
connection with the eNB.
Plane.

This alarm signifies OAM about non Start

critical SW component failure when the
non critical process crash has happened
and core dumping has been completed.
OAM triggers recovery actions.
This fault indicates that the F1AP: Reset Transient
procedure initiated by gNB-CU-CP fails
FDEV: OAM is informed what is the
after retries upon lack of response from
crashed non critical process name.
gNB-CU-UP.
This fault indicates that the E1AP: E1 Active / Cleared
Setup procedure initiated by gNB-CU-UP
fails after receiving E1 Setup Failure
response from gNB-CU-CP.
This fault indicates that the F1AP: Reset Transient
procedure initiated by gNB-CU-UP fails
after retries upon lack of response from
gNB-CU-CP.
This fault is raised when remote GTP-U Transient
tunnel endpoint (in non-standalone call:
MeNB) signals to SgNB that it does not
support "NR RAN Container" GTP-U
extension header. It is required for flow
A failure has occurred in the trace Start / Cancel
control between PDCP in SgNB and RLC
connection between the BTS and a third-
in MeNB and also to notify PDCP in
party tool.
SgNB of succesfully delivered PDCP
PDUs.
This alarm is raised when either no or an Start / Cancel
incompatible signal is received on the
interface referenced in the alarm text.
$UNIT indicates the affected module
from Equipment Management (last
A dead peer has been detected in one of Start / Cancel
element of the DN). E.g. SMOD-1.
the IPsec associations of the Transport
$INTERFACE indicates the interface on
Module.
the module following the labeling on the
There is no response to the requests
frontplate of the real HW or the
sent to the peer during the IKE SA setup,
The small form-factor
corresponding parameter pluggable
in the (SFP) Start / Cancel
the IPsec SA setup, or during DPD.
module
Management is not Model.
supported, it is expected
but
E.g.not EIF1 present, or could not be
Note: When the IPSec backup tunnel
recognized.
feature is enabled, this alarm should not
The
With small form-factor
an Ethernet pluggable (SFP)
This
be raisedfault is raisedinterface,
because ifofthe BTS
failures
the physical
cannot
when trying Start / Cancel
module
Ethernet islink
detected
is if the to
detected SFPbe slot
down. does
All
update
to set upthe Certificate
primary IPSec Revocation
tunnel in List
not
other comply with thealarms
transmission SFP modulerelated types
to this
(CRL). The failure reasons include the
"Secondary_Active_Probing_Primary"
supported
signal by the BTS element.
are suppressed.
following:
state.
- The LDAP binding fails.
Probable causes: causes forisEthernet interfaces:
-Possible
The LDAP search
reasons: empty (no CRL
- Noa SFP module
cable/fiber is is inserted
cut or there in no
is the SFP-
found),
- a cableoristhe cutLDAP
or there search
is nocontains
cable
based
cable/fiber SFPconnected
slot. to the interface
more
connected than oneto the entry.
interface
- The
the interface contacts
electrical/optical of the
signal is SFP
- The CRL signature
the signal is excessively validation
attenuatedfails.
module
excessively are corroded
attenuated or dirty, preventing
- The CRLatfile
the port theexceeds
connected the far
BTS endstorage
node
either
-limit. readataccess
the port to the SFP
the connected far endmodulenodeat
is switched off
the
is time of reading
switched off compliance data from
- The BTS certificate is part of the CRL.
the
- theSFP, or preventing
advertised technology detection of the
capabilities
module.
with auto-negotiation of both devices at
-the
The SFP module
Ethernet link dotype not is not supported.
match
The optical transceiver has reported a Active / Cleared
transmission fault condition and has
disabled the laser transmitter.

Probable causes:
A requested certificate could not be Start / Cancel
- The optical transceiver is defective.
retrieved from the certificate authority
(CA).
Note: The unit and interface variables
A requested certificate could not be
($U,$IF) will be replaced by appropriate
renewed from the certificate authority
The alarm Example:
hardware. is raised ifunit-FSM,
the BFD state for
interface Start / Cancel
(CA).
the
EIF1. session is not AdminDown and,
nevertheless, no BFD packet is received
A requested certificate could not be
at the local end during the detection time.
retrieved as the number of certificates
$BFDID indicates the BFD identifier.
The alarmfrom
received is raised if the server
repository BFD state (RA)ofor Start / Cancel
the session
certificate is not AdminDown
authority (CA) are more andthan
the
Example for alarm text:
BFD packet from the far end contains the
expected.
"BFD-10 down in ingress"
diagnostic code = 'Control Detection
The source and destination IP addresses
Time
A Expired'certificate
requested and no BFD could down Ingress
not be
This
will befault is raisedinwhen
displayed alarmthe Vendor
diagnostic BTS
info Start / Cancel
alarm
stored isinpresent.
the remaining storage available
certificate
field as below:is about to expire. The period
on the BTS. Operator
of notification in advance cleanup (e.g. via
is configurable
"Source IP addr $BFDSCRIPADDR, Dest
Example
site managerfor alarm
or text: of old, unused
NetAct)
from
IP addr1 day to 4999 days with default 90
$BFDDESTIPADDR"
"BFD-10
trust down in egress"
days.chains may be required.
The network
source and element storesIP
destination trust anchors
addresses Start / Cancel
for
will
Note:its own
beFor trust chain
displayed
RAC, in alarm
this andisdiagnostic
fault for peers.
raised info
only for
When
field asitsbelow:
the automated own oroperation
any trusttriggered
anchors by are
about
"Source
system, to for
expire
IP e.g.,or$BFDSCRIPADDR,
addr are expired,
automatic CMP this
keyalarm
Dest
is
IP sent.
addr
update $BFDDESTIPADDR"
(KUR). But not for the manual
The reference clock monitoring has Start / Cancel
operations,
detected a loss for e.g.,
of ToP manual CMP clock
reference IR or
CMP KUR triggered by operator.
signal received from the master clock
behind $IP.
- The BTS does not receive a reply from
During the IP address configuration, the Start / Cancel
ToP Master within a certain time (5 sec)
BTS tests the direct attached network
in which it has sent a sync request
whether the other already configured
message.
node on the network uses already the
- The BTS receives granted message
same IPv6 addresses on their network IP
A specific
rates from BTS
ToP local
Masteroperator account
(sync message Start / Cancel
interfaces. The DAD (Duplicate address
has
rate,been
delaylocked.
message rate), that does not
detection) detects those duplicated IPv6
The
match number of failed rate
the requested loginby
attempts
BTS. for a
addresses and prohibits the operation of
BTS local operator account has
this IPv6 address in the BTS. The Alarm
exceeded the threshold, and the account
The alarmthe
contains is corresponding
raised when the IKEaddress Start / Cancel
IPv6
has been locked on the BTS. No further
authentication
and the interface credentials
on whichprovided by
the address
logins are permitted for this account until
the
waspeer are not For
configured. valid.
each DAD event a
it is unlocked.
separate reporting shall be indicated.
The alarm is raised, if IKE parameters Start / Cancel
are not matching with the peer proposal.
It can happen due to following two
failures
--> When the 5G gNB sends or receives
This alarm is raised when the Network Start / Cancel
a failure notification as response
Element sends or receives the following
to an IKE_SA_INIT request message.
notification
The failure notifications includes:
as a response to an IKE_AUTH or
- NO_PROPOSAL_CHOSEN
CREATE_CHILD_SA request message.
- INVALID_SYNTAX
The failure notifications includes the
- INVALID_MAJOR VERSION
following:
- INVALID _IKE_SPI
- NO_PROPOSAL_CHOSEN
- INVALID_MESSAGE_ID
- TS_UNACCEPTABLE
-
- INVALID_SYNTAX
UNSUPPORTED_CRITICAL_PAYLOAD
- INVALID_MAJOR VERSION
or FAILED_CP_REQUIRED
- INVALID _IKE_SPI
--> When the 5G gNB sends or receives
- INVALID_MESSAGE_ID
a failure notification as response
-
to an IKE_AUTH request message.The
UNSUPPORTED_CRITICAL_PAYLOAD
Unit Status Unit Status Attributes

Working

Out of order

Working

Out of order Working, when btsSyncMode =

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

Working

Working
Working

Out of order

Degraded

Out of order

Degraded Degraded (there is no other

Working available and usable input
reference source to be
selected)
Working (5gNB is synchronized
Out of order
with another input reference
source)
Out of order

Out of order

Degraded

Working

Out of order

Out of order Out-of-order Always with one

Working exception related to impossibility
of upgrade SSD firmware
Working when SSD firmware is
single component that is not
Working
updated

Out of order

Degraded Degraded when one antenna

Degraded Degraded (there is no other

Working available and usable input
reference source to be
selected)
Working (5G BTS is synchronized
Out of order
with another input reference
source

N/A

Working

Degraded

Degraded Not all fans have failed: alarming

Out of order fan = out of order
All fans have failed: all fans = out
of order
Degraded Alarming fan = degraded, fan
group = degraded

Degraded

Out of order
Out of order

Out of order

Degraded Degraded (there is no other

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

Working Degraded (there is no other

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

Working

Working
Working

Working

Degraded Degraded (there is no other

Out of order

Degraded Degraded (no other ref. source

available)

Critical

Major The RU may not be operational

when this fault occurs.

Critical The RU is not operational when

this fault occurs.

Out of order

Minor
Minor

Out of order None

Minor

Major

Major
Effect Reported Alarms

The BTS operation might be decreased. 7106

This fault does not immediately affect the 7108

Requested SW version cannot be installed 7106

due to the limitations of the running SW
version.

Real time is not available. Alarms, logs, and 7108

all reports have the incorrect time.

When a tuning mode is phase

synchronization, and the alarm occurs
The BTS continues its operation with the old 7106
during start-up, the BTS will not go on Air as
file.
long as the alarm is active.

The BTS continues operation with the old 7104

software. 7105

The SW update to this BTS might not be 7105

Some operations in the BTS are being 7101

interrupted. Depending on the fault source, 7104
the BTS or cell operation is degraded or 7105
faulty.
Processing resources, cells, or the whole 7106
BTS might be out of order.

This fault can prevent the BTS from 7100

functioning when the Radio Unit is needed
for the required cell configuration.

The system clock frequency starts to drift 7108

Effects in Phase Synchronization mode:

Calls are not possible through the affected 7105

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

Calls are not possible, or problems might 7105

occur during calls through the affected cells.

There might be problems with calls made 7100

The fault can only be automatically

Calls are not possible with the affected cells 7104

RF module is not taken into use. Calls are 7104

not possible through the affected cells.

SW update needed. 7106

The antenna submodule may overheat, but 7100

there is no immediate effect on the module
operation.

Validated antenna submodule temperature 7104

The communication between the System 7100

Module and RF module might be corrupted.
Calls are not possible through the affected
antenna module.
The effect depends on the case when the 7101
fault is detected. 7104
7105

GNSS becomes unusable. 7108

The RAP resources have decreased or the 7101

RAP is faulty. 7108

Depending on the reported alarm, the fault 7100

FSP DSPs not in use; SBTS operation is 7106

degraded or faulty. 7101
7104

If the fans are not rotating as required, there 7106

is a risk that the module temperature is
rising too high.

If the fan(s) is/are not rotating as required, 7106

there is a risk that the module temperature
is rising too high.

If the fans are rotating faster than required, 7106

it creates unnecessary noise.

Source unit has inconsistent SW version. 7106

GNSS becomes unusable. 7108

Due to problem detection in Start-up, BTS 7109

remains out of order.

GNSS accuracy is not guaranteed. 7108

Software download has failed and must be 7109

retried.

Software download has failed and must be 7109

retried.

The unsigned release has been 7109

The fault has no direct impact on the current 7115

operation (BASE STATION
NOTIFICATION).

If other references are available and 7108

In the case Source = RAC:

The secondary unit is out of order or 7101
The VNFC is not operational for 5G BTS.
removed, or 40GbE connection is out of 7115
order. All cells supported by the secondary 7116
baseband modules connected to secondary
unit are disabled.
The AirScale secondary unit is not 7108
synchronized by AirScale primary unit (in
BTS runtime),
The AirScale secondary unit goes to
holdover (no other ref. source available),
RAPs are unavailable. 7120
4385 is raised with Degraded.

The RU unit in question may be out-of- 7121

service and cannot become active.
This fault is detected upon initial startup of
the NodeB, or connection of the
RU.
The RU unit in question is out-of-service 7122
and cannot become active.

This fault cancels all active faults for the

same unit.
The gNB services are degraded due to a 7107
gNB-DU out of order. 7101
This fault is detected upon initial startup of
the NodeB, or connection of the RU.

The RAP cannot set up a secure connection 7109

to the entity that the certificate is to be used
for.
The RAP may fail to set up a secure 7109
connection to a remote interface because it
is using an outdated or compromised
certificate.
All calls over the affected gNB-DU are 7107
failed.

No NSA calls can be setup over the affected 7107

eNB.

No call can be setup over the affected gNB- 7107

DU. 7101

The gNB services are degraded due to 7107

inconsistent F1AP: Reset management (i.e.
Release of existing F1AP UE contexts)
between gNB-DU and gNB-CU.
The gNB services are degraded due to 7107
inconsistent F1AP: Reset management (i.e.
Release of existing F1AP UE contexts)
between gNB-DU and gNB-CU.
RAP's SW version is incompatible with VNF. 7111

The BTS is not operational. 7101

7104
7108

The gNB services are degraded due to a 7107

gNB-DU out of order.

The gNB services are degraded. An F1AP 7107

procedure fails due to protocol error
detection.

The gNB services are degraded. An F1AP 7107

procedure fails due to protocol error
detection.

The load balancing algorithm will run out of 7123

CPUE/UPUE instances to allocate to
incoming call setup requests. Incoming call
setup requests cannot be accepted till the
CPU utilization drops below the
“reallocLoad” for the CPUE/UPUE VNFC.
Deployed resources are not utilized 7123
optimally leading to increased operating
expenses.

The cNB has started in a sub-optimal 7124

situation due to lack of VM resources.

No critical VM is available. 7125

The antenna carrier(s) for the cell is(are) 7104

deactivated. The cell is disabled.

Degraded: The availabilityStatus for the cell 7104

is degraded.
Out of order: The antenna carrier(s) for the
cell is(are) deactivated. The cell is disabled.
No NSA UE can connect to the gNB 7107

If the update of the cell was not successful, 7104

the reconfigured cells are not on air.

The gNB services are degraded due to a 7107

gNB-CU-UP out of order.

The gNB services are degraded due to a 7107

gNB-CU-UP or gNB-CU-CP being out of
order.

The gNB services are degraded due to a 7107

gNB-CU-UP being out of order.

All calls over the affected AMF are failed. 7107

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

All Xn based handover over the affected 7107

gNB peer are failed.

Snapshot is cancelled, or collecting of 7106

troubleshooting data continues at all
remaining sources, but the snapshot file
does not contain data from at least one
source.
RF module is not taken into use. 7104
7105

Shared radio cannot be used. 7104

7105

The gNB services are degraded due to a 7104

cell not being on air.

5GRAP is unavailable. 7101

None 7106

This fault has no effect on the BTS 7115

operation.

The SFP is operational and It has risk to 7100

operate.

The SFP is operational and it is risky to 7100

operate.
NSA calls over the affected eNB are failed. 7107

As long as the number of allowed 7101

autonomous BTS resets has not yet been 7105
exceeded, an autonomous BTS reset will be
performed in an attempt to recover.
The unit is not fully operational. 7101
7104

The gNB services are degraded due to 7107

inconsistent E1AP: Reset management (i.e.
Release of existing E1AP UE contexts)
between gNB-CU-UP and gNB-CU-CP.
The gNB services are degraded due to a 7107
gNB-CU-UP out of order.

The gNB services are degraded due to 7107

inconsistent E1AP: Reset management (i.e.
Release of existing E1AP UE contexts)
between gNB-CU-UP and gNB-CU-CP.
Data transfer on NSA bearer via X2-U is not 7115
possible with SN terminated split bearer
with the offending MeNB.

Flow control of user plane data is not

Possible impact on the connections over

this interface:
- voice calls or data connections cannot be
established
- remote management connectivity cannot
be established
- loss of synchronization if the interface is
used as a synchronization source
- depending on use of the Ethernet
interface, the above described impact can
The optical transceiver is not operational. 7100

The interface of the optical transceiver

module cannot be used for transmission.
The laser of the optical transceiver module
The requested service is not available. 7109
cannot be switched on.

No data or clock information is exchanged

through this interface of optical transceiver
The
module.communication link between the local 61605
and the remote peer is defective or the peer
is
The defective.
following are the possible impact on the
Transport
connections service mayinterface
over this not be available and
of the optical
calls may bemodule:
transceiver dropped.
The communication link between the BTS 61606
-andVoice
the calls
BFD or data
peer is connections cannot be
defective. Transport
established.
service may not be available and calls may
-beThe remote management connectivity
dropped.
cannot be established.
None
- There is loss of synchronization if the 7109
interface is used as a synchronization
source.

No immediate effect. If at all certificate 7109

expires without any action from operator
due to this fault, secure communication to
remote peers may fail.
5gNB performs switchover to another ToP 7108
master if available.

The remote peer to come online with the 61632

same IP address on the same subnet as the
local peer would just disable their network
interface and give an error until the situation
is resolved by the administrator.
No further logins are permitted for that 7109
account until it is unlocked.
This allows the local peer to continue
functioning without disruption, but
completely breaks IP base communications
Thethe
for IKEconnected
SA cannotnetwork.
be established. 61644

IKE SA cannot be established and 61645

subsequently no IPsec SAs can be
established.

The related IPsec SA cannot be established 61646

and used.
Reported Alarms Description

7100 HARDWARE PROBLEM

7108 is reported always

7101 reported in a case of autonomous recovery reset

will be performed
7104 CELL SERVICE PROBLEM (in case the source is
5GRU with allocated CELLs)
7105 RAT BASE STATION PROBLEM (in case the
source is 5GRAU (ASIx or ABIx or 5GRU without
allocated CELLs)

7104 CELL SERVICE PROBLEM (in case the source is

5GRU)
7105 RAT BASE STATION PROBLEM (in case the
source is ASIx)
7100 HARDWARE PROBLEM (if cells are not affected)
7104 CELL SERVICE PROBLEM (if cells are affected)

7100 HARDWARE PROBLEM (if cells are not affected)

7104 CELL SERVICE PROBLEM (if cells are affected)

7101 RESET NOTIFICATION

7104 CELL SERVICE PROBLEM (in case the source is
Radio Unit)
7105 RAT BASE STATION PROBLEM (otherwise)
7106 SINGLE RAN BASE STATION PROBLEM

10.01.2017 Detecting and Source unit aligned with

latest SBTS(SBTS16.10)

7101 RESET NOTIFICATION (when reset is being

performed)

When reset has not been triggered for any reason:

7104 CELL SERVICE PROBLEM
7101 RESET NOTIFICATION (when reset is being
performed)

7104 CELL SERVICE PROBLEM (When reset has not

been triggered for any reason)
7105 RAT BASE STATION PROBLEM

7105 RAT BASE STATION PROBLEM

7100 HARDWARE PROBLEM (cell not affected)

7104 CELL SERVICE PROBLEM (cell affected)

7100 HARDWARE PROBLEM

7104 CELL SERVICE PROBLEM (in case the cell

cannot operate because radio requires reset)

7100 HARDWARE PROBLEM

7104 CELL SERVICE PROBLEM

7100 HARDWARE PROBLEM

7111 BASE STATION SOFTWARE MANAGEMENT
PROBLEM

7100 HARDWARE PROBLEM

7104 CELL SERVICE PROBLEM (Source is ABIx, RU)

7105 RAT BASE STATION PROBLEM (Source is ASIx)
7101 RESET NOTIFICATION (if automatic site reset
recovery is performed)

7108 BASE STATION SYNCHRONIZATION PROBLEM

(always)
7101 RESET NOTIFICATION (in case recovery reset
will be triggered)
7100 HARDWARE PROBLEM (Level BTS fault is
toggling in the BTS.)

7106 SINGLE RAN BASE STATION PROBLEM (Level

BTS fault is toggling in the BTS.)

7107 BASE STATION CONNECTIVITY PROBLEM

(Level BTS fault is toggling in the BTS.)

When fault affects basic services of the base station:

7108 BASE STATION SYNCHRONIZATION PROBLEM

When fault does not affect basic services of the base

station:
7115 BASE STATION INFORMATION

7101 RESET NOTIFICATION (when reset is being

performed)
7104 Cell Service Problem (When 5GRAP reset has not
been triggered for any reason)
7105 RAT BASE STATION PROBLEM (When RAC
when autonomous recovery reset is being performed
reset has not been triggered for any reason)
due to fault
7101 RESET NOTIFICATION
when fault does not affect basic services of the base
station
The fault affects basic services of the base station
7115 BASE STATION INFORMATION
7108 BASE STATION SYNCHRONIZATION PROBLEM
when fault affects basic services of the base station
7116 BASE STATION SERVICE PROBLEM

7120: ALL RAPS OUT OF SERVICE

7121 NODEB FIBER LENGTH DEPLOYMENT

EXCEEDED

Severity is Major, the RU may not able to come into

service or provide service
7122 RU FIBER LENGTH DIFFERENTIAL EXCEEDED
until this fault is corrected
Severity is Critical, the RU is not able to come into
service or provide service until this fault is corrected
7101 RESET NOTIFICATION (when reset is being
performed)
7107 BASE STATION CONNECTIVITY PROBLEM
A fault (or faults) has(have) occurred in the base station
connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
7101 RESET NOTIFICATION (when reset is being
performed)
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
-
text field of the alarm.

7111 BASE STATION SOFTWARE MANAGEMENT

PROBLEM

7108 BASE STATION SYNCHRONIZATION PROBLEM

(always)
7104 CELL SERVICE PROBLEM (always)
7101 RESET NOTIFICATION (in case recovery reset
will be triggered)
-

7123 5G BASE STATION SCALING NOTIFICATION

7124 5G BASE STATION INCOMPLETE VM INIT

7125 5G BASE STATION FAILED VM INIT

A fault has occurred in BASE STATION

CONNECTIVITY PROBLEM At
MRBTS/NRBTS/X2linkSupervisionTmr expiry which is
started when there is no X2-C link available.
7104 CELL SERVICE PROBLEM

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

7105 RAT BASE STATION PROBLEM (in case fault

affects basic services of the base station)
7104 CELL SERVICE PROBLEM (in case the cell
cannot operate because it does not have enough
available and needed resources: Tx or Rx)
7105 RAT BASE STATION PROBLEM (in case the fault
affects basic services of the base station)
7104 CELL SERVICE PROBLEM (in case the cell
cannot operate because it does not have enough
available and needed resources: Tx or Rx)

7101 RESET NOTIFICATION (when reset is being

performed)
A fault (or faults) has (have) occurred in the base
station connectivity/interface.
Check the reason for the fault from the supplementary
text field of the alarm.
7105 RAT BASE STATION PROBLEM (otherwise)
7101 RESET NOTIFICATION (raised only if RESET
RECOVERY is triggered)

This non critical SW fault is raised whenever the

common unit/capacity unit (RAU) Platform CE non
critical process has crashed.

A fault has occurred where at least one MeNB involved

in non-standalone call with SgNB erroneously does not
support "NR RAN Container" GTP-U extension header
on X2-U interface.
7115 BASE STATION INFORMATION

61030 Dead Peer Detected

61605 BFD-$BFDID down in ingress

61606 BFD-$BFDID down in egress

61644 IKE authentication failure

61645 IKE SA failure

61646 IPSec SA failure

Instructions

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

Because there are several possibilities for the alarm

1. Retry the SW update.

1. Make sure that the unit/module is properly connected. If

Perform the following actions in order and, after each

Update the SW in the BTS.

- Check the alarms of the TRS signal used for

1. Check the connection and integrity of the antenna

connector, cable, and antenna.
2. Reset the radio module. If the alarm persists, replace
1. Reset the radio module. If the alarm persists, replace
the RM.
the RM.

1. Block/unblock RF HW unit
2. If the problem persists, replace the RF HW unit

Follow the steps below to clear the fault:

1. Check if the fan or airflow is free of foreign objects.

Remove any objects blocking the fan or the airflow.
2. Check if the fan connector is properly mounted. Mount
Take the following steps to clear the fault:
fan connector according to the guidelines.
3. Reset the RAP
1. Check if the ambient temperature/environmental
4. If the alarm is still observed, then replace the fan or the
conditions are within the design limits for the radio module.
RAP.
When the ambient temperature/environmental conditions
1. Check if the ambient temperature and environmental
exceed the limits, the alarm is expected and no further
conditions are within the designed limits for the radio
actions are needed.
module. When the ambient temperature and environmental
conditions exceed the limits, the alarm startup is expected
2. Check if airflow is free of foreign objects. Make sure the
and no further actions are needed.
No actionsthermal
minimum are needed since the
clearances BTS recovers
guidelines are followed.
independently.
Remove any objects If the alarm occurs
that might be multiple
blockingtimes, checkand
the airflow
2. Check if air flow is free of foreign objects. Make sure
other
mountactive alarmsaccording
the module to determine the root cause.
to instructions and
minimum thermal clearance guidelines are followed.
recommendations.
Remove any objects that might be blocking the airflow and
To clear
mount this
the fault: according to instructions and
module
3. Check if excessive sunlight is causing the unit to
recommendations.
overheat.
1. Retry the Install the sunshield following the mounting
SW update.
instructions
2. and recommendations.
3. If the problem
Check is permanent
if excessive contact
sunlight is causingNokia support
the unit to
overheat. Install the sunshield following
Take the following steps to clear the fault: the mounting
instructions and recommendations.
1. Check if the ambient temperature/environmental
conditions are within the design limits for the antenna
sumodule. When the ambient temperature/environmental
1. Check if the ambient temperature and environmental
conditions exceed the limits, the alarm is expected and no
conditions are within the designed limits for the antenna
further actions are needed.
submodule. When the ambient temperature and
environmental conditions exceed the limits, the alarm
2. Check if airflow is free of foreign objects. Make sure the
startup is expected and no further actions are needed.
1. Reset the
minimum RF HW
thermal unit.
clearances guidelines are followed.
Remove any objects that might be blocking the airflow and
2. Check if air flow is free of foreign objects. Make sure
2. If thethe
mount problem
modulecontinues
accordingafter step 1 has been
to instructions and
minimum thermal clearance guidelines are followed.
performed, replace the RF HW unit.
recommendations.
Remove any objects that might be blocking the airflow and
mount the module according to instructions and
3. Check if excessive sunlight is causing the unit to
recommendations.
overheat. Install the sunshield following the mounting
instructions and recommendations.
3. Check if excessive sunlight is causing the unit to
overheat. Install the sunshield following the mounting
instructions and recommendations.
1. Reset the RF HW unit.

2. If the problem continues after step 1 has been

performed, replace the RF HW unit.
1. Reset the FR HW unit and check if this solves the
problem.

2. If the alarm continues after executing steps 1, replace

the RF HW unit.
Check the source of the fault to see the level at which reset
loops have been occuring.
Investigate the fault or alarm history to solve the problem.
Consider resetting on higher level (ex. gNB reset) if fault
source is ASIx, ABIx, RU.
Perform the steps below in the listed order until the fault
disappears. If after autonomous GPS power reset, the fault
does not get canceled, wait for five minutes (from the start
of the fault) prior to performing the actions below.
This fault is most likely the result of a BTS hardware
Control Interface is not available:
problem or a reference source that is being followed by the
1. The BTS has detected a malfunction in the control
BTS that is in a faulted condition, therefore producing an
interface of the GPS receiver. A possible reason is that the
inaccurate reference. Perform the following steps to isolate
BTS and the GPS receiver do not support a common
the cause of the fault:
Follow theOtherwise,
interface. steps below to clear
perform a the fault: power reset for
(remote)
the GPS receiver.
1. Check the other alarms of the BTS and act accordingly.
1.
2. Check
Performthe fault name
a (remote) BTSof the
site toggling
reset forBTS fault. BTS.
the whole
3. Perform a power reset for the whole BTS.
2. If there are no other synchronization-related alarms
2.
4. Follow the between
instructionsthe of the receiver
toggling and
BTSthefault to clear
ToThe
clearcable
active, thisthe
start fault: GPS
fast tuning with BTS Element Manager.
BTS might
the
be problem.incorrectly. Check if the pins of the connectors
working
1. Check the fan and connector.
(onIf both
step ends
2. Reset 1 does of the help,
cable) are free from
fan.oxide and other
3. the site.not
Run fastreplace the
tuning again.
Note:
kind ofDetailed information
dirt, meaning that theabout the togglingquality
pin connection frequency
is
can
good. be found in the alarm history file, which can be
4.
To Check the fault:
clearcable
this reference signal accuracy by measuring it
downloaded
5. The using
between the the
VNFGPSWebUI. The and
receiver log file
theisBTS
available
might
with a frequency counter (note: requires a good timebase
with Snapshot.
be faulty. Check the situation and change the cable, if
for
1. the counter).
Check the fansThe andreference
ensure that signal
the can be found
ambient from
temperature
needed.
the Sync
on-site Out interface of the Flexi System Module, the
6. Thereismight
acceptable.
be a HW fault in the GPS receiver. Check
required
2. accuracy
Ifoperation
that does is +/-0.015ppm.
not help, replace theIfalarming
the reference
the
To clear this fault: change
and the GPS module, ifmodule.
needed.
accuracy is correct, run fast tuning. If the reference
7. There might be a HW fault in the BTS System Module.
accuracy is not correct the cause of the fault is the
Check
1. Makethe operation
sure the fan and change the System Module, if
reference source the is
BTSnotisblocked.
tuning to. Troubleshoot the
needed.
external synchronization network to find the root cause.
2. Make
Other surewith
BTSs the fan connector is properly mounted.
To clear this fault:the same alarm can provide further
information about the location of the root cause.
3.
5. If that does not help,
the reference replace
accuracy the fan.
is correct and running fast
1. Make sure the fan is not blocked.
tuning does not help, replace the system module.
2. Make sure the fan connector is properly mounted.
Replace the fan.
3. If that does not help, replace the fan.

If the BTS is not automatically updated by NetAct, update

Not tracking satellites:

2. Check the other possible alarms/fault indications of the

GPS/GNSS receiver
No manual action and thefrom
is needed BTS the
andoperator.
act accordingly.

3. There might be a malfunction in the GPS/GNSS

receiver. Perform a (remote) power reset for the
GPS/GNSS receiver module.

4. If there is only the alarming GPS/GNSS receiver

5. Check the connection between the GPS/GNSS receiver

Retry the SW update.

Change the GNSS constellation mode to a constellation

mode supported by the receiver to cancel the fault.

1. Check the cable connectivity on the ToP master side.

2. Check the TOP configuration on both the BTS and ToP
master sides.

Check BTS configuration (sync mode) and TOP

configuration.

In the case Source = 5GRAU (ASIx or RTM):

1. Check the Front Haul connection (between 5G BTS and
RAU).
2. Check RAU HW.
Note: Perform the steps in the listed order until the fault is
In the case Source = RAC:
resolved.
Check server HW.
1. Reset the BTS.
2. Check the connectivity:
AirScale: Ensure that the module is properly connected to
1. Wait for Secondary Unit reset.
the rack.
2. If it does not help, replace the unit one by one in the
3. Check the SW version on Secondary core if it is the
below order:
same as Primary core.
a. primary unit (ASIK primary)
4. Replace the faulty unit.
b. secondary unit (ASIK secondary) then
1) RAP having OFFLINE as availability status: Check RAP
c. AMIA subrack (AirScale)
connections.

2) In case RAP Reset needed fault is active and RAP

status is not offline: RAP reset
To solve this problem, the technician should inspect the
optic fiber deployment of the RU unit in question. This fault
3) In case RAP Reset does not recover: Site reset
occurs when a RU is configured with a
fiber optic cable between the RAU and RU that physically
4) In case Site reset does not recover RAPs: Replace the
exceeds the maximum length supported. The maximum
To solveRAP
needed this problem,
HW. the technician should inspect the
length supported will depend on the 5G release in question
optic fiber deployments of the RU unit in question. This
(and changes/increases with different releases). The
fault occurs when a RU is configured with two fiber optical
physical connections and physical deployment should be
cables to one modem card. The differential between these
checked to see that these lengths are not exceeded. The
fiber optical cables must not exceed 1000m. The physical
If fault recovery
technician failsreset
can then checkthe
theNodeB
F1 SCTPandstate and the will
the software
connections and physical deployment should be checked
gNB_CU logs.re-compute to see if the fiber lengths are not
automatically
to see that these lengths are not exceeded. The technician
within the acceptable differential range.
can then reset the NodeB and the software will
automatically re-compute to see if the fiber lengths are not
Manually
within the reset the RAP.
acceptable differential range.
Manually reset the RAP.

Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check the connection between gNB-CU and gNB-DU.

Note: Perform the steps below in the listed order until the
2. Check if the gNB-CU or gNB-DU is operational.
alarm disappears:
3. Check if the speed and duplex setting of the VNF F1
1. Check the connection with the eNB.
port is consistent with
Note: Perform the steps below in the listed order until the
2. Check if the eNB is operational.
alarm disappears:
the switch port that is connected directly to the VNF (for
example, they are
3. Check if the speed and duplex setting of the VNF X2
1. Check the connection between gNB-CU and gNB-DU.
port is consistent with
both
Check "Autodetect"
the gNB_DU or Cplane
both "1000
logsMbit/s Full duplex").
to identify the root cause.
2. Check if the gNB-CU or gNB-DU is operational.
the switch port that is connected directly to the VNF (for
4. Check if the speed and duplex setting of the gNB-DU F1
example, they are
3. Check
port if the speed
is consistent with and duplex setting of the VNF F1
port is consistent with
both
Check "Autodetect"
the port
gNB_CU or both "1000
logsMbit/s Full duplex").
the switch that isCplane
connected to identify
directly to the root cause.
gNB-DU
the
(for switch
example, portthey
thatare
is connected directly to the VNF (for
example, they are
both "Autodetect" or both "1000 Mbit/s Full duplex").
both "Autodetect"
1) Check or both "1000
the link between Mbit/s
VNF and Full duplex").
RAP.
2) Manually reset the RAP to trigger SW update to the
4. Check if the speed and duplex setting of the gNB-DU F1
RAP.
port is consistent with

If
theGPS is configured
switch port that isas a reference
connected clock,toperform
directly the
the gNB-DU
following:
(for example, they are
1. Check the GPS receiver installation.
2. Check
both the GPSor
"Autodetect" receiver status.
both "1000 Mbit/s Full duplex").
3. Check the connection between the GPS receiver and
Check the gNB_CU Cplane logs to identify the root cause.
ASIx.

If the TOP signal is configured as a reference clock,

perform the following:
Check
1. thethe
Check gNB_DU Cplane
connection logsTOP
to the to identify
server the root cause.

Check the gNB_CU Cplane logs to identify the root cause.

For this alarm to be cleared, it requires a manual

intervention from an operator.
The operator should check the current resources at CBAM
UI while scaling, and perform scale-out on a specific type
of VNFC.

Alarm is cleared for CPUE if the following criteria is met

o CPU Utilization of <CPUE Scale-out Threshold
Instances> drops below <
MRBTS/MNL/MNLENT/SCALADM /
cpueReallocThresholdCpu>
Alarm is cleared for UPUE if the following criteria is met
o CPU Utilization of <UPUE Scale-out Threshold
Instances> drops below
<MRBTS/NRBTS/cpuLoadConfigUpUe/reallocLoad>
For this alarm to be cleared, this requires a manual
intervention from an operator. The operator should check
the current resources at CBAM UI while scaling, and
perform scale-in on a specific type of VNFC.
Alternately, this alarm shall be cleared if a scale-out need
1) Check if the heat file definitions configured during VNF
is detected for the same type of VNFC, or if the operator
instantiation are correct
performs a scale-out for the same type of VNFC.
2) Make sure that there are enough HW resources.

This fault does not require any actions. There will be an

automatic reset.

1. Determine the gNB of the ASIR-HUB RMOD used for

the cell.
2. Use ASiManager to connect to the gNB identified in step
1 and check faults reported in ASiManager.
Follow instructions of those faults and correct the fault
1. Determine the Master gNB of the ASIR-HUB RMOD
situation.
used for the cell.
2. Use ASiManager to connect to the gNB identified in step
1 and check faults reported in ASiManager. Follow
instructions of those faults and correct the fault situation.
Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check if SCTP association is established from the LTE

eNB.
Check the configuration.
2. Check if the eNB is operational.

3. Check if EN-DC X2 Setup request message from the

If
LTEfault
eNBrecovery fails check
is received the E1 SCTP state and restart
by gNB.
the gNB.
4. Check if EN-DC X2 Setup Response message is sent to
eNB
If fault recovery fails, restart the gNB.

If fault recovery fails, restart the gNB.

Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check the connection with the AMF.

Note: Perform the steps below in the listed order until the
2. Check if the AMF is operational.
alarm disappears:
3. Check if the speed and duplex setting of the NG port is
1. Check the connection with the AMF.
consistent with
the switch port that is connected directly to the gNB (for
2. Check if the AMF is operational.
example, they are
both "Autodetect" or both "1000 Mbit/s Full duplex").
3. Check if the speed and duplex setting of the NG port is
consistent with
the switch port that is connected directly to the gNB (for
example, they are
both "Autodetect" or both "1000 Mbit/s Full duplex").
Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check the connection with the peer gNB/ng eNB.

Note: Perform the steps below in the listed order until the
2. Check if the peer gNB/ng eNB is operational.
alarm disappears:
3. Check if the speed and duplex setting of the Xn port is
1. Check the connection with the peer gNB/ng eNB.
consistent with
When
the switchsnapshot is triggered,
port that but not
is connected collected,
directly to the check the
gNB (for
2. Check if the peer gNB/ng eNB is operational.
reason
example, in they
the Alarm:
are
-both
New"Autodetect"
snapshot can or be blocked
both "1000 ifMbit/s
thereFull
is an ongoing
duplex").
3. Check if the speed and duplex setting of the Xn port is
snapshot in process
consistent with
- Too many snapshots: limit the number of snapshots per
Follow
the switchthe port
steps below
that to resolvedirectly
is connected the fault:
to the gNB (for
Fault ID (+CU or +DU) to 5 per 24 hours
example, they are
- Snapshot taken too often: set the minimum time interval
1.
bothIn case of NR-LTE
"Autodetect" sharing,
or both "1000tryMbit/s
to connect Radio Unit
Full duplex").
per Fault ID (+CU or +DU) between snapshots to 15
HW version >= Rel 5.1 (NAHKA)
minutes
2. In case NR-LTE sharing is not intended, RF sharing
Follow
- Other the steps
reason inbelow
snapshotto resolve the process
collection fault: (collect OAM
should be disabled in SCF
logs to resolve reason)
3. Replace the alarming unit with the unit planned in 5G
1.
WhenIn case of NR-LTE
snapshot sharing,lack
is collected, try of
to snapshot
configure data
the RFcan be
BTS planned HW configuration (BTS profile).
sharing
read from mode correctly on both NR and LTE side (NR as
the Alarm.
master and LTE as slave)
If fault recovery fails, check the nrRelLteId associated with
2. In case NR-LTE sharing is not intended, RF sharing
the NR CELL.
should be disabled in SCF
Check if LTE eNB provided via nrRelLteId is available.
3. Replace the alarming unit with the unit planned in 5G
BTS planned HW configuration (BTS profile).
OAM performs a configuration change. Fault will be
canceled after RAP reset.

Download snapshot from the node. Check which fault has

triggered the snapshot.

Check snapshot on external server. Check which fault has

triggered snapshot.

Collect technical logs from the BTS to clear the alarm

raised by this fault.
Internal logs collected by this process can only be
analyzed by Nokia R&D.
Replace the optical transceiver module with a
Additionally:
recommended module.
- Check the alarm history to confirm the frequency of fault
4527 in a specific eNB.
- Check the alarm history for other alarms in the same eNB
Replace
that mightthe
beoptical transceiver
related, especiallymodule
alarms with
with aRadio
module
alarms
recommended which can support extended temperature.
If an alarm with fault 4527 frequently occurs in the same
eNB, alarms with the same faults mentioned above are
present in the same eNB, or the eNB performance is
degraded, then collect a snapshot and open a case for
Nokia R&D log analysis.

Each RU crash are reported with own 4527 fault

Note: Perform the steps below in the listed order until the
alarm disappears:

1. Check the connection with the eNB.

Investigate the fault root cause. Lock/Unlock RAP.
2. Check if the eNB is operational.

3. Check if the speed and duplex setting of the VNF X2

port is consistent with
RAU (ASIx): Site reset
RAU (ABIx):
the switch FSP
port thatreset
is connected directly to the VNF (for
example, they are

both
Check"Autodetect" or both
the gNB-Cu-UP "1000logs
Cplane Mbit/s Full duplex").
to identify the root
cause.

If fault recovery fails check the E1 SCTP state and restart

the gNB.

Check the gNB-CU-CP Cplane logs to identify the root

cause.

Check peer (MeNB) configuration / SW version to enable

support of needed extension.

Workaround: Modification of SgNB parameter

1. Check that the cables/fibers are connected to the correct

connectors.
2. Check that the interface at the far-end is switched on
and has correct auto-negotiation settings.
3. Check whether there are active alarms at the far end. If
1. Check that the cables are connected to the correct
there are, follow the instructions for handling those alarms.
connectors.
4. To verify that the hardware of the interface works
2. Check that the interface at the far-end interface is
correctly, connect a loop cable and check whether the
switched on.
alarm disappears.
3. Check whether there are active alarms at the far end. If
1.
5. Check that the optical transceiver
length/type module is does
of the cable/fiber correctly
not
there are, follow the instructions for handling those alarms.
installed
introduceand plug-out/plug-in
excessive attenuation optical transceiver
or that module.
the cable/fiber is
cut somewhere.
2.
6. Check for
thatoptical transceiver
the Ethernet validity
interface has(could
correctbeauto-
the wrong
type) and insert
negotiation a compliant
settings, fitting to optical
the transceiver
far-end module.
interface.
Execute general configuration checks:
7. With an optical
- Configuration of Ethernet
primary CRL interface:
serverCheck that the
IP address and port.
3. CheckSFP
inserted that module
the electrical contacts of the optical
- Configuration of DNS server IP address. and
matches the fiber type
transceiver
wavelength module are clean
of the Gigabit from dust,
Ethernet dirt, or water.
link provided.
Check remote peers and intermediate network element
4. Replace the optical transceiver module with a module
interconnections.
recommended by Nokia.
Check the LDAP connection towards the Certificate
Revocation List server.
Note that only the optical transceiver might be faulty, and
Check the size of the file at the Certificate Revocation List
not the entire hardware unit.
server.
Perform connectivity checks related to primary CRL
servers.
Replace the faulty optical transceiver. Note that only the
optical transceiver is faulty, not the entire hardware unit.

1. Check the CMP configuration.

2. Check for CA server reach-ability.
3. If none of the above work, contact CA
administrator/Nokia service personnel
1. Check the network between both BFD peers for physical
link failures or misconfigurations.

2. Check if the BFD functionality in the peer is switched on

and that the configurations of the BFD local and remote
1. Check the network between both BFD peers for physical
peers match.
link failures or misconfigurations.
2. Check if the BFD functionality in the peer is switched on
and that the configurations of the BFD local and remote
peers match.
The customer needs to return the equipment to Nokia for
vendor certificate re-installation

Update trust anchors.

1. Check the cable connectivity on ToP master side.

2. Check the TOP configuration both in BTS and ToP
master sides.

1.Check for duplicate IPv6 addresses configured in the

BTS.

2.Change or delete the identified duplicate IPv6 addresses.

Check the validity of the username and password of the
account.

Check the authentication credential provided by the peer

(certificate).

Check the IKE profile configuration of the Network Element

and the peer for proper values.

Check that the configurations for the peer and the Network
Element security policies for corresponding failure
notification.
Related Faults Related Features

5GC000180: 5G Node B Temperature

management
5GC000169: 5G Node B basic faults indication

5GC000316: 5G Node B Synchronization Mode

Support

5GC000169: 5G Node B basic faults indication

5GC000316: 5G Node B Synchronization Mode

Support
5GC000170: 5G Node B recovery

5GC000169: 5G Node B basic faults indication

5GC000174: 5G Node B Software management

5GC000169: 5G Node B basic faults indication

5GC000170: 5G Node B recovery

5GC000174: 5G Node B Software management

5GC000169: 5G Node B basic faults indication

5GC000418: AMOB outdoor sub-rack for 5G

5GC000174: 5G Node B Software management

5GC000169: 5G Node B basic faults indication

5GC000718: F1 cell management
5GC000170: 5G Node B recovery

5GC000579: Long fiber support for CPRI

fronthaul
5GC000170: 5G Node B recovery

5GC000169: 5G Node B basic faults indication

5GC000316: 5G Node B Synchronization Mode

Support

5GC000316: 5G Node B Synchronization Mode

Support

5GC000316: 5G Node B Synchronization Mode

Support

5GC000169: 5G Node B basic faults indication

5GC000316: 5G Node B Synchronization Mode

Support
5GC000318: 1PPS&ToD Sync from External
GNSS Receiver
5GC000169: 5G Node B basic faults indication
5GC000170: 5G Node B recovery
5GC000169: 5G Node B basic faults indication
5GC000170: 5G Node B recovery

5GC000169: 5G Node B basic faults indication

5GC000174: 5G Node B Software management

5GC000169: 5G Node B basic faults indication

5GC001025: NR-LTE concurrent operation for

CPRI TDD MAA radios

5GC000174: 5G Node B Software management

5GC000169: 5G Node B basic faults indication

5GC000318: 1PPS&ToD Sync from External

GNSS Receiver

5GC000316: 5G Node B Synchronization Mode

Support
5GC000170: 5G Node B recovery

or IPv6
5GC000170: 5G Node B recovery

5GC000481: F1 link management

5GC000174: 5G Node B Software management

5GC000316: 5G Node B Synchronization Mode

Support
5GC000170: 5G Node B recovery

5GC000481: F1 link management

5GC000299: VNF Manual scaling with CBAM

5GC000548: VNF CU capacity and configuration

5GC000170: 5G Node B recovery

5GC001091: AirScale Indoor Radio NR

operation

5GC001091: AirScale Indoor Radio NR

operation

5GC000474: X2 Management for NSA mode 3x

operation

5GC000718: F1 cell management

5GC000170: 5G Node B recovery

5GC001009: E1 interface preparation

5GC000170: 5G Node B recovery

5GC001009: E1 interface preparation

5GC000681: Dual Stack IPv4/IPv6 for NG /Xn

interfaces in SA deployment

5GC000681: Dual Stack IPv4/IPv6 for NG /Xn

interfaces in SA deployment
5GC000681: Dual Stack IPv4/IPv6 for NG /Xn
interfaces in SA deployment

5GC000681: Dual Stack IPv4/IPv6 for NG /Xn

interfaces in SA deployment

5GC000507: Fault triggered snapshot

5GC000726: NR-LTE FDD concurrent operation

for CPRI RUs

5GC000726: NR-LTE FDD concurrent operation

for CPRI RUs

5GC000718: F1 cell management

5GC000170: 5G Node B recovery

5GC000631: ABIL & ASIK - new SW deployment

5GC000507: Fault triggered snapshot

5GC000371: gNB recovery log collecting

5GC001179: BTS Fronthaul CPRI 7 - 10/25GE

5GC000718: F1 cell management

5GC000169: 5G Node B basic faults indication
5GC000170: 5G Node B recovery

5GC000170: 5G Node B recovery

5GC000371: gNB recovery log collecting

5GC001009: E1 interface preparation

5GC000475: SgNB Addition and Release for

NSA mode 3x operation

5GC001097: Basic PCMD For NSA

5GC000380: 10GBase-SR Optical GE Interface

5GC000848: BTS Fronthaul CPRI 7 - 10/25GE
SFP+/SFP28 Dual Fiber Base Line
5GC000624: 10/25GBase-SR Optical GE
Interface
5GC000264: IPsec on Backhaul
5GC000388: 1000Base-BX Optical GE Interface
5GC000392: IPsec on F1
5GC000851: BTS Fronthaul CPRI 7 - 10/25GE
SFP28 Single Fiber
5GC000385: 1000Base-SX Optical GE Interface
5GC000380:
5GC000387: 10GBase-SR
1000Base-ZX Optical
Optical GE
GE Interface
Interface
5GC000848:
5GC000849: BTS Fronthaul CPRI 7 - 10/25GE
10GE
SFP+/SFP28 Dual Fiber Base Line
SFP+ Single Fiber
5GC000624:
5GC000381: 10/25GBase-SR Optical
Small Form Factor GE
Pluggable
Interface
SFP/SFP+/SFP28 slot
5GC000323: Operator Certificate Management
5GC000388:
5GC000386: 1000Base-BX Optical
Optical GE
GE Interface
Interface
& Multi Layer 1000Base-LX
of CA
5GC000851:
5GC000625: BTS Fronthaul CPRI
10/25GBase-LR 7 - 10/25GE
Optical GE
5GC000170: 5G Node B recovery
SFP28 Single Fiber
Interface
5GC000385:
5GC001179: 1000Base-SX
BTS FronthaulOptical
CPRI 7GE Interface
- 10/25GE
5GC000387:
QSFP+/QSFP28 1000Base-ZX
Base Line Optical GE Interface
5GC000849:
5GC000850: BTS Fronthaul CPRI 7 - 10GE
SFP+ Single
CWDMFiber
5GC000381:
5GC000382: Small Form Factor
10GBase-LR Pluggable
Optical GE Interface
SFP/SFP+/SFP28 slot
5GC000847: BTS Fronthaul CPRI 7 - 10GE
5GC000386: 1000Base-LX
SFP+ Dual Fiber Base Line Optical GE Interface
5GC000625: 10/25GBase-LR Optical GE
Interface
5GC001179: BTS Fronthaul CPRI 7 - 10/25GE
QSFP+/QSFP28 Base Line
5GC000380: 10GBase-SR Optical GE Interface
5GC000848: BTS Fronthaul CPRI 7 - 10/25GE
SFP+/SFP28 Dual Fiber Base Line
5GC000624: 10/25GBase-SR Optical GE
Interface
5GC000323: Operator Certificate Management
5GC000388: 1000Base-BX Optical GE Interface
& Multi Layer of CA
5GC000851: BTS Fronthaul CPRI 7 - 10/25GE
5GC000170: 5G Node B recovery
SFP28 Single Fiber
5GC000385: 1000Base-SX Optical GE Interface
5GC000296:
5GC000387: VNF CU on Third
1000Base-ZX PartyGE Interface
Optical
Infrastructure
5GC000849: BTS 1 Fronthaul CPRI 7 - 10GE
SFP+ Single Fiber
5GC000381: Small Form Factor Pluggable
SFP/SFP+/SFP28
5GC000296: VNF CU slot on Third Party
5GC000386: 1000Base-LX
Infrastructure 1 Optical GE Interface
5GC000625: 10/25GBase-LR Optical GE
Interface
5GC001179: BTS Fronthaul CPRI 7 - 10/25GE
5GC000323:
QSFP+/QSFP28 Operator
Base Certificate
Line Management
& Multi Layer BTS
5GC000850: of CAFronthaul CPRI 7 - 10GE
SFP+ CWDM
5GC000382: 10GBase-LR Optical GE Interface
5GC000847:
5GC000323: BTS Fronthaul
Operator CPRIManagement
Certificate 7 - 10GE
SFP+ Dual Fiber
& Multi Layer of CABase Line
5GC000170: 5G Node B recovery

5GC000313: Timing over Packet with Phase

Synchronization
5GC000609: ToP with Phase Sync Resiliency

5GC000170: 5G Node B recovery

5GC000307: Transport IPV4/IPv6 stack
enhancement

5GC000324: Operator Account Management on

gNB

5GC000264: IPsec on Backhaul

5GC000392: IPsec on F1

5GC000264: IPsec on Backhaul

5GC000392: IPsec on F1

5GC000392: IPsec on F1
5GC000264: IPsec on Backhaul
Restriction status

No
No

Yes
Yes

Yes

Yes
Yes

Yes

No
No

B39a Rrh8x10 Uzfb TD
No ratings yet
B39a Rrh8x10 Uzfb TD
36 pages
Operability Features Description - FL17A
100% (1)
Operability Features Description - FL17A
233 pages
BSS PPT 1-Jan-2024
No ratings yet
BSS PPT 1-Jan-2024
20 pages
Ref Bts Alarms and Fault Sran21b Sran21a
No ratings yet
Ref Bts Alarms and Fault Sran21b Sran21a
832 pages
System Overview - 20Rx
No ratings yet
System Overview - 20Rx
66 pages
01.nokia Airscale System Module Product - Description
No ratings yet
01.nokia Airscale System Module Product - Description
62 pages
S04M01 SG RA41320-V-21B Nokia LTE BTS Operation Administration and Maintenance Ktnu0f24
No ratings yet
S04M01 SG RA41320-V-21B Nokia LTE BTS Operation Administration and Maintenance Ktnu0f24
88 pages
AirFrame Support Services Playbook
No ratings yet
AirFrame Support Services Playbook
13 pages
Sync Hub Direct Forward
No ratings yet
Sync Hub Direct Forward
58 pages
EIRP 3.5 GHZ CBRS
No ratings yet
EIRP 3.5 GHZ CBRS
8 pages
Technical Solution Band 700 850 1900 2600MHz V7.0
No ratings yet
Technical Solution Band 700 850 1900 2600MHz V7.0
4 pages
Alarms in NOKIA Flexi BTS
No ratings yet
Alarms in NOKIA Flexi BTS
8 pages
Vodafone NZ LTE BTS Commissioning & Integration V3
No ratings yet
Vodafone NZ LTE BTS Commissioning & Integration V3
61 pages
19mis0356 VL2023240503980 Pe003
No ratings yet
19mis0356 VL2023240503980 Pe003
64 pages
Adhyaksa Raya BJM PL Boq
No ratings yet
Adhyaksa Raya BJM PL Boq
2 pages
Training Course - 5G RAN3.0 Multi-Operator Sharing
No ratings yet
Training Course - 5G RAN3.0 Multi-Operator Sharing
21 pages
Administration and Troubleshooting of The BTS Conversion Service
No ratings yet
Administration and Troubleshooting of The BTS Conversion Service
39 pages
Lte 1800-Mop-Inst & Comms-Vf v1.1
No ratings yet
Lte 1800-Mop-Inst & Comms-Vf v1.1
40 pages
OMS Product Description
No ratings yet
OMS Product Description
89 pages
Nokia Sran
No ratings yet
Nokia Sran
2 pages
Guideline Qos Audit Mrbts Sbts Sran17a Updated - Nokia eNB
No ratings yet
Guideline Qos Audit Mrbts Sbts Sran17a Updated - Nokia eNB
3 pages
Nokia 3G Alarm
No ratings yet
Nokia 3G Alarm
4 pages
LTE BTS HW Introduction To Ogero PDF
No ratings yet
LTE BTS HW Introduction To Ogero PDF
44 pages
Breezecompact Lte: System Manual System Manual
No ratings yet
Breezecompact Lte: System Manual System Manual
152 pages
Factory Delivery Software and Diagnostic and Recovery Software Description
No ratings yet
Factory Delivery Software and Diagnostic and Recovery Software Description
42 pages
SBTS 17A Configurations Guide
No ratings yet
SBTS 17A Configurations Guide
66 pages
AirHarmony 1000 - LTE Product Specification B53 v1.4 - 2
No ratings yet
AirHarmony 1000 - LTE Product Specification B53 v1.4 - 2
23 pages
2018 08 31 SRAN Configuraciones - Con Airscale - AMOB 2018 09 19 V4
100% (1)
2018 08 31 SRAN Configuraciones - Con Airscale - AMOB 2018 09 19 V4
14 pages
FSMF SiteEngineering v1 PDF
No ratings yet
FSMF SiteEngineering v1 PDF
15 pages
Flexi Multiradio Pre-PAT Certificate
No ratings yet
Flexi Multiradio Pre-PAT Certificate
11 pages
ABIL - AirScale - Capacity - Datasheet
No ratings yet
ABIL - AirScale - Capacity - Datasheet
5 pages
Compact Mobility Unit R21
No ratings yet
Compact Mobility Unit R21
8 pages
FL18
No ratings yet
FL18
121 pages
06 RA47076EN70NAA0 LTE Link Budget
No ratings yet
06 RA47076EN70NAA0 LTE Link Budget
70 pages
Flexi Multiradio 10 BTS Quick Guide
No ratings yet
Flexi Multiradio 10 BTS Quick Guide
17 pages
ASIB Technical Datasheet
No ratings yet
ASIB Technical Datasheet
4 pages
Creating Flexi Multiradio 10 Bts Fddlte Configurations
No ratings yet
Creating Flexi Multiradio 10 Bts Fddlte Configurations
242 pages
Lampsite RTWP Issue Handling Guide
50% (2)
Lampsite RTWP Issue Handling Guide
16 pages
01 OS90531EN15GLA00 Introduction
100% (2)
01 OS90531EN15GLA00 Introduction
78 pages
AHPDA
No ratings yet
AHPDA
8 pages
Nokia BSC Commands
No ratings yet
Nokia BSC Commands
3 pages
Nokia Airscale Capacity Unit (Abia)
No ratings yet
Nokia Airscale Capacity Unit (Abia)
1 page
RA47060-V-18A - LE01 - Flexi Zone LTE Products - Noted
No ratings yet
RA47060-V-18A - LE01 - Flexi Zone LTE Products - Noted
37 pages
04 Rn20114en16gla0 Osc+csdap
No ratings yet
04 Rn20114en16gla0 Osc+csdap
79 pages
Admin Help
No ratings yet
Admin Help
166 pages
Flexi WCDMA BTS - Introduction
100% (1)
Flexi WCDMA BTS - Introduction
28 pages
Flexi Multiradio BTS RF Sharing Supported Configurations PDF
No ratings yet
Flexi Multiradio BTS RF Sharing Supported Configurations PDF
86 pages
01 - Review of NB-IoT Network Architecture
No ratings yet
01 - Review of NB-IoT Network Architecture
14 pages
Training (Nokia Advance Technologies)
No ratings yet
Training (Nokia Advance Technologies)
25 pages
Administering Netact System Security Base
No ratings yet
Administering Netact System Security Base
594 pages
FWGP 2100MHz Data Sheet Summary
No ratings yet
FWGP 2100MHz Data Sheet Summary
10 pages
M0128a1d RMC1600
No ratings yet
M0128a1d RMC1600
35 pages
AHDA Radio Description
No ratings yet
AHDA Radio Description
7 pages
Cloud Flexi Zone Controller Alarms 17A
No ratings yet
Cloud Flexi Zone Controller Alarms 17A
136 pages
Lte 2562
No ratings yet
Lte 2562
14 pages
Troubleshooting SBTS
No ratings yet
Troubleshooting SBTS
207 pages
IPAA Installation Guide
No ratings yet
IPAA Installation Guide
26 pages
RRM Features RL10 17A
No ratings yet
RRM Features RL10 17A
600 pages
Ts Lte - Bts - FDD SW 0010
No ratings yet
Ts Lte - Bts - FDD SW 0010
63 pages
Flexi Multiradio 10 Base Station Transmission Description
No ratings yet
Flexi Multiradio 10 Base Station Transmission Description
27 pages
Differentiated Admission Control Guide
100% (1)
Differentiated Admission Control Guide
31 pages
LTE Shiraz Qrxlev A2thre Trail
No ratings yet
LTE Shiraz Qrxlev A2thre Trail
12 pages
Paging Parameter Rollout Report - LTE
No ratings yet
Paging Parameter Rollout Report - LTE
12 pages
Study of Overshooting Cells Using ERA and Tilt Recommendations - Kish City
No ratings yet
Study of Overshooting Cells Using ERA and Tilt Recommendations - Kish City
16 pages
LTE Procedures for Engineers
No ratings yet
LTE Procedures for Engineers
116 pages
LTE Procedures for Engineers
No ratings yet
LTE Procedures for Engineers
116 pages
Feb09 - West Region CBI Overview
No ratings yet
Feb09 - West Region CBI Overview
28 pages
LTE FDD Throughput Guide
No ratings yet
LTE FDD Throughput Guide
8 pages
Telecom Network Optimization
No ratings yet
Telecom Network Optimization
2 pages
Dual Carrier Strategy
No ratings yet
Dual Carrier Strategy
10 pages
Inter Working (IWK) Solution
No ratings yet
Inter Working (IWK) Solution
12 pages
Optimize FACH Bandwidth Expansion
100% (1)
Optimize FACH Bandwidth Expansion
5 pages
HSDPA Description (2008!05!30)
No ratings yet
HSDPA Description (2008!05!30)
51 pages
Frequency Planning in MapInfo Guide
No ratings yet
Frequency Planning in MapInfo Guide
26 pages
Transmission Resource Management Description (2008!05!30)
No ratings yet
Transmission Resource Management Description (2008!05!30)
39 pages
HSUPA Description (2008!05!30)
No ratings yet
HSUPA Description (2008!05!30)
61 pages
VRF Aware IKEv2 Crypto Map VPN - Integrating IT
No ratings yet
VRF Aware IKEv2 Crypto Map VPN - Integrating IT
7 pages
Anyconnect Ordering Guide
No ratings yet
Anyconnect Ordering Guide
13 pages
Security Policy SSG-5-20 ScreenOS 5 4
No ratings yet
Security Policy SSG-5-20 ScreenOS 5 4
21 pages
Cisco: Questions & Answers
No ratings yet
Cisco: Questions & Answers
8 pages
Dokumen
No ratings yet
Dokumen
372 pages
Presentation 7168 1572420263
No ratings yet
Presentation 7168 1572420263
107 pages
VPN Solutions for IT Professionals
No ratings yet
VPN Solutions for IT Professionals
23 pages
VPN Performance in Unstable Networks
No ratings yet
VPN Performance in Unstable Networks
35 pages
Fortinet NSE 4 Exam Questions & Answers
No ratings yet
Fortinet NSE 4 Exam Questions & Answers
58 pages
Cisco SA 500 VPN Security Appliance & GreenBow IPSec VPN Client Software Configuration (English)
No ratings yet
Cisco SA 500 VPN Security Appliance & GreenBow IPSec VPN Client Software Configuration (English)
14 pages
Cisco IOS XE SD-WAN Command Guide
No ratings yet
Cisco IOS XE SD-WAN Command Guide
2 pages
Undocumented ScreenOS Commands Guide
No ratings yet
Undocumented ScreenOS Commands Guide
8 pages
Security Configuration Guide of NSX-6.4-final-U1 PDF
No ratings yet
Security Configuration Guide of NSX-6.4-final-U1 PDF
13 pages
AJEST 12.b SG
No ratings yet
AJEST 12.b SG
274 pages
Remote Access VPN Configuration Guide
No ratings yet
Remote Access VPN Configuration Guide
6 pages
Rfc2409-The Internet Key Exchange (IKE)
No ratings yet
Rfc2409-The Internet Key Exchange (IKE)
41 pages
350-701 Corregidos 491Q
No ratings yet
350-701 Corregidos 491Q
143 pages
Chapter 8: Implementing Virtual Private Networks
No ratings yet
Chapter 8: Implementing Virtual Private Networks
168 pages
c8000v Releasenotes 17 11
No ratings yet
c8000v Releasenotes 17 11
9 pages
CCNA Security: Router Protection
No ratings yet
CCNA Security: Router Protection
33 pages
Configuring IPsec VPN with Pre-Shared Keys
No ratings yet
Configuring IPsec VPN with Pre-Shared Keys
44 pages
Báo cáo cuối kì môn thực hành an ninh mạng
No ratings yet
Báo cáo cuối kì môn thực hành an ninh mạng
5 pages
MP1700X and MP1800X Series Router WEB Manual (8.11.0.88 (R) - 20211015)
No ratings yet
MP1700X and MP1800X Series Router WEB Manual (8.11.0.88 (R) - 20211015)
86 pages
Azure Network Security
100% (2)
Azure Network Security
29 pages
Azure Networking Solutions Exam Guide
No ratings yet
Azure Networking Solutions Exam Guide
83 pages
Amazon VPC Nag
No ratings yet
Amazon VPC Nag
136 pages
FortiGate Site-To-Site IPsec VPN Guide - Private WAN IPs With Public Gateway IPs
No ratings yet
FortiGate Site-To-Site IPsec VPN Guide - Private WAN IPs With Public Gateway IPs
6 pages
Huawei Device Configuration Commands
No ratings yet
Huawei Device Configuration Commands
28 pages
300 730 SVPN v1.1
100% (1)
300 730 SVPN v1.1
2 pages
Paloalto Networks NGFW-Engineer Exam
No ratings yet
Paloalto Networks NGFW-Engineer Exam
12 pages