[c-nsp] c2960g: flash gone mad ?

[Alexandre Snarskii]

On Thu, Oct 16, 2008 at 09:33:33AM -0500, Church, Charles wrote:
> I believe the IOS is to blame.  I saw a similar thing with 12.2(44)SE2
> on 3550, I believe.  The verify never worked, but MD5 verify did.  I
> don't remember the reload and signature issue though.  I'm willing to
> bet it'll work ok from here on out. 

Well, it really looks like some 'new and cool IOS feature', 
"reload /verify", which is broken in 12.2(46)SE. 

Tested that in lab: got another 2960 (non-g), running 12.2(35)SE5, 
uploaded and successfully verified 12.2(46)SE, reloaded, and got

Switch#verify flash:c2960-lanbase-mz.122-46.SE.bin
File system hash verification failed for file flash:c2960-lanbase-mz.122-46.SE.bin(No such file or directory).

However, it reloaded just fine, so, it looks like there are 
two _different_ defaults: 2960 has default to reload /noverify 
and 2960g to reload /verify


> Chuck 
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Alexandre
> Snarskii
> Sent: Thursday, October 16, 2008 9:21 AM
> To: Cisco-NSP Mailing List
> Subject: [c-nsp] c2960g: flash gone mad ?
> 
> 
> 
> Hi!
> 
> While trying to upgrade IOS on one of ours c2960g, I got strange
> message: 
> 
> SW088-022#verify flash:c2960-lanbase-mz.122-46.SE.bin
> File system hash verification failed for file
> flash:c2960-lanbase-mz.122-46.SE.bin(No such file or directory).
> 
> however, MD5 verification of the same file succeeded: 
> 
> SW088-022#verify /md5 flash:c2960-lanbase-mz.122-46.SE.bin
> [....]
> ....................Done!
> verify /md5 (flash:c2960-lanbase-mz.122-46.SE.bin) =
> 27ad87f2c90595f3e682633c7985099a
> 
> Well, I tried to format flash:, and re-upload IOS image - results
> were the same. 
> 
> And then switch refused to reload 'by command': 
> 
> SW088-022#reload 
> %ERROR: Not able to process Signature in flash:.
> %ERROR: Aborting reload.
> 
> so, I had to visit equipment room and reboot it by power cycle 
> (booted normally, looks like that there are no signature check 
> on boot). 
> 
> What is it ? Faulty flash ? Does not looks like - md5 check is just
> fine... 
> And what to do with that switch ? Is it safe to leave it in network 
> (on office one, without remote reboot ability it not qualified to remote
> 
> installations) or better to RMA it ? 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/