602 BCF Notification

7602 BCF NOTIFICATION

Severity:
Object affected:
Object state:
Module/Unit:
Minor
BCF
Enabled
ESEA, EXxA/ESMx, EOCA.
Fault reason:
Instruction:
Backplane IP connectivity lost
ESMx System Module has lost IP connectivity with all integrated TRX resources.
No troubleshooting actions required. A BCF Reset is triggered and the alarms get
cleared.
Baseband bus minor operation error occurred in ESMx System module
Baseband bus minor operation error has occurred in System Module (ESMx). There i
s no impact in BTS performance.
1. Issue a BCF reset for alarm re-evaluation.
There is no need to replace the ESMx.
BSC is not responding to BTS init procedure
BSC is not responding to BTS_OMU_STARTED message.
1. Check site type at BSC and the version of ESMx being used. If the ESMA is bei
ng used and the BCF is created as Flexi Multi on BSC or another version of the E
SMx is being used and the BCF is created as Flexi EDGE on BSC, then it causes th
is fault.
2. Check that the BCF is not locked.
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 resolv
e it.
2. If another BTS is the synchronisation master, check if that it is up and aliv
e.
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 stop
ped by the user.
Commissioned RF cabling does not match BTS configuration.
Manually defined RF cabling in SCF is incorrect as verified against BTS Configur
ation 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 ma
in, 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 commissionin

g, but only one of those is reported.

Note 4. Refer to latest Flexi EDGE BTS Commissioning document for RF cable autod
etection 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, bu
t only one of those is reported.
RF Module fan operation deteriorated
RF Module cooling fan is not rotating at the specified speed.
This notification alone does not need immediate actions.
1. Check that nothing obstructs the fans from rotating.
2. Clean the fan unit for dust and/or dirt.
3. Replace the fan unit.
4. If the alarm persists, replace the RF Module.
If any temperature related alarms are active, perform these actions as soon as
possible.
RF Module fan broken (RF Module fan(s) report no rotation)
One or more fans of the RF Module are not rotating. There is a danger of overhea
ting.
1. Check that the fan unit cable is correctly mated to the RF Module.
2. Check that there are no obstacles preventing the fans from rotating.
3. Clean the fan unit of dust and/or dirt.
4. Replace the fan unit.
5. Replace the RF Module.
RF Module unable to read internal temperature
There is no temperature measurement in the RF
side the module are broken. Fans are rotating
1. Replace the RF Module.
If fan alarm(s) are active at the RF Module,
sible.

sensors
Module. All temperature sensors in
at maximum speed.
perform this action as soon as pos

RF Module temperature high

RF Module has detected that its internal temperature has exceeded +90 C / +194 F.
1. Ensure that the ambient temperature of the base station is below +55 C / +131 F
.
2. Check if any fan alarms are also active. If active, see the fan alarm instruc
tions to resolve the alarms.
3. If the alarm persists, replace the RF Module.
This alarm remains active if the temperature still increases and the "temperatu
re dangerously high" alarm is activated.
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 refer
ence PCM clock is drifted and causes OCXO oven oscillator to tune incorrectly ou
t of correct frequency and (if fault persists) will eventually cause handover fa
ilures 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 Power Port(s) switched off by user-initiated action
One or several power output(s) was switched Off from 2G Flexi BTS Site Manager.
1. Check from 2G Flexi BTS Site Manager that all power outputs are switched ON.
2.If all power outputs are ON, then issue a BCF reset.
ESMx System Module cooling fan speed has increased from the set speed.
The cooling fan speed of System Module has increased substantially from the comm
anded fan speed.
1. Check the ESMx operational voltage as an increased ESMx voltage could lead to
overspeeding of the fans.
2. Replace the fan unit.
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.
2. Clean the fan unit of dust and/or dirt.
3. Replace the fan unit.
4. Replace ESMx.
If "Temperature high/ dangerously high" and/or 7621 alarm(s) are also active, pe
rform these actions as soon as possible.
ESMx System module detected GSM/EDGE incompatible RF module
A non-GSM/EDGE capable RF Module is either connected to ESMx System Module or ch
ained to RF Module (FXxx).
Replace incompatible RF Module (FXxx).
ESMx System Module temperature high.
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 instru
ctions 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 s
ensors inside the module are broken. Fans are rotating at maximum speed.
1. Replace the ESMx.
If fan alarm(s) are active at ESMx, perform this action as soon as possible.
External synchronization 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 antenn
a 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.
BSC is not responding to BTS init procedure
BSC is not responding to BTS_OMU_STARTED message.
1. Check site type at BSC and the version of ESMx being used . If the ESMA is be
ing used and the BCF is created as Flexi Multi on BSC or another version of the
ESMx is being used and the BCF is created as Flexi EDGE on BSC this will cause t
his fault.
2. Check that the BCF is not locked.
Hardware failure detected in RF module
Failure in internal timing due to fault in RF module or invalid topology.
1. If RF Module is dedicated, check if more than one optical cables are connecte
d from System Module to RF Module. If the optical cables are not of equal length
, either the alarm "Hardware failure detected in RF module" or the alarm "Invali
d RF module hardware configuration detected" could be reported by the System Mod
ule. In such a case, remove the redundant optical cable.
2. If the RF Module is chained, check if more than one optical cables are connec
ted from System Module to this RF Module, or from a previous chained RF Module t
o this RF Module. If the optical cables are not of equal length, either the alar
m "Hardware failure detected in RF module" or the alarm "Invalid RF module hardw
are configuration detected" could be reported by the System Module. In such a ca
se, remove the redundant optical cable.
As a consequence, the chained units beyond the alarming unit cannot be detected
.
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 c
orrect 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.
Invalid RF Module hardware configuration detected
The detected RF Module (FXxx) hardware configuration is not supported.
In dedicated 2G mode:
1. Ensure that the following maximum number of FXxx modules are not exceeded:
a) FXxx module chaining, a maximum of 3 FXxx modules can be chained per RP3 opti
cal port in ESMx.
b) Mixture of chained and unchained, a maximum of 12 FXxx modules in ESMx.
When RF module is shared (that is, connected) between ESMx and FSMx:
1. Ensure that the following maximum number of FXxx modules are not exceeded:
a) Only one FXxx module shared with FSMx per RP3 optical port in ESMx.
b) Maximum of 2 shared FXxx modules in ESMx.
c) FXxx module in OPT3 port in ESMx cannot be shared with FSMx.
To cancel this alarm, either a BCF reset or FXxx module HW reset (in case viola
tion occurs in specific RP3 port only) is required.
ESMx System Module has lost connection to peer technology controlled RF Module

The shared RF Module has stopped responding. This could be due to an RF reset gi
ven from the peer technology (master) System Module (FSMx).
Remote:
1. Check if a reset was given to the shared RF Module by the peer technology Sys
tem Module. If yes, then this alarm will be cancelled when shared RF Module is a
gain up and running.
2. Check peer technology System Module alarms.
Local:
3. Check that optical cables are correctly mated between system modules and shar
ed RF Module. Replace in case broken.
Mismatch between commissioned and configured state for composite cell
Mismatch has occurred between the commissioned state (via SCF) and configured st
ate at BSC for the composite cell feature.
1. If composite cell is configured at BSC and not commissioned, then recommissio
n the BTS with composite cell feature state as commissioned.
2. If composite cell feature is commissioned but not configured on BSC, then loc
k the corresponding BCF and enable the composite cell feature at BSC and then pe
rform unlock of the BSC.
Mismatch between RF module type in commissioning file and detected hardware
The RF Module connected to the System Module (ESMx) is not commissioned.
Remove the incorrect RF Module type (RM or RRH) from ESMx port or RF Module port
and connect the correct RF Module type (RRH or RM).
Optical port IDs are not identical in ESMx and FSMx for shared RF Module
Same optical port IDs of ESMx and FSMx System modules must be used with shared R
F Module. In case of high bandwidth LTE, peer FSMx defines 2 links to shared RF
Module and in that case System Module (ESMx) port number can be either of them t
o yet be acceptable.
1. Check that shared RF Module is connected to the correct port in FSMx.
2. Ensure that ESMx is using the same port ID for shared RF Module as FSMx.
Packet Abis Security establishment failure
Either Security Gateway is not reachable or mismatch of cryptographic proposals
at BTS and Security Gateway end or authentication failure during IKE protocol.
1. Check the Security Gateway IP address at BTS is correct via SCF from 2G Flexi
BTS Site Manager.
RF Module ambient temperature outside operating range
Ambient temperature of the RF module is either below -35 C/- 31 F or over +50 C/ +1
22 F.
The temperature sensor for ambient temperature is located in the RF Module. An a
lgorithm is used to calculate the ambient temperature outside of the casings or
cabinet. If the BTS has just started up or is transmitting at a low power level
in extreme cold environments, this alarm could be generated for up to one hour a
fter BCCH transmission is started.
1. Ensure that the ambient temperature at the site is within the limits (between
-35 C and +55 C / -31 F and +131 F).
2. Check if any fan alarms are also active. If active, refer to fan alarm instru
ctions to resolve.
2. If the alarm persists, replace the RF Module.
The upper limit for ambient temperature is +50 C/ +122 F and temporary it can be
+55 C/ +131 F.
RF Module cooling fan speed has increased from the set speed
The cooling fan speed of the RF Module has increased substantially from the comm
anded fan speed.
1. Check the RF Module (FXxx) operational voltage as an increased input voltage
could lead to over speeding of the fans.

2. Replace the fan unit.

3. Replace the RF Module.
This alarm can co-exist with alarm 'RF module Cooling fan Speed has reduced' as
both alarms can be started on the basis of status of individual fan.
RFM running with older software image
RFM/RRH having different RF Module SW image from the RF Module SW running in the
BTS.
1. From BSC using MML terminal attach and activate a BTS SW package to any empty
pack, for example, NW or FB. The BTS package should be the same version which i
s already running in the BTS.
BSC SW S15.2 or higher is required for the RFM SW upgrade process to work.
2. Using 2G Flexi BTS Site Manager in Local or Remote mode, download again the s
ame BTS SW which is already running in the BTS. Do not select Forceful Upload.
3. RF Module activates the SW by RFM restart. Wait until the restart is done. Th
e alarm cancels automatically after the RFM has restarted.
With RF Sharing the RFM SW is managed by RFM Master.

RF 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 is obstructing the fans from rotating.
2. Clean the fan unit of dust and/or dirt.
3. Replace the fan unit.
4. Replace the RF Module.
If "Temperature high/dangerously high" and/or 7621 alarm(s) are also active, pe
rform these actions as soon as possible. This alarm can co-exist with alarm 'RF
module Cooling fan Speed has over speeded' as both alarms can be started on the
basis of status of individual fan.
Shared FXxx module detected two synchronisation master sources
Only one System Module can be the synchronization master to an RF Module at a ti
me. During the RF Module startup procedure, if the synchronization master has be
en already detected and another System Module attempts to act as a synchronizati
on master, this alarm is raised. In slave mode BTS shall take air interface cloc
k reference from synchronization master System Module.
1. Check which System Module should be set as the synchronization master.
2. Recommission the other System Module to be the synchronization slave.
Shared RF Module detected no peer technology System Module during startup
According to the Site Configuration File (SCF), a peer technology System Module
was defined as a synchronization master for the shared RF Module FXxx. However,
the RF Module was not able to detect System Module during startup.
1. Check that the optical cable is connected and correctly mated between the FSM
x and FXxx.
2. Check that the optical SFP plug-in matches the optical cable type (that is, m
ulti mode or single mode cable) at both ends. Replace in case it is broken.
3. Check the alarms on the peer technology FSMx.
4. Replace the RF Module.
5. Replace the FSMx.
Supply voltage to ESEA near low/high limit
The input voltage to the power supply of ESEA is less than 40VDC or more than 58
VDC.
1. Check that the input voltage range of System Extension module is within speci
fied 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 58

VDC.
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 Certifi
cate Authority at Certificate Repository.
1. Check Certificate Repository IP address in SCF at BTS.
2. Check BTS cable connectivity with Certificate Repository.
3. Verify that requested valid certificate exist in Certificate Repository.
BTS security certificate retrieval failure from Certificate Authority
Either Certificate Authority is not reachable or invalid certificate at Certific
ate Authority.
1. Check Certificate Authority IP address is correct via SCF from BTS Manager.
2. Check BTS cable connectivity with Certificate Authority.
3. Verify that valid BTS Certificate exist in Certificate Authority.
RF module software updated and waiting restart
Latest FRM SW is downloaded from BSC/EM on RM/RRH but activation is still pendin
g.
1. Identify sector id for impacted RFM/RRH and perform sector block/lock before
triggering RFM hardware reset from Remote/Local Element Manager.
2. Issue BCF reset from Element Manager / BSC.
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 t
he 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 su
pports the module.
2. Remove the unknown module.