rbs faul

RBS2000 ALARMS

Uppgjord (ven faktaansvarig om annan) - Prepared (also subject responsible if other)Nr - No.

Finn MagnussonERA/LRB-99:369

Dokansv/Godk - Doc respons/ApprovedKontr - CheckedDatum DateRevFile

KI/ERA/LRB/J00-04-17PA13

RBS 2000 Fault Codes Description (CME R7.1)

The purpose of this document is to give a description of the different fault codes, list possible reasons and suggest corrective actions. Further information on fault finding and corrective actions is provided in maintenance manual.

Note: This document has not been inspected, therefore it should not be used as reference information. See References p4.

BTS Fault Reporting

SW subsystems in BTS supervise their environment and report faults to the O&M Subsystem (OMS). After fault filtering, OMS sets a fault on the Managed Object (MO) responsible for the faulty area. The MO sends a fault report to BSC indicating importance and origin of fault:

Class I1A: fault inside MO, affecting MO functionality.

Class I1B: fault outside MO, affecting MO functionality.

Class I2A: fault inside MO, not affecting MO functionality.

Class EC1: fault outside BTS, affecting MO functionality.

Class EC2: fault outside BTS, not affecting MO functionality.

Fault reports coming from MO CF and TRXC also contain a RU map designating possible faulty HW unit(s).

Upon reception of a BTS fault report, BSC takes following actions:

Class I1A: the MO is taken out of operation and tested.

-If test result indicates MO not faulty, the MO is taken back into operation and the fault is considered as intermittent. A fault counter keeps track of intermittent faults and the MO will be permanently taken out of operation if the number of intermittent faults gets too high.

-If test result indicates MO faulty, the MO is permanently taken out of operation until fault cease or operator intervention. An alarm A2 is issued in BSC/OSS.

Class I1B and EC1: the MO is permanently taken out of operation until fault cease or operator intervention. An alarm A2 is issued in BSC/OSS.

Class I2A and EC2: an alarm A3 is issued in BSC/OSS. The MO stays in operation. Note that a class I2A fault on CF or TRXC can indicate that a class I1A/I1B fault is present on a subordinate MO.

Retrieving fault information

The complete fault information should be analysed in order to perform correct trouble-shooting. It can be retrieved:

From BSC will MML commands:

-All active alarms in a MO: RXASP:MO=RXO;

-All active faults (class 1) in TG: RXMFP:MO=RXOTG-x,FAULTY,SUBORD;

-All active faults in a MO: RXMFP:MO=RXO;

-Fault log for a MO: RXELP:MO=RXO;

On site from OMT:

-All active faults in TG: System view / RBS 2000 / Monitor / Fault status

-Faulty RUs in TG: System view/ RBS 2000 / Display faulty RUs

-Fault log in DXU/TRU/ECU: Hardware view / Select RU / Save log

LED Interpretation

The LEDs give a good overview of the fault situation but should always be used together with the OMT for correct trouble shooting.

Fault led (red):

On = The unit is probably faulty.

Try to find out if the fault is temporary by powering off/on the unit or resetting DXU.

Try to find out if the fault depends on the units environment by moving it to another position.

If this doesnt help, replace the unit. Always check the fault information in OMT and write it on the blue tag to be sent to Repair Center together with the unit.

Blinking on DXU = Two possibilities:

- IDB is missing or corrupted. Reinstall IDB and perform DXU reset.

- Application SW is missing or corrupted (unit running on base application). Reset DXU. If this doesnt help, perform a function change from BSC.

Blinking on TRU/ECU = Two possibilities:

- Lost contact with DXU. The faults CF I1A:14 or I2A:41/42 will probably appear in the OMT fault status monitor. See instructions corresponding to these fault codes.

- Application SW missing or corrupted (unit running on base application): new SW should be automatically downloaded from DXU. If not, reset the unit or reset DXU. The green led should start blinking on the unit.

Note: When a unit is running on base application, it cannot be accessed via OMT. OMT2 might work in some cases.

If the operational led (green) on DXU, TRU and ECU is blinking for a long time (typically 20 to 60 minutes depending on traffic load and LAPD bandwidth), then a SW download is going on. Dont press the reset button!

If the operational led is only blinking on DXU, then the TF is getting synchronised. Can take up to 5 minutes.

Local mode led (yellow):

Off = remote mode. The unit has got a signalling link with BSC.

On = local mode. The unit has no signalling link and cannot be controlled by BSC.

Blinking = remote mode in progress. The unit is waiting for BSC to establish a signalling link.

Note: When a unit (DXU/TRU) is in remote mode and local/remote button is pressed, a fault report EC1:4 is sent to BSC, to inform that some local maintenance will take place on the unit. All traffic MOs get disabled and the signalling link is disconnected. When the local/remote button is pressed again, the signalling link is re-established and the fault EC1:4 is ceased.

Problems with the local mode led:

Led is on all the time, the unit doesnt go into remote even after pressing local/remote button. Check the fault monitor in OMT. There will probably be some indications that the unit has failed its local configuration. After a 10 minutes timer, the unit might come into remote mode to inform BSC that it has failed its local configuration. See fault codes descriptions in this document (for example CF I1A:18, TRXC I1A:21).

Led is blinking all the time: this means that a signalling link couldnt be established with BSC. Check the OMT fault monitor: if no faults are indicated, the problem is probably external to BTS. Make sure that:

-the PCM cables on DXU and cabinet are properly connected

-the transmission parameters are properly set in IDB: DXU TEI value, PCM settings (CRC-4, cascade/stand-alone, spare bits), etc.

-the TEI values are properly set in BSC (RXMOP on CF and TRXC)

-the DCP values and A-bis paths are properly defined in BSC (RXAPP on TG, RXMOP on TRXC)

-the TRH and RBLT devices in BSC are working (RXMDP on CF/TRXC, then STDEP on RHDEV/RBLT)

-the transmission equipment is working.

Tips and tricks for fixing faults

The easiest way to fix a fault is usually to replace HW until the fault disappears. This can however be tiring, time-consuming, and most of all, expensive. Here are some corrective actions that you can try before replacing a unit. In some cases, it will help avoid some unnecessary swap and repair.

Corrective actions from BSC:

1- Block/deblock the CF or TRXC who reported the fault. (This will provoke a fast reset on DXU/TRU).

2- Try to take the CF or TRXC out of service and back into service again. (This will provoke a fast reset on DXU/TRU, erase LAPD links and TRAU links, select new TRHs and TRAs, re-establish links and restart DXU/TRU).

3- Try to perform an unconditional SW download (RXPLI:MO=RXOTG-x,SWVER=yy,UC). After the SW download is completed, a normal reset will occur on DXU, as if the reset button had been pressed. The normal reset is more effective than the fast reset from BSC.

Corrective actions on site:

1- Connect OMT and try to localise the fault(s) by reading the fault monitor and RU logs. (If the newest OMT doesnt provide all necessary functionality, try OMT R15/5 together with OMT2 R13/2. This has to do with OMT-BTS compatibility issues, see the information on PLMBTS homepage).

2- Check all the connections: RF cables, local bus terminator, CDU-bus, PCM cables, power cables, etc.

3- Reset or power off/on the faulty unit(s).

4- Reinstall IDB and press DXU reset.

5- Power off the whole cabinet, wait a while, then power on the cabinet.

6- Swap units inside the cabinet to see if the fault moves with the unit or stays at the same position. If the fault moves with the unit, then the unit is probably faulty. If the fault stays at the same position, then something is wrong with the connections (backplane, CDU-bus, feeders, etc.). If a unit is to be sent to Repair Center, make sure to fill in the blue tag with the fault code.

Replacement of units shall be done according to procedures described in maintenance manual.

Conclusion: The RU map on CF/TRXC fault reports and display faulty RUs function in OMT are good indications to locate faulty units. However, keep in mind that some faults are raised by other factors such as SW, IDB, connections, environment, etc. Thats why it is recommended to see if the faults can be cleared by simple corrective actions before replacing units.

Background Information about RBS 2000

Note 1: Information about IDB, RBS DB, RU DB and internal configuration (also called local configuration) can be found in what is the IDB (http://gsmrbs.ericsson.se/plmbts/lazydocs/2000/idb.html)

Note 2: Fault codes due to Reset are described in Restart Procedures (http://gsmrbs.ericsson.se/plmbts/lazydocs/2000/startcause.html)

This includes CF faults I1A:0-6, I2A:0-6, I2A:40 and TRXC faults I1A:0-6, I1A:19

Note 3: Information about internal architecture of DXU and TRU can be found on http://gsmrbs.ericsson.se/plmbts/lazydocs.html. There is a document for each unit and its associated busses.

Note 4: Handling of DC undervoltage when running on batteries:

DC fallingDC rising

25.7 V *Raise CF I2A:18 (undervoltage class 2)22.2 VCease CF I1A:12

21.2 VRaise CF I1A:12 (undervoltage class 1)25 V Connect battery (2101)

21 VDisconnect batteries (2102/2202)25.5 VConnect batteries (2102/2202)

20 VDisconnect battery (2101)26 V *Cease CF I2A:18

* In SW older than R7D, the limit for undervoltage class 2 is 22.5 V (raise) and 23.5 V (cease).

Note 5: Temperature and humidity ranges supported inside the cabinet (RBS macro) / outside the cabinet (RBS micro):

Operating ModeDefinitionTemperature RangeHumidity Range (non-condensing conditions)Faults occurring when climate outside of range

Normal ConditionAll units are able to function as specified5-45CRelative: 5-85 %

Absolute: 1-25 g/mCF I2A:16 (macro)

CF I2A:44/45 (micro)

Safe FunctionThe units are able to function but with reduced performance.

This operating mode shall not last more than 72 consecutive hours, and a total of not more than 15 days in one year.0-55C

(TX output power is reduced around 45C)Relative 5-90 %

Absolute 1-25 g/m

CF I1A:10 (macro)

CF I1A:19/20 (micro)

TX I1B:12/27

TRXC I2A:11/25

CF I2A:17

The units are not able to function properly but they will not be damaged.

This operating mode shall not last more than 96 consecutive hours, and a total of not more than 5.5 days in a 3 years period.Power on:

- 10 - +60C

Power off :

- 40 - +70C (transport, storage)

Temperature and humidity are measured by sensors in the cabinet and can be monitored with OMT/OMT2.

There is a sensor measuring the temperature of the air coming in and one for the air going out.

Note 6: Latched Faults

Latched faults are faults that dont cease automatically after repair, i.e. block/deblock TRXC or CF is necessary to bring back the MO into operation. The reason is to avoid a situation with cyclic raising/ceasing of the fault following MO state changes. Latched faults are usually I1B faults on TX/RX, for example:

- TX I1B: 1 (CDU VSWR limits exceeded), 2 (CDU output power limits exceeded), 4 (TX antenna VSWR limits exceeded), 12 (TX High temperature), 13 (TX output power limits exceeded), 14 (TX saturation), 27 (TX max power restricted).

- RX I1B: 11 (CDU output voltage fault).

A few abbreviations:

VCOVoltage Controlled Oscillator (13 MHz)

ESBExternal Synchronisation Bus

DSPDigital Signal Processor

RFRadio Frequency

IFIntermediate Frequency

RUReplaceable Unit

MOManaged Object

VSWRVoltage Standing Wave Ratio

Units in Power Supply:

BDMBattery and Distribution Module

BFUBattery Fuse Unit

ECUEnergy Control Unit

PSUPower Supply Unit

IDMInternal Distribution ModuleUnits inside TRU:

PWUPower Supply Unit in TRU

TRUDTRU Digital: contains CPU (MO TRXC), Signal Processing Platform (MO TS) and Radio Control.

TXUTransmitter Unit

PA(U)Power Amplifier (Unit): amplifies TXU signal

RXUReceiver Unit

Units in CDU-D

CUCombining Unit

DUDistributing Unit

FUFilter Unit

References:

BTS fault handling12/155 17-CRT 241 13

Fault coordination RBS 200020/1551-HRB 105 01

List of Supervised Entities OMS2/1551-CRH 201 101

List of Supervised Entities PLS2/1551-CRH 201 102

List of Supervised Entities TFS3/1551-CRH 201 103

List of Supervised Entities RTS3/1551-CRH 201 104

List of Supervised Entities EPS2/1551-CRH 201 105

BTS alarm coordination34/1553-HSC 103 12

O&M support functions (LEDs)24/15517-HRB10501

Diagnostics and fault handling40/155 17-HRB 105 01These documents can be found on

http://gsmrbs.ericsson.se/plmbts/library/2000/fault-info/index.html

4/1551-HRB 105 01 Product Description RBS 2000 general

Reference manual chapter environmental capabilities.

LRU/T-99:013 Improved functionality for RBS 2302 in high ambient temperature conditions

CF I1A

NrFault DescriptionPossible Reasons,

Recommended Corrective ActionsRelated Fault(s)

0Reset, failed restart attemptReset has occurred on DXU. See Note 2.

1Reset, power on

2Reset, switch

3Reset, watchdog

4Reset, SW fault

5Reset, RAM fault

6Reset, Internal function change

7Xbus fault

This fault is raised when 2 or more TRUs have reported communication problems on the X-bus. Possible reasons: faulty backplane, faulty TRUs, intermittent disturbances. Make sure all connections are ok (e.g. bus terminator, extension cable, etc.). Try to switch places between TRUs. Try to power off/on the cabinet. If this doesnt help, replace backplane.TRXC I1A:15

8Timing Unit VCO fault

There are 3 possible reasons for this fault:

1. The VCO control value has drifted out of range (see fault CF I2A:13). The VCO needs to be recalibrated.

2. VCO temperature too low. The start-up heater is stuck.

3. VCO not distributing any 13 MHz signal.1. Fault I2A:13 will probably warn before I1A:8 arises. Note: VCO control value can be monitored with OMT/OMT2.

2,3. Probably a HW fault in DXU or power supply problem. Power on/off DXU. If it doesnt help, change DXU.CF I2A:13

9Timing Bus fault

The fault is raised when the timing bus driver in DXU is faulty or if two or more TRUs have reported timing reception problems. Possible reasons: faulty DXU or DXU backplane, faulty TRU backplane. Try to power off/on DXU, else replace DXU. If this doesnt help, replace backplane or cable between backplanes.TRXC I1A:8

10Indoor temp out of safe range

(Only macro RBS). Temperature in master cabinet is out of the range 0-55(C (Note 5). Fault ceases when temperature comes back in range 2-53(C.Possible reasons:

- the weather

- climate system failure

- TRU dummies missing TRXC I1B:1

11Not used

12DC voltage out of range

The DC voltage (in master cabinet) is below 21.2 V (note 4). This means that AC mains has failed and BTS is running on batteries. The batteries are almost empty and will soon be disconnected. Fault will cease when DC voltage goes above 22.2 V.CF I2A:18 TRXC I1B:3.

13Not used

14Local Bus fault

The DXU is not able to send any data on local bus.Probably a HW fault (e.g. DXU, backplane, local bus terminator). CF I2A:30

15RBS Database Corrupted

The RBS database (Note 1) in DXU is corrupted or cannot be read by the SW.Reinstall IDB with OMT and press DXU reset. If this doesnt help, change DXU.

16RU Database Corrupted

The RU database (Note 1) in DXU is corrupted or cannot be read by the SW.Reset DXU. If this doesnt help, change DXU.

17HW and IDB inconsistent

The IDB doesnt match the HW present in cabinet (e.g. wrong cabinet type, wrong transmission type, etc.).Install the right IDB with OMT and press DXU reset.

18Internal Configuration failed

One or several subsystems in DXU SW have failed their internal configuration (Note 1). DXU SW will not be able to use DXU HW properly.This fault is usually a consequence of faults 15, 16, or 17 (see instructions above).

19Indoor Temp above safe range

(Only micro RBS). Ambient temperature around master cabinet is above 55(C (Note 5). BSC should take BTS out of operation. If the temperature reaches 65(C, BTS will automatically shut down. The fault ceases when temperature goes below 53(C. TRXC I1B:4

20Indoor Temp below safe range

(Only micro RBS). Ambient temperature around master cabinet is below 0(C (Note 5). Fault ceases when temperature is above 2(C. TRXC I1B:5

CF I2A



0Reset, failed restart attemptReset has occurred on ECU. See note 2.

1Reset, power on

2Reset, switch

3Reset, watchdog

4Reset, SW fault

5Reset, RAM fault


7RXDA amplifier current fault

An RXDA in a CDU (or DU) is faulty. Read the BTS logs to find out which side (A or B) is faulty. If the faulty side is not connected to an RX antenna, there is no performance degradation. If the faulty side is connected to an RX antenna, then RX looses diversity and sensitivity decreases by 3.5 dB. If the other RX side is also faulty, then fault I1B:0 is raised on RX.This is probably a HW fault on CDU. Try to power off/on CDU and reset DXU before replacing CDU (or DU).

RX I1B:0

8VSWR limits exceeded

The VSWR at TRU output or at CDU output has exceeded the class 2 limit (and maybe the class 1 limit as well if fault IB:1 or 4 are present on TX). If RU map indicates CDU or CU, the VSWR at TRU output is outside limits. See description of fault I1B:1 on TX.

If RU map indicates Antenna, then the VSWR at CDU output is outside limits. See description of fault I1B:4 on TX.TX I1B:1

TX I1B:4

9Output power limits exceeded

The TX power at CDU output is 7 dB lower than expected. (When the difference is 10 dB, fault I1B:2 is raised on TX.)There is probably a fault on the TX path. Check all TX feeders, both inside and outside cabinet. Check the Pf/Pr cables. Check the RU logs to see which TRU is emitting the fault. Try to switch positions between TRUs/CDUs to find out it is the units or the RF cables that are faulty.

Try to reinstall IDB (this has helped in some cases). Other reason: TX high temperature or saturation (see TX I1B:12 and 14).TX I1B:2

TX I1B:20

10DXU-opt EEPROM checksum fault

(Only in DXUs using 5 MHz optional sync reference).

The EEPROM of the DXU optional synchronisation board contains corrupted data. This data is necessary for the CPU to control the 13 MHz VCO (note 3). Probably a HW fault. It doesnt have any consequence if it occurs while the DXU is running. But at next DXU start-up, the TU will probably not be able to synchronise on the 5 MHz reference and fault I1B:1 will be raised on TF.TF I1B:1

11ALNA/TMA fault

A TMA is probably out of function. RX is not getting any signals from the side using this TMA, which reduces sensitivity by about 3.5 dB. If the other RX side is also faulty, then fault I1B:1 is raised on RX.

The current consumption in TMA is supervised from CDU. The fault is raised when current in TMA is outside the range 33-147 mA. These limits are set in IDB but can be changed with OMT R5/2 or later. The TMA current can be monitored with OMT/OMT2. Make sure that feeders/jumpers are ok and that right IDB is installed. Otherwise replace TMA.

Note: If the TMA has two amplifiers and only one is faulty, the current will be pulsated. This will be detected by CDU and reported (in SW 7D and later) as fault CF I2A:20.RX I1B:1

12RX maxgain/mingain violated

(Only in CDU C+/D). The fault is raised when total gain in RX path (from antenna to TRU) is outside the recommended range. If the gain is too high, there is risk for blocking (a mobile close to BTS overtalks a mobile far away). If the gain is too low, the RX sensitivity is reduced.

Note: In CDU C+/D, the gain in RXDA is adjusted by TRU (via CDU-bus) in order to fit the radio configuration. For example, RXDA gain is reduced when TMA is used and increased when no TMA. The most probable reason is that some attenuation values are wrongly defined in IDB. For example RX feeder loss, HLin/HLout loss, TMA amplification, etc.

The total gain in RX path can be checked with DVT monitor: RTS/RX/LC/PATH/LOSSA (LOSSB). Multiply the result by 3/256 to get value in dB.

13Timing unit VCO ageing

The VCO control value is an integer between 0 and 16384 (214). When it gets outside the range 384-16000, fault I2A:13 is raised on CF. TU functionality is not affected but if the control value gets outside the range 273-16111, fault I1A:8 will be raised on CF and RBS functionality will be lost. The 13 MHz oscillator in DXU is ageing and therefore its control value is drifting outside the authorised range. DXU should be sent to repair for recalibration of the VCO. Note: the VCO control value can be monitored with OMT/OMT2.CF I1A:8

14CDU supervision/communication lost

There is a communication problem on the CDU-bus between TRU and CDU/CU/DU/FU.

Use the BTS logs to localise the fault more precisely.

Possible reasons:

- The CDU-bus cable is faulty, disconnected (check backplane connection as well) or wrongly connected (can happen when using Y-cable).

- The CDU is powered off or faulty

- A TRU connected to the CDU-bus is faulty.TRXC I1B:0 TRXC I2A:22

TX I1B:0

15VSWR/output power supervision lost

(Only CDU-D). One or several Pf/Pr cables between FU and CU are disconnected, check the RU map to find out which.

If a Pf cable is disconnected, the CU cannot function and TX functionality is lost (fault I1B:22 is raised on TX).

If only a Pr cable is disconnected, the VSWR supervision is lost but traffic is not affected.Reconnect or replace the Pf/Pr cable between FU and CU.TX I1B:22

CF I2A:15

16Indoor temp out of normal condition range

(Only macro RBS). Temperature in cabinet is out of the range: 5-45(C. (see note 5)Fault ceases when temperature is in the range 7-43(C.

17Indoor humidity

(Only macro). The humidity inside cabinet is outside the normal condition range (note 5).


The DC voltage (note 4) is either:

1- Above 29 V or

2- Below 25.7 V (22.5 V in older SW) or

3- Below 21.2 V, but in extension cabinet only. In this case, TRXC fault I1B:3 will be raised on all TRUs in extension cabinet.In case 2-3, this means that AC mains has failed and BTS is running on batteries.

Fault will cease when DC voltage is:

1- Below 28 V or

2- Above 26.7 V (23.5 V in older SW) or

3- Above 22.2 V, but in extension cabinet only.CF I1A:12

TRXC I1B:3

19Power system in stand-alone mode

This indicates a fault in opto-communication loop. The power supply system (PSU/BFU/BDM) continues to operate but it cannot be controlled or supervised from ECU.Possible reasons:

- The Opto cable is broken or wrongly connected

- An RU on the opto-loop is faulty or powered off.

20(Up to MR7C) External power fault

There is a failure in AC supply.

From MR7D, this fault is moved to CF EC2:10 (Mains Fail).

Possible reasons:

- AC mains failure.

- ACCU fault (or wrong strapping).

- Disconnected AC input cable to ECU or PSU.

Note: if I2A:20, 23,29 and 37 are raised at the same time, then there is probably a bad connection between ACCU and ECU provoking false alarms.

20(From MR 7D) ALNA/TMA degraded

This fault is raised when the TMA contains two amplifiers and only one is faulty. See CF I2A:11.

21Internal power capacity reduced

The power supply from the PSUs is reduced. Possible reasons:

- AC failure (see CF I2A:20)

- Faulty PSU.

- Missing PSU. This can happen when there are more PSU units defined in IDB than the actual amount installed in cabinet. Can be corrected by doing modify IDB in OMT.

22Battery backup capacity reduced

The power supply from the batteries is reduced. Possible reasons:

- BFU circuit breaker tripped

- Battery overtemperature (battery temp>60(C)

- Faulty BFU or battery.

- Missing BFU or battery. This can happen when there are more BFU or battery units defined in IDB than the actual amount installed in cabinet.

Can be corrected by doing modify IDB in OMT.

23Climate capacity reduced

The climate system is not able to function properly.

Check RU map to find out which part of the climate system is causing problems.Possible reasons:

- No power to the climate unit (check fuses, circuit breakers, power cables, etc.)

- Faulty fan or FCU (fan control unit).

- Faulty heater, heat exchanger, active cooler or CCU (climate control unit).

- Faulty connection between CCU and the heat exchanger or active cooler.

- Faulty connection between CCU and ECU (replace cable or backplane).

- Faulty connection between ACCU and ECU, see note in CF I2A:20.

See maintenance manual for more help.

24CU HW fault

A fault has occurred on CU, affecting TX. See TX fault map to find out which fault it is.The possible I1B faults on TX are: 18,19,21,23,24,25,26.TX I1B:

18,19,21,23,24,25,26

25Loadfile missing in DXU or ECU

A SW file is missing in DXU or ECU flash. Probable cause is failed function change or connection of a unit lacking SW. In case of DXU, a function change must be performed to download the missing file. In case of ECU, the SW file should be transferred from DXU. TRXC I2A:17

26Climate sensor fault

A temperature sensor or humidity sensor is faulty. Check connection to the sensor, otherwise replace sensor. See maintenance manual.

27System voltage sensor fault

The system voltage sensor in ECU is not functioning. ECU reads voltage value from PSU/BFU instead. If the opto-loop becomes faulty, then system voltage supervision is lost. Check system voltage circuit breaker. Otherwise replace ECU.

28A/D Converter fault

The A/D converter in ECU is faulty => measurements from climate and voltage sensors cannot be read. Temperature and humidity supervision is lost. System voltage is read from PSU/BFU instead of sensor. If the opto-loop becomes faulty, then system voltage supervision is lost as well. Replace ECU.

29Varistor fault

A varistor (also called OVP-Overvoltage Protector) in ACCU is faulty. Replace varistor. See maintenance manual.

Note: could be a false alarm, see note in I2A:20.

30Local bus fault

DXU has received a high number of faulty frames on local bus. There are many disturbances on the local bus.Possible reasons:

- Missing local bus terminator

- High load on local bus (e.g. 12 TRU cabinet)

- Extension bus between cabinets disconnectedCF I1A:14

31High-frequency SW fault

Frequent errors during execution of application SW in DXU or ECU. Can lead to restart with startcause 3 (severe SW fault; see note 2).There are many possible reasons: bugs in SW, lack of memory, high processor load, faulty signals or timeouts between SW subsystems, faulty messages from BSC (TR AE55267), protocol errors on local busRead the RU logs to find out what is causing this fault. TRXC I2A:19

32Non-volatile memory corrupted

The contents of the DXU or ECU flash memory is corrupted. The DXU flash contains RBS database, DXU database and SW files for all units. The ECU flash contains ECU SW and ECU database.Try to perform a function change and reinstall IDB. If this doesnt help, power off/on the faulty unit. Otherwise replace the unit.TRXC I2A:16

33RX diversity lost

The imbalance in signal strength between the receiver A- and B-side is supervised on a TRU basis. The fault is raised when one or several TRUs have reported a signal strength imbalance of at least 12 dB during 50 minutes.

This indicates that an RX path to one or several TRUs is faulty. The receiver sensitivity for these TRUs is reduced by about 3.5 dB.

Note: This fault is not raised if one of the faults I2A:7 (RXDA), I2A:11 (TMA current), I2A:34 (TMA voltage) or I2A:39 (RX cable) is active on CF.Enable the diversity supervision monitor in OMT/OMT2 for each TRU, to find out which TRUs are affected and which side (A or B) is faulty. The diversity supervision measurements are only taken every 5 minutes so it takes some time to notice changes. The measurements give signal strength imbalance (SSI, expressed in dB) on each TS. The SSI is equal to RX signal A-side minus B-side so positive values indicate that A-side is better and vice-versa.

Check that all cables on RX-path are properly connected (including HLin/HLout). Also check the antennas. If several cells are affected then maybe two RX feeders have been switched. If only one TRU is affected, then check RX cable between TRU and CDU. Try moving TRUs, CDUs and cables in the cabinet to see if the fault follows the unit(s).

34Output voltage fault

The voltage supply to a TMA is faulty. RX is not getting any signals from the side using this TMA which reduces sensitivity by about 3.5 dB. If the other RX side is also faulty, then fault I1B:11 is raised on RX.

The TMA voltage is supplied by the CDU via the RX feeder. The nominal value is 15 V. The fault is raised when the TMA voltage supply is outside the range 13.75-16.25V.

This is probably a HW fault in CDU. Try to power off/on the CDU. Otherwise replace CDU.RX I1B:11

35Optional synchronisation sourceSee TF I1B:0TF I1B:0

36RU database corrupted

The RU database in one of the following units (CDU, CU, FU, DU, ECU, BFU, PSU, BDM) is corrupted or cannot be read by the SW. If it is the CDU/CU/DU/FU, then fault I1B:0 is raised on TRXC as well and TRU functionality is lost. Check RU map to find out which RU is involved, then check that the communication to the RU is ok (i.e. CDU bus, opto-loop, local bus).

If the communication is ok, power off/on the faulty RU and reset DXU/ECU.

If this doesnt help, change the RU and reset DXU/ECU.CF I2A:38

37Circuit breaker tripped

A circuit breaker in ACCU has tripped. Restore the circuit breaker in ACCU.

Note: could be a false alarm, see note in I2A:20.

38Default values used

A SW subsystem in DXU or ECU is using default parameters for its internal configuration =>the DXU/ECU performance might be reduced.This fault is usually a consequence of faults I2A:36 or I2A:46 on CF. CF I2A:36

CF I2A:46

39RX cable disconnected

An RX cable is disconnected (e.g. CDU RXin, HLin/HLout, Cab HLin). Check the RU map to see which one. Reconnect or replace the disconnected RX cable.RX I1B:9

40Reset, DXU link lostReset has occurred on ECU. See note 2.

41Lost communication to TRU

DXU has no contact on local bus with one or several TRUs that are marked as expected in the IDB.Possible causes:

- TRU missing or powered off (This can happen when there are more TRUs defined in IDB than the actual amount installed in cabinet. Can be corrected by doing modify IDB in OMT)

- Faulty dip switch setting in backplane

- Local bus fault (see CF I2A:30)

42Lost communication to ECU

DXU has no contact on local bus with one or several ECUs that are marked as expected in the IDB.Possible causes: same as in CF I2A:41 but with ECU instead of TRU.


One or several subsystems in ECU SW have failed their internal configuration (Note 1). The ECU will not be able to function properly.Possible causes: HW and IDB inconsistent, ECU database corrupted, communication problems on local bus or opto-loop. Check all the connections. Reinstall IDB with OMT and press DXU reset. If this doesnt help, change ECU.CF I2A:19

CF I2A:36

44(Up to MR7C) Indoor Temp above safe range

(Only micro RBS). Temperature in cabinet is above 45(C.

This fault is removed in MR7D and later.Fault ceases when temperature is below 43(C.

44(From R8) ESB distribution failure

45(Up to MR7C) Indoor Temp below safe range

(Only micro RBS). Temperature in cabinet is below 5(C.

This fault is removed in MR7D and later.Fault ceases when temperature is above 7(C.

46DB parameter fault

The RBS Database or one of the RU databases (in DXU, ECU, CDU, CU, FU, DU, PSU, BFU, BDM) contains one or several erroneous parameters (for example out of range).

SW will use a default value instead, the performance might be reduced.

Check RU map to find out which database is faulty. If it is the RBS Database, reinstall IDB and reset DXU. If it is a RU database, see indications in fault CF I2A:36.

Notice: In some cases, the RU map will indicate several faulty CDUs whereas only one is actually faulty. If this happens, change only one CDU at a time and press DXU reset to see if the fault disappears. CF I2A:38

47Auxiliary equipment fault

A fault has occurred on auxiliary equipment related to TX/RX antenna (for example power booster in active antenna). If I1B:47 is active on TX or RX, then the fault is class 1. If not, the fault is class 2. This is a new feature in R7 where the ARAE (Antenna Related Auxiliary Equipment) can be supervised via external alarms inlets by MOs TX/RX/CF. This allows BSC to take appropriate action on TX and RX which would not be possible if the fault was reported via external alarm.TX I1B:47

RX I1B:47

CF EC1



4L/R SWI (BTS in local mode)

The DXU is in local mode and cannot be controlled by BSC.To bring the DXU into remote mode, you need to press the local/remote button.

5L/R TI (Local to remote while link lost)

This fault tells the BSC that the DXU went into remote mode while the link was down. The field technician doesnt need to care so much about this fault.

CF EC2



9RBS door

(Only for outdoor cabinets 2101, 2102). The RBS door is open.The alarm ceases 5 minutes after RBS door is closed. If door is closed and fault stays active, maybe the little switch behind the door is faulty.

10(From MR 7D) Mains fail

This fault replaces the fault CF I2A:20 (external power fault).See CF I2A:20

TRXC I1A



0Reset, failed restart attemptReset has occurred on TRU. See note 2.

1Reset, power on

2Reset, switch

3Reset, watchdog

4Reset, SW fault

5Reset, RAM fault


7Not used

8Timing reception fault

The TRU gets bad timing signals. Could be a fault in TRU (e.g. Timing Bus receiver, LTU) or TRU backplane. If two or more TRUs have this fault, I1A:9 is raised on CF.Try to switch places between TRUs to see if the fault depends on TRU or TRU backplane. If the fault stays at same position, then TRU backplane is faulty. If the fault follows the TRU, then TRU is faulty.CF I1A:9

9Signal processing fault

Fault on TORA or CMA (note 3).Probably a HW fault. Try to power off/on TRU. If this doesnt help, replace TRU.

10Toura-Dannie communication fault

Fault on RX-bus (note 3).Probably a HW fault. Try to power off/on TRU. If this doesnt help, replace TRU.

11DSP-CPU communication fault

Fault on CPU bus towards DSP0 (note 3). Probably a HW fault. Power off/on TRU. If this doesnt help, replace TRU.

12Terrestrial traffic channel fault

Fault on iLIB (note 3).Probably a HW fault. Power off/on TRU. If this doesnt help, replace TRU.

13RF loop test fault

The RF loop test is used to detect faults on TXU/RXU. Dummy bursts are sent from TORA to TXU (via X-bus), then to RXU and finally back to TORA (note 3). Each test takes about 5 minutes. The fault is raised after 3 failed consecutive tests. (In SW released before MR99:1, fault is raised after only 1 failed test). Probably a HW fault on RXU or TXU. Reset or power off/on TRU. Try to switch positions between TRUs (might be a fault on X-bus). If this doesnt help, change TRU.

14RU database corrupted

The RU database in TRU flash is corrupted or cannot be read by the SW.Reset or power off/on TRU. If this doesnt help, change TRU.TRXC I2A:16

15Xbus communication fault

The TRU has communication problem on X-bus. Could be a fault in TRU (e.g. X-bus driver) or TRU backplane. If two or more TRUs get this fault, I1A:7 will be raised on CF.Try to switch places between TRUs to see if the fault depends on TRU or TRU backplane. If the fault stays at same position, then TRU backplane is faulty. If the fault follows the TRU, then TRU is faulty. CF I1A:7

16Initiation fault

Not possible to initialize ASTRA or LTU (note 3). This fault occurs at TRU start-up and stays as long as the initialisation is unsuccessful.Probably a HW fault. Try to power off/on TRU. If this doesnt help, replace TRU.

17X-interface fault

Fault on X-interface (note 3).Probably a HW fault. Try to power off/on TRU. If this doesnt help, replace TRU.

18DSP fault

DSP SW corrupted or communication fault on the internal DSP bus between DSP0 and DSP cluster (note 3). Reset or power off/on TRU. If this doesnt help, change TRU.

19Reset, DXU link lostReset has occurred on TRU. See note 2

20HW and IDB inconsistent

The IDB doesnt match the TRU/CDU HW (e.g. wrong frequency band, CDU type, etc.).Install right IDB and press DXU reset or check that you have the right TRU/CDU HW.


One or several subsystems in TRU SW have failed their internal configuration (Note 1). TRU SW will not be able to use TRU/CDU HW properly.This fault is usually a consequence of faults 14, or 20 (see above). Also occurs when TRU is not able to retrieve calibration parameters from CDU database. Power off/on TRU and CDU. Check all the connections: CDU-bus, CDU bus extension (Y-cable), backplane. Install right IDB and press DXU reset. If this doesnt help, change TRU, CDU or CDU-bus.TRXC I1A:14

TRXC I1A:20

CF I2A:14

TRXC I1B:0

TRXC I2A:22

22Voltage Supply fault

The voltage supply from PWU to PAU is supervised. The PAU voltage should be around 25.5 V. When it comes outside of the range 24.8V-26.2V, fault I2A:14 is raised on TRXC. The TX output power might be reduced but TRU is still functional.

If PWU is not responding or if PAU voltage comes out of the range 24V-26.3V, fault I1A:22 is raised on TRXC. Probably a HW fault in PWU. Maybe a HW fault in PAU. Power off/on TRU. If this doesnt help, change TRU.TRXC I2A:14

TRXC I1B



0CDU not usable

The CDU cannot be used by the TRU. TRU functionality is lost.

Possible reasons:

- CDU-bus communication fault (CF I2A:14)

- CDU database corrupted (CF I2A:36).

See description of these faults for more info.CF I2A:14

CF I2A:36

1Indoor temp out of safe range

(Only macro RBS). Temperature in extension cabinet is out of range 0-55(C (note 5).Fault ceases when temperature is in range 2-53(C.CF I1A:10.


The DC voltage in extension cabinet is below 21.2 V (note 4).Fault ceases when DC voltage is above 22.2 V.CF I2A:18

4Indoor Temp above safe range

(Only micro RBS). Ambient temperature around extension cabinet is above 55(C (note 5).Fault ceases when temperature is below 53(C

CF I1A:19

5Indoor Temp below safe range

(Only micro RBS). Ambient temperature around extension cabinet is below 0(C (note 5).Fault ceases when temperature is above 2(C

CF I1A:20

TRXC EC1



4L/R SWI (TRU in local mode)

The TRU is in local mode and cannot be controlled by BSC.To bring the TRU into remote mode, you need to press the local/remote button.

5L/R TI (Local to remote while link lost)

This fault tells the BSC that the TRU went into remote mode while the link was down. The field technician doesnt need to care so much about this fault.

TRXC I2A




An RX cable between TRU and CDU is disconnected.Reconnect the RX cable.RX I1B:9

1RX EEPROM checksum faultSee RX I1B:3RX I1B:3

2RX config table checksum faultSee RX I1B:4RX I1B:4

3RX synthesiser unlockedSee RX I1B:5 and 6.RX I1B:5/6

4RX internal voltage faultSee RX I1B:8RX I1B:8

5Astra-Dixie communication faultSee RX I1B:7RX I1B:7

6Astra-Tracy Communication fault See TX I1B:10TX I1B:10

7TX EEPROM checksum fault See TX I1B:6TX I1B:6

8TX config table checksum fault See TX I1B:7TX I1B:7

9TX synthesiser unlockedSee TX I1B:8 and 9TX I1B:8/9

10TX internal voltage fault See TX I1B:11TX I1B:11

11TX High temperature See TX I1B:12TX I1B:12

12TX output power limits exceeded

The difference between actual and expected TX power (at TRU output) exceeds 2 dB. TX performance is degraded but not lost. TX performance is lost when difference exceeds 4 dB and TX fault I1B:13 is raised.Possible reasons: faulty TRU, low power supply, TX cable not properly connectedTX I1B:13

13TX saturationSee TX I1B:14TX I1B:14

14Voltage Supply faultSee TRXC I1A:22TRXC I1A:22

15VSWR/output power supervision lost

(Only CDU A, C, C+). A Pf or Pr cable between TRU and CDU is disconnected. Check the RU map to find out which.

The VSWR and output power supervision is lost but traffic is not affected.Reconnect the Pf/Pr cable. If this doesnt help, check the coaxial connectors in TRU backplane, they can easily be destroyed when inserting a TRU.CF I2A:15

16Non-volatile memory corrupted

The contents of the TRU flash memory is corrupted. The TRU flash contains TRU database and TRU SW. Try to power off/on the faulty TRU or reset DXU. Otherwise replace the TRU.CF I2A:32

17Loadfile missing in TRU

An SW file is missing in TRU flash. Probable cause is failed function change or connection of a TRU lacking SW. DXU should automatically download new SW file to TRU.CF I2A:25

18DSP fault

This fault is not implemented in current BTS SW.N/ATRXC I1A:18

19High-frequency SW fault

Frequent SW errors during execution of application SW in TRU. Can lead to restart with startcause 3 (severe SW fault; see note 2).There are many possible reasons: bugs in SW, lack of memory, high processor load, faulty signals or timeouts between SW subsystems, faulty messages from BSC (TR AE55267), protocol errors on local busRead the RU logs to find out what is causing this fault.CF I2A:31

20RX initiation faultSee RX I1B:10RX I1B:10

21TX initiation faultSee TX I1B:17TX I1B:17

22CDU bus communication faultThis fault is equivalent to CF I2A:14CF I2A:14

23Default values used

A SW subsystem in TRU is using default parameters for its internal configuration =>the TRU performance might be reduced.This fault is usually a consequence of faults I2A:36 or I2A:46 on CF (faulty parameters in CDU) or I2A:26 on TRU. TRXC I2A:26

CF I2A:36

CF I2A:46

24Not used

25TX max power restrictedRefer to TX I1B:27TX I1B:27

26DB parameter fault

The RU Database in TRU contains one or several erroneous parameters (for example out of range). SW will use default value instead, the TRU performance is reduced.Reset TRU. If this doesnt help, change TRU.TRXC I2A:23

TX I1A



0TX offending

This fault has been introduced especially for CDU-D.

It is raised when the BSC has configured two TXs on the same frequency or if the frequency separation is below the guard band (600 kHz in GSM 900 and 1MHz in GSM1800).

The TX will be disabled in order to protect the CU from overheating. Possible reasons:

- BSC wants to move a frequency from one TX to another TX and forgets to disable the first TX before configuring the second TX. The TX will be automatically disabled and reconfigured to a non-offending frequency.

- The frequency planning is wrong (check Data Transcript for this cell).

TX I1B



0CU not Usable

(Only CDU-D). There is a communication problem on the CDU-bus between TRU and CU.

TX functionality is affected since the CDU-bus is used to tune the CU.Possible reasons:

- The CDU-bus cable is faulty or disconnected (check backplane connection as well)

- The CU is powered off or faulty.

- One of the two TRUs controlling the CDU-bus is faulty (e.g. faulty bus driver).CF I2A:14

TRXC I2A:22

TRXC I1B:0

1CDU VSWR Limits Exceeded

When VSWR at TRU output exceeds 2.0, the TX power is automatically reduced until VSWR goes below 2.0. Fault I2A:8 is raised on CF with RU map CDU.

When VSWR exceeds 4.0, fault I1B:1 is raised on TX and BSC should normally disable the TX. Possible reasons: the TX cable between CDU and TRU is faulty or disconnected. The TXU or PAU are faulty or affected by too high temperature (TX I1B:12 or 14).

Note: the CDU red led is turned on and CF RU map indicates CDU which can be misleading since the fault is more likely to be in TRU or TX cable between. TRU/CDU CF I2A:8

(RU map: CDU)

2CDU output power limits exceeded

When TX power at CDU output is 7 dB lower than expected, fault I2A:9 is raised on CF. When the difference is 10 dB, fault I1B:2 is raised on TX.There is probably a fault on the TX path. Check all TX cables, both inside and outside cabinet. Check the Pf/Pr cables. Check the RU logs to see which TRU is emitting the fault. Try to switch positions between TRUs/CDUs to find out it is the units or the RF cables that are faulty.

Try to reinstall IDB (this has helped in some cases). Other reason: TX high temperature or saturation (see TX I1B:12 and 14).CF I2A:9

4TX antenna VSWR limits exceeded

When VSWR at CDU output exceeds the class 2 limit defined in IDB with OMT (default value: 1.8), fault I2A:8 is raised on CF with RU map Antenna.

When VSWR exceeds the class 1 limit (default value: 2.2), fault I1B:4 is raised on TX.Possible reasons: faulty IDB, faulty CDU, TX antenna/feeder faulty or disconnected, Pf/Pr cables and, in some cases, the measurement receiver in TRU/CU.

Hint: try to reinstall the IDB before replacing units.CF I2A:8

(RU map: Antenna)

6TX EEPROM checksum fault

The data stored in TXU eeprom is corrupted. This data is needed by TRU SW to perform internal configuration. Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:7

7TX config table checksum fault

At TRU start-up, the data from TXU eeprom is copied into TRU RAM in order to create the TX configuration table which will be used for internal configuration of TRU SW. This fault is raised when the data in TRU RAM is faulty. Try to reset or power off/on the TRU. If this doesnt help, change TRU.TRXC I2A:8

8TX synthesiser A/B unlocked

One or both of the RF synthesisers in TXU could not lock to the required frequency. (note 3).Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:9

9TX synthesiser C unlocked

The IF synthesiser in TXU could not lock to the required frequency (note 3).Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:9

10Astra-Tracy Communication fault

Communication fault between Astra and Tracy (note 3). Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:6

11TX internal voltage fault

Fault on the internal voltage regulators of the TXU (note 3). Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:10

12TX High temperature

The temperature of the PA transistors is supervised. At 75(C (equals about 45(C cabinet temperature), faults I2A:11 and I2A:25 are raised on TRXC and maximum TX output power is reduced by 2 dB. If the temperature is still over 75(C after 2 minutes, the maximum output power is reduced by another 2 dB. If the temperature is still over 75(C after 2 more minutes the transmitter is automatically shut down and faults I1B:12 and I1B:27 are raised on TX. Possible reasons:

- climate system failure

- TRU dummies missing

- high temperature outside the cabinet

The fault stays active until temperature stays below the limit for 5 minutes. The TX is then enabled and maximum output power is progressively increased. TRXC I2A:11

TX I1B:27

TRXC I2A:25

13TX output power limits exceeded

When TX power at TRU output is 2 dB lower than expected, fault I2A:12 is raised on TRXC. When the difference is 4 dB, fault I1B:13 is raised on TX. Possible reasons: the TX cable between CDU and TRU is faulty or disconnected. The power supply is reduced. The TXU or PAU are faulty or affected by too high temperature. TRXC I2A:12

14TX saturation

TX saturation means that the TXU delivers maximum RF power to the PAU but it is still not sufficient to get the desired power from the PAU. The fault I2A:13 on TRXC is raised at the same time. Other faults such as I1B:2 and I1B:13 on TX might raise as consequence.Many possible reasons both SW and HW related. Can even be temperature related.

Try to block/deblock the TRU. If this doesnt help, power off/on the TRU or replace the TRU. See TR AE38584 for more information. TRXC I2A:13

15

16Voltage supply fault

Power unit not readyThese two faults are replaced by faults I1A:22 on TRXC (from MR99:1 R7, BTS SW B9381R0701).TRXC I1A:22

17TX initiation fault

The TXU could not be initialised. There is probably a fault in the ASIC (Tracy), the synthesisers or the eeprom. This fault occurs at TRU start-up and stays as long as the initialisation is unsuccessful. Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:21

18CU HW fault

(Only CDU-D). There is a fault in CU HW, for example step motor, measurement receiver, etc.Try to power off/on CU and reset TRU. If this doesnt help, replace CU.CF I2A:24

19

CU SW load/start fault

(Only CDU-D). The CU SW has a checksum fault or cannot be started in CU processor. TRU reloads CU SW over CDU-bus and CU is restarted. The fault should cease. If the fault doesnt cease or occurs too often, there is probably a HW fault in CU (for example boot prom corrupted). Try to power off/on CU and reset TRU. If this doesnt help, replace CU.CF I2A:24

20CU input power fault

(Only CDU-D).This alarm is raised by CU when TX power at CU input is different than the value expected (sent by TRU to CU over CDU-bus).Possible reasons:

-TX cable between TRU and CU is faulty or disconnected.

- TRU or CU is faulty. CF I2A:9

21

CU park fault

(Only CDU-D). One of the filter cavities in CU has failed to park or didnt park within the specified time (30 s). This might affect other TRUs as well.

Note: parking means that the filter cavity is tuned outside the TX frequency band in order not to disturb other TRUs. This is done for example when TX is disabled or when CU has lost contact with TRU.Probably HW fault in CU. Could also be a communication fault (CDU-bus). Try to power off/on CU and reset TRU. If this doesnt help, replace CU.

CF I2A:24

22VSWR/Output power supervision lost

(Only CDU-D).The Pf cable between FU and CU is missing or disconnected => CU cannot be tuned so TX functionality is lost. Moreover, antenna VSWR and output power cannot be supervised. Replace the Pf cable between CU and FU.CF I2A:15

23CU Reset, power on(Only CDU-D). CU has been reset. Fault raises and ceases immediately after reset. CF I2A:24

24CU Reset, communication fault

25CU Reset, Watchdog

26CU fine tuning fault

(Only CDU-D). The fine tuning occurs when TX is enabled. The purpose is to adjust the cavity according to TX power variations. Probably a HW fault in CU (for example step motor or cavity axes). Try to power off/on CU and reset TRU. If this doesnt help, replace CU.CF I2A:24

27TX max power restricted

This fault is raised when the TX has been disabled in order to protect it against high temperature. There is a corresponding class 2 fault (TRXC I2A:25) which is raised when the maximum TX output power has been reduced. See description of fault I1B:12 on TX.TRXC I2A:25

TX I1B:12

TRXC I2A:11

47TX Auxiliary equipment fault

A class 1 fault has occurred on auxiliary equipment related to TX antenna (for example power booster in active antenna). CF I2A:47

RX I1B:47

TX I2A



0TX diversity fault

The function TX diversity uses two TRUs to send on one carrier, providing an extra gain of 3 dB.

If one TRU becomes faulty, the TX-diversity functionality is lost but the carrier is still able to carry traffic thanks to the second TRU.Repair the faulty TRU to get back the TX-diversity functionality.

RX I1B



0RXDA amplifier current fault

An RXDA in CDU is faulty and there is no signal coming from the other RX side => RX functionality is lost.Probably a HW fault on CDU. Try to power off/on CDU and reset DXU. If this doesnt help, replace CDU.CF I2A:7

1ALNA/TMA fault

A TMA is faulty and there is no signal coming from the other RX side => RX functionality is lost. Probably a HW fault on TMA. Power off/on CDU and TRU. If this doesnt help, replace TMA.CF I2A:11

2Not used

3RX EEPROM checksum fault

The data stored in RXU eeprom is corrupted. This data is needed by TRU SW to perform internal configuration. Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:1

4RX config table checksum fault

At TRU start-up, the data from RXU eeprom is copied into TRU RAM in order to create the RX configuration table which will be used for internal configuration of TRU SW. This fault is raised when the data in TRU RAM is faulty. Try to reset or power off/on the TRU. If this doesnt help, change TRU.TRXC I2A:2

5RX synthesiser A/B unlocked

One or both of the RF synthesisers in RXU could not lock to the required frequency. (note 3).Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:3

6RX synthesiser C unlocked

The IF synthesiser in RXU could not lock to the required frequency (note 3).Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:3

7Astra-Dixie communication fault

Communication fault between Astra and Dixie (note 3).Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:5

8RX internal voltage fault

Fault on the internal voltage regulators of the RXU. Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:10


An RX cable is disconnected and there is no signal coming from the other RX side => RX functionality lost. Check the CF/TRXC RU map to find out which RX cable is disconnected. Could be CDU RXin, CDU RXout, HLin/HLout, Cab HLin. CF I2A:39

TRXC I2A:0

10RX initiation fault

The RXU could not be initialised. There is probably a fault in ASICS (Dannie, Dixie), the synthesisers or the eeprom. This fault occurs at TRU start-up and stays as long as the initialisation is unsuccessful. Probably a HW fault in TRU. Try to power off/on TRU before replacing it.TRXC I2A:4

11CDU output voltage fault

The voltage supply to the TMA is faulty and there is no signal coming from the other RX side => RX functionality lost.

Note: the TMA voltage is supplied by the CDU via the RX feeder. The nominal value is 15 V. The fault is raised when the TMA voltage supply is outside the range 13.75-16.25V.This is probably a HW fault in CDU. Try to power off/on the CDU. Otherwise replace CDU.CF I2A:34

47RX auxiliary equipment fault

A class 1 fault has occurred on auxiliary equipment related to RX antenna (for example TMA in active antenna).CF I2A:47

TX I1B:47

CON EC1 and EC2



8LAPD queue congestion

The LAPD concentrator in DXU supervises the length of uplink message queues.

Class 2 fault is raised when a message queue is more than 70% full. Class 1 fault is raised when a message is discarded due to queue overflow. Fault ceases after 5 seconds of operation without queue overflow.Possible reason: the signalling load is high and the signalling bandwidth is reduced due to use of LAPD concentration or LAPD multiplexing.

Try to increase LAPD bandwidth (by reducing the concentration factor for example).

TF I1B



0Optional synchronisation source


The long-term synchronisation reference from the optional oscillator is faulty (e.g. too much jitter/wander) or missing. The VCO goes into hold-over mode (i.e. stops using the reference) and after 5 minutes, fault I2A:35 is raised on CF. If the reference hasnt come back within one hour (hold-over timeout), fault I1B:0 is raised on TF and TF is disabled. There is probably a fault on the 5 MHz oscillator in DXU. It might be a temporary disturbance in the oscillator. Try to power off/on DXU. Then wait a while (several hours) to see if the fault comes back. If this doesnt help, replace DXU.

Note: at DXU cold start, it will take at least one hour for the 5 MHz oscillator to warm up and stabilize. CF I2A:35

1DXU-opt EEPROM checksum fault


The EEPROM of the DXU optional synchronisation board contains corrupted data. This data is necessary for the CPU to control the 13 MHz VCO (note 3). The TU is unable to synchronise.Probably a HW fault. Try to power off/on the DXU. If this doesnt help, replace DXU.CF I2A:10

TF EC1 and EC2



0EXT Sync (No usable external reference)

(Only when TF mode is slave).

The synchronisation reference from ESB (External Sync Bus) is missing.

- If the fault occurs while TF is trying to synchronise, then fault EC1:0 is raised after 5 minutes.

- If the fault occurs while TF is synchronised, then TF goes into hold-over mode and if the ESB reference hasn't come back within 2 minutes (holdover timeout), fault EC1:0 is raised and TF is disabled. No class 2 fault is raised before the class 1.Possible reasons:

- The master TF is disabled or powered off.

- The master TF is in stand-alone mode (e.g. after PCM link break longer than 10 minutes)

- The ESB cable is faulty or disconnected.

- A terminator on the ESB is faulty or missing.

1PCM Sync (No usable PCM reference)

(Only when TF mode is master or stand-alone).

The synchronisation reference from the PCM network is faulty (e.g. too much jitter/wander) or missing.

- If the fault occurs while TF is trying to synchronise, then fault EC1:1 is raised after 5 minutes.

- If the fault occurs while TF is synchronised, then TF goes into hold-over mode (i.e. stops using the reference) and after 5 minutes, fault EC2:0 is raised on TF. If the PCM reference hasnt come back within one hour (hold-over timeout), fault EC1:1 is raised on TF and TF becomes disabled. This is probably a transmission fault. Check the PCM line, the transmission equipment, etc.

Check PCM quality with BSC printout DTQUP and OMT monitor Phase difference error, PCM.

Note: the preferred PCM reference can be set in the IDB, e.g. PCM A, PCM B or both.

TS EC1



3TRA (Remote transcoder lost)

The TRAU frames (speech/data) coming from BSC to a specific TRU time-slot are missing or corrupted. This is most likely to be a fault in the BSC (e.g. no TRA allocated, no connection in Group-Switch, etc.) or in the A-bis transmission path.

BTS logs

......................................................................................................................................................... Note: The purpose of this document is to help interpret BTS logfiles. It has not been inspected, therefore should not be used as reference information. ..........................................................................................................................................................

I- General

In each main RU (DXU, TRU, ECU), there is 64 kBytes RAM reserved for storing log. The log area in RAM is a circular memory so the oldest information is overwritten when the size of the logs exceeds 64 kBytes. The log area can be saved to a text file with OMT.

When a certain event or fault occurs during SW execution, the concerned SW process writes a line in the log. Each line consists of 4 columns: - Date and time stamp - Name of process - Name of source file with line number where the printout occured - Message

Example: [98-12-06 08:14:30.567] OMS_HWU hwu.c:33518 FAULT:LB:0, raise i2a MISSING RU TRU 0 [98-12-06 08:14:32:078] PLS_SAP_MAIN sap_main.c:1567 TRACEH:TRU3 CONNECTED

Date and time-stamp: The date and time is set every 24 hours from BSC after a request from BTS (A-bis message Calendar Time Request). When the date-stamp shows 90-01-01, it means that the time has not been set by BSC yet, e.g. after reset. As soon as the BTS regains contact with BSC, it will send a calendar time request.

Name of process: The process name starts with subsystem indication: P for PLS (Platform Subsystem), T for TFS (Traffic Functions Subsystem), E for EPS (Energy and Power Subsystem), OMS for OMS (Operation & Maintenance Subsystem), RTS for RTS (Radio Transceiver Subsystem).

Source file and line number This information is mostly used by the designer for debugging.

Message The messages are divided into 4 categories, according to importance. - FAULT - TRACEH (high importance trace) - TRACEM (medium importance) - TRACEL (low importance) By default, only FAULT and TRACEH are output to the logfile. TRACEM and TRACEL can also be enabled via DVT (Debug and Verification Terminal). It is however recommended to only enable these traces on specific processes, otherwise the log will become full very quickly. It is also possible to trace signals, monitor values or events and output the result to the log. More information in "DVT command description". Note that DVT is only for internal use at ERA/LR.

II- Questions and answers

Q:Which log to analyse first? A:First, the DXU log, it gives an overview ot the status of the entire BTS. Then the log of the unit showing incorrect behaviour (TRU or ECU).

Q:What should I have in mind when examining the log? A:The log is presented in reverse chronological order, the most recent information is displayed at the top of the logfile. Since the log is cyclic, the oldest information is overwritten by the newest (FIFO, First In First Out).

Q:Where should I start? A:Start from the bottom and find the restart lines (90-01-01 00:00:00 NONAME dbg_main.c:1503 TRACEH:RESET TIME: ). Then interpret downwards, starting from each restart line.

III- Explanation for a few TRACEH in DXU log:

Note: the following traces are valid for MR 7A (SW R4/8). Some traces may have been changed or removed in later SW.

PRIVATE1- TRACEH giving info about PCM configuration:

PLS_PCM pcm_external.c:3467 PLS_PCM_TOPOLOGY_INFO with pcm_network_tplgy=0/1 pcm_last_in_chain=0/1 pcm_network_tplgy indicates the network topology that was defined in IDB with OMT. 0=cascade and 1=stand-alone pcm_last_in_chain is only valid for cascade topology. 0=false, 1=true. PLS_PCM pcm_external.c:3507 PLS_PCM_CRC4_INFO with A=0/1/2 B=0/1/2 This message indicates if CRC-4 is used on PCM A and PCM B. The CRC-4 is defined in IDB with OMT. 0=not valid, 1=off, 2=on. CRC-4 is only valid for E1. CRC-4 setting must be the same in DXU and in BSC (defined with MML command with DTIDC on DIP RBLT). PLS_PCM pcm_hw_config.c:1392 TRACEH:Initial config performed. pcm_2Mbit=0/1 0=false (=> DXU configured for T1), 1=true (=> DXU configured for E1) RTS_TF rts_tf_ctrl.c:3232 TRACEH:PCM_UPDATE_RPT arrived, 0/1 0/1 0/1 0/1 0-2 0-2 The Timing Function has received synchronisation information from the PCM handler. There are 6 bits in the PCM update report. Bit 1: PCM A error (0=no error, 1=error) Bit 2: PCM A available (0=not available, 1=available) Bit 3: PCM B error (0=no error, 1=error) Bit 4: PCM B available (0=not available, 1=available) Bit 5: PCM synchronisation source 1 (0=PCM_A, 1=PCM_B, 2=optional oscillator) Bit 6: PCM synchronisation source 2 (0=PCM_A, 1=PCM_B, 2=optional oscillator)

PRIVATE2- TRACEH giving info about cabinet configuration:

OMS_RBS_MAIN dbh_flash.c:304 TRACEH:Cabinet type:1-6 1=2101, 2=2102, 3=2103, 4=2202, 5=2301, 6=2302 OMS_RBS_MAIN dbh_flash.c:306 TRACEH:Climate system:0-5 0=2301/2302_no_climate, 1=2202_fans, 2=2101_heat_exchanger, 3=2103_heat_exchanger, 4=2101_air_conditioner, 5=2102_air_conditioner_and_heat_exchanger OMS_RBS_MAIN dbh_flash.c:307 TRACEH:Power system:0-10 0=undefined, 1=2101_no_battery, 2=2102_no_battery, 3=2101_with_battery, 4=2102_with_battery, 5=2103_with battery, 6=2301/2302_internal_battery, 7=2202_230VAC_optional_battery, 8=2202_24VDC, 9=2202_48VDC, 10=2302_external_battery Otherconfiguration parameters indicated in OMS_RBS_MAIN dbh_flash can be translated with the document Installation Database Description

PRIVATE3-TRACEH to be used as checkpoints during function change For more information, refer to the document BTS SW handling on this homepage.

P_LOADER ldf_loader.c:1839 TRACEH:Open loadfile TRLRxxx OK (yy units) The A-bis message "Load Data Init" has been received. TRU file is going to be downloaded to DXU flash. At the same time, DXU will copy this file into TRU flash ("yy units" indicates the number of TRUs who shall receive the file). In later SW, "yy units" indicates the number of Main RUs present in cabinet. PLS_MMI_LED_HND mmi_common.c:544 TRACEH:MMI Indication for OPERATIONAL state FLASH The green led on DXU/TRU/ECU will be flashing during SW download. P_LOADER ldf_loader.c:2086 TRACEH:Loadfile close OK The A-bis message "Load Data End" has been received. TRU file has been successfully downloaded to DXU flash and TRU flash. P_LOADER ldf_loader.c:1839 TRACEH:Open loadfile DXLRxxx OK (0 units) The A-bis message "Load Data Init" has been received. DXU file is going to be downloaded to DXU flash. It is not going to be copied to any other units, that's why "0 units" is written. In later SW, this has been changed and the total number of Main RUs present in cabinet is indicated. P_LOADER ldf_loader.c:2086 TRACEH:Loadfile close OK DXU file successfully downloaded. A-bis message "Load Data End" received. P_LOADER ldf_loader.c:1839 TRACEH:Open loadfile ECLRxxx OK (yy units) The A-bis message "Load Data Init" has been received. ECU loadfile is going to be downloaded to DXU flash. At the same time, DXU will copy this file into ECU flash ("yy units" indicates the number of ECUs who shall receive the file).In later SW, "yy units" indicates the number of Main RUs present in cabinet. P_LOADER ldf_loader.c:2086 TRACEH:Loadfile close OK ECU file successfully downloaded. A-bis message "Load Data End" received. OMS_HWU cpu_dex.c:1301 TRACEH:DXLRxxx, STARTCAUSE:6 (or FUNCTION_CHANGE_BSC), APPL. TYPE:1 The CF has sent a "Restart Required Report" to BSC who replies with "Start Command". The new SW is then loaded from flash to RAM and a normal local configuration takes place (more info in Restart Procedures document on this homepage). "Appl Type" 0 is for base application, 1 is for load application. The calendar time is erased so all time stamps after this message will indicate 90-01-01 until the local configuration is finished and BTS receives a new "Calendar Time Report" from BSC.

PRIVATE4-TRACEH to be used as checkpoints during normal local configuration

NONAME dbg_main.c:1503 TRACEH:RESET TIME: NONAME dbg_main.c:1516 TRACEH:DXLRxxx, STARTCAUSE: , APPL.TYPE:1 The reason for restart is indicated. Refer to Restart Procedures for more info. OMS_RBS_MAIN dbh_flash.c:271 TRACEH:INFO - RBS DB was read from flash The RBS Database is copied from flash into RAM. At this point, the RBS DB only contains information about PCM, cabinet configuration and passive RUs (the PCM and cabinet parameters will be written in the log according to paragraph 1 and 2). To be complete, the RBS DB needs information about the active RUs (TRU, ECU, CDU, etc.). OMS is now going to fetch these parameters and copy them into DXU RAM. OMS_RBS_MAIN rbs.c:60885 TRACEH:RBS Database installed and distributed The RBS Database in DXU RAM is now complete. The SW subsystems can start fetching parameters from the Database in order to perform their local configuration. More info about IDB and local configuration in "What is the IDB?" (Note: By comparing the time stamps between "RBS DB read from flash" and "RBS Database installed and distributed", you can find out how long time it took for OMS to get all the information from RU Databases.) (in DXU): RTS_IDH_SERVER rts_idh_dxu.c:945 TRACEH:OMS_DB_READY_RPT received (in TRU): RTS_LOCAL_CONF local_conf.c:796 TRACEH:OMS_DB_READY_RPT received RTS is aware that Database is ready and is going to start its local configuration. (in TRU): RTS_LOCAL_CONF local_conf.c:836 TRACEH:DB LOCAL CONFIGURATION OK. RTS SW in this TRU has successfully performed its local configuration. When all SW subsystems in a unit have done their local configuration, the unit can go into remote mode. PLS_MMI_LED_HND mmi_common.c:278 TRACEH:MMI Indication for LOCAL_MODE state FLASH All SW subsystems in the unit have successfully performed local configuration and the unit can go into remote mode.

PRIVATEPreparedDoc NrRevDateApproved

Finn MagnussonERA/LRB-00:182PA100-04-17LRB/JC

1/21

_937825490.doc

rbs faul

Documents