help about reason of media GW reset

Post Reply
wwe
Member
Posts: 16
Joined: 06 Oct 2009 12:11
Location: Germany, Hannover

help about reason of media GW reset

Post by wwe » 03 May 2011 04:34

Hi guys,

I'm wondering if somebody can see what is going wrong here:

Code: Select all

24/04/11 21:10:41 001021M|--/--/-/---|=3:1125=external alarm : "mtcl login"
24/04/11 22:16:50 001021M|02/00/-/---|=3:2490=Loss of a virtual coupler GPA (2,0) of the associated coupler MEX (2,0)
24/04/11 22:16:51 001021M|02/01/-/---|=2:2042=Loss of a UA type cpl
24/04/11 22:16:51 001021M|01/00/-/---|=0:4402=Compression state 26 (10-13 INFO, other ERROR); daughter board 0,DSP 0"
24/04/11 22:16:51 001021M|02/02/-/---|=2:2042=Loss of a UA type cpl
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854x009=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854x005=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854x005=MediaGateway messages lost
24/04/11 22:16:51 001021M|02/04/-/---|=2:2042=Loss of a UA type cpl
24/04/11 22:16:51 001021M|02/05/-/---|=2:2042=Loss of a Z type cpl
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854x029=MediaGateway messages lost
24/04/11 22:16:51 001021M|--/--/-/---|=2:2140=Alarm : SET resources quantity critical
24/04/11 22:16:51 001021M|02/08/-/---|=2:2042=Loss of a Z type cpl
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854x034=MediaGateway messages lost
24/04/11 22:16:51 001021M|02/--/-/---|=2:2043=Loss of the 2 CRYSTAL
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854x002=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854x008=MediaGateway messages lost
24/04/11 22:16:51 001021M|01/00/-/---|=2:5854=MediaGateway messages lost
24/04/11 22:17:21 001021M|01/00/-/---|=2:5854x007=MediaGateway messages lost
24/04/11 22:18:27 001021M|--/--/-/---|=5:2141=SET resources quantity normal
24/04/11 22:18:34 001021M|02/04/0/006|=4:2151=Undeclared subdevice AOM20 present
24/04/11 22:18:38 001021M|02/01/0/000|=5:3958=IBS operational
24/04/11 22:18:38 001021M|02/02/0/000|=5:3958=IBS operational
24/04/11 22:18:47 001021M|02/00/-/---|=4:2491=GPA(2,0) virtual coupler commissioning of the associated coupler MEX(2,0)
24/04/11 22:19:04 001021M|02/08/-/---|=5:2019=Z coupler commissioning
24/04/11 22:19:04 001021M|02/05/-/---|=5:2019=Z coupler commissioning
24/04/11 22:19:10 001021M|02/01/-/---|=5:2019=UA coupler commissioning
24/04/11 22:19:10 001021M|02/02/-/---|=5:2019=UA coupler commissioning
24/04/11 22:19:10 001021M|02/04/-/---|=5:2019=UA coupler commissioning
I'm pretty sure nobody was working on the network and pbx at this time.

Schnee88
Member
Posts: 2
Joined: 15 Sep 2015 14:37

Re: help about reason of media GW reset

Post by Schnee88 » 07 Nov 2017 12:15

I have a very similar problem with a R9.0 OXE intalled in a Hotel. It has 3 Large Cabinets, the main Cabinet has a CS2 and a GD2. Problem comes from time to time causing the loss of a virtual coupler and a real coupler (MEX board) , the thing is, it only happends with one of the two MEX Boards.

31/10/17 12:08:40 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
31/10/17 12:18:26 000001M|004/00/-/---|=3:2490=Loss of a virtual coupler GPA (4,0) of the associated coupler MEX (4,0)
31/10/17 12:18:26 000001M|004/01/-/---|=2:2042=Loss of a UA type cpl
31/10/17 12:18:26 000001M|004/02/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:18:26 000001M|004/03/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:18:26 000001M|---/--/-/---|=2:2140=Alarm : SET resources quantity critical
31/10/17 12:18:26 000001M|004/04/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:18:26 000001M|004/05/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:18:26 000001M|004/08/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:18:26 000001M|004/--/-/---|=2:2043=Loss of the 4 CRYSTAL
31/10/17 12:18:26 000001M|002/00/-/---|=0:4402=Compression state 26 (10-13 INFO, other ERROR); daughter board 0,DSP 0"
31/10/17 12:18:26 000001M|002/00/-/---|=2:5854=MediaGateway messages lost
31/10/17 12:18:26 000001M|002/00/-/---|=2:5854x014=MediaGateway messages lost
31/10/17 12:18:26 000001M|002/00/-/---|=2:5854=MediaGateway messages lost
31/10/17 12:18:47 000001M|002/00/-/---|=2:5854x002=MediaGateway messages lost
31/10/17 12:18:47 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
31/10/17 12:20:10 000001M|---/--/-/---|=5:2141=SET resources quantity normal
31/10/17 12:20:13 000001M|004/00/-/---|=3:2490=Loss of a virtual coupler GPA (4,0) of the associated coupler MEX (4,0)
31/10/17 12:20:13 000001M|004/01/-/---|=2:2042=Loss of a UA type cpl
31/10/17 12:20:13 000001M|004/02/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:20:13 000001M|---/--/-/---|=2:2140=Alarm : SET resources quantity critical
31/10/17 12:20:13 000001M|004/03/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:20:13 000001M|004/04/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:20:13 000001M|004/05/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:20:13 000001M|004/08/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:20:14 000001M|004/--/-/---|=2:2043=Loss of the 4 CRYSTAL
31/10/17 12:20:14 000001M|002/00/-/---|=0:4402=Compression state 26 (10-13 INFO, other ERROR); daughter board 0,DSP 0"
31/10/17 12:20:14 000001M|002/00/-/---|=2:5854=MediaGateway messages lost
31/10/17 12:20:14 000001M|002/00/-/---|=2:5854x004=MediaGateway messages lost
31/10/17 12:20:14 000001M|002/00/-/---|=2:5854=MediaGateway messages lost
31/10/17 12:20:14 000001M|002/00/-/---|=2:5854=MediaGateway messages lost
31/10/17 12:20:14 000001M|002/00/-/---|=2:5854=MediaGateway messages lost
31/10/17 12:20:43 000001M|002/00/-/---|=2:5854x013=MediaGateway messages lost
31/10/17 12:21:54 000001M|004/--/-/---|=2:2043=Loss of the 4 CRYSTAL
31/10/17 12:22:40 000001M|003/08/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:44 000001M|002/02/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:45 000001M|002/03/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:45 000001M|002/04/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:45 000001M|002/05/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:48 000001M|003/02/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:48 000001M|003/03/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:48 000001M|003/04/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:49 000001M|003/05/-/---|=2:2042=Loss of a Z type cpl
31/10/17 12:22:49 000001M|002/27/0/254|=4:3687=Error DSP GPA card 0 opcode : 3
31/10/17 12:22:56 000001M|002/07/-/---|=2:2042=Loss of a PCM type cpl
31/10/17 12:22:56 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
31/10/17 12:22:59 000001M|003/00/0/254|=4:3687=Error DSP GPA card 0 opcode : 3
31/10/17 12:22:59 000001M|003/06/-/---|=2:2042=Loss of a NDDI type cpl
31/10/17 12:23:19 000001M|002/27/0/000|=2:2440=Voice guide fct out of service - DTMF receiver of GPA (2,27)
31/10/17 12:24:29 000001M|002/00/0/254|=2:0379=Inter ACT link HS: 23,(19,1),172.20.94.144,00:80:9f:83:70:c4
31/10/17 12:24:29 000001M|002/--/-/---|=2:2043=Loss of the 2 CRYSTAL
31/10/17 12:24:29 000001M|002/00/-/---|=2:2042=Loss of a GD type cpl
31/10/17 12:24:29 000001M|003/--/-/---|=2:2043=Loss of the 3 CRYSTAL
31/10/17 12:24:29 000001M|002/27/-/---|=3:2490=Loss of a virtual coupler GPA (2,27) of the associated coupler GD (2,0)
31/10/17 12:24:29 000001M|003/00/-/---|=3:2490=Loss of a virtual coupler GPA (3,0) of the associated coupler MEX (3,0)
31/10/17 12:26:41 000001M|002/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.83.70.c4 (binmg)
31/10/17 12:26:41 000001M|002/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.83.70.c4 (binmg)
31/10/17 12:27:10 000001M|002/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.83.70.c4 (binmg)
31/10/17 12:27:10 000001M|002/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.83.70.c4 (binmg)
31/10/17 12:27:33 000001M|002/00/-/---|=5:0409=The inter-ACT link over IP from (19 1) is up
31/10/17 12:27:34 000001M|002/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 16
31/10/17 12:27:44 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
31/10/17 12:27:56 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
31/10/17 12:27:56 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
31/10/17 12:27:58 000001M|003/02/0/006|=3:1275=Waiting for MF Q23 detector neqt 406, typ_term AUTPOS, cristal 3
31/10/17 12:28:03 000001M|002/00/-/---|=5:2019=GD coupler commissioning
31/10/17 12:28:06 000001M|003/02/0/006|=3:1276=No MF Q23 detector for neqt 406, typ_term AUTPOS, cristal 3
31/10/17 12:28:09 000001M|---/--/-/---|=5:2141=SET resources quantity normal
31/10/17 12:28:12 000001M|004/01/0/000|=5:2053=Terminal 0 in service
31/10/17 12:28:13 000001M|004/01/0/001|=5:2053=Terminal 1 in service
31/10/17 12:28:14 000001M|004/01/0/002|=5:2053=Terminal 2 in service
31/10/17 12:28:14 000001M|002/07/-/---|=5:2019=PCM coupler commissioning
31/10/17 12:28:15 000001M|004/01/0/003|=5:2053=Terminal 3 in service
31/10/17 12:28:16 000001M|004/01/0/004|=5:2053=Terminal 4 in service
31/10/17 12:28:16 000001M|002/07/0/001|=2:0053=DDI R2 fault 23 DtEqt -1 Info -1
31/10/17 12:28:17 000001M|004/01/0/005|=5:2053=Terminal 5 in service
31/10/17 12:28:18 000001M|004/01/0/006|=5:2053=Terminal 6 in service
31/10/17 12:28:19 000001M|004/01/0/007|=5:2053=Terminal 7 in service
31/10/17 12:28:20 000001M|003/00/-/---|=4:2491=GPA(3,0) virtual coupler commissioning of the associated coupler MEX(3,0)
31/10/17 12:28:20 000001M|002/27/-/---|=4:2491=GPA(2,27) virtual coupler commissioning of the associated coupler GD(2,0)
31/10/17 12:28:24 000001M|003/06/-/---|=5:2019=NDDI coupler commissioning
31/10/17 12:28:30 000001M|004/00/-/---|=4:2491=GPA(4,0) virtual coupler commissioning of the associated coupler MEX(4,0)
31/10/17 12:28:30 000001M|002/05/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:30 000001M|002/04/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:30 000001M|002/02/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:30 000001M|002/03/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:38 000001M|003/02/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:38 000001M|003/05/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:38 000001M|003/04/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:38 000001M|003/08/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:38 000001M|003/03/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:48 000001M|004/02/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:48 000001M|004/05/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:48 000001M|004/03/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:48 000001M|004/04/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:48 000001M|004/08/-/---|=5:2019=Z coupler commissioning
31/10/17 12:28:53 000001M|004/01/-/---|=5:2019=UA coupler commissioning
31/10/17 12:29:51 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
31/10/17 12:30:03 000001M|002/06/-/---|=2:2457=PCM coupler (2,6) not initalized yet
31/10/17 12:32:36 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 10 2
31/10/17 12:34:22 000001M|003/00/-/---|=3:2490=Loss of a virtual coupler GPA (3,0) of the associated coupler MEX (3,0)

We dont know why this is happening, it doesnt say much in error "2490".
We are thinking into reload the Binaries to the GD board and also make changes in MEX Boards and HSL1 daughter boards.
Any advice?

Best Regards.

alexeik
Member
Posts: 193
Joined: 26 Apr 2007 10:47
Location: Bad Oeynhausen, germany

Re: help about reason of media GW reset

Post by alexeik » 09 Nov 2017 09:22

31/10/17 12:27:34 000001M|002/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 16
says

"- 16 : Not enough buffer descriptor"

i remember we had a customer with a similar error, and finally we changed the mex on expansion shelf to a gd (for example create a shelf 5, and move all cards from shelf 4 to 5)

it was the only way to solve it

fery_s
Member
Posts: 49
Joined: 08 Nov 2014 06:38

Re: help about reason of media GW reset

Post by fery_s » 12 Nov 2017 02:25

did you check your shelfs synchronization? i had this problem and it caused by synchronization , my shelf with mex board sync by e1 link and the link has some isue from public isdn , when it went down my gd and mex was reset.

Post Reply

Return to “Media Gateway”