Fault Code

SO CF I1A:9
SO CF I1A:14
SO CF I1A:15

Alarm Name
Timing bus fault
Bus fault
IDB corrupted

SO CF I2A:8

VSWR limits exceeded

SO CF I2A:33
SO CF I2A:39
SO TRXC I2A:39
SO CF I2A:41
SO CF I2A:42

RX diversity lost
RX cable disconnected
RF loop test fault, degraded RX
Lost communication to TRU
Lost communication to ECU

SO CF I2A:53

HW and IDB inconsistent

SO CF I2A:57
SO TRXC I2A:17

RX path imbalance
Loadfile missing in TRU/DRU

TRX ALARM
TRX ALARM
TRX ALARM
TRX ALARM
TRX ALARM

ABIS PATH UNAVAILABLE

TS SYNC FAULT
BTS INT AFFECTED
BTS EXT AFFECTED
LOOP TEST FAILED

TRX ALARM
TRX ALARM
TRX ALARM
TRX ALARM

PERMANENT FAULT
LOCAL MODE
RF PERFORMANCE FAULT
OML FAULT

AO CON EC1:8
AO TF EC1:1

LAPD queue congestion

PCM sync (No usable PCM-reference)

Alarm Description
This fault arises when the timing bus driver in the DXU is faulty or if two or more TRXs have reported timing
The DXU is not able to send any data on the local bus/Y link
The IDB/RBS database is corrupt or cannot be read by the SW.

If this fault occurs together with pinpointed RUs: CDU or CU, the VSWR at the TRU output has exceeded its
limits defined in the HW.The TRX output power will automatically be reduced. If the VSWR is above 4.0, the
An imbalance in signal strength between the receiver paths has been detected for one, or several, TRXs.
Depending on which of the RX paths that have the lowest signal strengths, one or several of the related faults are
An RX cable is disconnected.
RF Loop test is used to detect problems with the TX and RX by sending dummy bursts between them. One RX path has been detected as f
The DXU has no contact with one or several TRUs/DRUs that are marked as expected in the IDB
DXU has no contact on local bus with one or several ECUs.
HW and IDB inconsistent, for example wrong number of BFUs or PSUs or wrong type of TRU.If TRU, see related
fault SO TRXC I1A:20 for further information.
This fault occurs together with a pinpointed antenna, if the difference in signal strength between two antennas in
the same antenna system exceeds the limits defined using the OMT function Define RX Path Imbalance
Parameters. If the class 1 limit is exceeded, the related fault AO TX I1B:35 is also raised and the TX will be
A SW file is missing in TRU/DRU flash. Probable cause is failed function change or connection of a TRU/DRU
No transmission device exists between the Base Station Controller (BSC) and the Base Transceiver Station
Synchronization has been lost on the uplink or downlink Transcoder and Rate Adaptation Unit (TRAU) channels
A fault exists in a equipment which is internal to the BTS and that leads to that equipment not being able to
A fault exists in a equipment which is external to the BTS and that leads to that equipment not being able to
An automatic loop test of the traffic carrying capabilities has failed
An MO is classified as being permanently faulty when faults in the MO have occurred and been cleared a certain
number of times within a defined period of time. That is, the MO is "unstable". Manual intervention is required to
The MO is in Local Mode, or the MO has changed from Local Mode to Remote Mode while an OML fault exists
Sleeping DRU problem
Problem in Y-link(between DRU and CXU) or DRU hardware issue due to which DRU goes to LOCAL
The TRX signalling load towards the BSC is too high compared to the signalling bandwidth
The synchronisation reference from the PCM network is faulty (for example too much jitter/wander) or missing.

h has been detected as faulty