Comware R2612P02US Corrupted file

[XMK]

Greetings, 

I am evaulating a feature and I was about to try Comware release 2612P02-US. After download the zip file from official site, the size and md5 sum of zip matched with the one on hpe site.

ls -alh 5940_7.10.R2612P02-US.zip
-rw-r--r--. 1 root root 156M Mar 14 2019 5940_7.10.R2612P02-US.zip

md5sum 5940_7.10.R2612P02-US.zip | grep -i DAF14D9E0FE15020500E304CD869E86B
daf14d9e0fe15020500e304cd869e86b 5940_7.10.R2612P02-US.zip

To avoid any sort of loss during transfer to swich, I did a md5 check of the IPE file.

md5sum 5940-CMW710-R2612P02-US.ipe
acf1107194fdd9a1a399df9b868583b1 5940-CMW710-R2612P02-US.ipe

And once again on switch

<HPE>md5sum flash:/5940-CWM710-R2612P02-US.ipe
MD5 digest:
acf1107194fdd9a1a399df9b868583b1

But when I try to actually isntall this image, I receive an error that it is damaged

<HPE>boot-loader file flash:/5940-CWM710-R2612P02-US.ipe slot 1 back
up 
Verifying the file flash:/5940-CWM710-R2612P02-US.ipe on slot 1...Failed.
File is bad or damaged.

The "chinese" version does not have this issues, but it is also much larger ~130M comared to "US" version which is only around 96M

-rw-r--r--. 1 root root 96M Dec 20 11:49 5940-CMW710-R2612P02-US.ipe
-rw-r--r--. 1 root root 130M Sep 30 10:16 5940-CMW710-R2612P02.ipe

Can somebody confirm if they receive same values (md5sums)

[cgu]

no direct response to your problem here, but you could try to decompress the ipe file on your computer and send the 2 firmware files on the switch and install them to see if it also complains about corruption.

[parnassus · Accepted solution]

I think I found where the issue is.

The zipped file (archive) 5940_7.10.R2612P02-US.zip once decompressed will create the 5940_7.10.R2612P02-US folder with this structure:

├── 5940-cmw710-packet-capture-r2612p02-US.bin
├── 5940-CMW710-R2612P02-US.ipe
├── Comware V7 HPE 5930 & 5940 MIB Companion.pdf
├── HPE_NETCONF
│   ├── HPE Comware 7 NETCONF XML API Reference.pdf
│   └── Word
|       ├── Comware V7 ACL NETCONF XML API Configuration Reference.docx
│       ├── ...
|	└── Comware V7 WLOC NETCONF XML API Data Reference.docx
└── Manifest.txt

Now notice the Manifest.txt, it contains the SHA256 checksums for both the 5940-CMW710-R2612P02-US.ipe and 5940-cmw710-packet-capture-r2612p02-US.bin files. Declared checksum SHA256 for 5940-CMW710-R2612P02-US.ipe is:

ac36fc2f5f4133e70e270b8c8c84a1f72966c8de5880c7715ea3fdf3c7097559

I verified the SHA256 checksum of the file 5940-CMW710-R2612P02-US.ipe with the one above and they don't match.

Mine indeed is:

a44df5688ad9b31298a0fa3e2fc5dca52b5c0d4991979d8961f088bad0faef15

So the issue is the validity of the 5940-CMW710-R2612P02-US.ipe file itself -> call or open a support ticket to HPE.

It's curious that, instead, checksums of the other file - 5940-cmw710-packet-capture-r2612p02-US.bin - match.

@cguhope to not misunderstood you...but AFAIK IPE files can't be "decompressed" (extracted) by a mechanism external to the Comware switch (Comware 7 switches have the command to do so)...so if you want to check the validity of downloaded ipe file the only way to do that before uploading the entire ipe file to the switch is to validate its published checksum against what is reported on Manifest.txt.

[cgu]

You are right about the ipe files, my bad.

[XMK]

Thanks for taking time to validate, I am about to open a case regarding some other feature, and it will be a good opportunity to mention about this one also.