Forum Discussion
Different file size and checksum for BIG-IP images
Hi,
Is it normal that BIG-IP image files are different size on active and standby units in a cluster (same hardware platform):
[jay@F5-4000-a:Active:In Sync] images ls -la | grep 11.4.1.608
-rw-r--r-- 1 root root 1484894208 Oct 30 02:59 BIGIP-11.4.1.608.0.iso
[jay@F5-4000-b:Standby:In Sync] images ls -la | grep 11.4.1.608
-rw-r--r-- 1 tomcat tomcat 1575387136 Mar 11 2014 BIGIP-11.4.1.608.0.iso
Both units are in active/standby cluster and failover works.
Cheers, Jay
- R_MarcNimbostratus
One of them is likely a partial transfer (potentially both). There should be a checksum on the download site that you can validate the images against. This has nothing, necessarily, to do with what is actually installed.
if you see this with ls then there is no cosmetic bug.
as R Marc suggests use md5sum (i.e. md5sum BIGIP-11.4.1.608.0.iso) on them and compare with the official value, which should be 8466e36299a680637277b7baeffd7e00. they should match and if they don't then your are best of with reuploading.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com