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.

 

[TomMills]

get monitor running and try and capture a trace of the reboot.

SSA should also show why the most recent reboot happened.

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[TomMills]

unless you've manually rebooted it since then...

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[confusedtwo]

SSA is only showing informtion from 10:38am Tuesday, which is the when the system started back from the last reboot.

Will get a monitor trace going.

 

[TomMills]

if you log into SSA, click on alarms (don't expand it, click on the word), that will show you the reason for the last system restart.

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[Bas1234]

There are some bug in the 6.1.5 why didn't you go to 6.1.12?

http://marketingtools.avaya.com/knowledgebase/businesspartner/caveats

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

Dain Bramaged (

http://tinyurl.com/bas1234

)
___________________________________________

 

[Bas1234]

Forgot to paste the CQ's


CQ41668|Memory related system restart on IP Office 500v2 6.1.5|
6.1.5|SP_RELEASE_1Q11_6.1|4-Proven|6.1.058401


CQ41779|System restart on a pb and may be related to 41668 memory leak|6.1.5|SP_RELEASE_2Q11_6.1|4-Proven|6.1.058402

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

Dain Bramaged (

http://tinyurl.com/bas1234

)
___________________________________________

 

[thaddl]

I'm helping w/ this too. Here's what we get on our monitor trace when it restarts:

11352833mS PRN: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
11352833mS PRN: IP 412 6.1(5)
11352833mS PRN: OSMemPool::Allocate Out of Memory: 32
11367815mS PRN: Alarm log cyclic wrap
11367815mS PRN: .WATCHDOG TIMEOUT CMRtEngine stack 00970f00 009395e0 0093b720 009d51d0 009d7b78 009de3ec 009f4770 009f83c4 009e18f8 00a271dc 00a105ac 00a109f4 00a15fa0 00a105d0 00a1381c 00a56230 008fe360 009011b0 009016c8 00901818 IP 412 6.1(5)

Another thing to note is that before the upgrade to 6.1 our configuation file was at 249KB, after the upgrade it is 270K. Is there a 256K limit or is that just coincidence? I thouht the limit was 1MB, according to this post:

http://www.tek-tips.com/viewthread.cfm?qid=1303995&page=588

 

[thaddl]

TomMills,
Here's the SSA Alarms
Reason: Abnormal Termination
Termination Cause: <watchdog> addr=00000000 d=0 pc=00970f00

Bas1234,
That very well could be it, we use tapi drivers all over the place. We are updating to 6.1(12) tonight. Hopefully this will fix it.

 

[jamie77]

Get up to 6.1(12). There are bug fixes and Avaya will want you to do this before taking it on board.

Check for any user names or groups with unsupported characters, starting or ending with a space etc...

Get Monitor Traces/SSA Logs/Config to your BP/Disty to raise with Avaya.

Jamie Green

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

 

[tlpeter]

Was this system on 7.0.3 (fieldtrial) before "upgraded" back to 6.1 ???
If you did then this is a known issue.
You need to reset the security settings.

Then you are ok.


BAZINGA!

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

 

[jamie77]

A 412 on R7????

If theipgrade doesn't work, maybe rewrite the configuration or use an old backup. It could just be corruption.

Jamie Green

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

 

[tlpeter]

You are right.
A 412 cannot go to 7.0
Although i still find it strange.
A 412 has the same amount of internal memory as an IP500v1.


BAZINGA!

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

 

[confusedtwo]

Never had release 7. Upgraded to 6.1.12. We will wait and see now.

 

[tlpeter]

confusedtwo, you could not have been running 7.0
My mistake.


BAZINGA!

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

 

[confusedtwo]

Thanks to all for your input and help. We upgraded to 6.1.12 Teusday evening and as of Thursday morning no more problems with the system rebooting. Just have to find a fix to replace delta server.

 

[TomMills]

what were you using it for?

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[confusedtwo]

Customer has Replay T1 from Trisys. The Delta Server was being used to save the SMDR data as a .csv file that the call recording software could pull the call information from and then attach to the appropriate recording.

We installed Kiwi 30 day free trial as a temporary fix but the customer is not real interested in having to purchase even more stuff to do what they were doing before.

I am looking into sending the SMDR data directly to the call recorder through TCP.

 

[TomMills]

Yeah i'd just check with the call recording co and see if they can do direct smdr.

http://www.twitter.com/tem1985

ACSS-SME
fo shizzle ma nizzle.

 

[thaddl]

ok, so the "reset" just happened again. not sure what is going on. we are starting the trace files for the monitor again. I will post the results when I get them to see if anything has changed.