S/No

SR

Date

Sector Outage

1
2
3
4
5
6
7
8
9
10

2332964
2333225

11
12
13
14
15
16
17
18
19
20
21
22
23

2329547
2328626
2328965
2328277
2327294
2332103
2330908
2331162
2332638
2332990
2333296
2333695

30-07-2009 06:20 MDJH3293 (Sector A)

MDJH3291 (Sector D)
26-07-2009 10:12 MDIB3017 -A
28-07-2009 07:13 MDIB3053 -B
23-07-2009 23:13 MDIB3113 -B
18-07-2009 18:19 MDIB3118 -D
15-08-2009 07:51 MDIB3293 -B
07-08-2009 11:45 MDIB3201 -B
10-08-2009 07:54 MDIB3060 -B
18-08-2009 16:50 MDJH3072 -C
20-08-2009 15:41 MDIB3011 -B
22-08-2009 07:00 MDJH3293 -C
25-08-2009 12:48 MNPS4904 -A

24
25
26
27
28
29
30
31
32
33
34
35
36
37

2330256
2329397
2327923
2329598
2329951
2328637
2330441
2332398
2332428
2331120
2334621
2332206
2331797
2332913

04-08-2009 08:36
29-07-2009 15:40
22-07-2009 14:45
30-07-2009 12:48
01-08-2009 17:27
26-07-2009 12:55
5/8/2009 3:15
17-08-2009 15:02
17-08-2009 18:39
09-08-2009 07:45
30-08-2009 06:51
16-08-2009 08:11
13-08-2009 14:25
20-08-2009 04:19

MDGU4247 -C
MDLH1039 -C
MDLH1040 -C
MDLH1055 -A
MDLH1127_P -C
MDLH1171 -B
MDSK4285 -B
MDLH1039 -A
MDLH1167 -A
MDLH1184 -D
MDLHHUB10_P -D
MDSK4278 -C
MDSK4285 -D
WTLH7086 -B

38
39
40
41
42
43
44
45

2328843
2328426
2328889
2329988
2329527
2328402
2329190
2333599

27-07-2009
24-07-2009
27-07-2009
02-08-2009
30-07-2009
24-07-2009
28-07-2009
25-08-2009

MDKA2165 -A
MDKA2261_AG -C
MDKA2264 -B
MDKA2419 -B
MDKACMPAK0044 -A
MDKA2261 -D
WTKA8085 -B
MDKA2135 -A

2333502
2334141

2334259
2329070

RMA#

20-08-2009 12:45 MDFB4050_C

21-08-2009 17:53 MDFB4018_C
MDOK1206_D
24-08-2009 14:21 MDFB4020_D
MDFB4060_A
27-08-2009 06:50 MDSW4421_A
WTFB7059_C
MDSG4355_C
27-08-2009 18:58 MDFB4012_C
28-07-2009 15:14 MDSW1493 -C

17:19
13:30
22:36
09:33
02:45
11:56
23:52
00:19

RMA# 11290249-1
RMA#11282438-1
RMA#11282437-1
RMA#11282447-1
RMA#11286105-1
RMA#11282439-1
RMA#11290247-1

46

2333702

25-08-2009 13:31 MDKA2244 -D

47
48

2328583
2330768

25-07-2009 15:56 MNMU4413 -B

06-08-2009 16:03 MNMU4425

Faisalabad
AP SW Release
SP10
SP10
SP10
SP10
SP10
WMX2.5 SP1.5
SP10
WMX2.5 SP1.5
WMX2.5 SP1.5
SP10

Islamabad
SP10
SP10
SP10
SP10
WMX2.5 SP1.5
SP10
SP10
SP10
SP10
WMX2.5 SP1.5
SP10

Lahore
WMX2.5 SP1.4
SP10
SP10
SP10
SP10
SP10
SP10
SP10
SP10
SP10
SP10
WMX2.5 SP1.5

Karachi
SP10
SP10

SP10
SP10

SP10

Multan
SP10
WMX2.5SP1.5

Faisalabad
Flavour (TS)
PHYSAP_FM_EVENT_GANY_BBB1_MGT_RX_BUFFER_ERROR
PHYSAP_FM_EVENT_GANY_BBB1_MGT_RX_SYNC
Failed to read SIB EID, handle
PHYSAP_FM_EVENT_DAP1_TRX_POW_SUP_ALARM
physap_fpga_util_get_bbb_state - BBB0 status: 0xF0114
physap_fpga_isr_tsk - ERROR: Failed sending alarm message to FM thread
PHYSAP_FM_EVENT_DAP1_TRX_LOW_POW_ALARM
physap_fpga_util_get_bbb_state - BBB0 status: 0x4
physap_driver_create(), FPGA codeload failure
physap_fpga_util_get_bbb_state - BBB0 status: 0x10015
No known signature

Islamabad
Beginning load of TRX. This step could take several minutes
./mmt_sc_comms.c:151- Link Version Response not received from SC
physap_fpga_util_get_bbb_state - BBB0 status: 0x70114
physap_fpga_util_get_bbb_state - BBB0 status: 0x30015
physap_fpga_isr_tsk - ERROR: Failed sending alarm message to FM thread
physap_fpga_isr_tsk - ERROR: Failed sending alarm message to FM thread
No known signature
Failed to read SIB EID
Failed reading FPGA version from handle 1
PHYSAP_FM_EVENT_DAP1_TRX_POW_SUP_ALARM
No known signature
physap_fpga_isr_tsk - ERROR: Failed sending alarm message to FM thread

Lahore
physap_fpga_util_get_bbb_state - BBB0 status: 0x4
physap_fpga_util_get_bbb_state - BBB0 status: 0xF0015
Failed to read SIB EID, handle
physap_fpga_isr_tsk - ERROR: Failed sending alarm message to FM thread
PHYSAP_FM_EVENT_DAP1_TRX_POW_SUP_ALARM
Failed to initialize SIB[0] as sector 1
PHYSAP_FM_EVENT_DAP1_SIB_RF_LO_PLL_NOT_LOCKED
No known signature
apsnap missing
Failed to read SIB EID, handle
Modem logs missing
physap_fpga_util_get_bbb_state - BBB0 status: 0x80015
apsnap missing
physap_rfh_sib_init_sib - Primary Alarms never went ready

Karachi
TRX failure in SC.log; nothing in modem logs
RFHBBB1SIB alarm;no signature in modem logs
apsnap missing
apsnap missing
apsnap missing
physap_fpga_fm_translate_and_report_alarms - ERROR: Failed to set discrete alarm
apsnap missing
PHYSAP_FM_EVENT_DAP1_TRX_POW_SUP_ALARM

PHYSAP_FM_EVENT_DAP1_TRX_POW_SUP_ALARM

Multan
physap_fpga_isr_tsk - ERROR: Failed sending alarm message to FM thread

TS Comments

Eqpt Replaced (RAN)

RF Head
RF Head
RF Head
RF Head
RF Head
RF Head
Modem OSP loaded
Modem IMAG
RF Head
RFH
RFH
Modem
SFP
Hard Reboot
SFP
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH
RFH

RFH
SFP
RFH

PHYSAP_FM_EVENT_SAAP1_TRX1_POW_SUP_ALARM
This alarm is caused when the TRX power supply voltage is out of range. As there
are 4 TRX, if 1 or 2 TRX are showing this alarm, sector should be still active
but the performance might be reduced. If the power to the TRX is suffering,
these alarms might show up and power cycling the whole AP from the BCU breaker
will reset this condition.
Possible causes for a TRX power supply voltage is out of range:
- Power supply module failure.
- TRX HW failure with the voltage sensing ADC or FPGA circuitry
- TRX fault causing a voltage rail short
As per the suggestion from FW team, please go ahead and power cycle the SAAP
from the BCU breaker and wait till modem reboots. Let the modem comeup again and
verify if the alarms are gone. If not, then we need to replace the TRX module on
the RFH (As you already did with few of the RFH's earlier).