Guidelines

RBS6000 DUG-RUG Troubleshooting
Guidelines
DESCRIPTION
1/1551-LZA 701 6006 Uen A
Copyright
Ericsson AB 2013. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
1/1551-LZA 701 6006 Uen A | 2013-08-22
Contents
Contents
1 Introduction 1
1.1 Revision History 1
1.2 Flowchart Legend 1
2 BSC Alarms without Corresponding BTS Fault 3
2.1 LOCAL MODE or OML FAULT 3
2.2 BSC RF Output Power Supervision Alarms 5
3 Issues When Parameter No Alarms is Received 9
3.1 KPI Degradations 9
4 Issues with BTS Fault Codes 13
4.1 SO TRXC I1A:13 (RF Loop Test Fault) 13
4.2 SO TRXC I1A:25 (TX/RX Communication Fault) 14
4.3 AO TX I1B:12/32 (TX High/Low Temperature) 16
4.4 SO TRXC I1B:8 (Y Link Communication Fault) 18
4.5 AO RX I1A:5/6/7/8 (RX Path A/B/C/D Imbalance) 20
4.6 SO TRXC I2A:25 (TX Max Power Restricted) 22
4.7 Synchronization 23
4.8 SO TRXC I1A:22 (Voltage Supply Fault) 26
4.9 TX Output Power Limits Exceeded 27
4.10 Other Faults on MO TRXC, TX, RX, TS 29
5 Appendix 31
5.1 Local Conditions 31
5.2 Power 31
5.3 Basic RBS Log Reading 32
5.4 Starting OMT Monitors 35
5.5 RX Path Imbalance Monitor 37
5.6 RF Loop Test Parameters Monitor 40
5.7 RUG and Antenna Systems Connection 41
5.8 Moving BCCH between TXs from NOC 42
5.9 Checking If TG Is in a Cascaded Chain 42
5.10 Definition of IS Connections for DUG-10 44
5.11 VCO Control Value 45
1/1551-LZA 701 6006 Uen A | 2013-08-22
RBS6000 DUG-RUG Troubleshooting Guidelines
5.12 RXELP Decoding 46
5.13 Checking Which TX Transmits BCCH from OMT 48
Reference List 51
1/1551-LZA 701 6006 Uen A | 2013-08-22
Introduction
1 Introduction
This document describes common fault alarms and reactions for RBS6000
equipped with DUG-10 and RUG.
The document is valid for all supported BTS SW releases up to G13A_1 unless
otherwise stated.
It aims at increasing field troubleshooting efficiency, and avoiding the necessity
of replacing non-faulty hardware.
It is designed to support field activities for field operation engineers and
Network Operation Center (NOC) support engineers. All defined actions must
be performed in the documented order.
1.1 Revision History
This is the first version of this document.
1.2 Flowchart Legend
Gray shading = Action from NOC
1/1551-LZA 701 6006 Uen A | 2013-08-22 1
2 1/1551-LZA 701 6006 Uen A | 2013-08-22
BSC Alarms without Corresponding BTS Fault
2 BSC Alarms without Corresponding BTS
Fault
2.1 LOCAL MODE or OML FAULT
2.1.1 Symptoms
BSC alarm LOCAL MODE or OML FAULT on CF, TRX or both.
2.1.2 Description
Communication between the BSC and the MO in the BTS is not working.
The LOCAL MODE slogan occurs only after the DUG or RUG has been
manually set in LOCAL MODE, but can also occur after local automatic
recovery actions. In general, treat LOCAL MODE as OML FAULT.
2.1.3 Actions
Maximum time estimated:
NOC: 10 minutes
Field: 15 minutes
1/1551-LZA 701 6006 Uen A | 2013-08-22 3
P023720B
4 1/1551-LZA 701 6006 Uen A | 2013-08-22
2.2 BSC RF Output Power Supervision Alarms
2.2.1 Symptoms
BSC alarms:
RF PERFORMANCE
NO TRAFFIC
LOW DL QUALITY
2.2.2 Description
RF PERFORMANCE
This alarm is raised on a TRX when at least 105 failed assignments that have
been logged on a specific TX exceed successful ones.
NO TRAFFIC
This alarm is raised when a cell is verified to take no traffic. Cells with no active
channels are excluded.
Two alarm raise criteria exist:
No traffic in the cell for 24 hours
A sudden decrease in high levels of traffic to no traffic within a 1530
minute time period
LOW DL QUALITY
This alarm is raised on a Channel Group when 4000 measurements made
during a 40-minute period indicate that the DL quality is poor, although the UL
quality is acceptable.
2.2.3 Actions
These alarms are rarely caused by hardware issues in RBS6000. They are
designed to alert the operator when normal supervision is not sufficient.
1/1551-LZA 701 6006 Uen A | 2013-08-22 5
P023721A
6 1/1551-LZA 701 6006 Uen A | 2013-08-22
P023722B
1/1551-LZA 701 6006 Uen A | 2013-08-22 7
8 1/1551-LZA 701 6006 Uen A | 2013-08-22
Issues When Parameter No Alarms is Received
3 Issues When Parameter No Alarms is
Received
3.1 KPI Degradations
3.1.1 Symptoms
TCH/SDCCH drops
TCH/SDCCH establishment failures
Loss of traffic
Fewer handover attempts
3.1.2 Actions
Follow the checklist below to find common configuration and installation faults
that affect KPIs.
1/1551-LZA 701 6006 Uen A | 2013-08-22 9
P023723A
10 1/1551-LZA 701 6006 Uen A | 2013-08-22
Issues When Parameter No Alarms is Received
P023724C
Frequency
Band
PWRMAX
Combined
PWRMAX
Uncombined
1800/1900 49 47
800/900 51 49
1/1551-LZA 701 6006 Uen A | 2013-08-22 11
12 1/1551-LZA 701 6006 Uen A | 2013-08-22
Issues with BTS Fault Codes
4 Issues with BTS Fault Codes
4.1 SO TRXC I1A:13 (RF Loop Test Fault)
4.1.1 Fault Name
RF Loop Test Fault
4.1.2 Description
The RF loop test is used to detect faults on the TX or the RX. Data is sent uplink
on the Y link to the DUG and routed back to the RUG downlink on other pins on
the Y link. The data is used to transmit a series of RF bursts that are looped
internally in the RUG. The RX measures quality and level received. The test is
run during startup, and at regular intervals during normal operation.
4.1.3 Action
Maximum time estimated for the work:
NOC: 10 minutes
Field: 45 minutes
1/1551-LZA 701 6006 Uen A | 2013-08-22 13
P023725A
4.2 SO TRXC I1A:25 (TX/RX Communication Fault)
4.2.1 Fault Name
TX/RX Communication Fault
14 1/1551-LZA 701 6006 Uen A | 2013-08-22
4.2.2 Description
Problems are detected on the internal communication interface between the
TX and the RX.
This alarm can occur due to Y link issues or high traffic load, and when system
voltage is outside the range defined in the specifications.
4.2.3 Action
Maximum time estimated: approximately 20-25 minutes
1/1551-LZA 701 6006 Uen A | 2013-08-22 15
P023726A
4.3 AO TX I1B:12/32 (TX High/Low Temperature)
4.3.1 Fault Name
TX High Temperature
16 1/1551-LZA 701 6006 Uen A | 2013-08-22
4.3.2 Related Faults
SO TRXC I2A:11
4.3.3 Description
This alarm indicates either a high or low temperature in the TRX.
It indicates a high temperature in the TRX if it is raised together with faults
SO TRXC I2A:25 and SO TRXC I2A:1, TX high temperature.To lower the
temperature, the output power is reduced 2 dB. To achieve a total reduction of
4 dB, this action can be repeated once only. If the high temperature remains,
the output power is switched off and one of the AO TX alarms is also raised.
If the temperature remains high and the TX diversity function is activated, one
of the following alarms is also raised: AO TX I1B:12 or AO TX I2A:0.
4.3.4 Action
NOC: 5 minutes
Field: 50 minutes
1/1551-LZA 701 6006 Uen A | 2013-08-22 17
P023727A
4.4 SO TRXC I1B:8 (Y Link Communication Fault)
4.4.1 Fault Name
Y Link Communication Fault
18 1/1551-LZA 701 6006 Uen A | 2013-08-22
4.4.2 Description
Disturbances are detected on the Y link interfaces.
4.4.3 Action
NOC: 5 minutes
Field: 90 minutes
P023728A
Continued on the next page.
1/1551-LZA 701 6006 Uen A | 2013-08-22 19
P023729A
Continued from the previous page.
4.5 AO RX I1A:5/6/7/8 (RX Path A/B/C/D Imbalance)
4.5.1 Fault Name
RX Path Imbalance
This fault is also generated for the related alarms in the following list:
RX I2A:5/6/7/8 (RX Path A/B/C/D Imbalance)
CF I2A:57, TX I1B:35 (RX Path Imbalance)
CF I2A:33, RX I2A:1/2/3/4 (RX Diversity Lost)
4.5.2 Description
This fault is generated when the signal strength between two antennas in the
same antenna system differs to the extent that it exceeds the limits defined by
the Define RX Path Imbalance parameters in the OMT.
If the class 1 limit is exceeded, the related fault AO TX I1B:35 is also generated
and the TX is disabled.
20 1/1551-LZA 701 6006 Uen A | 2013-08-22
The supervision of this fault is based on measurements over a long period.
Hence the alarm does not cease as soon as it is corrected. The RX imbalance
monitor must therefore be used to verify the correction of the fault.
4.5.3 Action
Maximum time estimated for the work:
NOC: 20 minutes
Field: 60 minutes
Note: For 4-way diversity, that is RX C and RX D, replace A with C and B
with D as shown in the flowchart.
P023730B
Continued on next page.
1/1551-LZA 701 6006 Uen A | 2013-08-22 21
P023731B
(Continued from the previous page.)
4.6 SO TRXC I2A:25 (TX Max Power Restricted)
4.6.1 Fault Name
TX Max Power Restricted
22 1/1551-LZA 701 6006 Uen A | 2013-08-22
4.6.2 Description
If this alarm is raised together with SO TRXC I2A:11, TX high temperature, it
indicates a high temperature in the TRX. The output power is reduced 2 dB to
lower the temperature. This can be repeated once to give a total reduction of 4
dB. If the high temperature remains, the output power is switched off and one
of the AO TX alarms is also raised.
4.6.3 Action
Maximum work time:
NOC: 5 minutes
P023732B
4.7 Synchronization
4.7.1 Symptoms
No handover attempts between affected cells and non-affected cells are
observed.
AO TF EC1:1 - PCM SYNCH (No Usable PCM-Reference)
AO TF EC2:1 - PCM SYNCH (No Usable PCM-Reference)
1/1551-LZA 701 6006 Uen A | 2013-08-22 23
4.7.2 Actions
Estimated maximum work time:
NOC: 10 minutes
Field: 25 minutes
24 1/1551-LZA 701 6006 Uen A | 2013-08-22
P023733B
1/1551-LZA 701 6006 Uen A | 2013-08-22 25
P023734A
4.8 SO TRXC I1A:22 (Voltage Supply Fault)
4.8.1 Symptoms
SO TRXC I1A:22 Voltage Supply Fault
4.8.2 Actions
NOC: 10 minutes
Field: 15 minutes
26 1/1551-LZA 701 6006 Uen A | 2013-08-22
P023735A
4.9 TX Output Power Limits Exceeded
4.9.1 Symptoms
SO TRXC I2A:12 TX (Output Power Limits Exceeded)
1/1551-LZA 701 6006 Uen A | 2013-08-22 27
AO TX I1B:13 (TX Output Power Limits Exceeded)
4.9.2 Actions
NOC: 10 minutes
Field: 15 minutes
P023736A
28 1/1551-LZA 701 6006 Uen A | 2013-08-22
4.10 Other Faults on MO TRXC, TX, RX, TS
For help with handling all other faults on MO TRXC, TX, RX, and TS, see the
following flowchart.
P023737A
1/1551-LZA 701 6006 Uen A | 2013-08-22 29
30 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
5 Appendix
5.1 Local Conditions
5.1.1 Environment, Operating Conditions
For RBS6101, 6102 with a heater:
Between -33 and 50 degrees Celsius, relative humidity between 15% and
100%
For RBS6101, 6102 without a heater:
0 - 50 degrees Celsius, relative humidity between 15% and 100%
For RBS6201, 6202:
5 - 50 degrees Celsius, relative humidity between 5% and 85%
5.2 Power
5.2.1 AC Power
For RBS 6101, 6102:
Voltage 180-275 V, frequency range from 45 to 65 Hz
For RBS 6201:
Voltage 90-275 V, frequency range from 45 to 65 Hz
5.2.2 DC Power
For RBS 6101, 6102:
-48V: Voltage -40.0 to -58.5V
For RBS 6201:
-48V: Voltage -40.0 to -58.5V
+24 V: Voltage +20.5 V to +29.0 V
For RBS 6202:
-48V: Voltage -40.0 to -57.6 V
1/1551-LZA 701 6006 Uen A | 2013-08-22 31
5.2.3 Grounding
All equipment cables entering the site room must be individually connected to
the site earth grounding system by a cable with a diameter greater than 6 mm.
The following figure shows an example of a site grounding system.
5.3 Basic RBS Log Reading
5.3.1 Read Out RBS Log
1. Use OMT R35/7 or later.
2. Connect to the OMT and read the IDB
3. To read the RBS log, right-click on the GSM Node in System View, then
press Display => Log.
32 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
5.3.2 Verify RBS Log Type and Time Frame
5.3.2.1 RU Types in RBS Logs
A DUG log contains the header:
DUG log
*******
A RUG(-n) log contains the header, where -n
is the number of the RUG (0-n):
RUG-n log
*********
In a complete RBS RAM log, the DUG log is listed first, and all RUG logs follow
on in sequence.
5.3.2.2 Detailed and General Logs
The detailed log is a filtered log that includes more detail. The target group
is RBS designers.
The general log is a filtered log where only the main events are printed.
The target group is support engineers.
1/1551-LZA 701 6006 Uen A | 2013-08-22 33
The detailed logs are printed first, preceded by:
**** Detailed log ****
The general log is printed after the detailed log, preceded by:
**** General log ****
5.3.2.3 Log Time Coverage
The entries in the RBS logs are in chronological order.
The oldest information is at the top.
The logs are circular. When the log area is full, the oldest information is
overwritten.
The time-stamps in the logs are System Time when available.
If the RBS does not have any System Time, for instance just after a reset,
the time starts from 90-01-01 00:00:00.
After each restart and at regular intervals, the RBS is updated with the
system time fetched from the BSC:
[12-08-18 04:05:06.002] P_MPSK_CLOCK timeout_clock_main.c:404
TRACEH:Setting time: 12-08-18 04:05:28.00
5.3.3 Checking for Y Link Disturbances
When identifying Y link disturbances, determine whether they occur before the
RF Loop Test fault or before the TX/RX Communication fault.
5.3.3.1 Finding Latest Occurrence of Desired Fault in DUG General Log
Start from the bottom of the DUG general log and search backwards for:
Raise, I1A, TX RX COMMUNICATION FAULT, or Raise, I1A, RF LOOP
TEST FAULT.
Examples of printouts when these faults are raised are:
[12-09-04 10:21:56.926] O_RBS_Status RBS_STATUS_DEF.c:393
TRACEH:FAULT:12-09-04 10:21 MO: TRXC, Instance 1, Raise , I1A, TX
RX COMMUNICATION FAULT
[12-09-04 10:21:56.124] O_RBS_Status RBS_STATUS_DEF.c:393
TRACEH:FAULT:12-09-04 10:21 MO: TRXC, Instance 1, Raise , I1A, RF
LOOP TEST FAULT
Observe the time.
34 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
5.3.3.2 Finding Correct RUG Log
Find the correct RUG log.
For TRX 0-1, see RUG-0
For TRX 2-3, see RUG -1
5.3.3.3 Finding Corresponding Time in RUG Detailed Log
Check if any of the traces in the following list appear in the seconds just before
the observed time.
Tarot Fault Map Y1 Bit n: 0->1
Tarot Fault Map Y2 Bit n: 0->1
Tarot Fault Map TBI_G_ATC Bit n: 0->1
HWU_Tarot: Faultread error - 'Y2, Rx Receiver clock error'
HWU_Tarot: Faultread error - 'Y2, Rx Msg shorter than 16 bits'
Examples:
[12-09-09 23:10:01.050] 0\C_TarotSuper C_TarotSuper.c:673 TRACED:Tarot
Fault Map TBI_G_ATC Bit 7: 0->1
[12-09-09 23:10:01.050] 0\C_TarotSuper C_TarotSuper.c:673 TRACED:Tarot
Fault Map Y1 Bit 5: 0->1
[12-09-09 23:10:01.262] TAROT_DRV_MAIN_A tarot_drv_main.c:2725
TRACED:HWU_Tarot: Faultread error - 'Y2, Rx Msg shorter than 16 bits'
[12-09-09 23:10:01.262] TAROT_DRV_MAIN_A tarot_drv_main.c:2729
TRACED:HWU_Tarot: Faultread error - 'Y2, Rx Receiver clock error'
If any of these traces are present, treat the fault as a Y Link Fault.
5.4 Starting OMT Monitors
1. From the Maintenance drop-down menu, select Monitor
1/1551-LZA 701 6006 Uen A | 2013-08-22 35
2. Select the desired monitors from the list of available monitors in the
left-hand window. Click the right arrow (-->) to move them to the list of
monitors to start in the right-hand window.
If the monitor output is to be logged to file, check the appropriate box and
select the destination file. To start the monitors, select Start monitor.
36 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
3. The selected monitors are started. Either they run until stopped by the
OMT, or the OMT is disconnected, or the MO is reset.
5.5 RX Path Imbalance Monitor
5.5.1 Checking Current RX Path Imbalance Alarm Settings
1. From the "Configuration" drop-down menu, select "Define" and go to
Antenna Supervision.
1/1551-LZA 701 6006 Uen A | 2013-08-22 37
2. To display the current settings, select the antenna or antenna system.
5.5.2 Starting Monitor RX Path Imbalance
For the best result, start the RX Path Imbalance monitor for all TRXs
connected to one antenna system. See Section 5.7 on page 41.
38 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
5.5.3 Interpreting Monitor RX Path Imbalance
The monitor produces the following printout every 5 minutes for each TRX:
RX imb. superv. values:
Supervision window configured time: 1440 min
Supervision window elapsed time: 60 min
Average delta signal strength A-B: -3.1dB
Number of samples A-B: 7846
Parameter Supervision window configured time specifies the configured
time the ASM requires to collect measurements.
Parameter Supervision window elapsed time specifies the length of time
during which the ASM has been receiving data.
At TRX/RUG reset, all data in the ASM is erased and starts from scratch.
During normal operation, the elapsed time value is the same as the
configured time value, and the ASM overrides the oldest data with new
data every 5 minutes.
During a troubleshooting session, ensure that the elapsed time is reset to
zero after each step, for example: recabling, HW swap, reset, and so on.
The average delta signal strength A-B indicates the average difference
calculated in the RX signal strength between RXA and RXB.
A positive value means that RXA is stronger than RXB and that RXB is
probably faulty.
A negative value means that RXB is stronger than RXA and that RXA is
probably faulty.
The number of samples A-B indicates the number of samples collected.
Each sample consists of approximately 0.5 second of speech on one Air
Time Slot Number (TN)
Before drawing conclusions regarding faulty TX paths, ensure that enough
samples are available. In general, do not trust results based on fewer than
1000 samples.
The number of samples can be concentrated to one or more TRXs during
off-peak periods, such as at night, by blocking other TRXs in the same cell.
If a test call is made, it must be made from a relevant position at least 50 m
from the antenna and preferably involve some movement. Do NOT try to
aggregate the number of samples by making a test call from the site, since
any call from a position just under the antenna can cause significant signal
imbalance between RXA and RXB which is irrelevant.
1/1551-LZA 701 6006 Uen A | 2013-08-22 39
5.6 RF Loop Test Parameters Monitor
1. Start monitor RF Loop Test Monitors on the affected TRX.
The monitor output window typically presents a printout that contains no
values, which means that no RF Loop Test has been run since the monitor
was started.
2. When RF Loop Test has been run, the monitor output window is updated
with the new values:
40 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
The following tips are useful if the RF Loop Test fails for external reasons.
If an external interferer causes an RF Loop Test Fault:
BER values are typically high.
RXLevA and RXLevB values are also typically high.
If a Y link fault causes an RF Loop Test Fault:
BER values are typically high.
RXLevA and RXLevB values are typically fluctuating.
5.7 RUG and Antenna Systems Connection
1. In the Radio view, check the following boxes:
The TX or RXA box or both
The RXB box
2. To see connections related to the selected unit, check the Filter box and
highlight a RUG, antenna, or TMA.
1/1551-LZA 701 6006 Uen A | 2013-08-22 41
5.8 Moving BCCH between TXs from NOC
1. To verify which TXs are carrying BCCH, check the TX part of the RXCDP
printout to determine which TX is using C0F:
MO RESULT ARFCN TXAD BSPWR C0F MISMATCH
RXOTX-32-0 CONFIG HOP 9 45 NO NONE
RXOTX-32-4 CONFIG 48 0 45 YES NONE
2. To move the BCCH between TXs, block the TRX carrying BCCH and
subordinate MOs.
For example, referring to the table above:
RXBLI:MO=RXOTRX-32-4,subord,force;
3. Wait until all BPCs are reconfigured and value C0F is shown as YES on
another TX.
4. To move the BCCH to a specified TX, block all other TXs. This is only way
to handle this simply using one command.
5.9 Checking If TG Is in a Cascaded Chain
Check TMODE Mode: RXMOP:MO=RXOTG.
If TMODE=SCM: Cascading is not supported;
If TMODE=TDM: RXAPP:MO=RXOTG;
42 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
If TG is occupied, all TSs (24 on T1, 31 on E1) on all the DIPs in use
=> No Cascading
If TG is lower than all TSs on any of the DIPs, use the following guide to
find out which DIP is used, and if other TGs are connected to this DIP
A-bis Overview
DEV(RBLT-x&&-y)
! DIP(RBLTz)
GS-----SNT(ETRBLT-z)---------------------MO(TG/TRX/TS)
The Switching Network Terminal (SNT) represents the interface board (ETC)
between the Group Switch and the PCM line. The DIP represents the PCM
line. Each Device (DEV) handles the traffic for one PCM time slot. There are
32 DEVs per SNT/DIP.
Connection printouts
<-NTCOP NTCOP-> <-RXMDP on TRX or TS->
DIP-----------SNT-----------DEV----------------------MO
<-DTDIP-> <-RADEP <-RXAPP on RXOTG
The following are examples of how to use these printouts:
Find out which DIP is connected to a TG:
1- Find an RBLT device connected to the TG:
RXMDP:MO=RXOTRX (or RXAPP on RXOTG)
2- Find whichSNT is connected to this RBLT device:
RADEP:DEV=RBLT-x
3- Find which DIP is connected to this SNT
NTCOP:SNT=ETRBLT-z (or DTDIP:SNT=ETRBLT-z)
Find out which TG is connected to a DIP:
1- Find which SNT is connected to the DIP:
DTDIP:DIP=RBLTz
2- Find which RBLT devices are connected to this SNT
NTCOP:SNT=ETRBLT-z
3- Find which RBLT devices are in use
STDEP:DEV=RBLT-x&&-y;
Devices in state "sebu" are used by CF or TRX;
devices in state "busy" are used by TS.
4- Choose an RBLT device and find which MO is
using it For a device in state "sebu",
type RXMDP:MOTY=RXOTRX,DEV=RBLT-y;
For a device in state "busy",
type RXMDP:MOTY=RXOTS,DEV=RBLT-z;
Note: To ensure successful operation, all CFs connected to the same DIP
must have a different TEI value.
1/1551-LZA 701 6006 Uen A | 2013-08-22 43
5.10 Definition of IS Connections for DUG-10
Connections between IS and TRXs are defined with the RXMOI command
on RXOTRX.
Separate DCP ranges are defined for 16K and 64K signalling. The DCPs listed
below are the only values allowed.
16K signalling, that is non-EDGE/8PSK prepared:
TEI-0 DCP1=178 DCP2=179&&-186
TEI-1 DCP1=187 DCP2=188&&-195
TEI-2 DCP1=196 DCP2=197&&-204
TEI-3 DCP1=205 DCP2=206&&-213
TEI-4 DCP1=214 DCP2=215&&-222
TEI-5 DCP1=223 DCP2=224&&-231
TEI-6 DCP1=232 DCP2=233&&-240
TEI-7 DCP1=241 DCP2=242&&-249
TEI-8 DCP1=250 DCP2=251&&-258
TEI-9 DCP1=259 DCP2=260&&-267
TEI-10 DCP1=268 DCP2=269&&-276
TEI-11 DCP1=277 DCP2=278&&-285
64K signalling, that is EDGE/8PSK prepared:
TEI-0 DCP1=712 DCP2=713&&-747
TEI-1 DCP1=748 DCP2=749&&-783
TEI-2 DCP1=784 DCP2=785&&-819
TEI-3 DCP1=820 DCP2=821&&-855
TEI-4 DCP1=856 DCP2=257&&-891
TEI-5 DCP1=892 DCP2=893&&-927
TEI-6 DCP1=928 DCP2=929&&-963
TEI-7 DCP1=964 DCP2=965&&-999
TEI-8 DCP1=1000 DCP2=1001&&-1035
TEI-9 DCP1=1036 DCP2=1037&&-1071
TEI-10 DCP1=1072 DCP2=1073&&-1107
TEI-11 DCP1=1108 DCP2=1109&&-1143
Example 16K channel:
44 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
RXMOI:MO=RXOTRX-0-0,TEI=0,DCP1=178,DCP2=179&&-186;
RXMOI:MO=RXOTRX-0-1,TEI=0,DCP1=748,DCP2=749&&-783;
5.11 VCO Control Value
The VCO Control value is a control value used internally by the VCO in the
DUG. It can be used for troubleshooting PCM synchronization.
A monitor that prints the current VCO Control Value is available. The value is
printed in the DUG log during resynchronization and startup.
5.11.1 VCO Control Value Monitor
Select Maintenance => Monitor => VCO Control Value.
This monitor prints the C_V value used to keep the synchronization oscillator
at a stable frequency.
Normal behavior:
The C_V value displays minor changes due to temperature level. Aging causes
a slow increase of the C_V value. The C_V value differs between different
RBSs.
Faulty behavior:
1/1551-LZA 701 6006 Uen A | 2013-08-22 45
The C_V value must be stable and not continuously increase or decrease.
Note: Normally, a new DUG has a C_V of approximately 8200. This value
normally increases by 50250 steps per year. A value outside this
range can indicate PCM synchronization, in which case further analysis
must be performed. However, the value is not regarded as faulty.
5.11.2 VCO Control Value in RBS Log
The C_V value is printed in the Detailed DUG log in the following format:
[90-01-01 00:01:32.104] TSC_Regulation regulation.c:2576 TRACEH:C_V:
8105
5.12 RXELP Decoding
Each fault map is represented as a set of binary digits.
Each fault can be active (1) or inactive (0).
Every time a fault is raised (0 => 1), or ceased (1 => 0), the fault map for the
RU is sent from the BTS to the BSC, and the fault map in RXELP is updated
accordingly.
In RXELP, the fault maps are presented in hexadecimal format, thus four faults
are represented in each digit. If for instance fault 0 and 2 are active (0101), the
fault is shown as 5 in RXELP.
Example:
46 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
Start by transforming the Hex number to Bin:
0004 0000 0000 Hex => Bin:
0 = 0000
0 = 0000
0 = 0000
4 = 0100
0 = 0000
0 = 0000
0 = 0000
0 = 0000
0 = 0000
0 = 0000
0 = 0000
0 = 0000
1/1551-LZA 701 6006 Uen A | 2013-08-22 47
0000 0000 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 Bin
Counting the positions from the right, the digit on the far right corresponds to
alarm number 0. If alarm number 0 is received, this position has the value 1.
The second digit from the far right corresponds to alarm number 1, and so
on. In this case, only the 35th digit from right that is set to 1, thus only alarm
34 in this fault map is raised.
This corresponds to CF I2A:34, which in turn corresponds to Output Voltage
Fault in the RBS 6000 Fault List.
5.13 Checking Which TX Transmits BCCH from OMT
Use the OMT Monitor TS Channel Comb to determine which TX is transmitting
BCCH from the OMT.
This is the resulting printout:
48 1/1551-LZA 701 6006 Uen A | 2013-08-22
Appendix
The printout shows the channel combination for each TN and the air-time
timeslot on the selected TXs.
Channel combination 04 and 05 corresponds to BCCH, respectively
BCCH+SDCCH/4.
Channel combination 07 corresponds to SDCCH/8 and 08 is TCH.
In the example, BCCH is transmitted by TX-8.
1/1551-LZA 701 6006 Uen A | 2013-08-22 49
50 1/1551-LZA 701 6006 Uen A | 2013-08-22
Reference List
Reference List
[1] Fault List RBS 6000, 1/006 51-LZA 701 6002
[2] Setting IDB Parameters, G10A to G13A, 1/1543-LZA 701 6002
[3] Non-RF Connections, 47/1551-LZA 701 6001
1/1551-LZA 701 6006 Uen A | 2013-08-22 51

Guidelines

Uploaded by

Copyright:

Available Formats

Guidelines

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guidelines

Uploaded by

Copyright:

Available Formats

RBS6000 DUG-RUG Troubleshooting

You might also like