Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office R.11 rebooting 5-6 times after Immediate reboot 1

Status
Not open for further replies.

IgorStranzit

Systems Engineer
Apr 14, 2020
4
RU
Hi everyone!
After upgrading station from R8.0 to R11.0 IP Office starts with 5-6 rebooting.

18:30:40 538837mS PRN: .FATAL TLB Data Load Error address=00ffffec d=5 pc=f0256c20 f02b181c f027337c f150d5b4 f150bcb0 f150b138 IP 500 V2 11.0.0.0.0 build 849

If we change configuration with Immediate reboot the station starts same (5-6 rebooting)

18:22:53 71142mS PRN: ALARM: 12/03/2020 18:02:05 IP 500 V2 11.0.0.0.0 build 849 <ISI Exception > CRIT RAISED addr=00000000 d=5 pc=00000000 00000000 f09cbd08 f09cc278 f11466e8 f075b83c
18:22:53 71143mS PRN: ALARM: 12/03/2020 18:11:14 IP 500 V2 11.0.0.0.0 build 849 <TLB Data Load Error > CRIT RAISED addr=00ffffec d=5 pc=f0256c20 f02b181c f027337c f150d5b4 f150bcb0 f150b138
18:22:53 71143mS PRN: ALARM: 12/03/2020 18:16:54 IP 500 V2 11.0.0.0.0 build 849 <TLB Data Load Error > CRIT RAISED addr=00ffffec d=5 pc=f0256c20 f02b181c f027337c f150d5b4 f150bcb0 f150b138

18:32:35 71394mS PRN: ALARM: 17/03/2020 13:15:29 IP 500 V2 11.0.0.0.0 build 849 <OSMemPool::No Pools for: 12000 Remainin> CRIT RAISED addr=f02bc0b0 d=5 pc=f0257260 f025bb8c f13a37c8 f13a3964 f13a3e04 f13c28c8

Please help us :)

Here is full log of starting
 
 https://files.engineering.com/getfile.aspx?folder=906d698c-7359-43b3-af2d-3273a8dfc73a&file=14_04_2020_reboot.txt
Yes, we did it.
8.0 to 9.0 and then was 10.1 but after that IP Office started reboot. Then we upgraded it to R.11

We will try R11.1

Do you think we should do it to 8.1 then 9.0 and then 11.1?
 
I don't think you can go to 11.1, since you will probably need an upgrade/ migration license

I would say if you have the configuration backup from before the upgrade and licenses from 8.0, keep them on hand.
Maybe you can recreate the SD card using the avaya manager, Don't use regular format from the pc.

Upgrade from 8.1 to 9.1 and then go to 11.0.4
But add the upgrade license in version 8.1 and move upward
 
I would get a new SD card. At R8 it would have had the small card. A format and upgrade would be your best bet if you don't want to get a new SD. Our maintenance contract customers, who get regular upgrades, we found that the SD cards were getting filled by old FW files. We have been getting them new SDs when going to R11 just to be safe.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
Oh and I would upgrade to the latest build. 11.0.0.0 was the first release and the first release is always a bit buggy.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
Like budbyrd said, try the latest version, not the first one. 11.0.4
Also a question,do you have a spare control unit, just to check if it also isn't the control unit giving you issue?
 
tkwqtseh are you having a stroke

-Austin
I used to be an ACE. Now I'm just an Arse.
qrcode.png
 
I usually go 8.1 (95) then to R11.0.4 - At this point untick the "download files" box. Upgrade, then apply the new PLDS licences, then re-upgrade withe all the .bin files being uploaded (yeah, the really long, boring bit). This has worked for me on a regular basis. You may be getting the issues as the bootloader files change significantly in later versions of R8.
Best of luck :)

Should have been a Bus mechanic seeing as I spend so much time under them.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top