GD3 reboot

moradpp
Member
Posts: 1
Joined: 13 Dec 2011 04:19

Re: GD3 reboot

Post by moradpp » 13 Dec 2011 04:37

can i work without the gd3 if i am using only ip phones?
with app server
and sip ext

britda01
Member
Posts: 3
Joined: 03 Jun 2013 13:24

Re: GD3 reboot

Post by britda01 » 27 Jun 2015 10:27

Hi.

Please your help.

I have a similar problem.

26/06/15 08:31:27 000001M|001/00/-/---|=0:4402=Compression state 26 (10-13 INFO, other ERROR); daughter board 0,DSP 0"
26/06/15 08:31:44 000001M|001/00/0/254|=2:0379:R0=Inter ACT link HS: 23,(19,1),10.29.128.27,00:80:9f:35:c5:3e
26/06/15 08:31:44 000001M|001/--/-/---|=2:2043=Loss of the 1 CRYSTAL
26/06/15 08:31:44 000001M|001/00/-/---|=2:2042:R0=Loss of a GD/GD3 type cpl
26/06/15 08:31:44 000001M|001/04/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:31:44 000001M|001/05/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:31:44 000001M|001/06/-/---|=2:2042:R0=Loss of a PRA type cpl
26/06/15 08:31:44 000001M|001/07/-/---|=2:2042:R0=Loss of a PCM type cpl
26/06/15 08:31:44 000001M|003/--/-/---|=2:2043=Loss of the 3 CRYSTAL
26/06/15 08:31:44 000001M|004/--/-/---|=2:2043=Loss of the 4 CRYSTAL
26/06/15 08:31:44 000001M|001/27/-/---|=3:2490=Loss of a virtual coupler GPA (1,27) of the associated coupler GD/GD3 (1,0)
26/06/15 08:31:45 000001M|003/00/-/---|=3:2490=Loss of a virtual coupler GPA (3,0) of the associated coupler MEX (3,0)
26/06/15 08:31:45 000001M|003/01/-/---|=2:2042:R0=Loss of a UA type cpl
26/06/15 08:31:45 000001M|003/02/-/---|=2:2042:R0=Loss of a MIX type cpl
26/06/15 08:31:45 000001M|003/03/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:31:45 000001M|003/06/-/---|=2:2042:R0=Loss of a NDDI type cpl
26/06/15 08:31:45 000001M|003/07/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:31:45 000001M|003/08/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:31:45 000001M|003/02/-/---|=3:2490=Loss of a virtual coupler UA (3,9) of the associated coupler MIX (3,2)
26/06/15 08:31:45 000001M|003/02/-/---|=3:2490=Loss of a virtual coupler Z (3,10) of the associated coupler MIX (3,2)
26/06/15 08:31:45 000001M|004/00/-/---|=3:2490=Loss of a virtual coupler GPA (4,0) of the associated coupler MEX (4,0)
26/06/15 08:31:45 000001M|004/01/-/---|=2:2042:R0=Loss of a UA type cpl
26/06/15 08:31:45 000001M|004/02/-/---|=2:2042:R0=Loss of a UA type cpl
26/06/15 08:31:45 000001M|004/07/-/---|=2:2042:R0=Loss of a NDDI type cpl
26/06/15 08:31:45 000001M|004/08/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:31:53 000001M|---/--/-/---|=0:1609=114 incidents sent by coupler (1, 7)
26/06/15 08:31:54 000001M|---/--/-/---|=0:1609=340 incidents sent by coupler (2, 6)
26/06/15 08:32:53 000001M|---/--/-/---|=0:1609=4 incidents sent by coupler (2, 6)
26/06/15 08:35:30 000001M|001/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 16
26/06/15 08:35:50 000001M|001/07/0/001|=2:0053=DDI R2 fault 23 DtEqt -1 Info -1
26/06/15 08:36:00 000001M|001/00/-/---|=5:2019=GD/GD3 coupler commissioning
26/06/15 08:36:01 000001M|003/02/0/032|=5:2053=Terminal 32 in service
26/06/15 08:36:02 000001M|003/01/0/000|=5:2053=Terminal 0 in service
26/06/15 08:36:03 000001M|003/01/0/001|=5:2053=Terminal 1 in service
26/06/15 08:36:04 000001M|003/01/0/002|=5:2053=Terminal 2 in service
26/06/15 08:36:05 000001M|003/01/0/003|=5:2053=Terminal 3 in service
26/06/15 08:36:06 000001M|003/01/0/004|=5:2053=Terminal 4 in service
26/06/15 08:36:07 000001M|003/01/0/005|=5:2053=Terminal 5 in service
26/06/15 08:36:08 000001M|003/01/0/006|=5:2053=Terminal 6 in service
26/06/15 08:36:08 000001M|003/01/0/007|=5:2053=Terminal 7 in service
26/06/15 08:36:10 000001M|003/01/0/008|=5:2053=Terminal 8 in service
26/06/15 08:36:11 000001M|003/01/0/009|=5:2053=Terminal 9 in service
26/06/15 08:36:12 000001M|003/01/0/010|=5:2053=Terminal 10 in service
26/06/15 08:36:12 000001M|001/07/-/---|=5:2019=PCM coupler commissioning
26/06/15 08:36:12 000001M|004/01/0/000|=5:2053=Terminal 0 in service
26/06/15 08:36:13 000001M|004/01/0/001|=5:2053=Terminal 1 in service
26/06/15 08:36:13 000001M|003/01/0/012|=5:2053=Terminal 12 in service
26/06/15 08:36:14 000001M|004/01/0/002|=5:2053=Terminal 2 in service
26/06/15 08:36:14 000001M|004/02/0/002|=5:2053=Terminal 2 in service
26/06/15 08:36:15 000001M|004/01/0/003|=5:2053=Terminal 3 in service
26/06/15 08:36:16 000001M|003/01/0/014|=5:2053=Terminal 14 in service
26/06/15 08:36:16 000001M|004/01/0/004|=5:2053=Terminal 4 in service
26/06/15 08:36:16 000001M|004/02/0/004|=5:2053=Terminal 4 in service
26/06/15 08:36:17 000001M|003/01/0/015|=5:2053=Terminal 15 in service
26/06/15 08:36:17 000001M|004/02/0/005|=5:2053=Terminal 5 in service
26/06/15 08:36:17 000001M|004/01/0/005|=5:2053=Terminal 5 in service
26/06/15 08:36:18 000001M|004/02/0/006|=5:2053=Terminal 6 in service
26/06/15 08:36:19 000001M|004/02/0/013|=5:2053=Terminal 13 in service
26/06/15 08:36:19 000001M|004/01/0/007|=5:2053=Terminal 7 in service
26/06/15 08:36:19 000001M|004/02/0/007|=5:2053=Terminal 7 in service
26/06/15 08:36:19 000001M|003/02/-/---|=5:2019=MIX coupler commissioning
26/06/15 08:36:20 000001M|004/01/0/008|=5:2053=Terminal 8 in service
26/06/15 08:36:20 000001M|004/02/0/008|=5:2053=Terminal 8 in service
26/06/15 08:36:20 000001M|003/06/-/---|=5:2019=NDDI coupler commissioning
26/06/15 08:36:21 000001M|004/02/0/009|=5:2053=Terminal 9 in service
26/06/15 08:36:22 000001M|004/01/0/010|=5:2053=Terminal 10 in service
26/06/15 08:36:22 000001M|004/01/0/009|=5:2053=Terminal 9 in service
26/06/15 08:36:22 000001M|004/02/0/013|=5:2053=Terminal 13 in service
26/06/15 08:36:22 000001M|004/02/0/010|=5:2053=Terminal 10 in service
26/06/15 08:36:23 000001M|004/02/0/011|=5:2053=Terminal 11 in service
26/06/15 08:36:24 000001M|004/01/0/012|=5:2053=Terminal 12 in service
26/06/15 08:36:26 000001M|004/02/0/014|=5:2053=Terminal 14 in service
26/06/15 08:36:27 000001M|004/02/0/015|=5:2053=Terminal 15 in service
26/06/15 08:36:28 000001M|001/05/-/---|=5:2019=Z coupler commissioning
26/06/15 08:36:28 000001M|001/04/-/---|=5:2019=Z coupler commissioning
26/06/15 08:36:31 000001M|004/07/-/---|=5:2019=NDDI coupler commissioning
26/06/15 08:36:36 000001M|003/07/-/---|=5:2019=Z coupler commissioning
26/06/15 08:36:36 000001M|003/08/-/---|=5:2019=Z coupler commissioning
26/06/15 08:36:36 000001M|003/03/-/---|=5:2019=Z coupler commissioning
26/06/15 08:36:41 000001M|003/01/-/---|=5:2019=UA coupler commissioning
26/06/15 08:36:46 000001M|004/08/-/---|=5:2019=Z coupler commissioning
26/06/15 08:36:51 000001M|004/01/-/---|=5:2019=UA coupler commissioning
26/06/15 08:36:52 000001M|004/02/-/---|=5:2019=UA coupler commissioning
26/06/15 08:37:12 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:37:22 000001M|001/06/0/000|=5:2102:R0=T2 access back to normal
26/06/15 08:37:22 000001M|001/06/0/000|=5:0311=T2 Dlap Established
26/06/15 08:37:23 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:37:23 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:37:42 000001M|001/06/-/---|=5:2019=PRA coupler commissioning
26/06/15 08:37:47 000001M|003/04/-/---|=2:2457=Z coupler (3,4) not initalized yet
26/06/15 08:37:47 000001M|003/05/-/---|=2:2457=Z coupler (3,5) not initalized yet
26/06/15 08:37:58 000001M|004/03/-/---|=2:2457=Z coupler (4,3) not initalized yet
26/06/15 08:37:58 000001M|004/04/-/---|=2:2457=PCM coupler (4,4) not initalized yet
26/06/15 08:37:58 000001M|004/05/-/---|=2:2457=Z coupler (4,5) not initalized yet
26/06/15 08:37:58 000001M|004/06/-/---|=2:2457=NDDI coupler (4,6) not initalized yet
26/06/15 08:37:59 000001M|001/02/-/---|=2:2457=UA coupler (1,2) not initalized yet
26/06/15 08:38:16 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:24 000001M|001/27/-/---|=3:3541=Illegal term number
26/06/15 08:38:29 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:30 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:30 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:32 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:32 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:34 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:35 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:35 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:36 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:36 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:36 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:37 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:37 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:37 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:37 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:38 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:38 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:40 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:38:40 000001M|---/--/-/---|=5:2141=TRUNK resources quantity normal
26/06/15 08:38:53 000001M|---/--/-/---|=0:1609=112 incidents sent by coupler (1, 7)
26/06/15 08:38:54 000001M|---/--/-/---|=0:1609=138 incidents sent by coupler (2, 6)
26/06/15 08:39:04 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
26/06/15 08:39:13 000001M|001/00/0/254|=2:0379:R0=Inter ACT link HS: 23,(19,1),10.29.128.27,00:80:9f:35:c5:3e
26/06/15 08:39:13 000001M|001/--/-/---|=2:2043=Loss of the 1 CRYSTAL
26/06/15 08:39:13 000001M|001/00/-/---|=2:2042:R0=Loss of a GD/GD3 type cpl
26/06/15 08:39:13 000001M|001/04/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:39:13 000001M|001/05/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:39:13 000001M|001/06/-/---|=2:2042:R0=Loss of a PRA type cpl
26/06/15 08:39:13 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
26/06/15 08:39:13 000001M|001/07/-/---|=2:2042:R0=Loss of a PCM type cpl
26/06/15 08:39:13 000001M|003/--/-/---|=2:2043=Loss of the 3 CRYSTAL
26/06/15 08:39:13 000001M|004/--/-/---|=2:2043=Loss of the 4 CRYSTAL
26/06/15 08:39:13 000001M|001/27/-/---|=3:2490=Loss of a virtual coupler GPA (1,27) of the associated coupler GD/GD3 (1,0)
26/06/15 08:39:13 000001M|003/00/-/---|=3:2490=Loss of a virtual coupler GPA (3,0) of the associated coupler MEX (3,0)
26/06/15 08:39:14 000001M|003/01/-/---|=2:2042:R0=Loss of a UA type cpl
26/06/15 08:39:14 000001M|003/02/-/---|=2:2042:R0=Loss of a MIX type cpl
26/06/15 08:39:14 000001M|003/03/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:39:14 000001M|003/06/-/---|=2:2042:R0=Loss of a NDDI type cpl
26/06/15 08:39:14 000001M|003/07/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:39:14 000001M|003/08/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:39:14 000001M|003/02/-/---|=3:2490=Loss of a virtual coupler UA (3,9) of the associated coupler MIX (3,2)
26/06/15 08:39:14 000001M|003/02/-/---|=3:2490=Loss of a virtual coupler Z (3,10) of the associated coupler MIX (3,2)
26/06/15 08:39:14 000001M|004/00/-/---|=3:2490=Loss of a virtual coupler GPA (4,0) of the associated coupler MEX (4,0)
26/06/15 08:39:14 000001M|004/01/-/---|=2:2042:R0=Loss of a UA type cpl
26/06/15 08:39:14 000001M|004/02/-/---|=2:2042:R0=Loss of a UA type cpl
26/06/15 08:39:14 000001M|004/07/-/---|=2:2042:R0=Loss of a NDDI type cpl
26/06/15 08:39:14 000001M|004/08/-/---|=2:2042:R0=Loss of a Z type cpl
26/06/15 08:42:47 000001M|001/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 16


GD/GA/INTIP/RGD: reason of reboot 16---- this is 16 : Not enough buffer descriptor.

what does it mean Not enough buffer descriptor??.


Thanks.

8crespo8
Member
Posts: 11
Joined: 29 Dec 2015 10:58

Re: GD3 reboot

Post by 8crespo8 » 15 Aug 2017 17:30

Hello everyone,

I have a problem with my GD3 / GA - 3 cards, they are constantly restarting, according to the logs the reasons for the reboots is 13 I could someone please help me with this problem.
Image

Thank you.

User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4023
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: GD3 reboot

Post by tot3nkopf » 16 Aug 2017 06:18

You can use incinfo and incident number (e.g.: incinfo GEA 5857) to find more details about reason.

13 is either power off by pressing the power button or by rstcpl command.

8crespo8
Member
Posts: 11
Joined: 29 Dec 2015 10:58

Re: GD3 reboot

Post by 8crespo8 » 16 Aug 2017 10:06

thanks for answering,

If the incinfo command had already seen it and for what reason says 13 is not my situation since none of these actions have been done, is there any way to further review this problem of reboots?

Thank you again.

User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4023
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: GD3 reboot

Post by tot3nkopf » 16 Aug 2017 10:42

In my experience the reasons are quite accurate.

8crespo8
Member
Posts: 11
Joined: 29 Dec 2015 10:58

Re: GD3 reboot

Post by 8crespo8 » 16 Aug 2017 11:27

Sorry for adding that these restarts started from the time the GD & GA-2 cards were upgraded to GD3 & GA-3

HUSSAINQCS
Member
Posts: 290
Joined: 21 Jan 2017 02:57

Re: GD3 reboot

Post by HUSSAINQCS » 16 Aug 2017 14:59

can you see that in GD3 console what you are getting?

Whether its trying to reach the call server

8crespo8
Member
Posts: 11
Joined: 29 Dec 2015 10:58

Re: GD3 reboot

Post by 8crespo8 » 22 Aug 2017 18:16

I also have this problem.

Reason of reboot 21

Any solution to this problem?

User avatar
giovanni.attolini
Member
Posts: 271
Joined: 16 Apr 2009 13:44
Location: Veranopolis-RS-BRAZIL
Contact:

Re: GD3 reboot

Post by giovanni.attolini » 18 Sep 2017 08:49

I have not sure but seems that GD3 is not able to download one binary file from CS.

Maybe unstable link or a fail in CS TFTP server.
Giovanni A. Attolini
https://www.facebook.com/gio.atto

"When you make a stupid question, wait for a stupid answer!"

Post Reply

Return to “Media Gateway”