- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- 2920 checksums for WB.16.03.0003 verification
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-30-2017 12:07 PM
01-30-2017 12:07 PM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-30-2017 03:42 PM
01-30-2017 03:42 PM
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
I'm not an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-30-2017 08:22 PM
01-30-2017 08:22 PM
Re: 2920 checksums for WB.16.03.0003 verification
Thanks for your verification!
Does anyone know an HPE/Aruba address that can be contacted ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-30-2017 09:08 PM
01-30-2017 09:08 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-30-2017 10:35 PM
01-30-2017 10:35 PM
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!
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP