5410 Upgrade from R2 to R6 firmware

[sometechnician]

We have recently had an issue at 2 client sites in which - after a successful upgrade of system and modules from (A)Early 3.2.x and (B) 4.2.11 to 7.0.23 - a subselection of the client's 5410s have not upgraded, but rather say "Waiting for firmware download." All of the tricks - trying to rename phone bin files (from 5410_R2 to 5410_R6 in order to trick them into downgrading back), ALLOW_5410_UPGRADES, etc... have not worked to recover them. The 5410_R6 file is successfully TFTP'd to the module via the IPO, and the phone shows 0KB briefly, then cycles again to the same message. They are NOT in the serial number range as found in TB91 or the 2 subsequent TBs. They span 2 expansion modules, and other 5410s on each module are okay - just a selection of around 15 5410s at each client that won't come up. Does anyone have any insight into this? We will create a T3 case ASAP, but respect that the TekTips community is often faster at finding a resolution.
Any help is appreciated.

 

[tlpeter]

When it is a DSv2 module then you need to use 3.2.999 before you go to anything higher then 4.X


BAZINGA!

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

 

[sometechnician]

Thank you - we did that initially and it upgraded as expected. Other 5410 phones are working on this module too. Any other ideas?

 

[tlpeter]

Don't use a digital pport twice for upgrade phones.
You can only do that after rebooting the ipo.
So one phone upgrade per port.


BAZINGA!

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

 

[sometechnician]

I'm sorry, I don't follow?
Thanks for the timely response BTW!

 

[tlpeter]

Lets say you have a DS16.
Then you can upgrade phone 1 on port 1 and phone 2 on port 2.
When those phones are upgrade then you cannot put phone 3 on port 1 or 2.
It just will not upgrade at all.
It will only upgrade a phone on a port that did not upgrade a phone yet.
A reboot fixes this.


BAZINGA!

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

 

[sometechnician]

Thanks for the clarification. Each of the phones has their own port. They simply don't upgrade. They cycle around and around saying Waiting for Firmware download. They don't work in a port that has worked for another phone's successful upgrade, even after a reboot. They just don't do anything beyond cycling around and around. At our office, I have tried everything on a working port, - forcing the upgrade, trying to downgrade them, etc... they do not work on the old system anymore either (a 406) when plugged into the KSU. It seems they are cooked!

 

[tlpeter]

Check the serials of those phones please:

07N543XXXXXX to 08N503XXXXXX

When you upgrade them (or try to) then they are broken.


BAZINGA!

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

 

[sometechnician]

Indeed they do fall in that range. I didn't realize that it was a range between the 2 serials in TB91 - thought that they only included those starting with those digits - i.e. 07N543.
It seems our client's phones fall right in the middle - late 2007 models I suspect. Many thanks for clarification - should be an open-close issue for Avaya T3. Wow - I've read TB91 5 times and not interpreted it that way!

 

[tlpeter]

At least you found the issue


BAZINGA!

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

 

[Telecomboy]

Is Avaya still swapping them out? I thought the time frame ran out for getting them to swap them was over?

 

[tlpeter]

You cannot swap them anymore.
You need to get new phones for this customer.


BAZINGA!

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

 

[Telecomboy]

That's what I thought. Just wanted to make sure I was being told the correct info. from my distributor.

 

[sometechnician]

That won't be nice. We'll see what they say regardless. - need a firm answer before purchasing a handful of new phones!