• September 21, 2020, 08:14:59 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Error reading image file  (Read 5796 times)

0 Members and 1 Guest are viewing this topic.

Offline CptnBlues63

  • Sr. Member
  • ****
  • Posts: 100
Error reading image file
« on: January 20, 2014, 01:22:00 PM »
Background:

I still have some switches running v4.2.3 and am in the process of upgrading them.  I've gone through this process many times in the last 2 years as I slowly get all my switches up to a new standard (v6.2.7 for now) without issue.  The procedure I researched and confirmed in lab before using multiple times successfully is as follows:

v4.2.3 >> v5.0.0
v5.0.0 >> v6.0.0
v6.0.0 >> v6.2.7

Yesterday my coworker was at one of our other geographical locations and all set to upgrade two stacks from v4.2.3 to v6.2.7  and when he began the process by attempting to first upgrade the diagnostics to the v5.0.0 diags he received the "Error reading image file" error  He immediately contacted me, we conferred and I advised to stop right there since everything was still working.

Today I setup a 4 switch stack that's identical to the one on-site and downgraded it to v4.2.3 then  copied the config off the production stack and deployed it on the lab stack.  I then attempted to upgrade to v5.0.0, diags first as per proper procedure and I received the same "Error reading image file" message.

Has anybody else encountered the same issue and figured out what was wrong?

Barring that, has anybody got any ideas?


Offline Telair

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 965
Re: Error reading image file
« Reply #1 on: January 20, 2014, 01:50:25 PM »
In the past when trying to upgrade very old switches, at times I had to upgrade to the latest in the old code before jumping to v5.0.  So maybe try upgrading to v4.2.6 first before going to v5.0?  It has worked for me in the past.  Otherwise, has your v5.0 image gone corrupt or the TFTP server not support transferring over 16MB?  Had both those issues show up as well.
« Last Edit: January 20, 2014, 02:35:11 PM by Telair »

Offline TankII

  • Hero Member
  • *****
  • Posts: 556
Re: Error reading image file
« Reply #2 on: January 20, 2014, 02:17:52 PM »
This has happened to me for two different reasons.
1)  TFTP server was 16-bit and could not handle files over 16MB in size
2)  Didn't do the proper diagnostics file first.

TankII

Offline Paul L

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 754
    • paulaleroux
    • Paul's Networking blog
Re: Error reading image file
« Reply #3 on: January 20, 2014, 03:16:22 PM »
there are few gotchas when it comes to upgrading 5500 and 5600 series switches.

this path works for me is
4.1 -> 5.0-> 6.0 -> 6.2.4

As well, you need to go diag/fw 6.0.0.6 before you can go to 6.0.0.18.

As well X2.  when you get to version 6.0.0.0.5 there was a 5500 diag and 5600 diag.  make sure you are using the right diag

55x0_60006_diags.bin



ACSS- Avaya Enterprise Routing Switch  #8

Offline shezzski

  • Jr. Member
  • **
  • Posts: 34
Re: Error reading image file
« Reply #4 on: February 03, 2014, 04:16:17 AM »
Hi CptnBlues63,

Download the 5.0.0 image first and reboot, then you should be able to download the 5.x/6.0 diagnostics.


Offline CptnBlues63

  • Sr. Member
  • ****
  • Posts: 100
Re: Error reading image file
« Reply #5 on: February 03, 2014, 04:20:20 PM »
This is a follow up to my initial post.

I recopied the v5.0 FW/SW from our NAS and put it on both my PC and our Laptop and tested with both and it's now working.  I'm able to upgrade the lab stack (with production config on it).

I have no idea what happened but it appears something was corrupted in the copy of the v5.0 FW/SW I had on those two computers.  Refreshing both seems to have worked...........go figure......... :-\

Offline figunet

  • Rookie
  • **
  • Posts: 16
Re: Error reading image file
« Reply #6 on: February 05, 2014, 02:25:14 AM »
i think that you reach the other side, where you have the image file. Last week i had the same problem and i put default gateway to reach the other side.

Offline CptnBlues63

  • Sr. Member
  • ****
  • Posts: 100
Re: Error reading image file
« Reply #7 on: February 05, 2014, 10:06:10 AM »
i think that you reach the other side, where you have the image file. Last week i had the same problem and i put default gateway to reach the other side.

What happened to us was not a default gateway issue.

In both cases we were connected directly to the switch stack and thus not crossing any bounderies.  In the first case, with a laptop to the production stack.  In the second case, with my PC and the lab stack on my desk.  In the third case, with the aforementioned laptop connected to the lab stack on my desk.

Using Windows 7 and IE v10 (in both cases) I've found when directly connecting to a switch you have to actually remove the default gateway address in order to use EDM in IE.  When connected directly to a switch like that, one does not need a default gateway IP to connect to the switch via browser (EDM) or telnet (command line).

When I say "connecting directly" I mean of course having the console cable plugged into the PC/Laptop and the switch as well as a network cable running from the PC/Laptop to port 1 on the switch using the following TCP/IP settings:

PC/Laptop
IP: 192.168.0.3
SM: 255.255.255.0

Switch
IP: 192.168.0.2
SM: 255.255.255.0