3850-12XS-E IOS Upgrade

[Ravs]

Spoiler

Hi Guys,

We have the 3850-12XS-E in the Install Mode. I have few queries around it and will be very grateful for your assistance.

1. The Verify /md5 flash: cat3k_caa-universalk9.16.09.05.SPA.bin

     The md5 value match between Cisco.com and that of the Verify command on the Switch.

      =But when we Verify /sha512 flash: cat3k_caa-universalk9.16.09.05.SPA.bin, the SHA values fail. 

%Error verifying flash:cat3k_caa-universalk9.16.09.05.SPA.bin
Computed signature a01d8ab7121e50dc688b9a2a03bca187aab5272516c0df3cb7e261f16a1c8ac355880939fd0c24cc9a79e854985af786c430d9b704925e17808353d70bf923f4
Submitted signature = 2fe5f71f072dae0de5ff66507b274d887775db6931f868a78028578ec21db10a0a20532f5f346dfa741d67d6d1cad5a7d2511ac5e54d9a98a24a6aff67252f3b

Please if you can assist as to why the /sha512 would fail and md5 still Pass and can we use the IOS Image on this switch since I have copied 3 times, and every time the md5 values match and /sha512 fails.

Secondly, the show version is 

Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 16 WS-C3850-12XS 16.9.1 CAT3K_CAA-UNIVERSALK9 INSTALL

And show boot is : 

#show boot
---------------------------
Switch 1
---------------------------
Current Boot Variables:
BOOT variable does not exist

Boot Variables on next reload:
BOOT variable = flash:packages.conf
Manual Boot = no
Enable Break = no
Boot Mode = DEVICE
iPXE Timeout = 0

Nothing displayed after : show run | in ^boot

With the  16.9.5 already present in the flash, if we did a reload on this switch, will the switch boot up on the 16.9.5 automatically or that we will need to run some more commands. Somewhere i read that the switch will boot on the lastest IOS through the packages.conf and i am not sure at this stage since this is the production switch.

Regards

Ravs

[Leo Laohoo]

---

@Ravs wrote:

%Error verifying flash:cat3k_caa-universalk9.16.09.05.SPA.bin
Computed signature a01d8ab7121e50dc688b9a2a03bca187aab5272516c0df3cb7e261f16a1c8ac355880939fd0c24cc9a79e854985af786c430d9b704925e17808353d70bf923f4
Submitted signature = 2fe5f71f072dae0de5ff66507b274d887775db6931f868a78028578ec21db10a0a20532f5f346dfa741d67d6d1cad5a7d2511ac5e54d9a98a24a6aff67252f3b

---

That error message makes sense.  

a01d8ab7121e50dc688b9a2a03bca187aab5272516c0df3cb7e261f16a1c8ac355880939fd0c24cc9a79e854985af786c430d9b704925e17808353d70bf923f4

The above hash is the SHA512 for the file "cat3k_caa-universalk9.16.09.05.SPA.bin". 

The hash SHA512 you've submitted, ending with "2f3b", is for the file "cat3k_caa-universalk9ldpe.16.09.05.SPA.bin".

They are two totally different files therefore the SHA512 hash are totally different.

To unpack the "cat3k_caa-universalk9.16.09.05.SPA.bin" file, use the following command: 

request platform software package clean switch all
request platform software package install switch all file flash:cat3k_caa-universalk9.16.09.05.SPA.bin new auto-copy verbose

[Ravs · Accepted solution]

Thanks a lot Leo

Re-checked the Sha and its verified, Thanks a lot for your assistance.

Verified (flash:cat3k_caa-universalk9.16.09.05.SPA.bin) = a01d8ab7121e50dc688b9a2a03bca187aab5272516c0df3cb7e261f16a1c8ac355880939fd0c24cc9a79e854985af786c430d9b704925e17808353d70bf923f4

Thanks a lot for your help.

Regards

Ravs