You are on page 1of 29

Fault Analysis

BTS Nokia Alarm

1 © Nokia Siemens Networks. All rights reserved.


Alarm Found Based on Category

1. Hardware Problem.
• 7604 (BTS Operation Degrade).
• 7602 (BCF Notification).
• 7949 (Difference in Rx Levels of Main and Diversity Antenna /
TRX).
• 7874 (Temperature Controlling Device Faulty)
• 7890 (Fault in Cooling Fan).
• 7606 (TRX Faulty).
• 7735 (TRX Test Failed).

2 © Nokia Siemens Networks 11/6/2009


Alarm Found Based on Category

2. Transmission Problem.
• 8202 (Loss Of Supervision)
• 8066 (Alarm Indication Signal (AIS) Received).
• 7609 (TRE Faulty).
• 8048 (Loss Of Incoming Signal).
• 8221 (Version Mismatch).
• 7704 (PCM Failure).
• 8099 (Received Bit Error Ratio(BER)>1E-3).
• 8000 (Power Supply Fault).

3 © Nokia Siemens Networks 11/6/2009


Alarm Found Based on Category

3. Environment / External Alarm Problem.


• 7401 (External Alarm 1).
• 7402 (External Alarm 2).
• 7403 (External Alarm 3).
• 7404 (External Alarm 4).
• 7405 (External Alarm 5).
• 7406 (External Alarm 6).

4 © Nokia Siemens Networks 11/6/2009


Alarm Found Based on Category

4. Performance Degraded Problem


• 7745 (CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD).
• 7743 (MEAN HOLDING TIME BELOW DEFINED THRESHOLD).
• 7744 (EXCESSIVE TCH INTERFERENCE).
• 7746 (CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD).
• 7712 (WORKING SDCCH CHANNEL RATIO BELOW THRESHOLD)
• 7738 (BTS WITH NO TRANSACTIONS)

5 © Nokia Siemens Networks 11/6/2009


Hardware Problem Suggested Action (7604)

1. 7604 (BTS Operation Degraded)


First we have to identify which sector has problem. Then we should check if
problem comes from single TRX, several TRX or all TRX on that sector by following
steps mentioned below :
a) Checking all Cabling Connection (Including SMA, Semirigid etc).
b) Checking all connector connection on that sector and probably need to
repaired or replaced.
c) If problem comes from single TRX  Try to Swap TRX to make sure if TRX
is really faulty. If after swap activity problem cleared then previous TRX
need to replace but if problem still persist need to perform further action
on point “e”.
d) If problem comes from several TRX / all TRX  Try to check TRX Quality
by TRX Test and Swap DVHA / DVDC. If after swap activity problem
cleared then previous DVHA / DVDC need to replace but if problem still
persist need to perform further action on point “e”.
e) Check RSSI and VSWR Quality to make sure feeder of antenna quality.
f) Also need to check for SW of BTS Configuration and Parameter Setting of
BTS.

6 © Nokia Siemens Networks 11/6/2009


Hardware Problem Suggested Action (7602)

2. 7602 (BCF Notification)


• We found this alarm mostly occurred due to cooling fan problem
(Cooling fan is broken). Try to swap Cooling Fan with others to
make sure if cooling fan was really broken / faulty. But if problem
still persist then module need to replace.
• For other notification info we need to read the alarm info then
check the module which related to alarm info.
• Also we found for this type of alarm that SW Configuration and
Version between BTS and BSC is different which need to be
matched.

7 © Nokia Siemens Networks 11/6/2009


Hardware Problem Suggested Action (7949)

3. 7949 (Difference in Rx Levels of Main and Diversity Antenna /


TRX).
• Checking Cabling for specified TRX especially RX Cabling connection
between Main and Diversity.
• Checking Connector Condition and Connector for specified TRX 
Repaired / Replaced Connector.

Note :
Most problems we found were that connector need to repair /
replace and SMA Cabling connection was not tight.

8 © Nokia Siemens Networks 11/6/2009


Hardware Problem Suggested Action (other)

4. 7874 (Temperature Controlling Device Faulty)


• Check HCUA module Condition.
• Replace HCUA which Faulty.

5. 7890 (Fault in Cooling Fan).


• Replace Cooling fan which Faulty.

6. 7606 (TRX Faulty).


• Replace TRX which Faulty.

7. 7735 (TRX Test Failed)


• Try to swap TRX which has problem and if problem still persist then need to
replace TRX.

9 © Nokia Siemens Networks 11/6/2009


Transmission Problem Suggested Action (8202)

1. 8202 (Loss Of Supervision)


This Alarm do not impact to performance BTS itself only to loss of
supervision on specified TRE.
Steps for solving :
• Check Q1 cable condition and Connection  Probably need
to replace for Q1 cable or Q1 Connector / RJ-45.
• Scanning Q1 Connection from OSS.
• If alarm still persist then need to perform reset TRE which
makes outage impact during Reset Activity (Suggest to do on
Maintenance window).

10 © Nokia Siemens Networks 11/6/2009


Transmission Problem Suggested Action (Other
[1])
2. 8066 (Alarm Indication Signal (AIS) Received).
• Check the transmission link condition / Q1 Connection.
• Check the system / tributary connection.
Mostly for this alarm we found comes from other equipment which connected to
transmission equipment was down or Q1 system isn’t using anymore.

3. 7609 (TRE Faulty).


• Replace TRE which Faulty.
When performing of TRE Replacement will have outage impact and also due to will do
recomissioning of TRE Config so make sure previous configuration being captured.

4. 8048 (Loss Of Incoming Signal).


• Check the transmission link condition / Q1 Connection.
• Check the system / tributary connection.
Mostly for this alarm we found comes from other equipment which connected to
transmission equipment was down or Q1 system isn’t using anymore.

11 © Nokia Siemens Networks 11/6/2009


Transmission Problem Suggested Action (Other
[2])
5. 8221 (Version Mismatch).
• Check SW Configuration and Version between Hardware and
Software of TRE Equipment.
• Corrective SW Configuration and Version between Hardware and
Software of TRE Equipment.
• Check for previous configuration of TRE Equipment.

6. 7704 (PCM Failure).


Mostly this type of alarm we found occured due to site was down
due to Power Problem (PLN down but doesn’t have battery bank as
backup at site).

12 © Nokia Siemens Networks 11/6/2009


Transmission Problem Suggested Action (Other
[3])
7. 8099 (Received Bit Error Ratio(BER)>1E-3).
• Check the condition of cables, connectors and correct polarities of
the wire pairs.
• Check that FIxx is fully inserted in to ESMA.
• Replace FIxx.
• Check the signal quality of the transmission path to the alarming
equipment.

8. 8000 (Power Supply Fault).


• Try to plug / unplug power supply module but if alarm still persist
then power supply module need to replace.

13 © Nokia Siemens Networks 11/6/2009


Environment / External Alarm Suggested Action

1. 7401 (External Alarm 1).


2. 7402 (External Alarm 2).
3. 7403 (External Alarm 3).
4. 7404 (External Alarm 4).
5. 7405 (External Alarm 5).
6. 7406 (External Alarm 6).

• For all those alarm which mentioned above we need to check from DDF to
specified external alarm which connected (Rectifier, Power (R,S,T), Battery Bank,
and etc).
• Tightened DDF Connnection if found on loosen condition.
• If problem still persist then module or equipment which connection to ENVA
Alarm need to repair / replace (Rectifier Module, Battery Bank or etc).

14 © Nokia Siemens Networks 11/6/2009


Suggested Action Summary [1st level]

First or Standard Action :


1. Checking all Cabling Connection.
2. Checking Connector Condition.
3. TRX Test.
4. Check HW and SW Configuration of BTS.

Further Action :
1. Swap TRX.
2. Swap DVHA or DVDC,
3. Swap BB2F.
4. Check RSSI, VSWR Test.

15 © Nokia Siemens Networks 11/6/2009


Suggested Action Summary [2nd level]

Summary :
1. Identify alarm which occured to locate which
Sector or TRX that problem.
2. Do first action as mentioned at previous slide
before go to further action.
3. If problem still persist then HW or Module need
to replace.
4. If problem still persist then need further check on
parameter setting.

16 © Nokia Siemens Networks 11/6/2009


Performance Degradation Suggested Action

1. 7743 (MEAN HOLDING TIME BELOW DEFINED THRESHOLD).


2. 7744 (EXCESSIVE TCH INTERFERENCE).
3. 7746 (CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD).
4. 7712 (WORKING SDCCH CHANNEL RATIO BELOW THRESHOLD)
5. 7745 (CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD).

• Those all alarms related to BTS quality of service and need further check on
parameter setting beside check on physical condition of BTS Equipment.
• for 7744 type of alarm we need to make sure that interference didn’t come from
internal interference which probably comes from Combiner, Connector or Other
HW of BTS Problem.
• if Alarm still persist after HW Check or even replacement then parameter setting
need to further check or frequency scanning.
• Further info of 7745 and 7743 problem will explained on next slide.

17 © Nokia Siemens Networks 11/6/2009


7745 - Description

The rate of calls terminating in failure on a channel is above the threshold value
set by the operator. The alarm is used to supervise the functioning of traffic and
signaling channels, and to detect the possible faulty channels.
Alarm in TRXlevel, reported in BSC

Category : Quality of Services Alarm, Severity Medium

KeyWord
Whenever a channel is released with a release cause other than a normal one,
the counter of channel failures for the released channel is incremented.

NSN Default Threshold :


TCHFR = TCH failure rate (20 % or 30%)
SCHFR = SDCCH failure rate (80 %)
PRDCFR = length of supervision period (60 min)
CS = channel seizure threshold value (10)

18 © Nokia Siemens Networks 11/6/2009


7745 – Channel Release Procedure

Whenever a channel is released with a release cause other than a normal one,
the counter of channel failures for the released channel is incremented.
After a certain observation time and a certain threshold it will reported in the
7745 alarm. It give an indication that there’s a failure that need to be
addressed, but overall KPI need to be used as a first priority.

19 © Nokia Siemens Networks 11/6/2009


7745 - release cause description
7745 alarm occurance in Telkomsel Network
Around 90% is affected in TCH, around 10% is affected in SDCCH
Abnormal relase cause defined below :
TCH Failure SDCCH Failure
0A Channel state conflict between RRMPRB and ABIPRB 03 SDCCH radio failure
0B Channel type conflict between RRMPRB and ABIPRB 04 Source SDCCH radio failure in HO
0D TCH radio failure 05 Target SDCCH radio failure in HO
0E Source TCH radio failure in HO 0A Channel state conflict between RRMPRB and ABIPRB
0F Target TCH radio failure in HO 0B Channel type conflict between RRMPRB and ABIPRB
1D TCH transcoder failure 23 SDCCH failure due to a LAPD failure
1E Source TCH transcoder failure in HO 24 SDCCH failure due to a BTS failure
1F Target TCH transcoder failure in HO 25 SDCCH failure due to user actions
2E TCH failure due to a LAPD failure 26 SDCCH failure due to a BCSU reset
2F TCH failure due to a BTS failure 27 SDCCH failure due to radio network reconfiguration actions
30 TCH failure due to user actions 48 SDCCH activation failure during call set-up
31 TCH failure due to a BCSU reset 4A Target SDCCH activation failure in HO
32 TCH failure due to radio network reconfiguration actions 4B SDCCH failure due to an Abis interface failure in call set-up
51 TCH activation failure during call set-up 4C Source SDCCH failure due to an Abis interface failure in HO
53 Target TCH activation failure in HO 4D Target SDCCH failure due to an Abis interface failure in HO
54 TCH failure due to an Abis interface failure in call set-up 4E SDCCH failure due to an A interface failure in call set-up
55 Source TCH failure due to an Abis interface failure in HO 4F Source SDCCH failure due to an A interface failure in HO
56 Target TCH failure due to an Abis interface failure in HO 50 Target SDCCH failure due to an A interface failure in HO
57 TCH failure due to an A interface failure in call set-up
58 Source TCH failure due to an A interface failure in HO
59 Target TCH failure due to an A interface failure in HO
FF Actually no release cause, but causes all channels with
an abnormal release cause to be listed
20 © Nokia Siemens Networks 11/6/2009
7745 - Alarm Information
<HIST> AKSES_UI BCF-0065 BTS-0156 QUAL 2009-01-13 13:51:49.59
** ALARM TRX -006 JNCSILIWANGIMD2
DISABLED
(60756) 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD
01 00 01 01 01 01 01 00 00 04 00 48d

<HIST> AKSES_UI BCF-0065 BTS-0156 QUAL 2009-01-13 13:51:49.59


.. CANCEL TRX -007 JNCSILIWANGIMD2
ENABLED
(60755) 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD
01 00 00 00 00 00 00 00 00 00 00 0d

Supplementary information fields


1 indicates if the alarm is on the TCH or on the SDCCH channel 01: TCH 02: SDCCH
2..9 indicates if the channel failure rate is above the defined threshold in time slot 0 00:
belove threshold (no alarm) 01: above threshold (alarm)
10 time slot with the highest failure rate
11 subchannel identification TCH: 00: TCH/H -subchannel 0 01: TCH/H -subchannel 1 02:
TCH/F -subchannel subchannel identification SDCCH: 00 - 07: SDCCH -subchannel 0 – 7
12 proportion/percentage of TCH or SDCCH subchannel releases due to failure in all
channel releases on a given channel during the measurement period
21 © Nokia Siemens Networks 11/6/2009
Investigation Flowchart [7745]

Start 7745

Root Cause
&
Suplementary
information

TCH RR : TCH : 59 OK
0F
SD Audit Neighbour & Paramater Monitoring Alarm KPI OK
0D CR & Execute
& TCH ADCE & KPI Alarm
SD : 4B
4D

SD NOK

Justification for alarm :


VSWR
1. Countur
Check Check Installation Troubleshoot
2. Remote
Coverage Quality Report
3. Blocking & Fading
4. Etc

ND 196 > uplink & downlink Quality End


ND 195 > TRX by downlink /uplink level balance
ND 232 > Time advance

Unbalance
founded Troubleshooting if before VSWR OK > check cable connection
Action
Uplink & downlink & arester / grounding
per TRX

Check cross Troubleshooting


sector founded BCCH per feeder
NOK

Check Parameter /
ARFCN Monitoring Alarm Alarm Clear
CR & Execute
or Audit Antenna & KPI & KPI OK
tilting OK

22 © Nokia Siemens Networks 11/6/2009


BTS installation standard

TX1,2 and RX main

TX 3,4 and RX div

23 © Nokia Siemens Networks 11/6/2009


If we have 7745, 7743 alarms in our network, what is
really happening? [1]

Before Site Visit :


Make sure Audit neighbor, TSC checking and TRXtest

Action on site :
1. 7745, 7743 at one TRX only
- Check SMA cable at Tx connector to WCXA of the TRX, make sure properly connected
- Replace TRX, BB2F and SMA cables if needed
2. 7745, 7743 at two TRX
- Try to switch BCCH, if still appear potential have a partial cross feeder
- Replace TRX, BB2F WCXA, or DVXA if needed
- Check alarms of other sector to ensure analysis
3. 7745, 7743 at all TRXs under same cell
- Possibilities error : full partial cross feeder, bad feeder quality and its connection,
interference, broken DVXA

24 © Nokia Siemens Networks 11/6/2009


If we have 7745, 7604 alarms in our network, what is
really happening? [2]
If: VSWR have been checked,
Then: We can find out from hardware by checking its transmit path from TRx
unit, Tx port, SMA-cables from Tx port to WCxA, WCxA itself, and so on, until its
feeder connection and antenna.
Thus:
7604 alarm is usually related to degraded receive quality of one sector or one
TRx.
From hardware point of view:
Check its receive path from TRx unit, Rx main and RxDiv port, SMA cables from Rx
port to M2xA, M2xA itself, and so on, until its feeder connection and antenna.

25 © Nokia Siemens Networks 11/6/2009


AUDIT ANTENNA and Neighbors

26 © Nokia Siemens Networks 11/6/2009


Exception for 7745

7745 will keep occur for this condition :


1. No have neighbors cell ( island or remote standalone)
2. Landscape contour ( hill and valley)
3. Obstacle

This exception need to be justify as long as the KPI value achieve

27 © Nokia Siemens Networks 11/6/2009


Performance Problem Summary

1. Alarm 7745 occur due to Abnormal release Channel


-Mostly in TCH 53,56,59 because of Handover, Call Setup Issue
-SDCCH 4B because of antenna and feeder installation
2. Module M6HA should be part of BTS High Capacity
3. Correction related alarm 7745  software CX5 CD4 (replace CX4.1 CD4)
4. Many things that can lead to alarm 7745, it can be categorized as below :
Transmission issue, Power Related issue
Environment Related, Air Conditioning, Temperature
BTS HW problem related, Cooling Fan, Module faulty
BTS Antenna Line
Coverage Issue
Configuration Mismatch between BSC and BTS/MMI
Some existing problem in the old SW
Other maintenance activity in the BSC level

28 © Nokia Siemens Networks 11/6/2009


Thank You

29 © Nokia Siemens Networks. All rights reserved.