Upgrade 5410 to latest firmware, "firmware upgrade: file error" 2

[CTNAGZ]

I have a IPO500 V1, running 10.1. My 5410's show a FW release of 5.00 (6/11/07). I tried upgrading the phones to 5410_R6 and they all failed. I either got a "please wait", "firmware upgrade: file error" or "incompatibility". I have the BIN file located in "C:\Program Files (x86)\Avaya\IP Office\Manager" and I set Source Code "ALLOW_5410_UPGRADES" for NoUser. To get my users back up and running, I removed the Source Code entry and rebooted the IPO.

So is this setup correctly to perform the FW Update? Is the R6 Bin file corrupted or incorrect version for my IPO? What is the latest FW for the 5410, that will work with my version of IPO?

 

[budbyrd]

You also need to run the turn_on.bat file. You will need to edit it as well for the IP address. IMO the TFTP server in manager is a bit problematic so I use solarwinds TFTP server to load the files. Just remember to use the turn_off.bat when they are done or they will try to upgrade on every reboot.
R6 is the highest version.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[CTNAGZ]

@budbyrd, Thank you for your help.
I found the bat file, it is untouched, never been used before. I see where I need to enter the IP in the bat file.

So is this what I need to do?:

1 - Modify TFTP server address to point to a new TFTP server, preferably solarwinds for example. I haven't setup a TFTP before but I would imagine I will need to put the BIN file there and publish a directory.
2 - Modify and then run the turn_on.bat file.
3 - Reboot IPO, let the fun begin.
4 - After phones have upgraded, run the turn_off.bat file.

** Do I need to add the source code "ALLOW_5410_UPGRADES" again?

 

[budbyrd]

Yes the Nouser code needs to be there. At one time there was a problem with the 5410 firmware, so they disabled it by default. They never took out the disabled part.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[CTNAGZ]

thanks again!

Is there a chance I will brick the phones? If I wanted to isolate this and test on 1 handset, I'm thinking I would need to disconnect all other phones and leave only 1 connected? Seems kind-of cave man thinking, but I don't see another way with this setup.

 

[budbyrd]

That wold be the only way to test it. You shouldn't brick the phones unless you unplug them during the upgrade.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[budbyrd]

One other thing you may need to do is set the TFTP server address in the system tab of manager.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[CTNAGZ]

I am so glad that I disconnected all of my digital stations and left only 1 plugged into my main unit. It does "brick" the phone. Regardless of what I do now, when this phone is plugged in, it just says "Waiting for upgrade".


It looks like my phones are part of TB091 (

https://downloads.avaya.com/css/P8/documents/100020103)

This issue only affects 5410 telephones in the following serial number range: 07N543XXXXXX to 08N503XXXXXXExample: 07 – Year N5 – Manufacturing Code 43 – Week of the Year Manufactured XXXXXX – Individual Telephone number
Due to an issue with the R5 telephone firmware loaded during the manufacturing process, these telephones will not, if required, upgrade correctly when connected to an IP Office system.
The display will show “Waiting for firmware download”. The telephone will not upgrade and will no longer function.

The only reason I am attempting the upgrade is that I have one user (at the moment) that discovered that the calls logs are getting the correct time stamp. Sometimes, the time will even display a future time on the missed call.

 

[Teleco4321]

IPO500 V1, running 10.1 is not supported. IPO500 V1 is only supported up to version 9.0.

As well 5410 sets are only supported to 9.1. Maybe that is why you are having so many issues.

 

[CTNAGZ]

I don't know if I'm on 8.1 or 10.1 at this point. Must be 8.1 if you say 9 was the last for the V1.

 

[critchey]

Yes on R8.1 and older manager was 2 releases higher then the control unit... because... reasons. You can typically tell if you are on R8.1 rather then R10.1 because R8.1 would have parenthesis and the minor release part is not a specific service pack where as R10.1 would be done with a specific service pack number with no parenthesis.

R8.1(65) control unit with manager 10.1(65) is R8.1 build 65 (which doesn't mean much to anyone but development team)
R10.1.0.3 control unit and manager will match and be R10.1 service pack 3

I think you already posted the correct answer you happened to have phones that are on defective firmware and when upgraded brick (confirmed by serial#).

The truth is just an excuse for lack of imagination.