ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

2920 checksums for WB.16.03.0003 verification

ohauer
Occasional Contributor

2920 checksums for WB.16.03.0003 verification

Hi,

I've downloaded now the firmware WB.16.03.0003 for the 2920 on two systems from two different networks and got a checksum mismatch.

Checksums on the download page for WB.16.03.0003

MD5: ccff96bddc8aa15e72daf01c60c34f25
SHA1: 3c8883699ffa8d8a4662c45efbe68908243503c5
SHA256: fed4aad0d80ef555f9f23c1a754e80c774ec27ef364a186eac0a8ed4b02d59f7

 

sha256 -c fed4aad0d80ef555f9f23c1a754e80c774ec27ef364a186eac0a8ed4b02d59f7 WB_16_03_0003.swi
SHA256 (WB_16_03_0003.swi) = eb163c6b7506e7e377216ff1688fe0d10eac4db8eb0806d49c86553e99e2acd7 [ Failed ]

Perhaps someone can do a second verify?

4 REPLIES
parnassus
Honored Contributor

Re: 2920 checksums for WB.16.03.0003 verification

Yep.

Apparently there is a mismatch with respect to advertised (MD5|SHA1|SHA256) Hash values (not updated...) or the published file is somewhat corrupted server side (or it wasn't corrupted, simply it isn't the file which was used to calculate those published Hash values...all options are equally possible).

The WB_16_03_0003.swi firmware file for Aruba 2920 I just downloaded provided me a calculated SHA 256 Hash equal to:

eb163c6b7506e7e377216ff1688fe0d10eac4db8eb0806d49c86553e99e2acd7

exactly as your calculated one.

So I have:

  • MD5 Hash: 93c01adcbc5daa4f17c2f8ccee7eb54c
  • SHA1 Hash: 165a03554f5200e8404ca49654c9a6267310b830
  • SHA256 Hash: eb163c6b7506e7e377216ff1688fe0d10eac4db8eb0806d49c86553e99e2acd7

instead of

 

  • MD5 Hash: ccff96bddc8aa15e72daf01c60c34f25
  • SHA1 Hash: 3c8883699ffa8d8a4662c45efbe68908243503c5
  • SHA256 Hash: fed4aad0d80ef555f9f23c1a754e80c774ec27ef364a186eac0a8ed4b02d59f7

 

ohauer
Occasional Contributor

Re: 2920 checksums for WB.16.03.0003 verification

Thanks for your verification!

Does anyone know an HPE/Aruba address that can be contacted ?

Michael Patmon
Trusted Contributor

Re: 2920 checksums for WB.16.03.0003 verification

I checked against our internal build system and the checksums that you calculated are the correct ones.  The web page was wrong and should now be corrected.  We are checking on how this could have occurred along with the other builds.  

Thank you for posting.  

ohauer
Occasional Contributor

Re: 2920 checksums for WB.16.03.0003 verification

Thanks for picking up this so quickly and also to verify the checksums agains your internal builds!