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 TRU

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

BTS Hierarchy
Managed Objects Definition Physical representation
RXOTG-XX Transceiver Group Entire RBS/DIP (usually)
RXOCF-XX Control Function DXU
RXOTF-XX Timing Function Oscillator within the DXU
RXOIS-XX Interconnect Switch Switch in the DXU
RXOTRX-XX-Y Transceiver Controller TRU
RXOTX-XX-Y Transmitter Transmitter within the TRU
RXORX-XX-Y Receiver Receiver within the TRU
RXOTS-XX-Y-0&&-7 Time Slots 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 TRU’s 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
3LLLEC: (print cell resources)
2P
=
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 don’t. 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 you’re 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 0603

RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT

MO RSITE ALARM SLOGAN

RXOCF-46 PL223 BTS INTERNAL

A2/APT "PLT12C0 C000G00" 551 010302 0603

RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT

MO RSITE ALARM SLOGAN

RXOTRX-46-2 PL223 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 0603

RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT

MO RSITE ALARM SLOGAN

RXOCF-46 PL223 OML FAULT

A1/APT "PLT12C0 C000G00" 548 010302 0603

DIGITAL PATH FAULT SUPERVISION

DIP DIPEND FAULT SECTION HG DATE TIME

46RBLT ALL1 010314 152955

A2/APT "PLT12C0 C000G00" 549 010302 0603

DIGITAL PATH UNAVAILABLE STATE FAULT

DIP UAS UASR UASB SECTION BLOCKING DATE TIME

46RBLT - 010302 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 BCCH CBCH SDCCH NOOFTCH

PL223A 1 0 4 7- 14

BPC CHANNEL CHRATE SPV STATE ICMBAND CHBAND

6824 TCH-7343 FR 1,2 IDLE 1
TCH-24273 HR 1 IDLE 1
TCH-24272 HR 1 IDLE 1
6830 TCH-7349 FR 1,2 IDLE 1
TCH-24285 HR 1 IDLE 1
TCH-24284 HR 1 IDLE 1
6828 TCH-7347 FR 1,2 IDLE 1
TCH-24281 HR 1 IDLE 1
TCH-24280 HR 1 IDLE 1
6833 TCH-7352 FR 1,2 BUSY 1
TCH-24291 HR 1 LOCK 1
TCH-24290 HR 1 LOCK 1
6905 TCH-7421 FR 1,2 IDLE 1
TCH-24429 HR 1 IDLE 1
TCH-24428 HR 1 IDLE 1
6865 TCH-7384 FR 1,2 IDLE 1
TCH-24355 HR 1 IDLE 1
TCH-24354 HR 1 IDLE 1
7158 TCH-7660 FR 1,2 IDLE 1
TCH-8587 HR 1 IDLE 1
TCH-8586 HR 1 IDLE 1
8086 SDCCH-34067 IDLE 1
SDCCH-34066 IDLE 1
SDCCH-34065 IDLE 1
SDCCH-34064 IDLE 1
BCCH-34818 BUSY
END

And if the cell is down you will see this:

<rlcrp:cell=pl223a;

CELL RESOURCES

CELL BCCH CBCH SDCCH NOOFTCH

PL223A 0 0 0 0
END

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 (Operational)
COM MBL (Manually Blocked)
DEF MBL (Manually Blocked and out of service (Unloaded))
NOOP BLO (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; (Block the Time Slots)

RXBLI:MO=RXORX-46-2&RXOTX-46-2; (Block the RX & TX)
RXBLI:MO=RXOTRX-46-2; (Block the TRX)

Then unload the TRU in the same manner:

RXESE:MO=RXOTS-46-2-0&&-7; (Unload the Time Slots)

RXESE:MO=RXORX-46-2&RXOTX-46-2; (Unload the RX & TX)
RXESE:MO=RXOTRX-46-2; (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; (Load the TX & RX)

RXESI:MO=RXOTS-46-20&&-7; (Load the Time Slots)
RXBLE:MO=RXOTRX-46-2; (Deblock the TRX)
RXBLE:MO=RXOTX-46-2&RXORX-46-2; (Deblock the TX & RX)
RXBLE:MO=RXOTS-46-20&&-7; (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:

(print cell resources)

RLCRP:CELL=PL223A&PL223B&PL223C;
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 DCP APUSAGE APSTATE TEI

RBLT24-1104 1 UNCONC TRXC SIGNALLING 2
RBLT24-1105 2 UNCONC TRXC SIGNALLING 0
RBLT24-1106 3 MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
RBLT24-1107 4 MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
RBLT24-1108 5 MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
RBLT24-1109 6 MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
RBLT24-1110 7 MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
MPLEX16 SPEECH/DATA
RBLT24-1111 8 MPLEX16 SPEECH/DATA
MPLEX16 IDLE
MPLEX32 IDLE
RBLT24-1112 9 UNDEF IDLE
RBLT24-1113 10 UNDEF IDLE
RBLT24-1114 11 UNDEF IDLE
RBLT24-1115 12 UNDEF IDLE
RBLT24-1116 13 UNDEF IDLE
RBLT24-1117 14 UNDEF IDLE
RBLT24-1118 15 UNDEF IDLE
RBLT24-1119 16 UNDEF IDLE
RBLT24-1120 17 UNDEF IDLE
RBLT24-1121 18 UNCONC CF AND TRXC SIGNALLING 62 4

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 1104-
1121. 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:
 BLODE:DEV=RBLT24-1104&&-1121; (Deblock devices)

Then type the STDEP command again, they should now be IDLE. If this didn’t 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 wasn’t made on a TX, the printout would look like this:

RADIO X-CEIVER ADMINISTRATION

MANAGED OBJECT DATA

MO CELL CHGR TEI SIG DCP1

RXOTRX-46-2 PL223B ALL 2 UNCONC 134

SWVERREPL SWVERACT DCP2

DEFAULT B0531R0405 135
136

MO CELL CHGR BAND ANT MPWR

RXOTX-46-2 ALL ALL GSM1900 ALPHAB 45

MO RXD BAND ANTA ANTB

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; -Print Alarm list

-Print status of:
RXMSP:MO=RXOCF-XX; Control Function
RXOTF-XX; Timing Function
RXOIS-XX; Interconnect Switch
RXOTRX-XX-X; Transceiver Controller
RXOTX-XX-X; Transmitter
RXORX-XX-X; Receiver
RXOTS-XX-X-0&-7; Time Slots

RXMFP:MO=RXOXX; -Print faults on MO

RXELP:MO=RXOXX; -Print Error log of MO
RLCRP:CELL=PLXXXA; -Print Cell Resources
RXTCP:MOTY=RXOTG,CELL=PLXXXA; -Print TG connected to Cell
RXTCP:MO=RXOTG-XX; -Print Cells connected to TG
RXCDP:MO=RXOTG-XX; -Print MO configuration
RXBLI:MO=RXOXX; -Block an MO
RXBLE:MO=RXOXX; -Deblock an MO
RXESI:MO=RXOXX; -Load an MO
RXESE:MO=RXOXX; -Unload an MO
RXTEI:MO=RXOXX; -Test an MO
RXAPP:MO=RXOTG-X; -Print RBLT24 devices conn. to TG
DTSTP:DIP=XXRBLT; -Status DIP
STDEP:DEV=RBLT24-XX&&-YY; -Print status of device range
BLODI:DEV=RBLT24-XX&&-YY; -Block devices
BLODE:DEV=RBLT24-XX&&-YY; -Deblock devices
RXMOP:MO=RXOXXX; -Print MO definition
RXMOC:MO=RXOXX,(parameter)=(x); -Change MO definition

The following commands are not covered here but may be useful:

DTQUP:DIP=XXRBLT; -Print DIP hits

RXMDP:MO=RXOCF-XX; -Print devices connected to CF
RXOTRX-XX-Y; “ “ “ TRX
RXOTS-XX-YY-Z; “ “ “ TS
RLCFP:CELL=PLXXXA; -Print channel numbers for Cell
RLDEP:CELL=PLXXXA; -Print Cell definition
RLSTP:CELL=PLXXXA; -Print Cell status
RLSTC:CELL=PLXXXA,STATE=HALTED; -To halt a sector
RLSTC:CELL=PLXXXA,STATE=ACTIVE; -To activate a sector
RLNRP:CELL=PLXXXA,CELLR=ALL; -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 32 Non-Volatile Memory Corrupted
CF-2A 33 RX Diversity Lost
CF-2A 34 Output Voltage Fault
CF-2A 35 Optional Synchronization Source
CF-2A 36 RU Data Base Corrupted
CF-2A 37 Circuit Breaker Tripped
CF-2A 38 Default Values Used
CF-2A 39 RX Cable Disconnected
CF-2A 40 Reset, DXU Link Lost
CF-2A 41 Lost communication to TRU
CF-2A 42 Lost communication to ECU
CF-2A 43 Internal Configuration Failed
CF-2A 44 ESB Distribution Failure
CF-2A 45
CF-2A 46 DB parameter fault
CF-2A 47

^^^^^ 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 RU 29 CAB HLIN CABLE
CF RU 30 CDU BUS
CF RU 31 ENVIRONMENT
CF RU 32 LOCAL BUS
CF RU 33 POWER COMMUNICATION LOOP
CF RU 34 RBS DB
CF RU 35 EOM BUS
CF RU 36 TIMING BUS
CF RU 37 FDU CXU RXA CABLE
CF RU 38 FDU CXU RXB CABLE
CF RU 39 XBUS
CF RU 40 ANTENNA
CF RU 41 PSU DC CABLE
CF RU 42 CXU DC CABLE
CF RU 43 FLASH CARD
CF RU 44 PTU
CF RU 45 BATTERY TEMP SENSOR
CF RU 46 FCU
CF RU 47

^^^^^ 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 Fault Type
TRX-2A 0 RX cable disconnected
TRX-2A 1 RX EEPROM checksum fault
TRX-2A 2 RX Config table checksum fault
TRX-2A 3 RX Synthesizer unlocked
TRX-2A 4 RX Internal voltage fault
TRX-2A 5 Astra Dixie communication fault
TRX-2A 6 Astra Tracy communication fault
TRX-2A 7 TX EEPROM checksum fault
TRX-2A 8 TX Config table checksum fault
TRX-2A 9 TX Synthesizer unlocked
TRX-2A 10 TX Internal voltage fault
TRX-2A 11 TX High temperature
TRX-2A 12 TX Output power limits exceeded
TRX-2A 13 TX Saturation
TRX-2A 14 Voltage supply fault
TRX-2A 15 VSWR/Output Power Supervision Lost
TRX-2A 16 Non volatile memory corrupted
TRX-2A 17 Loadfile Missing in TRU
TRX-2A 18 DSP Fault
TRX-2A 19 High frequency software fault
TRX-2A 20 RX initiation fault
TRX-2A 21 TX initiation fault
TRX-2A 22 CDU-bus communication fault
TRX-2A 23 Default values used
TRX-2A 24
TRX-2A 25 TX Max Power Restricted
TRX-2A 26 DB parameter fault
TRX-2A 27 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)

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

NO. RU
TRX RU 0 TRU or dTRU
TRX RU 1
TRX RU 2 MICRO RBS or SIR CABINET
TRX RU 3 CXU dTRU RXA CABLE
TRX RU 4 CXU dTRU RXB CABLE
TRX RU 5 CDU CXU RXA CABLE
TRX RU 6 CDU CXU RXB CABLE
TRX RU 7
TRX RU 8
TRX RU 9
TRX RU 10 CDU TO TRU PFWD CABLE
TRX RU 11 CDU TO TRU PREFL CABLE
TRX RU 12 CDU TO TRU RXA CABLE
TRX RU 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 Fault Type

TX-1A 0 TX offending

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

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

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

Fault No Fault Type
RX-1B 0 RXDA Amplifier current fault
RX-1B 1 ALNA/TMA fault
RX-1B 2
RX-1B 3 RX EEPROM checksum fault
RX-1B 4 RX Config table checksum fault
RX-1B 5 RX Synthesizer A/B unlocked
RX-1B 6 RX Synthesizer C unlocked
RX-1B 7 Astra Dixie communication fault
RX-1B 8 RX Internal voltage fault
RX-1B 9 RX cable disconnected
RX-1B 10 RX Initiation fault
RX-1B 11 CDU Output voltage fault
RX-1B 12 TMA CM Output Voltage Fault
RX-1B 13 RX Path Fault
-
-
RX-1B 47 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
 -POWER COMMUNICATION LOOP
2. ANTENNAS
-RX A
-RX B
-TX A
-TX B
3. ENVIRONMENT
-TEMPERATURE

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

000000000001 0
000000000002 1
000000000004 2
000000000008 3
000000000010 4
000000000020 5
000000000040 6
000000000080 7
000000000100 8
000000000200 9
000000000400 10
000000000800 11
000000001000 12
000000002000 13
000000004000 14
000000008000 15
000000010000 16
000000020000 17
000000040000 18
000000080000 19
000000100000 20
000000200000 21
000000400000 22
000000800000 23
000001000000 24
000002000000 25
000004000000 26
000008000000 27
000010000000 28
000020000000 29
000040000000 30
000080000000 31
000100000000 32
000200000000 33
000400000000 34
000800000000 35
001000000000 36
002000000000 37
004000000000 38
008000000000 39
010000000000 40
020000000000 41
040000000000 42
080000000000 43
100000000000 44
200000000000 45
400000000000 46
800000000000 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 fault 4 Alarm indication from the remote end
DIP fault 5 Alarm indication signal in time slot 16
DIP fault 6 Loss of multiframe alignment
DIP fault 7 Alarm ind. from remote end signalling equipment
DIP fault 8 Alarm indication signal ALL1
DIP fault 9 Loss of CRC multiframe alignment
DIP fault 10 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 8 MO LTF blocked from TF

DIGITAL PATH (DIP) FAULT CODE LIST

~~~Numeric vaues~~~

1 Alarm indication signal, AIS

2 Loss of frame alignment
3 Excessive error rate
4 Remote defect indication (Alarm indication from remote end in some AI2 documents)
5 Alarm indication signal in time slot 16
6 Loss of multiframe alignment
7 Alarm indication from the remote end signalling equipment
8 Alarm indication signal, ALL1
9 Loss of incoming signal
10 Consecutive severely errored seconds

~~~Abbreviations~~~

AIS Alarm indication signal

LOF Loss of frame alignment
ERATE Excessive error rate
RDI Remote defect indication (REFF in some AI2 documents)
AISM Alarm indication signal in time slot 16
LOMF Loss of multiframe alignment
REFM Alarm indication from the remote end signalling equipment
ALL1 Alarm indication signal
LOS Loss of incoming signal
CSES 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 1’s 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 there’s a T-Berd in the
DSX
TRU/TEI DCP1 DCP2
0 128 129&130
1 131 132&133
2 134 135&136
3 137 138&139
4 140 141&142
5 143 144&145
6 160 161&162
7 163 164&165
8 166 167&168
9 169 170&171
10 172 173&174
11 175 176&177