406 reboots 2.1.35

[auEric]

I have a 406 running 2.1.35 with DT and POTS modules attached. It has a PRI module and VCM20 fitted. When minor changes are made most of the time we just merge the config. From time to time the system will completely reboot, not related to any changes, all users get cut off from calls they are on. Any one seen this before? I don’t want to upgrade the firmware unless this is a known bug.
Thanks

 

[TheDoz]

Open your configuration with Wizard and see if you have any errors in your config. You can do this off line or on line.
Make sure User Names have no spaces or staring with numbers or # sign in the Name.

"A politician is a fellow who will lay down your life for his country.

 

[auEric]

Thanks, I did have a dot in a name, that is gone now. We have had spaces in names for over a year with out problems. I believe the config was edited by a later version of manager. This is from monitor.

********** Warning: TEXT Logging to File STOPPED on 26/8/2006 06:59:05 **********

0mS PRN: Monitor Started IP=10.0.0.114 IP 406 DS 2.1(35) lnkSydney
0mS PRN: LAW=A PRI=1, BRI=0, ALOG=4, ADSL=0 VCOMP=20, MDM=0, WAN=0, MODU=5 LANM=0 CkSRC=5 VMAIL=1(VER=2 TYP=1) CALLS=0(TOT=60)
3001mS PRN: +++ START OF ALARM LOG DUMP +++
3001mS PRN: ALARM: 16/09/2005 12:10:31 IP 406 DS 2.1(35) <Machine Check Exception> CRIT RAISED addr=8001001c d=0 pc=ff63d4a0 00000000 00000000 00000000 00000000 00000000
3001mS PRN: ALARM: 15/03/2006 09:53:59 IP 406 DS 2.1(35) <WATCHDOG> CRIT RAISED addr=00000000 d=0 pc=00000000 20003300 201002d4 ff510268 00000000 00000000
3001mS PRN: ALARM: 23/04/2006 11:39:11 IP 406 DS 2.1(35) <TLB Instruction Error> CRIT RAISED addr=ff27fd8e d=5 pc=00000000 ff63e68c ff5034e0 ff70a210 ff63e81c ff63ee34
3001mS PRN: ALARM: 11/05/2006 19:33:19 IP 406 DS 2.1(35) <TLB Data Error> CRIT RAISED addr=00000c54 d=5 pc=ff7092d4 ffd333e8 ff70b55c ff70b738 ff70d3b4 ff70d654
3002mS PRN: ALARM: 15/08/2006 08:36:49 IP 406 DS 2.1(35) <TLB Data Error> CRIT RAISED addr=00c4ffe6 d=5 pc=ff707a70 ff707a44 ff709d18 ff70a604 ff709a78 ff70af1c
3002mS PRN: ALARM: 15/08/2006 08:38:04 IP 406 DS 2.1(35) <TLB Data Error> CRIT RAISED addr=0000066c d=5 pc=ff705cd8 ff63ecd4 ff70a200 ff70a5e0 ff709ab8 ff709b74
3002mS PRN: ALARM: 25/08/2006 13:41:29 IP 406 DS 2.1(35) <TLB Data Error> CRIT RAISED addr=000007d5 d=5 pc=ff707aac ff707a44 ff709d18 ff70a604 ff709a78 ff70af1c
3002mS PRN: ALARM: 25/08/2006 16:34:26 IP 406 DS 2.1(35) <TLB Instruction Error> CRIT RAISED addr=ff400000 d=5 pc=00000000 ff63ed00 ff70a200 ff70a5e0 ff709ab8 ff709b74
3003mS PRN: ALARM: 25/08/2006 18:32:33 IP 406 DS 2.1(35) <TLB Instruction Error> CRIT RAISED addr=ff400000 d=5 pc=00000000 ff63ecd4 ff70a200 ff70a5e0 ff709ab8 ff709b74
3003mS PRN: ALARM: 25/08/2006 18:33:12 IP 406 DS 2.1(35) <TLB Data Error> CRIT RAISED addr=0000006c d=5 pc=ff705cd8 ff63ecd4 ff70a200 ff70a5e0 ff709a78 ff70977c
3003mS PRN: +++ END OF ALARM LOG DUMP +++

 

[TheDoz]

Check you T1 connections also. I had a T1 plug at the D-Mark not seated corectly and caused an alarm on CSU intermittentantly and the IP Office would reboot then come back up dropping who ever was on the phone.
Just a thought.

"A politician is a fellow who will lay down your life for his country.

 

[jamie77]

Load the config into 3.2 manager and see what errors it pulls with the config. might be worth a look

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!