We have a Cisco ASA5510 which came last year with the default software installed:
i have successfully configured the vpn and security rules etc.
i would now like to upgrade the asdm and asa software, so i downloaded all the new software levels from the appropriate part of the cisco website
i have managed to upgrade the asdm to 509 using the following process:
asdm image disk0:/asdm509.bin
If i try any other higher version such as 511 i get the error:
"Device Manager image set, but not a valid image file"
I have read that you can get this error and it doesn't matter, so if i continue and write the setting to flash and reboot - then i can't get into the asdm once it has rebooted.
I have also tried updating the boot system variable to later software (eg 711) as well as the asdm (611). When the system reboots it seems to see the new asa software but it will not boot it. it does not spit out any errors but keeps recycling back to the choice of booting in 10 seconds or press escape to stop, whereby i have to boot it back into the 708 level of the software from the rommon# command line
i am not using tftp (which i don't believe is so necessary anymore) and i used the asdm to upload the newer downloaded files from my laptop to the device. are there any more checks that i can make to verify the software other than filesize?
what further options have i got?
ASDM 5.2(5) is only compatible with ASA 7.2. Therefore, can you try the following.
1. First change the boot parameters to point to the 7.2 file:
no boot system disk0:/asa708-k8.bin
boot system disk0:/asa724-k8.bin
2. Reboot the ASA, verifiy that it boots into 7.2(4) in the output of "show version".
3. Once it boots into 7.2(4), please change your ASDM image:
asdm image disk0:/asdm-525.bin
Please let us know your findings, thanks.
Quick question for you. You mentioned the following:
i have followed the directions to upgrade from asa 708 to asa 711 and from asdm 509 to 511(with both the CLI and the GUI) and it does not seem to work properly, this resulted in a perpetual rebooting process whereby i could only stop it by escaping from the boot process at the 'rommon:' prompt to force it to boot back into the asa 708.
Did you experience the perpetual reboot when the ASA image was changed from 708 to 711 (with the "boot system" command), or when the ASDM image was changed from 509 to 511 (with the "asdm image" command)? Please let me know.
Thanks in advance.