Cell Site Structure and troubleshooting from OSS

This procedure covers basic structure and troubleshooting of a site from an OSS perspective in situations where a site does not restore
whether partially or completely, for example after a rehome or software upgrade.

BTS Hierarchy:
In order to troubleshoot a site from the BSC it is necessary to have a knowledge of the logical hierarchy of the BTS (In the BSC) as
compared with its physical elements.
Physically the BTS is made up of RUs (Replaceable Units) such as the DXU, TRU, etc.
Logically these RUs are known as MOs (Managed Objects).
The Main MO of any site, the TG (Transceiver Group) is not associated with any hardware at the BTS but resides in the BSC. It can
be thought of as an Address of the site within the BSC. Connecting the TG to the Site in the Field is the DIP (Digital Path). It
represents the T1 (Abis Interface) link to the BTS. In the BTS itself there are RUs, which are represented by MOs in the BSC.
BSC

BTS
DXU

TG

RXOCF
RXOTF
RXOIS

DIP (RBLT)
TRU

TRU
RXOTRX
RXOTX
RXORX
RXOTS
(-0&&-7)

TRU
RXOTRX
RXOTX
RXORX
RXOTS
(-0&&-7)

RXOTRX
RXOTX
RXORX
RXOTS
(-0&&-7)

BTS Hierarchy
Managed Objects
RXOTG-XX
RXOCF-XX
RXOTF-XX
RXOIS-XX
RXOTRX-XX-Y
RXOTX-XX-Y
RXORX-XX-Y
RXOTS-XX-Y-0&&-7

Definition
Transceiver Group
Control Function
Timing Function
Interconnect Switch
Transceiver Controller
Transmitter
Receiver
Time Slots

Physical representation
Entire RBS/DIP (usually)
DXU
Oscillator within the DXU
Switch in the DXU
TRU
Transmitter within the TRU
Receiver within the TRU
Time Slots within the TRU

Numbering convention:
All MOs in a site share the number of the TG. For example, if a site has TG 46, all of the sub-MOs will have number 46. The MOs
related to the TRUs will have additional numbers added to them which refer to the TRUs assignment within the TG. For example,
TRU #0 in RXOTG-46 will have RXOTRX-46-0, RXOTX-46-0, RXORX-46-0, and RXOTS-46-0-0&&-7. The additional
designations on the time slots refer to the time slot position within that TRU (i.e. TG 46, TRU 0, TS 0 thru 7).
Any object in this list has a superior and a subordinate MO. What this means is that in order to perform certain operations it is
necessary to remember the status of subordinate and superior MOs. When loading and deblocking always follow the hierarchy from
top to bottom, and when taking out of service always follow the hierarchy from bottom to top.

Troubleshooting example #1 Sector down

When experiencing trouble at a site always get the Big Picture of how the site is behaving. Is the whole site down, or only certain
sectors? Run the following commands to see at what level the site is experiencing problems:
AL
(print alarm list)
RLC2
RP
3L
2P
=
LLEC: (print cell resources)

ALLIP
This will give an overview of all the alarms that exist on the BSC at the time which may point you in the right direction for your
specific site, then with the RLCRP command you will see which sectors have resources and which dont. In our example, if sector B
was down you would probably see alarms in the alarm list related to the TRUs at the site as well as the CF. You would see alarms for
Logical Channels Availability, and probably alarms on the CF and the individual TRUs. They would look like this in the alarm
printout:
What youre looking at
Alarm header: gives the alarm class (A1=critical, take immediate action, A2=less critical, take action during wkg hours, A3=take
action within a week, O1 &O2=observation only), switch name (i.e. PLT12C0), alarm number, date and time the alarm occurred. The
alarm information is printed underneath. When investigating an alarm look at the date and time stamp to see when it came in.
A1/APT "PLT12C0 C000G00" 560 010302
0606
CELL LOGICAL CHANNEL AVAILABILITY SUPERVISION
CELL
SCTYPE
CHTYPE
CHRATE
SPV
PL223B
BCCH
SDCCH
TCH
FR
1
A3/APT "PLT12C0 C000G00" 550 010302
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO
RXOCF-46

0603

RSITE
PL223

A2/APT "PLT12C0 C000G00" 551 010302

RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT

ALARM SLOGAN
BTS INTERNAL

MO
RXOTRX-46-2

0603

RSITE
PL223

ALARM SLOGAN
OML FAULT

The alarm on the CF, BTS Internal, means a fault on the CF which is caused by an RU inside the BTS (TRU, PSU, ECU, etc.) The
OML FAULT alarm on the TRX means that the TRU has lost communication with the BSC.
If the whole site were down due to a T1 failure, you would see the Cell Logical Channels Availability Supervision alarms for all 3
sectors, plus the following alarms on the CF, and the DIP:
A2/APT "PLT12C0 C000G00" 551 010302
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO
RXOCF-46

0603

RSITE
PL223

A1/APT "PLT12C0 C000G00" 548 010302

DIGITAL PATH FAULT SUPERVISION

0603

DIP
46RBLT

HG

ALARM SLOGAN
OML FAULT

DIPEND

FAULT
ALL1

SECTION

A2/APT "PLT12C0 C000G00" 549 010302

DIGITAL PATH UNAVAILABLE STATE FAULT
DIP
UAS
46RBLT -

UASR

UASB

SECTION

DATE
010314

TIME
152955

0603
BLOCKING

DATE
010302

TIME
060301

In this case we have an OML Fault on the CF and the whole site has lost communication with the BSC. Also there are faults on the
DIP which indicate the fault code (ALL1) and the state (Unavailable).

RLCRP
The RLCRP command gives the resources for a cell, i.e. number of BCCH, SDCCH, CBCH (always 0) and TCH. If the cell is up and
carrying traffic the printout will look like this:
<rlcrp:cell=pl223a;
CELL RESOURCES
CELL
PL223A
BPC
6824

BCCH
1

CBCH
0

6830

CHANNEL
TCH-7343
TCH-24273
TCH-24272
TCH-7349
TCH-24285
TCH-24284
TCH-7347
TCH-24281
TCH-24280
TCH-7352
TCH-24291
TCH-24290
TCH-7421
TCH-24429
TCH-24428
TCH-7384
TCH-24355
TCH-24354
TCH-7660
TCH-8587
TCH-8586
SDCCH-34067
SDCCH-34066
SDCCH-34065
SDCCH-34064
BCCH-34818

6828
6833
6905
6865
7158
8086

SDCCH
4

CHRATE
FR
HR
HR
FR
HR
HR
FR
HR
HR
FR
HR
HR
FR
HR
HR
FR
HR
HR
FR
HR
HR

NOOFTCH
7- 14
SPV
1,2
1
1
1,2
1
1
1,2
1
1
1,2
1
1
1,2
1
1
1,2
1
1
1,2
1
1

STATE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
BUSY
LOCK
LOCK
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
BUSY

ICMBAND
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

CHBAND

END
And if the cell is down you will see this:
<rlcrp:cell=pl223a;
CELL RESOURCES
CELL
PL223A
END

BCCH
0

CBCH
0

SDCCH
0

NOOFTCH
0

In order to troubleshoot further, the next piece of information we need is the TG number associated with the site:
RXT

(Print
O TG
M number
:
connected
P
C to the Cell)

The TG number is given in the alarm printouts also.

Then, start troubleshooting from the TRU level downward by getting the status of the MOs. First, find out what TRUs are defined in
the site:
RXCD
(Print Managed Object Configuration)
Among other things, this command will indicate which TRUs are in the site by giving a list of the respective TX, RX, and TS objects.
If any are blocked (whether they be manually blocked, out of service, or automatically blocked), they will show BLOCKED in the
printout as well. For this example though, we are only interested in which TRUs are assigned to the site; in our case the printout
shows TRU #0, 2 and 4 are assigned (3 sectors, 1 TRU per sector). Since B sector is down, look at TRU #2 by getting the status of the
MOs, following the hierarchy top to bottom, TRX to TS:
RXMSP:MO=RXOTRX-46-2&RXOTX-46-2&RXORX-46-2&RXOTS-46-2-0&&-7;
This command will give the Status of the MOs. The Status can be any of the following:
OPER
COM MBL
DEF MBL
NOOP BLO

(Operational)
(Manually Blocked)
(Manually Blocked and out of service (Unloaded))
(Not Operational, Automatically Blocked)

In our example, the resulting printout tells you that the TRX is in state NOOP BLO. In most cases you will need to block it down and
re-load it. When blocking down a TRU, start at the bottom of the hierarchy and work your way up to the TRX:
RXBLI:MO=RXOTS-46-2-0&&-7;
RXBLI:MO=RXORX-46-2&RXOTX-46-2;
RXBLI:MO=RXOTRX-46-2;

(Block the Time Slots)

(Block the RX & TX)
(Block the TRX)

Then unload the TRU in the same manner:

RXESE:MO=RXOTS-46-2-0&&-7;
RXESE:MO=RXORX-46-2&RXOTX-46-2;
RXESE:MO=RXOTRX-46-2;

(Unload the Time Slots)

(Unload the RX & TX)
(Unload the TRX)

Then reload the TRX:

RXESI:MO=RXOTRX-46-2;

(Load the TRX)

Just do the TRX at first to verify that you can communicate with it. If the response comes back LOADING FAILED, it will most
likely have to be reset manually. If the response comes back COM EXECUTED MO NOT LOADABLE FROM THE BSC you
can continue on.
Test the TRX:
RXTEI:MO=RXOTRX-46-2;

(Run diagnostic test on TRX)

If there is a fault in the TRU you will get a fault code in the response to the command. At this point the TRU may need to be replaced,
depending on the fault. If there is no fault, continue loading the TRU:
RXESI:MO=RXOTX-46-2&RXORX-46-2;
RXESI:MO=RXOTS-46-20&&-7;
RXBLE:MO=RXOTRX-46-2;
RXBLE:MO=RXOTX-46-2&RXORX-46-2;
RXBLE:MO=RXOTS-46-20&&-7;

(Load the TX & RX)

(Load the Time Slots)
(Deblock the TRX)
(Deblock the TX & RX)
(Deblock the Time Slots)

Note the order of loading and deblocking is opposite that blocking and unloading. Always block and unload from the bottom up, load
and deblock from the top down.
At this point you should be operational. Verify by re-issuing the command:
RLCRP:CELL=PL223A&PL223B&PL223C;
(print cell resources)

Troubleshooting example #2 Entire site down

When the entire site is down you will have to look at the MOs above the TRU level, and at the Dip (DIgital Path). Since the Dip is the
connection to the BSC, get its status first of all.
Usually the Dip has the same number as the TG, but sometimes if the site is microwaved or goes through Newbridge, it will be
different. To verify use the RXAPP command on the TG:
RXAPP:MO=RXOTG-46;

(Print device connection to the TG)

The printout looks like this:

RADIO X-CEIVER ADMINISTRATION
ABIS PATH STATUS
MO
RXOTG-46
DEV
RBLT24-1104
RBLT24-1105
RBLT24-1106

DCP
1
2
3

RBLT24-1107

RBLT24-1108

RBLT24-1109

RBLT24-1110

RBLT24-1111

RBLT24-1112
RBLT24-1113
RBLT24-1114
RBLT24-1115
RBLT24-1116
RBLT24-1117
RBLT24-1118
RBLT24-1119
RBLT24-1120
RBLT24-1121

9
10
11
12
13
14
15
16
17
18

APUSAGE
UNCONC
UNCONC
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX16
MPLEX32
UNDEF
UNDEF
UNDEF
UNDEF
UNDEF
UNDEF
UNDEF
UNDEF
UNDEF
UNCONC

APSTATE
TRXC SIGNALLING
TRXC SIGNALLING
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
SPEECH/DATA
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
CF AND TRXC SIGNALLING

TEI
2
0

62

END

This will give a list of the RBLT24 devices connected to the TG. This is how the RBLT/TG connection is actually made; on a device
level rather than a Dip level. There are 24 devices per Dip, numbered consecutively. Here you can see the device range of 11041121. To find the Dip, take the 1st device and divide by 24, the Dip number is 46, same as the TG. NOTE: The DIP and TG vaues are
usually the same, but not always. If there are Microwave hops or Newbridge involved, they may not be the same. To get the status of
the Dip, type the following command:
DTSTP:DIP=46RBLT;

(Status the DIP)

The Status should be WO. If it is ABL, there is probably a problem with the T1 and a ticket would be issued with Pac Bell. (For a list
of fault codes associated with the Dip, see the list at the end.) If the Dip is in state WO, check the devices:
STDEP:DEV=RBLT24-1104&&-1121;

(Check devices)

All the devices should be either SEBU (Sealed Busy, used for LAPD connections to the BTS), BUSY (carrying traffic), or IDLE
(Working, not carrying traffic). If they are in state MBL you will not be able to load the BTS even if the Dip is working. To deblock
the devices type the following command:

(Deblock devices)

BLODE:DEV=RBLT24-1104&&-1121;

Then type the STDEP command again, they should now be IDLE. If this didnt bring the site back, start looking at MOs:
RXMSP:MO=RXOCF-46&RXOTF-46&RXOIS-46;

(Check status of CF, TF & IS)

If all these show OPER then start looking at the TRUs as before. It may be that something got left blocked down, or is not
operational.
If any of the MOs show NOOP BLO then first try to restore them by a simple Block/Deblock RXBLI/RXESE sequence. If that fails
you will have to unload the site up to the CF, but in order to unload the CF you will have to first block and unload all of its
subordinate MOs. If not, when trying to unload the CF you will get a response SUBORDINATE MO NOT IN VALID STATE.
After unloading the CF attempt to reload it. If it comes back Loading Failed it may need to be reset manually.

Troubleshooting example #3 MOs Operational, Sector still down

In situations where all the MOs in a sector are operational and the sector is still down, there may be problems in the definition of the
MOs. The TRX, TX and RX have to be defined correctly for the TRU to be operational. They have the following properties:
TRX
TEI value, same as the TRX #
DCP1 value, Digital Connection Point 1
DCP2 value, Digital Connection Point 2
CELL, sector designation
TX
BAND, Operating band, must be GSM1900
ANT, Antenna designation
MPWR, Maximum Power
CELL, sector designation
RX
BAND, Operating band, must be GSM1900
RXD, Diversity. AB for normal diversity, A for Antenna A only, B for Antenna B only
ANTA, Antenna A
ANTB, Antenna B
If all the MOs are operational and the TRU is not carrying traffic, there is probably a mismatch in the definitions. For example if a
TRU is in B sector but the TX is connected to A sector, the TX will not enable. To print the MO definitions, use the following
command:
RXMOP:MO=RXOTRX-46-2&RXOTX-46-2&RXORX-46-2;
This will print a list of definitions in the order of the command, TRX, TX and RX. Look for Cell or Antenna assignments that are out
of place. For example, if the Cell designation wasnt made on a TX, the printout would look like this:
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT DATA
MO
RXOTRX-46-2

CELL
PL223B

CHGR
ALL

SWVERREPL
DEFAULT

TEI
2

SIG
UNCONC

SWVERACT
B0531R0405

MO
RXOTX-46-2

CELL
ALL

CHGR
ALL

BAND
GSM1900

MO

RXD

BAND

ANTA

DCP1
134
DCP2
135
136

ANT
ALPHAB
ANTB

MPWR
45

RXORX-46-2

AB

GSM1900

ALPHAB

BETAB

END

You would need to correct this before the TRU will go operational. To change a parameter on a MO you must first block and unload
the MO so that it is in state DEF. Then enter the following command:
RXMOC:MO=RXOTX-46-2,CELL=PL223B;
Then load and deblock the TX as usual and it should come up OPER and you will show resources after a few seconds.

COMMAND LIST
The following is a summary of commands used in these procedures:
ALLIP;
RXMSP:MO=RXOCF-XX;
RXOTF-XX;
RXOIS-XX;
RXOTRX-XX-X;
RXOTX-XX-X;
RXORX-XX-X;
RXOTS-XX-X-0&-7;

-Print Alarm list

-Print status of:
Control Function
Timing Function
Interconnect Switch
Transceiver Controller
Transmitter
Receiver
Time Slots

RXMFP:MO=RXOXX;
RXELP:MO=RXOXX;
RLCRP:CELL=PLXXXA;
RXTCP:MOTY=RXOTG,CELL=PLXXXA;
RXTCP:MO=RXOTG-XX;
RXCDP:MO=RXOTG-XX;
RXBLI:MO=RXOXX;
RXBLE:MO=RXOXX;
RXESI:MO=RXOXX;
RXESE:MO=RXOXX;
RXTEI:MO=RXOXX;
RXAPP:MO=RXOTG-X;
DTSTP:DIP=XXRBLT;
STDEP:DEV=RBLT24-XX&&-YY;
BLODI:DEV=RBLT24-XX&&-YY;
BLODE:DEV=RBLT24-XX&&-YY;
RXMOP:MO=RXOXXX;
RXMOC:MO=RXOXX,(parameter)=(x);

-Print faults on MO
-Print Error log of MO
-Print Cell Resources
-Print TG connected to Cell
-Print Cells connected to TG
-Print MO configuration
-Block an MO
-Deblock an MO
-Load an MO
-Unload an MO
-Test an MO
-Print RBLT24 devices conn. to TG
-Status DIP
-Print status of device range
-Block devices
-Deblock devices
-Print MO definition
-Change MO definition

The following commands are not covered here but may be useful:
DTQUP:DIP=XXRBLT;
RXMDP:MO=RXOCF-XX;
RXOTRX-XX-Y;
RXOTS-XX-YY-Z;
RLCFP:CELL=PLXXXA;
RLDEP:CELL=PLXXXA;
RLSTP:CELL=PLXXXA;
RLSTC:CELL=PLXXXA,STATE=HALTED;
RLSTC:CELL=PLXXXA,STATE=ACTIVE;
RLNRP:CELL=PLXXXA,CELLR=ALL;

-Print DIP hits

-Print devices connected to CF

TRX

TS
-Print channel numbers for Cell
-Print Cell definition
-Print Cell status
-To halt a sector
-To activate a sector
-Print neighbors to the cell

FAULT CODE LIST

^^^^^^ SO CF INTERNAL FAULT MAP CLASS 1A ^^^^^^^^^^
Fault No
Fault Type
CF-1A 0
CF-1A 1
Reset, Power on
CF-1A 2
Reset, Switch
CF-1A 3
Reset, Watchdog
CF-1A 4
Reset, SW fault
CF-1A 5
Reset, RAM fault
CF-1A 6
Reset, Internal function change
CF-1A 7
XBUS related fault
CF-1A 8
Timing unit VCO (Oscillator) fault
CF-1A 9
Timing bus related fault
CF-1A 10
Indoor temp out of safe range
CF-1A 11
CF-1A 12
DC voltage out of range
CF-1A 13
CF-1A 14
Local bus related fault
CF-1A 15
RBS database corrupted
CF-1A 16
RU database corrupted
CF-1A 17
HW and IDB inconsistent
CF-1A 18
Internal configuration failed
CF-1A 19
Indoor temperature above safe range
CF-1A 20
Indorr temperature below safe range
47
^^^^^^ SO CF INTERNAL FAULT MAP CLASS 2A ^^^^^^^^^^^^^^^
Fault No
Fault Type
CF-2A 0
CF-2A 1
Reset, Power on
CF-2A 2
Reset, Switch
CF-2A 3
Reset, Watchdog
CF-2A 4
Reset, SW Fault
CF-2A 5
Reset, RAM Fault
CF-2A 6
Reset, Internal function change
CF-2A 7
RXDA Amplifier Current Fault
CF-2A 8
VSWR Limits Exceeded
CF-2A 9
Power Limits Exceeded
CF-2A 10
DXU-Opt EEPROM checksum fault
CF-2A 11
CF-2A 12
RX Maxgain/Mingain Violated
CF-2A 13
Timing Unit VCO Ageing
CF-2A 14
CDU Supervision/Communication Lost
CF-2A 15
VSWR/Output Power Supervision Lost
CF-2A 16
Indoor Temp Out Of Normal Conditional Range
CF-2A 17
Indoor Humidity
CF-2A 18
DC Voltage Out Of Range
CF-2A 19
Power System in Standalone Mode
CF-2A 20
CF-2A 21
Internal Power Capacity Reduced
CF-2A 22
Battery Backup Capacity Reduced
CF-2A 23
Climate Capacity Reduced
CF-2A 24
HW Fault
CF-2A 25
Loadfile Missing in DXU or ECU
CF-2A 26
Climate Sensor Fault
CF-2A 27
System Voltage Sensor Fault
CF-2A 28
A/D Converter Fault
CF-2A 29
Varistor Fault
CF-2A 30
Bus Fault
CF-2A 31
High Frequency Software Fault

CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A
CF-2A

32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

Non-Volatile Memory Corrupted

RX Diversity Lost
Output Voltage Fault
Optional Synchronization Source
RU Data Base Corrupted
Circuit Breaker Tripped
Default Values Used
RX Cable Disconnected
Reset, DXU Link Lost
Lost communication to TRU
Lost communication to ECU
Internal Configuration Failed
ESB Distribution Failure
DB parameter fault

^^^^^ SO CF EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^

Fault No
Fault Type
EXT CF-1B 4 L/R SWI (BTS in local mode)
EXT CF-1B 5 L/R TI (Local to remote while link lost)
EXT CF-1B 7 Synch Info Lost (Valid for IP transmission)
^^^^^ SO CF EXTERNAL CONDITION MAP CLASS 2 ^^^^^^^^
Fault No
Fault Type
EXT CF-2B 7 Synch Info Lost (Valid for IP transmission)
EXT CF-2B 9 RBS DOOR (RBS cabinet door open)
EXT CF-2B 10 MAINS FAIL (External power source fail)
EXT CF-2B 11 ALNA/TMA Fault
EXT CF-2B 12 ALNA/TMA Degraded
EXT CF-2B 13 Auxiliary Equipment Fault
^^^^^^^^ SO CF, REPLACEMENT UNIT MAP ^^^^^^^^^^^^^^^
No.
Replacement Unit
CF RU 0
DXU
CF RU 1
ECU
CF RU 2
MICRO RBS or SIR CABINET
CF RU 3
Y LINK
CF RU 4
CF RU 5
CDU
CF RU 6
CF RU 7
PSU
CF RU 8
CF RU 9
BDM or BFU
CF RU 10
ACCU
CF RU 11
Active Cooler
CF RU 12
ALNA/TMA A
CF RU 13
ALNA/TMA B
CF RU 14
BATTERY
CF RU 15
FAN
CF RU 16
HEATER
CF RU 17
HEATER EXCHANGER EXT FAN
CF RU 18
HEATER EXCHANGER INT FAN
CF RU 19
HUMIDITY SENSOR
CF RU 20
TMA CM
CF RU 21
TEMPERATURE SENSOR
CF RU 22
CDU HLOUT HLIN CABLE
CF RU 23
CDU RX IN CABLE
CF RU 24
CU or TCU
CF RU 25
DU or FDU
CF RU 26
FU
CF RU 27
FU CU PFWD CABLE or FDU TCU PFWD CABLE
CF RU 28
FU CU PREFL CABLE or FDU TCU PREFL CABLE

CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF
CF

RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU
RU

29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

CAB HLIN CABLE

CDU BUS
ENVIRONMENT
LOCAL BUS
POWER COMMUNICATION LOOP
RBS DB
EOM BUS
TIMING BUS
FDU CXU RXA CABLE
FDU CXU RXB CABLE
XBUS
ANTENNA
PSU DC CABLE
CXU DC CABLE
FLASH CARD
PTU
BATTERY TEMP SENSOR
FCU

^^^^^ SO TRXC INTERNAL FAULT MAP CLASS 1A ^^^^^^^^^^

Fault No
Fault Type
TRX-1A 0
TRX-1A 1
Reset, Power on
TRX-1A 2
Reset, Switch
TRX-1A 3
Reset, Watchdog
TRX-1A 4
Reset, SW fault
TRX-1A 5
Reset, RAM fault
TRX-1A 6
Reset, Internal function change
TRX-1A 7
Radio Baseband Loop Test Fault
TRX-1A 8
Timing Reception Fault
TRX-1A 9
Signal Processing Fault
TRX-1A 10
Tora Dannie Communication Fault
TRX-1A 11
DSP CPU Communication Fault
TRX-1A 12
Terrestrial Traffic Channel Fault
TRX-1A 13
RF Loop Test Fault
TRX-1A 14
RU Data Base Corrupted
TRX-1A 15
XBus Communication Fault
TRX-1A 16
Initiation Fault
TRX-1A 17
X-Interface Fault
TRX-1A 18
DSP Fault
TRX-1A 19
Reset, DXU Link Lost
TRX-1A 20
HW And IDB Inconsistent
TRX-1A 21
Internal Configuration Failed
TRX-1A 22
Voltage Supply Fault
TRX-1A-47
^^^^^ SO TRXC INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^
Fault No
Fault Type
TRX-1B 0
CDU Not Usable
TRX-1B 1
Indoor Temp Out Of Safe Range
TRX-1B 2
TRX-1B 3
DC Voltage Out Of Range
TRX-1B 4
Indoor Temp Above Safe Range
TRX-1B 5
Indoor Temp Above Safe Range
47
^^^^^ SO TRXC INTERNAL FAULT MAP CLASS 2A ^^^^^

Fault No
TRX-2A 0
TRX-2A 1
TRX-2A 2
TRX-2A 3
TRX-2A 4
TRX-2A 5
TRX-2A 6
TRX-2A 7
TRX-2A 8
TRX-2A 9
TRX-2A 10
TRX-2A 11
TRX-2A 12
TRX-2A 13
TRX-2A 14
TRX-2A 15
TRX-2A 16
TRX-2A 17
TRX-2A 18
TRX-2A 19
TRX-2A 20
TRX-2A 21
TRX-2A 22
TRX-2A 23
TRX-2A 24
TRX-2A 25
TRX-2A 26
TRX-2A 27

Fault Type
RX cable disconnected
RX EEPROM checksum fault
RX Config table checksum fault
RX Synthesizer unlocked
RX Internal voltage fault
Astra Dixie communication fault
Astra Tracy communication fault
TX EEPROM checksum fault
TX Config table checksum fault
TX Synthesizer unlocked
TX Internal voltage fault
TX High temperature
TX Output power limits exceeded
TX Saturation
Voltage supply fault
VSWR/Output Power Supervision Lost
Non volatile memory corrupted
Loadfile Missing in TRU
DSP Fault
High frequency software fault
RX initiation fault
TX initiation fault
CDU-bus communication fault
Default values used
TX Max Power Restricted
DB parameter fault
RX Path Fault

^^^^^^^ SO TRXC EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^^^^^^

Fault No
Fault Type
EXT TRX-1B 4 L/R SWI (TRU In Local Mode)
EXT TRX-1B 5 L/R TI (Local to Remote while Link Lost)
^^^^^^
NO.
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU
TRX RU

SO TRXC, REPLACEMENT UNIT MAP ^^^^^^^^^^^^^^^

RU
0
TRU or dTRU
1
2
MICRO RBS or SIR CABINET
3
CXU dTRU RXA CABLE
4
CXU dTRU RXB CABLE
5
CDU CXU RXA CABLE
6
CDU CXU RXB CABLE
7
8
9
10
CDU TO TRU PFWD CABLE
11
CDU TO TRU PREFL CABLE
12
CDU TO TRU RXA CABLE
13
CDU TO TRU RXB CABLE
47

^^^^^^ AO TS EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^^^

Fault No
Fault Type
EXT TS-1B 3 TRA/PCU (Remote Transcoder/PCU Com. Lost)
^^^^^^ AO TF INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^^^^^
Fault No
Fault Type
TF-1B 0
Optional synchronization source
TF-1B 1
DXU-opt. EEPROM checksum fault

^^^^^^ AO TF EXTERNAL CONDITION MAP CLASS 1 ^^^^^^^^^^^^^

Fault No
Fault Type
EXT TF-1B 0 EXT SYNCH (No Usable External Reference)
EXT TF-1B 1 PCM SYNCH (No Usable PCM-Reference)
^^^^^ AO TF EXTERNAL CONDITION MAP CLASS 2 ^^^^^^^^^
Fault No
Fault Type
EXT TF-2B 0 EXT SYNCH (No Usable External Reference)
EXT TF-2B 1 PCM sync (no usable PCM-reference)
^^^^^ AO TX INTERNAL FAULT MAP CLASS 1A
Fault No
TX-1A 0

^^^^^^^^^^

Fault Type
TX offending

^^^^^
Fault
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B
TX-1B

AO TX INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^^^^

No
Fault Type
0
Not Usable
1
CDU VSWR Limits Exceeded
2
CDU Output Power Limits Exceeded
3
4
TX Antenna VSWR Limits Exceeded
5
6
TX EEPROM checksum fault
7
TX Config table checksum fault
8
TX Synthesizer A/B unlocked
9
TX Synthesizer C unlocked
10
Astra Tracy communication fault
11
TX Internal voltage fault
12
TX High temperature
13
TX Output power limits exceeded
14
TX Saturation
15
16
17
TX Initiation fault
18
HW Fault
19
SW Load/Start Fault
20
Input Power Fault
21
Park Fault
22
VSWR/Output Power Supervision Lost
23
Reset, Power On
24
Reset, Communication Fault
25
CU reset, watchdog
26
CU fine tuning fault
27
TX Max Power Restricted
28
TCU High Temperature
TX-1B 47
TX Auxiliary Equipment Fault
^^^^^ AO TX INTERNAL FAULT MAP CLASS 2A ^^^^^
Fault No
Fault Type
TX-2A 0
TX diversity fault
^^^^^
Fault
RX-1B
RX-1B
RX-1B
RX-1B
RX-1B
RX-1B

AO RX INTERNAL FAULT MAP CLASS 1B ^^^^^^^^^^^^^^^^^^

No
Fault Type
0
RXDA Amplifier current fault
1
ALNA/TMA fault
2
3
RX EEPROM checksum fault
4
RX Config table checksum fault
5
RX Synthesizer A/B unlocked

RX-1B
RX-1B
RX-1B
RX-1B
RX-1B
RX-1B
RX-1B
RX-1B

6
7
8
9
10
11
12
13
RX-1B 47

RX Synthesizer C unlocked
Astra Dixie communication fault
RX Internal voltage fault
RX cable disconnected
RX Initiation fault
CDU Output voltage fault
TMA CM Output Voltage Fault
RX Path Fault
RX Auxiliary Equipment Fault

^^^^^^^^^^^^^^^ TERMINOLOGY ^^^^^^^^^^^^^^^^^^^^

Fault No
The fault number is equal to the bit position in the
fault map reported over the Abis interface.
INTERNAL FAULT MAP CLASS 1A
Affect MO functionality.
Faulty HW is part of the signaling MO.
INTERNAL FAULT MAP CLASS 1B
Affect MO functionality.
Origin of the fault is external to the signaling MO.
INTERNAL FAULT MAP CLASS 2A
Not affect MO functionality.
Faulty HW is part of the signaling MO.
EXTERNAL CONDITION MAP CLASS 1
Affect MO functionality. The conditions are TG external.
EXTERNAL CONDITION MAP CLASS 2
Not affect MO functionality. The conditions are TG external.
REPLACEMENT UNIT MAP (RU MAP)
Suspected HW causing the faults in internal fault maps.
MO
Mangaged Object, the class of all object in the BTS O&M
model which BSC can communicate with.
SO
Service Object, an abstract subclass of MO which handles
HW. A SO manages one or more RUs.
AO
Application Object, an abstract subclass of MO which only
handles functionality.
RU
Replaceable Unit, Smallest unit in a RBS2000 cabinet
which can be replaced.
^^^^^ LOGICAL RU ^^^^^
A unit which can be refered to but is not a single
pysical unit. There are tree different kinds of logical RUs:
1. BUSSES
-XBUS
-LOCAL BUS
-TIMING BUS
-CDU BUS

2.

3.

-POWER COMMUNICATION LOOP

ANTENNAS
-RX A
-RX B
-TX A
-TX B
ENVIRONMENT
-TEMPERATURE

^^^^^^ BITMAP
000000000001
000000000002
000000000004
000000000008
000000000010
000000000020
000000000040
000000000080
000000000100
000000000200
000000000400
000000000800
000000001000
000000002000
000000004000
000000008000
000000010000
000000020000
000000040000
000000080000
000000100000
000000200000
000000400000
000000800000
000001000000
000002000000
000004000000
000008000000
000010000000
000020000000
000040000000
000080000000
000100000000
000200000000
000400000000
000800000000
001000000000
002000000000
004000000000
008000000000
010000000000
020000000000
040000000000
080000000000
100000000000
200000000000
400000000000
800000000000

FOR RXELP:MO=; ^^^^^^^^^^^^^^^^^^

0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

^^^^^^^^^^^^^^^^ DIGITAL PATH FAULTS ^^^^^^^^^^^^^^^

DIP fault 1
Alarm indication signal AIS
DIP fault 2
Loss of frame alignment
DIP fault 3
Excessive error rate

DIP
DIP
DIP
DIP
DIP
DIP
DIP

fault
fault
fault
fault
fault
fault
fault

4
5
6
7
8
9
10

Alarm indication from the remote end

Alarm indication signal in time slot 16
Loss of multiframe alignment
Alarm ind. from remote end signalling equipment
Alarm indication signal ALL1
Loss of CRC multiframe alignment
Consectutive severely errrored seconds

^^^^^^^^^^^ RADIO X-CEIVER ADMINISTRATION ^^^^^^^^^^^^

MANAGED OBJECT STATUS
BTS: Last known state of the MO in the BTS
RES= MO is in state RESET
STA=
STARTED
DIS=
DISABLED
ENA=
ENABLED
BITMAP for BLO (Blocking origin of automatic blocking)
HEX
BIT
xxx1
0 AP object blocked from own superv. perm.
xxx2
1 AT object blocked from own superv.
temp.
xxx4
2 AS object blocked due to fault suspected
xxx8
3 TG object blocked from TG
xx10
4 TRXC
object blocked from TRXC
xx20
5 TGC
object blocked from TGC
xx40
6 OML
object blocked from OML
xx80
7 X spare
x100
8 LMT
obj. blo. due to local maint. activities
x200
9 CF object blocked from CF
x400 10 LOM
object blocked from due to local mode
x800 11 LOOP
obj. blo. from due to loop test failure
BITMAP for BLA (Blocking origin of blocking due to action not completed)
HEX
BIT
xxx1
0 BNU obj. needs reset & uncond. load or reset & load. in progr.
xxx2
1 BNR obj. needs reset & load check or reset & load. in progr.
xxx4
2 BNL
obj. needs reset and load check or loading in progress
xxx8
3 BNP
obj. needs polling or polling in progress
xx10
4 BNT
obj. needs testing or testing in progress
xx20
5 BNI
obj. needs intermittent test or interm. test in progr.
xx40
6 BND
obj. needs updating of MO data
xx80
7 BNS
obj. needs to be started
x100
8 BNM
obj. needs to be manually deblocked (BTS initiated)
x200
9 BNO
obj. needs loop test or loop loop test in progress
BITMAP for LMO (Blocking origin of logical managed object TS)
HEX
BIT
xx20
5 CRN
LTS blocked due to creation in progress
xx40
6 ENA
LTS blocked due to not enabled
xx80
7 X
x100
8 MO
LTS blocked from TS
x200
9 LTF
LTS blocked from LTF
x400 10 RSL
RSL blocked from RSL
x800 11 DEV
LTS blocked from speech/data device
1000 12 X
2000 13 SYNCB
LTS blo. due to sync. fault in BTS
4000 14 X
8000 15 CHG
blocked due to change
BITMAP for LMO (Blocking origin of logical managed object TF)
HEX
BIT
xx20
5 CRN
LTF blocked due to creation in progress
xx40
6 ENA
LTF blocked due to not enabled
xx80
7 X

x100

MO

LTF blocked from TF

DIGITAL PATH (DIP) FAULT CODE LIST

~~~Numeric vaues~~~
1
2
3
4
5
6
7
8
9
10

Alarm indication signal, AIS

Loss of frame alignment
Excessive error rate
Remote defect indication (Alarm indication from remote end in some AI2 documents)
Alarm indication signal in time slot 16
Loss of multiframe alignment
Alarm indication from the remote end signalling equipment
Alarm indication signal, ALL1
Loss of incoming signal
Consecutive severely errored seconds

~~~Abbreviations~~~
AIS
LOF
ERATE
RDI
AISM
LOMF
REFM
ALL1
LOS
CSES

Alarm indication signal

Loss of frame alignment
Excessive error rate
Remote defect indication (REFF in some AI2 documents)
Alarm indication signal in time slot 16
Loss of multiframe alignment
Alarm indication from the remote end signalling equipment
Alarm indication signal
Loss of incoming signal
Consecutive severely errored seconds

Some common Dip faults you will see:

4, RDI Remote Defect Indicator (Yellow Alarm), problem at the remote end, either NIU or CSU
2&8, LOF&ALL1, Loss of Framing, All 1s alarm, the T1 is down due to a failure in the span
2&9, LOF&LOS, Loss of Framing, Loss of Incoming signal, the circuit is either not patched in the BSC or theres a T-Berd in the
DSX

TRU/TEI

DCP1

DCP2

0
1
2
3
4
5
6
7
8
9
10
11

128
131
134
137
140
143
160
163
166
169
172
175

129&130
132&133
135&136
138&139
141&142
144&145
161&162
164&165
167&168
170&171
173&174
176&177