412 Rebooting after upgrade to 6.1

[confusedtwo]

Sunday evening did a upgrade on a 412 from 5.0.8 to 6.1.5. Since the upgrade the system has rebooted three times. Twice on Monday at approxiamately 11:30am and 5:30pm and again at 10:35 Tuesday.

Need help! if need more info let me know.

 

[Bas1234]

OK so you have upgraded the IPO and it's still rebooting?

Termination Cause: <watchdog> addr=00000000 d=0 pc=00970f00

addr=00000000 has 00000000 in the error I would check the provider. When the addr is filled with hex digits then is a error in the IPO it self in this case its "empty" I would ask the provider I they are having problems with their lines.

I'm not for 100% sure because it's <watchdog> error and not a <TLB Data> error.

Making a trace and send it to Avaya would be the fastest option. Sometimes it's helps defaulting the IPO thru the Manager and sending saving a backup in again.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (

http://tinyurl.com/bas1234

)
___________________________________________

 

[thaddl]

Yes, we are running 6.1.12 now. We haven't had any problems since last Tuesday when up upgraded Tuesday night.

Here's the SSA Alarms on this one:
Last System Restart
Date: 3/28/2011 1:38:02 PM
Reason: Abnormal Termination
Termination Cause: <Machine C> addr=00000000 d=5 pc=00944f00 stack=00000400 00c1847c 00c18954 00c19340 00c19a10

Still waiting on the monitor trace.

thanks.

 

[thaddl]

This is still restarting every 4-5 days. Any ideas? here's some stuff from the trace file when it restarts.

Thanks everyone for your help.


325728573mS CMMap: a=33.14 b=0.0 R0
325728575mS CMMap: PCG::MapBChan pcp[159]b1r0 cp_b 1acff0c other_cp_b 0 type CGTypeSimple
325728575mS CMMap: PCG::MapBChan pcp[219]b1r0 cp_b 1a32848 other_cp_b 1acff0c type CGTypeSimple
325728576mS CMMap: a=33.14 b=20.6 M1
325728783mS PRN: 0189beb0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
325728783mS PRN: IP 412 6.1(12)
325728783mS PRN: OSBuffer::Alloc Out Of Buffers 1124

 

[galexa1004]

@Bas1234 -

Please elaborate on what you are describing; do you mean a flakey PRI connection can cause the IPO to reboot?

 

[Bas1234]

The error i've seen look like

Termination Cause: <TLB data> addr=00000000 d=0 pc=xxxxxxxxxx
and not <watchdog> in my case it was a faulty PRI, so in your case it might be the same but for 99% sure it's not the IPO. It could be the PRI or a fault in the Network.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________