5857=GD/GA/INTIP/RGD: reason of reboot 21

[hunggundam]

Hi All,

What is meaning about incident 5857 reboot =21? How to fixed it?
INCIDENT NUMBER: 5857
Network indicator: Alcatel 4400
OBJECT CLASS: Dhs3Board
EVENT TYPE: ProcessingErrorAlarm (10)
PROBABLE CAUSE: Unknown (0)
SEVERITY: Indeterminate

"GD/GA/INTIP/RGD: reason of reboot P1"
"P1 Error state"
"P1 :"
"GD/GA code :"
"- 21 : Reset on startemg file not received and no backup mode"

Thanks

[hunggundam]

incvisu
13/05/15 09:34:45
13/05/15 09:35:04 000002I|---/--/-/---|=4:2199=A4400 Version : R10.1.1-j2.603-25-a-hk-c80s1
13/05/15 09:35:11 000002I|---/--/-/---|=2:1006=DPNSS Prefix Missing, No DPNSS prefix added.
13/05/15 09:36:16 000002I|---/--/-/---|=2:2176=A dynamic patch has been installed for TEL
13/05/15 09:37:07 000002M|---/--/-/---|=5:2009=Initialisation CPU role MAIN
13/05/15 09:37:07 000002M|---/--/-/---|=5:2019=Z coupler commissioning
13/05/15 09:37:07 000002M|---/--/-/---|=5:1367=DECT network initialization
13/05/15 09:37:07 000002M|---/--/-/---|=5:5904=Remote extension network initialization
13/05/15 09:37:07 000002M|---/--/-/---|=4:0425=PRS related activity : Interface handler started
13/05/15 09:37:07 000002M|019/01/-/---|=5:2019=INTIPA coupler commissioning
13/05/15 09:37:51 000002M|018/00/-/---|=5:0409=The inter-ACT link over IP from (19 1) is up
13/05/15 09:37:56 000002M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 10 22
13/05/15 09:38:21 000002M|018/00/-/---|=5:2019=GD/GD3 coupler commissioning
13/05/15 09:38:21 000002M|018/01/-/---|=5:2019=4645 coupler commissioning
13/05/15 09:38:26 000002M|---/--/-/---|=2:5410=4645 The download of the /DHS3ext/vgeva/evavg.EN0 (A) language file failed.
13/05/15 09:38:26 000002M|---/--/-/---|=2:5410=4645 The download of the /DHS3ext/vgeva/evavg.CA0 (A) language file failed.
13/05/15 09:38:26 000002M|---/--/-/---|=2:5410=4645 The download of the /DHS3ext/vgeva/evavg.CN0 (A) language file failed.
13/05/15 09:38:28 000002M|---/--/-/---|=5:0903=VOCAL FACILITY starting link
13/05/15 09:41:03 000002M|000/06/-/---|=5:2169=Main CPU initialization completed
13/05/15 10:19:32 000002M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 10 2
13/05/15 10:52:37 000002M|001/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.36.c8.2a (binmg)
13/05/15 10:52:37 000002M|001/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.36.c8.2a (binmg)
13/05/15 10:52:46 000002M|019/00/0/000|=5:2862=PH:Hybrid Access (1 1 Main) is up
13/05/15 10:52:46 000002M|019/00/0/000|=3:2866=PH:Estab Req for PLL 0 on Hybrid Access (1 1 Main)
13/05/15 10:52:46 000002M|019/00/0/000|=5:2864=PH:PLL 0 is up on Hybrid Access (1 1 Main)
13/05/15 10:53:00 000002M|1-2 |=5:2827=PH:Local link [2 1] is up
13/05/15 10:53:00 000002M|---/--/-/---|=5:2846=PH:Node 1 is reachable
13/05/15 10:53:01 000002M|001/00/-/---|=5:0409=The inter-ACT link over IP from (19 1) is up
13/05/15 10:53:02 000002M|001/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 21
13/05/15 10:53:07 000002M|001/01/-/---|=3:0747=Config error or Loss of IP connection: 4,(1,1),192.168.45.52,00:80:9f:73:13:f8
13/05/15 10:53:12 000002M|---/--/-/---|=5:2141=TRUNK resources quantity normal
13/05/15 10:53:13 000002M|001/05/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:13 000002M|001/07/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:14 000002M|001/05/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:14 000002M|001/07/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:15 000002M|001/05/0/002|=5:2053=Terminal 2 in service
13/05/15 10:53:15 000002M|001/03/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:15 000002M|001/04/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:15 000002M|001/07/0/002|=5:2053=Terminal 2 in service
13/05/15 10:53:15 000002M|001/02/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:16 000002M|001/07/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:16 000002M|001/02/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:16 000002M|001/03/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:16 000002M|001/04/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:17 000002M|001/05/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:17 000002M|001/02/0/002|=5:2053=Terminal 2 in service
13/05/15 10:53:17 000002M|001/03/0/002|=5:2053=Terminal 2 in service
13/05/15 10:53:17 000002M|001/07/0/004|=5:2053=Terminal 4 in service
13/05/15 10:53:17 000002M|001/04/0/002|=5:2053=Terminal 2 in service
13/05/15 10:53:18 000002M|001/05/0/004|=5:2053=Terminal 4 in service
13/05/15 10:53:18 000002M|001/05/0/005|=5:2053=Terminal 5 in service
13/05/15 10:53:18 000002M|001/02/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:18 000002M|001/01/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.73.13.f8 (binmg)
13/05/15 10:53:18 000002M|001/01/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.73.13.f8 (binmg)
13/05/15 10:53:18 000002M|001/03/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:18 000002M|001/07/0/005|=5:2053=Terminal 5 in service
13/05/15 10:53:18 000002M|001/04/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:19 000002M|001/05/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:19 000002M|001/02/0/004|=5:2053=Terminal 4 in service
13/05/15 10:53:19 000002M|001/07/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:19 000002M|001/03/0/004|=5:2053=Terminal 4 in service
13/05/15 10:53:19 000002M|001/04/0/004|=5:2053=Terminal 4 in service
13/05/15 10:53:20 000002M|001/05/0/007|=5:2053=Terminal 7 in service
13/05/15 10:53:20 000002M|001/02/0/005|=5:2053=Terminal 5 in service
13/05/15 10:53:20 000002M|001/01/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.73.13.f8 (binmg)
13/05/15 10:53:20 000002M|001/01/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.73.13.f8 (binmg)
13/05/15 10:53:20 000002M|001/03/0/005|=5:2053=Terminal 5 in service
13/05/15 10:53:20 000002M|001/07/0/007|=5:2053=Terminal 7 in service
13/05/15 10:53:20 000002M|001/04/0/005|=5:2053=Terminal 5 in service
13/05/15 10:53:21 000002M|001/02/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:21 000002M|001/03/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:21 000002M|001/04/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:22 000002M|001/02/0/007|=5:2053=Terminal 7 in service
13/05/15 10:53:22 000002M|001/03/0/007|=5:2053=Terminal 7 in service
13/05/15 10:53:22 000002M|001/00/0/000|=5:2102=T2 access back to normal
13/05/15 10:53:22 000002M|001/00/0/000|=4:2113=T2 lapD not established still trying
13/05/15 10:53:22 000002M|001/04/0/007|=5:2053=Terminal 7 in service
13/05/15 10:53:22 000002M|001/00/0/000|=5:5974=IP Dlap Established
13/05/15 10:53:22 000002M|001/00/0/000|=5:2836=PH:Access (1 0 0) is up
13/05/15 10:53:23 000002M|001/02/0/008|=5:2053=Terminal 8 in service
13/05/15 10:53:23 000002M|001/04/0/008|=5:2053=Terminal 8 in service
13/05/15 10:53:24 000002M|001/03/0/008|=5:2053=Terminal 8 in service
13/05/15 10:53:24 000002M|001/02/0/009|=5:2053=Terminal 9 in service
13/05/15 10:53:24 000002M|001/04/0/009|=5:2053=Terminal 9 in service
13/05/15 10:53:25 000002M|001/03/0/009|=5:2053=Terminal 9 in service
13/05/15 10:53:25 000002M|001/03/0/010|=5:2053=Terminal 10 in service
13/05/15 10:53:25 000002M|001/02/0/010|=5:2053=Terminal 10 in service
13/05/15 10:53:26 000002M|001/04/0/010|=5:2053=Terminal 10 in service
13/05/15 10:53:26 000002M|001/02/0/011|=5:2053=Terminal 11 in service
13/05/15 10:53:26 000002M|001/04/0/011|=5:2053=Terminal 11 in service
13/05/15 10:53:27 000002M|001/03/0/011|=5:2053=Terminal 11 in service
13/05/15 10:53:27 000002M|001/02/0/012|=5:2053=Terminal 12 in service
13/05/15 10:53:27 000002M|001/03/0/012|=5:2053=Terminal 12 in service
13/05/15 10:53:27 000002M|001/04/0/012|=5:2053=Terminal 12 in service
13/05/15 10:53:28 000002M|001/02/0/013|=5:2053=Terminal 13 in service
13/05/15 10:53:28 000002M|001/04/0/013|=5:2053=Terminal 13 in service
13/05/15 10:53:29 000002M|001/03/0/013|=5:2053=Terminal 13 in service
13/05/15 10:53:29 000002M|001/03/0/014|=5:2053=Terminal 14 in service
13/05/15 10:53:30 000002M|001/04/0/014|=5:2053=Terminal 14 in service
13/05/15 10:53:30 000002M|001/02/0/014|=5:2053=Terminal 14 in service
13/05/15 10:53:30 000002M|001/02/0/015|=5:2053=Terminal 15 in service
13/05/15 10:53:30 000002M|001/03/0/015|=5:2053=Terminal 15 in service
13/05/15 10:53:31 000002M|001/04/0/015|=5:2053=Terminal 15 in service
13/05/15 10:53:31 000002M|003/01/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:31 000002M|003/02/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:31 000002M|003/04/0/000|=5:2053=Terminal 0 in service
13/05/15 10:53:31 000002M|001/00/-/---|=5:2019=GD/GD3 coupler commissioning
13/05/15 10:53:32 000002M|003/01/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:32 000002M|003/02/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:32 000002M|003/04/0/001|=5:2053=Terminal 1 in service
13/05/15 10:53:32 000002M|003/01/0/002|=5:2053=Terminal 2 in service
13/05/15 10:53:33 000002M|003/02/0/002|=5:2053=Terminal 2 in service
13/05/15 10:53:33 000002M|---/--/-/---|=5:2141=SET resources quantity normal
13/05/15 10:53:34 000002M|003/01/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:34 000002M|003/02/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:34 000002M|003/04/0/003|=5:2053=Terminal 3 in service
13/05/15 10:53:35 000002M|003/01/0/004|=5:2053=Terminal 4 in service
13/05/15 10:53:35 000002M|003/01/0/005|=5:2053=Terminal 5 in service
13/05/15 10:53:36 000002M|003/02/0/005|=5:2053=Terminal 5 in service
13/05/15 10:53:36 000002M|---/--/-/---|=3:1125=external alarm : "mtcl login"
13/05/15 10:53:37 000002M|003/02/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:37 000002M|003/01/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:37 000002M|003/04/0/006|=5:2053=Terminal 6 in service
13/05/15 10:53:38 000002M|003/02/0/007|=5:2053=Terminal 7 in service
13/05/15 10:53:38 000002M|003/01/0/007|=5:2053=Terminal 7 in service
13/05/15 10:53:39 000002M|003/02/0/008|=5:2053=Terminal 8 in service
13/05/15 10:53:41 000002M|003/01/0/009|=5:2053=Terminal 9 in service
13/05/15 10:53:42 000002M|003/01/0/010|=5:2053=Terminal 10 in service
13/05/15 10:53:42 000002M|003/02/0/011|=5:2053=Terminal 11 in service
13/05/15 10:53:43 000002M|003/02/0/012|=5:2053=Terminal 12 in service
13/05/15 10:53:43 000002M|003/01/0/011|=5:2053=Terminal 11 in service
13/05/15 10:53:44 000002M|003/02/0/013|=5:2053=Terminal 13 in service
13/05/15 10:53:44 000002M|001/06/-/---|=5:2019=NDDI coupler commissioning
13/05/15 10:53:45 000002M|003/01/0/013|=5:2053=Terminal 13 in service
13/05/15 10:53:45 000002M|003/01/0/012|=5:2053=Terminal 12 in service
13/05/15 10:53:46 000002M|001/01/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 13
13/05/15 10:53:47 000002M|003/01/0/015|=5:2053=Terminal 15 in service
13/05/15 10:53:47 000002M|001/27/-/---|=4:2491=GPA(1,27) virtual coupler commissioning of the associated coupler GD/GD3(1,0)
13/05/15 10:53:47 000002M|001/00/0/000|=2:5973=IP Dlap Released
13/05/15 10:53:47 000002M|001/00/0/000|=4:2113=T2 lapD not established still trying
13/05/15 10:53:47 000002M|001/00/0/000|=3:2825=PH:Access (1 0 0) goes down
13/05/15 10:53:47 000002M|001/05/-/---|=5:2019=UA coupler commissioning
13/05/15 10:53:48 000002M|001/07/-/---|=5:2019=UA coupler commissioning
13/05/15 10:53:50 000002M|003/00/-/---|=4:2491=GPA(3,0) virtual coupler commissioning of the associated coupler MEX(3,0)
13/05/15 10:53:57 000002M|001/02/-/---|=5:2019=UA coupler commissioning
13/05/15 10:53:58 000002M|001/03/-/---|=5:2019=UA coupler commissioning
13/05/15 10:53:58 000002M|001/04/-/---|=5:2019=UA coupler commissioning
13/05/15 10:54:02 000002M|001/00/0/000|=5:2102=T2 access back to normal
13/05/15 10:54:02 000002M|001/00/0/000|=4:2113=T2 lapD not established still trying
13/05/15 10:54:02 000002M|001/00/0/000|=5:5974=IP Dlap Established
13/05/15 10:54:02 000002M|001/00/0/000|=5:2836=PH:Access (1 0 0) is up