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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

8.1(43) TFTP Firmware Write Failure 2

Status
Not open for further replies.

Praefectus27

Programmer
Sep 7, 2012
13
0
0
IP Office 500v2 currently at 8.1(43) but was at 7.0 and 8.0 will issue out firmware updates to phones but will freeze up and not complete. I have 2 combo cards in the system one in slot 1 and the other in slot 2, it seems to happen only on slot 2. I've changed out combo cards and controll unit. Went from 9508 set to 1408 sets, 3 different levels of firmware. Changed bin files all the way back to release 5 to see if it would boot up with older versions. Set manager, SD card and TFTP Server 2000 to send files and nothing seems to work. Seems to happen at random whenever the system reboot BUT always on combo card in slot 2. I've talked to tons of people on the issues and no one seems to know what the problem is. Help! If anyone needs the log files i have two, one with the 1408 sets and the other with the 9508 sets.
 
Telecomboy, it is hardcoded in the IP500 software.
You will need to have the right version otherwise the phones will never try to grab it.
There is a 7.0 and a 8.0 version.
For 8.1 there is version yet (i think)


BAZINGA!

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

 
Excuse the bump, but after trying the hotfix linked above I'm still stuck on Please Wait. This is the error I'm seeing on Monitor when the files are being pushed out to the phone. UpgradeFileReader(f592438c:0)::End of File 9500R44.bin len=0 reason=4 error=2

Any ideas?
 
1347535mS PRN: Monitor Status IP 500 V2 8.1(433001)
1347536mS PRN: LAW=U PRI=0, BRI=0, ALOG=8, VCOMP=20, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=1(VER=2 TYP=3) 1-X=0 CALLS=0(TOT=0)
1348651mS PRN: UpgradeEngine(f5925038:0)::Start FileSysReader file=9500R44.bin
1348710mS PRN: UpgradeFileReader(f5925038:0)::End of File 9500R44.bin len=0 reason=2 error=4
1358710mS PRN: UpgradeEngine(f5925038:0)::Start FileSysReader file=9500R44.bin
1358771mS PRN: UpgradeFileReader(f5925038:0)::End of File 9500R44.bin len=0 reason=2 error=4
1368771mS PRN: UpgradeEngine(f5925038:0)::Start FileSysReader file=9500R44.bin
1368829mS PRN: UpgradeFileReader(f5925038:0)::End of File 9500R44.bin len=0 reason=2 error=4
1378829mS PRN: UpgradeEngine(f5925038:0)::Start FileSysReader file=9500R44.bin
1378887mS PRN: UpgradeFileReader(f5925038:0)::End of File 9500R44.bin len=0 reason=2 error=4
1388887mS PRN: UpgradeEngine(f5925038:0)::Start FileSysReader file=9500R44.bin
1388905mS RES: Thu 8/11/2012 17:11:01 FreeMem=60339912(1) CMMsg=2 (4) Buff=5200 942 999 7463 5 Links=8336 CPU=1/3/3463/23134/23386/0
1388905mS RES2: IP 500 V2 8.1(433001) Tasks=46 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=48 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=2 SSA=1 TCP=16 TAPI=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
1388958mS PRN: UpgradeFileReader(f5925038:0)::End of File 9500R44.bin len=0 reason=2 error=4
1398969mS PRN: UpgradeEngine(f5925038:0)::Start FileSysReader file=9500R44.bin
1399031mS PRN: UpgradeFileReader(f5925038:0)::End of File 9500R44.bin len=0 reason=2 error=4

The full spiel, hopefully there's somebody out there. In dire straits at the moment, and I don't mean the cool 80s band.
 
If anyone sees the above, force the 9500R44.bin file into the SD card with embedded file manager. Hand me the dunce cap.
 
Only ever seen this with dodgy combo cards, try a DS8 card if this is the case...just to prove it or not :)

 
I have seen this because the file is not copied to the SD card, you have to do this by hand like you already did.


BAZINGA!

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

 
Just an FYI should someone run across the future as I just did when hunting for a solution for my error:

UpgradeFileReader(f57762ec:3)::End of File 9500R45.bin len=0 reason=2 error=4

It turned out that someone had set the IP500 V1 for memory card rather than manager and since there is no memory card it was giving essentially the same error. Switching it back to manager fixed the problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top