- This topic is empty.
-
AuthorPosts
-
18th August 2005 at 13:19 #41958
Patrick
GuestWho can explain this alarm? I don’t understand NED explanation.
example:
BSC1024 BCSU-0 SWITCH 2005-07-25 17:33:35.63
* ALARM BCSU-0 1A030-27 HAS_BX
(6948) 2725 ADJACENT CELL IDENTIFIER CONFIGURATION ERROR
92d 01 07 04 820d92: ZEEI:BTS=92 OK
01?
07?
04?
820: BCCH but where? What’s BTS?thank you.
18th August 2005 at 19:45 #41959Mik
GuestHello!
As I guess, handover was attepted from BTS 92 to other cell, but it was failed. 92 is source BTS.
01 = the BSC has detected an error in the adjacent cell definitions.
07 = BCC of Target BTS
04 = NCC of Target BTS
820 = BCCH of target cell
So, try to do as following:
ZEAO:BTS=92.
You will get list of cells, which are adjacent cells for Cell92. In the output you find problem target cell description including BCCH=820, NCC=04 and BCC=07.Regards.
19th August 2005 at 09:05 #41960Patrick
Guestok thank you.
but i have an another question:
how this alarm come? only one or few bad hand-over?
19th August 2005 at 09:28 #41961Mik
Guestone is enough for alarm, as i know
3rd September 2005 at 11:33 #41962Ebrahim Talaq
GuestBasically, you will find some logs regarding that alarm from the BCSU that has the alarm.
in the log you will see something similar to:
CALLER : 01C0 010D 00 RETURN ADDRESS: 000C (L0001).00000BD0
WRITE TIME: 2005-08-31 10:35:36.12
PARAMETERS: E-01 0024.00001F20 00000082 000C.0005ED67
USER TEXT : HAS:set ALARM 0x2725. target cell list
USER DATA : 01 01 00 C8 4E 54 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00Can anyone tell me how to get the tool to decode those messages??
Thanks.
5th September 2005 at 14:04 #41963marcel
GuestIs BTS located near a border? This alarm is triggered when a user doesn`t has a roaming agreement when he calling, and during this, crosses a fourign border. So the call will be dropped after beiing to far from BTS 92.
regards
6th September 2005 at 08:33 #41964Ebrahim
GuestHi,
I have observed that the BTS is nearby the border of the BSC (not the border of the network) and i get this alarm more than 3 times a day. The thing is that sometimes the alarm is referencing the MSC as the one detecting the error and sometimes the BSC. When the MSC detects the error, you don’t get any BTS number and other information.
I don’t think it is regarding roaming aggreement since the alarms i’m getting sometimes (if detected by the BSC) are refering to BTSs in the middle of my network.
7th September 2005 at 15:11 #41965Mohammad Yasin
GuestHi,
When the 2725 alarm is detected by MSC the one of the reason can be wrong parameters definition in cell id creation.
For Eg when we faced this problem the BSCSPC that was wrong in cell id creation so the alarm was detected during any inter BSC handover.
Thanks10th November 2015 at 16:48 #41966venj
GuestDoes anybody know how to debug BCSU to find the target site info for alarm.
** ALARM BCSU-2 1A005-00 HAS_BX
(3984) 2725 ADJACENT CELL IDENTIFIER CONFIGURATION ERROR
3267d 00 FF FF 65535d20th November 2018 at 09:44 #41967Pankaj yadav
Guest01 is default value
07 is BCC
04 IS NCC
820 is BCC
92 is BTS20th November 2018 at 09:57 #41968Pankaj yadav
GuestDoes anyone explain following alarm
(8735) 2725 ADJACENT CELL IDENTIFIER CONFIGURATION ERROR
1403d 00 FF FF 65535d -
AuthorPosts
- The forum ‘Telecom Design’ is closed to new topics and replies.