RNC16 BTS Alarm and Fault Doc

RNC16 Operating Documentation
RNC RNW and Flexi Multiradio WCDMA

BTS Alarms and Faults
DN09210427
Issue 01D
Approval Date 2016-06-07
MA
1. Introduction
1.1 Overview and structure of alarms
The Alarm Reference Manual is intended for the operating personnel. It describes the alarms printed out on an alarm
output device and contains, when necessary, instructions for corrective maintenance actions.
The manual contains the alarms of all applications, and therefore it is possible that it also contains alarms that do not

belong to the configuration of a particular customer.
The user of this manual is assumed to understand the operation and the maintenance of the system.
According to the alarm type and the origin of the alarm, the numbering of the alarms conforms with the following:
Notices 0 - 999
Disturbances 1000 - 1999
Failure Printouts 2000 - 3999
Base Station Alarms 7000 - 8999
1.2 Handling of BTS alarms and faults

This document describes the handling of base station (BTS) alarms and faults. The base station software uses these
alarms and faults as a basis for internal diagnosis and fault reporting through the radio network controller (RNC) to
the Operations Support System (OSS) and the BTS Site Manager.
Base station (BTS) alarm handling is based on unit or module state information. It prevents the sending of
unnecessary alarms by checking and updating unit states. Fault messages come either from hardware devices or
software components. The faults are system or hardware specific. The Fault Diagnosis System creates upper
network alarms, which are based on an analysis of the faults, and sends them to the BTS Site Manager and to the
radio network controller (RNC).
In addition NetAct is used for handling the BTS alarms.
The BTS is able to maintain alarm handling after it has been commissioned and is in a configured state. During the
start-up, the BTS waits for the real-time clock from the Network Time Protocol (NTP) server, and the fault diagnosis
starts after the time has been set or a time-out has been detected. If the BTS is unable to set the time using the NTP
server, the default time (1.1.2004) will be used.
BTS transmission alarms

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

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

The 'Cancel' alarms are always sent to hosts (WCDMA BTS Site Manager and the RNC). When the unit or cell is in a
blocked state, the 'Start' alarms are only sent to WCDMA BTS Site Manager.
When a unit or cell is unblocked, all the active alarms related to the unblocked unit, module, or cell are automatically
sent to the hosts.
2. How to read this excel report

The excel report provides a full information on faults and alarms. It shows the full set of fault and alarm attributes
including the change information.
The excel report consists of two main sections:

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

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

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

This section shows the full alarm information including the following items:
- fault ID
- fault name
- meaning of the fault
- instructions
- list of related alarms
- change information
2.3 Field descriptions

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

Change information is a part of Alarm List and Fault List sections and is available in the following ways:
1. Definition on whether the fault/alarm is new, removed. That definition is provided in the following columns:
- Changes between issues ... which shows the changes since the previous issue of the document.
- Changes between releases ... which shows the changes since the latest issue of the document in the
previous product release.
If the cell is empty, the alarm/fault is not changed, nor new, nor removed.
Note that removed alarms/faults are listed in the very bottom and they are marked with red font.
Filters are enabled for convenient browsing of the change categories.
2. Detailed change information showing the current and previous values of parameter attributes. That
information is provided in the following columns:
- <fault/alarm attribute> in issue ... which shows the value in the previous issue of the document.
- <fault/alarm attribute> in release ... which shows value in the latest issue of the document in the previous
product release.
The columns are grouped into attribute-specific sections for structured and convenient view. Use unfold (+)
and fold (-) buttons in the top bar to browse the attribute-specific change details. Use unfold all (2) and fold
all (1) buttons on the left hand side of the top bar to respectively show and hide the change details for the
whole report.
Note that for all faults/alarms except new and removed ones, the field values for previous issue and previous
release are always provided to show a total history information. Additionally, the changed attributes of
faults/alarms are highlighted with grey color. Highlights are enabled to specify whether there is a change
between issues or releases.
whole report.
Note that for all faults/alarms except new and removed ones, the field values for previous issue and previous
release are always provided to show a total history information. Additionally, the changed attributes of
faults/alarms are highlighted with grey color. Highlights are enabled to specify whether there is a change
between issues or releases.
s printed out on an alarm
s.
ntains alarms that do not
e system.
ms with the following:
ation software uses these

ork controller (RNC) to
the sending of
m hardware devices or
em creates upper
te Manager and to the
gured state. During the

and the fault diagnosis
et the time using the NTP
smission equipment uses

he OMS or in the NetAct
descriptions.
ation of the modules at
set is required to cancel

the fields 'Fault source'
hen the unit or cell is in a
or cell are automatically
and alarm attributes

and alarm attributes
ns. Use fold (-) and unfold
the following ways:
in the following columns:
the document.
he document in the
with red font.
er attributes. That
e document.
cument in the previous
ent view. Use unfold (+)

e unfold all (2) and fold
change details for the
vious issue and previous

anged attributes of
her there is a change
vious issue and previous
anged attributes of
her there is a change
Note:
See the How to Read This Report tab
for instructions on the usage of Alarm List
Changes between issues Changes between releases Alarm Number

01C and 01D RNC8.1 and RNC16
Changed 7401
Changed 7402
Changed 7403
Changed 7404
Changed 7405
Changed 7406
Changed 7407
Changed 7408
Changed 7409
Changed 7410
Changed 7411
Changed 7412
Changed 7413
Changed 7414
Changed 7415
Changed 7416
Changed 7417
Changed 7418
Changed 7419
Changed 7420
Changed 7421
Changed 7422
Changed 7423
Changed 7424
Changed 7425
Changed 7426
Changed 7650
Changed 7651
Changed 7652
Changed 7653
Changed 7654
Changed 7655
Changed 7660
Changed 7661
Changed 7665
Changed 7740
Changed 7750
Changed 7761
Changed 7762
Changed 7771
Changed 7772
Changed 7773
Changed Changed 7775
7776
Changed 7778
Changed 7779
7780
Changed 7781
Changed 7782
Changed 7783
Changed 7784
Changed 7786
7794
Changed 7795
Changed 7796
Changed 8999
Alarm Name Alarm Group Event Type
EXTERNAL AL 1 Base Station Alarms ENVIRONMENTAL_ALARM


BASE STATION FAULTY Base Station Alarms EQUIPMENT_ALARM
BASE STATION OPERATION DEGRADED Base Station Alarms EQUIPMENT_ALARM
BASE STATION NOTIFICATION Base Station Alarms EQUIPMENT_ALARM
CELL FAULTY Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
CELL OPERATION DEGRADED Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
CELL NOTIFICATION Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
BASE STATION LICENCE EXPIRED Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
BASE STATION LICENCE NOTIFICATION Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
BASE STATION TRANSMISSION ALARM Base Station Alarms COMMUNICATIONS_ALARM
BEATING WCDMA BTS ALARM Base Station Alarms PROCESSING_ERROR_ALARM
FAILURE IN WCDMA WBTS O&M Base Station Alarms COMMUNICATIONS_ALARM

CONNECTION
RNW O&M SCENARIO FAILURE Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
RNW DATABASE OPERATION FAILURE Base Station Alarms PROCESSING_ERROR_ALARM
WCDMA CELL OUT OF USE Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
HSDPA CONFIGURATION FAILED Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
INSECURE O&M CONNECTION Base Station Alarms COMMUNICATIONS_ALARM
INCONSISTENCY IN WCEL Base Station Alarms PROCESSING_ERROR_ALARM

CONFIGURATION PARAMETERS
HSDPA FAILURE IN WCEL Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
WCDMA BTS DEDICATED Base Station Alarms QUALITY_OF_SERVICE_ALAR

MEASUREMENT FAILURE M
RECOVERY ACTIONS ONGOING Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
HSUPA FAILURE IN WCEL Base Station Alarms QUALITY_OF_SERVICE_ALAR
M
NETWORK ELEMENT CONFIGURATION Base Station Alarms PROCESSING_ERROR_ALARM

ERROR
HSUPA CONFIGURATION FAILED Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
IP BASED D-NBAP LINK FAILURE Base Station Alarms COMMUNICATIONS_ALARM
RECOVERY ACTION FAILURE Base Station Alarms COMMUNICATIONS_ALARM
WCDMA BASE STATION OUT OF USE Base Station Alarms QUALITY_OF_SERVICE_ALAR

M
ALARM STATUS REQUEST HAS TIMED Base Station Alarms COMMUNICATIONS_ALARM

OUT
INCONSISTENCY IN HIGH PEAK RATE Base Station Alarms PROCESSING_ERROR_ALARM

HSPA CONFIG
HIGH SPEED COMMON CHANNEL Base Station Alarms QUALITY_OF_SERVICE_ALAR

PROBLEM M
RNC RADIO NETWORK EXTENDED Transmission Equipment ENVIRONMENTAL_ALARM

RANGE TEST ALARM Alarms
Default Severity Meaning
Minor This is an external user-defined alarm. The alarm

is defined by
the user in a hardware database.
The meaning of the additional information fields

depends on the
is defined by
Base Station type. Not all of the fields are used in
all fault
cases, and specific values indicate when a field
Minor This
doesisnotancarry
external user-defined alarm. The alarm
depends on the
is defined by value.
a meaningful
all fault
The effect of the alarm depends on the purpose
The
that meaning
was of the additional information fields
Minor This
doesisnotanconfigured
carry
depends
for on the
defined by value. alarm input in the BTS.
the user-defined
is meaningful
a
all fault
The
that meaning
Minor This
carry
depends
for on the
is defined by value. alarm input in the BTS.
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The meaning
that was of the additional information fields
configured
does not carry
depends on the
for the user-defined alarm input in the BTS.
a meaningful value.
all fault
that was configured
does not carry
a meaningful value.

that was configured
is defined by

depends on the
is defined by
all fault
Minor This
doesisnot ancarry
depends on the
a meaningful
all fault
The
that meaning
Minor This
doesisnot anconfigured
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning of the additional information fields
Minor This was
does anconfigured
isnot external user-defined alarm. The alarm
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
Minor This was
does anconfigured
carry
depends
for on the
the user-defined
is meaningful
a
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
Minor This was
does anconfigured
carry
depends
for on the
the user-defined
is meaningful
a
all fault
The meaning
that was of the additional information fields
configured
does not carry
depends on the
a meaningful value.
all fault
that was configured
does not carry
a meaningful value.

that was configured
is defined by

depends on the
is defined by
all fault
Minor This
doesisnot ancarry
depends on the
a meaningful
all fault
The
that meaning
Minor This
carry
depends
for on the
the user-defined
a meaningful
all fault
The
that meaning
configured
Critical A critical
does not fault
carry(or faults) has occurred in the base
depends
for the on the
user-defined alarm input in the BTS.
station.
a meaningful value.
all fault
The meaning
effect of theof the
alarmadditional
depends information fields
on the purpose
depends
that was on the
configured
Major A major
does notfault
carry(or faults) has occurred in the base
Base
for theStation type. Not
user-defined all of
alarm the in
input fields are used in
the BTS.
station.
a meaningful value.
all fault
The meaning
effect of theof the
alarmadditional
depends information fields
on the purpose
does not carry
depends
that was on the
configured
Minor A minor fault (or
a meaningful faults) has occurred in the base
value.
Base
for theStation type. Not
user-defined all of
alarm the in
input fields are used in
the BTS.
station.
all fault
Check the reason for the fault from the
The meaning oftext
supplementary the field
additional
of information fields
does not carry
depends
the alarm. on the
Critical A meaningful
a critical fault value.
(or faults) has occurred in a
unit/module (or
all
The fault
effect of thethatfault on thetofunctioning of the
units/modules)
Check the reason for belong
the fault the
from sector
the indicated
cases,
network and specific values indicate when a field
element
in the alarm. text field
supplementary
does
depends not carry
on the fault description. For more
Major of
A the alarm.
major faultsee
(or faults) has occurred in a
a meaningful
information, value.
base
unit/module
station fault (or
descriptions in WCDMA RAN and
depends
The effecton
ofthethethat
fault on thetofunctioning of the
units/modules)
Check
Flexi the reason
Direct System belong
for the fault the
from sector
the indicated
Base
network Station
elementtype. Not all of the fields are used in
in the alarm. text field
supplementary
Libraries.
all fault on the fault description. For more
depends
Minor of the alarm.
A minor faultspecific
(or faults) hasindicate
occurred in a a field
cases, and
information, values when
The meaningsee base
of the additional information fields
unit/module
does
station not carry
fault (or
descriptions in WCDMA RAN and
depends
The effecton
ofthethethat
fault on the functioning of the
units/modules)
a meaningful
Flexi Direct value. belong to the sector indicated
System
Base
network Station
elementtype. Not all of the fields are used in
in the alarm.
Libraries.
all fault on the fault description. For more
depends
Critical Check
A licence thefault
reason for the has
(orbase
faults) faultoccurred
from thein the base
cases, and specific
information, values indicate when a field
The meaningsee
supplementary oftext
the field
additional
of information fields
station.
does
station not carry
fault descriptions in WCDMA RAN and
depends
the alarm.on the
a meaningful
Flexi Direct value.
System
Libraries.
all
The fault
effecton
ofthethe fault on the functioning of the
depends
Check thefault
reason for the has
faultoccurred
from thein the base
Minor A licence
cases,
network and (or faults)
specific
element values indicate when a field
Base Station type.
supplementary text Not
fieldall of the fields are used in
station.
does
depends not carry
on the fault description. For more
all faultalarm.
of the
a meaningfulsee
information, value.
base
The
station meaning
fault of the additional
descriptions information
in WCDMA RAN andfields
does
The not
effectcarry
ofthethe fault on the functioning of the
depends
Check
Flexi theonreason
Direct System for the fault from the
a meaningful
network element value.
Base Station
supplementary
Libraries. type.
textNot
fieldall of the fields are used in
depends
all the on
faultalarm. the fault description. For more
of
Check the reason
information, see basefor the fault from the
supplementary
station fault text field in WCDMA RAN and
descriptions
doeseffect
The not carry
of the fault on the functioning of the
of theDirect
Flexi alarm.System
a meaningful
network element value.
Libraries.
depends on the fault description. For more
The effect of the fault on the functioning of the
Check the reason
information, see basefor the fault from the
network element
supplementary text field in WCDMA RAN and
station fault descriptions
depends on the fault description. For more
of theDirect
Flexi alarm.System
information, see base
Libraries.
Minor A transmission fault (or faults) has occurred in the
BTS. This alarm is
an encapsulation alarm that is used to transfer
the Flexi Transport
Submodule (FTM) alarm data over the BTS O&M
Major The same radio network alarm has changed its
connection through RNC and
alarm state (start/cancel)
OMS to NetAct. Encapsulation is used because
20 times consecutively, always during informing
the RNC alarm system cannot
or cancelling delay,
support the FTM alarms directly due to
and has thus been filtered by the alarm system.
Minor This
differences alarm indicates in the alarm thatstructure.
a failure has occurred in
The same radio network
WBTS O&M
object is the object of both: the alarm in question
connection.
In NetAct and The OMS problem this alarm is related is shown to Iubin opened
and the beating
connection
format. Thisbetween means that
alarm that caused it.
controller
the and WBTS.
Major Thealarm alarmnumber, indicatesalarm a failure text in and some supplementary
of the
From
information controller are point ofinview, the actual reason
shown
following scenarios:
for
original the failureFTMrestart format and the alarm printout is thus
- Controller
is
different either in in the
NetAct transmission network between the
- WBTS initialization or WBTS reset
controller
compared andto WBTS,
alarm listings inor RNC MML interface
- cell initialization, activation blocking
Major RNW
in
that database
theshows
internal these operation
communication
FTM has of failed. This reading
controller
- forced handover
or
applications
alarms writing operation
or in WBTS
- modification of configuration data 7665.
as instances of alarm number
was
configuration. tried for some of the following scenarios:
- pid data updating (storing the process id of the
Check - WBTS reset
telecomthe reason for the fault from the
process
This
supplementary- WBTS alarm initialization
is setinformation
by controller in the following
Major The which alarm indicates
is responsible that anfields
of managing unlocked theWCDMA
situations:
and - Cell activation
supplementary text field of the alarm. The
cell
WBTS/WCELL has been blocked in question) for
actual -1)Cell WBTS blocking has and
documentation closed the
for O&M connection.
-some WBTS reason,
capability it cannot
information transmit
updating any traffic.
the -2)Cell WBTS unblocking
encapsulated O&M connection
alarm can supervision
be found in message the BTS
This
- Connection alarm is set configuration (COCO(IPA-
has
faults - Modification
not arrived
documents ofwithin
configuration
in data
only
RNC))/IPNB when a cell managementis moved to the blocked state by
Major This
WCDMA - Storing
the alarm
expectedthe
RAN indicates
pids
and time. that Direct
Flexi there has System beenLibraries.
an error
the
-when Auditsystem, handling
-3)Storing
There controller
the
is a WBTS has capability
problem in transmission information network
meaning
-requested Common that channela usersupervision initiated state change does
between
The - Storing cchconfiguration
effectcontroller
of the fault onor
parameters the reconfiguration
functioning of of the
not
-HSDPA cause
Common this
measurement
network - Celland channels
unlocking
WBTS.
element to BTS supervision
depends
alarm.
-via WBTS recovery (system initiated BTS restart
on -4)CellAPhysical
the reconfiguration
WBTS
faultindicatesShared
id conflict
description. Channel
has
For beenmoreReconfiguration
detected
information, in the see
Minor The
operation) alarm that one or more network
procedure.
network.
base - Controller
station restart
fault
elements
The
- Iu service have
alarm isbarring established
set when one of the following
descriptions
an -5)Audit
O&Mhandling
O&M connection
connectionin WCDMA is opened
with RAN
insecure and for Flexi
SBTS.
protocol Direct
while
situations
-The Cell deletion occurs:
System - Iu causes
service Libraries. which result in this alarm are:
barring
the
- Dedicated 1.controller
WCEL state is configured
measurement is changed from
initiation
As
in - Resource
a- consequence
probing status indication
security ofbl-
mode. this alarm
In handling
probing under modesituations
the
Minor -The BTS WO
alarmO&M -> BL(B),
data
indicates update WBTS
during
inconsistency establish/release
inbetween
-1), -aCommon
problem
2) and 3), in transmission
measurement
the network
supervision
secure
BTS - WO
O&M connections
->link BL(S), are
bl- system failure
parameterization
controller- BTS O&M and ofdata BTS between
availability
preferred, - WO and i.e.
-> the update
WBTS
BL(I), alarm O&M
bl- may
init
during
functionality
be an establish/release
might be
indication of a
controller
-BTS
limited. BTSO&M has rejected
link BTS.the It may be raised because
configuration or of
failure
These - WO in setting
->
scenariosofcan BL(L), up a bl- C-NBAP
be a consequence of either link failure
these
reconfiguration reasons: HSDPA
secure
user connection.
- operation
WO -> BL(M), orparameters bl- Common measurement
1.
Depending Configuration
channels on(or the scenario, in BTS
this might hasnot be
Major User-initiated
A
failure
operation major fault performed
or automatic
faults) by occurs
the
O&M
system. infailure
tasks
theUser BTS.(for Aled
unitto
consistent
-a
example, Controller
situation SW is
where unable
download, to send
HW the HSDPA
(or
Problems
operation units)
- WO in
->
can transport
BL(Ub),
be, layer
bl-
for because Blocked or incorrect by user locally
with
configuration
cell state thecouldparametersto BTS be in controller.
that
certificates
from
example, take
WBTS care
WCEL ofnot
request,
installation HSDPA
creation
modified
and
would WBTS
traffic
with
from
in
Element WCEL blocked
restart) can
Manager
to
cannot
be
working
be ofThese
controller
performed parameters
state internal
or
in case are CellRange,
problems (for example
faulty,
cause
or by plan.or
thethere network is not element to establish the
RACHCapacity,
congestion
vice
of an versa
Iub O&Minin Iub RACHPreambleSignatures,
controller
connection or itwithwas
problem. not possible
The WBTS to
enough
connection
Operations It is capacity
possiblewith
performed available
controller
that the by WCELin
the the
system BTS
state WSP
changes
are cards
in most
Major This
send
also alarm
SIB7factor,
interface)
configuration
cannot isreport
set when
ShutdownWindow,
its Dedicated
alarms Measurement
and
for
insecure
first
cases the
from HSDPA
relatedWO toservice.
protocol when the controller is
(for
to transmitted
ShutdownStepAmount.
data the tocontroller.
WBTS. code
Failure power)
in pid updating can cause
configured
recovery
Initiation to BL(H) in
operations, probing
(bl - shutting mode.
for down)
example andcommon only after
Location
trouble
This alarm tofails
The situation and
other
is set
due
the causing
O&M to the this
nature
when an
followingalarm
ofHSDPA-capable
the failure three
does can cases
notbeBTS
that
channel
during
obstruct to onesupervision.
cellnetwork
determined
scenarios
This wherefrom not the
that information is needed, and
sends ofalarm
initialization:
a Resource
the
operations.
does
above indicate
Status
mentioned a failure
states. Thisin WBTS
alarm is
Minor supplementary
failure
user
The
Indication in
plane
alarm (RSI)WBTS links.
indicates information
The
message that fields
controller
viathe NBAP of this
has alarm.
started
to RNC
not
In
1)
2. set
general,
BTS
The problem,
WCEL all in failuressuch
the cause
aslinks
nounit ofcell(s)
response orto nack
behas
capability
states
WBTS
indicating of updating
the
recovery user
thathence HSDPA orobject
plane
actions CCHstate parameter
can thechecked
be alarm
updating
blocked
2)
too when
NBAP-D
many andthe link WCEL is down state changes from WO to
The
can
using
due
is consequence
cause
to
changedOMS
abut inconsistent
Topology
non-performing
to "disabled". of this WCDMA alarm
As a consequencedependscell. During on the
of
BL(H),
unavailable
3) NBAP-D
adjacencies it is
to
module traffic.
configured has a so problemthat thus the (controller
size of the in
HSDPA
data
Browser.
recovery to be configuration
used
actions in controller phase. and problems
this set
internal)
System
alarm, when HSDPA the itBL(H) cannot state is replaced by one
-signalling
transmitIn case the
or initial
in configuration of HSDPA
connections
of
Failure the inany
Information
traffic.
cellcannot blocking
Block
be can
(SIB)
usedlead
would to
in thaterroneous particular cell.
exceed the cell
channels
actual calls. fails, the effect
state
Controller
maximum above mentioned
retriesconnections
size. blocked
Dedicated Measurement states.
The is that
RSIHSDPA
alarm isinset
message when regarding some of cannot
HSDPA be
the following used in
disabling
information
Initiation
this particular after the
the controller.
cell at
situations
can This arrive occur:
also is
alarm afteralsothe raised
corresponding
In case of parameter NBAP-D link
also inconsistency, isinre-created
BL(I) the -> BL(I,L)
to be are
alarm
1.
whole
transfer
Failure
all. Incell
Common this
when
in iscase
WBTS measurements
reported
C-NBAP capability
the HSUPA
as "disabled"are missing
updating
connections
by
or BTSandviais
pid
ready.
set
unavailable when If theBTS retry
if has
HSUPA
common
another goes measurement
RSI
down message.during
updating
succeeds,
failed isrecovery can
to accept
enabled the incause
alarm
the thecell. isBTS restart
cancelled.
parameters sent doneto itvia RNC:
during
This
incorrect - can
BL(I) WBTS actions
happen
-> BL(I,L), inhaveBTS
capability bl- failed.
recommissioning
C-NBAP
data to link
be failure
used phase
in the
cell
-2. setupoforreconfiguration
InCommon
case measurement of HSDPA channels
when
controller the celland isthus disabled initialization constantly
After
when
the this
BTSalarm,
effect ishas thatnot cells'
theresponded capacity to under the BTS
the parameter
fails.
in
problems the
AlarmBTSin end
7771 as
duepart
signalling to or ofactual
C-NBAPthe BTS linkmaintenance
calls. break would
might
sendingcell beduring
may affected.
not workcell with the intended HSDPA
3.
be Common
operations.visible Inchannel
this
in iscase creation constantly fails.
setup.
parameters.
4. There Theonly alarm cancelled automatically link after
this alarmis
case poor
can
RAN1461 handover-related
appear featuretogether withradio
is disabled. the Thisalarmssetup
is for
Major A major fault (or faults) occurs in the BTS. A unit
(or units)
taking care of HSUPA traffic in the WCEL can be
faulty, or there is not
enough capacity available on the BTS WSP cards
Critical The alarm indicates that the NEType indicated by
for HSUPA service.
the BTS and the Iub
Working Mode configured in the controller for the
This alarm is set when an HSUPA-capable BTS
WBTS object do
sends a Resource Status
not match. The controller sets this alarm when
Major This
Indication alarm(RSI) indicates message that there via NBAPhas been to theanRNC error
such a mismatch
when
indicating controller
that HSUPA state
is detected after the BTS O&M link establishment.
requested
is changedconfiguration to "disabled".orAsreconfiguration a consequence of of
HSUPA
this alarm, channels
HSUPAto
The consequences of this alarm are:
BTS
connections via Physical cannot Shared
be D-NBAP
used Channel
in that
Major One - WCEL or more unlocking IP-based operation linksparticular
under of aBTS cell.
this is
Reconfiguration (PSCR) procedure.
WCDMA
denied. BTS are detected lost
The
by theRSI message regarding HSUPA disabling
controller.
- WCEL creation under this BTS is denied.
The
can arrive possible also causes
after the which result in this alarm
- WCEL modification under this BTS is denied.
are:
whole cell is reported as "disabled" by BTS
The - The user plane traffic
creation, handling
modification, capability
and connection of via
theof a
Major This
another alarm RSI indicates
message. that automatic WCDMA BTS
WCDMA
related BTS is
recovery
-This There canhas action
happen been performed
ina problem
BTScapability in transmission
recommissioning phase
degraded, COCO or the traffic
(IPA-RNC)/IPNB of the whole
by
network
when controller
the between
cell has
is failed.
controller
disabled Theare denied.
recovery has been
WCDMA - WBTS BTS modification is is denied.
attempted
in and
the BTS.BTS because
end as part some of the BTS maintenance
totally - WBTS lost.and its child objects can be been
deleted.
of
-operations. the WCELs
BTS has rejected
In under
this the
case theconfiguration
WBTS have or
Major This - WCELalarmcan indicates
be locked.that there is a WBTS-level
detected
reconfiguration
this not toappear beHSUPA
of performing with the alarms for
Thisalarm
failure alarmthatcan causes
is set only iftogether the fault is detected in IP-
properly.
the channels.
same The
WCEL observed cause for the recovery is
all
based
The thealarm WCELs
D-NBAP is in the WO
canceled state underwhen
automatically this specific
the
given
-object: Controllerin alarm is unable to send the HSUPA
link(s)
WBTS ofto the
is become
deleted, WCDMA or BTS. The alarm is not set
supplementary
configuration
7761 RNW O&M information.
to BTS SCENARIO For
because FAILURE more information
unavailable.
for
no IP-based
mismatch D-NBAP
is detected links aftertothe
Major The
about
7771 alarm indicates
the recovery
of controller
WCDMA internal
CELL that due
problems
OUT OF USE theBTS
(for lack O&M
example of thelink
ifupload the C-NBAP
establishment. acknowledgement link is unavailable at the same
functionality
congestion inbehind
Iubwhen this alarm, see feature
This
time. alarm is set a known fault occurs and
message
descriptions
In interface)
case thefrom forthe
overall BTS,
features
WCEL the alarmstate
object uploadis WO cannot
makes all
be
RAN1302
(working) startedwhen between
and RAN1810
this the
alarm BTS in Product
the WCELs under a certain WBTS to become
and
Documentation.
Location the controller.
Minor appears,
The
unavailable alarmand check atthe
indicates the
once. naturethat of
reason thethe
for
Highfailure
the faultcan
Peak from
Ratebe the
determined
BTS
HSPA WSP-related from
configuration the
The reasons for this are the C-NBAP link break or alarms.
The alarm
reasonis(for forsetthe when two consecutive alarm
supplementary
parameters
Base Station information DCrecovery
HSDPAfields failure
or Dualof could
this
Band be
alarm. one
HSDPA
upload
of the requests have been
following:
or
Resource HSUPAManager IC or DC(BRM) HSUPA) hand crash in the
sent - The byamountthe controller without an actions on the
The
in
controller. least one of
at consequence WCEL WBTS
of thisof recovery
alarm
the BTSdepends
might not be
Minor This
acknowledgement
(restarts)
HSUPA alarm haveindicates
configuration been fromaused
failure
theup
phase in
forHS
BTS. a FACH or HS
consistent with the
RACH specific common WBTS channels
where
parameters
As a resultthe failure
inthistheobject RNC. for
occurred. the current day.
-in
If - the
this
The
If the cell.
alarm
total
failure Itof occurs,
amount setalarm,
isoccurred for the
there
of WBTS
the
cell whole
when
canrecovery
be a HSUPA
WBTS is
difference
actions in
In DC HSDPA
unavailable for case
traffic. this alarminitial
in the is also raised if the
-alarm the creation
(restarts)
configuration conditions
have ofbeen
or HS FACH/HS
in used up RACH common
BTS
There loses
can its also individual WCEL level alarms
be
channel
between for is fails
thethe
a specific
delivering controller
WBTS
HSUPA and
object. the
parameters BTS. toThis
the BTS,
Minor This
capability
active a test
for alarm
of supporting
the WCELs which DCisHSDPA.
used only for istesting
also a
-the - the
BTS capability
HSUPA restart of thedue
failed
connections WCEL to mismatches
missing BTS with HS
O&M
purposes
result
of this ifWBTS
userfor the if they were active prior to the
FACH/HS
The
connection.
cannotprecondition
be RACH in to this
setsystem
this alarm is RNC.
that the BTS
extended
locks
WBTS one level ofused
RNW the alarm
failure cells in particular
the cell ofpair cell
the at all.
during
O&M -
-This capability
BTS
If the link
does is
failure on not BTS
active. respond
occurred sidein to therestart request.
reconfiguration of
maintenance
detection. alarm does not indicate any fault situation,
-If-
the HS
the
BTS FACH/HS
BTS
HSUPA, is O&M
busy the RACH
link
handling is common
not active
software channels
at the
upgrade are
moment
and of
and the system
activities.
unavailable
the
rejects alarm
effect the
is upload
that due
restart the tocellsync
request.may loss not work with the
does
This not generate
alarm is setand onlythisif alarm
there by is atitself
least in one
any cell in
between
attempt,
intended BTS
alarm
HSUPA 7750RNC. is set instead.
circumstances.
The
the situation
WO state causing this alarm does not obstruct
-As Highaalarm Speed
result Cell FACH the Enhanced is enabled
Theparameters.
network
under isofhowever
theoperations.
WBTS.
this alarm, handled traffic
as any handling
actual
and configured
capacity of the for WCEL
WCDMA
alarm, so all the alarm
BTSin RNC maybut be BTS
reduced is not capablesome
because of supporting
WCELssame it.
handling
The
This alarm
alarm rules are valid
is cell-specific, forand it, and
not itindicated
hasonethe todo
If
not this alarmisproperly.
perform iscanceled
raised, then when UEatDRX least feature WCEL
adjustable
NetAct
under theby WBTSalarm is
default.
becomes out of use
parameters
Instead,
recovered the backas the
RNC-specific actual
toenabled)
the WOalarms.
alarm
state, 3325,
orfeatures
if the user
(if it was already
Recovery action is resumed as byboth
controller (HS
again,
"INCONSISTENCY
locks all the WCELs IN CONFIGURATION
FACHthe
after and faultHS RACH)
PARAMETERS",
under the WBTS.for is reported on NetAct when first
are pre-requisite
preventing operation of UE DRX feature.
instance of the 7795 recovery
is set. action has been
In case of High
corrected, and ifSpeed the problem Cell FACH Enhanced
For
mismatchmore information
theWCEL HS-RACH on thisis functionality, see
affecting
The alarmRAN the 7795documentation performance
is cancelled by the stillsystem
remains. when
WCDMA
not activated.
configuration
concerning feature at BTSRAN1461. and
RNC is consistent for High Rate HSPA features
(DC HSDPA, Dual Band HSDPA,
HSUPA IC and DC HSUPA) or when the cell is
deleted/locked.
Alarm indication preventions can be altered with

Supplementary Information Fields
1 in all BTS variants the value 100/64H in this field

indicates that the field has no relevant information.
In case of other values, see list below for details.
UltraBTS:
This field contains the rack (cabinet) number.
FlexiBTS:
The field meaning depends on the format given in 6th
UltraBTS:
field.
indicates
Format that the field
Meaning of has
this no
fieldrelevant information.
In1case of other values,
System module see list below for details.
identifier
FlexiBTS:
100/64H This field is not used.
UltraBTS:
field.
inThis
2 indicates fieldvariants
all BTS containsthe thevalue
rack (cabinet)
100/64H in number.
this field
Meaning of has
this no
indicates
In1case of that the field
other values, has no relevant information.
identifier
FlexiBTS:
UltraBTS:
field.
UltraBTS:
inThis
all BTS containsthe
that the field
thevalue
rack (cabinet)
has no 100/64H
relevant in
number.
this field
information.
Format
This field Meaning
contains of
thethis field
shelf number.
indicates
identifier
FlexiBTS:
FlexiBTS:
UltraBTS:
1 inThe
field. field variants
all BTS
UltraBTS:
meaningthe depends on the format
value 100/64H in thisgiven
field in 6th
2 inThis
field.
indicates
fieldvariants
all BTS containsthe
that the
thevalue
field
rack (cabinet)
has no 100/64H
relevant
number.
in this field
information.
Format
This fieldMeaning
contains of thethis field
shelf number.
indicates
InFormat that thevalues,
Meaning field
of has
this nolistrelevant
field information.
1case of other
System module see
identifier below for details.
FlexiBTS:
In1case of other interface
Optical values, see list below for details.
identifier
FlexiBTS:
The field meaning
100/64H This fielddepends
is not used.on the format given in 6th
UltraBTS:
1 inThe
all BTS
UltraBTS:
field in 6th
2 in
field.This
all fieldvariants
BTS containsthe thevalue
rack (cabinet)
100/64H number.
in this field
3 indicates
inFormat
This
all BTS
indicates
that
field the field
Meaning
contains
variants
that the
of
the
the
field
has
this no
field
shelf
value
has no
relevant in
number.
100/64H
relevant
information.
this field
information.
In Format
1case of Meaning
other of this field
indicates
FlexiBTS:
In1case of
System
that
otherthevalues,
module
field has
values,
see
see nolist
identifier below for
listrelevant
below for
details.
information.
details.
Optical
Thisinterface identifier
In100/64H
FlexiBTS:
case of other
The field meaning
field is not
values, see
depends
used.
list below
on the format for details.
given in 6th
100/64H
UltraBTS: This field is not used.
in all BTS variants the value 100/64H in thisgiven
The
1 UltraBTS:
field. field meaning depends on the format field in 6th
2 inThis
field.
UltraBTS:
indicates
fieldvariants
all BTS containsthe
that the
thevalue
field
rack (cabinet)
has no 100/64H
relevant
number.
in this field
information.
inFormat
This
3 indicates fieldMeaning
all BTS containsthe
variants
that
of
thethis
thevalues,
field value
has
field
shelf
no
number. in this field
100/64H
relevant information.
In Format
This
1casefield
of Meaning
contains
other
System of
modulethethis
slot
see field
identifier.
list
indicates
FlexiBTS:
other interface has
values, see nolistrelevant
below for information.
details.
Optical identifier
In100/64H
FlexiBTS:
case
The of This values,
other
field meaning
field is not
see
depends
used.
list below
on the format for details.
given in 6th
100/64H
FlexiBTS:
The
1 UltraBTS:
inThe
field. field
all BTS meaning
variants depends
the value on
100/64Hthe format
in thisgiven
field in 6th
2 in
field.This
all field
BTS meaning
fieldvariants
containsthe depends
thevalue on the format
rack (cabinet)
100/64H number.
in thisgiven
field in 6th
UltraBTS:
indicates that the field has no relevant in information.
3 inFormat
field.This
indicates
field
all BTS Meaning
contains
variants
that
of
the
the
thevalues,
field
this
value
has
field
shelf
no
number.
100/64H
relevant this field
information.
In Format
This
1casefield
of Meaning
contains
other
System of
modulethethis
slot
see field
identifier.
list
indicates
Format
FlexiBTS:
In1case of that the
Meaning field
of
other interface has
this
values, see no
list below for details.
Optical identifier
In100/64H
FlexiBTS:
1case
The of
RadioThis
other field isposition
values,
module
field meaning
not
see used.
list below
in chain for details.
100/64H
FlexiBTS:
UltraBTS: This fielddepends
is not used.on the format given in 6th
1 The
inThe
field. field
100/64H
all BTS meaning
This field
variants depends
theis not on
used.
value 100/64H the format
in thisgiven
field in 6th
UltraBTS:
field meaning depends on the format
2 inThis
field.
UltraBTS:
indicates
fieldvariants
all BTS containsthe
that the
thevalue
field
rack (cabinet)
has no 100/64H
relevant in thisgiven
number. field in 6th
information.
3 inFormat
field.This fieldMeaning
all BTS containsthe
variants of
thethis field
shelf
value number. in this field
100/64H
4 indicates
In Format
This
this
1case
indicates ofthat
field
field other
System
that
thevalues,
Meaning
contains
contains
the
field
of
thehas
this
slot
information
module
field see no
fieldrelevant
identifier.
list
identifier
has no on information.
the Fault
below for ID (4 digits)
details.
Format
FlexiBTS:
In1case of
that
Meaning of
other interface
Optical this
values, see listrelevant
field
identifier below for information.
details.
100/64H
FlexiBTS:
In1 casefield
of This
other
Radio field
values,
module is not used.
see list below for details. in 6th
The
100/64H
FlexiBTS:
triggered meaning
This isposition
depends
fieldand not on
theused.
in chain
the format
which given
field. fieldthe
UltraBTS:
The
100/64H
alarm,
meaning
This fielddepends
unit
is not used.on typethe format is
given in 6th
UltraBTS:
The field meaning depends on the format
considered
2 inThis
field. all BTS
UltraBTS: faulty.
fieldvariants
containsthe thevalue
rack (cabinet)
100/64H in this field in 6th
number.given
3 inFormat
field.This
Value fieldMeaning
all BTS
"NA" contains
variants
indicates of
the
the this
value
that field
shelf
the number.
100/64H
value in
is not this field
relevant.
4 indicates
Format
This
this
1 field
indicates
that
field the field
Meaning
contains
contains
System
that the
of
thehas
this
slot
information
module
field
no
fieldrelevant
identifier.
identifier
has no on the Fault
relevant
information.
ID (4 digits)
information.
Format
FlexiBTS:
In1case of Meaning of
other interface
Optical this
values, see field
identifier
that 100/64H This field isposition
not
seeused.
5 FlexiBTS:
In
in1case
all BTS
The of
field other
Radio values,
module
variants
meaning the value
depends list below
in
100/64H
on chain
the for details.
in this
format field in 6th
100/64H
FlexiBTS:
triggered
The fieldtheThis
meaning
field
alarm, and is not used.
the unit
depends on type
the which given
format is
given in 6th
field.100/64H
indicates
UltraBTS: This
that thefield
fieldis not
has used.
no relevant information.
inThe
considered
2
field. fieldfaulty.
all BTS
UltraBTS:
In case of
meaningthe
variants
other
depends
values, value
see
on the format
100/64H
list below in this
for
given
field in 6th
details.
3 inFormat
field.This
Value fieldMeaning
all BTS
"NA" contains
variants
indicates of
the
the this
value
that field
shelf
the number.
100/64H
value in
is not this field
relevant.
4 indicates
Format
This
this
1 field
indicates
that
field the field
Meaning
contains
contains
System
that the
of
thehas
this
slot
information
module
field
no
fieldrelevant
identifier.
identifier
has no on the Fault
relevant
information.
ID (4 digits)
information.
In Format
1case of Meaning of
other interface
Optical this
values, see field
identifier
that
UltraBTS:
in100/64H
5 FlexiBTS:
In 1case
all BTS
100/64H
FlexiBTS:
of
RadioThis
other
This
field
values,
module
variants the
field
isposition
not
seeused.
is value
not
list below
in
100/64H
used. chainfor details.
in this field
triggered
This
The the
field alarm,
contains
field meaning and
the the
unit unit
on type
number. which given
is
is not used. the format in 6th
UltraBTS:
FlexiBTS:
UltraBTS:
field.
indicates
Meaning of has
this no
identifier
FlexiBTS:
UltraBTS:
field.
inThis
all BTS containsthe thevalue
rack (cabinet)
100/64H in number.
this field
Meaning of has
this no
indicates
identifier
FlexiBTS:
UltraBTS:
field.
UltraBTS:
inThis
all BTS containsthe
that the field
thevalue
rack (cabinet)
has no 100/64H
relevant in
number.
this field
information.
Format
This field Meaning
contains of
thethis field
shelf number.
indicates
identifier
FlexiBTS:
FlexiBTS:
UltraBTS:
1 inThe
all BTS
UltraBTS:
field in 6th
2 inThis
field.
indicates
fieldvariants
all BTS containsthe
that the
thevalue
field
rack (cabinet)
has no 100/64H
relevant
number.
in this field
information.
Format
This fieldMeaning
contains of thethis field
shelf number.
indicates
InFormat that thevalues,
Meaning field
of has
this nolistrelevant
field information.
1case of other
System module see
FlexiBTS:
identifier
FlexiBTS:
The field meaning
is not used. on the format given in 6th
UltraBTS:
1 inThe
all BTS
UltraBTS:
field in 6th
2 in
field.This
all fieldvariants
BTS containsthe thevalue
rack (cabinet)
100/64H number.
in this field
3 indicates
inFormat
This
all BTS
indicates
that
field the field
Meaning
contains
variants
that the
of
the
the
field
has
this no
field
shelf
value
has no
relevant in
number.
100/64H
relevant
information.
this field
information.
In Format
1case of Meaning
other of this field
indicates
FlexiBTS:
In1case of
System
that
other thevalues,
module
field has
values,
see
see nolist
identifier below for
listrelevant
below for
details.
information.
details.
Optical
Thisinterface identifier
In100/64H
FlexiBTS:
case of other
The field meaning
field is not
values, see
depends
used.
list below
on the formatfor details.
given in 6th
100/64H
in all BTS variants the value 100/64H in thisgiven
The
1 UltraBTS:
field. field meaning depends on the format field in 6th
2 inThis
field.
UltraBTS:
indicates
fieldvariants
all BTS containsthe
that the
thevalue
field
rack (cabinet)
has no 100/64H
relevant
number.
in this field
information.
inFormat
This
3 indicates fieldMeaning
all BTS containsthe
variants
that
of
thethis
thevalues,
field value
has
field
shelf
no
number. in this field
100/64H
In Format
This
1casefield
of Meaning
contains
other
System of
modulethethis
slot
see field
identifier.
list
indicates
FlexiBTS:
other interface has
values, see nolistrelevant
below for information.
details.
100/64H Optical
This field is notidentifier
used.
FlexiBTS:
InThe
casefield
of other
meaning values, see list
depends onbelow for details.
the format given in 6th
100/64H
FlexiBTS:
inThe
1 UltraBTS:
field.The
field variants
all BTS
field
meaningthe
meaning
depends on the format
value 100/64H
depends on the in thisgiven
format field in
given
6th
in 6th
2 in
field.This
all fieldvariants
BTS
UltraBTS: containsthe thevalue
rack (cabinet)
100/64H number.
in this field
3 indicates
inFormat
field.This that
field
all BTS the field
Meaning
contains
variants of
the
the has
this no
field
shelf
value relevant in
number.
100/64H information.
this field
indicates
In Format
This
casefield
ofthat thevalues,
Meaning
contains
other field
of
thehas
this
slot
see no
fieldrelevant
identifier.
list below for information.
details.
1
indicates
Format System
that the
Meaning module
field
of identifier
has
this no
FlexiBTS:
identifier
In100/64H
FlexiBTS:
1case
The of
RadioThis
other
field meaning
field isposition
values,
module not
see used.
list below
100/64H
FlexiBTS:
UltraBTS: This fielddepends
is not used. on the format given in 6th
1 The
inThe
field. field
100/64H
all BTS meaning
This
variantsfield depends
theis not on
used.
value 100/64H the format
in thisgiven
field in 6th
UltraBTS:
This field meaning
fieldvariants
containsthe depends
thevalue on
rack 100/64H the
(cabinet) informat
number.given in 6th
2 in
field. all BTS
UltraBTS:
indicates that the field has no relevant in this field
information.
3 inFormat
field.This field
all BTS Meaning
contains
variants of
the
the this field
shelf
value number.
100/64H this field
4 indicates
In Format
This
this
1case
indicates ofthat
field
field other
System
that
thevalues,
Meaning
contains
contains
the
field
of
modulethe
field
has
this
slot
information
see no
fieldrelevant
identifier.
list
identifier
the Fault
below
relevant for ID (4 digits)
details.
information.
Format
FlexiBTS:
In1case of Meaning of
other interface
Optical this
values, see field
identifier
that
In1100/64H
FlexiBTS:
casefield
of This
other field
values,is not used.
see list below for details. in 6th
The Radio module
meaning isposition
depends on in chain
the format
100/64H
FlexiBTS:
triggered
fieldthe
UltraBTS:
The
This fieldand
alarm,
meaning
not
theused.
depends unit
on type which given
the format is
1 in
field.100/64H
all BTS
UltraBTS:
The
considered field
This
variants
meaning
faulty.
field
theis not
value
depends
used.
100/64H
on the in thisgiven
format field in
given
6th
in 6th
2 in
field.This
all fieldvariants
BTS
UltraBTS: containsthe thevalue
rack (cabinet)
100/64H number.
in this field
3 indicates
field.Format
inThis
all BTS
Value "NA" that
field the field
Meaning
contains
variants
indicates of
the
the has
this
value
that no
field
shelf
the relevant
number.
100/64H
value information.
in
is not this field
relevant.
4 indicates
In Format
This
this
1case
indicates ofthat
field
field other
System
that
thevalues,
Meaning
contains
contains
the
field
of
modulethe
field
has
this
slot
information
see no
fieldrelevant
identifier.
list
identifier
the Fault
below
details.
information.
Format
FlexiBTS:
In 1case of Meaning
other
Optical of
values,
interface this
see field
list
that
in100/64H
5 FlexiBTS:
In 1case
all BTS
The of
Radio
field
This
other field
values,
module
variants
meaning theisposition
not
seeused.
is value
depends list
on below
in
100/64H chain
the for details.
in this
format field in 6th
100/64H
FlexiBTS:
triggered
UltraBTS:
The fieldtheThis
meaning
field
alarm, and not
the
depends
used.
unit
on type
the which given
format is
given
1 100/64H
indicates
inThe
field. all BTS
UltraBTS:
considered field
This
that the
variants
meaning
faulty.
field
field
theis not
has used.
no relevant
value 100/64H
depends on the format field in
information.
in thisgiven 6th
in 6th
2 in
field.This
all
UltraBTS:
In case field
BTSof contains
variants
other thevalue
the
values, racklist
see (cabinet)
100/64H
below number.
in
for this field
details.
3 indicates
inFormat
field.This
all BTS
Value "NA" that
field the field
Meaning
contains
variants
indicates of
the
the has
this
value
that no
field
shelf
the relevant
number.
100/64H
value information.
in
is not this field
relevant.
4 indicates
In Format
This
this
1case
indicates ofthat
field
field other
System
that
thevalues,
Meaning
contains
contains
the
field
of
modulethe
field
has
this
slot
information
see no
fieldrelevant
identifier.
list
identifier
the Fault
below
details.
information.
In Format
FlexiBTS:
1case of Meaning of
other interface
Optical this
values, see field
identifier
that
UltraBTS:
in100/64H
5 FlexiBTS:
In 1case
all BTS
The of
Radio
field
This
other field
values,
module
variants
meaning theisposition
not
seeused.
value
depends list
on below
in
100/64H chain
the for details.
in this
format field in 6th
100/64H
FlexiBTS:
triggered
This
UltraBTS:
The the
field This field
alarm,
contains
fieldthat
meaning
is
and
the not
the
unit
depends
used.
unit
number.
on type which given
the format is
given in 6th
field.100/64H
indicates
UltraBTS: Thisthefield
fieldis not
has used.
no relevant information.
2 inThe
considered
field.
In This field
all BTS
UltraBTS:
case of
meaning
faulty.
field contains
variants
other
depends
thevalue
the
values, racklist
see
on the format
(cabinet)
100/64H
below number.
in
for thisgiven
field in 6th
details.
3 inFormat
field.This
Value fieldMeaning
all BTS
"NA" contains
variants
indicates of
the
the this
value
that field
shelf
the number.
100/64H
value in
is not this field
relevant.
4 FlexiBTS:
indicates
Format
This
this
1 field
indicates
that
field the field
Meaning
contains
contains
System
that the
of
thehas
this
slot
information
module
field
no
fieldrelevant
identifier.
identifier
has no on the Fault
relevant
information.
ID (4 digits)
information.
Format
The field
FlexiBTS:
In1case of Meaning
meaning of
other interface
Optical this
depends
values, see field
list below for details. in 6th
on
identifier the format given
that
UltraBTS:
In 100/64H
FlexiBTS:
case of This
other field
values,isposition
not
seeused.
5 in
field.1all
The BTSRadio
field module
variants
meaning the value
depends in
100/64H
on chain
the in this
format field in 6th
100/64H
FlexiBTS:
triggered
This
The the
field
field
This field
alarm, and
contains
meaning
is
the not
unit
depends
used.
the unit
number.
on type
the which given
format is
given in 6th
field.100/64H
indicates
Format
UltraBTS: This
that the
Meaning field
field
ofis not
has
this used.
no
inThe
considered
2
field.1case
fieldfaulty.
all BTS
UltraBTS:
In of
meaningthe
variants
other
This field
depends
values,
is not value
see
on the format
100/64H
list
currently below
used in
for
forthisgiven
field
details.
any
in 6th
purpose.
3 in
field.Format
This
all
Value field
BTS
"NA"
FlexiBTS: Meaning
contains
variants
indicates of
the
the this
value
that field
shelf
the number.
100/64H
value is in
not this field
relevant.
4 indicates
Format
This
this
100/64H
1
indicates
that
field
field thefield
Meaning
contains
contains
This
System
that
field
of
thehas
this
slot
information
module
thevalues,
fieldcontainsno
fieldrelevant
identifier.
identifier
has no on
thethe
relevant
information.
unitFault
number.ID (4 digits)
information.
In Format
The
1casefield
of Meaning
meaning
other
Optical of
interface this
depends
see fieldon
list
identifier the format
below for given in 6th
details.
that
UltraBTS:
In 100/64H
FlexiBTS:
case of This
other field
values,is not used.
see list below for details.
5 in
field.1all BTSRadio module
variants the position
value in
100/64H chain in this field
in100/64H
6 FlexiBTS:
triggered
This
The field
100/64H
indicates
the
field
all BTS This
meaning
This
that the
field
alarm,
contains
variants the
field
is value
and
the not
theused.
unit
depends
fieldis not
has
unit
number.type
100/64H
on
used.
no relevant
which
in
the format isfield in 6th
thisgiven
information.
Format
UltraBTS: Meaning of this field
2 inThe
considered
field. fieldthat
indicates
all BTS
UltraBTS:
meaning
faulty.the field
variants depends
the has
value on
no100/64H the format
relevant thisgiven
field in 6th
information.
in
UltraBTS:
FlexiBTS:
UltraBTS:
field.
indicates
Meaning of has
this nofieldrelevant information.
identifier
FlexiBTS:
UltraBTS:
field.
inThis
2 indicates
all BTS fieldvariants
rack (cabinet)
100/64H in number.
this field
Meaning of has
this nofieldrelevant information.
indicates
identifier
FlexiBTS:
UltraBTS:
field.
UltraBTS:
2 inThis
indicatesall BTS fieldvariants
rack (cabinet)
100/64H in number.
this field
Format
This fieldMeaning contains of thethis field
shelf number.
indicates
that that the field has no relevant information.
1 theSystem field hasmodule
no relevant
identifierinformation.
FlexiBTS:
In case
caseof
In100/64H
FlexiBTS: ofother
other values,
values,
This field
see
is not
list
listbelow
seeused. belowfor fordetails.
details.
1 The field meaning depends
in all BTS variants the value 100/64H in this
field. on the format given
fieldin 6th
UltraBTS:
UltraBTS:
field.
indicates
Format
This Meaning of this field
Thisfield
indicates
Format field
that
contains
contains
the field
Meaning
the
the
has
shelf
rack
no
number.
(cabinet)information.
relevant number.
that
1 theSystem field has noofrelevant
module this field
identifierinformation.
In 1case
In100/64H of other
Optical
case of other values,
interface
values, see list
list below fordetails.
identifier
seeused. below for details.
FlexiBTS: This field is not
FlexiBTS:
The
1 UltraBTS:
in The field
all BTS meaning
fieldvariants
meaningthe depends on
value 100/64H
depends the format
on the format in thisgiven
field
ID in 6th
given in
2 UltraBTS:
in
field. all BTS variants the value 100/64H in this field
indicates
6th infield.
This
3 indicates
all field
BTS contains
variants the
the shelf
value number.
100/64H in this field
This field
Format that contains
the field
Meaning the
thisrack
has no (cabinet)information.
relevant number.
that
indicatesthe field
Format ID has
that value noofrelevant
thevalues,
field Meaning
has
field
nolistinformation.
of this field
In case
In1case
case of other
Optical
otherinterface
ofother values,seeseeidentifier
see below
listbelow
below for
fordetails.
details.
In 1
FlexiBTS: of System
values, modulelist identifierfor details.
FlexiBTS:
100/64H
The
1 UltraBTS:
in The field
all BTS meaning This
dependsfield is
on not
the used.
format given in 6th
fieldvariants
meaningthe value 100/64H
depends on the format in this field
ID given in
UltraBTS:
field.
UltraBTS:
indicates
6thinfield.
3 This
all field
BTS contains
variants the
the shelf
value number.
100/64H in this field
2 that This
inFormat
alltheBTS field contains
variants the rack (cabinet)innumber.
This
Format
indicates
field Meaning
fieldcontains
ID
that has
value nothe
of
the field
the value
this
slot
relevant field 100/64H
identifier.
has no information.
Meaning of this field
relevant
this field
information.
indicates
1
Incase
case Optical
ofother interface
othervalues,
values,see identifier
seelistlistbelow
below fordetails.
details.
1
FlexiBTS:
In System module identifier
that theoffield
FlexiBTS:
100/64H
FlexiBTS: hasfield
This no relevant
is not used.information. for
1 In 100/64H
The
inThe field
all field
BTS meaning
variants This
depends
the field
value is
on not
the
100/64H used.
format
in thisgiven
field in 6th
The
case field meaning
of other
meaning values,depends
dependssee list on on theformat
below
the format
for ID
details.
given given in
in 6th
UltraBTS:
field.
UltraBTS:
indicates
6th
3 in
field. field.
all BTS variants the value 100/64H in this field
2 that This
inThis
alltheBTS field contains
variants the rack (cabinet)innumber.
Format
Format
UltraBTS:
indicates
Format
field Meaning
fieldcontains
ID
that has
value nothe
of
the field
Meaning
the
of
value
this
slot
relevant
Meaning
has
this
field
no
field
100/64H
identifier.
information.
of this field
relevant
this field
information.
indicates
1
In1This
case Optical
ofother
other interface
values, identifier
see list below fordetails.
details.
In 1 field
case System
contains the module
shelf identifier
number.
that theof
FlexiBTS:
100/64H
FlexiBTS:
Radio
field has
This
values,
module see
isposition
no relevant
field not
list
used.
below
in chainfor
information.
1 In 100/64H
100/64H
inTheall field
BTS This field
variants This
is
the notfield
value is
used. not
100/64H used. in this field
The
case field meaning
of other
meaning values,depends
dependssee list on on theformat
below
the format
for ID
details.
given given in
in 6th
UltraBTS:
FlexiBTS:
UltraBTS:
indicates
6th
3 in
field. field.
all BTS variants the value 100/64H in this field
2 This
inThis
allfield
The BTS field
field contains
variants
meaning thethe rack
value
depends (cabinet)
100/64H
on innumber.
this
IDIDfield
4 indicates
this
that the
Format
UltraBTS:
Format
field contains
contains
field
ID
that has
value no the slot
information
ofrelevant
the field
Meaning Meaning
has
this nofield ofthe
identifier.
information.
relevant
format
thisFault
field
information. (4given in
digits)
indicates
6th
that field.
In1This
case ofother
other values, see list below fordetails.
details.
In 1 field
case System
contains the module
shelf identifier
number.
theof
FlexiBTS:
thatFormat
FlexiBTS:
triggered
Radio
field has
ID value
the
values,
module
alarm, noand see
position
relevant
Meaning
the
list
unit
below
in chain
information.
of
typethis
for
field is
which
100/64H
in100/64H This fieldThis
is notfield is not used.
1 In all field
1The
case
The
considered
UltraBTS:
BTSfield variants
meaning
offaulty.
other
meaning the
values,
Optical seeused.
value
depends
interface
depends 100/64H
list
on on theformat
below
identifier
the in this
format
for field
ID
details.
given given in
in 6th
FlexiBTS:
UltraBTS:
indicates
6th field.
field.
2 Value100/64H
This
inThis "NA"
allfield
BTS field indicates
contains
variants This
that
thethe field
rack
value is not is
theidentifier.
value
(cabinet)
100/64H used.
not relevant.
innumber.
this field
4 this
thatThe the
Format field
field
fieldmeaning
contains
contains
ID has
value no depends
the slot
information
relevant
Meaning onofthe format
field IDID(4given
thisFault
information. in
digits)
UltraBTS:
Format Meaning of this field
indicates
6th
thatIn field.
case of variants
other values, see
3 1allBTS
in1This
5 FlexiBTS:
in all field
BTS Radio System
contains
variants
module the
the shelflist
module
value
position below
identifier
number.
100/64H
inthis
this field
FlexiBTS:
that
triggeredthe
Format field has
ID value
the alarm, nothe
and
value
relevant
Meaning
the
100/64H
unitinformation.
of
typethis in
field
which is
field
indicates
1 100/64H
100/64H
indicates
inTheall field
BTS thatThisthefield
variants This
fieldis
the not
has field
valueno is
used. not
relevant
100/64H used.information.
in this field
In 1The
case
considered
UltraBTS:
field meaning
offaulty.
other
meaning values,
Optical depends
dependssee list
interface on on theformat
below format
identifier
the for ID
details.
given given in
in 6th
FlexiBTS:
that
In case
indicates
6th theoffield
field. otherhasvalues,
no relevant
see listinformation.
below for details.
field.
2 Value100/64H
This
inThe "NA"
allfield
BTS field indicates
contains
variants This
that
thethe field
the is
value
racklist
value not
(cabinet)
100/64H used.
is not relevant.
innumber.
this
4 Inthis
that case
the field
of meaning
other
contains
field has no depends
values, see
information on the
below format
for
thisFault IDIDfield
(4given
details. in
digits)
Format
UltraBTS:
Format
indicates
6th field.
ID value
Meaning ofrelevant
Meaning
this field information.
of field
that
UltraBTS:
5 In
3 in case
1
in1This
allthe
all
FlexiBTS:
thatFormat
UltraBTS: BTS of variants
field
BTS Radioother
field
values,
System
contains
variants
module
has
IDcontains
value nothe
the
the see
shelflist
module
value
position
value
relevant
Meaning inbelow
identifier
number.
100/64H
100/64H chain
information.
of this
for
in
field
details.
inthis
this field
field
triggered
This
indicates100/64H fieldthe alarm, and
the
This the
unit
fieldunit
number.
is type
not which
used. is
In 100/64H
indicates
The
casefield that
field Thisthefield
meaning
offaulty.
other fieldis
values, not
has
depends
see used.
no relevant
on the information.
format ID given in
1
This
considered
UltraBTS:
FlexiBTS:
Optical
contains slot list
theinterface below
identifier
identifier. for details.
6th that
In casetheoffield
field. otherhasvalues,
no relevant
see listinformation.
below for details.
in100/64H
Value
4 FlexiBTS:
2 In
this This
The
case "NA"
allfield
BTS field
field indicates
contains
variants
meaning
ofcontains
other
This
that
the
values,the field
rack
value
depends
see
information
is
the list
valuenot is
(cabinet)
100/64H
on below
the
used.
not
format
for
Fault
relevant.
innumber.
this
IDIDfield
(4given
details. in
digits)
Format
UltraBTS:
FlexiBTS:
The field ID value
meaning Meaning
depends on ofthethisformat
field given in 6th
indicates
6th
that field.
UltraBTS:
3
5 in 1allBTS
inThis
The
all fieldvariants
BTS
field meaningSystem
contains
variants the
the module
dependsshelf100/64H
value identifier
number.
100/64H
on the ininthis
format thisID field
given in
field.
FlexiBTS:
that the
Format
UltraBTS:
triggered
This field
fieldthe has nothe
IDcontains
value
alarm, and
the
value
relevant
Meaning
the
unit unitinformation.
number.of
typethis field
which is
field
indicates
6th 100/64H
field.
indicates
Format that the
Meaning This
field
of has
thisfield
no
fieldis not
relevant used.information.
In1 The
casefield
This
considered field meaning
offaulty.
other values,
Optical
contains depends
the see
slot list
interface on the format
below
identifier
identifier. ID given in
for details.
6th FlexiBTS:
that
In 1casetheof
Format
field. field
ThisID
otherhasvalues,
value
field nonot
is relevant
Meaning
see list
currently information.
of
belowthis
used field
for
for details.
any purpose.
Value100/64H
2 FlexiBTS:
in100/64H "NA"
all BTS indicates
variants This
that
the field
the
value is
valuenot
100/64H used.
is notin relevant.
In The
1case
Format field meaning
of other
This Radio
field depends
values, see list
module
contains on
the the
unitformat
below
position in this
for IDfield
details.
chain
number. given in
UltraBTS:
FlexiBTS:
The
indicates
6th field.
100/64H field ID value
meaning This
Meaning
dependsfield onof
is the
not
this field
format
used. given in 6th
3 UltraBTS:
5 in
field.
that
1allBTS
inThis
The
allthe
fieldvariants
BTS
field
fieldmeaningSystem
contains
variants
has nothe
the
the module
dependsshelf100/64H
value
value
relevant on identifier
number.
100/64H the
information. ininthis
format thisID field
given in
field
6 in Format
UltraBTS:
This
all field
BTS
100/64H ID value
contains
variants the
the
ThisMeaning
unit
value
field number.of
100/64H
is not this field
used.in this field
indicates
6th In field.
indicates
Format
case that the
Meaning
ofthat
other field
of
values, has
thisseeno
field relevant information.
1
This
4 indicates
this
FlexiBTS:
that the
Format
field
field field theOptical
contains
contains
has
ID value field
no
the
has
relevant
Meaningnolist
interface
slot
information onbelow
identifier
identifier.
relevant for details.
the Fault
information.
of this field
ID (4 digits)
information.
1 probable cause reported by FTM
2 the managed object reported by FTM
3 alarm number reported by the FTM. The FTM has

1 the alarm number of the beating BTS alarm
reserved alarm numbers from space 61000 - 61999
2-15 if the beating alarm has any additional information, it

is
1 reason for the alarm
indicated here. Additional information is cut after 14
bytes and it is represented in hexadecimal format.
1 = failure in the controller - WBTS connection
2 = WBTS id conflict
3 = O&M connection opened for SBTS
1 reason for the failure
2 error code is received from IUB O&M connection. This
01 WBTS reservation has failed
field is
02 Configuration data updating has failed
significant only if the value of 1st field is 1
03 Inactivation of the cell has failed
1 specifies if the error occurred during reading from or
04 Activation of the cell has failed
writing to
05 Common channel deletion has failed
database
06 Common channel creation has failed
07 BCCH information updating has failed
01 Reading failure
1 08 indicates
WBTSthe state that
capability the WCEL
information was
was notchanged
receivedinto
02 Writing failure
and 09whatForced handover request was not accepted
caused
0A WBTS the capability
alarm to be set. Full information
information update hasabout failedthe
2 reason of the failure
current
0B AAL2 path unblocking has failed
cell state is available in the Element
has failedManager. The
1 0C reason
00
BTS O&M
Not of the alarm
specified
data update
meanings
0D Pid update has failed
01 Failure at initialization
of the
0E possibleNBAP
Unknown valuesinterface
and the type corresponding GUI
Possible
02 values: data
Configuration
abbreviations
1101Audit has failed, only 3GPP Iub
= No reply from
03 Deactivation of the BTS cell has failed
are:Cell setup procedure has failed, only 3GPP Iub
12 02Activation
= BTS rejects of thethe configuration
1 04 this
13 fieldbldeletion
0004:
Cell is- reserved
COCO/IPNB
cell
procedure
has failed
for future
failurehasuse. (C)
failed, only 3GPP Iub
0503NBAP-link
= Controller internal
state updating error failure
140008:
Common bl - WBTS (WBTS has
measurement sent disabled
initiation state
has failed, only
11 Failure in cell setup, 3GPP Iub
information)
3GPP Iub (B)
2 12 computer
Failureunit where
in cell this alarm is generated
reconfiguration, 3GPP Iub from
150020:
RRIblmeasurement
- system failure (S) has failed, only 3GPP
initiation
Iub
1 index0040:of
name bl the- initreason
(also during
why the resets)
failure (I)was observed.
3 scenario of thethatalarming
was being unitcarried out when the failure
16 0080:
Cell bl - C-NBAP-link
reconfiguration
Possible values: failure
procedure (L) has failed, only
occurred
3GPP 0100: bl - Common measurement failure (M)
Iubdetailed
4 more cause in case the BTS rejects the
18 0200:
Common
* SIB_FAIL bl - Blocked or
= SIB by
RRIsending user locally
measurement failure from WBTS failed,
termination (Ub)
configuration
01 WBTS initialization
only* 0400:
3GPP blIub - Blocked because cell does not exist in
02 INCONSIS
Cell unlocking = BTS parameters are not consistent
WBTS
with19 (N)
Cell barring has failed
03theConfiguration
Possible controller
values: data modification
* 0800:
20
04
COCO
INCAPA
00
bl - Blocked
= Error(IPA-RNC)/IPNB
Controller BTSbecause
in=restart
radio does notdisconnect
network
cell
have failure when
has
required
configuration
exiting
failed
capability
from21
for05thePower
COCO (IPA-RNC)/IPNB connect has failed
01Local
= Error cellinresource
transportstate layerchange
Saving Mode (P)
configuration
0602Forced
= Error in NBAP protocol layer
handover
2
1 07 scenario
general
* 03PSIG_FAIL that code
error was being of thecarriedsystem. out when the failure
reset= Parameter
= Miscellaneous
WBTS WCEL-
This
occurred
You field
can check
RACHPreambleSignaturescould have
its meaning one of above
with aupdate states, orofa the
command
08 WBTS capability information
combination
service terminal of them
or WCEL-CellRange in value
controller is not
5 09 possible
Pid values
update sent by the BTS, meaning
as bitwise-OR
00 Notonspecified
extension
compatible MRSupdate
with presentation.
(see Service Terminal Essentials,
depends
0A CCH the
data
01 WBTS
Maintenance initialization
the BTS infailure
1 cause
0B Link
this Cell
02
thatfailure/link
value is given
indicates
unlocking the4thcausesupplementary
cancel that has led information
to recovery
Manual)
field:
0C CCH or from
Supervision the document General Error Messages
actions:
2 general
03 error
Configuration code of
data the system.
modification
of
2 System,
0Dgeneral
Audit error handling, message 3GPP ofIubthe system. You can check
its 04
0E
00
Controller
Supplementary
meaning
00 Iu=
CommonUnknown
service
restart
References
cell
barring
measurements ID (RNW areconfiguration)
missing Error
and common
You
05with can
Local
a check
cell
command its of
resourcemeaning
the state from
service change General
terminal extension
0F 01
measurement =
BTS CellO&M not available
data
recovery update (RNW configuration)
Messages
2
MRS 06 Forced
communication
or of
in Node System.
thehave handover control port id Iub
81 06 =
WBTS
actions B resources
initialization,
failed. unavailable
3GPP (RNW
07 WBTS
General
configuration) reset
Error initiation
Messages from
of controller
System
82 Cell
01 WBTS
Common unlocking, 3GPP
measurement Iub initialization constantly
08 capability information update
8309Cell
fails. = Requested
reconfiguration, configuration
3GPP Iub not supported (RNW
09 Pid
configuration) update
84
02 controller channel restart, 3GPP Iubconstantly fails.
0A Common
Connection configuration creation management
8D
04 WBTS restart, 3GPP Iub
0B03Poor
Audit handover
= Message handling, related
3GPP
Not Compatible
radio link setup ratio.
Iub
8E
05 WBTS cell block, 3GPP Iub With Receiver State
0C Poor
(Protocol) CCH FACH Supervision RRC connection setup/complete ratio.
8F
06 WBTS cell unblock, 3GPP Iub
0D Constant
WBTS recovery radio link failure acknowledged by NodeB.
90
08 Resource status indication handling, 3GPP Iub
0E00Base
Iu= serviceStation
Control
resource
barring
processing
manager
overload
process
(Misc)
family
91
(BRM) Common
handdeletion, measurement
crash 3GPP Iub supervision
0F03Cell = Not enough user plane processing resources
FF inNot specified
controller.
1 indicates the BTS model in the WCDMA. The meanings
of the possible
values and the corresponding GUI abbreviations are:
00 - Not used
01 - Other
1 reason of the alarm
02 - UltraSite BTS
03 - FlexiBTS
Possible values:
04 - PicoBTS
01 = No reply from BTS
05 - Wimax
02 = BTS rejects the configuration
1 09 IPv4 address of the remote end. This field is filled with
- NB/RSxxx
03 = Controller internal error
zeroes
17 - FlexiLiteBTS
if IPv6 addressing is in use.
2 computer unit where this alarm is generated from
2 indicates the used communication mode for NodeB via
2
the IPv6
NBAP address of the remote end. This field is filled with
1
3 this
index value
of the indicates
alarming the unittype of failure that prevented
zeroes
interface. The meanings of the possible values and the
the
if IPv4 addressing
corresponding is in use.
GUIPossible
abbreviations are:
4 recovery action.
this info field is applicablevalues if the 1st are:supplementary
00 - UltraSite BTS, FlexiBTS, PicoBTS
information
0100- NB/RSxxx
Daily amount of BTS restarts as recovery action
field
1 reason value
whyisall01 the WCELs became unavailable at once.
has been
The possible
5reasons
moreused up. cause in case the BTS rejects the
detailed
are:
01 BTS restart failed due to missing BTS O&M
configuration
00 = C-NBAP link break
connection.
01 = BRM hand crash
02 BTS restart failed due to no response from BTS.
Possible
02 = Linkvalues:switch failure during rebalancing operation
0300BTS restart
= Error rejected
in radio network by BTS due to ongoing BTS
configuration
SW upgrade.
01 = Error in transport layer
0402BTS restart
= Error failed protocol
in NBAP becauselayer of invalid BTS O&M
message.03 = Miscellaneous
1 possible error code values are:
05 BTS restart failed due to non-supported field value
in The
* 746d value= in DC this field isNOT
HSDPA applicable
AVAILABLE if the 8th
BTSlocal
supplementary O&MCell message.
in the BTS is not Multi Cell Capable,
06 BTS restart
information
whereas field failed
value due is 02toorunknown
03 object type in
1
BTS error
O&M code, possible values are:
the Controller has the DC HSDPA feature
6
enabled message.
possible values sent by the BTS, value meaning
in the
-07
1315d BTS = restart
High Speed Cell FACH is enabled in the
depends cellthe failed due to controller internal errors.
on
controller
08
cause Totalbutamount
that is givenofinBTS the 4th restarts as recoveryinformation
supplementary action
has
field: been Disabled or not supported in the BTS.
1 *this is compared
1352d supplementary
= ADMINPICSTATE SET infoBY field meaning that
OPERATOR IS
test used up. WITH PIC
alarms
MISMATCHING
-09
1316d BTS = restart
Synchronization
failed due between
to missing theNBAP-C
BTS and
for00same= STATE
Unknown
objectRECEIVED
cancellbe ID (RNW
identified
FROM configuration)
byNODE-B
setting different
controller
connection.
01 = is
Cell not available (RNW configuration)
values intoPICState at BTS and AdminPICState set by
lost for HS FACH channels and those are
this06field.
Controller = Node
are B resources unavailable (RNW
unavailable.
2 this value
configuration) indicates the cause that has led to recovery
inconsistent
actions:
2 the one byte size ofconfiguration
09 = Requested field which isnot supported
output (RNW
in decimal
- 1914d = High Speed Cell FACH UL is enabled in the
configuration)
format.
* 2139d = Local Cell is not Dual Band Capable
controller
00
The Common
fieldlocal
value measurements
is in
Cell notthe BTS isare
significant. notmissing
Dual Band and Capable
common
measurement
03 but
= disabled
Message recoveryNotor not supported
Compatible in the
With BTS. State
Receiver
whereas
3 theactions
(protocol) twothe bytehave sizefailed.
Controllerof field
haswhichthe Dual is output in decimal
band HSDPA feature
-01
3099d Common= Highmeasurement
Speed Cell FACH Enhanced
initialization is enabled
constantly
format.
enabled
and
fails. configured
00field
= in
Control processing overload (Misc)
The value
the cell is not significant.
in
0203Common the enough
= Not controller
channel userbut not supported
creation
plane constantly
processing in fails.
the BTS.
resources
04
(Misc)
4 *the2645dPoor
four bytehandover
= DCsize HSUPA related
of field NOT radio
which link setup ratio.
is output in decimal
AVAILABLE
-05
Besides
04Poor these
FACH above specific error code, there can be
format. = local CellRRC
Unspecified in the connection
(Misc)BTS is notsetup/complete
Multi Cell E-DCH ratio.
other
06 error
Constant radio link failure acknowledged by NodeB.
The field value is not significant.
Capable,
codeBase
08
The corresponding
value Station
in this the to
resource
field is failuresmanager
applicable identified
processduring High
family
whereas Controller has ifthe theDC8th HSUPA
Speed
(BRM) FACH/
hand
supplementary crash
5 the one
feature byte size of field which is output in hexadecimal
enabled
HSinRACHcontroller.
information channel
field creation. For instance, insufficient
format. in the cellvalue is 02 or 03
DSP 09 resources.
Poor handover related HS radio link setup ratio.
The field value is not significant.
0A
In Poor
case HS-FACH
value not listed
* 2646d = MC_HSDPA_MISMATCH_EC RRC above connection
is received setup/complete
from BTS, it
ratio.
shall be
6 the twolocal byteCell sizeinofthe fieldBTS which is notis output in hexadecimal
Multi Cell HSDPA
considered as "unknown".
format.
Capable,
Instructions
The operation depends on the type of alarm that is used as

external alarm number 1.























Verify the configuration of a BTS by checking the

commissioning, cabling and correct installation of the
units/modules at the BTS. Make sure the environment does
not cause the fault.
Before a unit/module is replaced at the BTS, the site
Verify the configuration of a BTS by checking the
should be reset to recover from any temporary faults which
commissioning, cabling and correct installation of the
might have caused the malfunctioning of the unit/module.
units/modules at the BTS. Make sure the environment does
When an active alarm is a 'Start' alarm, a site reset is
not cause the fault.
required to cancel the alarm. If the site reset or module
Before a unit/module is replaced at the BTS, the site
Verify the configuration
block/unblock does not help, of a BTS replace by checking
the faultythe unit/module
should be reset to recover from any temporary faults which
commissioning,
(see the source cabling of the alarm and correct
and instructions installation of the
fields of the
might have caused the malfunctioning of the unit/module.
units/modules
corresponding at the BTS. Make sure the environment does
alarms).
When an active alarm is a 'Start' alarm, a site reset is
not
Below cause is the thelist fault.
of BTS fault(s) which might have caused
required to cancel the alarm. If the site reset or module
this alarm in
Verify the configuration WBTS16 release.
of a BTS In by case of earlier SW
checking
block/unblock does not help, replace the faultythe unit/module
Before
release aandunit/module
in case is replaced
you need more at the BTS, fault
detailed the site
commissioning, cabling and
(see the source of the alarm and instructions fields correct installation of the of the
should
descriptions be reset refer toto recover from anyand temporary faultsSystem
which
units/modules
corresponding at the WCDMA
alarms). BTS. Make RAN sure the Flexi Direct
environment does
might
Libraries.have The caused BTS the malfunctioning
fault descriptions areof also
the unit/module.
included in
not cause
Below is the thelist fault.
of BTS fault(s) which might have caused
When
BTS SW an release
active alarm is a 'Start' alarm,
documentation. If that does a site not reset is
help,
this
Verifyalarmthe in WBTS16 release. In case of earlier SW
required
contact toconfiguration
cancel the alarm.of a support.
BTSIf thebysite checking
reset orthe module
Before
release ayour
and in
local customer
unit/module case is replaced
you need more at the BTS, fault
detailed the site
commissioning,
block/unblock does cabling and correct
not help, replaceinstallation of the
the faulty unit/module
should
descriptions be reset refer toto recover
WCDMA from RAN anyand temporary
Flexi faultsSystem
Direct which
units/modules
(see source of at thethe alarmBTS.and Make sure the
instructions environment
fields of the does
might
Libraries.have The caused BTS the malfunctioning
fault descriptions areof also
the unit/module.
included in
not cause
corresponding
FAULT NAME the fault. alarms).
WhenSW
BTS an active:alarm
release
Antenna is alink
documentation. 'Start'is down alarm,
If that does a site not reset is
help,
FAULT
Verify
required theIDtoconfiguration
: 476: the
cancel EFaultId_Rp3BusError
of a support.
alarm. BTSIf thebysite checking
reset orthe module
contact
Before your
arelated local customer
unit/module is replaced at linkthe BTS, thethe site prefix shown
Alarms
MEANING
commissioning, : to
The RF
cabling resources
Antenna (RP3)
and correct may haveis "shared:x"
down:
installation of thetransmitter or receiver
block/unblock does not help, replace the faulty unit/module
should
before bedrops
the reset
fault to recover
text.
out of It providesfrom additional
synchronization. any temporary faults which
information
units/modules
(see the sourceatofthe theBTS. alarm Makeand sure the environment
instructions fields of the does
might
on haveradio
acause
given
INSTRUCTIONS: caused the malfunctioning
resource's
Note! Performsharing themode of the
steps unit/module.
towards
below inthe
theNetwork
listed order until
not
corresponding
FAULT NAME the fault. alarms).
:alarm
10b8biscoding error in Optical Interface
When
Management
the an active System. a 'Start' alarm, a site reset is device <opt link/
Before a RP3> unit/module is replaced at the BTS, the site
See
required
The the BTS
possible to cancel faults
values documents
the ofalarm.
the from in WCDMA
If the
"shared" site reset RAN
or moduleandas Flexi Direct System
should
Alarms
FAULT be fault
reset
related
ID
disappears:
totoRF
:details
2004: recover
resources
EFaultId_OIC_LVDSRecAl any information
may temporary
have "shared:x"
are
faults follows:
which
prefix shown
Libraries
block/unblock
N - Sharing for resources
does about not are BTS
help, not in license
replace use. themanagement.
Defaultfaultyvalue unit/module
when RF
might have
before
MEANING the faultcaused
: The the
text.fiber malfunctioning
It provides
cableand isadditional
experiencing of the unit/module.
information
interference; data
(see the source
sharing is disabled of thefor alarm instructions fields
whenof the is
When
on anFlexi
a given active
radio
transmission
BTS: alarm
resource's is aparticular
is faulty.
'Start'
sharing alarm,RAT.aUsed
mode site towardsreset isalarm
the Network
not
corresponding
related to RF alarms).
sharing (e.g. related to faults from BB resources).
required to cancel
Management System. the alarm. If the site reset or module
FAULT
D - BTS NAME
has
1. If shared
the : Feature resources
alarming expiry
module in onuse is<expDate>,
butExtension
the alarm <featName>
relates
System to Direct
Module
See
The the BTS
block/unblock
possible A faults
does
values
physical documents
not
of thehelp,
connection "shared" in
replace WCDMA
failure the
information
between RANunit/module
faulty and
are
the asFlexi
opticalfollows:
interfaceSystem
FAULT
Alarms
dedicated ID
related
(FSM2), :RF4002:
to RF EFaultId_LicenceExpired
resources
restartresources
it. only.
If the may
alarming have "shared:x"
module is prefix
the Systemshown
Libraries
(see
N - Sharing for resources
the source
and details
the about
ofsumming
the alarm
are BTS
not and
functionin licence
instructions
use. has management.
Default fields
value
occured(possibly of
whenthe caused
RF by bad
MEANING
before
S - BTSthe has fault : The
shared text.feature:
It provides
resources inadditional
useBTS. and alarminformation comes from slave RAT.
sharingModule(FSM1),
corresponding is
circuit
- expires
alarms).
disabled
joints).
in one for restart
particular
Month
the
oruse RAT.
one WeekUsed when
if the alarm
faultNetwork is
severity not
on
M -aBTS given radio resource's sharing mode towards the
Below
related is has
the
to RF
shared
list of BTS
sharing
resources
fault(s)
(e.g. related
in
which and
may
to faults
alarm
have from
comes
caused from master RAT
BB resources).
Management
For alarms 2.isIf minor;
System.
related
that to
does RF not sharing,
help, see
replace RF theSharing
alarming Operability
FSM. document.
FAULT
this alarm
D - BTS NAME
has in WBTS16 : Failure in license
release. In use activation
case of alarm
earlier SW to
The possible - hasshared
INSTRUCTIONS already
values
resources
of expired
the "shared"ifinthe but
fault
informationseverityrelates is major.
are as follows:
FAULT
release
dedicated ID
and
1. Reset:RF
in 4037:
case EFaultId_FailureInLicenceActivationAl
you
resources
the RF need only.
Module more with detailed
the faultoptical interface by
N - Sharingis Note:
theresources The feature
are name
not inwhich might
use. befaulty
shown aswhentruncated in RNC
Below
MEANING
descriptions
S - BTS has
list
refer
shared
oftoBTS
: Generation
blocking/unblocking WCDMA fault(s)
resources of target
RANin
it. use IdDefault
and might
has
and Flexialarm
value
have
failed
Direct caused
and
comes as from
System a RF
result,
slavethe
RAT.
thissharing
alarm OMSis
in and NetAct
disabled
WBTS16 for
release.alarmInuser
particular caseRAT. interfaces.
of Used
earlier whenSW alarm
release is not
Libraries.
M - BTS correct
Theshared
has BTS validation
fault
resources of license
descriptions in use files
are
and inalarm
also the BTS
included
comes is innotfrom master RAT
INSTRUCTIONS:
and related
in case to youRF sharing Activate
need more(e.g.the required
related license.
toand,
faults from BB refer resources).
BTS SW
For alarms possible.
release
2. related
If this BTSOM
documentation.
doesto RF not isdetailed
sharing,
clear restarted Ifsee
the
fault
that RF
fault, doesdescriptions
consequently
not help,
Sharing
replace Operability
the RF during
Module document.
D -WCDMA
to
FAULT BTS has RANshared and resources
Flexi Direct in use
System but alarm
Libraries. relates
fromThe thetoBTSBTS.fault
contact NAME startup,
your that local : Autonomous
all the
customer
isresources
causing license
the
recovery
support. files
alarm. are reset
deleted
dedicated
descriptions
FAULT ID :RF
are
1894: also included only. in
EFaultId_RecoveryResetAl BTS SW release
Below is Ifthe thelisttrial period
of BTS has expired,
fault(s) which might all optional
have caused features are
S - BTS has shared
documentation.
MEANING If that
: During resources
does
BTS notinhelp,
startup, use the and
contact
Systemalarm your comes
local
Module fromdetected
has slave RAT.a
this alarmeither3. inIf WBTS16
the disabled
System orModule
release.their Incapacity
case
is the of isearlier
only reduced
source SWof to the
the alarm, or RAT
M - BTS
customer
new RF has
support.
basic shared
(not resources
licensed) level. in use and alarm comes from master
FAULT
release NAME
andreplacing
in case : <parameterName>
you RF need more out
detailed of range
fault
FAULT
For alarms
INSTRUCTIONS:
NAME
HW related
type tothe
: License
that
Note! RF was
Module
missing
sharing,
not
Perform previously
the
does RF not
<licenseName>
see steps used
below
clearOperability
Sharing the fault, document.
inSystem
this
in theBTS listed order until
FAULT
descriptions ID :refer
replace4235: WCDMA
the EFaultId_VswrThresholdOutOfRangeAl
System RAN Moduleand Flexi
that Direct
is causing the Libraries.
alarm.
FAULT ID : 1885: EFaultId_MissingLicenseAl
configuration. A System Module reset is triggered to
the
MEANING
The BTS fault: descriptions VSWR majorare or alsoVSWR minor value
included in BTSset SW during
This alarm is an encapsulation alarm for original FTM alarm.
Follow up the instructions given in the BTS faults
documents in WCDMA RAN and Flexi Direct System Libraries for the
alarm number shown in supplementary information field 3.
Correct the fault that caused the original beating alarm. You can
find the number of that alarm in Supplementary information field 1.
FAULT NAME : $Protocol Timing source lost [on unit $U] [, interface $IF]
FAULT ID : 61059: FTM_TIMING_SOURCE_LOS
MEANING : One of the synchronisation sources in the configured
Error reason (field
priority list1)is indicates which part of the connection the
unavailable.
problem is located.
This can be the primary or the secondary clock source.
Error code In (field

the alarm: 2) indicates what caused the problem if the error
reason (field Protocol 1) value can is be1.fivePDH, SDH, Timing
This instruction contains main steps. Theover first Packet
four steps (ToP) areand
Synchronuous ethernet.
specific to certain failure situations. The last step is a general
Error reason = 1, failure in the WBTS connection
operating procedure for all other failures indicated by this alarm.
It is also Unit a default Number procedure is optional: to be performed if instructions given
Error code: -For PDH, SDH and Synchronous
in previous steps do not solve the problem. Ethernet, Unit number is 0
IPA-RNC:
14005 = or CONNECTION
1. RESET BY PEER
Abbreviation SIF refers to supplementary information field.
AtWBTS first, check has
-It is not thepresent
closed functionality
the connection.
for Timing of Radio OverNetwork Packet(TOP). database with
the Waitfollowinguntil WBTS MML-commands: opens a new connection and the system cancels
Step 1:
ZDBS:RAQUEL,0;
the alarm. Ifinterface the connection is does not recover in a few minutes,
In caseThe the value of SIF value optional:
2 (scenario) is 07 (WBTS reset):
Statecheck of -that
database the WBTS should is be normalconfigured
correctly and memory (and disk) updates
First task: verify
- First, For
wait for PDH using the
5 minutes. value range
ElementTypically, Managertheredepends that WBTS is to
on the
stillthe controller
hardware
id is valid unit
some
not and prevented.
to the
type: If updates are prevented, you can resume them with
network.
1..16
recovery in theoperation system and ongoing.COCOThe alarm gets
(IPA-RNC) cancelled iftothe
is connected WBTS.
command ZDBR:RAQUEL,0:<mem
-isFor Synchonuous orthe disk>;
recovery- Check successful.
also if alarm 7750Ethernet FAILURE INvalue WCDMA rangeBTS = 1..3 O&M
If database - Forstate SDHisthe "waiting
valuefor is 1dumping" or "dumping", database
CONNECTION
should
Error return
codes:
- It isfor to normal
not present state automatically
forIfTiming overindicating after dumping is ready.
Packet.
If the isautomatic
active recovery
this WBTS. does itnot correct
is active the situation, that follow information
Check
Also 13960
INSTRUCTIONS: first
status = the
of
BAD nature
the FILE disk
Use BTS of the
updating
DESCRIPTOR problem.
Site system
Manager The can 7th
to besupplementary
check checkedwhich with interfaces have
thesethere steps: is something wrong with WBTS O&M connection (Iub), then
field
been 13964value=indicates
MML-command PERMISSION ZDBD:OMU;the phase DENIED in which
Line "RAQUEL" the problem specifies hasthe occurred:
state of Radio
1. If the blocking reason
reset command cannot be sent from RNC to WBTS. in the supplementary information field
Network
13965 =database.
BAD ADDRESS(EFAULT)
01:
1->(WCELIf configured
Initial WBTSHSDPA
state) O&M asconnection
containssynchronization
configuration
0008is(BL(B)) OK,sources.
retry or 0200
to reset (BL(Ub)),
WBTS check with the
13986
WBTS = RESOURCE
alarm TEMPORARILY
that is related to this WCEL, UNAVAILABLE
and follow the
Element Manager.
If
Todatabase
13989 =the state
SOCKET is workingOPERATION (or becomes ON working
as NON-SOCKET after a while), do as
correct
The If For
operating
-> problem WBTS the PDH
problem,
instructions
O&M
has
interfaces,
ensure
there.that
connection
occurred during
do the
between follows:
correct
initial HSDPA RNCcertificates
and WBTS
setup
arenot
to aiscell.
installed
OK,
The try
follows:
in the13991 = MESSAGE
controller as well TOO
as in LONG
the network element which is trying to
effect to solve
of this the
is situation
that HSDPA with BTS
cannot Manager
be used by
in to examining
the cell. the
Try
establishto lock
14006 =
1.thethe
NO
Check cell
BUFFER
secure and
that O&M then
the SPACE unlock
cables
connection. it with
AVAILABLE
are connected Element Manager.
the correct
2. If theWBTS blockingalarms reason
and in
logs. the supplementary information
If this
14008 does = not clear the
SOCKET
connectors. IS alarm,
NOT try WBTS reset.
CONNECTED
field 1 (WCEL state) contains 0400 (BL(N)), an incorrect Local
02:14016 Reconfiguration
= NOcertificates
ROUTE of HSDPA
After
Step
Case Cell theResource
2:
1: If2.
right
the alarm hasTO
idreason are
been HOST
installed
given given in for toatthis
the
thecell.
first
Controller
Such Local
supplementary
end, operator
If database
should14608 =
trigger state
CONNECTION
Check remains
the exist whether
TLSmode abnormal
NOT
theas EXIST
interface
probing long
atcell
which the time far
will or
end
maketheisalarm switched
Controller appearsto close
In Cell
case does
information the not
value field of is in
SIF the
2
INCONSIS:isWBTS.
0A The
(Connection data must
configuration be
The
constantly problem for
controller
on.and, has
severalhas occurred
WBTSs
attempted during
and to HSDPA
cells,
send contact
an O&M reconfiguration
the
message local customerto
toward a cell.
the The
the server
corrected
management), port and and open
after the the
that,
value port
a WBTSof with
the right1 certificates.
reset
SIF is required
0B (AAL2 path unblocking
effect
support.
WBTS, is
Also thatcontroller
but the HSDPA
there is noreset may might
connection nothelp work
to the ifwith the intended
itcontroller
is possible to parameters.
has to failed):
Check remove the theparameters
cell problem. RACHCapacity,
In this
perform
(code case
it.
14608)
3. Check it is recommended
orwhether
some has thereerror that
are HSDPA
occurred
active inSIB7factor,
alarms is
TCP disabled
atlayer
the and
when
far end. enabled
- Check
ShutdownWindow,
in the cell theto configuration
confirm that of the parameters
proper corresponding are WBTS
taken node
into use.using
First the
3. If message
check
the If there
the WCEL
blocking was are, attempted
reason follow
operational
in the
the to be
state sent.
instructions
supplementary using RNW on handlingRNC
information those
Object Browser.
and BTS Manager.
ShutdownStepAmount It should match
in controller.the configuration
If these of the RNC.
More Thisinformation
action alarms. requires aboutcell thelocking.
exact failure reason canparameter
be found values are
-
thefield
Checksame 1 (WCEL
that ATM/IPstate) contains
resources 0004
related (BL(C)),to COCO then COCO/IPNB
(IPA-RNC)no actionsobject are
by
If the examining
Check WCEL
configuration thatas the those
operational related
in the
supplementary
WBTS is
state
to
BTS Site
correctly
WBTS is not infoWO Configuration
field(working),
configured
needs to
4 (error
be to the
corrected.
File,
code).
ignorecontrollerthis alarm and
are
03: not
neededPWSM locked.
inTo controller.
HSPA05 Check
reconfiguration if otherfailure alarms are activeunit for works
the BTS
and
analyze to the
4.
the problem network.
verify that the
with the WCEL hardware of
taking the interface
into account the other active
In orLocked
many
If the WCEL cases
ATM/IP
in
configuration
correctly,question.
there connect
resources
isisalsocorrect, more
aits
prevent
wait
loop information
the connection
untilWBTS
cable the
and incheck
WBTS OMUopens computer
whether a thelog.
alarms
4. In for
case
configuration the there same are WCELno
operations. alarmsor parent
targeted to the object.
WCEL, tryquestion
to
First,
The
IPA-RNC:
new check
problem
connection if there
alarm has are the
occurred
and
disappears. other alarms
during
system active the
HSDPA
cancels for the
reconfiguration
alarm. BTS in to a cell when
and lock
IPA-RNC:
follow
Ifcan
thebe and
cell the then
parameters unlockinthe
instructions givencell for
controller manuallythose withthethe
alarms.
areZDDE::"ZGSC";
not same controller
This alarm
as those Object
is in HSPA05
IfPower
Itthe WCEL
Browser.
- Use
Savingstudied
MML This
Mode
operational withFor
way
command the
BTS
MML-command
state
system
ZLAI is(PWSM)
WO,
to tries
print check
to
feature
ATM clear
has
ininterface
thethe RNC been
possible themaking
information WSP-related
cancelled
the BTSifSite
reconfiguration.
Multi-Controller the problemConfiguration
RNCHSPA05 or is solved
Flexi File by
reconfiguration
Direct and correcting
RNC: these has the other
parameters
been stopped active
need and to be
no cell
active hangingalarms that
cell are targeted
related ZLCItoto
resources theand related WBTS object.
alarms.
updated,
deletion
Logs
Error
and
can or
code:
MML
bethe
activationcommand
following
collected by and actions
PWSM studied can print
feature bethen
from
VP/VC
taken
will
recreate
location be toinformation
the
done.
(init)that
cell
In
"/srv/Log/log/"in
them.
this (ifcase
ATMit
has
The alarms layer to be checked
information are: by the user in controller Element
is given
is
thefailed
recommended
154 product. to
=BASETIME accept LIMIT the
torequireparameters
disable
EXCEEDED PWSM sent: feature. Do cell lock/unlock to
This
If
7650
5.
thereIfalarm
the
Manager).
are
does
alarm
no
STATIONnot
is
obvious not FAULTY
cancelled
faults
any
indicatedbyINthe
actions. MESSAGE
lock/unlock
by active
WAITING
alarms cell and this
recover
FAULT
7651 WBTS NAMEcell
BASE the HSDPA
supervision
:
STATIONAIS parameters
timer
(Administrative has and
expired. state.
Unit) on TheIf cell
unit is
connection
$U, not recovered
interface isWBTSclosed
$IF and
alarm operation,
-* is
Unlock
not
Modify youATM-interface
cancelled
these can tryOPERATION
by
parameters. some of
system, with theMML
follow
This
DEGRADED
following
isO&M thecommand
recommended actions
instructions if(the
ZLAS given
the and
cellin VP/VC
the
using
FAULT
WBTS
7652 the lock/unlock
ID controller
recovery
BASE : 61106: actions
STATION operation,
is waiting
FTM_AIS_AU
are fora
started
NOTIFICATION BTS
a new restart
when othercan be
connection
recovery attempted opening
actions usingfrom not
have
steps is unavailable
with
below
works, MML according
that during
command
is, cell to these
ZLCS
error
state operations).
code
(WCEL if needed.
givenstate) inThese
the
is WO. firstoperations
supplementary
TheElement
MEANING
recovered WBTS.
faulty Manager
the
unit : Alarm
cell.
is or
The
mentioned BTS
indication
reason Site
in Manager.
signal
for WBTS
supplementary on the
recoveryAdministrative
information actions is Unit.
field The SDH
indicated
3 of
first
information clear
- IfLockthisfield. and
alarm thenandrecreate
was generated thedue BTS related
tocell.userThis resources:
initiated action,
in
these the-*reset1st
alarms.
for
the
interface
supplementary
the
example
cell
Check
WBTS receives
COCO all with
then an
WSP-related
the
unlock
information
(IPA-RNC)AU-AIS
Element
the (Administrative
field.
alarms
Manager,
creation, because
try
operation
or
to performUnit
any -
of Alarm
the
The firstcausessupplementarythe parameters to signal
bethe resent to the BTS.
-Wait
WSP-related reform
the
until
Indication the
fault
the
operation
system
Signal).
can
connection
again.beinformation
cancels
the Thisreason
between
field
foralarm.
the
value
isthis
generated
WBTS alarm.indicates
andby
the main
theanCOCO(IPA-RNC)
1.
reasonError code
for the
intermediate problem. SDH device in the forward direction because it
If cell still does
/IPNB by firstnot work orafter
disconnecting the WBTS
thefailure recovery actions have
COCO(IPA-RNC)/IPNB andended
and
Multi-controller
13247
Moreno information
detects
reason a
RNC
no_answer_from_remote_end_ec
behind about
problem it can
Flexi
theinbe its
Direct
exact receive
found,
RNC:
signal.
collect reasonat
Nocan
All
least
response
other be following
the found frombythen
BTS
logs
If a HSDPA-dedicated
reconnecting
-NoThis configuration it (thisWSPC iscannot unit
be in BTS
done
relevent by
for is faulty, the
changing
Multi-controller theBTS used RNCreserves or
01: 15479
examining
Error reply
codes:nbap_bts_hw_res_not_avail_ec
the
transmission from errorWBTS code given in 2nd supplementary BTSare hardware information failure
and
another contact WSPC the
COCO(IPA-RNC)/IPNB
Flexi Direct local
when RNC. italarms
customer
becomes related
id support:
in freethe tofromthis
WBTS signal
otherwith traffic.
the suppressed.
Element Manager),
field.
14001
IPA-RNC:
These or =codes NETWORK IS DOWN
indicate that response from BTS was not received
Problem
14011
For--OMU more = may reside
OPERATION
Probable
computer
information cause:
log on somewhere
TIMED
There
(MML-commands
BTS alarms,isOUT aintransmission
transmission
see ZDDE::"ZGSC";
WCDMA network
problem
BTS Alarm to BTS.for
somewhere
and Check
-Ifblock/unblock
configuration
Dedicated
Probable Measurement
error code the
is BTS
correct
values with
and
Indication
are: the
ATM/IP BTSor BTSelement
resources hardware manager.
are unlocked,
failure. The
if there
14015
ZDDE::"ZGLE";)
Descriptions =
in areHOST
the other IS
intermediate
(SW and active
DOWNrelease alarms
network for
documentation). the
and WBTS
AIS is object
sent and
instead follow
of the
user
act * according
operation
instructions 94 = canNO given be to forthe
retried
RESPONSE general
those byalarms. operating
creating the instructions
corresponding in step NBAP-D 3
If-again
alarm
the
below. traffic.
alarm history is (MML-command
still active after the ZAHP
above oroperations
using Fault haveManagement
been
usingBTS Element notinManager (this operation causes allinthe
There
INSTRUCTIONS:
application
performed, are and inhas
problems Check
controller
no obvious
responded
theEM) transmission
intermediate
reason all
to parameter
behind network
transmission
it can
sending
between
be network
found,
timefor
the or
collect alarms
Ifcells
there of the
areresponseBTS
no being
apparent did unavailable
not include
problems for
shown the traffic):
cells
via the
other parameters
controller
- message
at least the following and
indicating WBTS.
monitoring the root
logs Try
from to
cause
and connect
OMU and
contact to
follow
(families the
the local theBTS 4FA) andsupport: the
using
instructions
50B,customer alarms, BTS check
forSite
First check the WCEL operational state using RNW RNC Object Browser.
If the WCEL operational state is not WO (working), ignore this alarm and
analyze the problem with the WCEL taking into account the other active
alarms for the same WCEL or its parent WBTS object.
The WBTS deletion and recreation are required when correcting the
incorrect configuration. The WBTS recreation is needed because the
If the WCEL operational state is WO, check in the RNC the WSP-related
Iub Working Mode is a non-modifiable parameter that must be
active alarms that are targeted to the related WBTS object.
given in the WBTS object creation phase.
The alarms to be checked are:
Step
76501: BASE STATION FAULTY
Step 1:
7651 BASE STATION OPERATION DEGRADED
Check
7652 BASE first the nature ofNOTIFICATION
STATION the problem. The 8th supplementary
Check, using the Topology Browser, if there are WCELs under
information
The faulty unit field value indicates
is mentioned the phase in information
in supplementary which the problem field 3
this WBTS. If so, lock all these WCEL objects and delete them.
ofhas
these occurred:
alarms. Check all WSP-related alarms because any of the
See the NBAP link operational states for the WCDMA BTS from Topology
WSP-related
Browser faults can be the reason for this alarm.
Step 2: in controller OMS to see which of the configured D-NBAP links
01: Delivering HSUPA parameters to BTS
are unavailable.
If02: Initial HSUPA configuration
a HSUPA-dedicated WSPC unit in the BTS is faulty, the BTS
Delete the WBTS object.
reserves another
In case this alarm is set right WSPC whenafter it becomes
the WBTS freeis fromenabled otherintraffic.
the system,
Check
The the problem reason hasforoccurredthe recovery duringfailure initialfrom HSUPA the 1st setup supplementary
to a cell. The
verify
Step using Topology Browser that the IPNB object configuration
3:
information
For effect
moreofinformation fieldisand
this thatproceedHSUPA accordingly.
cannot see be used in theBTS cell. Proceed
in controller is correct on BTS alarms,
in relation to the network WCDMA setup. Alarm
to the step(SW
Descriptions 2 in this and instruction.
release documentation).
Recreate
00: The amount the WBTS of performed object with BTSthe correctasIub
restarts Working
recovery Modeper day
action
Otherwise,
parameter the
value. problem Next, isrecreate
likely tothe be WCELlocatedobjects either inunder the BTS or in IP
exceeds
03: Reconfigurationthe limit which is given in the 4th alarm supplementary
of information
HSUPA
The 1st
transmission
this WBTS. supplementary
between the BTS and field indicates the
the controller. Seereason why
other possible
information field. In this case, the BTS cannot be restarted by
the
active whole WBTS became
BTS-originated alarms unavailable.
(7650, 7651) The that fieldcan contains
indicate thethe
the controller untiloccurred
next midnight duringwhen the reconfiguration
controller resetstothe BTSThe
firstThe
reason
problemreason
observed has
for the failure. for the problem. This means that during
HSUPA a cell.
specific
effect is restart
that the amount
HSUPA counters.
may not The
work BTSwith can
the be recovered
intended parameters.
recovery
Use BTS actions
Site Manager the whole to see WBTS can become
the operation status unavailable,
in the BTS butend thefor
manually
In thiscan case byitrestarting
is recommended it using eitherHSUPA Element Manager or
reason
additional change.
troubleshooting. For example,that it is possibleisthat disabled
the BRM andhand enabled crash
NoBTS
inactions
theSite cellare to needed
Manager.confirm in the
Increasing
that propercontroller.
the Use the
allowed
parameters BTS BTS
are restart
taken Siteinto Manager
amount in to see
causes the original problem, but after its recovery the C-NBAPuse. link
thePRFILEoperation enablesstatus in cell
the BTS
controller to endperform for an additional
additional troubleshooting.
restarts for
canThis be action
unavailable. requires The locking.
original alarm is kept active, as from the
BTS sites that have no recovery attempts left.
system point of view the whole WBTS is still unavailable.
04: PWSM HSPA05 reconfiguration failure
01: BTS
TheanalyzesituationO&Mcausing connection between BTS notand controller is not available
To and correctthis thealarm problem, does check obstruct
the 1st networksupplementary operations,
and and
The restart could
problem
therefore has
no not be performed.
occurred
immediate during
actions HSUPA
are See ifreconfiguration
required. controller
However, alarm to
you7750 caniswhen
a cell take
information field value.
active
Power for
Saving possibleMode details
For BTS on
the following actions to ensure consistency in configuration parameters. the
(PWSM) fault concerning
feature was the BTS
performing O&M HSPA05
connection. Check
reconfiguration. HSPA05 also the status of BTS O&M connection from
00: C-NBAP link break reconfiguration has been stopped and no cell
BTS
deletion
In case Site or
of can Manager.
DC beactivation
HSDPA See
by
relatedPWSMinstructions
problem,feature below
is done.
check for
firstpossible
Inthatthisthe caseneed
cellitpairto of
Case This
1) The caused
first supplementary by different informationunderlying field reasons
value isthat
1315d to
isperform
the cellrecommended manual
indicated recovery
to disable actions
PWSM depending
feature. Do oncellthe 2nd
lock/unlock
are indicatedinas
(enh_fach_capb_mismatch_ec).
thisthealarm C-NBAP is notlink lockedbreakbytouser RNW before
O&M:proceeding
supplementary
torecover
the- steps cellgiven HSUPA information
below. parametersIf that field is andvalue.
the state. then
case, If cell theisBTSnot recovered
eventual
a transmission break between controller and resulting from,
using
unlocking lock/unlock
for of the DCaHSDPA
example, operation,
cable or a
cell BTSpair will
external restart can be
clear this alarm.
transmission attempted
equipment using
02: Possible
ElementBTS does reasons:
Manager not respond or BTS to
Site theManager.
reset request. This may be due to high
failure, a BTS restart performed using BTS Site Manager,
1. load
No Find in BTS
operation
orthe a is cells
controller
side.
thatCheck
instruction. might have
network
the BTS
interface
status using
inconsistency unitchannel
failure.in BTS Site Manager and
configuration
Step-restart
There
2: the aBTSmismatch manually of the if HS-DSCH
possible. configuration between
parameters
- an internal by checking
controller the alarms
failure, for in the RNC.
example For these cells,
a spontaneous ICSU
See the controller
instructions and belowBTS. for possible need to perform manual recovery
proceed (IPA-RNC)/to step 2. Control plane unit (Multi-controller RNC/Flexi
The-actions
BTS first HW does noton
depending
supplementary support
the 2nd
information HSsupplementary
FACH fieldcommonindicates channels
information
the mainfield reason value.
- BTS Direct
runsRNC) out ofrestart. capability due to, for example, a HW failure.
for the problem.
2. a) If the 2nd supplementary information field value is "DCHSDPA":
03: BTS Check software
theofcell upgrade
parameter is ongoing
WCEL - and BTS cannot be restarted
DCellHSDPAEnabled at the
In case
Actions toBTS be the
taken: C-NBAP link failure the recommendation in is the
to RNC
01: moment.
No reply from restarts
WBTS after
usingwait for a couple of minutes and check if the disturbance the software upgrade has been completed.
the OMStemporary.
isCheck
only EM. The
1)05,
04,Problem 06: mayif therereside any system
aresomewhere BTS end recovers
inthe failuresautomatically
transmission that are networkindicated to withCheck
The
once Cell
76xx are the
alarms
has inconsistency
transmission
and that between
could affect
in the Dual
this
Cell HSDPA
controller
feature and
(for and BTS
example is BTS.
configuration
some
Unexpected
if parameters
there error
other has
active occurred
alarms in
for
if the Dual Cell HSDPA feature is enabled in the Cell BTS
the O&M
WBTS message
object handling.
follow The
the
available
HWmight again.
unit givenfailure).
reason
instructions
but be that
for controller
those alarms. and BTS do not use compatible
In thecaseHW of amapped longer WBTS for the unavailability,
Cell in the BTSit is can notbesupporting Dual
version
Cell of the BTS
HSDPA, O&M
or controller
if the interface.configuration
frequency Collect OMUiscomputer not properly log
2) checked
Check if
if no the
theapparent
relevant BTS fromhas active
is in the alarms
working for (IPA-RNC)/
state using the
from
Ifdone.
there controller
are
If so, and
do the also logs
problems shown BTS viain question.
other alarms, Fill in the the
check
Control
controller planeElement unitfollowing:
(Multi-controller
Manager. so, RNC/Flexi
If following check whether Direct theRNC)BTS or HW
problem
type of
- network
Check from report
network and
problem
BTS side send it
with to the local customer support.
instructions:
configuration interface isbelow unitsthat
correct that
so
the
thatcanHW cause
Enhanced
mapped theHSFACHto the Cell
C-NBAP linkresource
can berecovery
is
See instructions
capable of providing for
Dual Cellpossible need
HSDPA. to perform manual
unavailability.
supported. The relation between WBTS and (IPA-RNC)/
actions
- Precondition
Check depending
from RNCfor on
Physical
side thethat 2nd Shared
thesupplementary
WCEL Channel UARFCN field configuration
value information.
Reconfiguration
Control
If the working plane unit
state (Multi-controller
ofC-NBAP
the BTS link andto RNC/Flexi
the BTS is HW Direct RNC) unitis done
configuration
procedure
according
can be seen is that
to instructions
from the
WBTS given
data in RAN1906
using WBTS
the Element active.
feature Check
activation
Manager the
(the
are correct
07: Controller
state of C-NBAP while errors
internal this
link fault
of might
this stillWBTSoccurs,
be that object contact
reading from the local
BTS-related
Element
manual.
controller GUI for BTS Connection Resources dialog).
customerfrom
information support. database failed or there areworks,
already thesome
01:- Manager
IfBRM
configuration
hand main crash dialog.
parameters If the C-NBAP
have link
inconsistency then lock other
problem the
recovery
may
cell, actions
reside
correct WCEL in going
the BTS. on
UARFCN for
Check the BTS.
the BTS See if alarms
configuration
as well as and 7761 orlogs7762using
The system recovers from theconfiguration situation automatically. other
have BTS been
parameters Manager. set for
mentionedthe WBTS in question.
innon-performing
RAN1906 feature
Case This reason
2)instructions
When themay first trigger
supplementary information cellactivation
recovery
fieldmanualvalue isrecovery1316d
See manual. below for possible need to perform
actions
(hs_cch_sync_ec): in controller, meaning that the BTS gets restarted by
actions
If
- the the
Unlock depending
C-NBAP on
link the
does 2nd
the cell if were locked in previous step. not supplementary
work, check the information
success of field
PING value.
controller.
between controller and
02: Link switch failure during rebalancing operation BTS. Successful PING tells that the BTS is
Related Faults Clearing
Do not cancel the alarm. The system cancels the alarm

automatically
when the fault has been corrected.

automatically

automatically

automatically

automatically

automatically

automatically

automatically

automatically

automatically
automatically

automatically

automatically

automatically

automatically

automatically

automatically

automatically

automatically

automatically

automatically

automatically
automatically

automatically

automatically

automatically

automatically

automatically

automatically when
the fault has been corrected.

automatically when

automatically when

automatically when

automatically

automatically
automatically when

automatically
Do not cancel the alarm with error reason 1. The system

cancels
the alarm automatically when the fault has been corrected.
The alarm with error reason 2 must be cancelled manually.
Error reason = 1
automatically
The alarm is cancelled when BTS O&M connection is
working again.
Do notreason
Error cancel=the
2 alarm. The system cancels the alarm
automatically
The larm must be cancelled manually with MML
when
command the fault
AANhas been corrected.
or with
Fault Management application in RNC Element Manager
after
the conflicting WBTS id situation is corrected.
automatically
when the fault has been corrected. The alarm is cancelled
Error reason = 3
by system
The alarm
if the cell is cancelled
in question startswhen the again
to work RNC has
or it identified
is locked the
by
Do
BTS not
as cancel
a WBTS the alarm. The system cancels the alarm
user.
automatically
in the Audit procedure for situation 1.
whenThethe faultishas
alarm been corrected.
cancelled when the incorrectly-configured
BTS O&M
Locking or deleting of the cell, or next succeeded
Doconnection
not cancel is theclosed
alarm.forThe
situation
system2.cancels the alarm
configuration
For situation of 2,
HSDPA
in case another 7750 alarm with reason 1
automatically
channels
has been cancels the alarm.
raised for the same WBTS after correcting the BTS
configuration,
Dothenotalarm
cancel mustthe be
alarm. The system
manually cancels the alarm
cancelled.
automatically
after these parameters/SIBs have been sent successfully to
the WBTS.
automatically
when the fault is corrected.

automatically

automatically
automatically when the fault is corrected.

automatically
when the WBTS is deleted, or no mismatch is detected after
the
BTS O&M link establishment.
automatically
Locking or deleting of the cell, or next succeeded

configuration of HSDPA
automatically
channels cancels the alarm.

automatically

automatically

after the BTS has
acknowledged the alarm upload status request and when
the upload can be
started.
after the BTS has
indicated to the RNC that it supports the high peak rate
HSPA feature in
the cell in case of DC HSDPA or Dual band HSDPA or DC
HSUPA or MC HSDPA
automatically
or BTS and RNC has consistent PIC States in case of
HSUPA IC. The
alarm will also be cancelled when the cell is deleted or
The alarm is cancelled when either of the following occurs:
Cancel
locked. the alarm with an MML command.
- The creation of HS FACH/HS RACH common channel in
the cell is
successful.
- The cell is deleted from the Node-B.
- The cell is deleted internally from the controller as a
result of
the audit procedure.
Setting Delay in Time to Live Clearing Delay
Centralized Alarm
System
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
10 0 10
0 0 0
10 0 10
40 0 0
5 0 0
120 0 20
5 0 5
0 0 0
0 0 0
5 0 0
0 0 0
0 0 0
5 0 0
0 0 0
5 0 5
30 0 30
0 0 0
30 0 15
0 0 0
15 0 15
5 0 0
10 0 10
Alarm Output Number
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
5
NONE
NONE
NONE
Note:
See the How to Read This Report tab
for instructions on the usage of Fault List
Changes between issues Changes between releases Fault ID

01A and 01D WCDMA 16 and WBTS16
Changed 1
Changed 2
Changed 6
Changed 9
Changed 10
Changed 12
Changed 13
Changed 15
Changed 16
Changed 17
Changed 18
Changed 19
Changed 23
24
Changed 26
Changed 27
Changed 28
Changed 29
Changed 30
Changed 37
Changed 38
Changed 39
48
Changed 49
Changed 50
Changed 52
Changed 69
Changed Changed 88
Changed 94
Changed 95
Changed 96
Changed Changed 103
Changed 109
Changed 110
Changed 111
Changed 114
Changed 115
Changed 116
Changed 124
Changed Changed 125
Changed 128
Changed 129
130
Changed Changed 133
Changed Changed 134

Changed 139
New New 144
Changed Changed 145
Changed 146
Changed 149
Changed 150
Changed Changed 154
Changed Changed 157
Changed Changed 158
Changed Changed 160
Changed Changed 162
Changed Changed 163

Changed New 164
New New 166
Changed 214
Changed 215
Changed 216
Changed 217
Changed 218
Changed 300
304
Changed 418
Changed 420
Changed 476
Changed 1400
Changed 1401
Changed 1402
Changed 1403
Changed 1404
Changed 1405
Changed 1406
Changed 1407
Changed 1408
Changed 1409
Changed 1410
Changed 1411
Changed 1412
Changed 1413
Changed 1414
Changed 1415
Changed 1416
Changed 1417
Changed 1418
Changed 1419
Changed 1420
Changed 1421
Changed 1422
Changed 1423
Changed 1424
Changed 1425
1802
New New 1803
Changed 1806
Changed 1807
Changed 1811
1816
Changed 1817
Changed 1818
1820
Changed 1822
1825
1826
Changed 1827
Changed 1829
Changed 1836
Changed 1841
Changed 1850
1852
1856
1857
1858
1859
1860
1861
New 1866
New 1867

Changed 1882
Changed 1888
1892
Changed 1893
1894
Changed 1898
Changed 1899


Changed 1921
Changed 1922
Changed 1929
Changed 1931
1941
Changed 1955
1956
1958
Changed 2000
Changed 2001
Changed 2002
Changed 2004
Changed 2005
Changed 2006
Changed 2007
Changed 2008
Changed 2009
Changed 2010
2011
2013
2048
2049
2052
Changed 2054
2056
2057
Changed 2059
2060
2061
2073
2074
2078
2080
2326
Changed 3020
Changed 3030
Changed 3040
Changed 3060
Changed 3070
Changed 3080
3100
3511
4000
Changed 4001
Changed 4002
Changed 4003
4004
Changed 4011
4022
4023
4025
Changed 4029
Changed 4030
Changed 4036
4037
Changed 4038
4039
Changed 4040
4041
Changed 4043
Changed 4052
4053
4056
Changed 4057
4063
Changed 4064
4066
Changed 4068
4071
Changed 4072
Changed 4073
Changed 4076
Changed 4077
Changed 4078
Changed 4079
Changed 4080
4081
4082
4083
4085
Changed 4086
Changed 4087
4088
4091
4092
Changed 4097
4100
Changed 4102
4106
4107
Changed 4109
4110
4122
4123
Changed 4124
4125
4126
4137
4138
Changed 4139
4140
4145
4153
4156
4157
4158
Changed 4169
4175
4199
Changed 4202
Changed 4221
4231
4232
4235
4248
4257
4270
New New 4303
6280
Changed 6502
6701
Changed 6706
6707
6708
Changed 61006
Changed 61010
61020
61022
61028
61029
61030
61040
61050
61057
61058
61059
61070
61071
61072
61074
61075
61076
61077
61079
61084
61085
61102
61103
61104
61105
61106
61107
61108
61109
61150
61151
61152
61170
61171
61172
61175
61176
61177
61178
61179
61180
61181
61183
61201
61250
61251
Changed 61252
61260
61400
61411
Changed 61500
61510
61601
61602
61605
61606
61607
61613
61615
61616
61617
61622

61631
61634
61635
61636
61637
61638
61641
Removed Removed 126
Removed Removed 132
Removed Removed 136
Removed Removed 412
Removed Removed 1877

Removed 119
Removed 141
Removed 590
Removed 594
Removed 1301
Removed 1303
Removed 1804
Removed 1808
Removed 1815
Removed 1819
Removed 1831
Removed 1833
Removed 1864
Removed 1891
Removed 2003
Removed 2051
Removed 4035
Removed 4163
Fault Name Used in Product
Fan module operation degraded: <X> FlexiBTS
Fan module faulty: <X> FlexiBTS
Unit temperature is high FlexiBTS
Unit SW download failed FlexiBTS
Difference between BTS master clock and FlexiBTS

reference frequency
No connection to unit FlexiBTS
Baseband resources mapping to cells failure FlexiBTS
Unit initialization failure FlexiBTS
Unit synchronization failed FlexiBTS

BTS RNC/Flexi Direct interface signalling link FlexiBTS
failure

failure

failure
Incompatible SW version detected in unit: FlexiBTS

<unitName>
Obsolete SW version detected in unit: FlexiBTS,MetroSite,MetroSite 50,Optima,Optima

<unitName> Compact RF Extension,Optima
IBBU,Supreme,Triplemode
BTS time not corrected FlexiBTS
Error in file server during file download type FlexiBTS

<fileTypeNumber>
File corrupted in SW download FlexiBTS
BTS SW download or activation failed FlexiBTS
BTS SW download or activation failed FlexiBTS
Mains power break, running battery backup FlexiBTS
Delayed cell shutdown alarm FlexiBTS

Immediate cell shutdown alarm FlexiBTS
Unit blocked FlexiBTS
Cell blocked FlexiBTS
BTS blocked FlexiBTS
# autonomous reset as recovery action FlexiBTS
POST test failed FlexiBTS
Missing NBAP cell parameters, defaults are FlexiBTS

used
Unknown HW resource FlexiBTS
Unit not supported by running SW FlexiBTS
Cell block rejected by RNC/Flexi Direct RNC FlexiBTS
Carrier power measurement fault FlexiBTS
Telecom configuration failure FlexiBTS

Communication failure with RNC FlexiBTS
Telecom cell enabling or disabling failed FlexiBTS
Telecom cell enabling or disabling failed FlexiBTS
Not enough DSP capacity to set up a cell FlexiBTS
Cell power monitoring FlexiBTS
BTS config error (Wrong LTX Frequency Order) FlexiBTS
DSP failure in radiolink creation FlexiBTS
Not enough resources for commissioned FlexiBTS

HSUPA
Rx signal level failure FlexiBTS
Rx signal level failure FlexiBTS

DSP mode change failed FlexiBTS
DSP malfunction occurred FlexiBTS
Resource block not available FlexiBTS
Resource block occupied by high priority FlexiBTS

services
Ten consecutive Nacks received from a DSP at FlexiBTS

DCH setup
Rel2 ESM HSPA capability not fully utilized FlexiBTS
PIC pool configuration failure FlexiBTS
Not enough CCCH Processing Set licenses FlexiBTS

commissioned
Hanging HSPA resources FlexiBTS
One of the Common Transport Channels is FlexiBTS

deleted
Not all resource steps for HS-RACH are FlexiBTS,FlexiLiteBTS

possible
RX signal level failure FlexiBTS

Invalid Shared LCG PIC Pool Configuration FlexiBTS
RAN level misconfiguration <feature name> FlexiBTS
Flash operation failure FlexiBTS
WAM internal error FlexiBTS
ATM traffic overload FlexiBTS
Fatal OSE error FlexiBTS
Out Of Frame Data Error FlexiBTS
Antenna link is down FlexiBTS

[User defined] FlexiBTS


BTS file error FlexiBTS
Communication failure FlexiBTS
Invalid frequency channel for the BTS HW FlexiBTS
Baseband bus configuration of <x> was FlexiBTS

rejected
Transmission clock missing FlexiBTS
Oven oscillator heating failure FlexiBTS
BTS Master Clock tuning failure FlexiBTS
Oven oscillator missing pulse FlexiBTS
FSP/WSP Frame synchronisation failed FlexiBTS

Transmission parameters missing FlexiBTS
Transmission parameters missing FlexiBTS
Starting temperature below minimum FlexiBTS
Connection to transmission broken FlexiBTS
Mast Head Amplifier above current window FlexiBTS

fault, <line>
Mast Head Amplifier below current window FlexiBTS

fault, <line>
Antenna line failure FlexiBTS
VSWR major alarm FlexiBTS
VSWR minor alarm FlexiBTS
Low noise amplifier failure FlexiBTS
Filter unit operation failed FlexiBTS
Filter unit faulty FlexiBTS

RET antenna control failure FlexiBTS
Antenna line device HW failure FlexiBTS
Antenna line device missing software FlexiBTS
SW corrupted FlexiBTS
System clock for extension system module not FlexiBTS

available
Incoherency in cell configuration FlexiBTS
Incoherency with RF Modules FlexiBTS
Faulty configuration of system modules FlexiBTS

Waiting for RF connections FlexiBTS
Heating element not working FlexiBTS
Not enough DSP resources per cell FlexiBTS
Fault diagnostics rule file error FlexiBTS
Fault diagnostics rule file error FlexiBTS
Not enough HW for LCR FlexiBTS
MHA unit operation failure FlexiBTS
MHA operation failure FlexiBTS
Antenna line device operation failure FlexiBTS

SRAM operation failure FlexiBTS
SRAM operation failure FlexiBTS
Self test failed FlexiBTS
License missing <licenseName> FlexiBTS
Antenna line device configuration failure FlexiBTS
External Filter missing from LCR FlexiBTS
Internal delay measurement failure FlexiBTS
Autonomous recovery reset FlexiBTS
PPS reference missing FlexiBTS
2M external reference missing FlexiBTS
RF Module configuring failed FlexiBTS
RF Module critical file not found FlexiBTS

RF Module file not found FlexiBTS
Frame clock missing FlexiBTS
RF BB bus synchronization error FlexiBTS
RF BB bus configuration error FlexiBTS
RF BB bus connection transmission error FlexiBTS
TX out of order FlexiBTS
RF Module gain adjusting failure FlexiBTS
RF Module filter input power missing FlexiBTS
RX out of order FlexiBTS
RF Module out of order FlexiBTS
RF Module Overheat FlexiBTS
Cooling fan out of order FlexiBTS

RF Module power output faulty FlexiBTS
No feedback signal FlexiBTS
Transmission quality deteriorated FlexiBTS
Temperature too low (heating ongoing) FlexiBTS
Unit unidentified FlexiBTS
Configuration file corrupted FlexiBTS
Post test failed FlexiBTS
Module clock faulty FlexiBTS
RF power decreased FlexiBTS
FPGA SW update failed FlexiBTS
RF module optical interface configuration failure FlexiBTS
RF Module blocked FlexiBTS

No module fan detected FlexiBTS
Cooling fan broken FlexiBTS
Cooling fan has reduced from the set speed FlexiBTS
Cooling fan is overspeeding FlexiBTS
Unit (module) temperature is high FlexiBTS
Unit (module) dangerously overheating FlexiBTS
Pipe dangerously overheating FlexiBTS
RF module temperature is high FlexiBTS
Increased BER detected on the optical FlexiBTS

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

to Radio Module
Antenna line switched off FlexiBTS
RP3 routing collisions are detected on FR FlexiBTS

module
Optical interface faulty FlexiBTS
Optical interface faulty FlexiBTS
Receiving failure in optical interface FlexiBTS
10b8b coding error in Optical Interface device FlexiBTS

<opt link/RP3>
Synchronization failure in Optical Interface <opt FlexiBTS

link/RP3 link>
Optical interface data/control/Ethernet buffer full FlexiBTS
OIC MCU Buffer Full FlexiBTS
Frame burst receiving fault FlexiBTS

Frame clock deviation fault FlexiBTS
BB bus reception error (summing device) FlexiBTS
BB bus transmission error FlexiBTS
Address mismatch in summing FlexiBTS
Synchronization error in RP1 receiver FlexiBTS
Synchronization error in RP1 receiver FlexiBTS
RP1 synchronization burst error FlexiBTS
Buffer over/underflow in clock crossing logic FlexiBTS
Firmware SW mismatch FlexiBTS
BB bus message in the wrong slot FlexiBTS
Summing not enabled for message type FlexiBTS
Transmission rule collision in Muksu FlexiBTS

Overload collision in transmitter FlexiBTS
SRIO enumeration FlexiBTS
SRIO retry stopped FlexiBTS
Eeprom read error FlexiBTS
SRIO host link down FlexiBTS
DSP accelerator initialization failure FlexiBTS
SRIO link degradation FlexiBTS
System Module failure FlexiBTS
RF Module failure FlexiBTS
Failure in replaceable baseband unit FlexiBTS
Baseband Bus failure FlexiBTS
Failure in optical RP3 interface FlexiBTS

Temperature alarm FlexiBTS
Fan failure FlexiBTS
Commissioning error: <x> FlexiBTS
Configuration error: <x> FlexiBTS
BTS reference clock missing FlexiBTS
BTS internal SW management problem FlexiBTS
Antenna Line Device failure FlexiBTS
No connection to BTS transport submodule FlexiBTS
Incoherency in cell configuration FlexiBTS
BTS reset required FlexiBTS
Feature expiry on <expDate>, <featName> FlexiBTS
TX failure in MIMO FlexiBTS

Too many LCGs for HW to support FlexiBTS
PLL status not locked FlexiBTS
GPS Receiver alarm: control interface not FlexiBTS

available
SRIO chain configuration was rejected FlexiBTS
Master unit has lost connection to the slave unit FlexiBTS
Writing parameter to Radio Module failed FlexiBTS
Reading license targetID from BTS failed FlexiBTS
Internal MTU configuration failure FlexiBTS
SW corrupted FlexiBTS
BTS is uncommissioned FlexiBTS
Invalid configuration file FlexiBTS
Failure in license activation FlexiBTS

Radio Master Conflict FlexiBTS
RP3-01 Link Conflict FlexiBTS
Retrieving backup license targetId information FlexiBTS

from BTS failed
Tuning frequency out of range FlexiBTS
Antenna line faulty FlexiBTS
Antenna line operation degraded FlexiBTS
Antenna line device SW download failure FlexiBTS
Antenna line device SW download failure FlexiBTS
No connection to unit FlexiBTS
Baseband internal link test failed FlexiBTS
TargetId verification failure FlexiBTS

Radio resources switched off FlexiBTS
HW not supported by current SW version FlexiBTS
Missing RP3-01 link FlexiBTS
SRIO multicast configuration failed FlexiBTS
FSP in resetting state FlexiBTS
RS485 IUANT port failure FlexiBTS
Module dangerously overheating FlexiBTS
Parallel RP3-01 link length mismatch FlexiBTS
Fan vendor not detected FlexiBTS
Distributed site support not enabled FlexiBTS
FSP overheating FlexiBTS
Cooling fan broken FlexiBTS

Cooling fan speed decreased FlexiBTS
Cooling fan is over speeding FlexiBTS
Summing service release from reset failed FlexiBTS
SW fallback FlexiBTS
FSM's fixed BB allocation based LCG is missing FlexiBTS
Internal communication error FlexiBTS
File System access failed FlexiBTS
BTS reset time increased FlexiBTS
Summing service default initialization failed FlexiBTS
BTS configuration not supported FlexiBTS

FSP reset failure FlexiBTS
Boot configuration inconsistency detected FlexiBTS
SRIO connection failure between system FlexiBTS

module
Power on #smodLogicalId #pwrLineId line FlexiBTS

switched off remotely by user
Baseband reset needed FlexiBTS
Peer system module connection lost FlexiBTS
GPS Receiver alarm: not tracking satellites FlexiBTS
GPS Receiver alarm: survey in progress FlexiBTS
GPS Receiver alarm: no stored position FlexiBTS
GPS Receiver alarm: position questionable FlexiBTS
GPS Receiver alarm: EEPROM invalid FlexiBTS
Incorrect Rx bandwidth FlexiBTS

Incorrect Tx bandwidth FlexiBTS
Incorrect carrier separation FlexiBTS
Read-only field encountered in the antenna line FlexiBTS

device
Validation of signed file failed FlexiBTS
Reference clock missing in startup FlexiBTS
Vertical sectorization license missing FlexiBTS
Tilting per carrier license missing FlexiBTS
Tilting per TX/RX license missing FlexiBTS
Extended logging into ramdisk is active FlexiBTS
Feature is not activated in SCF FlexiBTS
Extension System Module cannot be taken into FlexiBTS

use
Extension System Module is connected through FlexiBTS

incorrect RP3-01 line rate
Reading targetId or timestamp from FR failed FlexiBTS
Internal baseband bus synchronization error FlexiBTS
BTS booted due to # FlexiBTS
<parameterName> out of range FlexiBTS
IRC Receiver not available for pure single RX FlexiBTS

BTS configuration
Unsupported fiber cabling FlexiBTS
MHA in bypass mode FlexiBTS
Target ID has been recovered FlexiBTS
Phase error exceeds 5 us limit FlexiBTS
High memory consumption FlexiBTS
Critical bit toggling error FlexiBTS
DSP platform fatal error FlexiBTS

DSP application fatal error FlexiBTS
Externally triggered DSP fatal error FlexiBTS
BTS booted at $date due to $RCause FlexiBTS
BTS reset required FlexiBTS
DSCP $D signalled but not configured FlexiBTS
BFD group $bfdGrpId down FlexiBTS
Forwarding table exceeds maximum route entry FlexiBTS

count 1200
LOF on unit $U, interface $IF FlexiBTS
LOS on unit $U, [Ethernet] interface $IF FlexiBTS
Dead Peer Detected FlexiBTS
Interface under test on unit $U, interface $IF for FlexiBTS

$T minutes
Missing or non-compliant SFP module on unit FlexiBTS

$U, interface $I
LOCD on unit $U, {interface/imag} $IF FlexiBTS
Synchronization lost FlexiBTS
$Protocol Timing source lost [on unit $U] [, FlexiBTS

interface $IF]
CESoPSN UDP port overlap fault FlexiBTS
CES pseudowire tunnel $T down on unit $U FlexiBTS
CES pseudowire $W down on unit $U FlexiBTS
CES pseudowire remote packet loss on wire FlexiBTS

$W on unit $U
CRL Update Failure FlexiBTS
Link OAM loopback inserted on unit $U, FlexiBTS

interface $F by $P peer
Link OAM link lost on unit $U, interface $F FlexiBTS
Link OAM critical link event $E on unit $U, FlexiBTS

interface $F
SFP HW Failure FlexiBTS

TWAMP session down for reason: $r FlexiBTS
OSPF neighbor $cause FlexiBTS
AIS (Multiplexer Section) on unit $U, interface FlexiBTS

$IF
RDI (Multiplexer Section) on unit $U, interface FlexiBTS

$IF
EBER on unit $U, {interface/imag} $IF FlexiBTS
LOP (Administrative Unit) on unit $U, interface FlexiBTS

$IF
AIS (Administrative Unit) on unit $U, interface FlexiBTS

$IF
UNEQ (High Order Path) on unit $U, interface FlexiBTS

$IF
PLM (High Order Path) on unit $U, interface $IF FlexiBTS
RDI (High Order Path) on unit $U, interface $IF FlexiBTS
LOMF on slot $U, interface $IF FlexiBTS
AIS on unit $U, interface $IF FlexiBTS

RDI on unit $U, interface $IF FlexiBTS
Loss of IMA frame on unit $U, interface $IF FlexiBTS
IMA link out of delay synchronization on unit FlexiBTS

$U, interface $IF
IMA remote failure indication on unit $U, FlexiBTS

interface $IF
Far-end transmit link unusable on unit $U, FlexiBTS

interface $IF
Far-end receive link unusable on unit $U, FlexiBTS

interface $IF
Far end group start-up on unit $U, IMA Group FlexiBTS

$IMAG
Config-abort state on unit $U, IMA Group FlexiBTS

$IMAG
Far end config-abort state on unit $U, IMA FlexiBTS

Group $IMAG
Insufficient links on unit $U, IMA Group $IMAG FlexiBTS
Far end insufficient links on unit $U, IMA Group FlexiBTS

$IMAG
Group timing mismatch on unit $U, IMA Group FlexiBTS

$IMAG
Transport module missing: $unit FlexiBTS
IPCP Failure FlexiBTS
LCP Failure on Interface $IF FlexiBTS
PPP Interface down FlexiBTS
STC link down on $IF FlexiBTS
Transport memory utilization threshold FlexiBTS

exceeded
Licence missing <licenceCode>, FlexiBTS

<licenceName>
CCM fault level $ prio $p cause $c FlexiBTS
ETH AIS fault interface $IF level $l mac $x FlexiBTS
Too many login attempts with incorrect FlexiBTS

credentials from $S
Automatic BTS Operator Certificate retrieval FlexiBTS

unsuccessful
Pseudowire $PW down in ingress direction on FlexiBTS

unit $U.
Pseudowire $PW down in egress direction on FlexiBTS
unit $U
BFD $session down, ingress, $sourceIP to FlexiBTS

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

$destinationIP
Auto-negotiation mismatch, on unit $U, Ethernet FlexiBTS

interface $IF
NTP server is not accessible FlexiBTS
Power cannot be applied to powered device on FlexiBTS

unit $U, IF $IF
Vendor BTS certificate is about to expire FlexiBTS
Link flapping fault FlexiBTS
BTS and/or peer trust anchor expired or due to FlexiBTS

expire
MLPPP link Degrade FlexiBTS
SyncE SSM Timed Out on unit $UID, interface FlexiBTS

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

interface $IF
ToP master service $IP unusable FlexiBTS
Unsupported HW device FlexiBTS
Frame loss threshold exceed on mac $m flm $f FlexiBTS
Two way delay threshold exceeded on mac $m FlexiBTS
OneWay delay variation threshold exceed on FlexiBTS

mac $m
Configuration change rejected by BTS FlexiBTS
IP Traffic Capturing Ongoing [port $port,] [mac FlexiBTS

$m]
Cell power parameter out of range FlexiBTS,MetroSite,MetroSite 50,Optima,Optima

Compact RF Extension,Optima
IBBU,Supreme,Triplemode
No baseband capacity for common channels FlexiBTS
Fault between FSM and FSP FlexiBTS
BTS reset needed to activate a licence FlexiBTS

RF loss of secondary optical interface FlexiBTS
Message routing problem in receiver (RX) FlexiBTS
SRIO link drop FlexiBTS
DSP lost all Bit Co-Processors FlexiBTS
Telecom configuration failure
Reduced receiver capacity in cell
ATM processor faulty
ATM processor faulty
Power unit output voltage fault
WEA power regulator fault
Unknown Cabinet Type
BTS config error (incorrect carrier candidates)

Not able to synchronize baseband bus with <x>
Oven oscillator clock missing
Active clock tuning fault
License missing Out of Order (MHA) - a license required for MHA

to work is not available at MHA's startup._x000D_
Degraded (RET) - changes of angle are not
allowed to due to lack of tilting license (cells may
be set up inproperly).
BTS config error (incorrect carrier candidates)
Summing service release from reset failed
Optical Interface Frame clock faulty
Optical interface buffer alarm
Configuration file is not supported
Unit inoperable due to missing license

<licCode>, <licName>
Detecting Unit Source
FCM Fan
FCM FSM/FANGROUP_x000D_
FCM/FCT FCM/FCT, FSP, FTM, FBIA_x000D_

_x000D_
FCM FSP, DSP_x000D_

_x000D_
FCM, FCT FCM, FCT
FCM/FCT FSP, FT, FF, MHA, TILT, FR, FA, extension

FSM, FBB_x000D_
For fault 4052 the only source is pluggable
FSP_x000D_
_x000D_
FCM/FCT FCM/FCT, FSP
FCM/FCT FCM/FCT, FSP_x000D_

_x000D_

_x000D_
FCM/FCT, FSP FCM/FCT, FSP_x000D_

_x000D_
FCM/FCT FCM/FCT_x000D_
_x000D_
_x000D_
FCM/FCT FCM/FCT
FCM/FCT FCM/FCT, FR, FF, FSP, FTM, uncommissioned

FR_x000D_
_x000D_
UltraSite, MetroSite, MetroSite 50, UltraSite, MetroSite, MetroSite 50, Triple-mode:

Triple-mode: WAM; FlexiBTS: FCM; WAM, WTR, WPA/WMP, AXC_x000D_
UltraSite/EUBB: WAMA _x000D_
FlexiBTS: FCM_x000D_
_x000D_
UltraSite/EUBB: WSMF
_x000D_
FCM/FCT FCM (FSMr2) / FCT (FSMr3), FR,

uncommissioned FR_x000D_
_x000D_
FCM/FCT FCM (FSMr2) / FCT (FSMr3), FR_x000D_
FCM/FCT FCM (FSMr2) / FCT (FSMr3), FR_x000D_
FCM FCM, FCT
FCM/FCT LCR
FCM/FCT LCR
FCM/FCT FR, extension FSM, FSP
FCM/FCT LCR
FCM/FCT FCM/FCT
FCM / FCT FCM/FCT, FR, FSP, FBIA, DSP_x000D_

_x000D_
FCM, FT, FSP FSP, FT, FCM/FCT, DSP
FlexiBTS: FSM; FlexiBTS: FCM, FCT
FCM/FCT - FSP (fixed and plug-in cards)_x000D_

- FR_x000D_
- FTM_x000D_
- FF_x000D_
_x000D_
FCM/FCT All possible units.
FCM/FCT LCR
FSM Tx1-n/Rx1-n
FCM, FSP, FCT extension module FCM/FCT, FSP, FR,

DSP_x000D_
_x000D_
DSP_x000D_
_x000D_

DSP_x000D_
_x000D_
FCM, FCT FCM, FCT, (RNC)_x000D_

_x000D_
FCM, FCT, FSP LCR
FCM, FCT, FSP LCR
FCM, FCT FCM, FCT_x000D_
FSM TX
FSM LTX
FCM/FCT DSP
FCM, FCT FCM, FCT
FSM Antenna Line
FSM Antenna Line

FSM DSP_x000D_
_x000D_
FSM DSP_x000D_
FSM FlexiBTS Rel2: FSP,FCM_x000D_

FlexiBTS Rel3: FCT_x000D_
FCM, FCT FlexiBTS Rel2: FSP,FCM_x000D_

FlexiBTS Rel3: FCT_x000D_
FCM/FCT DSP
FCM ESM
FCM, FCT LCR,FCM,FCT
FCM, FCT FCM, FCT
FCM/FCT DSP
FCM,FCT LCR
FCM, FCT, FSP FCM, FCT
FCM, FCT RX1-n

FSM FCT
FSP <feature code>
FCM, FCT, FSP FCM, FCT, FSP_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_
FCM, FCT FCM, FCT
System Module, Extension Module FSM (FCM, FSP), FBIA, FCT
FSP DSP
FSP DSP
FSP DSP
FCM, FCT FCM, FCT, FR_x000D_
_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_
_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_

_x000D_
_x000D_

_x000D_
FCM/FCT FCM / FCT _x000D_

_x000D_
FCM/FCT FCM/FCT
All units can use this fault This can be detected in any unit of the BTS.
FCM/FCT LCR
FCM/FCT HWPORT, FSP, DSP, FR_x000D_
FCM, FCT FCM, FCT

_x000D_
_x000D_
FlexiBTS: FCM, FCT; FlexiLiteBTS: FlexiBTS: FCM, FCT

SCR
FlexiLiteBTS: SCR
FCM FCM_x000D_
FCM/FCT FT, FCT
FCM/FCT FT, FCT
FCM FSM
FCM FSM
FR, FF Flexi MHA
FR, FF Flexi MHA
FF, FR Antenna line (RX, DC power)
Flexi Filter, FR Antenna line
Flexi Filter RX1-n
Flexi Filter TX1-n / RX1-n
Flexi Filter TX1-n / RX1-n_x000D_

AntennaLine (in case of uncommissioned
resource)
TILT TILT
TILT TILT
TILT TILT
TILT TILT
TILT TILT
FF, TILT FF, TILT, MHA, EFIL
FF, MHA, TILT FF, MHA, TILT
FCM/FCT Filter, FR, FTM, uncommissioned FR
FCM/FCT FSM
FCM FR
FCM FR
FCM, FCT FCM

FCM FCM
FCM FCM
FCM FCM
FCM, FCT FCM, FCT
FCM, FCT FCM, FCT
FCM/FCT LCR
AISG MHA AISG MHA
AISG MHA AISG MHA_x000D_
FSM,FCT Flexi Filter, FA, AISG MHA, RET

FSM FSM_x000D_
_x000D_
FSM FSM_x000D_
_x000D_
FCM FSP
FCM/FCT LICENSE-<feature code>
FSM FF, MHA, RET, other unknown ALD
FCM LCR
FSM, FSP, FCT DSP_x000D_
_x000D_
FR, FCM/FCT FR_x000D_

[AAS]:FR, TX1-n/RX1-n
FR FR_x000D_
FR FR_x000D_
FR FR, RX1-n
FR FR, TX1-n / RX1-n
FR TX1-n / RX1-n
FR FR, TX1-n
FR TX1-n
FR TX1-n
FR Antenna line
FR RX1-n
FR FR_x000D_
FR FR
FR Fan
FR FR, TX1-n
FR TX1-n
FR Antenna line
FR FR
FR FR
FR FR, TX1-n/RX1-n
FR FR
FR FR_x000D_
[AAS]: FR, TX1-n/RX1-n
FR TX1-n
FR FR
FR FR
FR FR
FR/RFSW Fan supervision.
FR/RFSW FAN, FAN_GROUP
FR/RFSW Fan supervision.
FR/RFSW RFSW
FR/RFSW FR
FR/RFSW FR_x000D_
[AAS]: FR, TX1-n / RX1-n
FR/RFSW TX1-n
FR FR
FR FR
FR FR
FR Antenna line
FR FR
FCM, FCT OptIF (HWPORT)
FCM, FCT FCM: OptIF (HWPORT) or the channel (1-12)

between the OIC FPGA and MUKSU
ASIC._x000D_
_x000D_
FCT: OptIF (HWPORT)
FCM, FCT FCM: OptIF (HWPORT) 1-5 or the channel (1-
12) between the OIC FPGA and MUKSU
ASIC._x000D_
_x000D_
FCT: OptIF (HWPORT) 1-6
ASIC._x000D_
_x000D_
ASIC._x000D_
_x000D_
ASIC._x000D_
_x000D_
ASIC._x000D_
_x000D_
FCM, FCT FCM, FCT
FCM, FCT FCM, FCT

_x000D_
FCM, FCT FSP, FBB, OptIF (HWPORT)

_x000D_
FCM, FCT FCM, FCT, FSP_x000D_

_x000D_
FCM FSM
FCM FSM
FCMD, FCT Master FSM
FCT, FCM OptIF (HWPORT)
FCT FCT(Master System Module or Extension

System Module)
FCM FSP
FCT, FCM FSP
FCT, FCM FSP

FCT, FCM FSP
FCT FCT, ESM
FCT FSP, FCT, FBB, DSP, ESM.
FCT FBB, ESM
FCT FCT, ESM
FSP DSP
FSP DSP
FSM FSM, FCT, FSP, DSP
FSM, FR FR
FSM FSP
FSM, FR FSM, FR_x000D_

_x000D_
FSM, FR FSM, FR
FSM, FR FSM, FR, FBIA
FSM, FR FSM/FAN, FR
FSM, FR FSM, FR, FT
FSM, FR FSM, FR, MHA, TILT, LCR, FBIA_x000D_

_x000D_
FSM FSM
FSM FSM, FR, FT, FBIA_x000D_

_x000D_
FSM, Antenna Line Device itself FR, MHA, TILT, EFIL
FSM FTM
FCM, FCT FSM, LCR
FSM Extension FSM, FR
FCM/FCT LICENSE-<feature code>
FCM/FCT LCR
FSM FR
FCM FSP_x000D_
_x000D_
FCM/FCT GNSS
FSM FSP, DSP_x000D_
FSM/FCT FSP, FSM/FCT (extension), FBIA,

DSP_x000D_
FCM/FCT FR
FCM/FCT FR
FCM FCM, FSP
FCM/FCT Filter, FR, FTM, uncommissioned FR
FCM/FCT FSM
FCM/FCT FCM/FCT
FCM/FCT FSM
FCM FR
FCM FR

_x000D_
FCM/FCT FR
FR TX1-n / RX1-n_x000D_
AntennaLine (in case of uncommissioned
resource)
FR Antenna line
FR Antenna line
FCM,FCT MHA, RET
FCM,FCT MHA, RET
FCM/FCT FSP, FT, FF, MHA, TILT, FR, FA, extension

FSM, FBB_x000D_
For fault 4052 the only source is pluggable
FSP_x000D_
_x000D_
FCM FCM
FSM FSM
FCM/FCT Antenna line
FCM, FCT FSM, FR
FCM Carriers
FSM FCT
FCM FSP
FCM FSP
FCM OptIF (Link)
FCT FAN1-n
FSM FR
FCT FSP
FCT Fan/Fan group

FCT Fan/Fan group
FCT Fan/Fan group
FCT FCT
FSMr2: FCM, FSMr3: FCT 4082:_x000D_

FSMr2: FCM, FSP MCU_x000D_
FSMr3: FCT_x000D_
_x000D_
4083:_x000D_
FSMr2: FCM_x000D_
FSMr3: FCT_x000D_
FSMr3: FCT_x000D_
_x000D_
_x000D_
4085: (for FSMr3 only)_x000D_
4083:_x000D_
FSMr3: FCT
FSMr2: FCM_x000D_
FSMr3: FCT_x000D_
FSMr3: FCT_x000D_
_x000D_
_x000D_
4083:_x000D_
FSM FSM FCT
FSMr3:
FSMr2: FCM_x000D_
FSMr3: FCT_x000D_
_x000D_
FSM/FSP, FCM/FCT FSM, FSP,
FSMr3: FCTDSP
FCM, FCT FCM, FCT
FSM FSM
FCT FCT
FCT FSP_x000D_
FCM/FCT FSP
FCM/FCT FCM/FCT, FSP MCU_x000D_

_x000D_
FCT slave FCT
FCM, FCT FCM, FCT
FCM FSP
FCM FCM
FCM/FCT GNSS
FCM/FCT GNSS
FCM/FCT GNSS
FCM/FCT GNSS
FCM/FCT GNSS
FSM LCR
FSM LCR
FSM LCR
FSM AISG MHA, TILT
FCT FCT
FCM, FCT FCM, FCT
FCM, FCT LCR
FCM, FCT LCR
FCM, FCT LCR
FCT FCT
FCM, FCT LCR
FCT ESM
FCT ESM
FCM/FCT FCM/FCT
FCM/FCT FSP
FCT, FCM FCT, FCM
FCM/FCT Antenna line
FCM/FCT FCM/FCT
FCM;FCT FR
AISG MHA MHA
FCM/FCT FSM
FCM/FCT BTS
FSM FCM/FCT, FSP_x000D_
FSP FSP
FCM/FCT DSP
FCM/FCT, DSP DSP
FCM/FCT, DSP DSP
FTEB, FTPB, FTIA, FTFA, FTJA, NE-FTM-1

FTHA, FTOA, FTIB, FTLB, FTFB,
FTIF,FSM
FTEA, FTEB, FTIA, FTIB, FTLB, NE-FTM-1

FTFA, FTHA, FTJA, FTOA, FTFB,
FTPB, FSM,FTIF
FTIB, FTIA, FTJA, FTFB, FTLB, QOS

FSM, FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, BFDGRP

FTEB, FTPB, FTHA, FTFA, FSMF ,
FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, IPRT-2

FTEB, FTPB, FTHA, FTFA, FSMF ,
FTIF
FTEB, FTPB, FTIA, FTFA, FTJA, PPTT

FSM,FTIF
FTEB, FTPB, FTIA, FTFA, FTJA, PPTT, SPTT, ETHLK

FSM,FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, IKESA

FTEB, FTPB, FTHA, FTFA, FSM,
FTIF
FTOA, FTIA, FTJA, FTIB, FTFB, PPTT, SPTT

FSM,FTIF, FTLB
FTOA, FTIA, FTJA, FTIB, FTFB, SPTT, ETHLK

FSM,FTIF, FTLB
FTHA, FTOA, FTIB, FTFB, FTIF
FTJA, FTHA, FTOA, FTEB, FTIA, STPG

FTFA, FTPB, FTIB,FIIB, FTLB,
FTFB, FSM,FTIF
FTEB, FTPB, FTIA, FTFA, FTIB, STPG

FTLB, FTOA, FTFB, FSM,FTIF
FTIB,FTLB,FTFB, FTIF,FSM CESIF
FTIB, FTLB, FTFB,FSM,FTIF CESPWT
FTIB, FTLB, FTFB, FSM,FTIF CESPW
FTIB, FTLB, FTFB, FSM,FTIF CESPW
FTIA, FTOA, FTJA, FTIB, FTLB, CERTH

FTFB, FTEB, FTPB, FTHA, FTFA,
FSM, FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, ETHLK

FSM,FTIF

FSM,FTIF

FSM,FTIF
FTIA, FTIB, FTLB, FTOA, FSM, NE-FTM-1

FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, TWAMP
FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, OSPFV2

FSM,FTIF
FTOA SMTT
FTOA SMTT

FTHA, FTIB, FTLB, FTFB,
FSM,FTIF
FTOA SVTT
FTOA SVTT
FTOA SVTT
FTOA SVTT
FTOA SVTT

FSM,FTIF

FSM,FTIF
FSM,FTIF
FTEB, FTPB, FTIA, FTFA, FTJA, IMAL

FTHA, FTIB, FTFB, FTLB, FSM,
FTIF

FTIF

FTIF

FTIF

FTIF
FTEB, FTPB, FTIA, FTFA, FTJA, IMAG

FTIF

FTIF

FTIF

FTIF

FTIF

FTIF
FSM, FTIF UNIT
FTEB, FTPB, FTIA, FTIB, FTLB, P3SL; P3ML

FTFA, FTJA, FTHA, FTOA, FTFB,
FSM,FTIF
FTEB, FTPB, FTIA, FTIB, FTLB, P3LP

FSM,FTIF
FTEB, FTPB, FTIA, FTFA, FTJA, P3ML, P3SL

FSM,FTIF
FTEB, FTPB, FTIA, FTFA, FTJA, A2ST

FTIF
FTLA, FTLB NE-FTM-1
FTJA, FTHA, FTOA, FTPB, FTEB, NE-FTM-1

FTIA, FTFA, FTIB, FTLB, FTFB,
FSM,FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, OAMMA,OAMMD,NE-FTM-1

FTEB, FTHA, FTFA, FSM, FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, NE-FTM-1

FTIF,
FTEB, FTPB, FTIA, FTIB, FTLB, NE-FTM-1

FSM,FTIF
FTEB, FTPB, FTIA, FTLB, FTFA, CERTH

FTJA, FTHA, FTOA, FTIB, FTFB,
FSM,FTIF
FTIA, FTJA, FTIB, FTLB PWMP

FTIA, FTJA, FTIB, FTLB PWMP
FTIA, FTJA, FTIB, FTLB, FTFB, BFD

FTIF
FTIA, FTJA, FTIB, FTLB, FTFB, BFD

FTIF
FTIB, FTFB, FTLB, FSM,FTIF ETHLK
FTIA,FTIB,FTOA,FTJA,FTLB,FTFB, INTP
FTPB, FTEB, FTHA, FTFA,
FSM,FTIF
FTIB,FTLB,FTOA, FTIA, FTJA, ETHLK

FTFB, FQGA
FTIA,FTIB,FTJA,FTLB,FTFB,FTIF, CERTH
FTPB, FTEB, FTHA, FTFA,
FTIB,FTLB,FSM,FTIF
FTIB,FTFB,FTLB,FTIA,FTJA, FTIF, ETHLK

FSM
FTLB, FTIB, FSM, FTIF CERTH
FTEB, FTPB, FTIA, FTFA, FTJA, P3ML

FSM,FTIF
FTIB,FTLB,FTFB, FSM,FTIF STPU
FTIB,FTLB,FTFB, FSM,FTIF STPU

FTIB,FTLB,FTFB,FSM, FTIF TOPF
FSM UNIT
FTIA, FTJA, FTIB, FTLB, FTFB, OAMMA

FSM, FTIF, FQGA

FSM, FTIF, FQGA

FSM, FTIF, FQGA
FTIA, FTJA, FTIB, FTLB, FTFB, NE-FTM-1

FSM, FTIF, FQGA
FSM,FTIF IPNO
UltraSite, MetroSite, MetroSite 50, LCR

Triple-mode: WAM; FlexiBTS: FCM,
FCT; UltraSite/EUBB: WSMF
FCM/FCT FCM/FCT
FSM, FSP; FSM, FSP_x000D_

_x000D_
FSP DSP

FR FR
FCT, FCM FSP
FCT FCT
FCT DSP

Triple-mode: WAM; FlexiBTS: FCM, slave WAM, WSP, WTR, WPA/WMP_x000D_
FSP, FCT; UltraSite/EUBB: WSMF, _x000D_
WSPF; FlexiBTS: extension module FCM, FSP, FR,
DSP_x000D_
FCT/FCM LCR
_x000D_
UltraSite/EUBB: WSMF, WSPF, WTR,
WPA/WMP

Triple-mode: WAM; FlexiBTS: FSM WAM, WSPC
(FSP)
FlexiBTS: FSM (FSP)
Triple-mode: WAM; FlexiBTS: FSM WAM, WSPC
(FSP)
FlexiBTS: FSM (FSP)
WPS WPS
WEA WEA
WAM WAM

Triple-mode: WAM; FlexiBTS: FCM LCR
FlexiBTS: LCR
FlexiBTS: FCM/FCT, FSP; FlexiBTS: FSP, OptIF,_x000D_
UltraSite/EUBB: WSMF; FlexiLiteBTS: FSP, SCR_x000D_
FlexiLiteBTS:SCR UltraSite/EUBB: WSMF, WSPF
FlexiBTS: FCM, FCT; FlexiLiteBTS: FlexiBTS: FCM, FCT

SCR
FlexiLiteBTS: SCR
WAM Active WSC, WMC
FCM MHA, RET

Triple-mode: WAM; FlexiBTS: FCM LCR
FlexiBTS: LCR
FlexiBTS: FCM, FCT; FlexiBTS: FCM, FCT
FCM OIC FPGA
FlexiBTS: FCMD; UltraSite/EUBB: FlexiBTS: FCMD: OptIF 1-5

WSMF
UltraSite/EUBB: WSMF (BOFU FPGA)

Triple-mode: WAM; FlexiBTS: FCM; WAM
UltraSite/EUBB: WAMA
FlexiBTS: FCM
FCM/FCT FR
UltraSite/EUBB: WAMA
Meaning State
The fan is not rotating, rotating slower Start / Cancel

than required, or the RPM information is
unavailable for the fan._x000D_
The fault is activated only when the unit
temperature exceeds the Tblock property
Multiple fans of the same fan group are Start / Cancel
(default being 67¿C). The threshold
rotating slower than required._x000D_
prevents faults caused by snow as
The fault is activated only when the unit
insufficient protection against snow for
temperature exceeds the Tblock property
the HW might block fans._x000D_
(default being 67¿C). The threshold
The
This temperature of a unit/module
fault is also raised if the fan is Start / Cancel
prevents faults caused by snow as
exceeds the threshold
rotating faster value.- no matter
than required
insufficient protection against snow for
what the temperature is._x000D_
the HW might block fans._x000D_
This fault is also raised if multiple fans of
Software
the same update
fan group to aare
unit/subunit or
rotating faster Start
module has failed._x000D_
than required - no matter what the
_x000D_
temperature is._x000D_
UltraSite, MetroSite: The fault might also
be caused by disconnected CIF bus
The reference frequency that the BTS Start / Cancel
cables.
master clock receives from the transport
part has changed by about 0.2 ppm or
more (which equals the change
magnitude of 204 DAC steps or more)
Connection to a unit belonging to the BTS Start / Cancel
during the measurement period (about 20
configuration has been lost or FSP
minutes), compared to the BTS master
cannot be detected.
clock frequency. _x000D_
_x000D_
Failure
The cause wasofdetected
the alarm when
can NodeB
be:_x000D_O&M Start
system
_x000D_ presented available FSPs
to_x000D_
1. The Iub reference frequency has
TCOM
changed software
because in of
order to map
a fault in theFSPs to
cell. The FSPs
transmission relatedsynchronization,
network to the
A unit or module or an IP address Start
faulty_x000D_
which in turnhas
is caused
initialization failed. by an equipment
operation may not
fault or a setting be utilized.
error. Note that The reason
if the
for the failure
network is an internal_x000D_
synchronization malfunction lasts
problem
for a longwith thethe
time, NodeB
alarmO&M system.
is canceled
A unit the
when or module or an IP reaches
BTS frequency address the Start
initialization has failed.
faulty Iub synchronization. The alarm can
also be activated if the faulty Iub
synchronization is corrected and there is
again the difference
FCM/FCT/FSP of 0.2 ppm or
synchronization hasmore. Start
The
failed.alarm is canceled when the
difference becomes lesser than 0.2
ppm._x000D_
_x000D_
2. The Iub reference frequency fluctuates
continuously because of a large quantity
of jitter or wander in the transmission
network. The alarm is continuously
activated or canceled, however, the
alarming state might predominate. There
is always some jitter or wander in the
transmission network; the limits are
defined in ITU-T G.823/824/825._x000D_
A common NBAP link failure has Start / Cancel
occurred. It can be caused by a
transmission network problem. The most
common reason for this alarm is a
frequent transmission breaking.
A dedicated Node-B Application Protocol Start / Cancel
(NBAP) link failure has occurred. It might
be caused by the RNC.
This indicates an AAL2 signaling link Start / Cancel

failure. The most common reason for this
alarm is a frequently breaking
transmission. In the case of Ultra BTS, it
can be caused by a broken WAM.
A new unit with an incompatible SW might Start / Cancel
have been inserted into the BTS.
Running SW version is not able to install Start / Cancel

requested SW version.
The SNTP time cannot be fetched from Start / Cancel

the transport system (FT) within the time
limit.
The BTS cannot obtain a file from the file Start / Cancel
server (error in FTP open or FTP get or
HTTP(S) GET). The file server is down,
the file is missing, or the path is incorrect.
There is a possible error in the DCN and
The download is corrupted or the Start / Cancel
Iub, or a user-administration error (an
software is incorrectly produced.
invalid username or password, or the user
does not have access rights to the
files)._x000D_
The BTS SW update has
<fileTypeNumber> failed.
that The error
is included in Start / Cancel
might bename
the fault caused
is by a unit reset
a variable during
parameter,
the
whichSWidentifies
update, the
a hardware problem
type of file in
for which
the unit, cabinet
download Incompatibility
failure problems
has been reported.
with the download or a corrupted flash file
The BTS SW update has failed. The error Start / Cancel
system.
might be caused by a unit reset during
the SW update, a hardware problem in
the unit, cabinet Incompatibility problems
with the download or a corrupted flash file
There is a fault in the mains power Start / Cancel
system.
supply. The BTS has received a Battery
Backup alarm and the intelligent
shutdown procedure has started.
The BTS cells are disabled because the Start / Cancel
Battery Backup alarm (ID=37) is active.
The BTS cells are disabled because the Start / Cancel
Battery Backup alarm (ID=37) is active.
A unit is blocked with the BTS Site Start / Cancel

Manager._x000D_
_x000D_
The purpose of the fault is to avoid
alarms that might be raised during the
The user has blocked the cell with the Start / Cancel
unit maintenance task.
BTS site manager.
The BTS is blocked with the BTS site Start

manager. The fault indicates that the
alarms that might be raised during a BTS
maintenance task should be avoided.
The BTS tries to correct a fault situation Transient
by performing a recovery reset to a unit,
the site, or the BTS.
A failure in the unit or module has been Start

detected during the BTS power-on self
test (POST).
One or more cell parameters are missing Start / Cancel

from the RNC/Flexi Direct RNC
configuration data and the BTS
commissioning file.
A unit cannot be identified by its product Start
code or its physical device address
(object ID).
An unsupported unit has been detected in Start

the BTS. Typically, this happens when a
new unit version is installed and there is
an older BTS SW in use that does not
support the new unit version.
The cell has been disabled because of Start / Cancel
BTS internal reasons (for example, if the
RNC has rejected the normal cell blocking
during an intelligent shutdown).
The RF module power measurement has Start / Cancel
failed.
This indicates a telecom slave Start

configuration or registration failure, a unit
RNW configuration failure, and a telecom
RNW reconfiguration failure._x000D_
_x000D_
- FSP unit to FCM allocation
failure_x000D_
- DSP subunit to FSP allocation
failure_x000D_
_x000D_
Note that depending on the fault source,
the unit status might be related to either
the state of a particular carrier resource
on the FR module or FSP board on the
FCM, and might therefore not be in line
_x000D_
failure_x000D_
failure_x000D_
_x000D_
The BTS does not receive a response
_x000D_ Transient
from
Note the
thatRNC (a block
depending onrequest).
the fault source,
failure_x000D_
the unit status might be related to either
failure_x000D_
on the cell
Either FR enabling
module or(theFSP board
setup of on the
CPICH Start / Cancel
_x000D_
FCM,
and and might therefore not be in line
NoteBCH) or cell disabling
that depending on the(the
faultrelease
source,of
with
commonthe source HW unit failed._x000D_
channels) state._x000D_
the unit status mighthas be related to either
_x000D_
The
on reason
the might be
FR enabling
module a hardware
or(the
FSP board or the
a bus
Either cell setup of on
CPICH Start / Cancel
problem,
FCM, andormight
a lack of DSP or
therefore nottransport
be in line
and BCH) or cell disabling (the release of
resources.
with the source HW hasunit failed._x000D_
state._x000D_
common channels)
_x000D_
The reason might be a hardware or a bus
There is not enough BTS baseband Start / Cancel
problem, or a lack of DSP or transport
capacity to set up a cell.
resources.
The WPA/radio output power has Start / Cancel

dropped._x000D_
There is a fault in the downlink
transmission path.
The lower LCR ID has been assigned to a Start
higher frequency, or vice versa, for an RF
Module that is in dual carrier mode.
_x000D_
_x000D_
Radio link creation has been failing Start
A second carrier is assigned to an RF
repeatedly because of the DSP rejection.
Module that is in single carrier mode.
At least one LCG in the BTS does not Start / Cancel

have enough resources for the HSUPA
minimum capacity commissioned with the
parameter "Number of HSUPA resource
steps reserved for HSUPA
133: Start / Cancel
users"._x000D_
EFaultId_RxAntennaSignalLevelTooLow
If the LCG has two HSUPA schedulers,
Al_x000D_
then the sum of the HSUPA Resource
The RX signal level is less than -112dBm
Steps that is statically allocated in both
_x000D_
133:
System Modules is compared with the Start / Cancel
_x000D_
EFaultId_RxAntennaSignalLevelTooLow
commissioned amount. The fault is raised
134:
Al_x000D_
for the BTS.
EFaultId_RxAntennaSignalLevelDifferenc
The RX signal level is less than -112dBm
eTooHighAl_x000D_
_x000D_
The difference between the maximum
_x000D_
and minimum power levels of all RX
134:
antennas in the same cell and sector
EFaultId_RxAntennaSignalLevelDifferenc
exceeds the defined limit for cell._x000D_
eTooHighAl_x000D_
The difference between the maximum
and minimum power levels of all RX
antennas in the same cell and sector
exceeds the defined limit for cell._x000D_
DSP configuration to correct mode was Start / Cancel
not successful.
If Telecom does not get a response from Start / Cancel

the PIC DSP or other DSP subsystems
on time then Telecom raises an alarm to
BTSOM. This fault is applicable for PIC
pool setup, activation, and deactivation.
If there are no DSP resources for PIC Start / Cancel
PIC reconfiguration messages are sent to
configuration, Telecom rejects the PIC
PIC DSP (either directly or via HSUPA
configuration, and raises an alarm to
L2).
indicate "Resource block not available".
If PIC configuration cannot be allocated to Start / Cancel
a DSP resource because the DSP is in
use with some high-priority users,
Telecom raises this fault. Telecom then
tries to move the high-priority users to a
One particular DSP Nacks DCH setup 10 Start
different resource block, and tries again
times with cause
to allocate PIC configuration to the DSP a
"NotEnoughResources=10" or
number of times for 3 minutes. In case of
"AlreadyActivated_Allocated=22" within a
failure, Telecom rejects the received
20-minute period.
1. If the Extension
configuration System aModule
and indicate message is lost Start / Cancel
and is not regained
"Resource within 10
block occupied by minutes,
high priority
Telecom
users"._x000D_attempts to re-allocate cells to
the Master System Module without HSPA
capability. If any cells have been
1.Cell setup is rejected because either all Start / Cancel
successfully re-allocated to the Master
cells in the same LCG, having the same
System Module after the Extension
UARFCN are not mapped to the same
System Module having returned, the
PIC pool, or there is another cell in the
performance is not optimal, because its
same LCG with the same UARFCN
The
HSPA cell was not is
capability setnot
uputilized._x000D_
because no Start / Cancel
outside the PIC pool._x000D_
sufficient
2. BTS with number of Common
configured HSPA Control
is started
2.PIC pool configuration (new or updated)
Channel
with ESMProcessing
having outdatedSet (CCCH
software
is rejected if either all LCELs in the same
Processing
version and Set) licenses
software wasis not
update
LCG, having the same UARFCN do not
commissioned
performed fast on BTS. to take ESM into
enough
PSCR request
belong for
to the same setting neworHSPA
PIC pool a LCEL Start
use._x000D_
resources up is beingtoexecuted
that does not belong any PIC on pool has
3. ESM is
already hot-inserted
existing during
(inalready
terms runtime, but
ofassigned
being
a UARFCN that is to
HSPA
allocated is commissioned
in DSP only for MSM
any PIC pool fromSW theinternal
same LCEL's
(ESM was not present during
databases)resources.
LCG._x000D_
One of the Common Transport Channels
commissioning), so HSPA capacity usage Start / Cancel
3.Rel.
(PCH, 3FACH,
BTS only:
RACH) Tooismany cellsby
released have
RNC.
is not optimal._x000D_
PIC activated (number of RX of non-PIC
_x000D_
cells + 2x number of RX of PIC cells >
This fault is used only in FSMr2+FSMr2
48). For Fixed BB allocation due HW rel.
configurations.
At least one BBLCGAllocation
in BTS does not have Start / Cancel
1 and Fixed Pooling, this
enough
conditionresources
is checked forLCG-wide
the HS-RACH for LCGs
resource
located insteps Rel. 3commissioned
FSMs only. For with
a
"Minimum
Flexible BBnumber Allocationof HS-FACH
pooling, thisusers" or
the allocation
condition of dynamic
is checked resource step
The RX signal level isBTS-wide
higher than for defined
all Start / Cancel
for HS-FACH
cells._x000D_ failed. The fault is raised for
for given Radio Module. Defined
BTS. _x000D_
value:_x000D_
Radio Module rel1: -55 dBm_x000D_
For newer Radio Modules this parameter
is not defined._x000D_
If more than two PIC pools are Start / Cancel
commissioned for a shared LCG in case
of FSM rel3+FSM rel3, then Telecom
shall reject the whole PIC pool
configuration by reporting this fault.
Feature configuration in BTS is different Start / Cancel
than feature configuration in RNC
(Configuration parameters in BTS related
to the feature are not in line with feature
license or feature activation state in
This indicates a flash memory operation Start
RNC).
failure. If this fault continuously appears,
the flash chip might be broken.




The C-Plane Telecom SW does not Start

communicate with the C-Plane TUPC SW
because of a fault.
There is a buffer overflow caused by a Start / Cancel

traffic overload. The maximum capacity is
exceeded and some data is discarded.
The operating system (OSE) error occurs. Start

_x000D_
_x000D_
If only one FSP in BTS generates this
fault, there is a malfunction in_x000D_
An out of frame data error interrupt Start / Cancel
one of the FSP sub-modules. If all FSPs
received from the SWS ASIC._x000D_
generate this fault, there is a_x000D_
malfunction in the FSM._x000D_
The Antenna (RP3) link is down: the Start / Cancel

transmitter or receiver drops out of
synchronization.
High or low voltage on the external alarm Start / Cancel
line._x000D_
_x000D_
The user specifies the fault text during
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
line._x000D_
_x000D_
commissioning.
The BTS module properties data or Start
optical interface FPGA file is invalid or
missing. The FSP MCU SW file is invalid
or missing._x000D_
The BTS module properties data or Start
optical interface FPGA file is invalid or
missing. The FSP MCU SW file is invalid
or missing._x000D_
Communication with the application <x> Start / Cancel
failed. The application has not replied to
the message that has been sent/re-sent
to it.
The requested channel in the cell setup is Start / Cancel
not acceptable for the BTS hardware,
because of an incorrect frequency band
and/or a carrier spacing and/or the
number of carriers.
- The baseband bus related configuration Start / Cancel
of <x> was rejected by the HW, SW,
DSP, or LTX._x000D_
- The BTS detected a RF Module that
cannot be used without resetting the BTS.
The reference clock monitoring has Start / Cancel
The detected RF Module type differs from
detected a loss of signal in the reference
the previous one and the BTS is still
received from the FT.
inactive._x000D_
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.
The OCXO adjustment area has reached Start / Cancel
its limit value (5% of the total adjustment
area). The range for the DAC word is 0 -
4095.
The output signal of the OXCO has some Start
problems and one or more clock pulses
are missed.
The frame synchronization burst, SFN or Start / Cancel

SFCLK signal from the FCM/WSPF is
missing.
A request to retrieve the public IP Start / Cancel
address information of the FCM/FCT from
the FT fails, or transmission parameters
have not been commissioned or properly
set.
A request to retrieve the public IP Start / Cancel
address information of the FCM/FCT from
the FT fails, or transmission parameters
have not been commissioned or properly
set.
The FSM cannot start properly because Start / Cancel
the FSPs cannot be powered up in too
cold conditions.
Data or states are corrupted in the ATM, Start

or there are possible hardware or
transmission related failures.
The Masthead Amplifier (MHA) is not Start / Cancel

working properly. The received RF signal
level has decreased._x000D_
_x000D_
If both stages of the LNA on the uplink
The Masthead Amplifier (MHA) is faulty. Start / Cancel
path fail, the MHA switches the LNA to
The received RF signal level is
by-pass mode. In by-pass mode, the
decreased._x000D_
MHA has no gain but some loss. If a
_x000D_
single stage of the LNA fails, the MHA still
If both stages of the LNA on the uplink
Radio Module
has about (60W
a half of itsRRH)
normalor Filter
gain. (all
With Start / Cancel
path fail, the MHA switches the LNA to
others) has detected
an integrated MHA, the an fault
overcurrent on
might affect
the by-pass mode. In the by-pass mode,
the
bothantenna
main andline. The antenna
diversity line might
branches.
the MHA has no gain but some loss. If
be damaged (short circuit), or an antenna
only one stage of the LNA fails, the MHA
line device is causing an overload. All
VSWR
still hasvalue
aboutexceeds
a half ofthe definedgain.
its normal level. Start / Cancel
antenna line devices powered by the
The
Withantenna line isMHA,
an integrated mismatched
the faultormay
antenna line are out-of-order.
damaged.
affect both main and diversity
branches._x000D_
Radio Module (60W RRH)/the Filter (all Start / Cancel
others) has detected a VSWR value
exceeding the defined level. The antenna
line is slightly mismatched.
The filter has detected a malfunction in Start / Cancel
the LNA unit.
A filter has been unable to tune onto an Start / Cancel

appropriate sub-band properly (tuning
failure).
A filter has detected major failure (unit Start / Cancel

faulty) or RFSW lost connection with FF
unit.
Antenna tilting is not possible or might Start / Cancel
function incorrectly.




A hardware failure detected by an Start / Cancel

antenna line device. Usually, this is a
permanent fault (the hardware is broken).
The unit is in Download Mode State. Start / Cancel

Returned upon unsupported procedure
when in Download Mode.
A corrupted SW file in the FLASH is Start

detected. The unit cannot perform a
complete start-up.
The Extension System Module does not Start

receive the system clock.
Unsupported mixed sector configurations Start / Cancel

have been commissioned to one RF
module.
Supported mixed sector configurations
are defined in officially supported Flexi
Incorrect cell configuration for RF Start / Cancel
WCDMA BTS configurations.
Modules with different frequency. The
same cell is configured for two RF
Modules which are not at the same
frequency.
1) A possible faulty configuration with the Start / Cancel
Radio Modules connected to both the
master system module and intended
extension system module._x000D_
2) O&M master system module cannot be
determined automatically._x000D_
NOTE: This fault is not applicable in
FSMr3+FSMr3 configuration.
The module has been configured as a Start / Cancel
master System Module, but no Radio
Module is connected to it.
The heater control connection of the FSM Start / Cancel

is faulty, there is no heater, or the heater
is faulty.
The number of DSP units in the BTS is Start / Cancel

too small. For every three cells, there
must be at least one DSP present.
The Fault diagnostics rule file is missing Start

or its parsing has failed.
The Fault diagnostics rule file is missing Start

or its parsing has failed.
A dual PA RF Module has been replaced Start / Cancel

with a single PA RF Module, and it cannot
serve all cells commissioned to the RF
Module.
A fault in the Masthead Amplifier (MHA) Start / Cancel
has been detected. The fault probably
reduces the gain performance of the
MHA.
A fault in the Masthead Amplifier (MHA) Start / Cancel
has been detected. The fault completely
prevents the gain function of the MHA.
The device is not working properly, the Start / Cancel

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



An SRAM memory operation failure has Start
occurred. If this alarm appears
continuously, the SRAM chip might be
broken.
An SRAM memory operation failure has Start
occurred. If this alarm appears
continuously, the SRAM chip might be
broken.
The self test of the unit/module has failed. Start
The BTS has detected a resource that Start / Cancel

requires a license but no license exists or
is available.
The antenna line or antenna line device is Start

not properly configured that may be due
to any of the following reasons:_x000D_
- AL device type is unknown._x000D_
- AL device set-up fails, for example, due
An external filter is missing from the Start / Cancel
to protocol error or interoperability
antenna line.
problem_x000D_
- Other AL device unexpected behavior.
An autonomous internal delay Start

measurement has failed. The TCOM was
not able to measure the internal delay for
a cell for any of the RAKEs in a certain
BB unit.
During BTS startup, the System Module Start
has detected a new RF HW type that was
not previously used in this BTS
configuration. A System Module reset is
triggered to reconfigure the bus resource
allocation.
detected a loss of PPS signal in the
reference that is received from the GPS
receiver or from the SyncHub master
BTS.
detected a loss of the 2.048 MHz signal
that is received from an external
reference source, which is connected to
the Sync In interface of the System
The RF module configuration has failed Start
Module.
because of a hardware or software fault.
A critical configuration file is missing from Start

the RF module.
The FR Module SW has detected that a Start
non-critical configuration file is missing.
The System Module clock reference Start / Cancel

differs from the FR Module clock.
The baseband bus between the system Start / Cancel

module and the RF module is out of
synchronization.
The RF module baseband bus is Start / Cancel

incorrectly configured.
There is an error in the baseband or Start / Cancel

optical bus.
The RF Module TX path cannot be used. Start / Cancel
The TX output power adjustment has Start / Cancel

failed.
The RF module filter has measured a TX Start

power that is too low.
The RF module RX FR synthesizer is not Start / Cancel

locked.
The RF module is out of order because of Start / Cancel

a software or hardware fault.
The RF module temperature is too high. Start / Cancel
The FR Module cooling fan is not rotating Start / Cancel

at the specified speed.
The power supply has detected an Start / Cancel
overvoltage, undervoltage, or overcurrent
in the RF module.
The feedback signal to predistortion is too Start / Cancel

weak or is missing. The TX performance
is degraded.
The TX signal adjustment fails. Start / Cancel
During RF start-up, the temperature Start / Cancel

inside the RF module is too low. Module
heating is ongoing. Wait until the alarm is
canceled. This might take up to 30
minutes._x000D_
The permanent memory in the module is Start
_x000D_
corrupted and the module product code
During RF runtime, the temperature
or serial number is missing, or the module
inside the RF module is too low. A
product code is unknown.
problem might occur.
The RF module SW has detected a Start / Cancel
conflicting or corrupted configuration
data.
The FR Module power-on self-test failed Start

at start-up.
The RF lost the lock to the incoming Start / Cancel

clock.
The highest temperature exceeds the Start / Cancel

power decrease limit.
The FPGA software update has failed. Start
The Rel 2.0 or Rel 2.1 RF Module with Start

SW prior the implementation of the
RAN2312(Radio Interface Harmonization
in Rel 2.x) is connected to the system
module_x000D_
A shared (Medusa) FR is blocked. Start / Cancel
with optical interface 2. This conflicts with
the instructions given in the user guide. It
is advised that optical interface 1 be
utilized instead.
Radio Module cannot identify the used Start
fan type, or the fan is not installed.
One or more fans are not running. Start / Cancel
Fan(s) is(are) rotating more slowly than Start / Cancel

required.
Fan(s) is(are) rotating faster than Start / Cancel

required.
Validated module temperature is higher Start / Cancel

than the predefined maximum value
allowed.
The validated sensor temperature is Start / Cancel

higher than or equal to the predefined
value on the unit property file.
The validated temperature of any PA Start / Cancel

sensor is higher than or equal to the
predefined value on the unit property file.
Validated module temperature is greater Start / Cancel

than the predefined value on unit property
file. Relevant for Rel1 FR module only.
Increased bit error rate has been Start / Cancel

detected on the optical link to the radio
module resulting in LCV errors in
downlink baseband processing.
Abnormally high bit error rate has been Start
detected on the optical link to Radio
Module which results to a permanent
baseband processing failure. I/Q data
stream cannot be successfully processed
Antenna line has been autonomously Start
by FRM due to the burst of consecutive
disabled by FRM to protect the HW from
LCV errors.
high reflection conditions.
FR module has detected permanent RP3 Start / Cancel

routing collisions either in the downlink
(TX), or the uplink (RX) transmission
direction.
The Small Form Factor Pluggable (SFP) Start / Cancel
malfunction has occured or the SFP
module is not physically present (no
electrical connection exists). The SFP is a
part of the fibre cable package. _x000D_
The Small Form Factor Pluggable (SFP) Start / Cancel
malfunction has occured or the SFP
module is not physically present (no
electrical connection exists). The SFP is a
part of the fibre cable package. _x000D_
The incoming optical signal to the Small Start / Cancel
Form Factor Pluggable (SFP) is missing,
too weak, or the fiber cable has been
detached._x000D_
_x000D_
The fiber cable is experiencing Start / Cancel
The connection between the System
interference; data transmission is
Module and the RF Module (LTX,
faulty._x000D_
Antenna Filter, Antenna Line Device) or
_x000D_
between the Master System Module and
A physical connection failure between the
The RP3 channel
the Extension has lost
System the achieved
Module is broken. Start / Cancel
optical interface and the summing
frame synchronization
That might state.or secondary
concern primary
function has occured(possibly caused by
link.
bad circuit joints).
The RP3 or Ethernet buffering is not Start / Cancel

working and the buffer becomes full. The
optical device is malfunctioning. The fault
might be generated because of
synchronization problems or incorrect
initialization.
initialization.
initialization.
initialization.
The control message traffic between the Start / Cancel
initialization.
modules is malfunctioning.
The optical interface has detected a CRC Start / Cancel

error in the received synchronization burst
from the clock function. This fault appears
on the RX side.
Synchronization to the clock control unit Start
frame pulse has been achieved earlier
but it differs from the currently received
frame pulse. The internally generated
frame clock might have drifted.
The master frame in the received Start / Cancel
baseband bus frame is not in the correct
place, regarding the internally generated
master frame pulse. Either the frame has
been set in the wrong place (PI delay), or
A decoding error has been detected in Start / Cancel
the data itself is in the wrong place.
the baseband internal link. The data
packet is lost or the content is
corrupted._x000D_
_x000D_
There is a baseband bus address Start / Cancel
This situation is also triggered when the
mismatched in the summing. There are
links do not synchronize with each other.
two possible causes:_x000D_
_x000D_
A configuration error (two different
The frame alignment is lost or the frame Start / Cancel
baseband units functioning) - after an
burst has a CRC error when the System
acknowledgment, the fault
Module is working in extension mode.
returns._x000D_
_x000D_
The
Dataframe alignment
corruption on theisbus
lost -orappears
the frame Start / Cancel
burst has a unsynchronized
once when CRC error whendata the System
is sent
Module is working in extension mode.
by the baseband.
A new RP1 Frame Clock Burst (FCB) Start

burst/message has been received from
the RP3-01 interface while processing the
previous burst/message.
The clock crossing buffer underflow or Start
overflow in RX block and the received
data might be invalid. The fault is an
indication of either too large a clock drift
between the received signal and the
The SW update to the BTS has failed or Start
internal clock, or an incorrect RX rate
the BTS SW is corrupted. _x000D_
setting.
Baseband bus message multiplexing slot Start / Cancel

for the message is not possible to be
fulfilled.
Summing checks header of the Start / Cancel

messages to be summed. If the header is
not any of the allowed types, no summing
is performed, and an empty message is
sent instead.
Transmitter detected an RP3 message Start / Cancel
from a summing coincident with a
transmission rule.
The transmitter detected more data Start / Cancel
coming from a summing than the current
link rate can support.
The enumeration algorithm has detected Start

a permanent failure, preventing sRIO
system maintenance.
Congestion avoidance hardware of the Start

sRIO switches has been triggered.
_x000D_
BMU (Board Management Unit) product Start

data EEPROM of an extension board
(FSP) cannot be read out during a
connect event._x000D_
It has been detected that the host link, Start
which is used for the sRIO system
maintenance, is going down.
There is a signal processing (DSP) Start

related malfunction in the BTS. This might
affect the signal processor receiver
functionality processed by the alarming
unit/module.
SRIO error rate is too high. Start / Cancel
The Flexi BTS has detected an abnormal Start / Cancel

operation or a failure in the internal
functionality of the System
Module._x000D_
_x000D_
The FlexiBTS has detected an abnormal Start / Cancel
operation or a failure in the internal
functionality of the RF Module.
The BTS has detected an abnormal Start / Cancel

operation or a failure in the BTS
replaceable_x000D_
baseband unit.
The BTS has detected an abnormal Start / Cancel
operation or a failure in the BTS internal
baseband bus. The failure cannot be
pointed to a specific unit/module but there
are several possible fault sources.
The BTS has detected abnormal Start / Cancel
operation or a failure in an optical RP3
interface between two modules. The
failure cannot be attributed to a specific
module but there are several possible
fault sources.
The internal temperature of the RF Start / Cancel
Module or System Module exceeds the
threshold value, or the ambient
temperature of the module(s) is beyond
the specified limits.
One or several fans in the same fan Start / Cancel
group are rotating more slowly or faster
than required, they are not rotating at all,
or the RPM information is not available for
the fans. The reason for this fault can be
Some of the commissioning parameters Start / Cancel
too low supply voltage or a broken fan.
are either missing or faulty or there is a
mismatch between them.
There is an incompatibility problem in the Start / Cancel

BTS HW/SW versions or the HW/HW
configuration. Another possibility is that
there is a mismatch between the BTS
configuration and the RNC/Flexi Direct
This BTS fault indication is generated if Start / Cancel
RNC parameters.
the reference clock monitoring function of
the BTS does not receive the highest
configured synchronization reference
signal or if all the synchronization
A software update to a unit/module or Start / Cancel
reference signals are missing. The BTS
subassembly has failed, or a corrupted
fault is not generated if the highest
SW file has been detected in the FLASH.
configured synchronization source is
present, no matter what the lower level
The
source System
statusesModule or the device itself
are._x000D_ Start / Cancel
has
_x000D_ detected an abnormal operation or a
failure
_x000D_ in the antenna line device.
Background information:_x000D_
There is a fixed synchronization
The connection to the BTS transport priority Start / Cancel
list in the FlexiBTS:_x000D_
submodule is lost.
_x000D_
-Priority 1: PPS (Pulse Per Second)
signal connected to the Synchronization
1)Too many LCRs
Input interface (Sync areIn) commissioned
of the Systemto Start / Cancel
one
Module. RF Module.
Normally the PPS signal is
2)Too
generated many byLCRs
the GPS are commissioned
receiver._x000D_ to
ESM
_x000D_
-Priority
The BTS2:detected externalan 2.048MHz
Extension signal
Module Start
connected to the Sync
as a capacity enhancement._x000D_ In
interface._x000D_
_x000D_
_x000D_
The BTS detected a RF Module that
-Priority
cannot be 3: used
the reference signal coming
without resetting the BTS.
The
from feature:_x000D_
the integrated transmission unittype Start / Cancel
The RF module might be the same
-(FTM).
expires in one Month or one Week if the
but the _x000D_
optical fiber connection topology
fault
_x000D_ severity is minor;_x000D_
or optical connection line rate are
-Normally,
has already expired
all the if thesources
FlexiBTS fault severity
changed during BTS run-time. If theare
RF
is
not major._x000D_
in use at the same time (it depends
Due to atype
Module TX path
differsfailure,
from the MIMO (Multiple
previous one Start / Cancel
Note:
on the The feature
network name might
planning be shown
Input
then Multiple
recommissioningOutput) is and
also BTS
functionalityrequiredin the
as truncated in During
configuration). RNC, OMS the andstart-up,
BTS NetAct
cell
(e.g.related
dual RF to Module
the faulty is TX is out with
replaced of order.
alarm
the user interfaces.
available sources are checked
triple RF Module or vice versa)._x000D_
against
_x000D_the reference source list in the
BTS
BTS commissioning
reset is required, fileif and
the LTEdeviations
system
regarding the missing
module type has changed or LTE highest priority
system
source
modulegenerate
is first time a fault.
detected Duringandruntime
the
operation,
module type theisBTS fault than
different functionality
default. runs
autonomously - notices also
added/vanished sources which are
missing from the commissioning
file._x000D_
_x000D_
The source for the FTM (which is the
There is not enough HW capacity to Start
support the commissioned number of
Local Cell Groups (LCG).
BTS monitors the Start / Cancel

FSP/FBB/WSPF/WSMF PLL (Phase-
Locked Loop) lock status and PLL locking
failures.
The BTS has detected a communication Start / Cancel
problem with the GPS receiver.
The platform SW rejected the baseband Start

bus related to the SRIO configuration for
the Faraday core. _x000D_
Connection to the DSP submodule has Start / Cancel

been lost or the submodule reports an
error.
Failure occured when writing parameter Start

to the Radio Module was requested.
Failure occurred during reading Start

parameter from the Radio Module.
Internal Maximum Transfer Unit (MTU) Start

configuration failed on FCM or FSP/FBIA.
A corrupted SW file in the FLASH is Start

detected. The unit cannot perform a
complete start-up.
Commissioning file download has not Start

started from BTS Site Manager nor from
NetAct during autoconfiguration.
The commissioning file is missing, or an Start / Cancel

incorrect commissioning file has been
detected during a BTS startup as follows:
"Validation failed because of incompatible
data"
Generation of target Id has failed and as Start
a result, the correct validation of license
files in the BTS is not possible. BTSOM is
restarted and, consequently during
startup, all the license files are deleted
from the BTS._x000D_
If the trial period has expired, all optional
features are either disabled or their
capacity is reduced to the basic (not
licensed) level.
FSM is the radio master for RFSW but Start / Cancel
recognizes that RFSW already has
another radio master defined. The fault
might arise temporarily when LTE
assumes the role of radio master but
FSM notices a shared radio module is Start / Cancel
should disappear autonomously after LTE
connected to different OptIF connectors
hands back the role of radio master to
on peer system modules.
WCDMA.
A unit or module or an IP address Start

initialization has failed.
Retrieving the list of all parameters Active

available in the Radio Module memory
failed. The list is retrieved in order to
check whether it contains the license
targetId parameter.
A filter has not been able to tune on an Start / Cancel
appropriate sub-band properly_x000D_
(tuning failure).
An alarm message has been received Start / Cancel

from the antenna line. The antenna line is
faulty.
An alarm message has been received Start / Cancel

from the antenna line device. The
antenna line operation is degraded.
SW download to an antenna line device Start

failed due to incorrect checksum or file
format.
SW download to an antenna line device Start

failed due to incorrect checksum or file
format.
Connection to a unit belonging to the BTS Start / Cancel

configuration has been lost or FSP
cannot be detected.
Echo test of Baseband (SRIO) link Start

between FSP boards was not successful.
NetAct Licence Manager did not respond Start / Cancel

to the verification request. TargetId
verification was not possible.
The TX carriers served by the affected Start / Cancel
antenna lines are disabled. This causes
the operation of the related cells to be
degraded or deactivated. As a result the
power transmitted by the Power Amplifier
An unsupported module has been Start
in Radio Module is reduced for the sake
detected in the System Module. Typically,
of protecting the Power Amplifier against
this happens when the System Module
HW failure that might be caused by
SW in use does not support the module.
operation under excessive VSWR value
Not enough(antenna
conditions RP3-01 line
linksimpedance
connected Start
between
mismatch).FSM and FR. Commissioned
cells cannot be routed through the
existing RP3-01 links.
Response is not received or response is Start
received with unsuccessful status for
SRIO multicast configuration related
messages.
FSP is undergoing a cold reset. Start
Radio Module or Filter (all others) has Start

detected an overcurrent on RS485
IUANT_x000D_
port. Some antenna line device is causing
overload. Depending on HW
The highest validated temperature value Start / Cancel
implementation, antenna line devices
on FSP board exceeds the threshold
powered by the RS485 IUANT and/or
value.
powered by the antenna line are out of
order._x000D_
The parallel RP3-01 links towards one
_x000D_ Start / Cancel
radio module have
The overcurrent was too large mutual
detected on RS485
length
IUANTdifference
port. Some(more thanline
antenna 60 device
meters).is
causing overload or there is a shortcut on
the
Fanport. Antenna
speed linefor
is too low devices powered
successful Start / Cancel
by the RS485 IUANT port are out of
detection. Detection is attempted again
order.
after Fan.Test.Timer expires.
Long fiber between FSM and furthest FR Start

detected but the feature status in SCF is
FALSE. _x000D_
- Fiber length 0.2 km - 15 km:
(actDistributedSite15 = False)
Temperature on the FSP board exceeds Start / Cancel
the critical threshold value.
Fan(s)is/are not running although the Start / Cancel

control is higher than 0.
Speed of the fan(s) is/are deviating too Start / Cancel
much from the required control.
Fan(s) is/are running faster than required. Start / Cancel
Summing service release from reset Start

failed.
4082:_x000D_ 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._x000D_
4082:_x000D_ Start
_x000D_
Source unit has reached the maximum
4083:_x000D_
Source unit requests SW fallback
source unit cannot successfully finish
because of a critical problem that
start-up after the SW update._x000D_
4082:_x000D_
occurred in start-up after the SW update, Start
_x000D_
Source unit has reached
that is configuration data the maximum
migration
4083:_x000D_
failed._x000D_
source
_x000D_ unit cannot successfully finish
start-up
4085:_x000D_after the SW update._x000D_
No fixed BB
occurred allocation
in start-up based
after LCGupdate,
the SW Start / Cancel
_x000D_
Transport SW on the FSM._x000D_
source unit
commissioned
that to the
is configuration data migration
4083:_x000D_
indicates a need for software fallback.
failed._x000D_
_x000D_
4085:_x000D_
Reliable
occurredmessage
in start-updelivery
after theservice is not
SW update, Start
Transport
able SW onan the
toconfiguration
deliver source
internal unit to a
message
that is data migration
indicates
recipient a need
(FSP or for software
FSM), fallback.
and sends an
failed._x000D_
asynchronous
_x000D_ notification to the message
sender about the unreachable recipient.
4085:_x000D_
File System access operation like File Start
Transport
System mountingSW on the source
or file unit failed.
opening
indicates a need for software fallback.
BTS has detected RF module power Start

cycle failure and is trying to recover from
the failure during BTS reset procedure.
BTS reset lasts longer due to additional
actions performed by BTS in order to
Summing service default configuration Start
recover from faulty situation.
has failed
FSP does not support the requested BTS Start

configuration.
[FSMr2] FSP reset during BB reset Start
recovery failed.
[FSMr3] FSP warm reset recovery failed.
During the SW update, it has been Start

detected that configurations of active and
passive SW in HW unit are the same.
Active and passive SW configurations are
compared:_x000D_
SRIO connection between system Start / Cancel
- before SW download,_x000D_
modules is not working.
- during SW activation, before active and
passive SW switch,_x000D_
- during start-up.
Power feeding for the given Radio Start / Cancel
Module has been switched off by the user
from BTS Site Manager remotely.
FSP is shut down. Baseband reset is Transient

needed to proceed.
The master system module has lost Start / Cancel

optical connection to the peer system
module.
Poor GPS antenna installation. Start / Cancel
The GPS receiver is running a site/self Start / Cancel

survey.
There is no accurate position stored in Start / Cancel

EEPROM.
The receiver is used in a stored position, Start / Cancel

but then is moved to a new position.
GPS receiver has detected that one or Start / Cancel

more EEPROM segments were corrupted
at reset, and its/their factory default
settings need to be restored.
Unsupported Rx carrier bandwidth has Start
been assigned to LCR.
Unsupported Tx carrier bandwidth has Start
been assigned to LCR.
Unsupported carrier separation in Dual- Start / Cancel

Carrier configuration is assigned to the
Radio Module.
An attempt to modify a field value in Transient

Antenna Line Device failed because the
field is read-only.
SW file validation against its signature Start / Cancel

failed.
Phase synchronization has been Start / Cancel

commissioned at the btsSyncMode, but
neither_x000D_
PPS nor ToP reference clock has
become available during startup timeout.
Calls are not possible through the Start / Cancel
_x000D_
affected cell(s) because of a vertical
sectorization license missing.
Vertical TX tilt angle is enforced to 0 Start / Cancel

degrees because of a tilting per carrier
license missing. Calls are possible
through the affected cell(s), but the
capacity and performance might be
Vertical RX tilt angle is enforced to the Start / Cancel
decreased.
same value as TX tilt angle because of a
tilting per TX/RX license missing. Calls
through the affected cell(s) are possible,
but the capacity and performance might
This fault is a notification that collecting Start / Cancel
be decreased.
log prints into ramdisk is activated in the
BTS. Activation may decrease the BTS
performance.
Feature is not activated as needed. Start / Cancel
[FSMr3+FSMr2] Flexible BB pooling is in Start / Cancel

use or no LCGs assigned to ESM in
fixed_x000D_
BB pooling._x000D_
[FSMr3+FSMr3] ESM has no LCGs
The used SFP does not support the Start / Cancel
assigned in fixed BB pooling or ESM is
required RP3-01 line rate between the
hot inserted_x000D_
system module and the extension system
in runtime but not found in HWF.
module.
Failure occured during reading of targetId Start / Cancel
parameters from the Radio Module.
FSM-internal (including DSP expansion Start / Cancel

cards) baseband bus link synchronization
has failed. Frame sync state has not been
reached, or link timing is incorrect.
BTS has had an uncontrolled reset due to Transient
a reason indicated in the fault name.
_x000D_
The following reset causes (#) are
possible: _x000D_
VSWR major or VSWR minor value set Transient
"FSM watchdog reset": System overload
during commissioning is out of range.
_x000D_
"FSM spurious reset": Reset reason
detection failed_x000D_
The
"FSMBTS detected
spurious a purereset":
container a single RXSW Start / Cancel
BTS
cells configuration
unexpected for which
reset. Exact thereason
reset IRC
Receiver
detection functionality
failed. unavailable.
RM module fiber cabling is incorrect and Start / Cancel

equivalent fiber cabling configurations
exist. The affected RM modules are GAIA
based RRHs & FRs.
MHA was unexpectedly set to bypass Start / Cancel
mode.
Connection to NetAct has to be restarted Start

as target ID has been recovered.
This fault indicates that:_x000D_ Start / Cancel

1)the absolute value of estimated phase
error of BTS, which is in
holdover,_x000D_
has exceeded the limit of 5 us,_x000D_
Physical memory supervision has Start / Cancel
or_x000D_
detected that memory usage has
2) BTS is more than 6 hours in holdover
exceeded 90%(FCM/FCT)/98%(FSP).
mode what means that
estimated_x000D_
Non-correctable
phase error valuebitmay toggling
be noterror is
credible. It Start
detected
is assumedin the critical
in this caseDSP memory.
that_x000D_
real absolute value of phase error is
bigger than 5us._x000D_
Fatal error of DSP HWAPI SW has Start
occured._x000D_
_x000D_
If FSP in the BTS generates this fault,
there is a malfunction in_x000D_
a corresponding FSP sub-
module._x000D_
If all FSPs generate this fault, there is a
malfunction in the FSM.
Fatal error of DSP Application SW has Start
occured._x000D_
_x000D_
If FSP in the BTS generates this fault,
there is a malfunction in_x000D_
BTSOM has triggered GPIO reset for the Start
DSP on purpose._x000D_
module._x000D_
_x000D_
If FSP in BTS generates this fault, there
malfunction in FSM.
is a malfunction in_x000D_
The transport part of the WBTS has been Start / Cancel
reset._x000D_
module._x000D_
Note:_x000D_
1.FSMr2 supports the following cause for
malfunction in FSM.
the reset:_x000D_
A change to the BTS IP settings has been Start
_x000D_
received from TRS Manager. The user
"trs unknown cause " : not yet evaluated
has to confirm the changes after the last
or not determinable_x000D_
BTS IP settings have been given. The
"trs power-on reset" : Cold start
confirmation is needed so that the BTS IP
DSCP
_x000D_ $D signalled but not configured. Start / Cancel
settings are taken in use through a BTS
$D
"trs specifies watchdogthe first mismatch
reset" : System DSCP
reset.
value.
overload_x000D_
"trs startup failure" : Failure during startup
The
_x000D_ combination of RNC and NodeB is
The alarm is raised if the BFD service is Start / Cancel
misconfigured
"trs with regard to quality of the
not available failure":
software anymoreSoftware on the BTS for all
service
failure_x000D_ configurations.
BFD sessions belonging to that BFD
"trs
group. management reset": Reset triggered
by management interface_x000D_
This
"trs fallback" alarm is raised if routing entries
: Fallback Start / Cancel
exceed
executed_x000D_ the maximum number(1200)in
forwarding
"trs Hardware table.
Failure": Hardware
Failure_x000D_
"trs
Losskernel reset"
of frame. It is :not
kernel panictoresulting
possible carry Start / Cancel
in
traffic sudden
on thereset_x000D_
interface referenced in the
_x000D_
alarm text. All other transmission alarms
_x000D_
related to this signal are suppressed.
FSMr3 supports the following cause for
No
the signal is received on the interface
reset:_x000D_ Start / Cancel
Probable causes for STM-1/STS-3c
referenced
_x000D_ in the alarm text. All other
interfaces:
transmission
"trs alarms "related to this signal
- theunknown SDH/SONET causeinterface : not yet evaluated
receives
are
or suppressed.
not determinable_x000D_
frames that have an incorrect frame
"trs
A dead
pattern power-on
peerand
(A1 reset"
was A2 : Cold
detected
bytes) in one of the Start / Cancel
Probable
start_x000D_ causes for PDH interfaces:
IPsec associationsof
- the configuration ofthe
theframing
FTM. (STM-1
-"trs a cable is cutreset"
watchdog or there : is no cable
System
or STS-3c) on the far-end interface does
connected
overload_x000D_ to the interface
Possibly
not match the configuration on the
-"trs thesoftware
electricalfailure":
signal is excessively
Software
-interfacea cable is cut or there
referenced is no cable
A
attenuatedloopback
failure_x000D_ has beeninconfigured
the alarm texta
by Start / Cancel
connectedtoo low antoinput
-management the interface
level
-"trs themanagement
port at the application.
connected
reset": Reset far-end node
triggered
- the signal is excessively attenuated
is
by switched
management off interface_x000D_
-Probable
the port at the connected
cause for E1 interfaces: far endThe node is
-"trs transmit
spuriousandreset"
receive cablesreason
: Reset are mixed
switched
interface offthe
at far end is not configured
up
detection
The failed_x000D_
to beSFP module
a framed E1detected
interface.in the interface Start / Cancel
_x000D_
connectors does not comply with the
Probable
2. causes
The "$date" for Ethernet interfaces:
security
Probable causeformat
requirements.for T1isinterfaces:
local time-stamp
The
-(GMT+/-xx:xx)
a cable is cut .orE.g: there is no cable
2014-04-12
interface at the far end is not configured
connected
00:51:26 to the interface
GMT+0530_x000D_
to be a framed T1 interface.
-_x000D_
the electrical signal is excessively
attenuated
3. There iscause
a bugfor in JT1
the older version of
Probable interfaces: The
-PLD(2.3
the portandat the connected
earlier), which far endin
result node is
interface at the far end is not configured
switched
wrong off reason getting reported from
to be areset
JT1 interface.
the PLD (E.g. Instead of "power-on reset"
the bit corresponding to "Element
manager or command-line reset" is
getting set), This bug is fixed in latest
FTIA PLD version 2.5.
Loss of ATM cell delineation. The network Start / Cancel
interface receives frames whose ATM
cells cannot be recognised. It is not
possible to carry traffic on the interface
referenced in the alarm text.The interface
Primary and secondary timing source lost. Start / Cancel
could be E1/T1/JT1 interface number or
The WBTS is running on internal clock or
IMA group number.
in hold-over mode and no timing signal is
sent.
Probable causes:
One
- the of the synchronisation
far-end frames do not have sources ATM in cell
the Start / Cancel
The first and second synchronisation
configured
mapping priority list is unavailable.
sources from the configured priority list
This
- the can far endbe thedoes primary
not insert or the idlesecondary
cells
are unavailable. On failure, the WBTS
clock
- theresource. are disturbances in the traffic of
switches automatically to the next clock
the
Thisphysicalalarm transmission
shall be raised link in question Start / Cancel
source in the priority list. if a
In the alarm:
configuration fulfills these
Protocol can be PDH, SDH, Timing over
conditions:_x000D_
Probable cause: The transmission links
Packet (ToP) and Synchronuous
(MinUDPPortCESoPSN
selected for clock source>are (MinUDPPort
faulty. The -
ethernet.
supported
reason can PWs))_x000D_
be alarms on the interfaces
This alarm is raised if a CES pseudowire Start / Cancel
AND_x000D_
(for example, LOS, LOF
tunnel
Unit Number is in 'Up' state,
is optional: butornoAIS).IP packets
(MinUDPPortCESoPSN <= (MinUDPPort
were
-For PDH, received SDHonand theSynchronous
tunnel in the last
+ (max_number_of_user_connections -
second.
Ethernet, Unit number is 0 or 1.
1))_x000D_
-It
The is alarm
not present
is raised for ifTiming
the CES Over Start / Cancel
AND_x000D_
The alarm is not raised in case the CES
Packet(TOP).
pseudowire
At least one is PW in 'Up' state, but the
is configured
pseudowire tunnel is in 'Init' state.
number
(irrespective of received
if the PW packets in the CES
is administratively
The
pseudowire interface valuethan is optional:
in use or outisofless use)._x000D_ 10% relative to
In
-the ForcasePDH thatthe allvalue
CES pseudowires of the
_x000D_ expected numberrange depends
of packets for 1on
This
tunnel
the alarm is raised
are taken
hardware unit out ifofthe
type: use packet
1..16 by theloss Start / Cancel
second.
Note : _x000D_
condition
operator,
- For Synchonuous for
alsopackets
no "PW oftunnel
Ethernet the given down"
the CES
value alarm
supportedPWs
pseudowire equals:_x000D_
persists
is
range raised even
= 1..3 when for the more
CES than 1
pseudowire
The - alarm
FTIB, is not be
FTLB: raised, if the CES
4_x000D_
second
tunnel
-pseudowire
For SDH isinstill
ingress._x000D_
the configured.
value is 1
- FSM-r3/FTIF: is in 'Init' state.
8_x000D_
_x000D_
-This
It isalarm
not present forifTiming over Packet. Start / Cancel
- FTFB: is raised
16 the BTS cannot
The packet loss condition is defined as
update the Certificate
follows:_x000D_
Revocation_x000D_
The CES over PSN pseudowire function
List (CRL). Please refer PDDB parameter
is capable to detect lost and misordered
CERTH::CRLInfo:
A loopback
packets. Theis sequence
requestednumber for an Ethernet
in the Start / Cancel
CRLUpdateFailureReason_x000D_
interface
control word either locally
is used foratthese
the BTS or the
purposes.
for failure reasons.
Link
The CES OAMover clientPSN of the BTS is setfunction
pseudowire into
loopback
shall reorder mode by the remote
misordered packets. Link OAM
peer.
Misordered packets that cannot beOAM Start / Cancel
On an interface for which the Link
reordered, shall be discarded
functionality was switched on, no Link and treated
as lost._x000D_
OAM PDUs were received during the
_x000D_
period specified in configuration
Note:This
parameter alarm linkLostTimeis locally raised
(2..10 by BTS
seconds,
A Link OAM
indicating PDU containing
transmitted packets a are
critical link Start / Cancel
step 1 second).
event
somehow flag notwasreceived
receivedby onpeer
the_x000D_
side.
Ethernet
Trigger isinterface.
the reception The alarm
of packets is raised
with R-
with
bit set thetofirst detection of the_x000D_
1._x000D_
flag._x000D_
A malfunctioning of the SFP transceiver Start / Cancel
_x000D_
was detected.
The following critical link events are
The SFP has reported a transmission
possible:_x000D_
fault condition and has disabled the laser
- Critical Event: either an Errored Symbol
transmitter.
Period Event, an Errored Frame_x000D_
Event an Errored Frame Period Event or
an Errored Frame Seconds
Summary_x000D_
Event was detected._x000D_
- Dying Gasp: either the local or the
remote peer has a fatal error
and_x000D_
is about to restart._x000D_
- Link Fault: the local peer has detected a
A TWAMP session has gone down. Start / Cancel
The alarm notifies if the OSPF neighbor is Start / Cancel

down.
The alarm cause can be: OSPF Neighbor
down for destination address 1.2.3.4
or OSPF Neighbor up for destination
Alarm indication signal on the Multiplexer Start / Cancel
address 1.2.3.4
Section. The SDH interface receives an
MS-AIS (Multiplexer Section - Alarm
Indication Signal). This signal is
generated by an intermediate SDH device
Remote defect indication (RDI) on the Start / Cancel
in the forward direction because it detects
Multiplexer Section (MS). This alarm
a problem in its receive signal.
occurs when the equipment at the far end
of a bidirectional multiplexer section
All other transmission alarms related to
connection has detected an error
Excessive
this signal are bit error rate. The measured bit Start / Cancel
suppressed.
condition on the signal that it is receiving.
error rate exceeds the threshold value of
The RDI indicates a serious fault in the
BER-3
Probable (10E-3).
cause: there is a transmission
received signal of the far-end equipment.
problem somewhere in the intermediate
Probable
network causes:
and AIS is thesentAdministrative
instead of user Start / Cancel
Loss of Pointer
Probable cause:for The far end has active
-traffic.
the signal level is too low (optical
Unit.
alarms This
on alarm occursinterface
its receiving when the(such SDH as
connectors or cables are dirty, electrical
interface
LOS, LOF, receives
TIM-RS, frames
AIS-MS, thatAIS-AU,
have an
connectors or cables are corroded)
incorrect
LOP-AU).Administrative Unit (AU) pointer.
- the specified maximum length of the
Alarm
cable is indication
exceeded signal on the Start / Cancel
this administrative unit are suppressed.
Administrative
- the connectorUnit. is notThe SDH interface
properly connected
receives
to the unitan AU-AIS (Administrative Unit -
Probable cause: there are disturbances in
Alarm Indication
- the receiver Signal).
or the far endThis signal is
transmitter
the traffic on the link in question.
generated
has failed by an intermediate SDH device
High Order Path Unequipped. The path Start / Cancel
in the forward direction because it detects
signal label byte (C2) and the path trace
a problem in its receive signal. All other
byte (J1), and BIP-8 byte (B3) in the SDH
transmission alarms related to this signal
path overhead (POH) all have the value
are suppressed.
zero. The path is unusable for traffic
Path Payload Label Mismatch on the Start / Cancel
transport.
High Order
Probable Path.There
cause: The SDH is a interface
transmission
receives frames on the
problem somewhere VC-3/VC-4
in the that
intermediate
Probable cause: the unequipped VC-
have
networka Path
and Payload
AIS is sent Label that does
instead not
of user
3/VC-4 comes from a VC-level cross-
correspond
traffic. to the "ATM" (Asynchronous
Remote defect
connection node indication on the Highis
and the VC-3/VC-4 Start / Cancel
Transfer Mode) signal. The path is not
Order Path (VC-3/VC-4).
not connected anywhere in This alarm
that node.
intended for ATM traffic transport.
occurs when the equipment at the far end
of a bidirectional VC-3/VC-4 connection
Probable cause: The Signal Type
has detected an error condition on the
Loss of multiframe.
Identifier on the far end The interface
interface has not Start / Cancel
signal that it is receiving. The far-end
referenced
been configured in theto alarm text has lost the
be "ATM".
equipment signals this remote defect in
multiframe alignment.
the signal that it transmits.
Probable cause: the interface type has
Alarm
The RDI indication
indicatessignal is received.
a serious fault in This
the Start / Cancel
not been configured to meet the framing
signal
receivedis generated
signal of thebyfar-end
an intermediate
equipment.
of the interface at the far end. For E1
PDH device in the forward direction
interfaces, the configuration of the far-end
because
Probable itcause:
detects
Thea problem in itsactive
far end has
node should be E1 Multiframe.
receive
alarms on signal.
its receiving interface (such as
LOS, LOF, TIM-RS, AIS-MS, AIS-AU,
All other transmission
LOP-AU, alarms related to
TIM-HP, UNEQ-HP).
this signal are suppressed.
Probable cause: There is a transmission

problem somewhere in the intermediate
network and AIS is sent instead of user
traffic.
Remote defect indication. It is sent by the Start / Cancel
intermediate or the far end equipment,
because it detects a serious fault in the
received signal.
Loss of an IMA frame. The loss of an IMA Start / Cancel
Probable cause: The far end has a LOS,
frame was detected in one link of the IMA
LOF or AIS alarm on its receiving
group. The far-end IMA link is not part of
interface.
an IMA group.
Link out of delay synchronisation. A Start / Cancel
LODS defect is reported when the link
this IMA link are suppressed.
differential delay between the link and the
other links in the group is higher than the
Probable causes:
tolerable link differential delay.
Remote failure indication.
- the configuration of the IMAAn IMA-related
group is Start / Cancel
remote
incomplete defect has been detected. A Loss
or faulty
Probable causes:
of IMA link
- there (LIF) or Link
is disturbance onout
theofline
delay
- the configuration of the IMA group is
synchronisation (LODS) alarm is active at
incomplete or faulty
the far end of the IMA link.
Far-end
- there istransmit
disturbancelink unusable.
on the lineThe IMA Start / Cancel
link
- theisdifferential
not yet in andelayIMAofgroup.
the IMA The alarm
links
Probable causes:
is typically to
belonging raised
one IMAonly group
temporarily
is too during
high
- disturbance on the line
IMA configuration and disappears when
- physical link defect
the configuration has been completed.
Far-end
- loss of receive
IMA frame link unusable. The IMA Start / Cancel
There are usually other IMA-related
link
- lossis of
notdelay
yet insynchronisation
an IMA group. The alarm
alarms active at the same time.
is typically raised only temporarily during
IMA configuration and disappears when
Probable cause: IMA configuration is
the configuration has been completed.
Far end group start-up. This alarm is
incomplete. Start / Cancel
There are usually other IMA-related
raised when the far end indicates that it is
alarms active at the same time.
in the start-up phase. The alarm is
typically active only temporarily.
Probable cause: IMA configuration is
Configuration
incomplete at abort state. interface.
the far-end This alarm is Start / Cancel
Probable cause: The IMA group at the far
raised when the far end tries to use
end is not yet up and running.
unacceptable configuration parameters.
Far end configuration abort state. This Start / Cancel
alarm is raised when the far end reports
Probable cause: The IMA group
unacceptable configuration parameters.
configuration is wrong (for example, the
IMA versions are incompatible).
Insufficient links. There are less operable Start / Cancel
IMA links in the IMA group than the
Probable cause: The IMA group
minimum number of IMA links required.
configuration is wrong (for example, the
The IMA group referenced in the alarm
IMA versions are incompatible).
text may not be able to carry all required
Far end insufficient links. The far-end IMA Start / Cancel
traffic.
group reports that there are less IMA links
in the far-end IMA group than required by
Probable causes:
the parameter Minimum number of IMA
- IMA links within the IMA group are out of
links.
Group
order timing mismatch. The far-end Start / Cancel
transmit
- there are clock
not mode
enough is different
IMA linksfrom the
Probable causes:
near-end
configuredtransmit clockgroup
for the IMA mode.atThethe traffic
far
- IMA links within the IMA group are out of
of
end the IMA group does not function
order
properly.
- the value for the parameter Minimum
- there are not enough IMA links
number of links is set to be too high
configured for the IMA group
The IMA group might not be capable of
- the value for the parameter Minimum
carrying traffic on the IMA group
number of links is set to be too high
referenced in the alarm text.
Probable cause: Too large differential

delay between the IMA links.
Unit missing. The slot has been Start / Cancel
configured to hold a unit but the plug-
in_x000D_
unit is not physically present in the
slot._x000D_
The IPCP statemachine is in the Closed Start / Cancel
_x000D_
or Initial state and cannot reach the
Probable causes:_x000D_
Opened state within 100 milliseconds.
_x000D_
- the unit has been configured but not
The alarm is raised if the LCP state
detected_x000D_ Start / Cancel
machine
- the unit on port $Pand
is broken is intherefore
the Closed notor
Initial state and cannot reach the Opened
detected_x000D_
state
- the unit withinhas 100beenmilliseconds.
configured but some
other unit is detected_x000D_
PPP interface is not operational either Start / Cancel
NOTE:
when allunit thevariable should
links in the be replaced
bundle_x000D_
by appropriate
of MLPPP are notHWavailable
names configured
or SLPPP link
(unitTypeConfigured)
is not available._x000D_ during runtime
reporting.
The SSCOP link controlled by this STC is Start / Cancel
down. The alarm text specifies the slot,
port, VPI and VCI number in $IF
variable._x000D_
_x000D_
This Alarm is triggered when overall Transient
Probable causes:_x000D_
system memory exceeds the configured
- the peer (RNC) releases the
threshold_x000D_
connection_x000D_
_x000D_
- the link goes down because the peer
Note: This Fault is applicable only for
The
(RNC) feature
does that is referenced
not respond withininthe
the Start / Cancel
FSMR2
alarm text has been configured
TIMER_NO_RESPONSE without
period._x000D_
installing
- the link was a valid license._x000D_
never established_x000D_
_x000D_
- problem on the ATM layer_x000D_
Probable
-Theproblem cause:
the A valid license that
alarmon physical
is triggered layer_x000D_
whenever a service Start / Cancel
allows
-OAM the operation
incomplete or faulty ofconfiguration
the feature is ofnot
error related to the transmission of
available
AAL2 in in the
the RNC WBTS._x000D_
Continuity Check Messages (CCM)
_x000D_
persists on a given Ethernet interface as
This BTS fault can be displayed in the
soon as one of the error conditions below
When
followings a MEP receives a valid ETH-AIS
variants:_x000D_ Start / Cancel
occurs._x000D_
frame
Licence and AIS is0000000598,
missing enabled, it shall trigger
Additional
_x000D_
an
2E1, AIST1,alarm containing the following
JT1 interface_x000D_
The following alarms are
information:
Licence missing 0000000616,
defined:_x000D_
-receiving interface
IMA_x000D_
Five consecutive failed login attempts to Transient
_x000D_
Licence-MDmissing
level 0000000767, UBR+ for
theMDL_MISMATCH,
1) BTS have been priority 5 (highest
Iub -Source
User MAC address
Plane_x000D_
performed.The_x000D_
priority): A CCM is received with an MDL
Licence
source missing
$S variable 0000000768,
can be BTSSM ATMor over
that is lower than the highest configured
NOTE:
Ethernet Infor
FSMr2,
BTS pure number interface
_x000D_
WebUI.
one in the BTS and does not not
match
A
arerequested (eg.certificate
usedmissing
Licence 1,2,3). Butcould
0000001191, for FSMr3 be any Start / Cancel
Timing
of the
retrieved configured
from the ones._x000D_
certificate repository
unit
Overtypes,
Packet interface
for is provided
BTS_x000D_ as:
Example:
server CCMcertificate
fault levelauthority
- prio 5 cause
Licence(RA)
"module typeorname"
missing EIF
0000001687, 2nd(CA).
MDL_MISMATCH_x000D_
A requested certificate could not be
"interface
Flexbus number".
interface_x000D_
Note:
renewed ForfromMDL_MISMATCH
the0000001688, cases, it may
certificate authority
Licence
Thebe missing
Pseudowire has beenthe Collocation
detected
not
(CA). possible to display local to be Start / Cancel
Flexbus interface_x000D_
down in the ingress direction by using the
MDL_x000D_
Licence
BFD missing 0000001689, Ethernet
wherefunction.
the fault was detected._x000D_
over FlexiHopper radio_x000D_
_x000D_
Licence missing 0000001515, BTS
_x000D_
Synchronous Ethernet_x000D_
2) MAID_MISMATCH, priority 5: A CCM
Licence missing 0000001788, QoS aware
is received with an MDL that is configured
Ethernet switching_x000D_
in the BTS, but with a MAID that does not
Licence missing 0000001847, IP over
match any MA configured in the BTS on
ML-PPP on E1/T1_x000D_
this MDL._x000D_
Licence missing 0000001850, Ethernet
Example: CCM fault level 5 prio 5 cause
OAM in Flexi BTS _x000D_
MAID_MISMATCH_x000D_
Licence missing 0000001849, Fast IP
_x000D_
Rerouting and OSPF_x000D_
3) MAID_MISMATCH, priority 5: A CCM
Licence missing 0000001905, IP
is received with matching MDL and MAID,
A Pseudowire has been detected to be Start / Cancel
down in the egress direction by using the
BFD function. The alarm is raised when
the BFD message from the far end
contains the diagnostic code 'Control
The alarm is raised if the alarm is Start / Cancel
Detection Time Expired' and the
enabled, the BFD state is not
corresponding ingress alarm is not
AdminDown, and no BFD packet is
present.
received at the local end during the
detection time.
The alarm is raised if the alarm is Start / Cancel
enabled, the BFD state is not
AdminDown, the BFD packet from the far
end contains the diagnostic code =
'Control Detection Time Expired' AND no
This alarm indicates that there is a Start / Cancel
ingress alarm is present.
mismatch between BTS configuration and
auto-negotiation result.
BTS shall report this alarm if the NTP Start / Cancel

server is not accessible or if the NTP
server cannot be used.
Note: Filtering time is related only to
startup and starting the alarm
An alarm will be raised if PoE is enabled Start / Cancel
not for clearing the alarm.
and failing (for example, in case of a
missing or short end device).
Power is enabled by management, but
cannot be applied to the powered device
The BTS raises a "Vendor BTS certificate Start / Cancel
for any reason.
is about to expire" alarm when the Vendor
BTS certificate is about to
expire._x000D_
_x000D_
The link flapping alarm shall be raised on Start / Cancel
The period of notification in advance is
the Ethernet interface, if the link status
configurable and the same as for
changes twice (DOWN-->UP, UP--
CA_x000D_
>DOWN) during the duration of the link
certificate expiry._x000D_
flapping prevention timer.
NE stores trust anchors for its own trust Start / Cancel
_x000D_
If the link goes up and down again during
chain
1 day and for peers.
... 4999 When
days with own or
default 90any
that flapping period, the link flapping timer
trust anchors are about to expire/expired
days._x000D_
shall be restarted.
this alarm is sent._x000D_
At least one of the sessions in MLPPP Start / Cancel
bundle has gone down.
In case the incoming SSM is not anymore Start / Cancel

received for a certain time period
(configured via 'ssmTimeout' parameter)
this an alarm is raised. _x000D_
_x000D_
This alarm is raised when the received Start / Cancel
Note: The interface numbering shall be
SSM indicates lower clock quality (e.g.
similar to ETHLK._x000D_
"do not use" or "EEC") than
E.g: DN:SYNC-1/STPG-1/STPU-1-4 for
required._x000D_
unit 1,interface 4.
_x000D_
Note: The interface numbering shall be
similar to ETHLK._x000D_
E.g: DN:SYNC-1/STPG-1/STPU-1-4 for
unit 1,interface 4.
detected a loss of ToP reference clock
signal received from the master clock
behind $IP.
- The eNB does not receive a reply from
SW does not support the detected HW Start / Cancel
ToP Master within a certain time (5 sec)
unit type.
upon it has sent a sync request message
- The eNB receives from ToP Master a
Probable causes:
granted message rates (sync message
This
rate, alarm
delay is triggered
message if during
rate), the 15not
that does Start / Cancel
- The system module's SW version is too
min.
match measurement
the requested window,
rate bythe
eNBframe
old
loss ratio, far-end, or near-end, exceeds
- Supported HW variant not present in
the configured threshold._x000D_
system module
_x000D_
This alarm is triggered if during the 1 min. Start / Cancel
The alarm shall include the following
measurement window, the average two-
information: _x000D_
way delay measured exceeds the
- Alarm cause: 15 min frame loss ratio
configured threshold._x000D_
threshold exceeded. _x000D_
This alarm is triggered
- Measurement if during
type (1ended orthe 15
2ended) Start / Cancel
min. measurement
[represented by flmwindow,
$f]_x000D_when either
- Alarm cause: 1min delay threshold
the near-end
- Alarm source:or MA_x000D_
the far-end one-way
exceeded. _x000D_
delay
- Remote variation
MEP exceeds
MAC address. the
- Alarm source:MA_x000D_
threshold._x000D_
[represented by mac $m]
-This alarmMEP
Remote is triggered once the new
MAC address. Start
configuration
[represented by filemac
is rejected and
$m]_x000D_
M-Plane connection is established with
- Alarm cause: 15 min one-way delay
fallback configuration as a result
variation threshold exceeded. _x000D_
of M-plane recovery action.
The base
- Alarm stationMA_x000D_
source: is currently capturing IP Start / Cancel
It shall be visible until next site reset.
traffic
- Remotetowards
MEPaMAC localaddress.
port or into a file on
the base station.
[represented by mac $m]_x000D_
if_x000D_
the traffic capturing is happening
towards a local port, port and destination
The power values in the cell configuration Start / Cancel
mac address needs to be provided.
data sent by the RNC are out of range.
Port values can be LMP or < HW
MODULE NAME >-<PORT ID>.
i.e LMP or FSM-EIF1, FSM-EIF2 or FTIF-
There
EIF1 is not enough common channel Start
capacity to set up any cells to the BTS
because Efficient Baseband or Full
Baseband HSDPA is allocated (the last
FSP card is fully reserved).
Telecom configuration file(s) are invalid, Start
missing, or not accessible.
Synchronization between FCM and Start

FSP/FBB is lost._x000D_
_x000D_
The license status has changed to valid Start / Cancel

and a BTS reset is needed to take the
license into use.
Secondary optical link between the Start / Cancel
System Module and the FR Module is
lost.
If a message is not routed, an interruption Start / Cancel

is generated._x000D_
_x000D_
Considered normal when Faradays are
starting up and RP3 sync has been done.
SRIO connection between system Start / Cancel
modules is not working._x000D_
SRIO connection between the system
module and a sub-module (FBBx) is not
working.
The fault is raised by Nyquist (Common Start
Channel Device or Mixed Channel
Device) when all Bit Co-Processors used
by this unit are lost.
Telecom slave configuration or Start
registration failure. Unit RNW
configuration failure. Telecom RNW
reconfiguration failure._x000D_
_x000D_
The RNC has requested more PRACH Transient
FlexiBTS: _x000D_
preamble signatures than the BTS can
support for the requested cell range.
failure_x000D_
UltraSite, MetroSite, MetroSite 50, Triple-
failure_x000D_ Start
mode:
_x000D_
Note that depending on the fault source,
There is a fault
unit status mightinrelate
the WAMeitherprocessor
to the state
SFN
of interruptcarrier
particular or theresource
SFN is not on being
FRTriple-
UltraSite, MetroSite, MetroSite 50, Start
updated
module in FSP
or the WSPC
board MCU.
on FCM, and might
mode:
not be in line with the state of the source
There
HW is a MCU failure in the WAM or the
unit._x000D_
There is a fault in the WAM processor
ATM
_x000D_loop test at start-up has failed.
SFN interrupt or the SFN is not being
The output voltage is too low or too high.
Or_x000D_ Start / Cancel
updated in the WSPC MCU.
FlexiBTS:
_x000D_
Usually
UltraSite, the reason for the fault 50,
is the unit
There is aMetroSite,
MCU failure MetroSite
in the WAMTriple-
or the
itself
There
mode: but
is in some
such
WSP cases
a fault
unit to the
in the
WAM reason
FSM thatcan
allocation the
ATM loop test at start-up has failed.
be
SFN theis
failure. unit
not that
beingthe WPS feeds.
updated
_x000D_ in the FSP
The WEA unit external interface Start / Cancel
MCU.
_x000D_
connectors
FlexiBTS: are connected incorrectly, or
If a short circuit occurs
UltraSite/EUBB: Faraday in the
unit fedWSPF
unit, it
there is a shot circuit in the +5toVCD.
may affectfailure.
allocation the WPS and the "Output
There is such a fault in the FSM that the
Voltage Fault" alarm is generated.
SFN is not being
The cabinet cannotupdated in the FSP
be identified by its Start
MCU.
product code (or object ID). The problem
is probably in the WID id.
Carrier candidates are commissioned for Start

each cell (not WTR/LTX specific).
The baseband bus synchronization Start / Cancel
towards <x> failed.
The output signal of the OXCO is missing Start / Cancel

and the FCM/FCT/SCR cannot deliver the
30.72 MHz System Clock required by the
other units.
The phase measurement cannot be Start / Cancel
performed in the active WSC or WMC.
The BTS detected a resource needing a Start / Cancel

license. However, no license exists or is
free.
Carrier candidates are commissioned for Start

each cell (not WTR/LTX specific).
Summing service release from reset Start

failed.
The VCXO does not get correct control Start

voltage from the PLL filter of the clock
cleaner. This may happen because of an
unsuccessful clock recovery in the optical
interface because of a missing or
RP3 or Ethernet buffering is not working Start / Cancel
degraded input signal.
and the buffer becomes full. The optical
device malfunctions. The fault might be
generated because of synchronization
problems or incorrect initialization.
BTS software does not support the Start
commissioning file downloaded to the
BTS.
In case of license "Distributed Site 15" or Start / Cancel

"Distributed Site 40", the long fiber
between FSM and the furthest FR is
detected but the required license is
missing.
Unit Status Unit Status Attributes
Degraded,Out of order Alarming fan = out of order, fan

group = degraded
Out of order Alarming fans = out of order, fan

group = out of order
Working
Out of order
Working
Out of order
Out of order
Out of order
Out of order
Out of order
Degraded
Degraded
Degraded
Out of order
Out of order,Working Out of order

(UltraSite/EUBB)_x000D_
_x000D_
Working (FlexiBTS, UltraSite,
MetroSite, MetroSite 50, Triple-
Working
mode)
Working
Working
Working
Working
Working
Out of order
Out of order
Out of order
Out of order
Working
Working
Out of order
Degraded
Degraded,Out of order Degraded (FF)_x000D_

Out of order (Otherwise)
Out of order
Working
Out of order
Out of order
Out of order
Out of order
Working
Working
Working
Working
Out of order
Out of order
Out of order
Working
Degraded Degraded (At least one RX power

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

given cell is working properly
Degraded
Working
Degraded
Degraded
Degraded
Degraded
Degraded
Out of order
Degraded
Out of order
Out of order
Out of order
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Working
Out of order,Working Working when there were

problems with files in SW package
but BTS is still
operational._x000D_
Out of order when the problems
Degraded,Out of order,Working Working when there were
prevent BTS from reaching
problems with files in SW package
operational state.
but BTS is still
operational._x000D_
_x000D_
Out of order
Degraded when there were
problems with rules missing (1866)
or parsing (1867): BTS is still in
operational state, but no
Out of order recoveries may be performed.Out
of order when the problems
prevent BTS from reaching
operational state.
Out of order
Degraded,Working Working:_x000D_
- some other reference clock is
available_x000D_
Degraded:_x000D_
- any reference clock source is not
Out of order
available
Degraded
Out of order
Out of order
Degraded
Degraded
Out of order
Out of order
Out of order
Out of order
Degraded
Out of order,Working Out of order: if

EFaultId_VSWRThresholdTuningO
ngoingAl=1810 is not active for the
same AL._x000D_
_x000D_
Degraded
Working: if
EFaultId_VSWRThresholdTuningO
ngoingAl=1810 is active for the
same AL
Out of order
Out of order
Out of order
Degraded
Degraded
Degraded
Degraded
Degraded
Degraded
Degraded
Degraded
Out of order
Out of order
Out of order
Degraded
Working
Working
Degraded
Out of order
Out of order
Out of order
Degraded Degraded
(MinorTMAFault)_x000D_
Out of order
Degraded
Degraded
Degraded
Degraded
Degraded
Degraded
Degraded
Degraded,Working Working _x000D_

- The license for an active feature
is missing but due to ongoing trial
period the feature is functioning
normally. _x000D_
Degraded
- The license is missing and the
trial period is unavailable but
feature is still active. _x000D_
_x000D_
Working Degraded _x000D_
- License is missing for an active
feature and trial period is not
available. Feature is disabled.
Out of order
Out of order
available_x000D_
Degraded:_x000D_
available
available_x000D_
Degraded:_x000D_
Degraded,Out of order [AAS]: Degraded if less than a half
available
of ActiveElements faulty._x000D_
[Otherwise]: Out of order

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

ActiveElements having faulty TX
HW._x000D_
[Otherwise]: Out of Order
Degraded
Out of order
Degraded,Out of order Degraded only for AAS if not all

ActiveElements (in RX path) inside
AAS faulty._x000D_
Otherwise Out of Order._x000D_
Degraded,Out of order [AAS]:Degraded only for AAS if
less than half of ActiveElements
inside_x000D_
AAS are faulty._x000D_
Degraded,Out of order [AAS]: [Rel1 HW] Degraded if less
than a half of ActiveElements
faulty. [Rel2 HW] Degraded if less
than a half of TX HW resources
faulty or all faulty TX HW
Out of order Not all fans failed: Module =
resources in same
Degraded, Fan group = degraded,
polarisation._x000D_
Single (failed) Fan = Out of
[AAS, RAN 2580 soft recovery
Order_x000D_
licence active]: Degraded if a half
All fans failed: Module = Degraded,
or less than a half of TX HW
Fan group = Out of Order
resources faulty._x000D_
[Otherwise]: Out of Order
Out of order
Degraded
Degraded
Out of order,Working Out-of-order during FR start-

up_x000D_
Working during FR runtime
Degraded
Degraded
Out of order

[Otherwise]: Out of order
Degraded
Degraded
Working
Out of order
Working
Degraded,Out of order Not all fans failed: Fan group =

Degraded, Module =
Working_x000D_
All fans failed: Fan group = Out Of
Order, Module = Degraded
Degraded,Working Module = Degraded, Fan group =
degraded_x000D_
[AAS]: Working
Working
Working
Degraded,Out of order [AAS]: Degraded if less than half of

ActiveElements faulty._x000D_
Degraded,Out of order Degraded - validated temperature

of any PA sensor is greater than or
equal to Tdanger (when any
TX/RX resources are available on
alarming FRM)_x000D_
Working
_x000D_
Out of order - dangerously high
temperature occurs longer than
tT+danger and PA is turned off
Degraded (when no RX/TX resources are
available on alarming FRM)
Out of order
Out of order
Working
Out of order
Out of order
Out of order
Out of order
Out of order
Degraded
Degraded
Degraded
Degraded
Degraded
Working
Degraded
Out of order
Out of order
Out of order
Degraded
Out of order
Out of order
Out of order
Degraded
Out of order
Out of order FSM becomes degraded when any

FSP is out of order_x000D_
FSP becomes out of order if at
least one Faraday is out of
order_x000D_
Out of order FSM becomes degraded when any
FSM becomes out of order if all
FSPs are out of order
order_x000D_
Out of order
FSPs are out of order
Out of order
Out of order
Out of order
Out of order
Out of order
Out of order
Degraded
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Out of order,Working Working (FSM)

Out of Order (LCR)
Out of order
Degraded,Working Possible unit statuses can be

raised, corresponding to two faults
of different severity, depending on
the time left before expiration:
_x000D_
Working
- Working: in case of expiration in
one month or one week _x000D_
- Degraded: in case of expiration at
the moment of fault raising
Out of order
Out of order
Working
Out of order
Out of order
Working
Working
Out of order
Degraded
Working
Out of order,Working Out of order: when the problems

prevent the BTS from reaching the
operational state._x000D_
Working: when there were
problems with files in the SW
Working
package but the BTS remains
operational.
Degraded
Degraded
Out of order
Working
Out of order
Out of order
Degraded
Working
Working
Out of order
Degraded
Degraded,Working Working - BTS is trying to verify

the targetId, but licensed
functionality is not affected for trial
period time._x000D_
_x000D_
Degraded - BTS is trying to verify
the targetId and licensed
functionality has been disabled
after trial period time had passed.
Out of order Out of order
Out of order
Out of order
Out of order
Out of order
Degraded
Out of order
Out of order
Working
Out of order
Out of order
Degraded,Out of order Not all fans have failed: alarming

fan = out of order, fan group =
degraded_x000D_
All fans have failed: all fans and
fan group = out of order
Degraded Alarming fan = degraded, fan
group = degraded
Degraded
Out of order
Out of order
Out of order
Out of order
Working
Out of order
Out of order
Working
Out of order
Out of order
Out of order
Out of order
Out of order
Working
Out of order
Working The master system module works

properly.
Working
Working
Working
Working
Working
Out of order
Out of order
Out of order
Working
Out of order,Working
Out of order
Out of order Out of order._x000D_
Degraded
Degraded
Working
Degraded,Out of order
Degraded
Out of order
Degraded
Out of order
Working
Working
Working Working - IRC Receiver is not

available for a pure single RX cells
configuration but the BTS remains
operational._x000D_
Out of order
Out of order
Out of order
Working
Working
Critical
Out of order
Out of order
Out of order
Minor
Major
Major
Critical
Minor
Critical
Critical
Major
Minor
Critical
Major
Major
Minor
Major
Major
Major
Major
Major
Major
Major
Major
Critical
Major
Warning
Critical
Major
Major
Critical
Critical
Critical
Critical
Major
Major
Major
Major
Critical
Critical
Major
Minor
Minor
Minor
Critical
Critical
Critical
Critical
Major
Critical
Critical
Critical
Major
Major
Warning
Major
Major
Major
Warning
Major
Critical
Critical
Major
Major
Major
Major
Critical
Major
Major
Major
Major
Minor
Minor
Minor
Critical
Minor
Minor
Minor
Major
Minor
Degraded
Working
Out of order
Out of order
Working
Working
Degraded,Out of order One of the links is faulty/broken or

is getting incorrect
messages._x000D_
FSM becomes degraded when any
Out of order
order_x000D_
Out of order FSPs are out of order
Out of order
Working
Out of order
Out of order
Out of order
Working
Degraded
Degraded
Out of order
Out of order
Degraded
Degraded,Out of order Out of Order (MHA) - a license

required for MHA to work is not
available at MHA's
startup._x000D_
Degraded (RET) - changes of
Degraded
angle are not allowed to due to
lack of tilting license (cells may be
set up inproperly).
Out of order
Out of order
Degraded
Out of order
Out of order
Effect Reported Alarms
If the redundant fans cannot cool the BTS 7652 BASE STATION NOTIFICATION
sufficiently, overheating might occur and a
temperature fault might be generated from
the unit/module.
Fans are rotating too slow and the module 7652 BASE STATION NOTIFICATION
temperature is too high or fans are rotating
too fast.
The BTS operation might be decreased. 7652 BASE STATION NOTIFICATION
If the FSP update fails, the BTS capacity 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
drops. If the optical interface FPGA SW
update fails, communication to radio
modules does not work and the BTS is not
operational._x000D_
This fault does not immediately affect the 7652 BASE STATION NOTIFICATION
_x000D_
operations of the BTS, but it is a notification
that the BTS frequency deviates from the Iub
reference. The BTS master clock tuning
continues despite the alarm, but because
The module in question is out of use. This 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
the BTS master clock adjustment is quite
alarm cancels all active alarms for the same
slow to filter the instabilities of the Iub
module.
interface, it takes some time (even several
hours) before the BTS operations start to be
BTS is not operational.
affected. 7650 BASE STATION FAULTY
If the fault source are all FSPs in the master 7650 BASE STATION FAULTY
system module, the BTS is not
operational._x000D_
If the fault source is FSP some cells are
faulty._x000D_
_x000D_
operational._x000D_
faulty._x000D_
BTS capacity might decrease (BASE 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
_x000D_
STATION OPERATION DEGRADED) if the
reporting unit is FCM/FCT on the ESM or
some FSPs._x000D_
The BTS might be completely out of order
(BASE STATION FAULTY) if the reporting
unit is FCM/FCT on MSM or all FSPs.
Signaling and calls made through the related 7651 BASE STATION OPERATION DEGRADED
cell(s) do not work.
The RNC NBAP starts link re-establishment 7651 BASE STATION OPERATION DEGRADED
procedures and keeps on trying until it either
succeeds or when the link is
removed._x000D_
_x000D_
The telecom SW does not operate on the 7651 BASE STATION OPERATION DEGRADED
Signaling and calls made through the related
Telecom Master WAM, and thus, the WAM
cell(s) do not work.
is not operational._x000D_
_x000D_
Signaling and calls made through the related
The resources provided by the unit cannot 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
cell(s) do not work._x000D_
be used, which means that some features
_x000D_
might not work._x000D_
The user data cannot be used in the related
_x000D_
cell(s), but the WAM can still work as a
If the fault is reported for the FR module, the
Requested
Telecom Master SW version
WAM. can not be installed 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
BTSOM does not know the real FR module
due to the limitations of the running SW
state; consequently, the BTS SM keeps the
version.
FR LED display disabled (grayed). The
reason for the FR LED status inconsistency
No
is thereal time is available.
restriction of the RP1 Alarms, logs, and 7652 BASE STATION NOTIFICATION
communication
all
onlyreports
to SWinclude an incorrect
management time. in case
procedures
of an SW mismatch situation. Thus, it is not
possible to align the RF LED and BTS SM
LED
The BTS display status._x000D_
continues its operation with the old 7652 BASE STATION NOTIFICATION
_x000D_
file.
If the fault is reported for Extension System
Module, the ESM unit LED in BTSSM is gray
as BTSOM does not report LED color to
The
BTSSM BTS- continues
unit statusitsis operation
unknown (inwithcase
the of
old 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
software.
incompatible software version,
communication between Master System
Module should be reduced to minimum,
start-up
If the SWofdownload
incompatible unitHW
for any (Extension
unit has 7652 BASE STATION NOTIFICATION
System Module) should be halted
failed, the eNB continues to operate and only
with the
SW update
currently shouldSW
installed be allowed).
version._x000D_
_x000D_
If the SW activation has failed for FCM/FCT
If the SW download for any HW unit has 7652 BASE STATION NOTIFICATION
in the master FSM, the eNB continues to
failed, the eNB continues to operate with the
operate with the currently installed SW
currently installed SW version._x000D_
version._x000D_
_x000D_
_x000D_
If the SW activation has failed for FCM/FCT
The
If thebattery backup unit
SW activation fails is
forpartly
otherorHW units, 7652 BASE STATION NOTIFICATION
in the master FSM, the eNB continues to
completely
(for example, in use.
an RF The intelligent
unit) then theshutdown
eNB
operate with the currently installed SW
operation
restarts and has started. with
operates If thethe
mains
new power
SW is
version._x000D_
not restored,
version. If thethe
eNB cells are shut down
is integrated to NetAct
_x000D_
according
after to the predefined
the shutdown
automatic recovery parameters.
SW update,
The
If thecell
SW activationisfails
started as part
for other HW thethe 7653 CELL FAULTY
of units,
eNB restarts
intelligent and
shutdownoperates with the
(for example, an RF procedure.
unit) then the eNB
previously installed SW version.
restarts and operates with the new SW
version. If the eNB is integrated to NetAct
after the automatic recovery SW update, the
eNB restarts and operates with the
previously installed SW version.
Cell shutdown is started as part of the 7653 CELL FAULTY
intelligent shutdown procedure.
The BTS does not send alarms that are 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
related to the blocked unit or module to the
network management system (NMS). Alarm
sending to the BTS Site Manager is always
enabled. The alarm cancellations are always
The BTS does not send any alarms that are 7653 CELL FAULTY
sent to the NMS._x000D_
related to the blocked cell or the units
_x000D_
commissioned to the blocked cell to the
Phone calls cannot be established through
network management system (NMS). Alarm
the blocked unit or module.
sending to the BTS site manager is always
The BTS does not send alarms to the 7650 BASE STATION FAULTY
enabled. Alarm cancellations are always
network management system (NMS) when
the BTS is blocked. Alarm cancellations are
_x000D_
Calls through the blocked cell are
_x000D_
The BTS is to
transferred operational.
another cell. New phone calls 7652 BASE STATION NOTIFICATION
All cells are disabled.
cannot be established through the blocked
cell.
Since it is not possible to use the faulty FSP 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
in the configuration, the BTS capacity
decreases or the BTS becomes faulty.
The default values are used for the cell. The 7651 BASE STATION OPERATION DEGRADED
cell operation might become degraded.
Depending on the reported severity, the BTS 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
capacity might decrease (BASE STATION
OPERATION DEGRADED, CELL
OPERATION DEGRADED, CELL FAULTY)
or the BTS might not be operational at all
(BASE STATION FAULTY).
capacity might be decreased (BASE
STATION OPERATION DEGRADED, CELL
OPERATION DEGRADED, CELL FAULTY)
or the BTS might not be operational at all
The cell is disabled. 7653 CELL FAULTY
(BASE STATION FAULTY)._x000D_
_x000D_
For resources that are not in use (not
commissioned), the lack of support_x000D_
The gain control
is reported feature
by a minor is lost alarm
severity possibly
(BASE 7653 CELL FAULTY7654 CELL OPERATION DEGRADED
generating an interference to the network.
STATION NOTIFICATION).
_x000D_
_x000D_
The NBAP common measurement message
The affected FCM unit is not operational. In 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
is incorrect because of missing
the event of an FSP fault, the channel
measurement data from the RF module.
capacity is lost and the cell(s) might become
unavailable. In case of an FR, the
associated cell(s) become(s) faulty.
Handing traffic over to another cell might not 7652 BASE STATION NOTIFICATION
work.
The affected cell state remains unchanged. 7655 CELL NOTIFICATION
The affected cell state remains unchanged. 7655 CELL NOTIFICATION
The cell setup is rejected. 7652 BASE STATION NOTIFICATION
Calls are not possible through the affected 7653 CELL FAULTY7654 CELL OPERATION DEGRADED
cell(s) (7653 CELL FAULTY)._x000D_
Calls are possible but the cell capacity and
performance might be decreased (7654
CELL OPERATION DEGRADED).
The cell setup has succeeded but the cell 7653 CELL FAULTY7654 CELL OPERATION DEGRADED
state is disabled.
Depending on the reported severity, BTS 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
capacity might decrease (BASE_x000D_
STATION OPERATION DEGRADED) or
BTS might not be operational at all (BASE
STATION FAULTY).
The minimum HSUPA capacity, which is 7652 BASE STATION NOTIFICATION
based on the commissioning parameters, is
not fully guaranteed. The HSUPA resource
handling still works dynamically in addition to
the partially reserved minimum capacity for
Cell capacity is decreased. 7654 CELL OPERATION DEGRADED
the HSUPA.
Cell capacity is decreased. 7654 CELL OPERATION DEGRADED

This fault prevents the BTS from functioning 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
correctly._x000D_
_x000D_
Some baseband processing resources are
not working or the BTS is not operational.
DSP unit restart 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
BTS HSUPA Capability is degraded in the 7651 BASE STATION OPERATION DEGRADED
cell where the Parallel Interference
Cancellation (PIC) feature was
active._x000D_
cell, where the Parallel Interference
Cancellation (PIC) feature was
active._x000D_
capacity might decrease (7651 BASE
STATION OPERATION DEGRADED) or the
BTS might not be operational at all (7650
BASE STATION FAULTY).
The performance of the BTS is not optimal 7651 BASE STATION OPERATION DEGRADED
because its HSPA capability is not fully
utilized.
Malfunctioning cell setups or rejected new 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
PIC pool configurations are ignored by
TCOM.
Not enough CCCH Processing Set licenses 7661 BASE STATION LICENCE NOTIFICATION
commissioned to set up cell.
FSP is not operational. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
Cell is temporary degraded, all connected 7654 CELL OPERATION DEGRADED

UEs are informed that the cell is degraded.
All ongoing calls are still possible, but UE
cannot establish the new one.
HS-RACH is not possible at least in one 7652 BASE STATION NOTIFICATION
LCG.
Radio Module is restarted. Incoming calls 7654 CELL OPERATION DEGRADED

may be dropped.
cells where the Parallel Interference
Cancellation (PIC) feature was active.
_x000D_
Functionality related to the reported feature 7661 BASE STATION LICENCE NOTIFICATION
is not available in BTS.
The BTS memory operations (for example, 7651 BASE STATION OPERATION DEGRADED
software download and parameter updates)
are unstable.
are unstable.
are unstable.
are unstable.
are unstable.
The BTS is not functional while in this faulty 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
state.
This fault has variable consequences. Calls 7651 BASE STATION OPERATION DEGRADED
might be cut off and, in worst cases, cells
might be disabled.
The BTS capacity decreases or BTS is out 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
of order. The Digital Signal Processing
(DSP) is not working correctly.
If this fault is cancelled more than 4 seconds 7651 BASE STATION OPERATION DEGRADED
after fault appearance, then no effect. Card
functionality is still degraded, but unit status
is working._x000D_
_x000D_
The BTS is not operational or the capacity is 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
If this fault is active for more than 4 seconds,
degraded.
this means SWS ASIC HW problem, and the
digital signal processing (DSP) does not
work correctly. BTS capacity is permanently
decreased.
For example, with the intelligent shutdown,
the WPA/WMP and the local cell resources
are blocked to minimize the power
consumption. Therefore, the battery backup
can keep the AXU unit up and running
longer than the other BTS units.
Depending on the reported severity, the fault 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
situation might have no impact on the
operation (BASE STATION
NOTIFICATION), the BTS capacity might
have decreased (BASE STATION
OPERATION DEGRADED) or the BTS
might not be operational at all (BASE
STATION FAULTY).
have decreased (BASE STATION
Some operations inside the BTS are being 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
interrupted. Depending on the fault source,
the BTS or cell operation is degraded or
STATION FAULTY).
faulty._x000D_
_x000D_
The BTS capacity possibly decreases. 7653 CELL FAULTY
Depending on <x>, some processing 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
resources, some cells, or the whole BTS
might be out of order.
Tuning does not follow the external 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
reference._x000D_
_x000D_
Clock tuning is halted and the BTS
continues its operation based on the internal
The system clock frequency starts to drift 7650 BASE STATION FAULTY
oven oscillator._x000D_
and the air interface frequency accuracy
_x000D_
starts to degrade. The BTS might work
The air interface accuracy of 0.05ppm is
properly for a few days without an external
kept for at least 24 hours. Within that time,
reference but the network performance
The BTScan
the BTS canwork
operate properly
properly but for
themonths
networkor 7651 BASE STATION OPERATION DEGRADED
might start to gradually decrease.
even a year ifmight
performance withinstart
the 5% margin area, but
to gradually
eventually
degrade. the DAC value reaches the
adjustment limit (0 or 4095), and the OCXO
cannot follow the synchronization reference
The BTS is not operational. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
signal beyond the limit. Assuming that even
in this phase the BTS reference signal has
correct accuracy (meaning the alarm
indication is real), the BTS air interface
The
startsBTS canfrom
to drift function properlyvalue
the correct for some
(after 7650 BASE STATION FAULTY
time. Thethe
reaching BTS is not
limit 0 oroperational.
4095), and after a
while the 3GPP accuracy limits are not met.
Even in that phase, the BTS might still be
operational but the system performance
might drop, affecting, for example,
handovers.
The BTS is not commissioned or integrated 7651 BASE STATION OPERATION DEGRADED
to the network. The BTS cannot be
accessed or configured remotely.
The O&M Iub connection to the RNC cannot

The BTS is not commissioned or integrated 7651 BASE STATION OPERATION DEGRADED
be established without the public IP
to the network. The BTS cannot be
addresses of the FCM and RNC.
accessed or configured remotely.
Transmission connections cannot be
The O&M Iub connection to the RNC cannot
FSM cannotto
established reach the operational
the RNC state.
autonomously when 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
be established without the public IP
the transmission information is missing.
addresses of the FCM and RNC.
Transmission connections cannot be

The connection
established to RNC
to the the transmission
autonomously is when 7650 BASE STATION FAULTY
broken. The BTSinformation
the transmission is not operational.
is missing.
If the MHA is faulty, the RX performance is 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
degraded. The cell size might be reduced
(7654 CELL OPERATION
DEGRADED)._x000D_
No impact on system (7652 BASE STATION
If the MHA is faulty, the RX performance is 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
NOTIFICATION).
degraded. The cell size might_x000D_
be reduced (7654 CELL OPERATION
DEGRADED)._x000D_
No impact on the system (7652 BASE
The antenna line is not operating correctly. 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
Cell capacity is decreased.
The cell is disabled if all of its critical radio 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
resources are affected, or the cell operation
is degraded if the part of the cell's resources
is affected, but the cell still has critical
resources that are working._x000D_
The output power at the antenna is 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
_x000D_
decreased and the antenna is not working at
Downlink signal transmission on the given
the optimum level.
antenna line is disabled, and the
corresponding FR transmitter is unusable.
The RX path operating performance is
_x000D_ 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
decreased.
_x000D_
Note that overall FR module state is not
affected, since the fault is caused by
external
The signal phenomena on antenna
path is unusable. The line
cells(e.g.
using 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
disconnected antenna or broken
the faulty unit might not work. ALD). RF
HW and its subsystems are not affected by
the fault despite some functions of FR
module (e.g. transmitter on the alarming
The signal
antenna path
line) is unusable.
cannot be usedThe cellsas
as long using
the 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
the
faultfaulty
remainsunit active.
might not_x000D_
work.
The BTS capacity possibly decreases. 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
The antenna line device is not working 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
properly. The cell operation is degraded.
The device is out of use. 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
The unit might be started with an old SW 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
version and is therefore not compatible with
any other units.
The Extension System Module is not 7651 BASE STATION OPERATION DEGRADED
operational. The BTS capacity possibly
decreases.
cell(s) (7653 CELL FAULTY).
Calls are possible but cell capacity and
performance may be decreased (7654 CELL
OPERATION DEGRADED).
cell(s) (7653 CELL FAULTY).
performance may be decreased (7654 CELL
The BTS capacity decreases, and cell(s) 7651 BASE STATION OPERATION DEGRADED
might remain down.
The BTS is operational. 7652 BASE STATION NOTIFICATION
Heating from the heating element is not 7652 BASE STATION NOTIFICATION
available. The module temperature might not
reach the working level or might reach it very
slowly.
The BTS capacity drops, cell(s) may be 7651 BASE STATION OPERATION DEGRADED
inactive.
The BTS does not operate. 7650 BASE STATION FAULTY
The BTS does not operate. 7650 BASE STATION FAULTY
The BTS capacity drops. 7653 CELL FAULTY
The MHA gain is decreased. The cell 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
performance may be decreased.
The MHA gain is decreased or a loss might 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
even be produced. The cell
performance_x000D_
is decreased._x000D_
Some antenna line device functions might 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED765
not work properly.
not work properly.
not work properly.
not work properly.
The BTS functionality is degraded and/or 7651 BASE STATION OPERATION DEGRADED
resources are unavailable.
The BTS functionality is degraded and/or 7651 BASE STATION OPERATION DEGRADED
The unit/module operation is degraded. 7651 BASE STATION OPERATION DEGRADED
Depending on the reported 7660 BASE STATION LICENCE EXPIRED7661 BASE STATION LICENCE NOT
severity:_x000D_
- If the severity is Minor, the BTS works
normally but the functionality/resources
is/are to be disabled/unavailable after the
The device is out of use. 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
trial period time expires._x000D_
- If the severity is Major, BTS functionality is
degraded and/or the resources are
unavailable.
The RF performance is not on the expected 7655 CELL NOTIFICATION
level.
Default values for the internal delays in the 7650 BASE STATION FAULTY
BB card are used._x000D_
Effects on functionality:_x000D_
1) Cell boundaries cannot be defined as
accurately as with measured internal delay
The Master and Extension System Modules 7650 BASE STATION FAULTY
values._x000D_
are reset.
2) 3GPP Dedicated measurement (RTT
measurement) accuracy is lower than with
measured internal delay values.
If other references are available, the 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
synchronization reference source changes
to another source. Tuning then follows this
new reference. _x000D_
_x000D_
If other references are available, the 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
If other references are not available, tuning
synchronization reference source changes
does not follow the external reference
to another source. Tuning then follows this
anymore. Clock tuning is halted and the BTS
new reference._x000D_
continues its operation based on the internal
_x000D_
Calls are not possible through the affected 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
oven oscillator._x000D_
If other references are not available, the
cell(s)
_x000D_ (7653 CELL FAULTY)._x000D_
BTS master clock (OCXO) tuning is halted
Calls
If the are
FCMpossible but the cell
is approaching the capacity
end of itsand
and the BTS synchronization drops to
performance
lifetime but the might decrease
reference (7654 CELL
frequency is still
holdover mode.
OPERATION
correct, the DEGRADED)._x000D_
BTS and system performance
No
mightimpactnormal
on theforsystem (7652 BASE
cell(s) be
(7653 CELL months or even
FAULTY)._x000D_ one
STATION
year after NOTIFICATION)
the alarm activation (provided that
the DAC is not at the edge of
performance might decrease (7654 CELLthe adjustment
area).
OPERATION DEGRADED)._x000D_
STATION NOTIFICATION)
The FR Module is configured with default 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
settings and the performance is not as
expected._x000D_
_x000D_
The following faults may occur (may be
generated) in the consequence of fault
1902: _x000D_
_x000D_
1907/EFaultId_FrTxOutOfOrder _x000D_
There can be problems with calls made
110/EFaultId_UnitRnwConfigAl _x000D_
through the affected cell(s) (7654 CELL
134/EFaultId_RxAntennaSignalLevelDifferen
ceTooHighAl_x000D_
_x000D_
_x000D_
1924/EFaultId_FrConfigurationFileCorrupted
NOTIFICATION)
performance might decrease (7654 CELL
_x000D_
_x000D_
There might be problems with calls made 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
through the affected cell(s).
_x000D_
through the affected cell(s) (7654_x000D_
CELL OPERATION DEGRADED)._x000D_
_x000D_
There can be problems with the calls made
The TX/RX paths of the RF module are out 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
of order._x000D_
_x000D_
Calls are not possible through the affected
No effect on the system, however, it might
not be possible to commission the cells on
Calls are notRx(7652
the affected possibleBASE
through the affected 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
STATION
NOTIFICATION).
_x000D_
The FR Module might overheat. 7652 BASE STATION NOTIFICATION
The TX part is out of power._x000D_ 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
Calls are not possible through the affected
This fault should cancel itself. _x000D_ 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
Module heating is ongoing._x000D_
During RF start-up, the affected cell
resources are not reported to the TCOM.
The FR configuration might fail and cause 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
another fault, and there might be problems
with calls made through the affected
cell(s)._x000D_
_x000D_
The default configuration is used and the cell 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
TX and/or RX performance_x000D_
NOTIFICATION)
is degraded. There might be problems in the
calls through the affected_x000D_
cell(s) (7654 CELL OPERATION
Calls are not possible to go through the 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
DEGRADED)._x000D_
affected cell(s) (7653 CELL
_x000D_
FAULTY)._x000D_
STATION NOTIFICATION)_x000D_
The communication between the system
_x000D_ 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
module and the
The following FR might be
faults occur (might be
corrupted._x000D_
generated) in consequence of_x000D_
NOTIFICATION).
Calls are not
fault 1924: possible through the affected
_x000D_
1900/EFaultId_FrConfiguringFailed_x000D_
The TX power level is decreased and there 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
1902/EFaultId_FrFileNotFound
might be problems with calls made through
the affected cell(s).
There
STATION might be problems with calls made
NOTIFICATION) 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
through the affected cell(s) (7654
CELL_x000D_
None 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
NOTIFICATION)._x000D_
_x000D_
The BTS does not send faults related to the
blocked Flexi Radio module (FR) to the
network management system (NMS). Fault
sending to BTS Site Manager is always
enabled. The fault cancellations are always
sent to the NMS.
Default values for fan parameters are to be 7652 BASE STATION NOTIFICATION
used.
If the fans are not rotating as required, there 7652 BASE STATION NOTIFICATION
is a risk that the module temperature rises
too much.
is a risk of the module temperature rising too
high.
If the fans are rotating faster than required, 7652 BASE STATION NOTIFICATION
unnecessary noise appears.
The RF Module might overheat, but there is 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
no immediate effect on the module
operation.
There might be problems with calls made 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
through the affected cell(s) (7654_x000D_
NOTIFICATION).
The operation of the BTS might decreases. 7652 BASE STATION NOTIFICATION
Problems might occur during calls made with 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
the affected cell(s) (7654_x000D_
Calls and data transmissions are not
possible through the affected cell(s).
The cell using resources of the FR module 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
that raised the fault is disabled or degraded
(depending on the amount and type of Tx/Rx
resources lost - see also Reported Alarms
Description). _x000D_
Flexi BTS unit in question is transmitting or 7652 BASE STATION NOTIFICATION
_x000D_
receiving data with degraded performance.
Downlink signal transmission on the given
Fault does not trigger any special action on
antenna line is disabled and the
BTS.
corresponding FR transmitter is unusable.
_x000D_
_x000D_
Note that overall FR module state is not
affected, since the fault is caused by
external phenomena on the antenna line (i.e.
extremely high VSWR level). RF HW and its
subsystems are not affected by the fault
despite some functions of FR module (e.g.
transmitter on the alarming antenna line)
cannot be used as long as the fault remains
In the case of primary optical link to RF 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
Module, the cell(s) of the RF Module behind
the broken connection is/are not operational
and the RF Module cannot be used.
_x000D_
In the case of primary optical link to RF 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
_x000D_
Module, the cell(s) of the RF Module behind
In the case of primary link to Extension
the broken connection is/are not operational
System Module, all cells that have been
and the RF Module cannot be used.
allocated to BB resources on the Extension
_x000D_
In
FSMthearecasenotofoperational
primary optical link to RF FSM 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
and Extension
_x000D_
Module,
cannot be the cell(s) of the RF Module behind
used._x000D_
In the case of primary link to Extension
the broken connection are not operational
_x000D_
System Module, all cells that have been
and
In thethe RF of
case Module
secondary cannot be used.
optical link to RF
allocated to BB resources on the Extension
_x000D_
Module or Extension System Module, the
The BTS
FSM are notcapacity decreases.
operational The optical
and Extension FSM 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
_x000D_
cells that are transmitted through the
interface
cannot beloses synchronization if the number
used._x000D_
In the case of primary
antenna link to Extension
of errors carrier
_x000D_ exceeds or the
have resources
defined limit.allocated
System Module,
via secondary linkallare
cells that have
affected. been
Cells not
In the case of secondary optical link to RF
allocated
affected mightto BBstill
resources on the Extension
be operational.
Module
The ortraffic
Extension
to theSystem Module,RF the
FSMRP3 are not operational appropriate
and Extension FSM 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
cells
Module,that are transmitted
Extension through
System Module, or the
cannot be used._x000D_
antenna
summing carrier or have resources allocated
_x000D_ device is malfunctioning. The
via secondary
related cell(s) link aretoaffected. Cells not
In the case of (traffic
secondary the RF Module)
optical link to RF
affected
is/are not might still
operational, be operational.
or the BTS operation
Module or Extension System_x000D_
Baseband bus RP3 traffic to the RF 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
is degraded
Module, the (traffic
cells that to the
are Extension
transmitted System
Module/Extension System Module, or
Module),
through or the BTS is not operational
betweenthe theantenna
summing carrier or have_x000D_
and optical devices is
(traffic
resources to the summing device).
not working. Depending on the link,link
allocated via secondary are
either
affected. Cells not affected_x000D_
the BTS capacity or cell operation is
Baseband
might bus
still be RP3 traffic to the RF
operational. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
degraded.
between the summing and optical devices is
not working. Depending on the link, either
degraded.
degraded.
degraded.
There are possibly no immediate effects on 7652 BASE STATION NOTIFICATION
degraded.
the BTS operation but it might cause an
optical interface alarm.
The RP1 synchronization burst related to the 7651 BASE STATION OPERATION DEGRADED
failed FIFO is removed and possibly has to
be sent again. The BTS operation is to be
degraded.
The traffic between the System Module and 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
RF Module/Extension System Module
becomes unreliable. Some calls or other
connections might be lost._x000D_
_x000D_
The connection to the associated port is lost. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
The data is partly/completely lost. The worst-
case fault effect can expand further from the
cell level. _x000D_
_x000D_
The data traffic to the appropriate RF 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
This fault can prevent BTS operation when
Module or Extension System Module is
the RF Module is needed for the required
malfunctioning. Depending on the alarming
cell configuration.
module, the BTS operation is faulty (Master
System Module), or the BTS operation is
RP3 traffic from the baseband to the 7651 BASE STATION OPERATION DEGRADED
degraded (Extension System
appropriate module/unit is malfunctioning.
Module)._x000D_
The BTS operation is degraded.
_x000D_
The Extension System Module is out of 7651 BASE STATION OPERATION DEGRADED
order and the BTS operation is decreased.
The Extension System Module is out of 7651 BASE STATION OPERATION DEGRADED
order and the BTS operation is decreased.
The BTS is not operational. 7650 BASE STATION FAULTY
Baseband bus RP3/RP3-01 traffic might not 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
operate correctly. The cell operation is
degraded.
SW update needed. 7650 BASE STATION FAULTY
The BTS operation is degraded because 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
some of the BTS resources are not
available.
7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
The BTS operation is degraded because 7651 BASE STATION OPERATION DEGRADED
available.
The BTS operation is degraded, because 7651 BASE STATION OPERATION DEGRADED
available.
The BTS is out of order. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
sRIO communication to devices on the 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
impacted port is no longer possible._x000D_
Either the I2C connections are disturbed or 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
the remote board is defective. This prevents
the sRIO system from configuring a new
connected extension board.
The BTS is out of order because of 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
malfunctioning sRIO communication.
If all of the BTS signal processing capacity is 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
malfunctioning, the BTS is not operational. If
some signal processing capacity is working
normally, the BTS operation is degraded.
The cell may enter a "sleeping" mode. 7651 BASE STATION OPERATION DEGRADED
capacity might decrease (BASE STATION
might be not operational at all (BASE
STATION FAULTY).
Depending on the reported severity, the fault 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
operation (BASE STATION NOTIFICATION)
or the BTS capacity might decrease(CELL
OPERATION DEGRADED or CELL
FAULTY).
capacity might have decreased (BASE
STATION OPERATION DEGRADED), or the
STATION FAULTY).
operation (BASE STATION or CELL
have decreased (BASE STATION or CELL
OPERATION DEGRADED, or CELL
FAULTY), or the BTS might not be
operation (BASE STATION NOTIFICATION)
operational at all (BASE STATION
or the BTS capacity might have decreased
FAULTY).
(BASE STATION OPERATION DEGRADED
or CELL OPERATION DEGRADED, or
CELL FAULTY) or the BTS might not be
FAULTY).
decrease (CELL OPERATION DEGRADED,
If the fans are not rotating as expected, 7652 BASE STATION NOTIFICATION
or CELL FAULTY) or the BTS might not be
there is a risk the module temperature might
rise too high. For example, a Temperature
FAULTY).
alarm might be generated from the alarming
module.
capacity might decrease (BASE STATION or
CELL OPERATION DEGRADED), or the
STATION FAULTY).
decrease (BASE STATION OPERATION
If the alarm severity is 7652 BASE STATION 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
DEGRADED or CELL OPERATION
NOTIFICATION, the BTS is using the lower
DEGRADED, or CELL FAULTY), or the BTS
level synchronization source as a reference
for tuning the BTS master clock (OCXO).
STATION FAULTY).
This does not necessarily have any effect on
the BTS operation, it depends on the quality
situation might cause the BTS capacity to be
of the used lower level source._x000D_
decreased (BASE STATION DEGRADED or
_x000D_
CELL OPERATION DEGRADED, or CELL
If the alarm severity is 7651 BASE STATION
FAULTY ) or the BTS might not be
Depending
OPERATION onDEGRADED,
the reported severity,
the BTS the
hasfault
no 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
operational at all (BASE STATION FAULTY)
situation might have no
valid synchronization impactas
sources onathe
reference
or there is no impact on operation (BASE
operation
for tuning (BASE
the OCXO STATION
and theorOCXOCELL is in
NOTIFICATION),
holdover mode, using the cell
the capacity might
last calculated
decrease
tuning (CELL
control OPERATION
value. The fault situation does 7650 BASE STATION FAULTY
The BTS is not operational.
DEGRADED),
not affect the BTSor the
aircell might stability,
interface not be but if
operational at all (CELL
the fault situation lasts forFAULTY).
a long time, the
accuracy starts to drift slowly. However, it
might take several weeks before the
The BTS capacity
BTS/RAN operations might have
start decreased.
to be affected 7652 BASE STATION NOTIFICATION7653 CELL FAULTY
because of the very small OCXO aging
factor.
The newly installed HW resources are 7652 BASE STATION NOTIFICATION7653 CELL FAULTY
unavailable before resetting the BTS.
Recommissioning is also performed when
the RF Module type differs from the previous
one.
The alarm 7661 BASE STATION LICENCE 7660 BASE STATION LICENCE EXPIRED7661 BASE STATION LICENCE NOT
NOTIFICATION indicates that the feature is
to expire in one Week or one Month. This
does not have an immediate effect on BTS
operation._x000D_
The affected cell remains working as a non- 7655 CELL NOTIFICATION
_x000D_
MIMO cell. All MIMO users of the cell are
If the reported alarm is 7660 BASE
deleted.
STATION LICENCE EXPIRED, the feature
has expired.
Some cells may not work. 7653 CELL FAULTY
BTS is out of order or the capacity is 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
degraded.
The fault has no direct impact on operations 7652 BASE STATION NOTIFICATION
(BASE STATION NOTIFICATION).
BTS malfunction. Some BB processing 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
resources in the BTS are out of use.
The BTS resources have decreased or the 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
BTS is faulty.
The ongoing BTS operations may be 7652 BASE STATION NOTIFICATION

influenced, the BTS capacity might be
decreased, or the BTS might not be
operational.
This fault has no immediate effect on the 7652 BASE STATION NOTIFICATION
BTS operation. But if System Module is
replaced then, for example, licensing data
cannot be recovered from the Radio Module
and licensed features are disabled.
The BTS operation is degraded (FSP) or the 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
BTS is not operational (FCM).
The unit might be started with an old SW 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
version and is therefore not compatible with
any other units.
BTS is ready to be commissioned, but has 7652 BASE STATION NOTIFICATION

no commissioning file.
BTS startup is interrupted and the BTS is out 7650 BASE STATION FAULTY7652 BASE STATION NOTIFICATION
of order.
Licenses cannot be activated. 7661 BASE STATION LICENCE NOTIFICATION

This fault can prevent BTS from functioning 7651 BASE STATION OPERATION DEGRADED
when the RF Module is needed_x000D_
for the required cell configuration. _x000D_
This fault can prevent BTS from functioning 7651 BASE STATION OPERATION DEGRADED
when the RF Module is needed for the
required cell configuration.
operational._x000D_
faulty._x000D_
The parameter could not be read from the 7652 BASE STATION NOTIFICATION
_x000D_
Radio Module. It is impossible to tell whether
the proper parameter value exists in the
Radio Module, in that sense the writing
operation cannot be performed.
The signal path is unusable. The cells using 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
the faulty unit might not_x000D_
work.
The antenna line is not operating correctly. 7652 BASE STATION NOTIFICATION7653 CELL FAULTY
The cell gets disabled. _x000D_
The antenna line is not operating correctly. 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
The cell capacity decreases.
There is no immediate effect on cell 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
operation. The device continues operation
with the previous SW.
There is no immediate effect on cell 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
operation. The device continues operation
with the previous SW.
The module in question is out of use. This 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
alarm cancels all active alarms for the same
module.
Part (or all) of the baseband processing 7651 BASE STATION OPERATION DEGRADED
resources might be out of order.
Depending on the reported 7660 BASE STATION LICENCE EXPIRED7661 BASE STATION LICENCE NOT
severity:_x000D_
- if Minor (Working), the BTS is working
normally but the functionality/resources
is/are to be disabled/unavailable after the
trial period time expires._x000D_
- if Major (Degraded), the BTS functionality
is degraded and/or the resources are
unavailable.
The cell is faulty if all of its critical radio 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
resources are affected, or the cell operation
is degraded if the part of the cell's resources
is affected, but the cell still has critical
resources working._x000D_
Unsupported module will not be put into use. 7652 BASE STATION NOTIFICATION
_x000D_
Note: FR Status LED may not match the
expected color and pattern as
specified_x000D_
Commissioned cells of
for this fault in case using thewith
radios missing RP3- 7653 CELL FAULTY7654 CELL OPERATION DEGRADED
01 link are not
harmonized RP1activated.
interface (v.2.x)._x000D_
It may be overridden by "Alternating Red
and Green" LED pattern_x000D_
caused
The BTSbydoesactive
notfault 4045correctly.
function informing about 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
faulty Antenna Line, which_x000D_
is not reported to BTS SM / NetAct by
Master RAT BTS.
The BTS functionality is degraded and/or 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
resources becomes unavailable.
The RS485 interface is not operating 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
correctly. The cell capacity decreases.
BB resources that belong to the alarming 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
module are shut down; the BTS operation is
to be degraded or faulty.
FCM and FTM are kept powered.
No commissioned cells are activated. 7651 BASE STATION OPERATION DEGRADED7653 CELL FAULTY7654 CEL
Fan control is not optimized. The effect to 7652 BASE STATION NOTIFICATION
noise/temperature level is marginal.
Radio module detected but faulty. 7653 CELL FAULTY
FSP resources shut down; BTS operation is 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
degraded or faulty._x000D_
FCT and other FSPs not signaling an alarm
are kept operational._x000D_
is a risk that the module temperature is
rising too high.
If the fan(s) is/are not rotating as required, 7652 BASE STATION NOTIFICATION
there is a risk that the module temperature is
rising too high.
If the fans are rotating faster than required, it 7652 BASE STATION NOTIFICATION
creates unnecessary noise.
BTS is not operational. 7650 BASE STATION FAULTY
Source unit has inconsistent SW version. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
The BTS capacity decreases. 7652 BASE STATION NOTIFICATION
Some operations inside the BTS are 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
interrupted. Depending on the fault source,
the BTS or cell operation becomes degraded
or faulty.
The module cannot: 7650 BASE STATION FAULTY
- memorize a cause of the SW fallback on
request in the file
or
- [FSMr3 only] mount passive File System,
Ongoing BTS reset will last longer. 7652 BASE STATION NOTIFICATION
and thus read the cause of SW fallback on
request from the file.
BTS is not operational. 7650 BASE STATION FAULTY
BTS baseband processing power is 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
decreased. If all FSPs are faulty, then the
BTS is not operational._x000D_
_x000D_
[FSMr3 and BTS has only 1 FSP]: 7651 BASE STATION OPERATION DEGRADED
BTS is reset.
[ELSE]
FSP is removed from the configuration and
Newly downloaded SW will overwrite active 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
shut down. The BTS is degraded.
SW. Therefore, the SW download and
activation are not allowed. Currently, the
active SW is still running._x000D_
Slave mode is not operational. 7650 BASE STATION FAULTY
Radio module is powered off, therefore 7652 BASE STATION NOTIFICATION

calls/data transfers cannot be served by that
module.
BTS operation capacity decreases 7652 BASE STATION NOTIFICATION

depending on resource allocation, and some
cells might be lost.
None 7652 BASE STATION NOTIFICATION
The fault has no direct impact on the 7652 BASE STATION NOTIFICATION
operation (7652 BASE STATION
NOTIFICATION).
NOTIFICATION).
NOTIFICATION).
NOTIFICATION).
NOTIFICATION).
Cell with incorrect Rx carrier bandwidth will 7653 CELL FAULTY

be disabled.
Cell with incorrect Tx carrier bandwidth will 7653 CELL FAULTY
be disabled.
Cell will be disabled. 7653 CELL FAULTY
The data field value in Antenna Line Device 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
was not updated.
In the case of a problem detection in SW 7650 BASE STATION FAULTY7652 BASE STATION NOTIFICATION
activation, the SW activation and
consequent reset are aborted._x000D_
In the case of a problem detection in Start-
up, BTS remains out of order.
Startup is stopped. BTS is reset if reference 7650 BASE STATION FAULTY
clock becomes available after 5 min.
Calls are not possible through the affected 7653 CELL FAULTY
Calls are possible but the cell capacity and 7654 CELL OPERATION DEGRADED
performance might decrease.
Calls are possible but the cell capacity and 7654 CELL OPERATION DEGRADED
performance might decrease.
Extended logging into ramdisk is active and 7652 BASE STATION NOTIFICATION
may decrease performance of the BTS.
Depending on the reported severity, capacity 7653 CELL FAULTY7654 CELL OPERATION DEGRADED
might decrease (7654 CELL OPERATION
DEGRADED), or calls are not possible
FAULTY).
Extension System Module is not used after 7651 BASE STATION OPERATION DEGRADED
hot insertion(FSMr2/FSMr3)/startup(FSMr2).
Extension System Module is not taken into 7651 BASE STATION OPERATION DEGRADED
use.
BTS functionality is degraded and/or the 7651 BASE STATION OPERATION DEGRADED
7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
BTS is operational. 7652 BASE STATION NOTIFICATION
Radio uses the default VSWR threshold. 7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
The BTS is working normally but the IRC 7652 BASE STATION NOTIFICATION
Receiver functionality is unavailable for a
pure single RX cells configuration.
Commissioned cells using incorrectly 7652 BASE STATION NOTIFICATION7653 CELL FAULTY7654 CELL OPERAT
connected fiber cable might not function
properly.
The MHA does not compensate the signal 7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
loss of the long feeder cable to the BTS
located at the base of the tower.
BTS cannot reach OnAir. 7650 BASE STATION FAULTY
The shared radio may not be suitable to use 7652 BASE STATION NOTIFICATION
and - in case of startup - RP3-01 links are
not enabled till phase is tuned.
High memory usage (memory outage risk). 7652 BASE STATION NOTIFICATION
Critical impact on FSP operation. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
The BTS capacity decreases or the BTS is 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
out of order. The Digital Signal_x000D_
Processing (DSP) does not work correctly.
Processing (DSP) is not working correctly.
Processing (DSP) is not working correctly.
The alarm text indicates the time that the 7665 BASE STATION TRANSMISSION ALARM
reset took place and also whether the reset
was triggered by the software (SW
activation, file commissioning) or by turning
the power in the transport part of the WBTS
The BTS does not take the new BTS IP 7665 BASE STATION TRANSMISSION ALARM
off and on.
settings in use before the change is
confirmed.
The calls signaled with an unknown DSCP 7665 BASE STATION TRANSMISSION ALARM
value are mapped to the best effort service
category.
The communication link between the BTS 7665 BASE STATION TRANSMISSION ALARM
and one or more peers is defective. No
communication is possible towards these
peers.
None 7665 BASE STATION TRANSMISSION ALARM
Possible impact on the connections over this 7665 BASE STATION TRANSMISSION ALARM
interface:
- no calls are possible anymore
- loss of remote management access to
other network elements in the RAN
- loss of synchronization if the interface is
interface:
used as synchronisation source.
Possible effects: 7665 BASE STATION TRANSMISSION ALARM
- loss of synchronisation if the interface is
used as a synchronisation source
The interface cannot be used for 7665 BASE STATION TRANSMISSION ALARM
used as a synchronisation source.
transmission. It can be used for connectivity
checks only.
The interface cannot be used for 7665 BASE STATION TRANSMISSION ALARM
transmission.
Possible impact: 7665 BASE STATION TRANSMISSION ALARM
- no calls possible anymore
Possible impact: The BTS isn't synchronized 7665 BASE STATION TRANSMISSION ALARM
to the network anymore.
Possible impact: WBTS might have to use a 7665 BASE STATION TRANSMISSION ALARM
synchronization interface that has a lower
clock quality.
7665 BASE STATION TRANSMISSION ALARM
Transmission via CES over PSN over the 7665 BASE STATION TRANSMISSION ALARM
CES pseudowire tunnel is defective.
CES pseudowire is defective.
CES pseudowire is defective.
The Certificate Revocation List could not be 7665 BASE STATION TRANSMISSION ALARM
updated. New revoked certificates_x000D_
remain unknown to the BTS.
Normal traffic is interrupted. Only loopback 7665 BASE STATION TRANSMISSION ALARM
OAM frames are transmitted and received
over the interface. If the test frame generator
is switched on, test frames are transmitted.
The Ethernet interface might be out of order 7665 BASE STATION TRANSMISSION ALARM
or the remote peer might be out of order.
Traffic might get lost.
The Ethernet interface is defected or the 7665 BASE STATION TRANSMISSION ALARM
remote peer is defective. Traffic might get
lost.
The SFP is not operational. 7665 BASE STATION TRANSMISSION ALARM

None, except that the TWAMP session goes 7665 BASE STATION TRANSMISSION ALARM
in disabled state.
The transport connection towards the 7665 BASE STATION TRANSMISSION ALARM
remote peer may be defective. Traffic may
get lost. The OSPF deamon attempts
however to reach the deamon via an
alternative IP route.
interface:
interface:
- slow management access to the WBTS
and other network elements in the RAN
- poor voice quality and data performance
- if this interface is part of an IMA group, this
IMA link is temporarily suspended from
interface:
operation
interface:
interface:
interface:
interface:
Possible impact: the performance 7665 BASE STATION TRANSMISSION ALARM
management data collected on this interface
becomes invalid.
Possible impact on the connections over the 7665 BASE STATION TRANSMISSION ALARM
interface in question:
interface:
- the IMA link is not usable
- the data rate is reduced

- the data rate of the IMA group is reduced

- the data rate is reduced
Possible impact: the capacity of the IMA 7665 BASE STATION TRANSMISSION ALARM
group is not as high as expected.
Possible impact: the capacity of the IMA 7665 BASE STATION TRANSMISSION ALARM
group is not as high as expected.
Possible impact for connections over this 7665 BASE STATION TRANSMISSION ALARM
interface:
interface:
interface:
interface:
interface:
interface:
Possible impact:_x000D_ 7665 BASE STATION TRANSMISSION ALARM
_x000D_
- no calls are possible for the connections
over this unit_x000D_
_x000D_
interface:
- no calls are possible
- loss of remote management access
interface:
interface:_x000D_
- no calls are possible_x000D_
Possible impact: It is not possible to 7665 BASE STATION TRANSMISSION ALARM
exchange any AAL2 signalling requests and
therefore calls cannot be established or
released. Calls that have already been
established are not affected.
Possible impacts on TRSW_x000D_ 7665 BASE STATION TRANSMISSION ALARM
- Reboot_x000D_
- Packet loss
Possible impact: Calls are not possible 7665 BASE STATION TRANSMISSION ALARM
anymore.
The transport connection toward the remote 7665 BASE STATION TRANSMISSION ALARM
peer might be defective. Traffic might get
lost.
The transport connection towards the 7665 BASE STATION TRANSMISSION ALARM
remote peer may be defective. Traffic may
get lost.
The requested service is not available. 7665 BASE STATION TRANSMISSION ALARM
No traffic in the ingress direction is possible. 7665 BASE STATION TRANSMISSION ALARM
No traffic in the egress direction is possible. 7665 BASE STATION TRANSMISSION ALARM
and its peer is defective. No communication
possible.
and the RNC is defective. No
communication
possible.
If the alarm is active, then potentially there is 7665 BASE STATION TRANSMISSION ALARM
a synchronization loop
BTS will not have time synchronisation. 7665 BASE STATION TRANSMISSION ALARM
No frames are transmitted and all incoming 7665 BASE STATION TRANSMISSION ALARM
frames are discarded in BTS.
MLPPP operates with one of the sessions 7665 BASE STATION TRANSMISSION ALARM
down. But if there is only one session
then;_x000D_
Possible impact on the connections over this
interface:_x000D_
- no calls are possible_x000D_

There might be available another 7665 BASE STATION TRANSMISSION ALARM
synchronization source at eNB; in that case
the BTS switches automatically to the other
clock source.
If no other synchronization source is
available at eNB, it runs in hold-over mode;
- No calls are possible for the connections
over this unit
Please refer to status of 3080:
Possible impact for connections over this
EFaultId_BtsReferenceClockMissing 7665 BASE STATION TRANSMISSION ALARM
interface:_x000D_
- Connectivity loss_x000D_
- System may work in degraded mode.
Possible impact on connections over this 7665 BASE STATION TRANSMISSION ALARM
interface:_x000D_
Possible impact on connections over this 7665 BASE STATION TRANSMISSION ALARM
interface:_x000D_
The active base station configuration is not 7665 BASE STATION TRANSMISSION ALARM
the same as requested in the configuration
change.
In a cell setup, the cell is set inactive until 7654 CELL OPERATION DEGRADED
the valid cell configuration data has been
received. In a cell reconfiguration, the cell
continues operating with the previous
configuration data.
The cell setup is rejected and the BTS is 7650 BASE STATION FAULTY
faulty.
Depending on the reported severity, BTS 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
capacity might have decreased (BASE
STATION OPERATION DEGRADED, CELL
FAULTY) or the BTS might be completely
out of order(BASE STATION FAULTY).
The BTS capacity decreases. The digital 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
signal processing (DSP) is not functioning
correctly.
The BTS cannot use the licensed feature 7652 BASE STATION NOTIFICATION
until the BTS is reset.
Calls are not possible through the affected 7652 BASE STATION NOTIFICATION
cell(s). In case of shared RF (lack of fault
2000/2001/2002/2004/2005/2016), alarm
7652 is raised. In case of not shared RF
(fault 2000/2001/2002/2004/2005/2016
The BTS operation is degraded because 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
active), no alarm is raised.
some BTS resources are unavailable.
Slave mode is not operational._x000D_ 7651 BASE STATION OPERATION DEGRADED

FSPs in the baseband sub-module are not
operational.
Common Channel Device or Mixed Channel 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
Device cannot work in the current mode.
UltraSite, MetroSite, MetroSite 50, Triple- 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
mode:_x000D_
_x000D_
The affected WAM unit is not operational. In
case of a WSP fault, the channel capacity is
The fault indication is informative and does 7655 CELL NOTIFICATION
lost and cell(s) might become unavailable. In
not have effect on the BTS operation. The
case of WTR or WPA/WMP, the associated
end user may experience delay in call setup.
cell(s) become(s) faulty._x000D_
_x000D_
The BTS capacity is decreased.
FlexiBTS:_x000D_ 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
_x000D_
The affected FCM unit is not operational. In
case of an FSP fault, the channel capacity is
lost
The and
BTScell(s) might
capacity become unavailable. In
is decreased. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
case of an FR, the associated cell(s)
become(s) faulty._x000D_
_x000D_
UltraSite/EUBB: _x000D_
The subrack and cell under the WPS unit
_x000D_ 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
may become WSPF
The affected degraded
unitoris faulty.
not operational.
In case of a Faraday fault, the channel
A single faulty
capacity is lostpower unit will
and cell(s) notbecome
might adversely
affect the operation
unavailable. In case of
of other
a WTR power
or units in
The external connectors are not functioning. 7652 BASE STATION NOTIFICATION
the system.
WPA/WMP, the associated cell(s)
become(s) faulty.
The BTS starts up as a previously detected 7651 BASE STATION OPERATION DEGRADED
cabinet type. If the previous cabinet type
cannot be determined, the BTS starts up as
a Supreme cabinet.
UltraSite, MetroSite, MetroSite 50, Triple- 7654 CELL OPERATION DEGRADED
mode:
The BTS cannot configure the TRX to a

channel that is not physically supported by
the WTR. The WTR or TRX is unoperational.
FlexiBTS:

the LTX. The LTX or TRX is unoperational.
This fault can prevent the BTS from 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
functioning when the RF Module is needed
for the required cell configuration.
The BTS is not operational. 7650 BASE STATION FAULTY
If there is only one WSC or both the active 7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFIC
and redundant WSCs are faulty, the BTS is
not operational. There is no working WSC
unit and the synchronization does not work.
The BTS functionality is degraded and/or
If there is a redundant WSC and the
recovery switch operation was successful,
the BTS can work normally.
UltraSite,
If there is MetroSite,
a WMC, theMetroSite 50, Triple-
BTS is not 7654 CELL OPERATION DEGRADED
mode:
operational. There is no working WMC unit
and the synchronization does not work.
BTS is not operational. 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
the WTR. The WTR or TRX is unoperational.
FlexiBTS:
Depending on theconfigure
The BTS cannot alarmingthemodule
TRX either
to a 7650 BASE STATION FAULTY7651 BASE STATION OPERATION DEGRADED
the BTS that
channel is not
is operational andsupported
not physically all the BTSby
optical
the LTX.interfaces
The LTXare faultyis(Master
or TRX System
unoperational.
Module), or the BTS operation is degraded
(Extension System Module).
Baseband bus RP3/RP3-01 traffic to the 7651 BASE STATION OPERATION DEGRADED7654 CELL OPERATION DEG
connected module/unit might not work
correctly. The BTS capacity is degraded.
BTS startup is interrupted and the BTS is out 7650 BASE STATION FAULTY
of order.
In case of license "Distributed Site 15" or 7653 CELL FAULTY

"Distributed Site 40" the Radio Module is
detected but the required license is missing.
Calls and data transfers are not possible
through the affected cells.
Reported Alarms Description
7650 BASE STATION FAULTY (all FSPs in the master

FSM or all FSPs in the BTS are faulty)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (at
least one working FSP in the master FSM,
DSP)_x000D_
_x000D_
7650 BASE STATION FAULTY (FT)_x000D_

7651 BASE STATION OPERATION DEGRADED (FSP,
extension FSM, FBB)_x000D_
7652 BASE STATION NOTIFICATION (FSM FAN,
external ALD, any source HW unit which is already
blocked or uncommissioned)_x000D_
7653 CELL FAULTY (FR (all critical cell resources are
lost in MHA, TILT, FA (but cell already faulty because of
other faults))_x000D_
4040:EFaultId_InitFaultManAl:_x000D_
7654 CELL OPERATION DEGRADED (FR (There is
7650
enough BASE STATION
critical FAULTY
cell resources left(FCM/FCT
for the cellintomaster
remain
system module,
operational), FF All FSPs)_x000D_
, MHA, TILT, FA)_x000D_
7651
_x000D_BASE STATION OPERATION DEGRADED
(FCM/FCT in extension system module, not all
FSPs)_x000D_
7650 BASE STATION FAULTY (FCM/FCT in master
7653 CELL FAULTY (FSP)_x000D_
system module, All FSPs)_x000D_
_x000D_
7650 BASE STATION FAULTY (FCM/FCT on MSM or
FSPs)_x000D_
all FSPs)_x000D_
_x000D_
(FCM/FCT on ESM or not all FSP)_x000D_
_x000D_
7650 BASE STATION FAULTY (FCM/FCT, FTM or all
FSPs)_x000D_
(FCM/FCT, FSP or undefined)_x000D_
7653 CELL FAULTY (FR, FF, all TX/RX FFs in LCR are
UltraSite, MetroSite, MetroSite 50, Triple-mode:_x000D_
broken)_x000D_
7654 CELL OPERATION DEGRADED (FF, a working
(WAM, AXC or undefined)_x000D_
TX/RX FF exists in LCR) _x000D_
7653 CELL FAULTY (WPA/WMP or the only WTR in the
7652 BASE STATION NOTIFICATION (FCM/FCT,
cell)_x000D_
uncommissioned FR)_x000D_
7654 CELL OPERATION DEGRADED (WTR)_x000D_
_x000D_
7652 BASE STATION NOTIFICATION (WAM or
undefined)_x000D_
7655 CELL NOTIFICATION (WTR)_x000D_
_x000D_
FlexiBTS:_x000D_
7652 BASE STATION NOTIFICATION (FCM)_x000D_
_x000D_
UltraSite/EUBB:_x000D_
FlexiBTS rel2:_x000D_
7650
7652 BASE
BASE STATION
STATION FAULTY (WSMF)_x000D_
NOTIFICATION (FCM,
7651 BASE STATION OPERATION
uncommissioned FR)_x000D_ DEGRADED
(WSMF)_x000D_
7655 CELL NOTIFICATION (FR)_x000D_
7652 BASE STATION NOTIFICATION (WSMF)
_x000D_
FlexiBTS rel3:_x000D_
7652 BASE STATION NOTIFICATION (FCT,
uncommissioned FR)_x000D_
7655 CELL NOTIFICATION (FR)_x000D_
_x000D_
_x000D_
(extension FSM, FSP)_x000D_
_x000D_
7652 BASE STATION NOTIFICATION (un-
commissioned RF unit, WBTS_FMGT_60468)_x000D_
_x000D_
7653 CELL FAULTY (RF Module)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (RF is faulty, but
MIMO/VAM cell has at least one TX transmitting P-
CPICH and one RX working on different RF)
7650 BASE STATION FAULTY (FT, FCM/FCT or if all

FSPs are faulty)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (FBB
or if a working FSP exists)_x000D_
7650 BASE STATION FAULTY (FTM, all

FSPs)_x000D_
FBIA, extension FCM)_x000D_
7652 BASE STATION NOTIFICATION (FR/TX/RX/FF
7650 BASE STATION FAULTY (all FSPs faulty,
when the unit is not commissioned)_x000D_
FCM/FCT)_x000D_
7653 CELL FAULTY (FR/TX/RX/FF is faulty and there is
no working TX transmitting P-CPICH or no working RX
FBIA)_x000D_
left in the cell)_x000D_
7652 BASE STATION NOTIFICATION (FR, TX, RX, FF,
7654 CELL OPERATION DEGRADED (FR/TX/RX/FF is
LTX when the unit is not_x000D_
faulty but at least one TX transmitting P-CPICH and at
commissioned)_x000D_
least one RX are not faulty)_x000D_
7653 CELL FAULTY (FR/TX/RX/FF is faulty and there is
_x000D_
no working TX transmitting_x000D_
_x000D_
7653 CELL
P-CPICH orFAULTY_x000D_
no working RX left in the cell)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (FR/TX/RX/FF is
7654
faulty CELL
but at OPERATION DEGRADED
least one TX_x000D_
transmitting P-CPICH and at least one RX are not
faulty)_x000D_
7650 BASE STATION FAULTY (if all FSPs are faulty)
_x000D_
_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (if the
unit is a slave FCM; if the unit is a FSP and at least one
FSP is working)_x000D_
_x000D_
7653 CELL FAULTY (FR)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (FR with RX
Carrier Resource redundancy)
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
7653 CELL FAULTY (TX is faulty and there is no

working TX transmitting P-CPICH)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (TX is faulty but
at least one TX transmitting P-CPICH is fine)
7653 CELL FAULTY (primary TX is faulty or all RXs are
faulty) _x000D_
7654 CELL OPERATION DEGRADED (otherwise)
7650 BASE STATION FAULTY (all FSPs in master

system module are faulty)_x000D_
_x000D_
or at least one FSP is working)_x000D_
7654 CELL OPERATION DEGRADED (some RX levels

are over the threshold or the difference between the
max. and min. RX levels is over the limit)
7654 CELL OPERATION DEGRADED (some RX levels

are over the threshold or the difference between the
max. and min. RX levels is over the limit)
7650 BASE STATION FAULTY (all FSP are
faulty)_x000D_
or at least one working FSP)_x000D_
7650 BASE STATION FAULTY (FCM/FSM out of
order/all FSP's out of order)_x000D_
_x000D_
(extension FSM degraded, not all FSP's_x000D_
None
out of order)_x000D_
_x000D_
7652 BASE STATION NOTIFICATION (only PIC
feature/functionality is degraded)
None
FlexiBTS:_x000D_
7650 BASE STATION FAULTY (all FSPs in master
system module are faulty)_x000D_
7651 BASE STATION OPERATION DEGRADED (FBIA
or at least one FSP is working)_x000D_
_x000D_
FlexiLiteBTS:_x000D_
7650 BASE STATION FAULTY (FSP is faulty)
7655 CELL NOTIFICATION (LCR)_x000D_

7652 BASE STATION NOTIFICATION (FCM,
FCT)_x000D_
7650 BASE STATION FAULTY (MSM out of order / all

FSPs out of order)_x000D_
7651 BASE STATION OPERATION DEGRADED (FSM
degraded, not all FSPs_x000D_
out of order)
7654 CELL OPERATION DEGRADED (RX level is over

the threshold)
7661 BASE STATION LICENCE NOTIFICATION -
Feature configuration (license or feature activation) is
not aligned between BTS and RNC
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
7650 BASE STATION FAULTY (master

WAM/FCM/FCT)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (slave
WAM)

FSM or in BTS are faulty)_x000D_
_x000D_
least one working FSP)_x000D_
FlexiBTS:_x000D_
_x000D_
7650 BASE STATION FAULTY (FSM or all FSPs are
faulty)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGARDED (FBB
_x000D_
_x000D_
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)

7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)

7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)

FCM/FCT)_x000D_
_x000D_
(extension FCM/FCT)_x000D_
_x000D_
FCM/FCT)_x000D_
7652 BASE STATION NOTIFICATION (master
_x000D_
FCM/FCT, when unit status is working)_x000D_
_x000D_
(extension FCM/FCT or in case of faults
FlexiBTS:_x000D_
1866/1867)_x000D_
_x000D_
_x000D_
7650 BASE STATION FAULTY (FCM/FCT out of order /
all FSPs and all FBBs out of order)_x000D_
FCM/FCT, when unit status is working)_x000D_
_x000D_
_x000D_
_x000D_
(FCM/FCT on extension FSM out of order / at least one
_x000D_
working/degraded FSP or FBB exists)_x000D_
_x000D_
Depends
7652 BASE on STATION
<x>_x000D_ NOTIFICATION (external
_x000D_
ALD)_x000D_
7651
_x000D_BASE STATION OPERATION DEGRADED (FSP,
DSP, HWPORT
7653 CELL connecting
FAULTY system
(LTX/TX/RX is modules)_x000D_
faulty and there is
_x000D_
no working TX transmitting P-CPICH and/or noother
working
7652 BASE STATION NOTIFICATION (some
7652
RX leftBASE
in theSTATION NOTIFICATION
cell)_x000D_
reference clock is available)_x000D_
(Uncommissioned
_x000D_ source in HWPORT)_x000D_
7651 BASE STATION OPERATION DEGRADED (any
_x000D_
7654 CELL OPERATION DEGRADED
reference clock source is not available) (LTX/TX/RX is
7653
faulty CELL
but at FAULTY
least one(HWPORT connecting
TX transmitting RF module
P-CPICH is fine,
to
andsystem
at leastmodule)
one Rx of the cell is working,
communication with and ALD failed)
FlexiBTS:
7650 BASE STATION FAULTY (Master System Module)

(Extension System Module)
FlexiLiteBTS:
7650 BASE STATION FAULTY

7650 - fault raised for Master System Module_x000D_
7651 - fault raised for Extension System Module

(Otherwise)_x000D_
_x000D_
7652 BASE STATION NOTIFICATION
(Uncommissioned source)_x000D_
(Otherwise)_x000D_
_x000D_
(Uncommissioned source)
7654 CELL OPERATION DEGRADED (Otherwise)
7653 CELL FAULTY (Antenna line faulty and cell's

primary Tx is faulty or no working Rx in cell)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (Antenna line
faulty, but cell's primary Tx is working and at least one
Rx is working)._x000D_
_x000D_
7653 CELL FAULTY (If cell is already faulty)_x000D_
7655 CELL NOTIFICATION (When tuning is ongoing -
7655 CELL NOTIFICATION (When tuning is ongoing,
fault 1810 is present. Reported towards BTS Site
that is the fault 1810 is active; reported towards BTS
7653
ManagerCELL FAULTY (All LNAs faulty within the
only)_x000D_
Site Manager only)_x000D_
cell)_x000D_
_x000D_
_x000D_
7654 CELL OPERATION
(Uncommissioned source DEGRADED
or fault source(Alisleast one unit)
external
LNA working within the cell)_x000D_
7653 CELL FAULTY (Unit source TX filter)_x000D_
_x000D_
_x000D_
7652 BASE STATION NOTIFICATION (not
7654 CELL OPERATION DEGRADED (Unit source
commissioned resource).
diversity RX filter)_x000D_
_x000D_
_x000D_
(Uncommisisoned unit source Tx/Rx filter)
_x000D_
7654 CELL OPERATION DEGRADED (TILT failure
affects antenna carrier of a cell within same
BTS)_x000D_
7652 BASE STATION NOTIFICATION (TILT connected
in external mode - no impact on cells within same BTS,
impact on cells from other BTS/RAT served by TILT in
unknown; uncommissioned source)
BTS)_x000D_
BTS)_x000D_
BTS)_x000D_
BTS)_x000D_
7652 BASE STATION NOTIFICATION (external AISG
MHA, external TILT; uncommissioned source)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (FF, TILT, MHA)
7652 BASE STATION NOTIFICATION (external ALD;
uncommissioned source)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (FF, MHA,
TILT)_x000D_
7654 CELL OPERATION DEGRADED_x000D_
(uncommissioned FR)

working TX transmitting P-CPICH)
at least one TX transmitting P-CPICH is not faulty)
working TX transmitting P-CPICH)
at least one TX transmitting P-CPICH is not faulty)
7652 BASE STATION NOTIFICATION (The alarming
MHA serves another BTS; uncommissioned
source)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (The alarming
7652 BASE STATION NOTIFICATION (The alarming
MHA serves this BTS)
MHA serves another BTS; uncommissioned_x000D_
source)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (The alarming
MHA serves this BTS)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (Flexi
Filter)_x000D_
_x000D_
7655 CELL NOTIFICATION (AISG MHA, RET)
_x000D_
Filter)_x000D_
_x000D_
_x000D_
Filter)_x000D_
_x000D_
_x000D_
Filter)_x000D_
_x000D_
7660 BASE STATION LICENCE EXPIRED - The license
is missing and the trial period is unavailable, which
results in the BTS functionality being degraded._x000D_
_x000D_
7661 BASE STATION LICENCE NOTIFICATION - The
7652 BASE STATION NOTIFICATION (external ALD,
license is missing during trial_x000D_
period. The BTS is functioning normally.
_x000D_
7654 CELL OPERATION DEGRADED (FF, MHA, RET)
FCM/FCT out of order_x000D_
7652 BASE STATION NOTIFICATION (another

reference clock source is not available)
7652 BASE STATION NOTIFICATION (another
reference clock source is not available)
7653 CELL FAULTY (FR is faulty and there is no
working/degraded TX transmitting_x000D_
P-CPICH or no working/degraded RX left in the
cell)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (FR is faulty but
at least one TX transmitting_x000D_
P-CPICH and at least one RX are not faulty)_x000D_
cell)_x000D_
_x000D_
_x000D_
(Uncommissioned source - radio resources_x000D_
are not assigned to any cell)_x000D_
_x000D_
are not assigned to any cell)
(Otherwise)_x000D_
_x000D_
7653 CELL FAULTY (all Rx/Primary TX resources for
given cell are faulty)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (cell has enough
Rx/Primary TX resources to remain
7653 CELL FAULTY (FR/TX/RX is faulty and there is no
operational)_x000D_
working TX transmitting P-CPICH and/or no working RX
_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (FR/TX/RX is
7653 CELL FAULTY (TX/RX is faulty and there is no
faulty but at least one TX transmitting P-CPICH is fine
working TX transmitting P-CPICH and/or no working RX
and at least one cell's Rx is working). _x000D_
left in the cell)._x000D_
_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (TX/RX is faulty
7652 BASE STATION
(Uncommissioned NOTIFICATION
source)
but at least one TX transmitting P-CPICH is fine and at
least one cell's Rx is working)._x000D_
_x000D_
7653 CELL FAULTY
(Uncommissioned (There is no working/degraded TX
source)_x000D_
transmitting P-CPICH)_x000D_
7654 CELL OPERATION DEGRADED (At least one TX
transmitting P-CPICH is not_x000D_
faulty) _x000D_

_x000D_
at least one TX transmitting P-CPICH is not
7653 CELL FAULTY (all RX's in the cell). _x000D_
faulty)_x000D_
_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (only part of RX's
in the cell)._x000D_
_x000D_
7652 BASE STATION NOTIFICATION (not
commissioned RX resource) _x000D_
_x000D_
cell)._x000D_
For AAS according to RFSW reported severity.
_x000D_
7653 CELL FAULTY (FR module rel1: FR is in faulty
state, FR module rel2: TX is faulty and there is no
P-CPICH and at least one RX are not faulty)._x000D_
7654 CELL OPERATION DEGRADED (FR module
_x000D_
rel2:TX is faulty but at least one TX transmitting P-
CPICH is not faulty). _x000D_
For AAS according to RFSW reported severity.
7653 CELL FAULTY (LTX/TX is faulty and there is no
_x000D_
7654 CELL OPERATION DEGRADED (LTX/TX is faulty
but at least one TX transmitting P-CPICH is not
faulty)_x000D_
_x000D_

_x000D_
7653 CELL FAULTY (FR start-up, module is faulty and
cell has no RX or primary TX working)_x000D_
_x000D_
(Otherwise)_x000D_
7654 CELL OPERATION DEGRADED (FR start-up,
_x000D_
module is faulty but cell has at least one RX and primary
TX working)_x000D_
_x000D_
(Otherwise)_x000D_
7655 CELL NOTIFICATION (FR runtime)
_x000D_
_x000D_
faulty)_x000D_
_x000D_
cell)_x000D_
_x000D_
7652 BASE
are not STATION
assigned to anyNOTIFICATION
cell)
_x000D_
7654
7652 CELL
BASE OPERATION
STATION NOTIFICATION
DEGRADED(Otherwise)._x000D_
_x000D_
are not assigned to any cell).
are not assigned to any cell)_x000D_
_x000D_
7655 CELL NOTIFICATION(Otherwise)_x000D_
_x000D_
faulty)_x000D_
_x000D_
7655 CELL NOTIFICATION (Otherwise)_x000D_
_x000D_
7653 CELL FAULTY (there is no working/degraded TX
transmitting P-CPICH_x000D_
and/or no working RX left in the cell). _x000D_
_x000D_
7654 CELL OPERATION DEGRADED (at least one TX
transmitting P-CPICH is fine_x000D_
not faulty and at least one cell's Rx is working not
7653 CELL FAULTY (The cell does not have enough
faulty)._x000D_
resources (Tx/Rx) to remain operational)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (The cell has
enough resources (Tx/Rx) to remain operational)
are not assigned to any cell).


7653 CELL FAULTY (The cell cannot operate because
not enough resources are available: Tx or Rx)_x000D_
7654 CELL OPERATION DEGRADED (The cell can still
operate because it still has enough available and
needed resources: both Tx and Rx)
(HWPORT serving primary or secondary link towards
ESM failure)_x000D_
_x000D_
7652 BASE STATION NOTIFICATION (HWPORT
serving primary or secondary link towards RFM failure
and no cells affected)_x000D_
ESM failure)_x000D_
_x000D_
_x000D_
7653 CELL FAULTY (HWPORT serving primary or
7651 BASElink
secondary STATION
towardsOPERATION
RFM failure and DEGRADED
the cell has no
(HWPORT
working TX serving primary
transmitting or secondary
P-CPICH linkworking
or all not towards Rx-
ESM failure)_x000D_
es)_x000D_
_x000D_
_x000D_
7652
7654 BASE OPERATION
STATION NOTIFICATION (HWPORT
7651 CELL
BASElink
secondary STATION DEGRADED
towardsOPERATION
RFM failure and DEGRADED
the cell has no
(HWPORT
working TX serving primary
transmitting or secondary
P-CPICH linkworking
or all not towards Rx-
ESMthe cell has
failure)_x000D_
es)_x000D_
at least one working Tx transmitting P-
_x000D_
CPICH and one working Rx)
_x000D_
7652
CELL OPERATION DEGRADED (HWPORT
FlexiBTS
secondaryRel2:_x000D_
link towards RFM failure and the cell has no
_x000D_
working TX transmitting P-CPICH or all not working Rx-
and no
the cells affected)_x000D_
cell has at leastFAULTY
one working Tx transmitting
7650 BASE
es)_x000D_ STATION (channel between P-
_x000D_
optical
_x000D_ and summing devices)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (HWPORT
FlexiBTS Rel2:_x000D_
secondary link towards RFM failure and the cell has no
7651
servingBASE
primarySTATION OPERATION
or secondary DEGRADED
link towards RFM failure
_x000D_
(HWPORT
and the cellserving
has at primary
least one orworking
secondary
Tx link towardsP-
transmitting
7650 BASE STATION FAULTY (channel between
es)_x000D_
ESM
CPICH failure)_x000D_
and summing
one working Rx)
optical and
_x000D_ devices)_x000D_
_x000D_
_x000D_
FlexiBTS
7652 BASE Rel2:_x000D_
7651
servingBASE
primarySTATION OPERATION
or secondary DEGRADED
link towards RFM failure
_x000D_
(HWPORT
and the cell4-5)_x000D_
has at least
7650
and no BASE
cells STATION FAULTY (channel between P-
one
affected)_x000D_
working Tx transmitting
_x000D_
optical
_x000D_ and summing devices)_x000D_
7654 CELL OPERATION DEGRADED (HWPORT 1-
_x000D_
FlexiBTS
3)_x000D_ Rel2:_x000D_
secondary
_x000D_ link towards RFM failure and the cell has no
(HWPORT
working TX 4-5)_x000D_
transmitting P-CPICH or all not working Rx-
7650 BASE
FlexiBTS STATION FAULTY
Rel3:_x000D_ (channel between
_x000D_
es)_x000D_
optical and summing devices)_x000D_
_x000D_
7654
_x000D_CELL OPERATION DEGRADED (HWPORT 1-
_x000D_
FlexiBTS
3)_x000D_
7654 Rel2:_x000D_
7651 CELL
(SystemBASE OPERATION
STATION
Module beyond
DEGRADED
OPERATION (HWPORT
DEGRADED
alarming optical
_x000D_
(HWPORT 4-5)_x000D_
interface)_x000D_
7650 BASE
FlexiBTS
and the cell STATION
Rel3:_x000D_
has at leastFAULTY
one (channel
working Tx between P-
transmitting
_x000D_
optical
CPICH and
_x000D_ and summing
one working devices)_x000D_
Rx)_x000D_ (HWPORT 1-
7654
_x000D_CELL OPERATION DEGRADED (RF Module
7651 BASE
FlexiBTSalarmingSTATION
Rel2:_x000D_ OPERATION DEGRADED
3)_x000D_
beyond optical interface)
7651
(SystemBASE STATION OPERATION DEGRADED
_x000D_Module
FlexiBTS beyond
Rel3:_x000D_ alarming optical
(HWPORT 4-5)_x000D_
interface)_x000D_
_x000D_
7650 BASE
FlexiBTS STATION FAULTY (channel between
Rel3:_x000D_
_x000D_
7651 BASE STATIONdevices)_x000D_
OPERATION DEGRADED
optical
_x000D_ and summing
7654
(HWPORTCELLserving
OPERATION primary DEGRADED
or secondary (HWPORT
(RF
linkModule
towards1-
_x000D_
3)_x000D_
beyond
ESM alarming
failure)_x000D_ optical interface)
7651 BASE
(System STATION
Module beyond OPERATION DEGRADED
alarming optical
_x000D_
(HWPORT 4-5)_x000D_
interface)_x000D_
FlexiBTS
7652 BASERel3:_x000D_
_x000D_
_x000D_
serving primary or secondary link towards
7654 CELL OPERATION DEGRADED (RFRFM
(HWPORT failure
Module 1-
7651
and noBASE
cells STATION OPERATION DEGRADED
affected)_x000D_
3)_x000D_
beyond alarming optical interface)
(System
_x000D_ Module beyond alarming optical
_x000D_
interface)_x000D_
FlexiBTS Rel3:_x000D_
_x000D_
_x000D_
7654
workingCELL
TX OPERATIONP-CPICH
transmitting DEGRADED all (RF
or DEGRADED Module Rx-
not working
7651 BASE STATION OPERATION
es)_x000D_
(System Module beyond alarming optical
_x000D_
interface)_x000D_
7654
_x000D_CELL OPERATION DEGRADED (HWPORT
serving
7654 CELLprimary or secondary
OPERATION link towards
DEGRADED (RFRFM failure
Module
and the cell has at least one
beyond alarming optical interface) working Tx transmitting P-
7650 BASE STATION FAULTY (Master System
Module)_x000D_
(Extension System Module)_x000D_
_x000D_
7650 BASE STATION FAULTY (All FSPs in Master
System Module)_x000D_
_x000D_
7650 BASE STATION FAULTY (Master System Module
ESM failure; FSP; FBB)_x000D_
FCM, FCT)_x000D_
_x000D_
_x000D_
(Extension System Module FCM, FCT)_x000D_
_x000D_
_x000D_
es)_x000D_
_x000D_
and the cell has at least one working Tx transmitting P-

(commissioned module behind the failed HWPORT, no
LCRs affected)_x000D_
7654 CELL OPERATION DEGRADED (commissioned
module behind the failed HWPORT, LCR is
affected)_x000D_
(uncommisisoned/unknown module behind the affected
HWPORT)
7650 BASE STATION FAULTY (If all FSPs are down
BTS reset failed)_x000D_
7651 BASE STATION OPERATION DEGRADED (At
least one FSP is still operational)
7650 BASE STATION FAULTY (FCT)_x000D_
(ESM)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (ESM,
DSP)_x000D_

(ESM)_x000D_

(ESM)_x000D_
FlexiBTS:_x000D_
_x000D_
_x000D_
7651 BASE STATION OPERATION DEGARDED (FBB
_x000D_
7650 BASE STATION FAULTY (The System Module

internal communication or synchronization problem. All
signal processors inside the System Module are
unstable.)_x000D_
_x000D_
7652 BASE STATION NOTIFICATION (Retrieving the
7651 BASE STATION OPERATION DEGRADED (The
list of all parameters available in the Radio Module
System Module internal communication or
memory failed. The list is retrieved in order to check
synchronization problem, or the BTS memory operations
whether it contains the license targetId
are not stable. At least one signal processor inside the
parameter.)_x000D_
7650
System BASE STATION
Module FAULTY (There are no working
is working.)
_x000D_
baseband resources available in the BTS.)_x000D_
7653 CELL FAULTY (A critical HW/SW fault inside the
_x000D_
RF Module. All TX resources in one cell are out of
order.)_x000D_
replaceable baseband unit is faulty but some of the BTS
7650
_x000D_ BASE STATION FAULTY (The System Module
baseband resources are still working.)
internal
7654 CELL baseband bus is out
OPERATION of synchronisation.
DEGRADED Or the
(Some TX/RX
baseband
resources arebus out
related configuration of <x> was rejected
of order.)
by the HW SW, DSP )_x000D_
_x000D_
7650 BASE STATION FAULTY (A synchronization
failure in the optical RP3 interface.)_x000D_
operation is degraded in the BTS internal baseband bus
_x000D_
between the System Module and RF Module. Or the
7651 BASE STATION OPERATION DEGRADED (A
synchronization is lost in the downlink or in the
CRC failure, synchronization problems or an incorrect
uplink.)_x000D_
initialization in the optical RP3 interface. Antenna (RP3)
_x000D_
link is down.)_x000D_
7652 BASE STATION NOTIFICATION (Data corruption
_x000D_
on the System Module internal baseband bus.)_x000D_
7652 BASE STATION NOTIFICATION (The control
_x000D_
message traffic is malfunctioning between the System
7653 CELL FAULTY (The RF Module internal baseband
and RF Modules/Extension System Modules.)_x000D_
bus is out of synchronization.)_x000D_
_x000D_
_x000D_
7653 CELL FAULTY (The Small Form Factor Pluggable
7654 CELL OPERATION DEGRADED (There is a
(SFP) malfunction occurred or the SFP module is not
synchronization failure in the RF Module internal
physically present (there is no electrical connection). Or
7650 BASE STATION FAULTY (The temperature
measured from the FSM is lower than -10 degrees
Centigrade. The BTS cannot start properly, because the
FSPs cannot be powered on in too cold
conditions.)_x000D_
_x000D_
7651 BASE STATION FAULTY (if at least one FSP is
working)_x000D_
_x000D_
7650
7652 BASE STATION FAULTY NOTIFICATION (The software
(The does not
support
System/Radio the new commissioning
Module temperature file exceeds
loaded tothe the
BTS.)_x000D_
threshold value.)_x000D_
_x000D_
7651
7653 BASE FAULTY STATION OPERATION DEGRADED the (An
7650 CELL BASE STATION(The FAULTYtemperature
(The MasterinsideSystem
incorrect
specific RFcommissioning
Module is too parameter
high.)_x000D_ value or an error in
Module cannot be identified by its product code but is
the
_x000D_commissioning file. Or the transmission parameters
known by its physical device address (object_ID). Or
have
7654 not been commissioned or properly set.)_x000D_
there CELLis a System OPERATION Module DEGRADED
subassembly(The (FSP) temperature
allocation
_x000D_
inside the specific RF Module is too low or the highest
failure.)_x000D_
7651
7653 BASE
CELL FAULTY
temperature STATION
exceeds OPERATION
(There
the poweris not DEGRADED
enough
decrease HW capacity(No
_x000D_
valid
to reference
support
limit.)_x000D_ sources available.
the commissioned number TheofBTS LocalOCXO Cell is in
7651 BASE STATION OPERATION DEGRADED (A
holdover
Groups
_x000D_ mode.)_x000D_
(LCG). Or the commissioning file do not contain
subassembly (FSP) inside the System Module cannot
_x000D_
proper
7655 feature
CELL activation in place.)_x000D_
NOTIFICATION (Validated RF module
be identified by its product code but is known by its
7652
_x000D_ BASE STATION
temperature is higher NOTIFICATION
than the predefined (According to the
7650
physical BASE device STATION address FAULTY
(object_ID). (The Or BTS themaximum
unit properties
number of
synchronization
7654
allowed CELL OPERATION
value.)_x000D_ priority list, the synchronization
DEGRADED (The
data
FSPsisininvalid the BTS or missing.
is too small. Or the Or optical
there isinterface
a moduleFPGA
reference
commissioning
_x000D_ source filehas been changed
contains incorrect to another
carrier source.
candidate
file
Radio is invalid
Network or missing.)_x000D_
(RNW) configuration failure. Or a unit or
Tuning
information. follows Or this
the new reference.)file do not contain
commissioning
_x000D_
IP address initialization has failed.)_x000D_
proper
7651 BASE feature activation
STATION in place.) DEGRADED (A
OPERATION
_x000D_
7652 BASE STATION NOTIFICATION (Alarm from the
Flash
7652 memory
BASE operation
STATION failure. Or the (An BTS-internal SW
External Antenna Line NOTIFICATION
Device (ALD) is reported unsupported
as BTS
update
module has
was failed
found orinathecorrupted
BTS. SW file has
Typically, this been
happens
notification; uncommissioned source)_x000D_
detected
when a new in the moduleFlashversion
memory.)_x000D_
is installed and there is an
_x000D_
_x000D_
older BTS SW in use that does not support the new
7653 CELL FAULTY (The connection to all TX/RX
7652
module BASE version.STATION Or the NOTIFICATION
module has been ( SWconfigured as
resources related to the alarming Local Cell Resource
management
a Master System problem Module, occurred
but no on uncommissioned
Radio Module is RF
(LCR) have been lost.)_x000D_
module.)_x000D_
connected to it.)_x000D_
_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (A HW failure
7653 CELL FAULTY (The SW downloading
RFdevice.
Module to cannot
the RF be
7652
detected BASE by STATION
an antennaNOTIFICATION
line Oror(FSM)
Filter
communication
Module
identified has failed and as a result cell cannot operate
with the application MHA or TILT failed.)_x000D_physical
by its product code but is known by its
because
device
7653 of not
address
CELL FAULTY enough
(object_ID).
(LCR)available
Or anand RF needed
Module resources:
with
_x000D_
Tx or Rx)_x000D_
incompatible frequency has been detected. Or both is
7655 CELL NOTIFICATION (The antenna line device
_x000D_
sector types (A and B) are configured to the same RFa
not
7652 working
BASE properly,
STATION the configuration is
NOTIFICATION not valid or
(FSM)_x000D_
7654
Module CELL in theOPERATION
two-carrier DEGRADED
case. Or a (The
dual PA SW
RF module
given
_x000D_ parameter is incorrect. Or External Filter is missing
downloading
has been to the with
replaced RF Module
a singlehas PA failed and asand
RF module, a result
it
from
7653 Antenna
CELL line.) (FR)
cell
cannot can still FAULTY
serve operate
all cellsbecause
commissioned it still has enough
to the available
RF module.
and
Or TX needed
is faulty resources:
and thereboth is noTxworking
and Rx)TX transmitting
P-CPICH)_x000D_
7661 BASE STATION LICENCE NOTIFICATION, the
_x000D_
feature is to expire in one week or one month. This does
7654
not have CELL an OPERATION
immediate effect DEGRADED
on the BTS (The Mast Head
Amplifier
operation._x000D_(MHA) or TILT cannot be identified by its
product code but is known by its physical device
_x000D_
address
7660 BASE (object_ID).
STATION OrLICENCE
the Filter EXPIRED,
cannot be identified
the feature by
its product
has expired. code but a working TX/RX Filter exists in the
LCR. Or the Filter and/or TILT is not properly configured.
Or the power values in the cell configuration data sent
by the RNC are out of range. Or TX is faulty but at least
one TX transmitting P-CPICH is not faulty)_x000D_
_x000D_
7655 CELL NOTIFICATION (External Filter is missing
from Antenna line.)_x000D_
_x000D_
7650 BASE STATION FAULTY (all FSPs are
faulty)_x000D_
_x000D_
7650 BASE STATION FAULTY (all FSP are

faulty)_x000D_
_x000D_
_x000D_
faulty)_x000D_
7651 BASE STATION OPERATION DEGRADED (FBIA
_x000D_
7650 BASE STATION FAULTY (FCM)_x000D_

_x000D_
FBIA)
7654 CELL OPERATION DEGRADED_x000D_
(uncommissioned FR)

FCM/FCT)_x000D_
FCM/FCT, when the unit status is working)
7650 BASE STATION FAULTY (FCM/FCT in master
system module, All FSPs)_x000D_
FSPs)_x000D_
_x000D_

_x000D_
_x000D_
7653 CELL FAULTY (Otherwise)


_x000D_
_x000D_
7650 BASE STATION FAULTY (FT)_x000D_
extension FSM, FBB)_x000D_
7652 BASE STATION NOTIFICATION (FSM FAN,
external ALD, any source HW unit which is already
blocked or uncommissioned)_x000D_
7653 CELL FAULTY (FR (all critical cell resources are
lost in MHA, TILT, FA (but cell already faulty because of
other faults))_x000D_
7661
7654 BASE STATION LICENCE
CELL OPERATION DEGRADED NOTIFICATION
(FR (There is
(severity Minor/Working),
enough critical the BTS
cell resources didthe
left for notcell
receive a
to remain
response to the
operational), FF targetId verification
, MHA, TILT, request and retries
FA)_x000D_
the verification procedure. Licensed features are
_x000D_
enabled for trial period time._x000D_
_x000D_
7660 BASE STATION LICENCE EXPIRED (severity
Major/Degraded), the BTS did not receive a response to
the targetId verification request within trial period time
and licensed features have been disabled.
7653 CELL FAULTY (Antenna Line supervisiong
licenses are not available, Antenna line faulty, Cell's
primary Tx is faulty or no working Rx in cell)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (Antenna Line
supervisiong licenses are not available, Antenna line
faulty, Cell's primary Tx is working and at least one Rx is
working)_x000D_
_x000D_
7653
7652 CELL
BASE FAULTY
STATION(TX/RX is faulty and there is no
NOTIFICATION
working TX transmitting
(Uncommissioned P-CPICH and/or no working RX
source)
7654 CELL OPERATION DEGRADED (TX/RX is faulty
but at least one TX transmitting P-CPICH is fine and at
7650: MSM is alarming
least one cell's RX is working)._x000D_
7651: ESM is alarming

faulty)_x000D_
_x000D_
least one working FSP)
7650 BASE STATION FAULTY (master/single

FSM/alarming extension module has Telecom master
role)
(extension FSM without Telecom master role)
7651 BASE STATION OPERATION DEGRADED (RF
sharing - link is the slave)_x000D_
7653 CELL FAULTY (Tx/Rx served by broken optical
interface is faulty and cell has no working Tx transmitting
P-CPICH or no working Rx)_x000D_
7654 CELL OPERATION DEGRADED (Tx/Rx served by
broken optical interface is faulty but cell has at least one
working Tx transmitting P-CPICH and one working
Rx)_x000D_
7650 all FSP resources lost_x000D_

7651 not all FSP resources lost
4082:_x000D_
7650 BASE STATION FAULTY (FCM/FCT as Master, all
FSPs)_x000D_
(FCM/FCT as ESM, FSP)_x000D_
4082:_x000D_
_x000D_
7650 BASE STATION FAULTY (FCM/FCT as Master, all
4083:_x000D_
FSPs)_x000D_
7650 BASE STATION FAULTY (FCM/FCT)_x000D_
_x000D_
4082:_x000D_
4085:_x000D_
_x000D_
7650 BASE STATION FAULTY (FCM/FCT
(FCT) as Master, all
4083:_x000D_
FSPs)_x000D_
_x000D_
4085:_x000D_
_x000D_
7650 BASE STATION FAULTY (FCT)
4083:_x000D_
_x000D_
7650 BASE STATION FAULTY (FCM/FCT/FSM out of
4085:_x000D_
order/all
7650 BASE FSPs out of order)_x000D_
STATION FAULTY (FCT)
_x000D_
(extension FSM degraded, not all FSPs out of order)
7650 BASE STATION FAULTY (FCM, FCT)
7650 BASE STATION FAULTY (all FSPs in the BTS are

faulty)_x000D_
least one FSP in the BTS is operational)_x000D_
_x000D_
7650 BASE STATION FAULTY (FCM/FCT, all
FSPs)_x000D_
7651 BASE STATION DEGRADED (FSP)
7652 BASE STATION NOTIFICATION (external ALD,
Uncommissioned resource)
7655 CELL NOTIFICATION (Flexi Filter, COMB, AISG
MHA, TILT)
7650 - BTS is faulty because of the problem with file
signature._x000D_
7652 - BTS is working on current SW. New SW cannot
be activated due to file signature mismatch.
7653 Cell Faulty (if all TXs or all RXs are faulty in the
cell)_x000D_
7654 Cell Operation Degraded (all cells, which are using

the affected AAS)
7654 Cell Operation Degraded (all cells are degraded in

the affected AAS)
7653 CELL FAULTY

(Vertical Sectorization (VS) not in use; BTSOM disables
all inner cells, which are using Vertical Sectorization
without VS feature activation. Only one (outer) cell
remain operational.
Note that the Tilt per Carrier (TpC) feature also needs to
be activated to enable tilt for each cell separately.)

(Tilt per Carrier (TpC) not in use; BTSOM set both Tx
and Rx tilt values to defaults.
Tilt per Tx/Rx not in use; If (TpC) is in use then BTSOM
will set the Rx tilt value to the same as Tx. If (TpC) is not
in use, then BTSOM will set tilt values to defaults.)
7650 BASE STATION FAULTY (all FSP cards are
faulty)_x000D_
FBBx is faulty)_x000D_
7652 BASE STATION NOTIFICATION (if no LCR is

commissioned to the affected antenna line)_x000D_
7655 CELL NOTIFICATION (if at least one LCR is
commissioned to the affected antenna line)_x000D_

(Uncommissioned source) _x000D_
7653 CELL FAULTY (The cell cannot operate because
there are not enough available and needed resources:
Tx or Rx) _x000D_
7654 CELL OPERATION DEGRADED (MHA
7654 CELL OPERATION DEGRADED (The cell can still
commissioned to cell)_x000D_
operate because it still has enough available and
_x000D_
needed resources: both Tx and Rx)
7652 BASE STATION NOTIFICATION (MHA is not
commissioned to any cell served by the BTS
cell)_x000D_
The estimated phase error in holdover has exceeded 5

us.

FSM or all FSPs in the_x000D_
BTS are faulty)_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
None
7650 BASE STATION FAULTY (master FCM, all FSPs

or master FSM)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (FBIA,
extension FCM, all FSPs of extension FSM)_x000D_
_x000D_
_x000D_

_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (if at
least one FSP is working)
UltraSite, MetroSite, MetroSite 50, Triple-mode:_x000D_
_x000D_
unit is a slave WAM, WSP)_x000D_
_x000D_
7653 CELL FAULTY (TX/RX-WTR, WPA/WMP with no
redundancy)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (RX-WTR or
7650
WPA/WMPBASE with
STATION FAULTY (if all FSPs/WSPs
redundancy)_x000D_
alarm)
_x000D_
FlexiBTS:_x000D_
7651
_x000D_BASE STATION OPERATION DEGRADED
(otherwise)
7650
7650 BASE
BASE STATION
STATION FAULTY
FAULTY (if (if all
all FSPs are faulty)
FSPs/WSPs
_x000D_
alarm)
_x000D_
7651
7651 BASE
BASE STATION
STATION OPERATION
OPERATION DEGRADEDDEGRADED (if the
unit is a slave
(otherwise) FCM; if the unit is a FSP and at least one
7650
FSP isBASE STATION FAULTY (when this fault is active
working)_x000D_
for all WPS units)
_x000D_
7651
_x000D_BASE STATION OPERATION DEGRADED (single
WPS)
Carrier Resource redundancy)_x000D_
_x000D_
_x000D_
7650 BASE STATION FAULTY (if WSMF is faulty)
_x000D_
_x000D_
unit is a WSPF)_x000D_
_x000D_
7653 CELL FAULTY (TX/RX-WTR, WPA/WMP with no
redundancy)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (RX-WTR or
WPA/WMP with redundancy)
FlexiBTS:_x000D_
_x000D_
faulty)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (not
all FSPs in BTS are faulty)_x000D_
_x000D_
7653 CELL FAULTY (OptIF)_x000D_
7651 BASE STATION OPERATION DEGRADED (if no
_x000D_
working WSC or WMC)
_x000D_
7652
7650 BASE STATION NOTIFICATION (if working
FAULTY (WSMF)_x000D_
redundant
_x000D_ WSC available)
(WSPF)_x000D_
_x000D_
7653 CELL FAULTY (WSMF)_x000D_
_x000D_
_x000D_
7650 BASE STATION FAULTY
7650 BASE STATION FAULTY (Master TCOM located
in WSMF)
(WSMF does not have Master TCOM)
7650 BASE STATION FAULTY (master FCM)

(extension FCM)
FlexiBTS:

(System Module beyond alarming optical interface)
7654 CELL OPERATION DEGRADED (RF Module

UltraSite/EUBB:

Instructions
1. Check the fan and the connector._x000D_

_x000D_
2. Replace the fan module.
To clear this fault:_x000D_

1. Check the fans and the connector._x000D_
2. Replace the fan module.
Check the active fan alarms and the airflow in the BTS.
1. Download the BTS SW again._x000D_

2. FCM: Reset the BTS._x000D_
3. If Step 2 does not help, replace the alarming
module._x000D_
_x000D_
Since there are several possibilities for an alarm activation,
a BTS Clock Frequency History feature has been
developed, which enables you to access the stored history
data through the BTS Site Manager. You can use the
history data as a tool for finding out the reason for a fault or
To clear this fault, perform the following steps:_x000D_
alarm situation (for further instructions about the history
1. Make sure that the module is properly connected. If the
feature, see the online help of the BTS Site Manager).
module LED does not light up, the module is faulty. Check
Depending on the possible reason, follow the instructions
the alarming module._x000D_
below:_x000D_
For two FSM-r3 modules, also check the SRIO cable
1. Block/Unblock the alarming module._x000D_
_x000D_
connection between the system modules._x000D_
2.
1. Perform
In case of aapower-off reset._x000D_
fault in the transmission network
2. Check the fault history.
3. If step 2 does not
synchronization, youhelp,
mustreplace
correct the alarming
network module.
synchronization. The long-term accuracy of the Iub signal
must be 0.015 ppm
1. Block/Unblock theoralarming
better (check
module. theIfcorrect
that does Iub not help,
accuracy by measuring it).
replace the alarming module._x000D_ No actions on the BTS are
necessary._x000D_
2. If the fault source is FCM/FCT, check the RNC IP
_x000D_
address in the commissioning file and modify the file if
2. If the basic
needed. If thataccuracy
does notof the perform
help, Iub signal is proper but there
a power-off
1.
is Block/Unblock
too much the alarming
instability, that is, module.
the jitter If that
or wander doesisnot help,
outside
reset._x000D_
replace
the the alarming
acceptable limits, module._x000D_
you must correct the synchronization
3. If step 2 does not help, replace the alarming
2.
of If
the the fault sourcenetwork.
transmission is FCM/FCT, checkfor
The limits the RNC
jitter or IP
wander
module._x000D_
address
are in the
defined in commissioning
the ITU-T file and modify
G.823/824/825. No the fileon
actions if the
_x000D_
needed.
BTS are If that does not help, perform a power-off
needed._x000D_
1. Block/Unblock the alarming unit._x000D_
reset._x000D_
_x000D_
2. Replace the alarming unit._x000D_
3. If
Instep
case2ofdoes
a BTSnotequipment
help, replace thethe
fault, alarming
location might be
_x000D_
module._x000D_
on the:_x000D_
_x000D_
a. Transport part:_x000D_
_x000D_
- First, check the alarms of the AXC node with the AXC
Manager, or FTM and then perform the necessary
actions._x000D_
- If there are no alarms, check the AXC/FTM
synchronization settings._x000D_
_x000D_
b. WSC/FCM unit:_x000D_
1. Reset the BTS._x000D_
_x000D_
2. Check the transmission links to the RNC/Flexi Direct
RNC._x000D_
_x000D_
3. Check the BTS and RNC/Flexi Direct RNC transmission
_x000D_
settings._x000D_
2. Check the transmission links to the RNC._x000D_
_x000D_
_x000D_
4. Replace the System Module.
3. Check the BTS and RNC transmission settings._x000D_
_x000D_
2. Check the transmission links to the RNC._x000D_
3. Check the BTS and RNC transmission settings._x000D_
4. Replace the system module.
Update the compatible SW in the BTS (check the SW
versions to see the active SW version and update the
active SW version), unless it is automatically updated by
NetAct._x000D_
_x000D_
Flexi: Update compatible SW in the BTS._x000D_
NOTE: If the fault 10:EFaultId_NoConnectionToUnitAl is
Other: Update compatible SW in the BTS (check the SW
also active on the source unit, then the SW update must be
versions to see the active SW version, and update the
postponed until the fault
active SW version), unless it is automatically updated by
10:EFaultId_NoConnectionToUnitAl is canceled._x000D_
NetAct._x000D_
1. Check the NTP setting._x000D_
_x000D_
_x000D_
_x000D_
Related BTS - AXC interface: Check the SW version of the
NOTE: If also fault 10:EFaultId_NoConnectionToUnitAl is
2.
BTSCheckand the AXC,stratum parameter
and oncompatible
update the the NTP server.
SW in the
active on the source unit, then the SW update should be
AXC or the BTS.
postponed until fault 10:EFaultId_NoConnectionToUnitAl is
1. Check the file type according to the file type number
canceled._x000D_
below:
_x000D_ _x000D_
<fileTypeNumber>
Related - <fileType>_x000D_
BTS - AXC interface: check the SW version of the
BTS1and - hwConfigurationFile_x000D_
AXC, and update compatible SW in the AXC or
BTS. 2 - configurationPlanFile_x000D_
1. Retry the SW update._x000D_
3 - logFile_x000D_
_x000D_
4 - swFile_x000D_
2. Save a snapshot and check the download status from
5 - licFile_x000D_
the BTS SWDLreport in the snapshot file._x000D_
6 - measurementFile_x000D_
_x000D_
1. Retry the SW update. _x000D_
7 - rnwConfigurationPlanFile_x000D_
2. If11other flash memory-related faults in the alarming
- combinedSiteConfigurationPlanFile_x000D_
module are simultaneously active, replace the alarming
12 - allConfigurationPlanFile_x000D_
module._x000D_
14 - testResultFile_x000D_
_x000D_
15 - autoConfReport_x000D_
1. Retry the SW update. _x000D_
2. If17 - measurementPlanFile_x000D_
other flash memory-related faults in the alarming
18 - rnwMetadataFile_x000D_
module are simultaneously active, replace the alarming
19 - topologyFile_x000D_
module._x000D_
22 - togglingParFile_x000D_
_x000D_
Check23 -the mains power supply.
troubleShootingData_x000D_
[...]_x000D_
41 - AntennaParameters_x000D_
_x000D_
2. Retrythe
Check theexternal
file update a few times._x000D_
Powerline conditions and make sure
_x000D_
that there is an external power provided to the BTS.
3. Check the file server account user settings._x000D_
_x000D_
4. Check the file and path names._x000D_
_x000D_
5. Check the administration log on the file server.
Check the external Powerline conditions and make sure
that there is an external power provided to the BTS.
To cancel the alarm, unblock the unit or module.
To cancel the alarm, unblock the cell.
To cancel the alarm, unblock the BTS. Unblocking of the

BTS causes a site reset.
Check the alarm history and other active alarms of the

unit._x000D_
_x000D_
Note: This alarm does not require any (special) actions.
1. Block/Unblock the alarming unit or module._x000D_
2. Remove/Re-insert the alarming unit or module._x000D_
3. Replace the alarming unit or module._x000D_
1. Check the cell parameters in the RNC/Flexi Direct RNC

and the BTS._x000D_
2. If the parameters configured to the RNC/Flexi Direct
RNC are correct, lock and unlock all cells of this BTS using
the OMS element manager to trigger parameter sending
Replace the alarming unit or module._x000D_
from the RNC to the BTS again._x000D_
_x000D_
3. If the parameters configured to the RNC/Flexi Direct
RNC are incorrect, lock the cells and configure the
parameters to the correct values. Afterwards, unlock the
1. Upgrade the system module SW._x000D_
cells._x000D_
2.
4. Replace the unit._x000D_
If the default values for the cell parameters (such as
_x000D_
rampdown time/step) are not appropriate in the BTS,
reconfigure the BTS with the commissioning wizard.
1. Check the other active alarms._x000D_
2. Check the mains power supply.
1. Reset the alarming RF module using the block/unblock

function. If there was an internal failure or SW interruptions,
the module must be blocked or unblocked in order for it to
be restarted and reconfigured._x000D_
2. Check the cables between the system module and the
1. Reset the BTS. _x000D_
RF module._x000D_
2. If step 1 does not help, check your commissioning
3. If this does not help, replace the faulty RF module.
_x000D_
3. If step 2 does not help, replace the affected HW.
_x000D_
_x000D_
Check the signaling link settings and the RNC connections.

2. Check the number of FSP units.

2. Check the number of FSP units.
1. Lock/Unlock the cells._x000D_

2. Add more baseband capacity to the BTS or replace the
baseband unit if the reason for the lack of capacity is a
broken baseband unit.
Take the following action to clear the fault:_x000D_
_x000D_
1. Make sure that alarming RF module is properly
connected._x000D_
2. Make sure that all system modules do not have reported
Recommissioning is needed. For a dual carrier RF Module,
connection (fault 10) or synchronization (fault 3020) issues.
the lower LCR must be assigned to the lower frequency
If there are any, clear them first._x000D_
carrier.
3. Block/Unblock the RF module. If there was an internal
failure or if unit SW freezes, the module must be
If the faulty FSP is in
blocked/unblocked to the
get extension module,
it started and block/unblock
configured
the extension module. Otherwise, block/unblock the
again._x000D_
BTS._x000D_
4. Replace the alarming RF module._x000D_
_x000D_
1. Check the configuration to make sure that there are
enough resources for the minimum HSUPA
capacity._x000D_
_x000D_
2. If there are not enough resources, replace the broken
Take the following action to clear the fault: _x000D_
module or recommission the BTS and pre-reserve less
_x000D_
capacity for HSUPA._x000D_
1. Check BTS Site Manager for the received signal levels to
_x000D_
find out which RX is causing the problem._x000D_
3. Reset the BTS to get the minimum capacity pre-selection
_x000D_
Take
for thethe following
HSUPA action to clear the fault: _x000D_
in use.
2. If an MHA alarm is active, replace the MHA unit and
_x000D_
check if the RX signal level failure alarm is
1. Check BTS Site Manager for the received signal levels to
inactive._x000D_
find out which RX is causing the problem._x000D_
_x000D_
_x000D_
3. If there are antenna line devices, check them._x000D_
2. If an MHA alarm is active, replace the MHA unit and
_x000D_
check if the RX signal level failure alarm is
4. Check the antenna cables. The faulty radio module,
inactive._x000D_
antenna feeder, or antenna can be identified by locating the
_x000D_
source of the inadequate RX level on the antenna line.
3. If there are antenna line devices, check them._x000D_
Check and replace the faulty equipment or change the
_x000D_
maximum RX signal level difference
4. Check the antenna cables. The faulty radio module,
(maxRxLevelDifference) threshold (given during re-
antenna feeder, or antenna can be identified by locating the
commissioning with default value 7dB)._x000D_
source of the inadequate RX level on the antenna line.
_x000D_
Check and replace the faulty equipment or change the
Replace the alarming module/unit.
1. Make sure that the unit/module is properly

connected._x000D_
2. If the unit/module LED does not light up, the unit/module
is faulty._x000D_
3. Check the alarming unit/module.
1) When the fault is detected, a new PIC configuration is to
be provided by the BTS Site Manager._x000D_
2) If this is a repetitive problem, remove and insert the FSP
card again.
To clear this alarm:_x000D_
1) The alarm indicates that the PIC configuration has failed.
New BTS re-commissioning is needed. Commissioning
done by the BTS Site Manager / NetAct is to include PIC
pool configuration. It is recommended to do re-
FlexiBTS:_x000D_
commissioning on low traffic time._x000D_
If the faulty FSP is in the extension module, block/unblock
2) If this is a repetitive problem, then the operator must
the extension module. Otherwise, block/unblock the
restart the BTS. _x000D_
BTS._x000D_
_x000D_
1. In order to restore optimum performance, reset the BTS
manually or lock-unlock all the cells re-allocated from the
1. Block/unblock the Flexi Lite BTS._x000D_
Extension System Module to the Master System
2. Replace the Flexi Lite BTS.
Module._x000D_
2. Reset BTS._x000D_
When the fault is detected, the operator should check the
3. Re-commission BTS to use ESM for HSPA.
UARFCN configuration of the cells and the PIC pool
configuration. _x000D_
The operator should change the UARFCN of the cell at the
RNC, so there are no two cells in LCG with the same
Lack of CCCH licensed capacity on BTS (because of
UARFCN, while one is in PIC pool and the other is
insufficient number of CCCH Processing Set licenses
not._x000D_
commissioned) caused unsuccessful cell setup with
The operator should also modify the PIC pool configuration,
requested cell settings._x000D_
so that the number of PIC cells is correct (number of RX of
In order to set up the cell, the following actions can be
1. Reset cells
non-PIC FSM._x000D_
+ 2x number of RX of PIC cells <= 48).
performed:_x000D_
2. Replace the faulty unit.
1. Decrease the CCCH licensed capacity
consumption._x000D_
And/Or_x000D_
No manual action
2. Increase is required
the CCCH from the
Processing Set operator. Fault is just
licensed capacity in
to
BTS notify operator that("CCCH
commissioning Common Transportset"
processing Channel
amount)is
deleted.
_x000D_
_x000D_
Consider
1a. Checkthat BTSexists
if LCG should have
with enoughnumber
"Minimum CCCH Processing
of HS-
Set licenses loaded or received from NetAct
FACH users" which value is different then 0 and to change
whether
CCCH
there islicensed
enough capacity
hardwareaccording
resourcestotonew CCCH
allocate the
Processing Set commissioning
requested resource steps._x000D_settings.
1b. Add more hardware resources or re-commission
If the problem still occurs after five RF module resets within
"Minimum number of HS-FACH users" to a smaller
one hour:_x000D_
value._x000D_
1. Check the Antenna Line which has the inadequate RX
2a. If there isn't at least one LCG which suits point 1, then
level. Check and replace the faulty equipment._x000D_
check if an LCG exists with "Minimum number of HS-FACH
2. Replace the alarming RF module.
users" which value is equal to 0. It means that there is not
enough space to allocate the dynamic resource step due to
DCH users or/and HSUPA resource steps._x000D_
2b. Wait until traffic will decrease in the BTS or set
"Minimum number of HS-FACH users" to a value different
than 0.
To clear this fault, perform the following steps: _x000D_
When the fault is detected, a new PIC configuration has to
be provided by the BTS Site Manager with an increase in
LCGs or a reduction of the number of PIC pools to max
two. _x000D_
Take the following actions to clear the fault:_x000D_
_x000D_
1. Check the license or the feature activation state in RNC
and feature related configuration parameters in
BTS._x000D_
1. Check the other active faults. If the /rom-disk is
2. Align the configuration in RNC and BTS._x000D_
corrupted, change the alarming unit or module._x000D_
3. [RAN2518: Do Reset BTS.]_x000D_
2. Block/Unblock the alarming unit or module. Note that
_x000D_
there are no recovery actions and blocking/unblocking can
_x000D_
be performed once. If that does not help, replace the
_x000D_
alarming unit or module.
corrupted,
_x000D_ change the alarming unit or module._x000D_
Replace the faulty unit.
1. Check that bandwidths (cell/s) are the same at the BTS,

AXC and RNC._x000D_
_x000D_
2. Check the data integrity from the incoming Iub (see
Troubleshooting instructions)._x000D_
Perform the following steps until the fault is
_x000D_
resolved._x000D_
3. Check the other transmission elements' active faults (see
_x000D_
the faults for AXC document).
1. Reset the System Module._x000D_
_x000D_
FlexiBTS:_x000D_
2. Replace the System Module._x000D_
1. The FSPA is not necessarily faulty. Check also the state
of the other units. _x000D_
2. Block/unblock the FSM._x000D_
3. If that does not help, replace the faulty module (System
Note! Perform the steps below in the listed order until the
Module)._x000D_
fault disappears:_x000D_
_x000D_
Flexi BTS:_x000D_
_x000D_
1. If the alarming module is the Extension System Module
(FSM2), restart it. If the alarming module is the System
Module (FSM1), restart the BTS. _x000D_
_x000D_
2. If that does not help, replace the alarming FSM.
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
1. Download two different SW packages so that the faulty

file is removed from the BTS._x000D_
_x000D_
2. Download the SW again. _x000D_
_x000D_
_x000D_
_x000D_
FlexiBTS:_x000D_
_x000D_
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._x000D_
There are different variations of the HW that might have
limitations in the supported frequency range and
bandwidth. Check the RNC cell parameters against the
BTS HW configuration and change it if needed. It might be
due to any of the following causes: The cell frequency is
Replace the alarming module._x000D_
out of the min/max limit of the HW, the number of carriers
_x000D_
for the HW type has exceeded, or the carrier spacing limit
has exceeded._x000D_
BTS reset is needed to take the frequency channel into use
1.
and Check thethe
to clear Iubfault._x000D_
connection._x000D_
2. Check the FT status._x000D_
3. Check the connection between the FT and the FSM.
Replace the alarming module._x000D_

_x000D_
NOTE: Perform the following steps until the fault is

resolved._x000D_
_x000D_
1. Check the other alarms of the BTS and FTM, and act
accordingly._x000D_
1. Block/unblock the System Module.
_x000D_
2. If there are no other synchronization related alarms
active, start fast tuning with the BTS Site
Manager._x000D_
1. Reset the site._x000D_
_x000D_
_x000D_
3. Reset the site. Run fast tuning again._x000D_
2. If that does not help, replace the System Module.
_x000D_
4. Check the reference signal accuracy by measuring it with
a frequency counter (NOTE: requires a good timebase for
the counter). The reference signal can be found from the
Sync Out interface of the Flexi System Module, the
required accuracy is +/-0.015ppm. If the reference accuracy
is correct, run fast tuning._x000D_
_x000D_
5. If that does not help, replace the system module.
Commission the transmission with the correct parameters,
either with a commissioning file or manually.
Commission the transmission with the correct parameters,

either with a commissioning file or manually.
1. Wait until the module is automatically heated to the

required start-up temperature._x000D_
2. If the fault is active for more than two hours, check the
environmental conditions of the site.
1. Check the transmission connections._x000D_
_x000D_
_x000D_
3. If that does not help, replace the alarming System
Perform the following steps:_x000D_
Module.
_x000D_
1. Restart the MHA by taking one of the following
steps:_x000D_
_x000D_
-Toggling DC voltage on the antenna line off and
_x000D_
on._x000D_
1. Check the antenna cables and connectors running to the
-Blocking and unblocking the Flexi Radio (FR) Module.
MHA. Fix or replace any broken parts._x000D_
_x000D_
_x000D_
To recover from
-Restarting this fault, perform the following
BTS._x000D_
2. Restart the MHA by blocking and unblocking the Flexi
steps:_x000D_
_x000D_
Radio (FR) Module._x000D_
1. Check
Note: Thethe antenna
above line and
operations antenna
might affectline devices.
other antennaFixline
or
_x000D_
replace
devices the_x000D_
connected to the FR Module (and related cells), not
Note! This operation affects all the antenna lines and cells
faulty
just parts/devices._x000D_
Takethe
relatedthefaulty one._x000D_
tofollowing actions not
the FR Module, to clear thefaulty
just the fault: one.
_x000D_
If the
2. Cancel the fault by FR Module reset or BTS
_x000D_
_x000D_
alarm re-appears, replace the alarming module._x000D_
reset_x000D_
2.
1. Check
Check the
_x000D_ the antenna
antenna cables
cables,and connectors
connectors, towards
antenna, the
and
or_x000D_
MHA. Fix or replace the broken parts. _x000D_
possible
3. Restartantenna
the MHA line
bydevices._x000D_
disabling and enabling DC power on
3. Disable and enable DC power of affected antenna line
_x000D_
_x000D_
antenna lines_x000D_
Take
3. the following
(depending
Replace actions
on_x000D_
the alarming to clear the fault:_x000D_
module._x000D_
2. Check the
connected to antenna
MHA._x000D_line (TX-cable-antenna) impedance
_x000D_
the FR hardware type, the fault might be solvable by
matching.
_x000D_
1. Check the
switching the antenna
DC power cables,
off andconnectors,
on)._x000D_ antenna and
Note.
possibleAlarm can be cancelled only upon FR Module reset
_x000D_antenna line devices. _x000D_
(including
2. Check the FRantenna
hot removal), BTS reset or DC voltage
line (TX-cable-antenna) turn-
impedance
Replace
off by usertheonalarming
antenna radio
line. module.
matching.
Replace the filter unit.
Replace the filter unit.

_x000D_
1. Re-calibrate the RET antenna._x000D_
_x000D_
2. If that does not help, replace the RET unit.
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
Take the following actions to clear the fault: _x000D_
_x000D_
1. Block/unblock the Radio Module to give a power-off reset
to the antenna line devices._x000D_
_x000D_
2. If this does not help, replace the antenna line device.
_x000D_
1. Update the corresponding SW onto the device or
perform ALD power reset (for example RF
block/unblock)_x000D_
Update the SW in the BTS.
2. If that does not help, replace the antenna line
device._x000D_
1. Connect to the Extension System Module with BTS Site

Manager to check if there are optical interface alarms.
2. If there are, follow the instructions for those alarms.

Recommission the LCRs in such a way that only one sector
3. If there are no optical interface alarms, replace the
type or allowed mixed sector type is used in one RF
module.
Module.
1. Check which Radio Module is at the faulty frequency.
2. Replace the incompatible Radio Module.
1) Remove Radio Modules from the intended extension

system module and hot insert them to the intended master
system module._x000D_
2) Connect IUB connection or LMT connection to the
system module that is intended to be O&M master.
Add Radio Modules to the System Module if it is intended
to be the master System Module.
1. Check whether the heating element exists at all.

2. Check the heater control connection and make sure that
the heater is working.
3. Replace the alarming component.
Increase the number of DSP units in the BTS.
Note: Perform the following steps in the listed order until

the fault disappears:_x000D_
_x000D_
1. Download two different software packages so that the
faulty file is removed from the BTS._x000D_
Note: Perform the following steps in the listed order until
_x000D_
the fault disappears:_x000D_
2. Download the software again._x000D_
_x000D_
_x000D_
1. Download two different software packages so that the
faulty file is removed from the BTS._x000D_
Replace the single PA RF Module with a dual PA RF
_x000D_
Module._x000D_
2. Download the software again._x000D_
_x000D_
_x000D_
Alternatively, recommission the BTS with fewer cells.
_x000D_
_x000D_
2. Replace the alarming module.
_x000D_
1. Check the MHA type and configuration settings of the
BTS. If the given_x000D_
MHA requires DC voltage on the BTS2 (Diversity) port,
perform ALD commissioning_x000D_
_x000D_
properly, then reset the BTS._x000D_
1. Check the functionality of the antenna line
_x000D_
device._x000D_
2. Replace the alarming module._x000D_
_x000D_
2. Check the compatibility between the antenna line device
_x000D_
and the BTS._x000D_
_x000D_
device._x000D_
3. Make sure that the given parameters are within the valid
_x000D_
Take
range.the following actions to clear the fault: _x000D_
_x000D_
and the BTS._x000D_
_x000D_
device._x000D_
_x000D_
Take
range.the following actions to clear the fault: _x000D_
_x000D_
and the BTS._x000D_
_x000D_
device._x000D_
_x000D_
range.
and the BTS._x000D_
_x000D_
range.
_x000D_

_x000D_
1. Block/unblock the alarming unit/module._x000D_

_x000D_
2. If that does not help, replace the alarming unit/module.
Activate the appropriate license or extend the license.
1. Check and/or correct the antenna line

configuration._x000D_
_x000D_
2. If that does not help, replace the antenna line device.
Install an external filter to the antenna line.
None
None
1. Check the GPS receiver installation._x000D_

2. Check the GPS receiver status._x000D_
3. Check the connection between the GPS receiver and the
FSM._x000D_
4. If 1PPS is received from the SyncHub master BTS,
check the connection between the SyncHub master and the
alarm disappears._x000D_
SyncHub slave BTS._x000D_
_x000D_
_x000D_
1. Check the cabling (connected to Sync In
interface)._x000D_
_x000D_
_x000D_
2. Check that the 2.048 MHz reference source works
1. Confirm if the existing applied configuration is within the
normally and that the 2.048 MHz signal is
configured RF HW capabilities._x000D_
available._x000D_
2. Check the BTS connections and commissioning
Take
_x000D_the following actions to clear the fault:_x000D_
settings._x000D_
_x000D_
3. Replace the alarming module.[FlexiLiteBTS: Replace the
3. Block/Unblock the BTS._x000D_
1. Block/Unblock
Flexi Lite BTS.] the RF HW unit._x000D_
4. If the HW configuration is confirmed, then this problem is
2. If the problem persists after performing the first step,
caused by the eNB SW. Check the other active alarms.
replace the RF HW unit.
1. Block/unblock FR HW unit._x000D_
2. If problem still exists after performing step 1, replace the
FR HW unit.
Instructions are divided into three sections. Execute steps

from section chosen based on best knowledge and
common sense to minimize the cost and time effort.
_x000D_
_x000D_
There are three sets of instructions. Execute the
Section A: Check on system module side:_x000D_
appropriate set of instructions based on your best
1. Check if the connector seal is properly mounted and
knowledge to minimize cost, time, and effort. _x000D_
firmly in place. _x000D_
_x000D_
2. Check if the SFP (Small Form Factor Pluggable) is
Set A: Check the system module side:_x000D_
Take
properly theconnected/mounted
following actions to clear in thethe fault:_x000D_
System Module. If SFP
_x000D_
connection/mounting is not correct, re-adjust the
1. Confirm that the existing applied configuration is within
connection/mounting._x000D_
2. Check if the small form-factor pluggable (SFP) is
the configured
3. Check if the RF LEDHW capabilities._x000D_
indicates the faulty SFP (connected to
properly connected or mounted to the system module. If the
2. CheckModule).
System the BTSReplace connections the and ifcommissioning
SFP it is faulty._x000D_
Thereconnection
SFP are three set of instructions.
or mounting is not Execute the appropriate
correct, re-adjust the
settings._x000D_
4. Check if the optical cable is properly connected/mounted
set of instructions
connection based on your best knowledge
or mounting._x000D_ to
3.
in Block/Unblock
the SFP._x000D_ the BTS._x000D_
minimize
3. Check cost, if the time, and effort.the
LED indicates _x000D_
faulty SFP (connected to
4.
5. If the HW
Clean the configuration
optical connectors is verified,
that are then this problem
connected to SFP.is
_x000D_
system module). Replace the SFP if it is faulty._x000D_
caused
Reset RF byHW the unit
eNBby SW. doingCheck the the other activeprocedures,
block/unblock alarms.
Set
4. A: Check
Check if thethe system
optical cablemoduleisclear side:_x000D_
properly connected or
Take
_x000D_
and the following
check if this actions
solves thetoproblem._x000D_the fault:_x000D_
1. Check
mounted that
to the the connector
SFP._x000D_ seal is properly mounted and
_x000D_
firmly
5. Clean in place.
the optical _x000D_ connectors that are connected to the
1. Block/Unblock
Section B:that Check the RF HW
on radio unit._x000D_
module side:_x000D_
2. Check
SFP. Reset thetheRF small
HW form-factor
unit by pluggable (SFP) and
blocking/unblocking is
2.
1. If the problem
Check persists after
if the connector seal is performing
properly the first step,
mounted andIf the
properly
check if connected
this solves or
the mounted
problem._x000D_ to the system module.
replace
firmly in the RF HW unit.
place._x000D_
Take
SFP
_x000D_ the following
connection or actions
mounting to clear
is not the fault:_x000D_
correct, re-adjust the
2. Check
_x000D_
connection if the
or theSFP (Small Form Factor Pluggable) is
mounting._x000D_
Set B: Check radio module side._x000D_
properly connected/mounted
Block/Unblock the
LEDRF HW in the RF module. If SFP
3. Check
1. ifthatthetheconnector sealunit._x000D_
indicates is the faulty
properly SFP (connected
mounted and
connection/mounting
2.
to If the is not correct, re-adjust the
system
firmly in problem module).
place._x000D_ persists
Replace after theperforming
SFP if it isthe first step,
faulty._x000D_
replace
4. the RFthe HW unit._x000D_
2.
1. Check
Block/Unblock ifthatthe SFP optical
the isRF cableunit._x000D_
properly
HW is properly connected
connected or mountedorto
3. Check to
mounted if the the optical
SFP._x000D_ cable is properly connected/mounted
the
2. If RF
the module.
problem If
is the
still SFP connection
observed after or mountingthe
performing is not
first
in
5. the
Clean SFP._x000D_
the optical connectors that are connected to the
correct,
step, re-adjust
replace the the
RF connection
HW unit._x000D_ or mounting._x000D_
4.
SFP.Clean Reset thethe optical
RF HW connectors
unit by at RF module end. Reset
blocking/unblocking
3. Check if the optical cable is properly connected orand
the RF
check if this HW unit
solvesby doing
the problem._x000D_ procedures and
the block/unblock
mounted to the SFP._x000D_
check
Take
_x000D_ if this
the solvesactions
following the problem._x000D_
to clear the RF fault: _x000D_
4. Clean the optical connectors at the module end.
_x000D_
_x000D_
Set B: the
Check
Reset RF the HWradio unit by module side._x000D_ and check if
blocking/unblocking
Section
1. C: Check of optical
RF HWconnection:_x000D_
thisBlock/Unblock
Check
solvesthat thethe the
connector
problem._x000D_ unit._x000D_
seal is properly mounted and
1.
2. Check
If the
firmly if
in problem optical
place._x000D_ cables
persists after are not over bent.
performing theIf first
so, then
step,
_x000D_
replace
replace
2. Check the
thethat optical
RF HW SFPcable because
unit._x000D_
is properly over
connected bending or the optical
mounted to
Set C:
Takecables Check
the following the optical
actions connection._x000D_
to clearand thecan fault:_x000D_
fiber
the RF module. damages
If the the cables
SFP connection or detach oris not
mounting
1. Check
_x000D_ if the optical cables are not over bent. If yes, then
damage
correct, the connectors.
re-adjust the _x000D_or mounting._x000D_
connection
replace
1. the
Block/Unblock opticalthe cable
RF sinceunit._x000D_
HW over-bending the optical
2.
3. OPTIONAL:
Check that Test
the the
optical fiber
cable cable
is after(for example,
properly connected measureor
fiber
2. cables
Ifoptical
the problem damages the
is still observed cables and can detach
performing or
the first
the
mounted to attenuation)
the SFP._x000D_ from System Module end. Check
damage
step, the
replace connectors.
the RF HW _x000D_
unit._x000D_
the
Take measuring
the the following equipment
actions documentation for instruction
4. Optionally,
2. Clean optical
test the fiber to
connectors clear
cable at(fortheexample,
the fault:_x000D_
RF module end. the
measure
details._x000D_
_x000D_
Reset
opticalthe RF HW unit
attenuation) from bythe blocking/unblocking
system module end andand/or
checkthe if
3.
1. OPTIONAL: Test the fiber cable (for example, measure
RFCheck
this solvesthat
module the
end.the environment
problem._x000D_
Check the measuringtemperature is within
equipment the
the
limits optical
for the attenuation)
radio fromWhen RF Module end. Check the
_x000D_
documentation for module.
instruction the environment
details._x000D_
measuring
temperature
Set C: Check equipment
exceeds documentation
the limits then for
the instruction
alarm is expected
_x000D_
1. Check
details._x000D_ if fanthe or optical
air flowconnection._x000D_
is blocked by some objects.
and
1.
If the no
Check further
alarm that actions
the
still optical
isblocking observed are needed._x000D_
cables
afterare not overthe
executing bent.stepsIf yes,
from
Remove
_x000D_ any objects._x000D_
2.
theCheck
then replace
instructionthatthe the airA,flow
optical
sets is not
B,cable
and blocked
since
C, by
thesome
over-bending
replace RFMount objects
the fan or
2.
If Check
alarm if fan
still exists connector is properly mounted.
walls.
optical Remove
fiber
module._x000D_ anyafter
cables objects
damages executing
blocking theairflow
the cables steps from
andand the
canmount
detach or
connector
sections A,B, properly._x000D_
and C, replace the RF module._x000D_
module according
damage the to the instructions
connectors. _x000D_ and
3. If alarm is still observed then reset radio module by
_x000D_
recommendations._x000D_
2. Optionally, test the fiber cable (for example, measure the
block/unblock._x000D_
3. Check
optical whether excessive
attenuation) from the sunlightmodule
system is possibly causing
endmodule.
and/or the
4. If alarm is still observed then replace the fan
the
RF unit to overheat.
module end. Check Installthe ameasuring
sunshield equipmentfollowing the
_x000D_
mounting
documentation instructions and recommendations._x000D_
for instruction details._x000D_
_x000D_
If the alarm is still observed after executing the steps from
the instruction sets A, B, and C, replace the RF
module._x000D_
_x000D_
_x000D_
1. Block/Unblock the RF HW unit._x000D_
_x000D_
replace the RF HW unit._x000D_
2. If the problem is still observed after performing the first
step, replace the RF HW unit._x000D_
_x000D_
1. Check if the temperature of the environment is within the
design limits for the radio module. When the environment
temperature is out of limits, then the alarm is expected and
no further action is needed._x000D_
2. Check if any object or wall blocks the airflow. Remove
1. Block/unblock FR HW unit._x000D_
any objects blocking the airflow and mount the module
according to instructions and recommendations._x000D_
FR HW unit.
3. Check if excessive sunlight is causing overheating.
Install a sunshield following the mounting instructions and
_x000D_
1. Block/unblock the FR HW unit._x000D_
FR HW unit.
There are three sets of instructions. Execute the

appropriate set of instructions based on your best
knowledge to minimize cost, time, and effort. _x000D_
_x000D_
Set A: Check the system module side:_x000D_
1. Check that the connector seal is properly mounted and
_x000D_
1. Check that the environment temperature is within the
2. Check that the small form-factor pluggable (SFP) is
limits for a radio module. When the environment
properly connected or mounted to the system module. If the
temperature exceeds the limits then the alarm is expected
1.
SFPBlock/unblock
connection or FRmounting
HW unit_x000D_
is not correct, re-adjust the
to activate itself and no further actions are
2. If the problem
connection persists, replace the FR HW unit
or mounting._x000D_
needed._x000D_
3. Check that the LED indicates the faulty SFP (connected
2. Check that the airflow is not blocked by foreign objects or
to system module). Replace the SFP if it is faulty._x000D_
walls. Remove any foreign objects blocking the airflow and
4. Check if the
Reconnect the optical cable
alarming is properly
release 2 FR toconnected
opticalor
theand
mount the module according to instructions
mounted
interface 1.to the SFP._x000D_
5. Clean the optical connectors that are connected to the
3. Check whether excessive sunlight is causing the unit to
SFP. Reset the RF HW unit by blocking/unblocking and
overheat. Install the sunshield following the mounting
check if this solves the problem._x000D_
instructions
No action is and recommendations._x000D_
needed.
_x000D_
Set B: Check the radio module side:_x000D_
1. Check that the connector seal is properly mounted and
firmly in place._x000D_
2. Check that the SFP is properly connected or mounted in
the RF. If the SFP connection or mounting is not correct,
re-adjust the connection or mounting._x000D_
3. Check that the optical cable is properly connected or
mounted in the SFP._x000D_
4. Clean the optical connectors at the RF end. Reset the
RF HW unit by blocking/unblocking and check if this solves
the problem._x000D_
_x000D_
Set C: Check the optical connection._x000D_
1. Check that the optical cables are not over bent. If they
1. Check if the fan or airflow is blocked by some objects.
Remove any blocking objects._x000D_
2. Check if the fan connector is properly mounted. Mount
fan connector properly._x000D_
3. If the alarm is still observed then reset radio module by
1. Check if the fan or the airflow is blocked by some
objects. Remove any blocking objects._x000D_
4. If the alarm is still observed then replace the fan module.
1. Check if the environment temperature is within design
temperature is out of limits then the alarm is expected and
no further actions are needed._x000D_
2. Check if the airflow is not blocked by some objects or
walls. Remove any objects blocking the airflow and mount
_x000D_
module according to instructions and
3. Check if excessive sunlight is causing overheating.
temperature exceeds the limits, the alarm is expected and
Take
Installthethefollowing
sunshieldactions
followingto clear the fault:_x000D_
mounting instructions and
_x000D_
the module according to instructions and
temperature exceeds the limits, the alarm is expected and
Check the fans and ensure that the ambient temperature
on the sitewhether
3. Check is is acceptable.
excessive sunlight is causing the unit to
overheat. Install the sunshield while following the mounting
instructions and recommendations._x000D_
the module according to the instructions and
Instructions are divided into three sections. Execute the
steps
3. Check fromwhether
the section chosen
excessive based is
sunlight oncausing
the bestthe unit to
knowledge
overheat. Install and common senseaccording
the sunshield to minimize costs
to the and time
mounting
effort. _x000D_
instructions and recommendations._x000D_
_x000D_
NOTE: Perform the steps below in the listed order until the
fault disappears._x000D_
1. Check the optical connection between the system
module and FR module. Check SFP module(s) and/or re-
adjust optical connectors, and verify operation of any
To clear this
properly fault, perform
connected the following
to the System Module. steps:_x000D_
If SFP
devices in the optical network between FSM and FRM, if
1. VSWR measured atisRF
connection/mounting not(transmitter)
correct, readjustexceeds the the values
such devices are in use._x000D_
permitted by the RF module._x000D_
connection._x000D_
2. Block/unblock the FR module. _x000D_
2.
3. Check the if theimpedance
LED indicatesmatching of theSFP
the faulty Antenna Line to
(connected
3. If the problem still exists, reset the site by
System
the (replace
System Module).elements
Replace thatthe
causes
SFP mismatch)._x000D_
if faulty._x000D_
1. Check BTS connections
blocking/unblocking the BTS. and commisionning settings.
_x000D_
3.
4. To check if the stepscable
mentioned above solved the
2. Check
4. If
if the
Block/unblock
that does notthe
optical BTS
help,
is properly
(using
replace theSFP
the localconnected
BTS Sitetointhe
module(s) which
problem,
SFP._x000D_ block/unblock the RF module. _x000D_
Manager connection
the malfunctioning if a remote
optical connection
connection is not possible).
is terminated, and/or
*5.Forcing
Clean the theoptical
RF HWconnectors
to work underthat such conditionstomight
are connected the
replace the fiber.
result to RF the
SFP. Reset HWFR permanent
HW unit damage._x000D_
by following the block/unblock
procedures, and check if this solves the problem._x000D_
_x000D_
Section B: Check on radio module side:_x000D_
firmly in place._x000D_
properly connected to the FR module. If SFP
connection/mounting is not correct, readjust the
connection._x000D_
3. Check if the optical cable is properly connected to the
1. Check that the SFP is properly connected._x000D_
_x000D_
2. Replace the SFP module.
1. Check that the SFP is properly connected._x000D_

_x000D_
2. Replace the SFP module.
1. Check the status of the module behind the faulty link

(Power on, and so on)._x000D_
_x000D_
2. Check the SFP from both ends (the System Module and
the module behind the faulty link). The optical interface
1. Reset the RF Module with the faulty optical interface by
LED indicates the faulty SFP. Replace the SFP if it is
blocking/unblocking it._x000D_
faulty._x000D_
_x000D_
_x000D_
2. If this does not clear the fault, replace the RF Module
3. Clean the connectors, test the fiber cable, and replace it
that is causing the alarm._x000D_
Swap the links between alarming and working ports and
if faulty._x000D_
_x000D_
then
_x000D_check where the_x000D_
3. If the System Module is the only source of the alarm, or
alarm is steps
4. If the reported.
aboveIf the
do alarming
not help, port remains
replace the same,
the module
replacing the RF Module does not clear the fault, replace
replace
behind the thefaulty
System_x000D_
link.
the System Module that is causing the alarm._x000D_
Module. If the alarming port changes, replace the RF
Module behind that_x000D_
then check where the alarm is reported. If the alarming port
link.
remains the same, replace the System Module. If the
alarming port changes, replace the RF Module behind that
link.
link.
link.
link.
link.
Check the RF Module alarms.
1. Depending on the alarm source, reset the RF Module

and/or Extension System Module by blocking/unblocking it.
2. If that does not clear the fault situation, replace the RF

Module/Extension System Module that causes the alarm.
3. If the System Module is the only alarming source, or

replacing the RF Module/Extension System Module does
not clear the fault situation, replace the System Module
causing the alarm.
1. Check the cables between the System Module and RF
Module/Extension System Module._x000D_
_x000D_
2. Reset the alarming System Module._x000D_
_x000D_
Fault source FSP, FBB:_x000D_
1. Replace the unit causing the fault (System Module,
_x000D_
FBB)._x000D_
4. Replace the alarming System Module._x000D_
_x000D_
_x000D_
Fault source HWPORT:_x000D_
1. Check the cables between the Master System Module
1. Check the cables between the Master System Module
and RF Module/Extension System Module._x000D_
and the RF Module/Extension System Module._x000D_
_x000D_
2. Replace SFP at both ends of primary link. If the fault is
2. Replace the alarming unit (System Module)._x000D_
raised for one secondary HWPORT, replace the SFPs for
_x000D_
Check the antenna
the affected HWPORT mapping to the local cells in the
as-well._x000D_
commissioning
3. Replace the file.
units (System Module, RF Module)
connected with the faulty HWPORT sequentially._x000D_
1. Check the other active synchronization alarms and act

accordingly.
2. Reset the Extension System Module.

1. Check the other active synchronization alarms and act
accordingly.
2. Reset the Extension System Module.

1. Reset the alarming Extension System Module by
blocking/unblocking it.
2. If that does not clear the fault situation, replace the

alarming Extension System Module.
1. Check the status of the module with the faulty port (for
3. If the System Module is the only alarming source or
example, power on)._x000D_
replacing the Extension System Module does not clear the
_x000D_
fault situation, replace the alarming System Module.
2. Check the alarming fiber connection._x000D_
_x000D_
_x000D_
3. Replace the alarming fiber connection.
1. Switch to the latest active BTS configuration._x000D_
_x000D_
2. Retry the SW update.
Reset of FCM should be performed.
Reset of FCM/FCT must be performed.
Reset of FCM/FCT should be performed.

Reset of FCM/FCT should be performed.
1. Obtain technical logs for further analysis._x000D_

2a. If fault source is FCT, restart system module._x000D_
2b. If fault source is ESM, restart ESM.
1. Collect logs from BTS_x000D_

2a. If FCT is the fault source, perform site reset._x000D_
2d. If extension module is the fault source, restart ESM.

2a. If fault source is FCT, perform site reset._x000D_

2a. If fault source is FCT, perform site reset._x000D_
To clear from this fault, perform the following

actions:_x000D_
_x000D_
In FlexiBTS:_x000D_
_x000D_
1. Block/unblock the FSM._x000D_
1. If the alarming module is the Extension System Module
2. If that does not help, replace the faulty module (System
(FSM2), restart_x000D_
Module)._x000D_
it. If the alarming module is the System Module (FSM1),
restart the BTS._x000D_
Note:
_x000D_ Perform the steps below in the listed order._x000D_
_x000D_
2. If this does not help, replace the alarming FSM or
1. Check cables between the modules and replace them if
unit._x000D_
needed._x000D_
_x000D_
_x000D_
Note: Perform the steps below in the listed order until the
2. Resetcan
Restart thebe
System Module._x000D_
performed by BTS block/unblock, system
_x000D_
module block/unblock from_x000D_
_x000D_
3.
BTS Replace the from
SEM and System Module._x000D_
1. Block/unblock RFNetAct
HW unit.to _x000D_
reset the BTS.
_x000D_
2. If the problem is still observed after step 1 replace RF
HW unit.
BTS fault indication disappears._x000D_
_x000D_
1. Check the other active BTS faults and act
accordingly._x000D_
Note: Perform the steps below in the listed order._x000D_
_x000D_
_x000D_
2. Check if the plug-in type baseband unit is installed
1. Check other active BTS alarms and act
correctly._x000D_
accordingly._x000D_
_x000D_
_x000D_
Note:
3. Reset Perform the steps
the alarming below inunit._x000D_
baseband the listed order until the
alarm
_x000D_ disappears._x000D_
Module/Extension System Module._x000D_
_x000D_
4. Replace the alarming baseband unit.
_x000D_
1. Check the other active BTS alarms and act
3. Reset the RF Module and/or System Module, depending
accordingly._x000D_
on the alarm source:_x000D_
_x000D_
a. Reset the RF Module by blocking/unblocking
it._x000D_
Module/Extension System Module. Note that dirty optical
b. Reset the Extension System Module by
connectors can cause a significant drop in signal
level._x000D_
c. Reset the master System Module._x000D_
_x000D_
_x000D_
3. Depending on the alarm source, reset the RF Module,
4. Replace the alarming RF Module/Extension System
Extension System Module and/or System Module by
Module._x000D_
_x000D_
_x000D_
_x000D_
1. Check other BTS faults and act accordingly._x000D_
_x000D_
2. Check the ambient temperature of the BTS modules. If
the ambient temperature is too high, make sure the airflow
_x000D_
to the BTS modules is unobstructed, that is, the BTS
1. Check if the fan or the air flow is blocked by some
modules are not covered with anything. If the ambient
temperature is too low, it takes a while for the BTS modules
Note:
to heatPerform
themselves the steps
to thebelow in thevalue._x000D_
threshold listed order._x000D_
the fan connector properly._x000D_
_x000D_
3. If the alarm is still observed then reset the radio module
1.
3. Check
Reset the the alarming
commissioning parameters
module/unit with the BTS Site
by blocking/unblocking
by block/unblock._x000D_
Manager
it._x000D_ Commissioning Wizard._x000D_
_x000D_
2.
4. Load
Replace the the correct commissioning
alarming module/unit. file to the BTS.
_x000D_
1. Check the installed HW/SW version compatibility and the
HW compatibility with the current BTS
configuration._x000D_
Depending on the installed and commissioned
_x000D_
synchronization source(s) listed in section "Meaning", see
2. Make sure that the BTS cell parameters from the
the commissioned synchronization option below and
RNC/Flexi Direct RNC match the BTS HW configuration
perform the steps in the listed order until the BTS fault
(for example frequency, power)._x000D_
indication disappears._x000D_
Note:
_x000D_ Perform the steps below in the listed order._x000D_
_x000D_
_x000D_
3. Check the RNC/Flexi Direct RNC BTS faults for the
GPS receiver (PPS source):_x000D_
1. Check local
alarming othercellactive BTS faults. If the ROM disk is
(LCR)._x000D_
1. If there is a GPS receiver commissioned at the BTS site,
corrupted,
_x000D_ change the alarming module._x000D_
note the following: If the GPS receiver is not locked to any
_x000D_
4. Recommission the BTS to ensure that allorder
parameters
Note:
satellite,Perform
it turnstheoffsteps
the PPSbelow in the
signal listed
which is normally until theare
2. Reset the
correctly RF Module and/or FBIA and/or System
configured.
alarm
delivered disappears._x000D_
to the BTS (Sync In interface). The most common
Module, depending on the alarm source:_x000D_
_x000D_
reason is that the GPS receiver does not see any satellites
a. Reset the RF Module by blocking/unblocking
1. Check of
because thepoor
antenna
antenna lineinstallation
and antenna linesky
(poor devices. Make
visibility).
it._x000D_
sure
The that permanent
only the antennacure line for
connectors
this is to are in the
change right
the GPS
Note: Perform
b. Reset thethe
FBIA steps below in the listed order.
by blocking/unblocking _x000D_
it._x000D_
torque._x000D_
antenna location. One indication of a fairly poor sky visibility
_x000D_
c. Reset the System Module._x000D_
_x000D_
is that thethe BTS fault is activated/canceled every now and
1. Reset
_x000D_ site._x000D_
2. Reset the alarming RF module by blocking/unblocking
then._x000D_
_x000D_
3. Update and activate the SW to the BTS._x000D_
it._x000D_
_x000D_
2. Replace the Transport submodule, which is located
_x000D_
1)Recommission
_x000D_
2. There bethe BTS with a in correct number of LCRs
inside
4. Check themightSystem
the
a malfunction
Module.
SW files._x000D_
the GPS receiver.
per
3.
PerformRF Module.
Replace the faultypower
a (remote) parts reset
and/or fordevices
the GPS along the
_x000D_
2)Recommission the BTS with a correct number of LCRs
antenna
receiver._x000D_line._x000D_
5.
perReplace
ESM. the alarming module/unit._x000D_
_x000D_
_x000D_
4.
3. Replace
There might
Recommission the be
RF
BTS aModule.
malfunction in the BTS. Perform a BTS
(optional step)._x000D_
site
_x000D_reset._x000D_
_x000D_
Reset (block/unblock) the BTS.
4. The GPS cable and/or connectors might be damaged.
Check the cable and the connectors._x000D_
Activate
_x000D_the required license.
5. There might be a HW fault in the GPS receiver. Check
the operation and change the HW, if needed._x000D_
_x000D_
External
The affected 2.048MHz signal:_x000D_
cell automatically starts operating as a non-
1. If there is an external
MIMO cell. It does not require 2.048MHz signal source
any manual
commissioned
adjustments._x000D_ at the BTS site, check the BTS faults of that
device
The celland act accordingly.
operates as a non-MIMO If this does
cell fornotashelp,
long check
as thethe TX,
cables. Note that since the device type
responsible for the cell's transmission of S-CPICH remains is not known,
detailed
faulty._x000D_ instructions cannot be given. For further actions
refer to the
Check the other appropriate
active BTS user for
manual
faultsof theact
and device._x000D_
accordingly.
_x000D_
2. There might be a malfunction in the BTS. Perform a BTS
site reset._x000D_
_x000D_
FTM reference (TDM, SyncE or ToP as source):_x000D_
1. If there is an integrated transmission unit (FTM)
commissioned at the BTS site, note the following: the FTM
unit operates so that if it is not locked to a synchronization
Re-commission the BTS with the correct number of LCGs.
1. Block/unblock the FSM/FBB._x000D_

2. If the problem persists, replace the FSM/FBB._x000D_
_x000D_
Perform the steps below in the following order until the fault
is resolved._x000D_
Control Interface not available:_x000D_
1. The BTS has detected a malfunction in the control
interface of the GPS receiver. A possible reason could be
Replace the alarming unit/module.
the BTS and GPS receiver not supporting a common
interface. If is this is not the case, continue by performing a
(remote) power reset for the GPS receiver._x000D_
2. Perform a (remote) BTS site reset for the whole
BTS._x000D_
fault is resolved:_x000D_
3. Perform a power reset for the whole BTS._x000D_
_x000D_
4. The cable between the GPS receiver and the BTS might
1.
beReset the BTS._x000D_
malfunctioning. Make sure that the connector pins (both
2. Replace
ends of the the faulty
cable) aremodule/unit._x000D_
free frominoxide and dirt, ensuring
Note! Perform the steps below the listed order until thethe
_x000D_
best possible connection quality. _x000D_
fault disappears.
5. The cable between the GPS receiver and the BTS might
be faulty. the
1. Check Investigate and faults.
other active if necessary, change is
If the memory the
corrupted,
cable._x000D_
change the alarming module.
Note!
6. TherePerform
might the steps
be an HWbelow in the
fault in the GPS
listedreceiver.
order until the
Check
alarm
the disappears._x000D_
operation and if necessary, change the GPS
2. Reset the RF Module by blocking/unblocking it.
_x000D_
module._x000D_
1.
7. Check might
the otheran active alarms. If the memory is Module.
3. There
Replace the be alarmingHWmodule.
fault in the BTS System
corrupted,
Check the change
operation the alarming
and if module._x000D_
necessary, change the System
1. Reset the alarming System Module or unit._x000D_
_x000D_
Module.
_x000D_
2. Reset the RF Module by blocking/unblocking it._x000D_
2. Replace the alarming System Module or unit
_x000D_
Update the SW in the BTS.
1. Make sure that autoconfiguration is enabled in

NetAct._x000D_
_x000D_
2. Check the autoconnection/autoconfiguration information
with BTS Site Manager._x000D_
1. Check and correct the contents of the commissioning
_x000D_
file._x000D_
3. Load the correct commissioning file to BTS.
_x000D_
2. Recommission the BTS with a valid commissioning file.
_x000D_
1. Reset the NetAct Licence Manager. _x000D_
3. Make sure that the correct BTS licenses have been
purchased and installed.
Commissioning error. Only one System Module is to be set
as master for particular radio resource.
RP3-01 cabling from peer system modules to shared radio

module is to be corrected._x000D_
1. Block/Unblock the alarming module. If that does not help,

replace the alarming module._x000D_
2. If the fault source is FCM/FCT, check the RNC IP
address in the commissioning file and modify the file if
needed. If that does not help, perform a power-off
reset._x000D_
fault disappears.
3. If step 2 does not help, replace the alarming
module._x000D_
1.Check the other active faults. If the memory is corrupted,
_x000D_
replace the alarming module.
Reconfigure the frequency settings._x000D_
2. Reset the RF Module by blocking/unblocking it.
To clear this fault take the following actions:_x000D_

1. Check the antenna line and antenna line device that
causes the alarm. _x000D_
2. Fix or replace the faulty parts/devices._x000D_
To clear this fault take the following actions:_x000D_
_x000D_
1. Check the antenna line and antenna line device that
causes the alarm. _x000D_
2. Fix or replace the faulty parts/devices.
Perform the steps below in the listed order until the BTS
_x000D_
1. Check the SW package._x000D_
2. Download SW to the antenna line device again.
Perform the steps below in the listed order until the BTS
_x000D_
1. Check the SW package._x000D_
2. Download SW to the antenna line device again.
1. Make sure that the module is properly connected. If the
module LED does not light up, the module is faulty. Check
the alarming module._x000D_
For two FSM-r3 modules, also check the SRIO cable
1. Manually reset the BTS.
connection between the system modules._x000D_
2. If the alarm is still visible after the BTS reset, replace the
alarming FSM module.
_x000D_
1. Reset the NetAct Licence Manager. _x000D_
3. Check the BTS license situation: the correct licenses
have been purchased_x000D_
and installed.
_x000D_
1. Check the antenna lines: antennas, antenna cables,
connector torques, and antenna line devices._x000D_
2. Check the antenna line (TX-cable-antenna) impedance
Replace the unsupported module or upgrade the System
matching.
Module SW.
Note! Perform the steps below in the listed order._x000D_

1. Check if other BTS fault indications are active. _x000D_
2. Make sure that all RP3-01 fiber links and SFP
transceivers between system module and radio module are
properly connected and working. Add missing parallel RP3-
01 links._x000D_
fault disappears.
3. Restart the Radio Module._x000D_
1. Block/unblock the BTS.
4. Restart the BTS.
2. Replace the alarming unit.
_x000D_
2. Replace the faulty module/unit.
_x000D_
1. Check the RS485 IUANT interface and antenna line
devices. Fix or replace the faulty parts/devices._x000D_
_x000D_
Note! Perform the steps below in the listed order.
2. Alarm is canceled only at the RF module reset or a BTS
1. Check the fans and ensure that the ambient temperature
reset.
on the site is acceptable.
2. If that does not help, replace the alarming module.
Replace parallel RP3-01 fiber links towards one radio
module so that the maximum mutual length difference
between fibers is less than 60 meters.

1. Check the fan and connector._x000D_
2. If step 1 does not help, replace the fan.
Perform the steps below in the listed order until the fault
disappears:_x000D_
_x000D_
1. Either activate the required license for 15 km distributed
site or switch to a shorter fiber between FSM and
FR._x000D_
_x000D_
2. Restart FSM.
1. Check the fans and ensure that the ambient temperature
on-site is acceptable._x000D_
2. If that does not help, replace the alarming module.
_x000D_
1. Make sure the fan is not blocked._x000D_
_x000D_
2. Make sure the fan connector is properly
mounted._x000D_
_x000D_
3. If that does not help, replace the fan.
_x000D_
1. Make sure the fan is not blocked._x000D_
_x000D_
2. Make sure the fan connector is properly
Replace the fan(s).
mounted._x000D_
_x000D_
3. If that does not help, replace the fan.
1. Reset the System Module.
2. If a reset does not resolve the fault situation, replace the

System Module.
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._x000D_
NOTE: In case BTS Element Manager detects an incorrect
SW version, the BTSSM should be reconnected.
Re-commission the BTS with a correct number of fixed BB
allocation based LCGs so that every FSM has an LCG.

_x000D_
1. Make sure that the unit/module is properly connected.
_x000D_
_x000D_
Update SW to the BTS, unless it is automatically updated
2. Reset the alarming unit._x000D_
by NetAct.
_x000D_
3. If step 2 does not help, replace the alarming unit.
None

System Module.
NOTE: Perform the steps below in the listed order until the
1. Change the BTS configuration._x000D_
2. Reset the BTS.
Check the faulty FSP.
Replace the faulty unit.
1. Check the QSFP (SRIO) cable between the modules.

2. Replace the cable.
Enable power feeding towards Radio Module by switching

RF power on in BTS Site Manager.
None
Check the optical connection between master and peer

system modules.
Perform the steps below in the listed order until the fault
disappears._x000D_
_x000D_
Not tracking satellites:_x000D_
1. The most common reason for this fault indication is the
Perform the following steps in the listed order until the fault
GPS antenna installation that was not done properly, which
disappears._x000D_
makes the sky visibility not good enough. See
_x000D_
documentation for installations .If there are discrepancies
Survey in progress:_x000D_
with the actual installation, re-install the GPS antenna.
1. Do nothing. The alarm is informative only. Normally, the
Perform
NOTE: Even the stepswhenbelow the GPS in the listed order
antenna has a until
goodthe skyfault
GPS receiver runs the survey for two reasons: a)
disappears._x000D_
visibility, the problem might be due to installation of the
somebody has started the survey manually; b) the GPS
_x000D_
GPS antenna that is too close to the transmitter antenna(s)
receiver has detected that the position has changed, and
No
of thestored
BTS,position:_x000D_
causing disturbances to the GPS receiver.
the receiver has started an automatic survey. NOTE: An
1. One of the GPS receiver settings is incorrect. Using the
_x000D_
Perform the
automatic following
survey takes steps
place in every
the listed timeorderduring until
thethefirstfault
manager
_x000D_ SW of the GPS receiver, set the receiver to store
disappears._x000D_
start-up._x000D_
the
2. position
There might intobe non-volatile
a malfunction memory. in the _x000D_
GPS receiver.
_x000D_
2. If an automatic survey takes place every now and then, it
If there isano
Perform tick mark
(remote) powerin theresetposition
for the storage
GPS selection, the
Position
might bequestionable:_x000D_
an indication that the sky visibility is poor, and
GPS receiver runs the site/self survey every time the GPS
receiver._x000D_
1. The on
based GPS receiver
thefollowing has valid
poorly tracked position the dataGPS but receiver
it is not
Perform
receiver
_x000D_ the
is reset (eithersteps insatellites,
by manager the listed order until
command, powerthe fault
properly aligned
concludes that thewith the information
position has changed. estimated
In thisfrom
case, the
disappears._x000D_
outage,
3. There or a GPS
might be recovery
a HW reset).
fault in the This
GPS means thatCheck
receiver. if the
actual
check satelliteofvisibility.
activity other The (BTS
faults reason faultfor history
this fault indication
data). If
_x000D_
GPS
the receiver and
operation installation
change quality
the GPS is only
module average, and
if needed.
might
feasible, be re-install
that the GPS the antenna
GPS installation
antenna._x000D_ has not been
EEPROM
mostly if the invalid:_x000D_
installation is a poor one, the GPS receiver
done
3. If properly,
the GPSreceiver which makes
installation is the sky
good but visibility not good
still an automatic
1. The
turns GPS
the PPS reference hasOFF detectedevery a nowmalfunction
andisthen induring
the
Check iftakes
enough.
survey the
Refer assigned
to the
place Rx nowcarrier
documentation
every and bandwidth
then, supported
for instructions,
there might andaby
be if
EEPROM
the site memory
survey. This ofmeans
the GPS that receiver.
the BTS Perform
master a (remote)
clock
the
there given
malfunction RFinmodule
are deviations the GPS and
with change
the
receiver.actual it installation,
if needed.
Perform a re-install
(remote) power
power
drops reset
to for themode
holdover GPS much receiver._x000D_
easier during the survey than
BTS
the
reset reset
GPS is GPS
antenna.
for the needed to take
Notice thatthe even changed
when Rx the carrier
GPS antenna
2. There
during themight
normal be receiver._x000D_
a HW fault in the GPS receiver. Check
operation.
bandwidth
has
4. athegood into
skyuse and to
visibility, clear
the problemthe fault.mightdid benot
duecorrect
to
theIfoperationactions anddetailed
change in previous
the GPS module steps if needed.
installation
the situation, of there
the GPS might antenna
be a HW thatfaultis too close
in the GPS to the
transmitter
receiver. Check antenna(s) of the BTS,
the operation causing the
and change disturbances
GPS module to
the GPS receiver. _x000D_
if needed.
2. There might be a malfunction in the GPS receiver.
Perform a (remote) power reset for the GPS
receiver._x000D_
3. There might be a HW fault in the GPS receiver. Check
the operation and change the GPS module, if needed.
Check if the assigned Tx carrier bandwidth is supported by
the given RF module and change it if needed.
BTS reset is needed to take the changed Tx carrier
bandwidth into use and to clear the fault.
Check if the assigned carrier separation is supported by the
given RF module and change it if needed._x000D_
The fault is to be canceled after the operator sets the
correct UARFCN to the cells so that carrier separation is
within the correct range._x000D_
No action required from the operator.
A BTS reset is needed to take the changed carrier
separation into use and to clear the fault.
Trigger SW update for BTS to the requested SW version.
Depending on the installed and commissioned

synchronization sources, see the commissioned
synchronization option below and perform the steps in the
listed order until the BTS fault indication
disappears._x000D_
Check the number of required AAS vertical sectorization
_x000D_
licenses and install licenses if required.
GPS receiver (PPS source):_x000D_
Check
3. Check thethe
number of required
connection betweentilting
theper
GPScarrier licenses
receiver and
and install licenses if required. If additional licenses are not
FSM._x000D_
available,
_x000D_ then in order to cancel the alarm update
commissioned
FTM reference tilt values
(ToP to 0.
as source):_x000D_
1. Check that the signal
Check the number of required is being received
tilting from the
per TX/RX ToP
licenses
Master._x000D_
and install licenses if required. If the needed licences are
2.
notCheck the FTM
available, status._x000D_
in order to cancel the alarm set the RX tilt to
3. Check the synchronization
the same value as TX. settings of the FTM unit.
Extended logging mode as streaming AaSysLog prints into

ramdisk may decrease performance of the BTS. In critical
case, disactivate/stop the extended logging mode with BTS
Site Manager.
Note: Perform the steps below in the listed order.
1. Check and correct the commissioning parameters with

the BTS Site Manager Commissioning Wizard.
2. Load the correct commissioning file to the BTS.
[FSMr3+FSMr2] Re-commission BTS to use Extension
System Module._x000D_
[FSMr3+FSMr3] Reset BTS. Extension System Module is
used automatically, unless there is no LCG assigned to it -
in such case re-commission BTS to use new Extension
1. Check if other BTS fault indications are active. _x000D_
System Module.
2. Make sure that all SFP transceivers between the system
module and the extension system module support the
required line rate. _x000D_
3. Restart the BTS.
_x000D_
1. Check other active alarms. If the memory is corrupted,
change the_x000D_
If the fault persists after a BTS reset, replace the alarming
alarming module._x000D_
module or plug-in FSP.
_x000D_
2. Reset the RF Module by blocking/unblocking it._x000D_
_x000D_
This is an indication
3. Replace of anmodule._x000D_
the alarming uncontrolled BTS reset. No
actions
_x000D_ needed.
4. Restart the BTS.
Set correct VSWR threshold values using VSWR tuning or

recommission the BTS with VSWR threshold supported by
the Radio Module.
Check and correct the contents of the commissioning file if

needed.
Note! Perform the steps below in the listed order:_x000D_

1. Check cabling instruction for the faulty module._x000D_
2. Make sure that all RP3-01 fiber links and SFP
transceivers between the system module and the radio
module are correctly connected and working
1. If MHA is shared between two BTSs (via separate AISG
properly._x000D_
port for each BTS):_x000D_
3. Correct fiber cabling._x000D_
¿ Check if MHA is not switched to bypass mode by
4. Restart the BTS._x000D_
another BTS for all BTS. _x000D_
¿ Check if MHA is not switched to bypass mode by other
1. Reset the Site._x000D_
BTS._x000D_
2. Perform SW update.
2. IF MHA is not shared between two BTSs:_x000D_
¿ Reset the BTS._x000D_
¿ Replace alarming unit._x000D_
If GPS is configured as reference clock, perform the
following:_x000D_
3. Check the connection between the GPS receiver and
Source: _x000D_
FSM.
- FCM/FCT: Perform eNB reset._x000D_
- FSP: Change cell configuration to decrease call
processing load._x000D_
fault is resolved._x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
N/A
Confirm the changes when all the required BTS IP settings

have been made.
1. Check the configured DSCP value ranges in the RNC.
2. Check the configured DSCP value ranges in the BTS.
3. Ensure that both match each other.

1) Check if the far end has BFD switched on.
2)Check cabling and network connections to the far end.
Check and delete any unwanted manual route entries in the

forwarding table.
E1 interfaces: Check that the interface type of the far-end

interface is also configured to be a framed E1 interface. If
this is not the case, reconfigure the interfaces so that they
match each other.
1. Check that the cables are connected to the correct
JT1 interfaces: Check that the interface type of the far-end
connectors.
interface is also configured to be a JT1 interface. If this is
not the case, reconfigure the interfaces so that they match
2. Check that the interface at the far-end interface is
each other.
switched on.
connectors.
3. Check whether there are active alarms at the far end. If
there are, follow the instructions for handling those alarms.
switched on.
Switch the loopback
4. To verify off or waitoffor
that the hardware the
the timeoutunit
interface to expire.
works
This opens
correctly, the loop
connect whichcable
a loop cancels
and the alarm.
check whether the
alarm disappears.
Insert a valid SFP module.

1. Ensure that the far end is using ATM cell mapping.
2. Check whether any other alarms concerning the fault are

on. If this is the case, follow the instructions on handling
those alarms.
Use the BTS Site Manager to check which interfaces have
been configured as synchronization sources.
3. If the alarm is on only temporarily, no action is needed.
For the PDH interfaces, do as follows:
Use BTS Site Manager to check which interfaces have
been configured as synchronization sources.
connectors.
For the PDH interfaces, do as follows:
2. Check whether the interface at the far end is switched
Check
on. the configuration of either MinUDPPortCESoPSN or
MinUDPPort.
connectors.
there are, follow the instructions on handling those alarms.
2. Check whether the interface at the far end is switched
1.
on.Check that the cables are connected to the correct
4. To verify that the hardware of the interface unit works
connectors.
correctly, connect a loop cable and check whether the
alarm
2. disappears.
Check
there are,that thethe
follow interface at theon
instructions far-end interface
handling thoseisalarms.
switched on.
4. To verify that the hardware of the interface unit works
connectors.
3. Check whether
correctly, connect there
a loopare active
cable andalarms
check at the farthe
whether end. If
there
alarm are, follow the instructions for handling those alarms.
disappears.
switched on.
1.
4. Check that the cables are
the configuration ofconnected
the relatedtoCESthe pseudowires.
correct
connectors._x000D_
_x000D_
switched on._x000D_
Execute
4. Checkgeneral configuration
the configuration checks:_x000D_
of the CES pseudowire.
_x000D_
- Configuration of CMP server IP address and port and
DNS server IP address_x000D_
there are, follow the instructions for handling those
- Configuration of routing entries towards remote
alarms._x000D_
peers_x000D_
None.
_x000D_
- Configuration of IPSec policies towards remote
4. Check the configuration of the CES pseudowire.
peers_x000D_
_x000D_
Check remote peers and intermediate network elements
interconnections._x000D_
1)Check
Check the cabling
LDAP and networktowards
connection connections to the far
the Certificate
end._x000D_
Revocation List server._x000D_
2)Check
Check DNS Linknames._x000D_
OAM event- and Link OAM state
information._x000D_
Check the size of the file at the Certificate Revocation List
3)Check
server. Ethernet interface configuration at local and
1)Inspect details of the type of the critical event through
remote side._x000D_
online configuration management._x000D_
4)Insert a Link OAM loopback.
2)Check Link OAM state information of the
interface._x000D_
3)Check cabling and network connections to the far
Replace the faulty SFP. Note that only the SFP might be
end._x000D_
faulty, not necessarily the entire hardware unit.
4)Check Ethernet interface configuration at local and
remote side._x000D_
5)Insert a Link OAM loopback.
Check the cabling towards the TWAMP responder. Check
the configuration of the TWAMP responder.
1) Check cabling
2) Check the configuration of the static routes towards the
neighbor
Check the intermediate transmission network for alarms

indicating the root cause and follow the instructions for
handling these alarms.
1. Check the intermediate transmission network for alarms

2. To check the transmit hardware, connect a loop cable

1. Clean the cables and connectors.
and check that LOS alarm is not raised.
2. Check that the connectors are properly connected to the
unit.
Check the intermediate VC-12 transmission network for
3. Check that the cable connected to the interface in
alarms indicating the root cause and follow the instructions
question is not damaged and is within the specifications.
for handling these alarms.
4. Follow the signal in the network and check whether any
Check the intermediate
other alarms concerningtransmission
the fault are network
on (suchforasalarms
Laser
indicating theIfroot
End of Life). this cause and follow
is the case, followthe
theinstructions
instructionsfor
for
handling these
those alarms.
1. Check the configuration and ensure that the cross-

connections between the nodes have been properly
configured for transporting traffic.
2. Ensure that the Path Payload Label for the VC-3/VC-4 at

Ensure that the path payload label for the VC-3/VC-4 at the
the far end is configured to be "ATM".
far end is configured to be "ATM".
3. Follow the signal in the network and check whether any
other alarms concerning the fault are active. If this is the
1. Check
case, thethe
follow intermediate transmission
instructions for handlingnetwork for alarms
those alarms.

Check that the configured interface type matches the
and check that LOS alarm is not raised.
configured interface type of the far end. If this is the case,
the problem is somewhere in the transmission network.
Check the intermediate transmission network for alarms

1. Check the intermediate transmission network for alarms

Do as follows for the interface referenced in the alarm text:
and check that no alarms appear for this interface.
1. Verify that the IMA configuration of the near end and far
end is correct.
Do as follows for the interface referenced in the alarm text:
2. Check the physical line for errors.
1. Verify that the IMA configuration of the near end and far
end is correct.
Follow the instructions for handling the alarms raised at the
2. Check the physical line for errors.
far end of the IMA link.
3. Check the delay of the IMA link in question. If necessary,
select another suitable link.
Ensure that the IMA link is configured to be part of an IMA
group.
Ensure that the far-end IMA link is configured to be part of

an IMA group.
If the alarm is on only temporarily, no action is needed.
If the alarm stays active, check whether any other alarms

related to this fault are on (such as problems on individual
IMA links). If this is the case, follow the instructions for
Check that the configurations at the near end and far end fit
together (for example, IMA version and frame length).
Change the configuration, if necessary.
Check that the configurations at the near end and far end fit
together (for example, IMA version and frame length).
Change the configuration if necessary.
1. Check the individual IMA links in the IMA group for

problems. Correct them if necessary.
2. Configure additional IMA links to the IMA group.

1. Check the individual IMA links in the IMA group for
3. If feasible, reduce the minimum number of IMA links in
problems. If needed, correct them.
the IMA group.
2. Configure additional IMA links to the IMA group.
4. Check that the configurations at near end and far end fit
The IMA group
together. Change reconfigures automatically.
the configurations If the alarm
if necessary.
3. If feasible, reduce the minimum number of IMA links in
remains active, do as follows:
the IMA group.
1. Check the delay of the links. Special measurement
4. Check that the configurations at the near end and far
equipment might be needed for this. Take appropriate
end fit together. Change the configurations if necessary.
actions to reduce the delay.
2. If the IMA link is used over a leased line, the problem

might be located in the leased line network. In this case,
the operator should be contacted.
Replacing faulty hardware:_x000D_
1. Re-Plug in the expected transport unit referenced in the
alarm text._x000D_
_x000D_
2. In case there is a unit present in the slot, remove it from
Check the configuration of the far end
the slot_x000D_
and plug it back in. If the unit is still not recognised and the
alarm_x000D_
remains, replace the faulty unit with a new one. _x000D_
Check
_x000D_ the configuration and corresponding alarms on the
far end.
De-commissioning previously commissioned
hardware:_x000D_
1. Re-commission to remove the hardware unit referenced
in
Allthe alarmdown
session text._x000D_
due to out of order or unplugged cable or
_x000D_
interface down _x000D_
NOTE: Before re-commissioning, the hardware unit must
not be present in the slot._x000D_
1. Check that there are no other active alarms on the

physical or ATM layer._x000D_
_x000D_
2. Check that the RNC is up and running._x000D_
_x000D_
Collect a snapshot and send to R&D for analysis. Restart
3. Check the AAL2 configuration. For example, make sure
the site at the earliest possible time
that the VPs/VCs used for AAL2 signalling in the RNC and
WBTS match.
Download a valid license to the WBTS.
1) Check the cabling._x000D_

2) Check the CCM configuration at the remote peer.
1) Check cabling.
2) Check configuration at remote peer.
Check your username and password.
Provide the certificate.
Check that the Pseudowire configuration is complete.

Check that the Pseudowire configuration is complete.
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 peers match.
Check the BFD configuration at local end.
Try with local management or site support equipment.
check the connectivity to NTP server

check the NTP server configuration at BTS.
Check if there is a missing or short end device.

Make sure that a compatible and functional powered device
is connected.
Check if there is a problem with the cable.
Check the vendor BTS certificate expiry date and extend it.
Check link breaks.
Update trust anchors.
This alarm is because of FTM_IPCP or FTM_LCP alarms.
1. Confirm that SyncE is desired as a synchronization

source._x000D_
2. Confirm that configuration settings for ssmEnabled is
correct._x000D_
3. Troubleshoot with Backhaul provider on the reason SSM
1. Confirm that SyncE is desired as a synchronization
errors._x000D_
source._x000D_
2. Confirm that SBTS configuration settings for ssmEnabled
is correct._x000D_
3. Troubleshoot with Backhaul provider on the reason SSM
errors._x000D_
Check the cable connectivity.
Check the TOP configuration.
SW upgrading:
- Upgrade the FSM SW release to the latest version that
includes the support for the new external tranport device
variant.
1.Configure the threshold value lower compared to the
Unit variant replacement:
actual frame loss ratio. _x000D_
- Replace the unsupported device variant to another one
2.Check whether there are active alarms at the far end and
that the currently running SW release supports.
near end. If yes, follow the instructions for handling those
alarms._x000D_
1.Configure the threshold value lower compared to the
actual average two way delay threshold._x000D_
_x000D_
2.Check whether there are active alarms at the far end and
near end. If_x000D_
1. Configure the threshold value lower compared to the
yes, follow the instructions for handling those
actual average one way_x000D_
alarms._x000D_
delay threshold._x000D_
_x000D_
2. Check whether there are active alarms at the far end and
None
near end. If_x000D_
yes, follow the instructions for handling those
alarms._x000D_
An IP Traffic Capturing session is ongoing and base station

traffic is captured to a local Ethernet interface or into a file
on the base station.
Set the correct power values to the RNC.
None_x000D_

_x000D_
_x000D_
1. If only one FSP/FBB in the BTS generates this alarm, the
3. Replace the System Module or FBIA.
FSP/FBB is faulty._x000D_
2. If all FSPs generate this alarm, the FSM is
faulty._x000D_
3. Block/Unblock the FSM._x000D_
Reset the BTS.
4. If that does not help, replace the faulty module (system
module) or the faulty FBB._x000D_
_x000D_
Instructions are divided into three sections. Execute steps
from section chosen based on the best knowledge and
common sense to minimize the cost and time effort.
_x000D_
_x000D_
Baseband reset must be performed.
In multiple
properly system modules case:_x000D_
connected/mounted in the System Module. If SFP
1. Check the QSFP (SRIO)
connection/mounting cable between
is not correct readjustthe the
modules._x000D_
2.
3. Reset
Check the if theSlave
LEDModule._x000D_
indicates the faulty SFP (connected to
3. Replace
System the cable._x000D_
1. Reset the BTS_x000D_ the SFP if it is faulty._x000D_
Module). Replace
_x000D_
4. Check if the optical cable is properly connected/mounted
_x000D_
In
in baseband
the SFP._x000D_ sub-module case:_x000D_
2. Replace the FBB/FSM.
1.
5. Check
Clean the the optical
connection of the sub-module._x000D_
connectors that are connected to SFP.
2. Reset
Reset FRthe HWsub-module._x000D_
unit by block/unblock procedures and check
UltraSite,
3. Replace
if this solves MetroSite,
the MetroSite 50, Triple-mode,
thesub-module._x000D_
problem._x000D_
_x000D_
_x000D_
Section B: Check on radio module side:_x000D_
Block/unblock
1. Check if the the alarming
connector unit.
seal is Ifproperly
there was an internal
mounted and
failure,
firmly in the unit needs to be blocked/unblocked to get it
place._x000D_
Commission a smaller amount of PRACH preamble
initialized/configured
2. Check if or thecellSFP again._x000D_
(Small Form Factor Pluggable)
signatures range to modified cell size to one is
_x000D_
properly connected/mounted in the FR module. If SFP
supported by BTS.
UltraSite/EUBB:
connection/mounting If theisalarming
not correctunitreadjust
is WSPF, theblock/unblock
the EUBB subrack._x000D_
UltraSite,
3. Check ifMetroSite,
_x000D_ the opticalMetroSite 50, Triple-mode:
cable is properly connected/mounted
FlexiBTS:_x000D_
in the SFP._x000D_
1.
4. If
_x000D_ping the
Clean to the BTSconnectors
optical is working, at restart the BTS
FR module remotely.
end. Reset
1.
FRReset
HW unit the by BTS. _x000D_ procedures and check if this
block/unblock
2. Ping
If step
solves the
the BTS. not
1MetroSite,
does If it help,
problem._x000D_is notcheck
working your butcommissioning
ping to the AXC is
UltraSite, MetroSite 50, Triple-mode:
working,
_x000D_restart the AXC remotely so that the BTS is also
automatically
3. restarted.
1. If
If step
SectionpingC:2 does
toCheck
the BTS not
of help,
opticalreplace the affected
the BTSHW.
connection:_x000D_
is working, restart remotely.
1. Check if optical cables are not over bend. If so then
3. Ping the
replace the AXC.
optical If it is not working, visit the site and restart
2. Ping the BTS. If cable
it is notsince overbut
working bending
ping to thetheoptical
AXC is
1.
the Check
fiber BTS. the
If thisother
does active
not alarms.
help, replace the detach
alarming WAM
working, restart the AXC remotely so that the BTSoris also
cables damages the cables and can
unit.
damage the connectors.
automatically restarted. _x000D_
2.
2. Check
OPTIONAL: the units Testthat
theare supplied
fiber by the
cable (f.ex. alarming
measure theWPS.
FlexiBTS:
optical attenuation) from System Module end. Please check
3. Ping the AXC. If it is not working, visit the site and restart
3. Check the
measuring backplane
equipment connectors and
documentation for cables.
instruction
1.
theDisconnect
BTS. If thisthe doesexternal cables
not help, replaceand check whether
the alarming the
WAM
1. Reset the BTS.
details._x000D_
alarm
unit. disappeares.
4.
3. Replace
OPTIONAL: the Test
alarming WPScable
the fiber unit. (f.ex. measure the
2. If
optical
2. the BTS
attenuation)reset does
from not
FR help,
Module
Check the external cables and connections. change the alarming
end. Please check
FlexiBTS:
module.
measuring equipment documentation for instruction
Check the WID connection and replace the WID, if
details._x000D_
3.
1. If the alarm
Reset the BTS. does not disappear, check the WEA and
necessary.
_x000D_
replace it if it is faulty.
If alarm
2. If the isBTS stillreset
observed
does after executing
not help, change steps from sections:
the alarming
A,B,C
module. replace the FR module._x000D_
Recommission (Reconfiguration commissioning) the BTS
with the correct carrier candidate values.
FlexiBTS:_x000D_
Replace the alarming module/plug-in FSP._x000D_
_x000D_
Replace the Flexi Lite BTS.
1. Run fast tuning with BTS Site Manager.
2. Block/unblock the alarming unit.
3. Replace the alarming unit.

An appropriate license should be provided to BTS.
Note that because of a fault situation in the active clock, the
redundant clock is not tuned. To make sure that the tuning
is correct, run "Fast Tune BTS Clock" with BTS Site
Recommission
Manager after the(Reconfiguration commissioning)
switchover when the new WSCthe BTS
is taken
with the correct
into use. If therecarrier candidate
is a WMC or onlyvalues.
one WSC, the tuning
continues but the cells remain disabled.

System Module.
1. Depending on the interface, reset the connected

module/unit behind the interface that causes the alarm by
blocking/unblocking it.
2. If that does not clear the fault situation, replace the

1. Check and correct the contents of the commissioning
connected module/unit behind the interface causing the
file.
alarm.
2. Download the corrected commissioning file to the BTS
FlexiBTS:
and reset it.
Perform the steps
3. If the System belowisinthe
Module theonly
listed ordersource,
alarm until the
orfault
disappears:_x000D_
replacing the RF Module/Extension System Module does
1.
notEither
clear activate
the fault the required
situation, license
replace theforSystem
15/40 kmModule
distributed
causing thesite or switch to a shorter fiber between FSM
alarm.
and FR._x000D_
2. No need to restart FSM.
UltraSite/EUBB:
3. If WSMF is the only alarm source, or replacing the
connected module/unit does not clear the fault situation,
replace the WSMF that causes the alarm.
Related Faults
3050
3050
3040
3090, 3013
3000, 3030, 3100, 3511, 3013
3070
3000, 3070, 3013
3000, 3070, 3013
3000, 3013
3090
3090
3090
3000, 31850, 31851, 3013
3060
3070
3070
3010
3000, 3070, 3013

3000, 3070, 3013
3000, 3070, 3013
3010
3000, 3013
3000, 31851, 3013
3000, 3013
3000, 3013
3000, 3090, 3013
3000, 3090, 3013
3000, 3090, 3013
3000, 3090, 3013
3000, 3090, 3013
3000
3000, 3013
3000, 3013
3090
3090
3000, 3030, 3100, 3013
3070
3000, 3020, 3013
3080
3000
3000
3060
3060
3040
3511
3010
3010
3010
3100
3090
3030
3070
3070
3070
3070
3070
3090
3090
3070
21236
3100
3100
3100
3100
3000
3000
3000, 31851, 3013
3070
3080
3080
3010
3010
3010
3010
3010
3010
3010
3050
3010
3010
3010
3010
3010
3010
3050
3050
3050
3050
3040
3030
3030
3030
3030
3030
3030
3030
3030
3030
3030
3030
3030
3030
3000, 3020, 3013
3020
3000, 3020, 3013
3030
3030
3030
3000, 3020, 3013
3000, 3020, 3013
3000, 3020, 3013

3000, 3020, 3013
3000, 3013
3000, 3013
10, 4052, 10, 4052, 16, 13, 15, 4040, 13, 15, 4040, 13,
15, 4040, 9052, 9052, 9055, 69, 109, 110, 111, 109,
110, 111, 109, 110, 111, 109, 110, 111, 214, 215, 216,
217, 218, 214, 215, 216, 217, 218, 214, 215, 216, 217,
218, 214, 215, 216, 217, 218, 214, 215, 216, 217, 218,
103, 125, 1839, 1840, 1840, 1901, 1902, 1907, 1908,
10461, 10461, 10461, 10469, 10469, 10470, 10470,
1910, 1911, 1912, 1918, 1920, 1923, 1924, 1925, 1928,
10471, 10471, 300, 418, 1817, 15658, 1820, 1811,
4041
15670, 129, 1806, 1806, 17810, 2016, 2019, 17888,
17891, 17910, 17911, 17917, 18288, 1875, 1876, 1875,
10, 4052,
1876, 10,476,
1882, 4052, 16, 13,
4010, 15, 4040,
29331, 4015, 13, 15, 4040,
31510, 2302, 13,
139,
15, 4040,
4053, 9052,
4066, 9052,
4087, 9055,
4102, 149,69, 109,79890,
2057, 110, 111, 109,
2059, 2060,
110,
2061,111, 109,
2326, 110,
158, 111, 109,
99510, 6706,110, 111,
6707, 214, 215, 216,
6708
217, 218, 214, 215, 216, 217, 218, 214, 215, 216, 217,
218, 214, 215, 216, 217, 218, 214, 215, 216, 217, 218,
10468, 1811, 15670, 2016, 2017, 17871, 2019, 17892,
10469, 10469, 418, 1811, 15670, 129, 1806, 2016,
17908
2019, 1882, 476, 6, 4010, 4015, 4019, 4025, 2302, 139,
4068, 4087, 4102, 149, 2057, 79890, 2059, 2060, 2061,
2326, 158, 99510, 6706, 6707, 6708
10, 4052, 10, 4052, 1806, 1852, 2000, 2001, 2000,
2001, 2002, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
2006, 2007, 2008, 2009, 2010, 2006, 2007, 2008, 2009,
2010, 2006, 2007, 2008, 2009, 2010, 2006, 2007, 2008,
2009, 2010, 2011, 2013, 2014, 2048, 2049, 2048, 2049,
2052, 4039, 4064
2, 1827, 1941, 4071, 4077
0, 1, 1917, 1932, 1933, 1934, 1935, 4073, 4078, 4079,

4080
88, 13557, 13557, 1825, 1826, 1825, 1826, 4036, 4004,

4038, 4175
13, 15, 4040, 13, 15, 4040, 13, 15, 4040, 94, 95, 109,
110, 111, 109, 110, 111, 109, 110, 111, 109, 110, 111,
1807, 1856, 1857, 1858, 1859, 1868, 1892, 1861, 4000,
49670, 4063, 4097, 12
1816, 1898, 1899
29, 30, 29, 30, 28, 214, 215, 216, 217, 218, 214, 215,
216, 217, 218, 214, 215, 216, 217, 218, 214, 215, 216,
217, 218, 214, 215, 216, 217, 218, 1802, 1802, 1802,
1802, 1850, 4029, 1850, 4029, 6, 31710
10, 4052, 10, 4052, 1847, 1806, 1806, 1871, 1872,
1873, 1874, 1871, 1872, 1873, 1874, 1871, 1872, 1873,
1874, 1871, 1872, 1873, 1874
10, 4052, 10, 4052, 1829, 1806
3070
3060
3000, 3013
3000, 3020, 3013
3000
3090
3090
3000, 3013
3090
3060
3060
3030
3000, 3070, 3013
3010
3010
3000, 3030, 3100, 3511, 3013
3000
3070
3030
3000
3000, 3013
3040
3050
3040
3050
3050
3050
3070
3000, 3013
3000
3070
3000, 3013
3000
3060
3020, 3013
3000, 3013
3000, 3013
3000, 3013
61605, 61606
3070
3090
3000, 3013
3000, 3020, 3013
3000, 3013
3000, 3070, 3013
3070
3000
3000
3060
3000, 3020, 3013
3000
3060
3000, 31850
3000
3030

RNC16 BTS Alarm and Fault Doc

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RNC16 BTS Alarm and Fault Doc

Uploaded by

Copyright:

Available Formats

RNC16 Operating Documentation

RNC RNW and Flexi Multiradio WCDMA

The manual contains the alarms of all applications, and therefore it is possible that it also contains alarms that do not

1.2 Handling of BTS alarms and faults

In addition NetAct is used for handling the BTS alarms.

BTS transmission alarms

Instructions for solving problems

Blocking and unblocking

2. How to read this excel report

The excel report consists of two main sections:

The excel report consists of two main sections:

The alarms and faults are listed by numbers in an ascending order.

2.1 Alarm List

2.2 Fault List

2.3 Field descriptions

2.4 Change information

Filters are enabled for convenient browsing of the change categories.

ntains alarms that do not

ation software uses these

gured state. During the

smission equipment uses

ation of the modules at

set is required to cancel

hen the unit or cell is in a

or cell are automatically

and alarm attributes

ns. Use fold (-) and unfold

the following ways:

in the following columns:

with red font.

ent view. Use unfold (+)

vious issue and previous

Changes between issues Changes between releases Alarm Number

Changed Changed 7775

EXTERNAL AL 1 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 2 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 3 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 4 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 5 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 6 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 7 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 8 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 9 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 10 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 12 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 13 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 14 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 15 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 16 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 17 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 18 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 19 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 20 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 21 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 22 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 24 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 25 Base Station Alarms ENVIRONMENTAL_ALARM

EXTERNAL AL 26 Base Station Alarms ENVIRONMENTAL_ALARM

BASE STATION FAULTY Base Station Alarms EQUIPMENT_ALARM

BASE STATION OPERATION DEGRADED Base Station Alarms EQUIPMENT_ALARM

BASE STATION NOTIFICATION Base Station Alarms EQUIPMENT_ALARM

CELL FAULTY Base Station Alarms QUALITY_OF_SERVICE_ALAR

CELL OPERATION DEGRADED Base Station Alarms QUALITY_OF_SERVICE_ALAR