Forum Discussion
NimbostratusFun with uploading software ISO/HF to 11.x via generic file transfer interface
Howdy all,
Using (pretty much verbatim) the perl file transfer example provided on the codeshare, I did a test upload of a hotfix (Hotfix-BIGIP-11.3.0-3117.0-HF5.iso). The transfer completed and I got on the box to view the image in TMSH to make sure that everything was copacetic.
Well, I goofed and did a tmsh list sys software images instead of hotfix. Here's what I got:
[root@gns1:Active:Standalone] images t li sy so im
sys software image BIGIP-10.2.3.112.0.iso {
build 112.0
build-date "Fri Sep 30 00 04 48 PDT 2011"
checksum 53b2bf21a656c135d6de61f8e5fea660
file-size "925 MB"
last-modified "Mon Apr 23 17:39:31 2012"
product BIG-IP
verified yes
version 10.2.3
}
sys software image BIGIP-11.2.0.2446.0.iso {
build 2446.0
build-date "Tue May 29 22 02 24 PDT 2012"
checksum 5a476a03678d3465de16cff3ee8a67f9
file-size "1127 MB"
last-modified "Thu Dec 13 15:53:34 2012"
product BIG-IP
verified yes
version 11.2.0
}
sys software image Hotfix-BIGIP-11.3.0-3117.0-HF5.iso {
build none
build-date none
checksum ERROR
file-size "272 MB"
last-modified "Wed Jun 5 12:53:06 2013"
product none
verified no
version none
}
Well, that doesn't look right! I hadn't yet realized that I had goofed, so the fact that a hotfix is displayed in the images list didn't register with me at that point. So:
[root@gns1:Active:Standalone] config cd /shared/images
[root@gns1:Active:Standalone] images md5sum Hotfix-BIGIP-11.3.0-3117.0-HF5.iso
fe1d80c100d3d95769083e3eed214149 Hotfix-BIGIP-11.3.0-3117.0-HF5.iso
The MD5 Sum matches the one on the downloads site. Ok. Then I realize that I goofed, so I do the list sys software hotfix, realizing that a hotfix shouldn't be displayed in the images list. Pay attention to the MD5 sum of the file on the hotfix list (doesn't match, but F5 thinks everything is good):
[root@gns1:Active:Standalone] images t li sy so hot
sys software hotfix Hotfix-BIGIP-10.2.3-123.0-HF1.iso {
build 123.0
checksum 5b154ff50bbf9282f2249a349fece86a
id HF1
product BIG-IP
title "Hotfix Version 123.0"
verified yes
version 10.2.3
}
sys software hotfix Hotfix-BIGIP-11.2.0-2713.0-HF3.iso {
build 2713.0
checksum aff586eb55d6ac95df12c91f8aca00a7
id HF3
product BIG-IP
title "Hotfix Version 2713.0"
verified yes
version 11.2.0
}
sys software hotfix Hotfix-BIGIP-11.3.0-3117.0-HF5.iso {
build 3117.0
checksum e57c8676fdc10d4df01b1e2a4b4a3764
id HF5
product BIG-IP
title "Hotfix Version 3117.0"
verified yes
version 11.3.0
}
Methinks that something's afoot.
Any input or theories from the Guru's or anyone else?
Thanks,
Chris
3 Replies
El_JefeI think maybe you uploaded a hotfix as an image? You used to be able to do this through the GUI if you aren't watching what you are doing.
Faintly_LuckyThat's an interesting theory and I think that it might be part of the issue, but I used the generic file upload method in system/configysnc because I couldn't find any method for doing so in the software management interface. I combed over the SDK looking for something like it and wasn't able to find anything. Did you find something? Am I not looking in the right interface?
Michael_YatesTake a look at this thread: MD5 checksum from System::SoftwareManagement.get_software_image
It appears that the BIG-IP's Checksum Values do not match the CLI Checksum, probably because of something the system is doing with the file before it runs its checksum.
