CS reset and boot problem

Post Reply
Mati

CS reset and boot problem

Post by Mati »

I have a problem with CS. Can someone help me?

I don't know why but sometimes the CS resets (allwais on friday evening). The problem is that in some cases does not start because it remains in a loop. When I connect to CS I see this:

TFTPLOAD STARTED using ip = 192.68.2.1 - Bootp Server - File Name
* RcvTO, TOIPRcv, TFTP_Time_out on No: 0001
ICMP: type 03, code 03
TFTP server not ready try later!

TFTPLOAD STARTED using ip = 192.68.2.1 - Bootp Server - File Name
* RcvTO, TOIPRcv, TFTP_Time_out on No: 0001
ICMP: type 03, code 03
TFTP server not ready try later!

The IP 192.168.2.1 is a router, but not even this in the PBX network. Since CS is 192.168.1.18/24

The OXE is in the realease 5.1.2al

There may be something online that pull the PBX? (Too much traffic on the network)
Why does it sometimes seems that that the CS boots into boot mode network?
Top
Mr T

Post by Mr T »

when logged into the console port do you see any IRQ errors?
Top
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3852
Joined: 23 Sep 2004 06:47

Post by vad »

Check "incvisu -1" (-2 ..) - what was before restart.
Do you use f.e. dynamic routing (netadmin -m)?
Top
Mati

Post by Mati »

I've static IP addesses,


This are the incvisu -1 -2 -3
incvisu -1
29/10/10 15:52:06
29/10/10 15:52:27 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 0
29/10/10 15:52:27 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 1
29/10/10 15:52:27 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 2
29/10/10 15:52:28 000001I|--/--/-/---|=4:2199=A4400 Version : R5.1.2-e2.504-1-al
-es-c80s1
29/10/10 15:52:30 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ENTITY cause 0 info -1 -1 -1
29/10/10 15:53:22 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed
for TEL
29/10/10 15:53:22 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed
for TEL
29/10/10 15:53:48 000001M|--/--/-/---|=2:2176x031=A dynamic patch has been insta
lled for TEL
29/10/10 15:53:48 000001M|--/--/-/---|=5:2009=Initialisation CPU role MAIN
29/10/10 15:53:48 000001M|--/--/-/---|=5:2019=Z coupler commissioning
29/10/10 15:53:48 000001M|--/--/-/---|=5:2019=UA_FICTIF coupler commissioning
29/10/10 15:53:48 000001M|--/--/-/---|=5:1367=DECT network initialization
29/10/10 15:53:48 000001M|--/--/-/---|=5:5904=Remote extension network initializ
ation
29/10/10 15:53:49 000001M|19/01/-/---|=5:2019=INTIPA coupler commissioning
29/10/10 15:56:50 000001M|00/06/-/---|=5:2169=Main CPU initialization completed
29/10/10 15:58:40 000001M|01/00/-/---|=4:0740=Beginning of an INT/IP downloading
@:00.80.9f.32.f8.8d (binmg)
29/10/10 15:58:40 000001M|01/00/-/---|=5:0741=End of downloading of an INT/IP bo
ard @:00.80.9f.32.f8.8d (binmg)
29/10/10 15:58:56 000001M|01/00/-/---|=4:0740=Beginning of an INT/IP downloading
@:00.80.9f.32.f8.8d (binmcv_ver)
29/10/10 15:58:57 000001M|01/00/-/---|=5:0741=End of downloading of an INT/IP bo
ard @:00.80.9f.32.f8.8d (binmcv_ver)
29/10/10 16:00:11 000001M|01/00/-/---|=5:0409=The inter-ACT link over IP from (1
9 1) is up
29/10/10 16:00:12 000001M|01/00/-/---|=3:4421= MCV24 registered, but 0 plugged
29/10/10 16:00:12 000001M|01/00/-/---|=0:5857=GD/GA/INTIP/RGD : reason of reboot
21
29/10/10 16:00:13 000001M|01/00/-/---|=0:4402=Compression state 8 (10-13 INFO, o
ther ERROR); daughter board 1,DSP 1"
29/10/10 16:00:14 000001M|01/27/-/---|=4:2597=Registered board but not physicall
y there
29/10/10 16:00:17 000001M|--/--/-/---|=4:2500=Dow: file /DHS3ext/vgadpcm/flash/s
td/vgadpcm.DE0 opening error
29/10/10 16:00:17 000001M|--/--/-/---|=4:2500=Dow: file /DHS3ext/vgadpcm/flash/s
td/vgadpcm.EN0 opening error
29/10/10 16:00:17 000001M|--/--/-/---|=5:2141=SET resources quantity normal
29/10/10 16:00:22 000001M|01/27/-/---|=4:0260=Beginning of downloading 90_0090
29/10/10 16:00:26 000001M|01/02/0/000|=5:2053=Terminal 0 in service
29/10/10 16:00:27 000001M|01/02/0/001|=5:2053=Terminal 1 in service
29/10/10 16:00:27 000001M|01/27/-/---|=5:0261=End of downloading 90_0090
29/10/10 16:00:28 000001M|01/02/0/002|=5:2053=Terminal 2 in service
29/10/10 16:00:29 000001M|01/02/0/003|=5:2053=Terminal 3 in service
29/10/10 16:00:30 000001M|01/02/0/004|=5:2053=Terminal 4 in service
29/10/10 16:00:31 000001M|01/02/0/005|=5:2053=Terminal 5 in service
29/10/10 16:00:32 000001M|01/02/0/006|=5:2053=Terminal 6 in service
29/10/10 16:00:34 000001M|01/02/0/008|=5:2053=Terminal 8 in service
29/10/10 16:00:35 000001M|01/02/0/009|=5:2053=Terminal 9 in service
29/10/10 16:00:36 000001M|01/02/0/010|=5:2053=Terminal 10 in service
29/10/10 16:00:37 000001M|01/02/0/011|=5:2053=Terminal 11 in service
29/10/10 16:00:38 000001M|01/02/0/012|=5:2053=Terminal 12 in service
29/10/10 16:00:39 000001M|01/02/0/013|=5:2053=Terminal 13 in service
29/10/10 16:00:41 000001M|01/02/0/015|=5:2053=Terminal 15 in service
29/10/10 16:00:42 000001M|01/00/-/---|=5:2019=GD coupler commissioning
29/10/10 16:00:57 000001M|01/27/-/---|=4:2491=GPA(1,27) virtual coupler commissi
oning of the associated coupler GD(1,0)
29/10/10 16:01:00 000001M|01/03/-/---|=5:2019=Z coupler commissioning
29/10/10 16:01:00 000001M|01/04/-/---|=5:2019=Z coupler commissioning
29/10/10 16:01:00 000001M|01/05/-/---|=5:2019=Z coupler commissioning
29/10/10 16:01:05 000001M|01/02/-/---|=5:2019=UA coupler commissioning
29/10/10 16:01:46 000001M|--/--/-/---|=5:2141=TRUNK resources quantity normal
29/10/10 16:02:14 000001M|01/06/-/---|=5:2019=BRA coupler commissioning
29/10/10 16:03:16 000001M|--/--/-/---|=2:2081=IO1 in free running and synchro bo
ard activated
29/10/10 16:04:46 000001M|--/--/-/---|=2:2081=IO1 in free running and synchro bo
ard activated
29/10/10 16:06:16 000001M|--/--/-/---|=2:2088=Bad clock synchro state (MIXED)




incvisu -2
25/10/10 23:04:30
25/10/10 23:04:50 000001I|--/--/-/---|=4:2199=A4400 Version : R5.1.2-e2.504-1-al
-es-c80s1
25/10/10 23:04:50 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 0
25/10/10 23:04:50 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 1
25/10/10 23:04:50 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 2
25/10/10 23:04:53 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ENTITY cause 0 info -1 -1 -1
25/10/10 23:05:45 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed
for TEL
25/10/10 23:06:12 000001M|--/--/-/---|=2:2176x032=A dynamic patch has been insta
lled for TEL
25/10/10 23:06:12 000001M|--/--/-/---|=5:2009=Initialisation CPU role MAIN
25/10/10 23:06:12 000001M|--/--/-/---|=5:2019=Z coupler commissioning
25/10/10 23:06:12 000001M|--/--/-/---|=5:2019=UA_FICTIF coupler commissioning
25/10/10 23:06:12 000001M|--/--/-/---|=5:1367=DECT network initialization
25/10/10 23:06:12 000001M|--/--/-/---|=5:5904=Remote extension network initializ
ation
25/10/10 23:06:12 000001M|19/01/-/---|=5:2019=INTIPA coupler commissioning
25/10/10 23:09:13 000001M|00/06/-/---|=5:2169=Main CPU initialization completed
25/10/10 23:11:12 000001M|01/00/-/---|=4:0740=Beginning of an INT/IP downloading
@:00.80.9f.32.f8.8d (binmg)
25/10/10 23:11:12 000001M|01/00/-/---|=5:0741=End of downloading of an INT/IP bo
ard @:00.80.9f.32.f8.8d (binmg)
25/10/10 23:11:28 000001M|01/00/-/---|=4:0740=Beginning of an INT/IP downloading
@:00.80.9f.32.f8.8d (binmcv_ver)
25/10/10 23:11:29 000001M|01/00/-/---|=5:0741=End of downloading of an INT/IP bo
ard @:00.80.9f.32.f8.8d (binmcv_ver)
25/10/10 23:11:35 000001M|01/00/-/---|=5:0409=The inter-ACT link over IP from (1
9 1) is up
25/10/10 23:11:36 000001M|01/00/-/---|=3:4421= MCV24 registered, but 0 plugged
25/10/10 23:11:37 000001M|01/00/-/---|=0:5857=GD/GA/INTIP/RGD : reason of reboot
21
25/10/10 23:11:38 000001M|01/00/-/---|=0:4402=Compression state 8 (10-13 INFO, o
ther ERROR); daughter board 1,DSP 1"
25/10/10 23:11:38 000001M|01/27/-/---|=4:2597=Registered board but not physicall
y there
25/10/10 23:11:46 000001M|--/--/-/---|=5:2141=SET resources quantity normal
25/10/10 23:11:46 000001M|--/--/-/---|=4:2500=Dow: file /DHS3ext/vgadpcm/flash/s
td/vgadpcm.DE0 opening error
25/10/10 23:11:46 000001M|--/--/-/---|=4:2500=Dow: file /DHS3ext/vgadpcm/flash/s
td/vgadpcm.EN0 opening error
25/10/10 23:11:51 000001M|01/02/0/000|=5:2053=Terminal 0 in service
25/10/10 23:11:51 000001M|01/27/-/---|=4:0260=Beginning of downloading 90_0090
25/10/10 23:11:52 000001M|01/02/0/001|=5:2053=Terminal 1 in service
25/10/10 23:11:54 000001M|01/02/0/002|=5:2053=Terminal 2 in service
25/10/10 23:11:54 000001M|01/02/0/003|=5:2053=Terminal 3 in service
25/10/10 23:11:54 000001M|01/02/0/004|=5:2053=Terminal 4 in service
25/10/10 23:11:55 000001M|01/02/0/005|=5:2053=Terminal 5 in service
25/10/10 23:11:56 000001M|01/02/0/006|=5:2053=Terminal 6 in service
25/10/10 23:11:56 000001M|01/27/-/---|=5:0261=End of downloading 90_0090
25/10/10 23:11:58 000001M|01/02/0/008|=5:2053=Terminal 8 in service
25/10/10 23:11:59 000001M|01/02/0/009|=5:2053=Terminal 9 in service
25/10/10 23:12:00 000001M|01/02/0/010|=5:2053=Terminal 10 in service
25/10/10 23:12:01 000001M|01/02/0/011|=5:2053=Terminal 11 in service
25/10/10 23:12:02 000001M|01/02/0/012|=5:2053=Terminal 12 in service
25/10/10 23:12:03 000001M|01/02/0/013|=5:2053=Terminal 13 in service
25/10/10 23:12:06 000001M|01/02/0/015|=5:2053=Terminal 15 in service
25/10/10 23:12:06 000001M|01/00/-/---|=5:2019=GD coupler commissioning
25/10/10 23:12:26 000001M|01/27/-/---|=4:2491=GPA(1,27) virtual coupler commissi
oning of the associated coupler GD(1,0)
25/10/10 23:12:29 000001M|01/04/-/---|=5:2019=Z coupler commissioning
25/10/10 23:12:29 000001M|01/05/-/---|=5:2019=Z coupler commissioning
25/10/10 23:12:29 000001M|01/03/-/---|=5:2019=Z coupler commissioning
25/10/10 23:12:30 000001M|01/02/-/---|=5:2019=UA coupler commissioning
25/10/10 23:13:15 000001M|--/--/-/---|=5:2141=TRUNK resources quantity normal
25/10/10 23:13:43 000001M|01/06/-/---|=5:2019=BRA coupler commissioning
25/10/10 23:14:45 000001M|--/--/-/---|=2:2081=IO1 in free running and synchro bo
ard activated
25/10/10 23:16:15 000001M|--/--/-/---|=2:2081=IO1 in free running and synchro bo
ard activated
25/10/10 23:17:45 000001M|--/--/-/---|=2:2088=Bad clock synchro state (MIXED)
28/10/10 10:09:15 000001M|01/02/0/004|=5:2053=Terminal 4 in service
incvisu -3
20/10/10 09:16:39
20/10/10 09:17:00 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 0
20/10/10 09:17:00 000001I|--/--/-/---|=4:2199=A4400 Version : R5.1.2-e2.504-1-al
-es-c80s1
20/10/10 09:17:00 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 1
20/10/10 09:17:00 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ACCES cause Synch. prior. < 200 info 1 6 2
20/10/10 09:17:02 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM tab
le ENTITY cause 0 info -1 -1 -1
20/10/10 09:17:56 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed
for TEL
20/10/10 09:18:21 000001M|--/--/-/---|=2:2176x032=A dynamic patch has been insta
lled for TEL
20/10/10 09:18:21 000001M|--/--/-/---|=5:2009=Initialisation CPU role MAIN
20/10/10 09:18:21 000001M|--/--/-/---|=5:2019=Z coupler commissioning
20/10/10 09:18:22 000001M|--/--/-/---|=5:2019=UA_FICTIF coupler commissioning
20/10/10 09:18:22 000001M|--/--/-/---|=5:1367=DECT network initialization
20/10/10 09:18:22 000001M|--/--/-/---|=5:5904=Remote extension network initializ
ation
20/10/10 09:18:22 000001M|19/01/-/---|=5:2019=INTIPA coupler commissioning
20/10/10 09:21:22 000001M|00/06/-/---|=5:2169=Main CPU initialization completed
20/10/10 09:22:31 000001M|01/00/-/---|=4:0740=Beginning of an INT/IP downloading
@:00.80.9f.32.f8.8d (binmg)
20/10/10 09:22:31 000001M|01/00/-/---|=5:0741=End of downloading of an INT/IP bo
ard @:00.80.9f.32.f8.8d (binmg)
20/10/10 09:22:47 000001M|01/00/-/---|=4:0740=Beginning of an INT/IP downloading
@:00.80.9f.32.f8.8d (binmcv_ver)
20/10/10 09:22:48 000001M|01/00/-/---|=5:0741=End of downloading of an INT/IP bo
ard @:00.80.9f.32.f8.8d (binmcv_ver)
20/10/10 09:22:55 000001M|01/00/-/---|=5:0409=The inter-ACT link over IP from (1
9 1) is up
20/10/10 09:22:56 000001M|01/00/-/---|=3:4421= MCV24 registered, but 0 plugged
20/10/10 09:22:56 000001M|01/00/-/---|=0:5857=GD/GA/INTIP/RGD : reason of reboot
21
20/10/10 09:22:57 000001M|01/00/-/---|=0:4402=Compression state 8 (10-13 INFO, o
ther ERROR); daughter board 1,DSP 1"
20/10/10 09:22:58 000001M|01/27/-/---|=4:2597=Registered board but not physicall
y there
20/10/10 09:23:07 000001M|--/--/-/---|=5:2141=SET resources quantity normal
20/10/10 09:23:07 000001M|--/--/-/---|=4:2500=Dow: file /DHS3ext/vgadpcm/flash/s
td/vgadpcm.DE0 opening error
20/10/10 09:23:07 000001M|--/--/-/---|=4:2500=Dow: file /DHS3ext/vgadpcm/flash/s
td/vgadpcm.EN0 opening error
20/10/10 09:23:11 000001M|01/02/0/000|=5:2053=Terminal 0 in service
20/10/10 09:23:12 000001M|01/27/-/---|=4:0260=Beginning of downloading 90_0090
20/10/10 09:23:12 000001M|01/02/0/001|=5:2053=Terminal 1 in service
20/10/10 09:23:14 000001M|01/02/0/003|=5:2053=Terminal 3 in service
20/10/10 09:23:15 000001M|01/02/0/004|=5:2053=Terminal 4 in service
20/10/10 09:23:16 000001M|01/02/0/005|=5:2053=Terminal 5 in service
20/10/10 09:23:17 000001M|01/02/0/006|=5:2053=Terminal 6 in service
20/10/10 09:23:17 000001M|01/27/-/---|=5:0261=End of downloading 90_0090
20/10/10 09:23:19 000001M|01/02/0/008|=5:2053=Terminal 8 in service
20/10/10 09:23:20 000001M|01/02/0/009|=5:2053=Terminal 9 in service
20/10/10 09:23:21 000001M|01/02/0/010|=5:2053=Terminal 10 in service
20/10/10 09:23:22 000001M|01/02/0/011|=5:2053=Terminal 11 in service
20/10/10 09:23:23 000001M|01/02/0/012|=5:2053=Terminal 12 in service
20/10/10 09:23:24 000001M|01/02/0/013|=5:2053=Terminal 13 in service
20/10/10 09:23:26 000001M|01/00/-/---|=5:2019=GD coupler commissioning
20/10/10 09:23:26 000001M|01/02/0/015|=5:2053=Terminal 15 in service
20/10/10 09:23:47 000001M|01/27/-/---|=4:2491=GPA(1,27) virtual coupler commissi
oning of the associated coupler GD(1,0)
20/10/10 09:23:50 000001M|01/04/-/---|=5:2019=Z coupler commissioning
20/10/10 09:23:50 000001M|01/05/-/---|=5:2019=Z coupler commissioning
20/10/10 09:23:50 000001M|01/03/-/---|=5:2019=Z coupler commissioning
20/10/10 09:23:51 000001M|01/02/-/---|=5:2019=UA coupler commissioning
20/10/10 09:24:36 000001M|--/--/-/---|=5:2141=TRUNK resources quantity normal
20/10/10 09:25:03 000001M|01/06/-/---|=5:2019=BRA coupler commissioning
20/10/10 09:26:06 000001M|--/--/-/---|=2:2081=IO1 in free running and synchro bo
ard activated
20/10/10 09:27:36 000001M|--/--/-/---|=2:2081=IO1 in free running and synchro bo
ard activated
Top
User avatar
murraya
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 900
Joined: 16 Oct 2007 02:35

Post by murraya »

Hi Mati, first thing I would look at is possible harddrive failing. check the logs on the drive it may be that the system loops at the start as it can't read the drive. I would have thought that you would see other issues in incvisu but not always.
Best Regards
Murray

ACSE 10.0 corporate
ACSE 6.x IPT data
Top
Mati

Post by Mati »

Thank's murraya

Today the CPU fall down again, and like you said it was problem of the drive (it was completly broken). I like to think that it is only a disc problem, but it is strange that sometimes the drive goes well and suddenly fail causing a reset and not start again. It is also the second time in 5 months I change the HD ... I think the cs also have a problem, (but not sure)

I will report news.
Top
Mr T

Post by Mr T »

Or it could be the HDD adaptor on the CS. If I were you I would replace the entire CS along with the HDD.
Top
Mati

Post by Mati »

My nightmare....

I went yesterday to change the CS and HDD. I found another problem... the GD was blocked (not showing anything for V24, and no bootup). I triyed another GD and also failed. Try rebooting several times and the same... Finally changing the back-pannel and the power supply worked well, all GDs.

I joined the damaged back-pannel and the power supply in the office... seems to go right now :-(
Top
krzysioD

Post by krzysioD »

Just a hint:
you plug laptop (with v24 + terminal program) to the very same PDU as your PBX? you got good earthing? Seen that many times: V.24 cable not working on GD, and if plug into CS the CS suddenly crashes, all because of earthing / grounding problem with power. Maybe you should see if your MR3 has 36V batteries BOX and if it's working (after puling plug from PDU, power on GD goes orange well red+green it looks like orange) and CPU should receive some incident, and then it should slowly stop. In other words, CPU should issue a 'shutdown -h XXX' command.
Good power, use and train of batteries and earthing is very crude to good work of pbx system.
Also: R5.1Lx looks like some older install, maybe you should consider change of hdd,batteries (all of it, with Li CR2032 on CS,GD,GA...), fans etc every 3 years, it looks good for end-customer if you call and propose that...
Top
Post Reply

Return to “Media Gateway”