20 Jan
2012
20 Jan
'12
1:05 p.m.
Hi,
I am using OpenBSC with nanoBTS 165CU and 165AU models. In normal location
update BTS sends CHAN ACT NACK several times for the same ts and ss. After
that it sends some failure messages and restart the trx. Here i copy the
related logs from openbsc console:
Thu Jan 19 15:44:03 2012 <0000> chan_alloc.c:421 (bts=0,trx=0,ts=6,ss=0)
starting release sequence
Thu Jan 19 15:44:03 2012 <0003> gsm_04_08_utils.c:231 Sending Channel
Release: Chan: Number: 0 Type: 2
Thu Jan 19 15:44:03 2012 <0004> abis_rsl.c:579 (bts=0,trx=0,ts=6,ss=0)
DEACTivate SACCH CMD
Thu Jan 19 15:44:03 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=6,ss=0):
MEAS RES for inactive channel
Thu Jan 19 15:44:04 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=6,ss=0):
MEAS RES for inactive channel
Thu Jan 19 15:44:05 2012 <0004> abis_rsl.c:891 (bts=0,trx=0,ts=6,ss=0)
CONNECTION FAIL: RELEASING CAUSE=0x01(Radio Link Failure)
Thu Jan 19 15:44:05 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=6,ss=0) RF
Channel Release CMD due error 1
Thu Jan 19 15:44:05 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=6,ss=0):
MEAS RES for inactive channel
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:594 (bts=0,trx=0,ts=6,ss=0) is
back in operation.
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=6,ss=0):
MEAS RES for inactive channel
Thu Jan 19 15:44:08 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=6,ss=0)
SAPI=0 Thu Jan 19 15:44:08 2012 <0000> abis_rsl.c:1436
(bts=0,trx=0,ts=6,ss=0) ERROR INDICATION cause=Timer T200 expired (N200+1)
times
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=6,ss=0) RF
Channel Release CMD due error 1
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=6,ss=0):
MEAS RES for inactive channel
Thu Jan 19 15:44:08 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=warning level failure Probable cause= 03 00 01 Additional
Text=l3_if_dl.c:276Unrecognised signal(1302)
Thu Jan 19 15:44:08 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=warning level failure Probable cause= 03 00 01 Additional
Text=l3_if_dl.c:276Unrecognised signal(1302)
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=6,ss=0):
MEAS RES for inactive channel
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:658 (bts=0,trx=0,ts=6,ss=0) RF
CHANNEL RELEASE ACK
Thu Jan 19 15:44:08 2012 <0000> chan_alloc.c:303 Freeing lchan with state
RELEASE DUE ERROR - setting to NONE
Thu Jan 19 15:44:08 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=6,ss=0)
SAPI=0 RELEASE INDICATION
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:1322 (bts=0,trx=0,ts=6,ss=0)
Activating ARFCN(885) SS(0) lctype TCH/F r=LOCATION_UPDATE ra=0x0f
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:658 (bts=0,trx=0,ts=6,ss=0) RF
CHANNEL RELEASE ACK
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:665 (bts=0,trx=0,ts=6,ss=0) CHAN
REL ACK but state ACTIVATION REQUESTED
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:1322 (bts=0,trx=0,ts=6,ss=0)
Activating ARFCN(523) SS(0) lctype TCH/F r=LOCATION_UPDATE ra=0x0a
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:1060 (bts=0,trx=0,ts=6,ss=0)
CHANNEL ACTIVATE ACK
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:856 (bts=0,trx=0,ts=6,ss=0)
CHANNEL ACTIVATE NACK CAUSE=0x50(Radio channel already activated) Thu Jan
19 15:44:08 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=6,ss=0) RF Channel
Release CMD due error 1
Thu Jan 19 15:44:08 2012 <0000> chan_alloc.c:303 Freeing lchan with state
RELEASE DUE ERROR - setting to NONE
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:856 (bts=0,trx=0,ts=6,ss=0)
CHANNEL ACTIVATE NACK CAUSE=0x50(Radio channel already activated) Thu Jan
19 15:44:08 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=6,ss=0) RF Channel
Release CMD due error 1
Thu Jan 19 15:44:08 2012 <0000> chan_alloc.c:303 Freeing lchan with state
RELEASE DUE ERROR - setting to NONE
Thu Jan 19 15:44:08 2012 <0004> abis_rsl.c:1322 (bts=0,trx=0,ts=6,ss=0)
Activating ARFCN(523) SS(0) lctype TCH/F r=LOCATION_UPDATE ra=0x0f
Thu Jan 19 15:44:08 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=warning level failure Probable cause= 03 00 01 Additional
Text=l3_if_dl.c:276Unrecognised signal(1302)
Thu Jan 19 15:44:08 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=warning level failure Probable cause= 03 00 01 Additional
Text=l3_if_dl.c:276Unrecognised signal(1302)
Thu Jan 19 15:44:08 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=critical failure Probable cause= 03 00 00 Additional
Text=l3_dcm.c:1190
****
** l3_dcm.c#1190:Cn0x0e: Aborting RF Chan Rel on second attempt
** IPA_SW_FATAL_ERROR
** In task "TRX Proc:L3" @ (37329).
****
Thu Jan 19 15:44:09 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=critical failure Probable cause= 03 00 00 Additional Text=TRX
Proc:L3:l3_dcm.c#1190 (37329)
Thu Jan 19 15:44:09 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=warning level failure Probable cause= 03 00 01 Additional
Text=16395:WARN:OAM_RES:trx_fatal_error_log.c#260:Cn0x0e: Aborting RF Chan
Rel on second attempt
Thu Jan 19 15:44:09 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=critical failure Probable cause= 03 00 00 Additional Text=
[000ad1e8] |000ad230|800d2fe7|800a4144|000ad250|
Thu Jan 19 15:44:09 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=critical failure Probable cause= 03 00 00 Additional Text=
[000ad278] |00000000|000b91cc|000ad3c4|000ad3c4|
Thu Jan 19 15:44:09 2012 <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04)
INST=(00,00,ff) Failure Event Report Type=processing failure
Severity=warning level failure Probable cause= 03 00 01 Additional
Text=16396:WARN:OAM_RES:res_trx_status.c#231:TRX is not responding -
reinitialising the unit...
I could not realize the reason of the problem but i think there is
something wrong about the sequence of channel activation, release, ack and
nack messages between openbsc and bts. Could somebody help about the
solution of this or at give some idea to realize the problem?
Thanks
Jason