Comments on: Verify your IOS before reloading that router!

By: Roy Follman

Roy Follman — Mon, 07 Jun 2010 07:35:46 +0000

Hi there, Great site, I’m going to post a link back to your article on my website with a quote. just thought I would check that’s ok?

By: Turret Press Reloading

Turret Press Reloading — Fri, 21 May 2010 01:03:30 +0000

Hi, awesome post. I just now came across your site and I’m already a fan.

By: Carlos Curit

Carlos Curit — Thu, 20 May 2010 18:29:30 +0000

Major thankies for the blog.Really thank you! Really Cool.

By: Espen Nilsen

Espen Nilsen — Tue, 19 May 2009 15:16:55 +0000

@Rich: I agree, I just meant that it’s better though than trying to upload it a couple of times to the router and verify there if it’s already corrupt

By: Rich

Rich — Tue, 09 Sep 2008 19:48:18 +0000

You can, but that doesnt help you to determine if the file was corrupted in-transit. Taking the original (known good) MD5 from cisco.com and then matching it up by using Verify on the router ensures you are not about to buy yourself a long drive out to the site!

By: Espen Nilsen

Espen Nilsen — Sun, 07 Sep 2008 04:00:38 +0000

If you run your TFTP server on linux, you can get the md5 hash for the file by using the ‘md5sum’ command on the file to match against cisco.com

By: Rich

Rich — Thu, 24 Jul 2008 22:37:52 +0000

Another very useful tip, thanks

By: Simon

Simon — Thu, 24 Jul 2008 20:16:52 +0000

nice.

btw eric from http://www.nettiki.com/ just told me the following..

“Another thing to look for is that when you use tftp (Trivial File Transfer Protocol) to upgrade your image from a tftp server, you should look for two “OK”s. The 1st OK will indicate that the file transfer completed successfully and the 2nd OK will indicate that the checksum of the file validated correctly.”