- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Calculating a lost EVA WWN checksum value
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Report Inappropriate Content
тАО02-09-2010 05:02 AM
тАО02-09-2010 05:02 AM
Calculating a lost EVA WWN checksum value
We've got an old EVA 4000. It's been moved from its original rack (by people other than me), so we longer have the EVA WWN and checksum label, or even the EVA serial number!
It's initialized now, so we know the WWN, but we don't know the checksum. If we re-initialize the array it'll ask for the checksum, but we don't know it.
Is the algorithm for calculating the EVA checksum publicly known?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2010 06:15 AM
тАО02-09-2010 06:15 AM
Re: Calculating a lost EVA WWN checksum value
The storage team on your country should be able to find the article and link to the checksum generator.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2010 03:00 AM
тАО02-10-2010 03:00 AM
Re: Calculating a lost EVA WWN checksum value
Well - you could guess!
But that I mean start at AA, then AB, then AC and so on. It will take a while!! but if you go through all the combinations you should get there eventually!!
However you would have to uninit the EVA first which would not be good !!
Probably better stick with the above answer then...
Mark...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2010 06:42 AM
тАО02-10-2010 06:42 AM
Re: Calculating a lost EVA WWN checksum value
I don't understand why HP would view this as commercially sensitive information.
Anyway, I'll see if I can get hold of some support people with clue to get the required information... Thanks for the responses.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2013 02:20 PM
тАО04-26-2013 02:20 PM
Re: Calculating a lost EVA WWN checksum value
.... brauche dringen d die checsumme wwn 21 00 00 1B 32 13 FF 9E /SN RFC0821M85887
oder wwn 50 01 43 80 00 C4 D6 80 P/N AE311- 60001
mfg webmaster@glauben.de
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2014 09:07 AM
тАО04-12-2014 09:07 AM
Re: Calculating a lost EVA WWN checksum value
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2020 08:18 AM
тАО05-26-2020 08:18 AM
Re: Calculating a lost EVA WWN checksum value
First of all my long story in a short form:
We used to have about 10 EVA 8100 storages for almost 10 years in our production environment and I personally like them very much. We had a lot of spare parts, typical configuration (168x450GB/15K) and my job was just about to replace failed drives and add it to existing groups.
Anyway times go on, performance metrics, datacenters space and energy price matters, so our "EVA beasts" were all replaced by some IBM stuff. Actually we left one EVA 8100 in some remote location - it was fine since some planned power maintenance which required shutdown of all IT stuff, including EVA. It wasn't a nice surprice when storage asked for a WWN/checksum after powering it up again. My coleagues doing this operation were completely astonished. I had some notes about checksum (I used to note down such informations), but unfortunately I was like "10 timezones away from home" having first day of my holiday...
Finaly data was restored from backup and I found WWN/checksum when I was back at work, but we were fealing uncomfortable, so we decided to build some EVA CHECKSUM CRACKER. Let me show it for those who still love EVA 8100 storages.
EVA 8100 controller "desktop version" with front panel connected to ParpberryPi zero (radiometrix and some other stuff is from another project):
Python script (most of the code - main loop - done by friend of mine Pawel):
Checksum bruteforceing for a given WWN:
Script in (successful) action:
The script tries all checksum combinations for a given WWN checking some LED on front panel. What took me quite a long time was tuning of how fast RaspberryPi can "click" - our cracker have some proven delays between "clicks" to not drop anything which happen when you go too fast (it was designed for human and "finger operation").
PS: If you recognize pcb below it means you have been looking for some way to reprogram EVA 8100 battery. You may find some movie on Youtube about how to clear PIC eeprom for EVA4400 battery (by Christian from Switzerland). Unfortunatelly I still can't do this for 8100