7601 BCF Operation Degraded

Severity:

Object affected:

Object state:

Module/Unit:

Major

BCF

Enabled

ESMx, FAEA, ESEA

Fault reason:

Instruction:

All external Q1 devices fail None of the configured Q1 devices in the Q1 bus are responding to a polling
to respond.
command.
1. Check that Q1 addresses and baud rate match between the Q1 devices
and BSC.
2. If FIFA is used and BTS is polling Q1 equipment, check that Q1 switch
towards the Q1 bus is closed with FlexiHub Manager.
3. Check that the Q1 cables are correctly mated between the ESMx and Q1
devices.
4. Replace ESMx.

Difference between PCM

and BTS frequency
reference.

There is over 5 Hz difference to the 2MHz reference clock due to Abis

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

ESEA System Extension

Module fan(s) out of order.

ESEA System Extension module detected reduced speed or no rotation

of fan(s) against commanded speed.
1. Check that the fan unit cable is correctly mated to ESEA.
2. Check that there are no obstacles preventing the fan(s) from rotating.
3. Clean the fan unit of dust and/or dirt.
4. Replace the fan unit.
5. Replace ESEA.

ESMx System Module

cooling fan(s) report no
rotation.

One or more fans of the ESMx System module are not rotating. There is
a danger of overheating.
1. Check that the fan unit cable is correctly mated to ESMx.
2. Check that there are no obstacles preventing the fan(s) from rotating.
3. Clean the fan unit of dust and/or dirt.
4. Replace the fan unit.
5. Replace ESMx.

ESMx System Module

FLASH memory writing
error.

Memory write failure occurred at SW download and is not valid. The

previously active SW is taken into use.
1. Issue a HW reset to ESMx from (remote) BTS Manager.
2. Attempt the SW download again.
3. If this alarm persists, replace ESMx.

ESMx System Module has

detected no fans.

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

ESMx System Module has

lost connection to FSEx
External Alarm (EAC)
module.

FSEx External Alarm (EAC) module does not respond to poll message of
the ESMx System Module.
1. Check that FSEx is set to Active Mode by connecting pins 3-4 of
X1103 jumper.
2. Check that the cabling is correctly mated between ESMx and FSEx.
3. Replace FSEx.
4. Replace ESMx.

Loss of BSS Synch while on This alarm indicates that the FCLK has slipped between 20 s and 40 s
Abis clock
away from the LMU FCLK while using the Abis clock as a secondary
master-clock.
1. No corrective actions required.
Note that alarm start/cancel is based on the alignment of the BTS clock
to the external clock reference after external clock reference has
recovered from fault condition.
Alarm start will equate to degradation in DFCA performance.
A site reset will reduce alignment time.

Module power cable

One or more of the internal power cable connections does not match
connections are incorrectly power cabling rules. Intelligent shutdown feature may not operate
configured.
correctly.
1. Check the internal power and bus cabling against the product
documentation set.
2. Issue a BCF reset.
During intelligent shutdown, the BTS SW cuts off the power
supply (from ESMA System Module's "PWR" port) and LapD links for the
affected TRXs, and, during recovery, turns them back on. Now, if the
DTRX power cabling from the ESMA is incorrect (that is, 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.
Irrecoverable Loss of BSS
Synch.

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