Wordpress Com

ABOUT
Nokia BSC, MSC, HLR Commands
18 Tuesday Nov
2014
A T
R Y
NA OR KC I HA I
V 2 E GS
: F
Search
Go
7606 TRX FAULTY

POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION &
TROUBLSHOOTING
LEAVE
7606 TRX Faulty
Severity:
Object
affected:
Object
state:
Module/Unit:
Major
TRX
Disabled
ECxx,
ERxA,
ESMx,
EXxA,
EOCA.
Fault
reason:
Instruction:
ECxx
RTC
module
cavity
is
broken.
ECxx RTC module has detected

that its cavity stepper motor
cannot be moved or its phase
detection logic is broken.
1. Issue a TRX lock/unlock to allow
RTC module reconfiguration.
2. If alarm reappears, replace
ECxx.
ECxx
RTC
module
has
detected
VSWR
above
major
limit
at
antenna.
User definable major alarm

threshold for VSWR measurement
has been exceeded. The default
value is 3.1.
1. Check the condition of the
feeder and jumper cable, their
connectors, sockets and connector
seals starting from BTS end and
proceed towards the antenna end.
Replace damaged feeder cable.
2. If MHA is used, check that is of
correct (sub)band.
3. With external test equipment,
measure the Return loss/VSWR of
the antenna line. Perform step 1
again, if the measurement result is
higher than expected.
4. Revise the VSWR alarm
threshold by appending the
commissioning.
5. Replace ECxx.
ECxx
RTC
module
has
lost
Tx
power
from
all
inputs.
No Tx power detected from any of

the TRXs connected to ECxx RTC
module.
Note: This alarm might take up to
one hour to appear after RTC
module is reset.
1. Issue a sector reset and run a
TRX test for each TRX.
2. Check the Tx cabling from all
the TRXs and issue a sector reset.
Run a TRX test for each TRX.
3. If the alarm persists, replace
ECxx.
ECxx
RTC
module
received
insufficient
Tx
power.
ECxx RTC module detected

insufficient power during cavity
tuning. RTC is unable to perform
cavity tuning.
1. Issue a sector lock/unlock to
allow ECxx RTC module
reconfiguration.
2. Check that the Tx cabling
between EXxx and ECxx is
correctly mated. Check also the
condition of cables.
3. If all the EXxx connected to the
ECxx have raised this alarm,
replace ECxx.
4. Replace EXxx.
5. Replace ECxx.
ERxx
DDU
module
connected
There is a conflict in the antenna

cabling (RF source unit) between
the SCF and the actual
configuration.
A COMMENT
&
to
wrong
EXxx
TRX
module.
1. Check that the antenna cabling

information in the SCF refers to
the correct and existing ERxx.
ERxx
DDU
module
has
detected
no
Tx
power
at
TxA
input.
There is no Tx power detected at

TxA input of ERxx DDU module. If
the alarm is raised on an
IDD/DPTRX object serving the
BCCH and another IDD/DPTRX
object is available in the sector,
lock the BCCH TRX object. BSC will
reconfigure the BCCH to the
working IDD/DPTRX object.
Otherwise the IDD/DP enabled
sector operates with reduced
performance.
1. Check the whole Tx cabling
chain between EXxx, EWxx (upon
usage) and ERxx that they are
correctly mated between the units.
2. Check that the cables are not
damaged or bent too sharply.
3. Replace EXxx.
4. Replace ERxx.
5. Replace EWxx.
Note that when the IDD TRX is
connected to DDU, if any one path
is broken, the alarm is 7607; if
both paths are broken, the alarm
is 7606.
ERxx
DDU
module
has
detected
no
Tx
power
at
TxB
input.
There is no Tx power detected at

TxB input of ERxx DDU module.If
the alarm is raised on an
performance.
1. Check the whole Tx cabling
chain between EXxx, EWxx (upon
usage) and ERxx that they are
correctly mated between the units.
2. Check that the cables are not
damaged or bent too sharply.
3. Replace EXxx.
4. Replace ERxx.
5. Replace EWxx.
is broken, the alarm is 7607; if
both paths are broken, the alarm
is 7606.
ERxx
DDU
module
has
detected
VSWR
above
major
limit
at
antenna
A.

value is 3.1.If the alarm is raised
on an IDD/DPTRX object serving
the BCCH and another IDD/DPTRX
performance.
2. If MHA is used, check that it is
of correct (sub) band.
commissioning.
5. Replace ERxx.
exceeds the VSWR major limit, the
alarm is 7607; if both paths
exceed the limit, the alarm is
7606.
Note that the Dual Duplexer
module is able to report Return
Loss reliably if the TX (BCCH)
power in its TxA or TxB input
exceeds ca. +32 dBm.
ERxx
DDU
module
has
detected
VSWR
above
major
limit
at
antenna
B.

value is 3.1.If the alarm is raised
on an IDD/DPTRX object serving
the BCCH and another IDD/DPTRX
performance.
2. If MHA is used, check that it is
of correct (sub) band.
commissioning.
5. Replace ERxx.
exceeds the VSWR major limit, the
alarm is 7607; if both paths
exceed the limit, the alarm is

7606.
Note that the Dual Duplexer
module is able to report Return
Loss reliably if the TX (BCCH)
power in its TxA or TxB input
exceeds ca. +32 dBm.
ESMA
System
module
has
lost
connection
to
EXxx
TRX
module.
EXxx TRX module does not

respond to polling command from
ESMA System module. EXxx TRX
module can be connected to ESMA
either directly or via ESEA System
Extension module.
1. Check the bus cable chain from
ESMA to EXxx.
2. If the EXxx LED is off, replace
the power cable.
3. Replace EXxx.
4. Replace ESEA if alarming TRX is
connected to it.
5. Replace ESMA.
Note: If this alarm is starting and
cancelling repeatedly and EXxx
TRX module is connected with
EOCA then check input voltage
supplied to EOCA. Ensure that
power supply provides voltage
within 42V 57.0V DC range.
EXxx
TRX
detected
no
connection
to
ERxx
DDU/ECxx
RTC
via
RF
cable
autodetection
RF cable autodetection failed due

to no Tx or Rx connectivity from
EXxx TRX module to ERxx
DDU/ECxx RTC module. All Rx
measurement report values for a
TRX object were below
connectivity threshold.
1. Check that the Tx and Rx cables
between EXxx, EWxx, and ERxx or
ECxx are correctly mated and the
connectors and cables are not
damaged. Issue a sector reset to
restart RF cable autodetection.
2. Check that ECxx/ERxx and EXxx
are of same frequency band.
3. Wait for DDU to come in
supervisory (Fixed green LED on
DDU). Issue a sector reset to
restart RF cable autodetection.
4. Replace EXxx.
Note that if the DDU is shared
across two sectors, a BCF reset is
needed.
EXxx
TRX
module
detected
no
Rx
signal
during
RF
cable
autodetection
RF cable autodetection failed due

to no Rx connectivity from EXxx
TRX module to ECxx RTC module.
All Rx measurement report values
for a TRX object were below
connectivity threshold.
1. Check that the Rx cables
between EXxx and ECxx are
correctly mated and the
connectors are not damaged.
Issue a sector reset to restart RF
cable autodetection.
2. Check that ECxx and EXxx are
of same frequency band.
3. If all the EXxx connected to the
ECxx have raised this alarm,
replace ECxx.
4. Replace EXxx.
EXxx
TRX
module
failed
to
synchronize
to
incoming
frame
clock
FCLK.
EXxx TRX module has detected

that it cannot synchronise to the
Frame Clock. FCLK is generated by
ESMA System Module which is
distributed to EXxx TRX modules
either directly or via ESEA.
ESMA to EXxx. Issue a HW Reset
to EXxx.
2. Replace EXxx.
3. Replace ESMA.
4. Replace ESEA.
Caution: If bus cables are looped
back to the same module, ongoing
calls may be dropped or a module
may freeze until the loop is
removed. Do not loop bus cables
back to the same module.
EXxx
TRX
module
has
no
combiner
ERxx
DDU
or
ECxx
RTC
module
present.
There is no ERxx DDU module or

ECxx RTC module detected for the
sector at start up.
1. Depending on the desired
configuration:
1.1 Connect/check ER_A cable
between ERxx and EXxx for the
associated sector and issue a
sector reset. OR
1.2 Connect/check bus cable
between ECxx and ESMA and
issue a sector reset.
2. Replace ERxx/ECxx.
3. Replace EXxx.
needed.
Note: If the configuration is 1+X
containing only one ERxx DDU
module, it has to be connected to
the split EXxx TRX module shared
between the two sectors.
EXxx
TRX
module
has
lost
connection
to
ESMA
System
module
Ethernet link to system box

broken.
This alarm is not visible to
customer.
EXxx
TRX

that the 6.5 MHz reference clock
module
incoming
6.5
MHz
reference
clock
missing.
coming from the ESMA System

Module is missing. The 6.5 MHz
reference is generated by ESMA
System Module which is
ESMA to EXxx.
2. Replace EXxx.
connected to it.
4. Replace ESMA.
EXxx
TRX
module
incoming
frame
clock
FCLK
missing.

that the Frame Clock coming from
the ESMA System Module is
missing. FCLK is generated by
ESMA System Module which is
ESMA to EXxx.
2. Replace EXxx.
connected to it.
4. Replace ESMA.
EXxx
TRX
module
Rx
fixed
frequency
synthesizer
fails
to
lock.
Rx fixed frequency synthesizer in

EXxx TRX module was unable to
(maintain) lock to the given
channel.
1. Reset TRX/Sector.
2. Replace EXxx.
EXxx
TRX
module
Rx
hopping
synthesizer
1
fails
to
lock.
Rx hopping synthesizer 1 in EXxx

TRX module was unable to
channel.
2. Replace EXxx.
EXxx
TRX
module
Rx
hopping
synthesizer
2
fails
to
lock.
Rx hopping synthesizer 2 in EXxx

channel.
2. Replace EXxx.
EXxx
TRX
module
Tx
power
is
less
than
minimum
at
DPC.
Tx output power is less than

+14.5dBm at Digital Power Control
circuit block in EXxx TRX module.
1. Replace EXxx.
EXxx
TRX
module
Tx
power
overdriven
at
DPC.
Tx output power is over 2 dB

higher than expected at Digital
Power Control circuit block in EXxx
TRX module.
1. Replace EXxx.
EXxx
TRX
module
SW
download
from
ESMA
System
Module
failed.
ESMx System Module detected

that SW download to EXxx TRX
module has failed repeatedly at
TRX startup. EXxx TRX module can
be connected to ESMA either
directly or via ESEA System
Extension module.
ESMA to EXxx.
2. Replace EXxx.
EXxx
TRX
module
temperature
dangerously
high.

that its internal temperature has
exceeded +95C/+203F.
1. Ensure that the ambient
temperature of the base station is
below +50C/+122F.
2. Check if any fan alarms are also
active. If active, refer to fan alarm
instructions to resolve.
3. Replace the EXxx.
EXxx
TRX
module
Tx
hopping
synthesizer
1
fails
to
lock.
Tx hopping synthesizer 1 in EXxx

channel.
2. Replace EXxx.
EXxx
TRX
module
Tx
hopping
synthesizer
2
fails
to
lock.
EXxx
TRX
module
Tx
power
overdriven
at
DPC.
Tx hopping synthesizer 2 in EXxx

channel.
2. Replace EXxx.
Internal
failure
occurred
during
EXxx
TRX
module
configuring.
There was no internal response or

timeout occurred during EXxx TRX
module configuration.
1. Reset the EXxx to allow unit
reconfiguration.
2. If alarm persists, replace EXxx.
Irrecoverable
Loss
of
BSS
Synch
The received FCLK has slipped

more than 40s away from the
LMU FCLK while using the Abis
clock as a secondary master-clock.
This timing error is too high to be
recovered reliably.
1. Site reset is required.
Note that the alarm start is based
on the following:
1.Large alignment problems
between Abis clock and external
clock reference, after external
clock reference has recovered
from fault condition.
2. Fluctuation in the DAC word.
Alarm start will equate to
significant degradation in DFCA
performance.
Logical
TRX
object
has
missing
transmission
time
slot
allocation.
TRXsig and/or TCH allocation for

Logical TRX object is missing from
the Abis allocation.
1. Check that BTS configuration
and Abis time slot allocation
matches between the SCF,
installed units, and the BSC.
2. Add missing time slot allocation
to the SCF/BTS by appending the
commissioning file.
Mismatch
between
SCF
and
actual
ECxx
RTC
module
position.
There is a conflict in the antenna

cabling (RF source unit) between
the SCF and the actual
configuration.
1. Check that the antenna cabling
information in the SCF refers to
the correct and existing ECxx.
Phase
difference
between
Tx
signals
is
too
high
with
DPTRX
Phase difference between the

combined Tx signals is too high
resulting in reduced Tx output
power. If the alarm is raised on an
performance.
1. Check that the Phase Detector
cable is correctly mated between
EWxA and EXxx.
2. Replace the Phase Detector
cable.
3. Replace EWxA.
4. Replace EXxx.
PDU
control
has
switched
off
ECxx
RTC
Module
Either System module has

switched OFF power to ECxx RTC
module due to low/high voltage or
power is toggled OFF by user from
BTS Manager power control menu.
1. Check the ESMA input voltage is
between 39 58VDC.
2. Power ON the PDU from BTS
Manager (BTS Control | Power
Control).
3. Replace ESMA.
PDU
control
has
switched
off
EXxx
TRX
Module
Either System (extension) module

has switched OFF power to EXxx
TRX module due to low/high
voltage or power is toggled OFF by
user from BTS Manager power
control menu.
1. Check the ESMA/ESEA input
voltage is between 39 58VDC.
2. Power ON the PDU from BTS
Manager (BTS Control | Power
Control).
3. Replace ESMA/ESEA.
Tx output power is over 2 dB

higher than expected at Digital
Power Control circuit block in EXxx
TRX module.
If alarm is raised on IDD/DPTRX
object serving the BCCH AND
another IDD/DPTRX object is
available in the sector, then lock
the BCCH TRX object. BSC will
reconfigure BCCH to the working
IDD/DPTRX object. Otherwise
IDD/DP enabled sector operates
with reduced performance.
Remote:
Local:
2. Issue DTRX HW reset via BTS
Manager.
3. Replace EXxx.
18 Tuesday Nov
2014
RF
cable
autodetection
failed.
RF cable autodetection fails due to

inconclusive Rx levels received.
Therefore, BTS cannot determine
RF cabling.
1. Run RFCAD to the failing
sector(s) by performing a sector
lock/unlock or a sector reset from
the BTS Manager.
2. Define the RF cabling manually
through recommissioning.
3. Replace EWxx.
4. Replace Erxx/ECxx.
5. Replace EXxx.
6. Replace ESxx.
needed.
RF
cabling
missing
for
DPTRX.
RF cabling is detected to be
missing from DPTRX object.
1. Check that all Tx and Rx cables
are fully mated between the EXxx,
EWxA and ERxx.
2. Replace EWxA.
3. Replace EXxx.
4. Replace ERxx.
Two
or
more
ERxx
DDU
modules
detected
in
2or
4way
combined
sector
In this configuration, RF cable

autodetection does not support
more than one ERxx DDU module
in a sector.
1. Check that the Tx cabling from
EXxx and EWxx modules in one
sector are connected to the same
ERxx module.
2. Depending on the desired
configuration:
2.1. If more than one ERxx is
needed in a sector, change
commissioning settings so that RF
cables are defined manually.
OR
2.2. Remove extra ERxx from the
sector.
XEOCA
optical
module
detected
extreme
temperature.
EOCA Optical module has detected

that its internal temperature has
exceeded +90C/+194F.
1. Ensure that the ambient
temperature of the base station is
below +50C/+122F.
2. Check if any fan alarm is also
active. If active, refer to fan alarm
instructions to resolve.
3. Replace the alarming EOCA.
XEOCA
optical
module
reported
HW
failure
ESMA System module detected

that hardware failure has occurred
in EOCA Optical module at startup.
1. If on Local EOCA, replace Local
EOCA.
2. If on Remote EOCA, replace
Remote EOCA.
XEOCA
optical
module
reported
incoming
clock
failure
Incoming clock errors or optical

link failures either in Local or
Remote EOCA Optical module.
1. If on Local EOCA:
1.1 Check the bus cable, the
connectors or replace the cable
between ESxx and Local EOCA.
1.2 Check optical transceiver plugin unit of Local EOCA.
1.3 Replace Local EOCA.
1.4 Check optical transceiver plugin unit of Remote EOCA.
1.5 Replace Remote EOCA.
1.6 Check the optical cable and its
connector(s) and replace cable in
case faulty.
2. If on Remote EOCA:
2.1 Check optical transceiver plugin unit of Local EOCA.
2.2 Replace Local EOCA.
2.3 Check optical transceiver plugin unit of Remote EOCA.
2.4 Replace Remote EOCA.
2.5 Check the optical cable and its
connector(s) and replace cable
incase faulty.
7605 BTS NOTIFICATION

TROUBLSHOOTING
LEAVE
A COMMENT
7605 BTS Notification
Severity:
Object affected:
Object state:
Module/Unit:
Minor
BTS
Enabled
ECxA
Fault
reason:
Instruction:
ECxx RTC
module
cooling fan
speed has
The cooling fan speed has increased substantially from the commanded fan
speed.
1. Check the ESMA operational voltage as an increased ESMA voltage could lead
to overspeeding of the fans.
18 Tuesday Nov
2014
increased
from the set
speed.
2. Replace the fan unit.

3. Replace ECxx.
ECxx RTC
module
cooling fan
speed has
reduced
from the set
speed.
The cooling fan speed has reduced substantially from the commanded fan speed.
1. Check that nothing obstructs the fan(s) from rotating.
2. Clean the fan unit of dust and/or dirt.
Note: If Temperature high/ dangerously high and/or 7621 alarm(s) are also
active, perform these actions as soon as possible.
ECxx RTC
module
cooling
fan(s) report
no rotation.
One or more fans of the ECxx RTC module are not rotating. There is a danger of
overheating.
1. Check that the fan unit cable is correctly mated to ECxx.
2. Check that there are no obstacles preventing the fan(s) from rotating.
3. Clean the fan unit of dust and/or dirt
5. Replace ECxx.
ECxx RTC
module has
detected no
fans.
ECxx RTC module has not detected a fan unit at start up. There is a danger of
overheating.
1. Check that the fan unit cable is correctly mated to ECxx.
3. Replace ECxx.
ECxx RTC
module
temperature
dangerously
high.
ECxx RTC module has detected that its internal temperature has exceeded
+65C/+149F.
1. Ensure that the ambient temperature of the base station is below +50C/+122F.
2. Check if any fan alarms are also active. If active, refer to fan alarm instructions
to resolve.
3. Replace the ECxx.
ECxx RTC
module
unable to
read internal
temperature
sensors.
There is no temperature measurement in the ECxx RTC module. All temperature

sensors inside the module are broken. Fans are rotating at maximum speed.
1. Replace the RTC.
Note: If fan alarm(s) are active at RTC, perform this action as soon as possible.
The cooling
fan speed of
RTC module
has
increased
substantially
from the
commanded
fan speed.
1. Check the ESMA operational voltage as an increased ESMA voltage could lead
to overspeeding of the fans.
3. Replace ECxx.
7602 BCF NOTIFICATION

TROUBLSHOOTING
LEAVE
7602 BCF Notification
Severity:
Object
affected:
Object
state:
Module/Unit:
Minor
BCF
Enabled
ESEA,
ESMx,
EOCA.
Fault
reason:
Instruction:
BSS
synchronisation
failed.
ESMx System Module has lost

synchronisation signal at synchronisation
input (SIN) port.
1. If LMU provides the synchronisation,
check if alarm 8202 is active and resolve it.
2. If another BTS is the synchronisation
master, check if that it is up and alive.
3. Check that the synchronisation cabling is
correctly mated between the units. If LMU is
used, check also Q1 cabling and power
supply to the LMU unit.
4. Replace ESMx.
BTS Trace
Collection
Ongoing.
User initiated BTS trace collection from BTS

Manager.
No repair actions required, alarm is
cancelled when BTS trace collection is
stopped by the user.
A COMMENT
Commissioned
RF cabling
does not
match BTS
configuration.
Manually defined RF cabling in SCF is

incorrect as verified against BTS
Configuration received from BSC. It may
result in degraded BTS performance.
1. Revise manually defined RF cabling in
SCF against the actual configuration.
2. Check that RXDIV=N for sector is using
only one antenna.
3. Enable RF cable autodetection (RFCAD)
through commissioning wizard.
Note 1: Rack field contains information
check for cable present (1 = TX, 2=RX
main, 3=RX Div, 4=both RX paths from
same Ant connection).
Note 2: Shelf filed contains the TRX number
which contains Faulty RF cables.
Note 3: Also, there may be more RF cabling
errors introduced during commissioning,
but only one of those is reported.
Note 4. Refer to latest Flexi EDGE BTS
Commissioning document for RF cable
autodetection limitations.
1. Rack field contains information check for
cable present (1 = TX, 2=RX main, 3=RX
Div, 4=both RX paths from same Ant
connection).
2. Shelf field contains the TRX number
which contains faulty RF cables.
3. Also, there may be more RF cabling
errors introduced during commissioning,
but only one of those is reported.
Difference
between
current and
last stable
DAC words
DAC word has been changed more than

408 steps from original DAC word (is
usually within 2048 +/- 20)
1. Check at NetAct if there are any active
core network synchronisation related
alarms starting with code 1xxx and/or 2xxx,
due to which the incoming sync reference
PCM clock is drifted and causes OCXO oven
oscillator to tune incorrectly out of correct
frequency and (if fault persists) will
eventually cause handover failures for CS
calls.
2. Correct the synchronization problem in
the upper part of network.
ECxx RTC
module
connected
to wrong
port.
ECxx RTC module is not connected to port

1/2/3 of ESMx System Module.
1. Connect ECxx to ESMx port 1,2 or 3 and
issue a BCF reset.
EOCA
Optical
module
connected
to wrong
port.
EOCA Optical module is not connected to

ESMA System Extension module.
1. Connect Local and Remote EOCA to
ESEA.
ESEA
System
Extension
module
connected
to wrong
port.
ESEA System Extension module is not

connected to port 6 of ESMA System
Module.
1. Connect ESEA to port 6 of ESMA, and
issue a BCF reset.
ESEA
System
Extension
module
temperature
high.
Internal temperature of ESEA System

Extension module has exceeded
+85C/+185F.
1. Ensure that the ambient temperature of
the base station is below +50C/+122F.
2. If the fault persists, replace ESEA.
Note that this alarm remains active if the
temperature still increases and the
temperature dangerously high alarm is
activated.
ESMx
System
Module
cooling fan
speed has
increased
from the set
speed.
The cooling fan speed of System Module

has increased substantially from the
commanded fan speed.
1. Check the ESMx operational voltage as
an increased ESMx voltage could lead to
overspeeding of the fans.
3. Replace ESMx.
ESMx
System
Module
cooling fan
speed has
reduced
from the set
speed.
The cooling fan speed has reduced

substantially from the commanded fan
speed.
1. Check that nothing obstructs the fan(s)
from rotating.
4. Replace ESMx.
Note: If Temperature high/ dangerously
high and/or 7621 alarm(s) are also active,
perform these actions as soon as possible.
ESMx
System
ESMx System Module has detected that its

internal temperature has exceeded
Module
temperature
high.
+90C/+194F.
2. Check if any fan alarms are also active. If
active, refer to fan alarm instructions to
resolve.
3. Replace the ESMx.
Note that this alarm remains active if the
temperature still increases and the
temperature dangerously high alarm is
activated.
ESMx
System
Module
unable to
read
internal
temperature
sensors.
There is no temperature measurement in

the ESMx System Module. All temperature
sensors inside the module are broken. Fans
are rotating at maximum speed.
Note: If fan alarm(s) are active at ESMx,
perform this action as soon as possible.
External
synchronisation
signals
disabled.
LMU has operated without GPS signal over

specified time and is turning its FCLK
output off.
1. Check the GPS antenna fix status is OK
with LMUManager. Adjust the GPS antenna
so that satellites become visible.
2. Check that the GPS cable is correctly
mated to LMU.
3. Check that the latest LMU SW is being
used. Download newer SW if necessary.
4. Replace LMU.
EXxx TRX
module
connected
to wrong
port.
EXxx TRX Module is not connected to ESEA

System Extension module.
1. Connect EXxx module to ESEA.
Incoming
reference
clock has
started to
deviate
rapidly
The DAC word has been changed more than

408 steps rapidly from the original DAC
word (is usually within 2048 +/- 20), due to
which the incoming synchronisation
reference PCM clock has drifted and causes
OCXO oven oscillator to tune out of correct
frequency and (if fault persists) will
eventually cause handover failures.
1. Check at NetAct if there are any active
core network synchronisation related
alarms starting with code 1xxx and/or 2xxx.
2. Correct the synchronisation problem in
the upper part of the network.
Supply
voltage to
ESEA near
low/high
limit
The input voltage to the power supply of

ESEA is less than 40VDC or more than
58VDC.
1. Check that the input voltage range of
System Extension module is within
specified range.
2. Replace ESEA.
Supply
voltage to
ESMx near
low/high
limit
The input voltage to the power supply of

ESMx is less than 40VDC or more than
58VDC.
1. Check that the input voltage range of
System module is within specified range.
2. Replace ESMx.
Certificate
Revocation
List retrieval
failure from
Certificate
Repository
Either Certificate Repository is not

reachable or invalid Certificate Revocation
List at Certificate Repository or Certificate
Revocation List Size too Big.
1. Check Certificate Repository IP address
in SCF at BTS
2. Check BTS cable connectivity with
Certificate Repository
Certificate
Authority
certificate
retrieval
failure
Either Certificate Repository is not

reachable or invalid certificate of Certificate
Authority at Certificate Repository
1. Check Certificate Repository IP address
in SCF at BTS.
Certificate Repository.
3. Verify that requested valid certificate
exist in Certificate Repository.
18 Tuesday Nov
2014
BTS security
certificate
retrieval
failure from
Certificate
Authority
Either Certificate Authority is not reachable

or invalid certificate at Certificate Authority
1. Check Certificate Authority IP address is
correct via SCF from BTS Manager.
Certificate Authority.
3. Verify that valid BTS Certificate exist in
Certificate Authority.
Unknown
module
connected
to ESxx
System
(Extension)
module.
ESMA System Module does not recognise

the module connected to this port. SW
release incompatibility with the connected
HW.
1. Check the HW \ SW compatibility from
the SW release binder
a. If the module is compatible with the
current SW running in the BTS, replace the
module.
b. If the module is not compatible with the
current SW running in the BTS, check which
SW version supports the module. Upgrade
the BTS SW to the version that supports the
module.
2. Remove the unknown module.
7601 BCF OPERATION DEGRADED

TROUBLSHOOTING
7601 BCF Operation Degraded
Severity:
Object
affected:
Object
state:
Module/Unit:
Major
BCF
Enabled
ESMx,
FAEA,
ESEA
Fault
reason:
Instruction:
All external
Q1 devices
fail to
respond.
None of the configured Q1 devices in the Q1

bus are responding to a polling command.
1. Check that Q1 addresses and baud rate
match between the Q1 devices and BSC.
2. If FIFA is used and BTS is polling Q1
equipment, check that Q1 switch towards the
Q1 bus is closed with FlexiHub Manager.
3. Check that the Q1 cables are correctly
mated between the ESMx and Q1 devices.
4. Replace ESMx.
Difference
between
PCM and
BTS
frequency
reference.
There is over 5 Hz difference to the 2MHz

reference clock due to Abis link instability.
1. Check that Synchronisation priority list has
correct Rx clock sources.
2. Check the Abis link quality (G.826
performance statistics via BTS
Manager/NetAct). Check the alarm history for
8xxx alarms reported and resolve any link
problems occurred.
3. Check the network synchonisation between
the BSC and the base station.
4. If alarm is active at multiple sites, check
the quality of synchronisation for the whole
BSS.
ESEA
System
Extension
Module
fan(s) out
of order.
ESEA System Extension module detected

reduced speed or no rotation of fan(s) against
commanded speed.
1. Check that the fan unit cable is correctly
mated to ESEA.
2. Check that there are no obstacles
preventing the fan(s) from rotating.
5. Replace ESEA.
ESMx
System
Module
cooling
fan(s)
report no
rotation.
One or more fans of the ESMx System module

are not rotating. There is a danger of
overheating.
mated to ESMx.
2. Check that there are no obstacles
preventing the fan(s) from rotating.
LEAVE
A COMMENT

5. Replace ESMx.
18 Tuesday Nov
2014
ESMx
System
Module
FLASH
memory
writing
error.
Memory write failure occurred at SW

download and is not valid. The previously
active SW is taken into use.
1. Issue a HW reset to ESMx from (remote)
BTS Manager.
2. Attempt the SW download again.
3. If this alarm persists, replace ESMx.
ESMx
System
Module has
detected no
fans.
ESMx System module has not detected a fan

unit at start up. There is a danger of
overheating.
mated to ESMx.
ESMx
System
Module has
lost
connection
to FSEx
External
Alarm (EAC)
module.
FSEx External Alarm (EAC) module does not

respond to poll message of the ESMx System
Module.
1. Check that FSEx is set to Active Mode by
connecting pins 3-4 of X1103 jumper.
2. Check that the cabling is correctly mated
between ESMx and FSEx.
3. Replace FSEx.
4. Replace ESMx.
Loss of BSS
Synch while
on Abis
clock
This alarm indicates that the FCLK has

slipped between 20 s and 40 s away from
the LMU FCLK while using the Abis clock as a
secondary master-clock.
1. No corrective actions required.
Note that alarm start/cancel is based on the
alignment of the BTS clock to the external
clock reference after external clock reference
has recovered from fault condition.
Alarm start will equate to degradation in
DFCA performance.
A site reset will reduce alignment time.
Module
power
cable
connections
are
incorrectly
configured.
One or more of the internal power cable

connections does not match power cabling
rules. Intelligent shutdown feature may not
operate correctly.
1. Check the internal power and bus cabling
against the product documentation set.
2. Issue a BCF reset.
During intelligent shutdown, the BTS
SW cuts off the power supply (from ESMA
System Modules PWR port) and LapD links
for the affected TRXs, and, during recovery,
turns them back on. Now, if the DTRX power
cabling from the ESMA is incorrect (that is,
DTRXs power cable is not connected to the
right PWR port on ESMA), some TRX objects
are left in the blocked state as the recovery
actions are routed to the wrong DTRX. In this
case, give TRX reset for the affected TRX
objects.
Irrecoverable
Loss of BSS
Synch.
The received FCLK has slipped more than 40

s away from the LMU FCLK while using the
Abis clock as a secondary master-clock. This
timing error is too high to be recovered
reliably.
1. Site reset is required.
Note that the alarm start is based on the
following:
2. Large alignment problems between Abis
clock and external clock reference, after
external clock reference has recovered from
fault condition.
3. Fluctuation in the DAC word.
Alarm start will equate to significant
degradation in DFCA performance.
7600 BCF Faulty

TROUBLSHOOTING
LEAVE
7600 BCF Faulty
Severity:
Object
affected:
Object
state:
Module/Unit:
Critical
BCF
Disabled
ESEA,
ESMx, FIxx
Fault reason:
Instruction:
Air i/f
reference
clock 26 MHz
not available.
System module detected that its Oven

Controlled Oscillator is not generating the
frequency reference.
1. Make sure that ambient temperature of the
site is within normal operating temperature
range (-35 to +50C/-31 to +122F).
2. Issue a HW reset to ESMx from (remote)
BTS Manager.
Note that the sites bypass transmission will
be cut for 1-2 minutes.
3. Replace ESMx.
A COMMENT
BSS
synchronisation
failed.
ESMx System Module detected no

synchronisation signal at synchronisation
input (SIN) port at startup.
1. Check that the BCF synchronisation related
settings are correct at the BSC via MML
command(s) (ZEFO).
2. If LMU provides the synchronisation, check
if alarm 8202 is active and resolve.
3. If another BTS is the synchronisation
master, check if that it is up and alive.
4. Check that the synchronisation cabling is
correctly mated between the units. If LMU is
used, check also Q1 cabling and power supply
to the LMU unit.
5. Replace ESMx.
Critical
transmission
licence
missing at the
BSC.
Abis over IP/Ethernet, Additional 2 E1,T1 IF,

or Packet Abis Security licence is not
installed in the BSC.
1. Check which transmission licence alarm
(8273 or 8274) is active and follow the alarm
specific instructions given.
ESEA System
Extension
module
reported HW
failure.
ESMx System Module detected that a

hardware failure has occurred in the ESEA
System Extension module.
1. Issue HW reset to ESMx from BTS Manager.
2. If fault persists, replace ESEA and reset the
BCF.
ESEA System
Extension
module SW
upgrade
failed.
ESMA System Module detected that SW

download to ESEA System Extension module
failed at startup.
1. Issue a HW reset to ESEA.
2. Issue a HW reset to ESMA.
3. If alarm persists, replace ESEA.
4. Replace ESMA.
ESMx System
Module has
lost
connection to
all ECxx RTCs
and EXxx
TRXs.
None of the BTS modules respond to ESMx

polling command.
1. Reset BCF.
2. Check all cable connections between ESMx
and ECxx Remote Tune Combiner (ECxx) and
EXxx TRX modules.
3. If the fault persists, replace ESMx.
ESMA System
Module has
lost
connection to
ESEA System
Extension
module.
ESEA System Extension module does not

respond to polling command from ESMA
System Module.
1. Check the power distribution to ESEA.
2. Check that the bus cable is correctly mated
between ESMA and ESEA.
3. Replace ESEA.
4. Replace ESMA.
ESMx System
Module has
lost
connection to
FIxx
transmission
submodule.
FIEA/FIPA/FIFA/FIQx/FIYx transport submodule is not detected.

This alarm is reported to the BTS Manager
only.
1. Check that the PIU
(FIPA/FIEA/FIFA/FIQx/FIYx) is properly inserted
into the ESMx.
2. Check the LED status. If LED is not lit (all
PIU types) or yellow (for FIPA/FIEA/FIQx/FIYx),
check the back connector of the PIU.
3. Replace PIU.
4. Replace ESMx.
At the BSC, alarms 7767 BCCH Missing,
7706 BTS O&M link failure may be active for
the alarming BCF.
ESMx System
Module
temperature
dangerously
high.
Internal temperature of ESMx System Module

has exceeded +95C/+203F.
2. Check if any fan alarms are also active. If
active, refer to fan alarm instructions to
resolve.
FIxx type
mismatch
between
commissioning
file and
detected
hardware.
FIEA/FIPA/FIFA/FIQx/FIYx transport submodule is of wrong type. This alarm is

reported to the BTS Manager only.
1.1. Replace PIU module with a correct type
(as defined in SCF) and issue a HW reset to
ESMx.
OR
1.2. Set PIU type in SCF according to the
actual PIU module type and re-commission
the site.
2. Replace the PIU and issue a HW reset to
ESMx.
Mismatch
between the
commissioned
configuration
and actual
configuration.
There is a conflict between the SCF and the

actual configuration during commissioning or
at start up:
1. SCF contains ESEA, but it is not detected in
the actual configuration.
2. SCF does not contain ESEA, but it is
detected to port 6 of ESMx.
3. If cabling source is AUTODECTECTED in
SCF, issue BCF reset with RFCAD.
4. Modify SCF to match the actual
configuration or modify the actual
configuration to match the SCF.
5. Replace ESEA.
6. Replace ESMA.
BTS has lost

CS U-Plane
connection to
BSC
BTS has detected a U-Plane (CS) Link Failure

1. Check U Plane IP address configurations.
2. Check if there is any filtering/firewall
configurations in the network for U-CS traffic.
Newer posts
SUBSCRIBE
Entries (RSS)
Comments (RSS)
ARCHIVES
November 2014
September 2014
January 2014
August 2013
January 2009
CATEGORIES
Nokia 2G Flexi Edge BTS Alarm Discription & Troublshooting

Uncategorized
META
Register
Log in
Create a free website or blog at WordPress.com.

Wordpress Com

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Wordpress Com

Hochgeladen von

Copyright:

Verfügbare Formate

ABOUT

Nokia BSC, MSC, HLR Commands

7606 TRX FAULTY

7606 TRX Faulty

ECxx RTC module has detected

User definable major alarm

No Tx power detected from any of

ECxx RTC module detected

There is a conflict in the antenna

1. Check that the antenna cabling

There is no Tx power detected at

There is no Tx power detected at

User definable major alarm

User definable major alarm

exceed the limit, the alarm is

EXxx TRX module does not

RF cable autodetection failed due

RF cable autodetection failed due

EXxx TRX module has detected

There is no ERxx DDU module or

Ethernet link to system box

EXxx TRX module has detected

coming from the ESMA System

EXxx TRX module has detected

Rx fixed frequency synthesizer in

Rx hopping synthesizer 1 in EXxx

Rx hopping synthesizer 2 in EXxx

Tx output power is less than

Tx output power is over 2 dB

ESMx System Module detected

EXxx TRX module has detected

Tx hopping synthesizer 1 in EXxx

Tx hopping synthesizer 2 in EXxx

There was no internal response or

The received FCLK has slipped

TRXsig and/or TCH allocation for

There is a conflict in the antenna

Phase difference between the

Either System module has

Either System (extension) module

Tx output power is over 2 dB

RF cable autodetection fails due to

In this configuration, RF cable

EOCA Optical module has detected

ESMA System module detected

Incoming clock errors or optical

7605 BTS NOTIFICATION

7605 BTS Notification

2. Replace the fan unit.

There is no temperature measurement in the ECxx RTC module. All temperature

7602 BCF NOTIFICATION

7602 BCF Notification

ESMx System Module has lost

User initiated BTS trace collection from BTS

Manually defined RF cabling in SCF is

DAC word has been changed more than

ECxx RTC module is not connected to port

EOCA Optical module is not connected to

ESEA System Extension module is not

Internal temperature of ESEA System

The cooling fan speed of System Module

The cooling fan speed has reduced

ESMx System Module has detected that its