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

Stubborn TFTP checksum errors on 2513 Flash

Status
Not open for further replies.

Gus0920

Programmer
May 26, 2009
2
US
In trying to upgrade my 2513 to 16MB Flash, the 8MB SIMM I installed in slot1 wouldn't fit unless I turned it so the chips faced backward. I'd tried this before on other routers and usually I got the "order reversed - Flash initialization failed" message at bootup. But I didn't get that this time!

So it booted up to 12.0(8) as always, and next I set out to copy 12.2d from another router via TFTP. All looked well and good but then I got an invalid checksum error. Now the thing only comes up to (boot) mode. (The 12.0(8) imasge, once stored in slot0, is gone since Flash was erased prior to the TFTP transfer.)

I'm trying to figure out why I'd get that checksum problem with an image that boots just fine on the other router which has the exact same amount of Flash memory, and with the new Flash module apparently having initialized just fine (a show flash command showed 16384K ready and waiting).

This here Cisco website says IOS's TFTP client won't work for files greater than 16MB, except I've copied this 12.2d image around via TFTP plenty of times, into 2501's, 2502's and my 2521 without any difficulties.

Any ideas what the problem is? Solutions?
 
I wonder why the thread index said "5 replies" when I see roughly zero replies...
 
well don't worry about the reply.
however the best way to do is to use a TFTP Application not Cisco TFTP that does not work well with the older model. first of all if you are on rommon1> mode do a "dir all
then look at your files see if you recognize your older version and use the "rommon #>boot (slot0:/flash0:/or any) and the file system. also becareful you might have created a sub directory for the new image. if you have the second case simply use the "copy comand andfollow the direction that it gives you.
it is easy if you understand the concept, which i know you do otherwise you wouldn't be ancient to find out how to fix it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top