cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
892
Views
1
Helpful
11
Replies

Verify standby supervisor engine ios-xe image fails

LuensmannIT
Level 1
Level 1

Hi, there,

I've a couple of WS-C4507R+E switches (Version 03.08.07.E.152-4.E7) with installed standby supervisor engine.

Verifying the ios-xe image on the primary supervisor engine works, but verifying and image on the slavebootflash doesn't work:

HOSTNAME#verify bootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin
Digital signature successfully verified in package cat4500es8-base.SPA.03.08.07.E.pkg
Digital signature successfully verified in package cat4500es8-firmware.SPA.03.08.07.E.pkg
Digital signature successfully verified in package cat4500es8-infra.SPA.03.08.07.E.pkg
Digital signature successfully verified in package cat4500es8-universalk9.SPA.152-4.E7.pkg
Digital signature successfully verified in file bootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

HOSTNAME#verify slavebootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin
Error Verifying file slavebootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

Is this a expected behavior?
Do i have to attach (attach module 4", "session module 4") to the standby supervisor engine first and execute the verify command from the standby supervisor engine itself?

1 Accepted Solution

Accepted Solutions

Try this: 

 

verify /md5 slavebootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin b2251364febbdfb5b6d4149ddd0e7a71

If this still comes up as corrupt, copy the IOS into a USB and stick it into the standby-supervisor card's USB port. 

And then re-run the verify.

 

View solution in original post

11 Replies 11

balaji.bandi
Hall of Fame
Hall of Fame

where did you copy the image from ? primary bootflash ?

i would check the size of the file ? compare primary and seconday bootflash :

make sure you can able to dir slavebootflash:

 

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

LuensmannIT
Level 1
Level 1

On most of the switches the image was copied from a usb stick to the primary bootflash.
Since the Supervisor Engines run in SSO mode the image was automatically copied from primary bootflash to the standby
The size of the files are equal.
The image seems to be ok, because we can switch between the supervisor engines without problems.
dir slavebootflash also works.

Leo Laohoo
Hall of Fame
Hall of Fame

Post the complete output to the following commands: 

dir bootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin
dir slavebootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

HOSTNAME#dir bootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin
Directory of bootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

38405 -rw- 514855624 Jun 9 2020 07:30:45 +02:00 cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

1732517888 bytes total (1214300160 bytes free)
HOSTNAME#$otflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin
Directory of slavebootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

23045 -rw- 514855624 Jun 9 2020 07:39:00 +02:00 cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

1732517888 bytes total (1214300160 bytes free)
HOSTNAME#

I tried it on multiple switche - output (regarding size and names) is the same

 

Try this: 

 

verify /md5 slavebootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin b2251364febbdfb5b6d4149ddd0e7a71

If this still comes up as corrupt, copy the IOS into a USB and stick it into the standby-supervisor card's USB port. 

And then re-run the verify.

 

LuensmannIT
Level 1
Level 1

Hi @Leo Laohoo
this commands works with both primary and standby sup / bootflash. The checksums are correct.

Do you have an explanation why i need to provide /md5 and a hash for the check of slavebootflash but not for (primary) bootflash?

My expectation is that I either need to provide /md5 and the hash all the time regardless if primary or secondary supervisor flash is checked or I don't need to provide /md5 and the hash regardless if primary or secondary supervisor flash is checked.

 

 


@LuensmannIT wrote:
this commands works with both primary and standby sup / bootflash. 

Let me clarify, if you entered the command into the primary and secondary the output says "Verified"?

If it does, then it is a bug.

Primary: 

verify /md5 bootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin b2251364febbdfb5b6d4149ddd0e7a71
Verified (bootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin) = b2251364febbdfb5b6d4149ddd0e7a71

verify bootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin
Digital signature successfully verified in package cat4500es8-base.SPA.03.08.07.E.pkg
Digital signature successfully verified in package cat4500es8-firmware.SPA.03.08.07.E.pkg
Digital signature successfully verified in package cat4500es8-infra.SPA.03.08.07.E.pkg
Digital signature successfully verified in package cat4500es8-universalk9.SPA.152-4.E7.pkg
Digital signature successfully verified in file bootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

Secondary:

verify /md5 slavebootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin b2251364febbdfb5b6d4149ddd0e7a71
Verified (slavebootflash:cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin) = b2251364febbdfb5b6d4149ddd0e7a71

verify slavebootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin
Error Verifying file slavebootflash:/cat4500es8-universalk9.SPA.03.08.07.E.152-4.E7.bin

RMA the secondary Supervisor card.  The flash if f*cked.

Hmmm, it's happening on all 24 WS-C4507R+E switches (only standby sup) in production.
Having 24 times a f*cked up flash at the same time seems to be very weird.
Maybe it's indeed a bug. I will try to update the ios-xe image in a lab enviroment.
Could take quite a bit but i keep to updated.

Upgrade the firmware and try. 

I have never seen a behaviour like that before.

Review Cisco Networking for a $25 gift card