IP406 V" randomly rebooting

[Ant007]

I have read through some of the posts but have been unable to find an answer.
I have a IP406 on site and it has been there for a number of years running ver5.0(15).
I haven't made any changes to it in the recent months. This morning it has decided it doesn't like the easy life and has started randomly rebooting. I have copied a part of the trace, any ideas:

Warning: TEXT Logging to File STOPPED on 9/9/2013 13:59:45 **********
1252349mS PRN: Monitor Started IP=192.168.0.26 IP 406 DS 5.0(15) LawExpress
(IP Office: Supports Unicode, System Locale is eng)
1252350mS PRN: LAW=A PRI=1, BRI=0, ALOG=4, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=1 LANM=0 CkSRC=5 VMAIL=1(VER=3 TYP=1) CALLS=2(TOT=29)
1252847mS RES: Mon 9/9/2013 13:59:45 FreeMem=39175316(1) CMMsg=8 (9) Buff=100 618 499 1048 3 Links=6169
1252847mS RES2: IP 406 DS 5.0(15) Tasks=24 RTEngine=0 CMRTEngine=0 Timer=61 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=4
1255350mS PRN: +++ START OF ALARM LOG DUMP +++
1255350mS PRN: ALARM: 02/09/2013 17:58:31 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=5 pc=ff16c7ac ff16c528 00000000 ff11f36c ff2715a4 ff271568
1255351mS PRN: ALARM: 02/09/2013 18:40:46 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=2 pc=ff16c7ac ff16c528 00000000 00000000 00000000 00000000
1255351mS PRN: ALARM: 02/09/2013 19:02:03 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=2 pc=ff16c7ac ff16c528 00000000 00000000 00000000 00000000
1255351mS PRN: ALARM: 02/09/2013 19:23:30 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=5 pc=ff16c7ac ff16c528 00000000 ff11f36c ff2715a4 ff271568
1255352mS PRN: ALARM: 09/09/2013 12:26:51 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=2 pc=ff16c7ac ff16c528 00000000 00000000 00000000 00000000
1255352mS PRN: ALARM: 09/09/2013 12:35:36 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=2 pc=ff16c7ac ff16c528 00000000 00000000 00000000 00000000
1255352mS PRN: ALARM: 09/09/2013 12:54:04 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=5 pc=ff16c7ac ff16c528 00000000 ff11f36c ff2715a4 ff271568
1255353mS PRN: ALARM: 09/09/2013 13:38:35 IP 406 DS 5.0(15) <TLB Data > CRIT RAISED addr=7f7f7fe3 d=2 pc=ff16c7ac ff16c528 00000000 00000000 00000000 00000000
1255353mS PRN: +++ END OF ALARM LOG DUMP +++
1263263mS CMExtnRxP: v=6608
CMShortCode
Line: type=NoLine 0 Call: lid=0 id=-1 in=0
ShortCode GetSystemInfo (99) = []
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
1263263mS CMExtnEvt: Indy: ProcessShortCode feature=GetSystemInfo id=
1263264mS CMExtnTxP: v=6608
CMShortCode
Line: type=DigitalExtn 4 Call: lid=0 id=-1 in=0
ShortCode GetSystemInfo (99) = [5.0 (15)] Calling[LawExpress] Type=Default Plan=Default
Display [IP 406 DS]
Tag type=Text flags=0x1 [1,1,3,1,0,1,0.] [0x31 0x2c 0x31 0x2c 0x33 0x2c 0x31 0x2c 0x30 0x2c 0x31 0x2c 0x30 0x00 ]
Timed: 09/09/13 13:59

Thanks

 

[hairlessupportmonkey]

I would download and upgrade to the latest rel 5 software.

[link ftp://ftp.avaya.com/incoming/Up1cku9/SoftwarePub/5_0GA_Builds/ADMIN/ADMIN5_0_26.exe]5.0.25 is what you need[/url]

ACSS - SME
General Geek

 

[Ant007]

Thanks for the reply.
I will upgrade, but will this sort the problem. The systems been on this firmware version for years without any issues, I thought that it was perhaps a hardware failure as this was a new fault.

Cheers

 

[AndrePa]

I would for sure upgrade the 406v2 to R5.0(26), it's much more stable!
Also verify no one logged in and made any changes, errors can make IPO reboot.
I would also re-check monitor, if You're getting cold restarts, you might have a weak power supply. You might get lucky with replacing the power supply, however, the 406v2 also has a voltage regulator on the main board. If this is the case, You would need to replace/repair the unit, or upgrade to 500/500v2.

Andre

 

[tlpeter]

It could be some kind of loop created with forwarding etc etc.
Let monitor run and enable logs (setup the automatic log writes) and capture what is going on.


BAZINGA!

I'm not insane, my mother had me tested!

 

[smokinjoe2938]

I would try to 1st replace the power supply as have seen this very same issue in the past.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[Ant007]

Thanks all.

I think I will go for the easy option first and replace the power supply, then upgrade and then replace(as a last resort).

Thanks for everyone's help.

 

[tlpeter]

Replacing the power supply is not the easiest as these are not sold as spare part


BAZINGA!

I'm not insane, my mother had me tested!