Firmware asa805-k8 was installed and saved on an ASA5505. Upon power failure the ASA5505 reverts to an older firmware,
asa724-k8. 1) Is it normal for ASA5505's to revert to older version upon power failure. 2) ASDM/web browser doesn't work using IE--username and password brings to empty screen. Kindly advise on how to revert back to later image. Thank you.
# sh ver
Cisco Adaptive Security Appliance Software Version 7.2(4)
Device Manager Version 5.2(4)
Compiled on Sun 06-Apr-08 13:39 by builders
System image file is "disk0:/asa724-k8.bin"
Config file at boot was "startup-config"
# sh disk
Initializing disk0: cache, please wait.......Done.
-#- --length-- -----date/time------ path
6 8515584 Mar 20 2009 10:11:18 asa724-k8.bin
7 4181246 Mar 20 2009 10:12:18 securedesktop-asa-22.214.171.124-k9.pkg
8 398305 Mar 20 2009 10:12:42 sslclient-win-126.96.36.199.pkg
9 6514852 Mar 20 2009 10:14:38 asdm-524.bin
12 0 Mar 20 2009 10:18:44 crypto_archive
13 0 Aug 01 2011 21:48:34 log
43 13934592 Aug 01 2011 22:34:24 asa805-k8.bin"
Issue the command
"show run boot"
Make sure that the command for the old image doesnt exist. When you configure new image with "boot system" command the old WONT be removed. You either need to remove the old command manually or remove the image file from flash.
# sh run boot
boot system disk0:/asa805-k.bin "
Yet the sh ver command output: "...System image file is "disk0:/asa724-k8.bin"..."
I haven't personally run into any problems with images unless I have made some configuration mistake or I have been provided with wrong image file (though for that you get a warning message from the firewall)
I imagine if you can only see the new image with the "show run boot" command it should use that during boot up.
I presume you have saved the configuration to the startup configuration so it would try to boot up with the new one.
I can't be 100% sure but I'd imagine if there was some problem with the actual new software image file it wouldnt let you configure it as a boot image.
Might be a good idea to try to copy it to the ASA again or maybe even try some other ASA software, like 8.2 which is the last one before the NAT changes that come from 8.3 and forward.
Also in a situation where the ASA has no "boot system" command lines I think the OS files are just gone through in order and the ASA would use the first one to boot up with. But cant be 100% sure again.
If possible, you could try booting up the ASA with the new software and having a console connection to it while its booting up and look for any error messages.
I dont know if I would remove the old image alltogether without atleast adding several software images to the ASA. If there could be some problem with the new image and it was only one on the Flash it might lead to having an ASA that cant boot up and you would have to load an imagine file to the ASA again.