Вы находитесь на странице: 1из 100

8125 Loss of synchronization signal (s)

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
8125 Loss of synchronization signal(s)

Severity: Object affected: Object state: Module/Unit:

Critical TRE Enabled FIxx

Fault
reason: Instruction:

All defined synchronisation sources in the synchronisation priority list


are invalid or the list is empty. Node is running on its internal clock.
1. Check that synchronisation priority list has Rx clock entries for used
interfaces.
2. In case FIFA PIU is used, check that the microwave link is
commissioned and operational. Refer to FIFA product documentation
for further instructions.
3. If any of the alarms 8050, 8066, 8081, 8099, 8056, 8073, 8277,8278,
or 8282 are active, follow the instructions on them..
4. Check that interface cables are correctly mated to FIxx. Check also
condition of the connectors.
5. With FIQA or FIYA and using adaptive clock recovery at a PW as
synch source, check if packet switched network is of sufficient quality.
Field Refer to documentation about synchronization of BTS with FIQA,
not used. FIYA.
6. Replace FIxx.

REPORT THIS AD

REPORT THIS AD

7616 OSCILLATOR ADJUSTMENT


TEMPORARILY INTERRUPTED

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7616 Oscillator Adjustment Temporarily interrupted

Severity: Object affected: Object state: Module/Unit:

Minor BCF Enabled ESMx

Fault
reason: Instruction:

Oven oscillator DAC word is within 5% of the min/max limit. Alarm is


activated if the DAC word is between 0-204 or 3891-4095. This alarm
can be activated due to incorrect synchronisation settings in
transmission network.
1. Check the Abis synchronisation that there are valid Rx clock sources
Clock available.
tuning 1.1. If the reference clock is ok, tune the ESMx clock to the correct
DAC frequency.
word 1.2. If the reference clock is not ok, check the alarm history for 8xxx
reaching alarms for the possible reason for the incorrect reference clock. Follow
min/max the instructions on 8xxx alarms. After correcting the reference clock
limit. tune ESMx clock to the correct frequency.

8081 Loss of frame alignment

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
8081 Loss of frame alignment

Object
Severity: Object affected: state: Module/Unit:

Critical TRE Enabled FIxx

Fault
reason: Instruction:

Framing error has been detected in the received signal. This alarm can
Field not be caused by bad quality of the E1/T1 signal or the device at the far-end
used. is not sending valid E1/T1 signal due to misconfiguration.
1. If FIFA PIU is used, refer to the FIFA product documentation for
instructions.
2. Check that the interface settings are correct for the link.
3. Check quality of the E1/T1 line by enabling a Loop to Interface (line)
at the far end equipment. If the alarm is cancelled during the loop test,
check the far-end equipment.
4. Equip an external cable loop to the interface to check that the
interface in FIxx is ok. If the alarm is still active during the loop test, go
to step 6.
5. Check the condition of cables, connectors and correct polarities of
the wire pairs.
6. Check that FIxx is fully inserted in to ESMx.
7. Replace FIxx.
8. Check the signal quality of the transmission path to the alarming
equipment.

7995 Mains breakdown with battery back-up

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7995 Mains breakdown with battery back-up

Severity: Object affected: Object state: Module/Unit:

Minor BCF Enabled FPBA

Fault reason: Instruction:

One or more AC phases of the mains supply are faulty and site is
operating on battery backup.
1. Check the mains supply coming to the site support equipment.
a. If the mains supply is ok, check the EAC cabling between ESMx
and the site support equipment.
OR
b. Check that the cable is completely mated between FPA and the
Field not power module.
used. 2. Repair the site support equipment.
8276 Licence for Flexi TRS Loop Protection is
not available

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
8276 Licence for Flexi TRS Loop Protection is not available

Severity: Object affected: Object state: Module/Unit:

Minor TRE Enabled ESMx

Fault reason: Instruction:

Abis protection and/or protected cross-connections are configured


in used E1/T1 interfaces without a licence.
1. Install and activate the ‘Flexi TRS Loop Protection’ licence at
the BSC.
2. Disable all cross-connections which are controlled by ‘Flexi
TRS Loop Protection’.
Note: Protected bi-directional cross-connections, Masked bi-
Field not directional cross-connections and Abis protection are controlled by
used. ‘Flexi TRS Loop Protection’.

8275 Licence for Flexi Abis TRS Grooming is


not available

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
8275 Licence for Flexi Abis TRS Grooming is not available

Severity: Object affected: Object state: Module/Unit:


Minor TRE Enabled FIxx

Fault
reason: Instruction:

Bypass cross-connections are configured in used E1/T1 interfaces


without a licence.
1. Install and activate the ‘Flexi Abis TRS Grooming’ licence at the
BSC.
2. Disable all the cross-connections which are controlled by ‘Flexi
Abis TRS Grooming’.
Note: Bi-directional cross-connections controlled by ‘Flexi Abis
Field not TRS Grooming’ are of the following granularities: 8 kBit/s, 16
used kBit/s, 32 kBit/s, 64 kBit/s and n*64 kBit/s.

8179 Far-end alarm

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
8179 Far-end alarm

Object
Severity: Object affected: state: Module/Unit:

Major TRE Enabled FIxx

Fault reason: Instruction:

Sent by the equipment in the far-end (TS0 Bit 3), which


indicates that far-end equipment is unable to receive the
signal.
1. Check the far end equipment for alarms 8050, 8066, 8081
and 8086. See the instructions on them.
2. Apply Loop to interface (line) at far end to check that link is
ok. If 8050/8066/8081/8086 alarm is not active at near-end
during the loop test the problem is at the far-end receiver.
Note: 8179 Far-end alarm will be cancelled during this test.
3. Equip an external cable loop to the interface to check that
the interface in FIxx is ok. If 8050/8066/8081/8086 alarm is
active during the loop test, go to step 5. Note: 8179 Far-end
alarm will be cancelled during this test.
Field not used. 4. Check the condition of cables, connectors, and correct
polarities of the wire pairs.
5. Check that FIxx is fully inserted in to ESMx.
6. Replace FIxx.

8020 Blocked from use

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
8020 Blocked from use

Object
Severity: Object affected: state: Module/Unit:

Major TRE Enabled ESMx

Fault
reason: Instruction:

A cross-connection is configured to an interface which is not in use.


Field not 1. Check that all interfaces where cross connection termination points
used. have been set are in use. In cross connection window, blocked cross
connections are highlighted in Italic font.
2. Remove any unnecessary cross connections that have termination
point(s) to non-existing or unused interfaces.

7608 TRX NOTIFICATION

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7608 TRX Notification

Object
Severity: Object affected: state: Module/Unit:
ECxx,
ERxA,
EXxA,
Minor TRX Enabled EOCA

Fault reason: Instruction:

ECxx RTC module has detected that the Frame Clock coming
from the ESMA System module is missing. Air3 loop
services are unavailable.
ECxx RTC 1. Reset the BCF to allow ECxx to attempt resynchronisation
module incoming to incoming FCLK.
frame clock FCLK 2. Replace ECxx.
lost during 3. If alarm is raised for all ECxx modules connected to
runtime. ESMA, replace ESMA.

ECxx RTC
module loop The RF loop synthesizer in ECxx RTC module has not
synthesizer fails to achieved phase lock state after several attempts.
lock. 1. Replace ECxx.

ERxx DDU
module loop The RF loop synthesizer in ERxx DDU module has not
synthesizer fails to achieved phase lock state after several attempts.
lock. 1. Replace ERxx.

ERxx DDU
module SW
upgrade EXxx TRX module cannot identify connected ERxx DDU
impossible, module.
unknown 1. Download and activate the latest release of the BTS SW to
manufacturer. the BTS site.
EOCA Optical module is not responding to ESMA System
module.
1. If on Local EOCA:
1.1 Check the bus cable, cable connectors between ESxx and
Local EOCA.
1.2 Replace Local EOCA.
2. If on Remote EOCA:
ESMA System 2.1 Replace Remote EOCA.
module has lost Note: If this alarm is starting and cancelling repeatedly then
connection to check input voltage supplied to alarming EOCA. Ensure that
XEOCA Optical power supply provides voltage within 42V – 57.0V DC
module. range.

The cooling fan speed of TRX module has increased


EXxx TRX substantially from the commanded fan speed.
module cooling 1. Check the ESMA operational voltage as an increased
fan speed has ESMA voltage could lead to overspeeding of the fans.
increased from the 2. Replace the fan unit.
set speed. 3. Replace EXxx.
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.
EXxx TRX 3. Replace the fan unit.
module cooling 4. Replace EXxx.
fan speed has Note: If “Temperature high/dangerously high” and/or 7621
reduced from the alarm(s) are also active, perform these actions as soon as
set speed. possible.

EXxx TRX 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 alarms are also active. If active, refer to
fan alarm instructions to resolve.
3. Replace the EXxx.
EXxx TRX Note that this alarm remains active if the temperature still
module increases and the “temperature dangerously high” alarm is
temperature high. activated.

EXxx TRX There is no temperature measurement in the EXxx TRX


module unable to module. All temperature sensors inside the module are
read internal broken. Fans are rotating at maximum speed.
temperature 1. Replace the EXxx.
sensors. Note: If fan alarm(s) are active at EXxx, perform this action
as soon as possible.
OVP plug-in unit
is damaged (of
remote or local
EOCA). Replace the OVP plug-in unit.

Internal temperature of EOCA Optical module has exceeded


+85C/+185F.
1. Ensure that the ambient temperature of the base station is
Temperature below +50C/+122F.
inside XEOCA 2. Check if fan alarm is also active. If active, refer to fan
exceeds specified alarm instructions to resolve.
temperature range. 3. Replace the alarming EOCA.

EOCA Optical module detected reduced or no rotation of fan


against commanded speed.
1. Check that nothing obstructs the fan from rotating.
2. Clean the fan unit of dust and/or dirt.
XEOCA Optical 3. Replace the fan unit.
module detected 4. Replace the alarming EOCA.
cooling fan speed Note: If temperature alarms are also active, perform these
degradation. actions as soon as possible.
Over current occured on the output power port(s) of Remote
XEOCA Optical EOCA Optical module. Affected EXxx TRX module(s) are
module detected powered down.
over current on its 1. Check the power cable between Remote EOCA and EXxx.
output power 2. Replace EXxx.
port(s). 3. Replace Remote EOCA.

There is no temperature measurement in the EOCA Optical


module. All temperature sensors inside the module are
XEOCA Optical broken. The fan is rotating at maximum speed.
module detected 1. Replace the alarming EOCA.
temperature sensor Note: If EOCA fan alarm is active, perform this action as
problem. soon as possible.

7607 TRX OPERATION DEGRADED

18 TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7607 TRX Operation Degraded

Object
Severity: Object affected: state: Module/Unit:

ECxx,
ERxA,
Major TRX Enabled EXxA

Fault reason: Instruction:


Measured current consumption of Mast Head Amplifier has
exceeded min or max threshold indicating broken amplifier.
MHA is using its bypass circuit and antenna feeder cable loss is
not compensated.
Current used by 1. Check that the current min/max limits and MHA settings
MHA is out of correspond to the actual configuration.
range for ECxx 2. Check the antenna line for any damage affecting the current
RTC module supply to the MHA.
(antenna A 3. Replace MHA.
bypassed) 4. Replace ECxx.

Measured current consumption of Mast Head Amplifier has


exceeded min or max threshold indicating broken amplifier.
MHA is using its bypass circuit and antenna feeder cable loss is
not compensated.
Current used by 1. Check that the current min/max limits and MHA settings
MHA is out of correspond to the actual configuration.
range for ECxx 2. Check the antenna line for any damage affecting the current
RTC module supply to the MHA.
(antenna B 3. Replace MHA.
bypassed) 4. Replace ECxx.
Measured current consumption of Mast Head Amplifier has
exceeded min or max threshold indicating broken amplifier.
MHA is using its bypass circuit and antenna feeder cable loss is
not compensated.
Current used by 1. Check that the current min/max limits and MHA settings
MHA is out of correspond to the actual configuration.
range for ERxx 2. Check the antenna line for any damage affecting the current
DDU module supply to the MHA.
(antenna A 3. Replace MHA.
bypassed). 4. Replace ERxx.

Measured current consumption of Mast Head Amplifier has


exceeded min or max threshold indicating broken amplifier.
MHA is using its bypass circuit and antenna feeder cable loss is
not compensated.
Current used by 1. Check that the current min/max limits and MHA settings
MHA is out of correspond to the actual configuration.
range for ERxx 2. Check the antenna line for any damage affecting the current
DDU module supply to the MHA.
(antenna B 3. Replace MHA.
bypassed). 4. Replace ERxx.

Diversity Rx
LNA amplifier Both low noise amplifiers in a balanced stage have failed for
chain is broken diversity branch of ECxx RTC module. The main branch is still
in ECxx RTC working.
module. 1. Replace ECxx.
DPTRX initialisation fails due to loose cables, faulty, or
incorrect hardware which results in reduced Tx output power.
1. Check that phase detector cable is correctly mated between
EXxx and EWxx.
2. Check that RF cables connected between EXxx and EWxx
DPTRX are of same length.
initialisation 3. Replace EWxx.
fails. 4. Replace EXxx.

ECxx RTC
module cavity
tuning The cavities are not fine tuned. ECxx RTC module tries to fine
synthesizer tune the cavities periodically. After successful fine tuning the
faulty. Tuning alarm is cancelled.
is only 1. Issue a sector lock/unlock to allow ECxx reconfiguration.
predicted. 2. Replace ECxx.

Measured current consumption of Mast Head Amplifier has


either exceeded the upper limit or dropped below the lower
limit. MHA bypass is not configured/equipped. The upper and
lower limits are user definable during commissioning. Main
ECxx RTC antenna is still working.
module has 1. Check that the current min/max limits and MHA settings
detected that correspond to the actual configuration.
MHA on 2. Check the antenna line for any damage affecting the current
diversity supply to the MHA.
antenna is 3. Replace MHA.
broken. 4. Replace ECxx.
Measured current consumption of Mast Head Amplifier has
either exceeded the upper limit or dropped below the lower
limit. MHA bypass is not configured/equipped. The upper and
lower limits are user definable during commissioning. If
diversity is used, diversity antenna is still working.
ECxx RTC 1. Check that the current min/max limits and MHA settings
module has correspond to the actual configuration.
detected that 2. Check the antenna line for any damage affecting the current
MHA on main supply to the MHA.
antenna is 3. Replace MHA.
broken. 4. Replace ECxx.

User definable minor alarm threshold for VSWR measurement


has been exceeded. The default value is 2.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 it is of correct (sub)band.
3. With external test equipment, measure the Return loss/VSWR
ECxx RTC of the antenna line. Perform step 1 again, if the measurement
module has result is higher than expected.
detected VSWR 4. Revise the VSWR alarm threshold by appending the
above minor commissioning.
limit at antenna. 5. Replace ECxx.
ECxx RTC module has detected that the Frame Clock coming
from the ESMA System Module is missing.
1. Issue a HW reset to ESMA.
2. Check that the bus cable is correctly mated between the ECxx
and ESMA.
3. Check whether other ECxx modules have the same alarm,
ECxx RTC replace ESMA.
module 4. Replace ECxx.
incoming frame Caution: If bus cables are looped back to the same module,
clock FCLK ongoing calls may be dropped or a module may freeze until the
missing at loop is removed. Do not loop bus cables back to the same
startup. module.

ECxx RTC
module internal At startup ECxx RTC module reported internal HW failure.
HW failure. 1. Replace ECxx.

ECxx RTC ESMA System Module detected that SW download to ECxx


module SW RTC module has failed at startup.
download from 1. Issue a HW reset to ESMA.
ESMA System 2. If alarm persists, replace ECxx.
module failed. 3. Replace ESMA.

ERxx DDU
module ERxx DDU module which provides diversity cables for 4UD
frequency band configuration is of a different frequency band.
mismatch with 1. Make sure that the ERxx and/or EXxx are of correct
4UD. frequency band.
Measured current consumption of Mast Head Amplifier has
either exceeded the upper limit or dropped below the lower
limit. MHA bypass is not configured/equipped. The upper and
lower limits are user definable during commissioning. If
diversity is used, ANT B path is still working.
ERxx DDU 1. Check that the current min/max limits and MHA settings
module has correspond to the actual configuration.
detected that 2. Check the antenna line for any damage affecting the current
MHA on its supply to the MHA.
antenna A is 3. Replace MHA.
broken. 4. Replace ERxx.

Measured current consumption of Mast Head Amplifier has


either exceeded the upper limit or dropped below the lower
limit. MHA bypass is not configured/equipped. The upper and
lower limits are user definable during commissioning. If
diversity is used, ANT A path is still working.
ERxx DDU 1. Check that the current min/max limits and MHA settings
module has correspond to the actual configuration.
detected that 2. Check the antenna line for any damage affecting the current
MHA on its supply to the MHA.
antenna B is 3. Replace MHA.
broken. 4. Replace ERxx.
User definable minor alarm treshold for VSWR measurement
has been exceeded. The default value is 2.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 it 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.
ERxx DDU 4. Revise the VSWR alarm threshold by appending the
module has commissioning.
detected VSWR 5. Replace ERxx.
above minor Note that the Dual Duplexer module is able to report the Return
limit at antenna Loss reliably if the TX (BCCH) power in its TxA or TxB input
A. exceeds ca. +32 dBm.
User definable minor alarm treshold for VSWR measurement
has been exceeded. The default value is 2.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 it 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.
ERxx DDU 4. Revise the VSWR alarm threshold by appending the
module has commissioning.
detected VSWR 5. Replace ERxx.
above minor Note that the Dual Duplexer module is able to report the Return
limit at antenna Loss reliably if the TX (BCCH) power in its TxA or TxB input
B. exceeds ca. +32 dBm.

Connected module is either of wrong network type or device


type.
1. Check that the connected ERxx is of correct frequency band
ERxx DDU in respect to the used EXxx.
module not 2. Check that ERxx is connected to EXxx.
supported. 3. Replace ERxx.

ERxx DDU
module reported At startup ERxx DDU module reported internal HW failure.
HW failure. 1. Replace ERxx.
ERxx DDU module did not activate inactive SW and therefore it
ERxx DDU is running with current active package.
module SW 1. Issue a HW reset to EXxx.
activation fails. 2. If alarm reappears after ERxx SW download, replace ERxx.

SW upgrade is aborted due to negative acknowledgement from


ERxx DDU ERxx DDU module during SW download.
module SW 1. Issue a HW reset to ESMA.
upgrade failed. 2. If the alarm persists, replace ERxx.

ECxx RTC module does not respond to polling command from


ESMA System ESMA System Module.
module has lost 1. Check the bus cable chain from ESMA to ECxx.
connection to 2. If the ECxx LED is off, replace the power cable.
ECxx RTC 3. Replace ECxx.
module. 4. Replace ESMA.

One or more fans of the EXxx TRX module are not rotating.
There is a danger of overheating.
1. Check that the fan unit cable is correctly mated to EXxx.
2. Check that there are no obstacles preventing the fan (s) from
EXxx TRX rotating.
module cooling 3. Clean the fan unit of dust and/or dirt.
fan(s) report no 4. Replace the fan unit.
rotation. 5. Replace EXxx.
RF cable autodetection found Rx signal missing from the sector
where Rx diversity is being used.
1. Check that the Rx cabling between EXxx and ERxx are
correctly mated. Check the condition of cables and connectors.
2. If DDU is shared between two sectors, issue BCF reset else
issue a sector reset.
EXxx TRX 3. Check that ECxx/ERxx and EXxx are of same frequency
module detected band.
only one Rx 4. Recommission the site with manual cabling, if Rx diversity is
signal during not to be used.
RF cable 5. Replace ERxx.
autodetection. 6. Replace EXxx.

EXxx TRX module has not detected a fan unit at start up. There
EXxx TRX is a danger of overheating. There is a danger of overheating.
module has 1. Check that the fan unit cable is correctly mated to EXxx.
detected no 2. Replace the fan unit.
fans. 3. Replace the EXxx.

ERxx DDU module is not responding to poll command from


EXxx TRX EXxx TRX module.
module has lost 1. Check that the ER_A cable is correctly mated between EXxx
connection to and ERxx.
ERxx DDU 2. Replace ERxx.
module. 3. Replace EXxx.
EXxx TRX
module Tx
power is at least Tx output power is over 3 dB lower than expected at Digital
3dB less than Power Control circuit block in EXxx TRX module.
expected at 1. Reset TRX/Sector.
DPC. 2. Replace EXxx.

Mismatch between User specified Receiver Band in MHA


Frequency band information and actual network type of ECxx RTC
mismatch module/ERxx DDU module.
between 1. Modify MHA information of antenna settings in the Site
commissioning Commissioning file according to the actual HW configuration.
file and detected 2. Replace the ECxx/ERxx module to correspond to the MHA
hardware. information of antenna settings in the Site Commissioning file.

DPTRX object configured for a sector in which ECxx RTC


module is present.
HW 1. Depending on the desired configuration:
incompatibility 1.1. Disable the DPTRX feature from the TRX object(s) using
detected during the MML command ZERM&ldots:DTRX=0;
DPTRX OR
configuration 1.2. Remove ECxx and recommission with ERxx.
Frequency band/channel or BTS configuration mismatch
between the BTS units and BSC configuration.
1. Check that frequency number defined at the BSC match with
the used ECxx/ERxx at the BTS site.
Hardware 2. Check Antenna Cabling information is defined correctly for
incompatibility all the connected ECxx/ERxx module in SCF.
detected during 3. Check that RF hopping is not used when ECxx is installed.
EXxx TRX 4. Modify TRX object parameters (MML command ZERM:…)
module against the actual configuration at the site.
configuring 5. Replace ERxx or ECxx.

IDD TRX object configured for a sector in which ECxx RTC


module is present.
HW 1. Depending on the desired configuration:
incompatibility 1.1. Disable the IDD feature from the TRX object(s)using the
detected during MML command ZERM&ldots:DTRX=0;
IDD OR
configuration. 1.2. Remove ECxx and recommission with ERxx.

In a 4UD configuration, one or more (not all) Rx cables are


either missing or connected to the same antenna.
1. Check that the bus, power, and RF cables are correctly mated
between the ESxx, EXxx, and ERxx.
2. In case RFCAD is used, make sure that the ERxx which
provides the additional Rx diversity signals has at least one Tx
cable connected to EXxx.
3. Check that the ERxx which provides the additional Rx
diversity signals is of the same frequency band with the 4UD
Incorrect Rx TRX.
cabling with 4. Check that all four Rx paths are connected to different
4UD. antennas.
One of the two Tx cables between the EXxx TRX module and
EWxA WBC is missing or they are not connected to the same
combiner.
1. Check that both Tx cables are fully mated between modules
and connected to the same EWxA.
2. Check that the Tx cabling shown on the BTS Manager view
Incorrect Tx corresponds to the actual Tx cabling.
cabling with 3. Replace EWxA.
DPTRX. 4. Replace EXxx.

One of the two Tx cables between the EXxx TRX module and
the ERxx DDU module is missing or they are combined to the
same antenna path.
1. Check that both Tx cables are fully mated between the
modules and connected to a different ERxx.
2. Check that the Tx cabling shown on the BTS Manager view
Incorrect Tx corresponds to the actual Tx cabling.
cabling with 3. Replace ERxx.
IDD. 4. Replace EXxx.

DPTRX is configured with 4-way combining.


1. Two alternative options depending on the desired
configuration:
1.1. Disable the DPTRX feature from the TRX object(s) using
Incorrect Tx the MML command ZERM&ldots:DTRX=0;
combining with OR
DPTRX. 1.2. Remove the second EWxA from the HW configuration.
ERxx DDU module configuration (Gain or Bias-T) failed.
Internal failure 1. Check SCF that “Antenna Id” is given for alarming ERxx
occurred during unit. If nothing is given provide “Antenna Id” in SCF.
ERxx DDU 2. HW Reset the Exxx Module to allow ERxx unit
module reconfiguration.
configuring. 3. If the alarm reappears, replace ERxx.

Main Rx LNA
amplifier chain Both low noise amplifiers in a balanced stage have failed for
is broken in main branch of ECxx RTC module. If diversity is used, the
ECxx RTC diversity branch is still working.
module 1. Replace ECxx.

One amplifier
stage of Rx
LNA Path A is One of the two low noise amplifiers in balanced stage failed in
broken in ECxx Path A of ECxx RTC module.
RTC module. 1. Replace ECxx.

One amplifier
stage of Rx
LNA Path B is One of the two low noise amplifiers in balanced stage failed in
broken in ECxx Path B of ECxx RTC module.
RTC module. 1. Replace ECxx.

One amplifier
stage of Rx
LNA Path A is One of the two low noise amplifiers in balanced stage failed in
broken in ERxx Path A of ERxx DDU module.
DDU module. 1. Replace ERxx.

One amplifier
stage of Rx
LNA Path B is One of the two low noise amplifiers in balanced stage failed in
broken in ERxx Path B of ERxx DDU module.
DDU module. 1. Replace ERxx.
Path A of Rx
LNA amplifier Both low noise amplifiers in a balanced stage have failed for
chain is broken Path A of ERxx DDU module. If diversity is used, Path B is still
in ERxx DDU working.
module. 1. Replace ERxx.

Path B of Rx
LNA amplifier Both low noise amplifiers in a balanced stage have failed for
chain is broken Path B of ERxx DDU module. If diversity is used, Path A is still
in ERxx DDU working.
module. 1. Replace ERxx.

Phase Detector cable is missing between EXxx TRX module


and EWxA WBC when DPTRX is configured.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 that the Phase Detector cable is correctly mated
between EWxA and EXxx.
Phase Detector 2. Replace the Phase Detector cable.
cable missing 3. Replace EWxA.
with DPTRX. 4. Replace EXxx.
Phase difference between the combined Tx signals is too high,
resulting in reduced Tx output power.
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.
Phase 1. Check that the Phase Detector cable is correctly mated
difference between EWxA and
between Tx EXxx.
signals is too 2. Replace the Phase Detector cable.
high with 3. Replace EWxA.
DPTRX. 4. Replace EXxx.

During RF cable autodetection, Tx combining is found to be


imbalanced. The Rx measurement value differences between
any of the two carriers in the sector is more than 2.5 dB.
1. Check that the ERxx has equal number of EWxx modules in
both Tx paths in 2-/4-way combined configuration. Issue a
RF cable sector reset.
autodetection 2. Check that the Tx cabling is correctly mated between units.
found mixed Check the condition of cables and connectors. Issue a sector
(bypass/2-/4- reset.
way) Tx 3. Replace EWxx.
combining in a 4. Replace EXxx.
sector. 5. Replace ERxx.
The difference limit of Received Signal Strength Indicator
measurement has exceeded between the main and diversity
antennas. Supplementary information fields of RSSI alarm from
BSC history will give further details of which antenna has
exceeded the threshold value.

Supplementary info field can be decoded as follows:


 Absolute RSSI difference in dB (in Hex, for example, ‘1A’
= 26 dB).
 Faulty Antenna ID (in Hex, for example, ‘0A’ = Antenna
ID 10)
For example:
1-6 xx xx xx xx xx xx
123456
1. Check RSSI results with BTS Manager which antenna
appears to have abnormal values. If abnormal values are lower
than values from other antennas, it indicates a disconnected or
faulty cable in the loop or a faulty LNA. If abnormal values are
higher than values from other antennas, it indicates interference
coming outside of the BTS or a faulty cable/module.
2. Check the actual RF cabling and connections against what is
displayed in the BTS Manager.
3. Check whether the selectable RSSI Sample Count is correct
considering the BTS site environment (EP1.1 and later
releases).
4. Check that the RXDL parameter at the BSC is set to a
reasonable value, taking into account the site condition in order
to prevent unnecessary alarms.
5. If the alarm is intermittent, the supplementary information
fields in the BSC alarm history (ZEOH) give further details of
which antenna has exceeded the threshold values.
6. Check and measure the antenna lines.
7. Check the antenna alignment.
RSSI detected 8. Replace ERxx.
Rx signal 9. Replace EXxx.
difference
exceeding Note that if the actual RF cabling and BTS Manager RF cabling
threshold.
view do not match and RFCAD is used to detect the RF cabling,
run a sector reset with RFCAD. This alarm may result when
EP1.1 is upgraded to EP2 and Rx diversity is enabled
afterwards.
Note that if the DDU is shared across two sectors, a BCF reset is
needed.
ERxx DDU module that supplies the two additional diversity Rx
signals for 4UD is lost.
Two Rx 1. Check that the bus and power cables are correctly mated
diversity between ESxx, EXxx and ERxx.
branches lost 2. Replace ERxx.
with 4UD. 3. Replace EXxx.

One or more Rx cables in a 4UD sector are connected to the


ERxx DDU module which is part of another sector.
1. Two alternative options depending on the desired
configuration:
1.1. Disable the 4UD feature from the TRX object(s) using the
Rx cables split MML command ZERM&ldots:DTRX=;
across sectors OR
with 4UD. 1.2. Check the Rx cabling.

Frequency band/channel or BTS configuration mismatch


between the BTS units and configuring BSC configuration.
1. Check that frequency number defined at the BSC match with
the used ECxx/ERxx at the BTS site.
Hardware 2. Check Antenna MO information is defined correctly for all
incompatibility the connected ECxx/ERxx module in SCF.
detected during 3. Check that RF hopping is not used when ECxx is installed.
EXxx TRX 4. Modify TRX object parameters (MML command ZERM:…)
module against the actual configuration at the site.
configuring. 5. Replace ERxx or ECxx.

7606 TRX FAULTY


18 TuesdayNOV 2014

POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7606 TRX Faulty

O
b
j
e O M
c b o
t j d
S a e u
e f c l
v f t e
e e s /
r c t U
i t a n
t e t i
y d e t
: : : :

E
C
x
x
,
E
R
x
A
,
E
S
M
D
x
i
,
s
E
M a
X
a b
x
j T l
A
o R e
,
r X d
E
O
C
A
.

F
a
u
l
t
r
e
a
s
o
n
: Instruction:

E
C
x
x
R
T
C
m
o
d
ECxx RTC module
u
has detected that
l
its cavity stepper
e
motor cannot be
c
moved or its
a
phase detection
v
logic is broken.
i
1. Issue a TRX
t
lock/unlock to
y
allow RTC
i
module
s
reconfiguration.
b
2. If alarm
r
reappears,
o
replace ECxx.
k
e
n
.

E User definable
C major alarm
x threshold for
x VSWR
R measurement
T has been
C exceeded. The
m default value is
o 3.1.
d 1. Check the
u condition of the
l feeder and
e jumper cable,
h their connectors,
a sockets and
s connector seals
d starting from BTS
e end and proceed
t towards the
e antenna end.
c Replace damaged
t feeder cable.
e 2. If MHA is used,
d check that is of
V correct
S (sub)band.
W 3. With external
R test equipment,
a measure the
b Return
o loss/VSWR of the
v antenna line.
e Perform step 1
m again, if the
a measurement
j result is higher
o than expected.
r 4. Revise the
l VSWR alarm
i threshold by
m appending the
i commissioning.
t 5. Replace ECxx.
a
t
a
n
t
e
n
n
a
.

No Tx power
E
detected from
C
any of the TRXs
x
connected to
x
ECxx RTC
R
module.
T
Note: This alarm
C
might take up to
m
one hour to
o
appear after RTC
d
module is reset.
u
1. Issue a sector
l
reset and run a
e
TRX test for each
h
TRX.
a
2. Check the Tx
s
cabling from all
l
the TRXs and
o
issue a sector
s
reset. Run a TRX
t
test for each
T
TRX.
x
3. If the alarm
p
persists, replace
o
ECxx.
w
e
r
f
r
o
m
a
l
l
i
n
p
u
t
s
.

E
C
x
ECxx RTC module
x
detected
R
insufficient
T
power during
C
cavity tuning.
m
RTC is unable to
o
perform cavity
d
tuning.
u
1. Issue a sector
l
lock/unlock to
e
allow ECxx RTC
r
module
e
reconfiguration.
c
2. Check that the
e
Tx cabling
i
between EXxx
v
and ECxx is
e
correctly mated.
d
Check also the
i
condition of
n
cables.
s
3. If all the EXxx
u
connected to the
f
ECxx have raised
f
this alarm,
i
replace ECxx.
c
4. Replace EXxx.
i
5. Replace ECxx.
e
n
t
T
x
p
o
w
e
r
.

E
R
x
x
D
D
U
m
o
d
u
l
e
c
o
n
There is a conflict
n
in the antenna
e
cabling (RF
c
source unit)
t
between the SCF
e
and the actual
d
configuration.
t
1. Check that the
o
antenna cabling
w
information in
r
the SCF refers to
o
the correct and
n
existing ERxx.
g
E
X
x
x
T
R
X
m
o
d
u
l
e
.

E There is no Tx
R power detected
x at TxA input of
x ERxx DDU
D module. If the
D alarm is raised on
U an IDD/DPTRX
m object serving
o the BCCH and
d another
u IDD/DPTRX
l object is available
e in the sector, lock
h the BCCH TRX
a object. BSC will
s reconfigure the
d BCCH to the
e working
t IDD/DPTRX
e object. Otherwise
c the IDD/DP
t enabled sector
e operates with
d reduced
n performance.
o 1. Check the
T whole Tx cabling
x chain between
p EXxx, EWxx (upon
o usage) and ERxx
w that they are
e correctly mated
r between the
a units.
t 2. Check that the
T cables are not
x damaged or bent
A too sharply.
i 3. Replace EXxx.
n 4. Replace ERxx.
p 5. Replace EWxx.
u Note that when
t 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.
There is no Tx
power detected
at TxB input of
ERxx
E
DDU module.If th
R
e alarm is raised
x
on an IDD/DPTRX
x
object serving
D
the BCCH and
D
another
U
IDD/DPTRX
m
object is available
o
in the sector, lock
d
the BCCH TRX
u
object. BSC will
l
reconfigure the
e
BCCH to the
h
working
a
IDD/DPTRX
s
object. Otherwise
d
the IDD/DP
e
enabled sector
t
operates with
e
reduced
c
performance.
t
1. Check the
e
whole Tx cabling
d
chain between
n
EXxx, EWxx (upon
o
usage) and ERxx
T
that they are
x
correctly mated
p
between the
o
units.
w
2. Check that the
e
cables are not
r
damaged or bent
a
too sharply.
t
3. Replace EXxx.
T
4. Replace ERxx.
x
5. Replace EWxx.
B
Note that when
i
the IDD TRX is
n
connected to
p
DDU, if any one
u
path is broken,
t
the alarm is
.
7607; if both
paths are broken,
the alarm is
7606.
E User definable
R major alarm
x threshold for
x VSWR
D measurement
D has been
U exceeded. The
m default value is
o 3.1.If the alarm is
d raised on an
u IDD/DPTRX
l object serving
e the BCCH and
h another
a IDD/DPTRX
s object is available
d in the sector, lock
e the BCCH TRX
t object. BSC will
e reconfigure the
c BCCH to the
t working
e IDD/DPTRX
d object. Otherwise
V the IDD/DP
S enabled sector
W operates with
R reduced
a performance.
b 1. Check the
o condition of the
v feeder and
e jumper cable,
m their connectors,
a sockets and
j connector seals
o starting from BTS
r end and proceed
l towards the
i antenna end.
m Replace damaged
i feeder cable.
t 2. If MHA is used,
a check that it is of
t correct (sub)
a band.
n 3. With external
t test equipment,
e measure the
n Return
n loss/VSWR of the
a antenna line.
A Perform step 1
. again, if the
measurement
result is higher
than expected.
4. Revise the
VSWR alarm
threshold by
appending the
commissioning.
5. Replace ERxx.
Note that when
the IDD TRX is
connected to
DDU, if any one
path 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.
E User definable
R major alarm
x threshold for
x VSWR
D measurement
D has been
U exceeded. The
m default value is
o 3.1.If the alarm is
d raised on an
u IDD/DPTRX
l object serving
e the BCCH and
h another
a IDD/DPTRX
s object is available
d in the sector, lock
e the BCCH TRX
t object. BSC will
e reconfigure the
c BCCH to the
t working
e IDD/DPTRX
d object. Otherwise
V the IDD/DP
S enabled sector
W operates with
R reduced
a performance.
b 1. Check the
o condition of the
v feeder and
e jumper cable,
m their connectors,
a sockets and
j connector seals
o starting from BTS
r end and proceed
l towards the
i antenna end.
m Replace damaged
i feeder cable.
t 2. If MHA is used,
a check that it is of
t correct (sub)
a band.
n 3. With external
t test equipment,
e measure the
n Return
n loss/VSWR of the
a antenna line.
B Perform step 1
. again, if the
measurement
result is higher
than expected.
4. Revise the
VSWR alarm
threshold by
appending the
commissioning.
5. Replace ERxx.
Note that when
the IDD TRX is
connected to
DDU, if any one
path 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.
E
S
M
A
S
y
s
EXxx TRX module
t
does not respond
e
to polling
m
command from
m
ESMA System
o
module. EXxx TRX
d
module can be
u
connected to
l
ESMA either
e
directly or via
h
ESEA System
a
Extension
s
module.
l
1. Check the bus
o
cable chain from
s
ESMA to EXxx.
t
2. If the EXxx LED
c
is off, replace the
o
power cable.
n
3. Replace EXxx.
n
4. Replace ESEA if
e
alarming TRX is
c
connected to it.
t
5. Replace
i
ESMA.
o
Note: If this
n
alarm is starting
t
and cancelling
o
repeatedly and
E
EXxx TRX module
X
is connected with
x
EOCA then check
x
input voltage
T
supplied to
R
EOCA. Ensure
X
that power
m
supply provides
o
voltage within
d
42V – 57.0V DC
u
range.
l
e
.

E RF cable
X autodetection
x failed due to no
x Tx or Rx
T connectivity from
R EXxx TRX module
X to ERxx
d DDU/ECxx RTC
e module. All Rx
t measurement
e report values for
c a TRX object
t were below
e connectivity
d threshold.
n 1. Check that the
o Tx and Rx cables
c between EXxx,
o EWxx, and ERxx
n or ECxx are
n correctly mated
e and the
c connectors and
t cables are not
i damaged. Issue a
o sector reset to
n restart RF cable
t autodetection.
o 2. Check that
E ECxx/ERxx and
R EXxx are of same
x frequency band.
x 3. Wait for DDU
D to come in
D supervisory
U (Fixed green LED
/ on DDU). Issue a
E sector reset to
C restart RF cable
x autodetection.
x 4. Replace EXxx.
R Note that if the
T DDU is shared
C across two
v sectors, a BCF
i reset is needed.
a
R
F
c
a
b
l
e
a
u
t
o
d
e
t
e
c
t
i
o
n
E
X
x
x
T
R
X
m
o
d
u
l
e
RF cable
d
autodetection
e
failed due to no
t
Rx connectivity
e
from EXxx TRX
c
module to ECxx
t
RTC module. All
e
Rx measurement
d
report values for
n
a TRX object
o
were below
R
connectivity
x
threshold.
s
1. Check that the
i
Rx cables
g
between EXxx
n
and ECxx are
a
correctly mated
l
and the
d
connectors are
u
not damaged.
r
Issue a sector
i
reset to restart
n
RF cable
g
autodetection.
R
2. Check that
F
ECxx and EXxx
c
are of same
a
frequency band.
b
3. If all the EXxx
l
connected to the
e
ECxx have raised
a
this alarm,
u
replace ECxx.
t
4. Replace EXxx.
o
d
e
t
e
c
t
i
o
n

E
X
x
EXxx TRX module
x
has detected that
T
it cannot
R
synchronise to
X
the Frame Clock.
m
FCLK is generated
o
by ESMA System
d
Module which is
u
distributed to
l
EXxx TRX
e
modules either
f
directly or via
a
ESEA.
i
1. Check the bus
l
cable chain from
e
ESMA to EXxx.
d
Issue a HW Reset
t
to EXxx.
o
2. Replace EXxx.
s
3. Replace
y
ESMA.
n
4. Replace ESEA.
c
Caution: If bus
h
cables are looped
r
back to the same
o
module, ongoing
n
calls may be
i
dropped or a
z
module may
e
freeze until the
t
loop is removed.
o
Do not loop bus
i
cables back to
n
the same
c
module.
o
m
i
n
g
f
r
a
m
e
c
l
o
c
k
F
C
L
K
.

E There is no ERxx
X DDU module or
x ECxx RTC module
x detected for the
T sector at start
R up.
X 1. Depending on
m the desired
o configuration:
d 1.1
u Connect/check
l ER_A cable
e between ERxx
h and EXxx for the
a associated sector
s and issue a
n sector reset. OR
o 1.2
c Connect/check
o bus cable
m between ECxx
b and ESMA and
i issue a sector
n reset.
e 2. Replace
r ERxx/ECxx.
E 3. Replace EXxx.
R Note that if the
x DDU is shared
x across two
D sectors, a BCF
D reset is needed.
U Note: If the
o configuration is
r 1+X containing
E only one ERxx
C DDU module, it
x has to be
x connected to the
R split EXxx TRX
T module shared
C between the two
m sectors.
o
d
u
l
e
p
r
e
s
e
n
t
.

E
X
x
x
T
R
X
m
o
d
u
Ethernet link to
l
system box
e
broken.
h
This alarm is not
a
visible to
s
customer.
l
o
s
t
c
o
n
n
e
c
t
i
o
n
t
o
E
S
M
A
S
y
s
t
e
m
m
o
d
u
l
e
E
X
x
x
T
R
X
m
EXxx TRX module
o
has detected that
d
the 6.5 MHz
u
reference clock
l
coming from the
e
ESMA System
i
Module is
n
missing. The 6.5
c
MHz reference is
o
generated by
m
ESMA System
i
Module which is
n
distributed to
g
EXxx TRX
6
modules either
.
directly or via
5
ESEA.
M
1. Check the bus
H
cable chain from
z
ESMA to EXxx.
r
2. Replace EXxx.
e
3. Replace ESEA if
f
alarming TRX is
e
connected to it.
r
4. Replace
e
ESMA.
n
Caution: If bus
c
cables are looped
e
back to the same
c
module, ongoing
l
calls may be
o
dropped or a
c
module may
k
freeze until the
m
loop is removed.
i
Do not loop bus
s
cables back to
s
the same
i
module.
n
g
.

E EXxx TRX module


X has detected that
x the Frame Clock
x coming from the
T ESMA System
R Module is
X missing. FCLK is
m generated by
o ESMA System
d Module which is
u distributed to
l EXxx TRX
e modules either
i directly or via
n ESEA.
c 1. Check the bus
o cable chain from
m ESMA to EXxx.
i 2. Replace EXxx.
n 3. Replace ESEA if
g alarming TRX is
f connected to it.
r 4. Replace
a ESMA.
m Caution: If bus
e cables are looped
c back to the same
l module, ongoing
o calls may be
c dropped or a
k module may
F freeze until the
C loop is removed.
L Do not loop bus
K cables back to
m the same
i module.
s
s
i
n
g
.

E
X
x
x
T
R
X
m
o
d
u
l
e
R
x
Rx fixed
f
frequency
i
synthesizer in
x
EXxx TRX module
e
was unable to
d
(maintain) lock to
f
the given
r
channel.
e
1. Reset
q
TRX/Sector.
u
2. Replace EXxx.
e
n
c
y
s
y
n
t
h
e
s
i
z
e
r
f
a
i
l
s
t
o
l
o
c
k
.

E
X
x
x
T
R
X
m
o
d
u
Rx hopping
l
synthesizer 1 in
e
EXxx TRX module
R
was unable to
x
(maintain) lock to
h
the given
o
channel.
p
1. Reset
p
TRX/Sector.
i
2. Replace EXxx.
n
g
s
y
n
t
h
e
s
i
z
e
r
1
f
a
i
l
s
t
o
l
o
c
k
.

E
X
x
x
T
R
X
m
o
d
u
l
Rx hopping
e
synthesizer 2 in
R
EXxx TRX module
x
was unable to
h
(maintain) lock to
o
the given
p
channel.
p
1. Reset
i
TRX/Sector.
n
2. Replace EXxx.
g
s
y
n
t
h
e
s
i
z
e
r
2
f
a
i
l
s
t
o
l
o
c
k
.

E
X
x
x
T
R
X
m
o
d
u
l
e
T
x
Tx output power
p
is less than
o
+14.5dBm at
w
Digital Power
e
Control circuit
r
block in EXxx TRX
i
module.
s
1. Replace EXxx.
l
e
s
s
t
h
a
n
m
i
n
i
m
u
m
a
t
D
P
C
.

E
X
x
x
T
R
X
m
o
d
u
l
e
T
x
p
o
w
Tx output power
e
is over 2 dB
r
higher than
o
expected at
v
Digital Power
e
Control circuit
r
block in EXxx TRX
d
module.
r
1. Replace EXxx.
i
v
e
n
a
t
D
P
C
.

E
X
x
x
T
R
ESMx System
X
Module detected
m
that SW
o
download to
d
EXxx TRX module
u
has failed
l
repeatedly at TRX
e
startup. EXxx TRX
S
module can be
W
connected to
d
ESMA either
o
directly or via
w
ESEA System
n
Extension
l
module.
o
1. Check the bus
a
cable chain from
d
ESMA to EXxx.
f
2. Replace EXxx.
r
Caution: If bus
o
cables are looped
m
back to the same
E
module, ongoing
S
calls may be
M
dropped or a
A
module may
S
freeze until the
y
loop is removed.
s
Do not loop bus
t
cables back to
e
the same
m
module.
M
o
d
u
l
e
f
a
i
l
e
d
.

E
X
x
x
T
R
X
m
o
d
u
EXxx TRX module
l
has detected that
e
its internal
t
temperature has
e
exceeded
m
+95C/+203F.
p
1. Ensure that
e
the ambient
r
temperature of
a
the base station
t
is below
u
+50C/+122F.
r
2. Check if any
e
fan alarms are
d
also active. If
a
active, refer to
n
fan alarm
g
instructions to
e
resolve.
r
3. Replace the
o
EXxx.
u
s
l
y
h
i
g
h
.

E
X
x
x
T
R
X
m
o
d
u
l
e
T
x
h
o
p
p
i
n
g
s
y
Tx hopping
n
synthesizer 1 in
t
EXxx TRX module
h
was unable to
e
(maintain) lock to
s
the given
i
channel.
z
1. Reset
e
TRX/Sector.
r
2. Replace EXxx.
1
f
a
i
l
s
t
o
l
o
c
k
.

E
X
x
x
T
R
X
m
o
d
u
l
e
T
x
h
o
p
p
i
n
g
s
y
n
Tx hopping
t
synthesizer 2 in
h
EXxx TRX module
e
was unable to
s
(maintain) lock to
i
the given
z
channel.
e
1. Reset
r
TRX/Sector.
2
2. Replace EXxx.
f
a
i
l
s
t
o
l
o
c
k
.

Tx output power
is over 2 dB
E
higher than
X
expected at
x
Digital Power
x
Control circuit
T
block in EXxx TRX
R
module.
X
If alarm is raised
m
on IDD/DPTRX
o
object serving
d
the BCCH AND
u
another
l
IDD/DPTRX
e
object is available
T
in the sector,
x
then lock the
p
BCCH TRX object.
o
BSC will
w
reconfigure BCCH
e
to the working
r
IDD/DPTRX
o
object. Otherwise
v
IDD/DP enabled
e
sector operates
r
with reduced
d
performance.
r
Remote:
i
1. Reset
v
TRX/Sector.
e
Local:
n
2. Issue DTRX HW
a
reset via BTS
t
Manager.
D
3. Replace EXxx.
P
C
.

I
n
t
e
r
n
a
l
f
a
i
There was no
l
internal response
u
or timeout
r
occurred during
e
EXxx TRX module
o
configuration.
c
1. Reset the EXxx
c
to allow unit
u
reconfiguration.
r
2. If alarm
r
persists, replace
e
EXxx.
d
d
u
r
i
n
g
E
X
x
x
T
R
X
m
o
d
u
l
e
c
o
n
f
i
g
u
r
i
n
g
.
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.
I 1. Site reset is
r required.
r Note that the
e alarm start is
c based on the
o following:
v
e 1.Large
r alignment
a problems
b between Abis
l clock and
e external clock
L reference, after
o external clock
s reference has
s recovered from
o fault condition.
f
2. Fluctuation in
B
the DAC word.
S
S Alarm start will
S equate to
y significant
n degradation in
c DFCA
h performance.
L
o
g
i
c
a
l
T
R
X
o
b
j
e
c
t
h
a
s
m
i
s
s
i
n
g
t
TRXsig and/or
r
TCH allocation
a
for Logical TRX
n
object is missing
s
from the Abis
m
allocation.
i
1. Check that BTS
s
configuration and
s
Abis time slot
i
allocation
o
matches
n
between the SCF,
t
installed units,
i
and the BSC.
m
2. Add missing
e
time slot
s
allocation to the
l
SCF/BTS by
o
appending the
t
commissioning
a
file.
l
l
o
c
a
t
i
o
n
.

M
i
s
m
a
t
c
h
b
e
t
w
e
e
n
S
C
F
a
n
d
a
c
t
There is a conflict
u
in the antenna
a
cabling (RF
l
source unit)
E
between the SCF
C
and the actual
x
configuration.
x
1. Check that the
R
antenna cabling
T
information in
C
the SCF refers to
m
the correct and
o
existing ECxx.
d
u
l
e
p
o
s
i
t
i
o
n
.

P Phase difference
h between the
a combined Tx
s signals is too high
e resulting in
d reduced Tx
i output power. If
f the alarm is
f raised on an
e IDD/DPTRX
r object serving
e the BCCH and
n another
c IDD/DPTRX
e object is available
b in the sector, lock
e the BCCH TRX
t object. BSC will
w reconfigure the
e BCCH to the
e working
n IDD/DPTRX
T object. Otherwise
x the IDD/DP
s enabled sector
i operates with
g reduced
n performance.
a 1. Check that the
l Phase Detector
s cable is correctly
i mated between
s EWxA and EXxx.
t 2. Replace the
o Phase Detector
o cable.
h 3. Replace
i EWxA.
g 4. Replace EXxx.
h
w
i
t
h
D
P
T
R
X

P
D
U
c
o
Either System
n
module has
t
switched OFF
r
power to ECxx
o
RTC module due
l
to low/high
h
voltage or power
a
is toggled OFF by
s
user from BTS
s
Manager power
w
control menu.
i
1. Check the
t
ESMA input
c
voltage is
h
between 39 –
e
58VDC.
d
2. Power ON the
o
PDU from BTS
f
Manager (BTS
f
Control | Power
E
Control).
C
3. Replace ESMA.
x
x
R
T
C
M
o
d
u
l
e

P
D
U
c
o
n
t
r
o
l
Either System
h
(extension)
a
module has
s
switched OFF
s
power to EXxx
w
TRX module due
i
to low/high
t
voltage or power
c
is toggled OFF by
h
user from BTS
e
Manager power
d
control menu.
o
1. Check the
f
ESMA/ESEA input
f
voltage is
E
between 39 –
X
58VDC.
x
2. Power ON the
x
PDU from BTS
T
Manager (BTS
R
Control | Power
X
Control).
M
3. Replace
o
ESMA/ESEA.
d
u
l
e

RF cable
autodetection
fails due to
inconclusive Rx
R levels received.
F Therefore, BTS
c cannot
a determine RF
b cabling.
l 1. Run RFCAD to
e the failing
a sector(s) by
u performing a
t sector
o lock/unlock or a
d sector reset from
e the BTS
t Manager.
e 2. Define the RF
c cabling manually
t through
i recommissioning.
o
n 3. Replace EWxx.
f 4. Replace
a Erxx/ECxx.
i 5. Replace EXxx.
l 6. Replace ESxx.
e Note that if the
d DDU is shared
. across two
sectors, a BCF
reset is needed.
R
F
c
a
b
l
i
n
g
m
i
s RF cabling is
s detected to be
i missing from
n DPTRX object.
g 1. Check that all
f Tx and Rx cables
o are fully mated
r between the
D EXxx, EWxA and
P ERxx.
T 2. Replace
R EWxA.
X 3. Replace EXxx.
. 4. Replace ERxx.

T In this
w configuration, RF
o cable
o autodetection
r does not support
m more than one
o ERxx DDU
r module in a
e sector.
E 1. Check that the
R Tx cabling from
x EXxx and EWxx
x modules in one
D sector are
D connected to the
U same ERxx
m module.
o 2. Depending on
d the desired
u configuration:
l 2.1. If more than
e one ERxx is
s needed in a
d sector, change
e commissioning
t settings so that
e RF cables are
c defined
t manually.
e OR
d 2.2. Remove
i extra ERxx from
n the sector.
2
-
o
r
4
-
w
a
y
c
o
m
b
i
n
e
d
s
e
c
t
o
r
X
E
O
C
A
o
p
t
i
c
a
l
m
o
d
u
l
e
d
e
t
e
c
t
e EOCA Optical
d module has
e detected that its
x internal
t temperature has
r exceeded
e +90C/+194F.
m 1. Ensure that
e the ambient
t temperature of
e the base station
m is below
p +50C/+122F.
e 2. Check if any
r fan alarm is also
a active. If active,
t refer to fan alarm
u instructions to
r resolve.
e 3. Replace the
. alarming EOCA.
X
E
O
C
A
o
p
t
i
c
a
l
m
o
d
u
l
e
r
e
p
o
r ESMA System
t module detected
e that hardware
d failure has
H occurred in EOCA
W Optical module
f at startup.
a 1. If on Local
i EOCA, replace
l Local EOCA.
u 2. If on Remote
r EOCA, replace
e Remote EOCA.
Incoming clock
errors or optical
X link failures
E either in Local or
O Remote EOCA
C Optical module.
A 1. If on Local
o EOCA:
p 1.1 Check the bus
t cable, the
i connectors or
c replace the cable
a between ESxx
l and Local EOCA.
m 1.2 Check optical
o transceiver plug-
d in unit of Local
u EOCA.
l 1.3 Replace Local
e EOCA.
r 1.4 Check optical
e transceiver plug-
p in unit of Remote
o EOCA.
r 1.5 Replace
t Remote EOCA.
e 1.6 Check the
d optical cable and
i its connector(s)
n and replace cable
c in case faulty.
o 2. If on Remote
m EOCA:
i 2.1 Check optical
n transceiver plug-
g in unit of Local
c EOCA.
l 2.2 Replace Local
o EOCA.
c 2.3 Check optical
k transceiver plug-
f in unit of Remote
a EOCA.
i 2.4 Replace
l Remote EOCA.
u 2.5 Check the
r optical cable and
e its connector(s)
and replace cable
incase faulty.

Advertisements
REPORT THIS AD

REPORT THIS AD

7605 BTS NOTIFICATION

18
TuesdayNOV 2014
POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7605 BTS Notification

Severity: Object affected: Object state: Module/Unit:

Minor BTS Enabled ECxA

Fault
reason: Instruction:

ECxx RTC
module The cooling fan speed has increased substantially from the commanded fan
cooling fan speed.
speed has 1. Check the ESMA operational voltage as an increased ESMA voltage could
increased lead to overspeeding of the fans.
from the set 2. Replace the fan unit.
speed. 3. Replace ECxx.

ECxx RTC The cooling fan speed has reduced substantially from the commanded fan
module speed.
cooling fan 1. Check that nothing obstructs the fan(s) from rotating.
speed has 2. Clean the fan unit of dust and/or dirt.
reduced 3. Replace the fan unit.
from the set Note: If “Temperature high/ dangerously high” and/or 7621 alarm(s) are
speed. also active, perform these actions as soon as possible.
One or more fans of the ECxx RTC module are not rotating. There is a
danger of overheating.
ECxx RTC 1. Check that the fan unit cable is correctly mated to ECxx.
module 2. Check that there are no obstacles preventing the fan(s) from rotating.
cooling 3. Clean the fan unit of dust and/or dirt
fan(s) report 4. Replace the fan unit.
no rotation. 5. Replace ECxx.

ECxx RTC module has not detected a fan unit at start up. There is a danger
ECxx RTC of overheating.
module has 1. Check that the fan unit cable is correctly mated to ECxx.
detected no 2. Replace the fan unit.
fans. 3. Replace ECxx.

ECxx RTC module has detected that its internal temperature has exceeded
+65C/+149F.
ECxx RTC 1. Ensure that the ambient temperature of the base station is below
module +50C/+122F.
temperature 2. Check if any fan alarms are also active. If active, refer to fan alarm
dangerously instructions to resolve.
high. 3. Replace the ECxx.
ECxx RTC
module There is no temperature measurement in the ECxx RTC module. All
unable to temperature sensors inside the module are broken. Fans are rotating at
read maximum speed.
internal 1. Replace the RTC.
temperature Note: If fan alarm(s) are active at RTC, perform this action as soon as
sensors. possible.

The cooling
fan speed of
RTC module
has
increased
substantially 1. Check the ESMA operational voltage as an increased ESMA voltage could
from the lead to overspeeding of the fans.
commanded 2. Replace the fan unit.
fan speed. 3. Replace ECxx.

7602 BCF NOTIFICATION

18 TuesdayNOV 2014

POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7602 BCF Notification

Obje Obj
ct ect
affec stat Modul
Severity: ted: e: e/Unit:

ESEA,
Ena ESMx,
Minor BCF bled EOCA.
Fault
reason: Instruction:

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
BSS between the units. If LMU is used,
synchro check also Q1 cabling and power
nisation supply to the LMU unit.
failed. 4. Replace ESMx.

BTS
Trace User initiated BTS trace collection
Collectio from BTS Manager.
n No repair actions required, alarm
Ongoing is cancelled when BTS trace
. collection is stopped by the user.
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
Commis paths from same Ant connection).
sioned
2. Shelf field contains the TRX
RF
number which contains faulty RF
cabling
cables.
does not
match 3. Also, there may be more RF
BTS cabling errors introduced during
configur commissioning, but only one of
ation. those is reported.
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
Differen sync reference PCM clock is
ce drifted and causes OCXO oven
betwee oscillator to tune incorrectly out
n of correct frequency and (if fault
current persists) will eventually cause
and last handover failures for CS calls.
stable 2. Correct the synchronization
DAC problem in the upper part of
words network.

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

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

ESEA
System
Extensio
n
module ESEA System Extension module is
connect not connected to port 6 of ESMA
ed to System Module.
wrong 1. Connect ESEA to port 6 of
port. ESMA, and issue a BCF reset.
Internal temperature of ESEA
System Extension module has
exceeded +85C/+185F.
1. Ensure that the ambient
temperature of the base station is
ESEA below +50C/+122F.
System 2. If the fault persists, replace
Extensio ESEA.
n Note that this alarm remains
module active if the temperature still
tempera increases and the “temperature
ture dangerously high” alarm is
high. activated.

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

The cooling fan speed has reduced


substantially from the
ESMx commanded fan speed.
System 1. Check that nothing obstructs
Module the fan(s) from rotating.
cooling 2. Clean the fan unit of dust
fan and/or dirt.
speed 3. Replace the fan unit.
has 4. Replace ESMx.
reduced Note: If “Temperature high/
from the dangerously high” and/or 7621
set alarm(s) are also active, perform
speed. these actions as soon as possible.
ESMx System 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 alarms are also
active. If active, refer to fan alarm
instructions to resolve.
ESMx 3. Replace the ESMx.
System Note that this alarm remains
Module active if the temperature still
tempera increases and the “temperature
ture dangerously high” alarm is
high. activated.

There is no temperature
ESMx measurement in the ESMx System
System Module. All temperature sensors
Module inside the module are broken.
unable Fans are rotating at maximum
to read speed.
internal 1. Replace the ESMx.
tempera Note: If fan alarm(s) are active at
ture ESMx, perform this action as soon
sensors. as possible.
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.
External 2. Check that the GPS cable is
synchro correctly mated to LMU.
nisation 3. Check that the latest LMU SW is
signals being used. Download newer SW
disabled if necessary.
. 4. Replace LMU.

EXxx
TRX
module
connect EXxx TRX Module is not connected
ed to to ESEA System Extension
wrong module.
port. 1. Connect EXxx module to ESEA.

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
Incomin
and (if fault persists) will
g
eventually cause handover
referenc
failures.
e clock
1. Check at NetAct if there are any
has
active core network
started
synchronisation related alarms
to
starting with code 1xxx and/or
deviate
2xxx.
rapidly
2. Correct the synchronisation
problem in the upper part of the
network.

The input voltage to the power


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

The input voltage to the power


Supply supply of ESMx is less than 40VDC
voltage or more than 58VDC.
to ESMx 1. Check that the input voltage
near range of System module is within
low/hig specified range.
h limit 2. Replace ESMx.
Certifica
te
Revocati Either Certificate Repository is not
on List reachable or invalid Certificate
retrieval Revocation List at Certificate
failure Repository or Certificate
from Revocation List Size too Big.
Certifica 1. Check Certificate Repository IP
te address in SCF at BTS
Reposit 2. Check BTS cable connectivity
ory with Certificate Repository

Either Certificate Repository is not


reachable or invalid certificate of
Certificate Authority at Certificate
Certifica Repository
te 1. Check Certificate Repository IP
Authorit address in SCF at BTS.
y 2. Check BTS cable connectivity
certifica with Certificate Repository.
te 3. Verify that requested valid
retrieval certificate exist in Certificate
failure Repository.
BTS
security Either Certificate Authority is not
certifica reachable or invalid certificate at
te Certificate Authority
retrieval 1. Check Certificate Authority IP
failure address is correct via SCF from BTS
from Manager.
Certifica 2. Check BTS cable connectivity
te with Certificate Authority.
Authorit 3. Verify that valid BTS Certificate
y exist in Certificate Authority.

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
Unknow a. If the module is compatible with
n the current SW running in the BTS,
module replace the module.
connect b. If the module is not compatible
ed to with the current SW running in the
ESxx BTS, check which SW version
System supports the module. Upgrade the
(Extensi BTS SW to the version that
on) supports the module.
module. 2. Remove the unknown module.

7601 BCF OPERATION DEGRADED


18 TuesdayNOV 2014

POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7601 BCF Operation Degraded

Object
affected Object Module/Unit
Severity: : state: :

Enable ESMx, FAEA,


Major BCF d ESEA

Fault reason: Instruction:

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
All external Q1 bus is closed with FlexiHub Manager.
Q1 devices 3. Check that the Q1 cables are correctly mated
fail to between the ESMx and Q1 devices.
respond. 4. Replace ESMx.
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
Difference Manager/NetAct). Check the alarm history for
between 8xxx alarms reported and resolve any link
PCM and problems occurred.
BTS 3. Check the network synchonisation between
frequency the BSC and the base station.
reference. 4. If alarm is active at multiple sites, check the
quality of synchronisation for the whole BSS.

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.
ESEA System 2. Check that there are no obstacles preventing
Extension the fan(s) from rotating.
Module 3. Clean the fan unit of dust and/or dirt.
fan(s) out of 4. Replace the fan unit.
order. 5. Replace ESEA.
One or more fans of the ESMx System module
are not rotating. There is a danger of
overheating.
ESMx 1. Check that the fan unit cable is correctly
System mated to ESMx.
Module 2. Check that there are no obstacles preventing
cooling the fan(s) from rotating.
fan(s) report 3. Clean the fan unit of dust and/or dirt.
no rotation. 4. Replace the fan unit.
5. Replace ESMx.

ESMx Memory write failure occurred at SW download


System and is not valid. The previously active SW is
Module taken into use.
FLASH 1. Issue a HW reset to ESMx from (remote) BTS
memory Manager.
writing 2. Attempt the SW download again.
error. 3. If this alarm persists, replace ESMx.

ESMx System module has not detected a fan


unit at start up. There is a danger of
ESMx overheating.
System 1. Check that the fan unit cable is correctly
Module has mated to ESMx.
detected no 2. Replace the fan unit.
fans. 3. Replace the ESMx.
ESMx FSEx External Alarm (EAC) module does not
System respond to poll message of the ESMx System
Module has Module.
lost 1. Check that FSEx is set to Active Mode by
connection connecting pins 3-4 of X1103 jumper.
to FSEx 2. Check that the cabling is correctly mated
External between ESMx and FSEx.
Alarm (EAC) 3. Replace FSEx.
module. 4. Replace ESMx.

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.
Loss of BSS Alarm start will equate to degradation in DFCA
Synch while performance.
on Abis clock A site reset will reduce alignment time.

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.
Module 2. Issue a BCF reset.
power cable
During intelligent shutdown, the BTS SW
connections
cuts off the power supply (from ESMA System
are
Module’s “PWR” port) and LapD links for the
incorrectly
affected TRXs, and, during recovery, turns them
configured.
back on. Now, if the DTRX power cabling from
the ESMA is incorrect (that is, DTRX’s 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.

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.


Irrecoverabl
e Loss of BSS Alarm start will equate to significant
Synch. degradation in DFCA performance.

7600 BCF Faulty

18 TuesdayNOV 2014

POSTED BY KAUSHALP13102014 IN NOKIA 2G FLEXI EDGE BTS ALARM DISCRIPTION & TROUBLSHOOTING
≈ LEAVE A COMMENT
7600 BCF Faulty
Object
affecte Object Module/Un
Severity: d: state: it:

Disable ESEA,
Critical BCF d ESMx, FIxx

Fault reason: Instruction:

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)
Air i/f BTS Manager.
reference Note that the site’s bypass transmission will
clock 26 MHz n be cut for 1-2 minutes.
ot available. 3. Replace ESMx.

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
BSS used, check also Q1 cabling and power
synchronisatio supply to the LMU unit.
n failed. 5. Replace ESMx.
‘Abis over IP/Ethernet’, ‘Additional 2 E1,T1
IF’, or ‘Packet Abis Security’ licence is not
Critical installed in the BSC.
transmission 1. Check which transmission licence alarm
licence missing (8273 or 8274) is active and follow the alarm
at the BSC. specific instructions given.

ESMx System Module detected that a


hardware failure has occurred in the ESEA
ESEA System System Extension module.
Extension 1. Issue HW reset to ESMx from BTS
module Manager.
reported HW 2. If fault persists, replace ESEA and reset the
failure. BCF.

ESMA System Module detected that SW


download to ESEA System Extension module
failed at startup.
ESEA System 1. Issue a HW reset to ESEA.
Extension 2. Issue a HW reset to ESMA.
module SW 3. If alarm persists, replace ESEA.
upgrade failed. 4. Replace ESMA.

None of the BTS modules respond to ESMx


polling command.
ESMx System 1. Reset BCF.
Module has 2. Check all cable connections between ESMx
lost connection and ECxx Remote Tune Combiner (ECxx) and
to all ECxx RTCs EXxx TRX modules.
and EXxx TRXs. 3. If the fault persists, replace ESMx.
ESEA System Extension module does not
respond to polling command from ESMA
ESMA System System Module.
Module has 1. Check the power distribution to ESEA.
lost connection 2. Check that the bus cable is correctly mated
to ESEA System between ESMA and ESEA.
Extension 3. Replace ESEA.
module. 4. Replace ESMA.

FIEA/FIPA/FIFA/FIQx/FIYx transport sub-


module 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
ESMx System connector of the PIU.
Module has 3. Replace PIU.
lost connection 4. Replace ESMx.
to FIxx
transmission At the BSC, alarms 7767 BCCH Missing,
submodule. 7706 BTS O&M link failure may be active for
the alarming BCF.

Internal temperature of ESMx System


Module has exceeded +95C/+203F.
1. Ensure that the ambient temperature of
ESMx System the base station is below +50C/+122F.
Module 2. Check if any fan alarms are also active. If
temperature active, refer to fan alarm instructions to
dangerously resolve.
high. 3. Replace the ESMx.
FIEA/FIPA/FIFA/FIQx/FIYx transport sub-
module is of wrong type. This alarm is
reported to the BTS Manager only.
1.1. Replace PIU module with a correct type
FIxx type (as defined in SCF) and issue a HW reset to
mismatch ESMx.
between OR
commissioning 1.2. Set PIU type in SCF according to the
file and actual PIU module type and re-commission
detected the site.
hardware. 2. Replace the PIU and issue a HW reset to
ESMx.

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
Mismatch SCF, issue BCF reset with RFCAD.
between the 4. Modify SCF to match the actual
commissioned configuration or modify the actual
configuration configuration to match the SCF.
and actual 5. Replace ESEA.
configuration. 6. Replace ESMA.

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


BTS has lost CS 1. Check U Plane IP address configurations.
U-Plane 2. Check if there is any filtering/firewall
connection to configurations in the network for U-CS
BSC traffic.