Professional Documents
Culture Documents
7745 Alarm Troubleshoot PDF
7745 Alarm Troubleshoot PDF
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.
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.
3 © Nokia Siemens Networks. All rights reserved.
7745 - CHANNEL FAILURE RATE ABOVE DEFINED
THRESHOLD
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
4 © Nokia Siemens Networks. All rights reserved.
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
• KPI Browser
Cell Doctor (report 211 Network Doctor) OSS
Cell KPI (report 204 Network Doctor) OSS
Check TSC
SD TCH : 59, 0F, 0D Switch BCCH Frequency to
Audit Neighbours TRX using ZERO command
& TCH SDCCH : 4B, 4D another TRX
BCC using ZEQO command
Site Visit
End
TX 3 , 4 and RX div
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
Performance Analysis:
IF: band q5 value is under 90%
THEN: we suspect that the TRX have bad
quality uplink or Downlink ( in this case
downlink issue)
Objective:
1. To have better site integration verification procedure
2. To make sure that all functionality of the integration site already
in place and being verified
3. To avoid unnecessary mistake on integration such as cross feeder
(partial and full), Loose feeder and others functionalities.