Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SA 5510 problems-booting old image?

Status
Not open for further replies.

Kockalone

Technical User
Dec 10, 2009
13
RS
We have ASA 5510 running 8.2(2) image on asdm-631. When we upgraded from ver 7 to 8.3 we used command ASA5510# rename asa706-k8.bin asa706-k8.old. After upgrade to 8.3 version and asdm-6.3 we didn't accomplished to ping outside interface, make vpn to work, although we permitted everything. So we decided to downgrade to 8.2(2) version with same asdm-6.3 and after few modifications (vpn,NAT,access lists) everything worked fine.

But just one day :-(.

The problem is that ASA booted old 706-k8.bin version and asdm-5.0. The whole room is on UPS and I don't think it's a power failure?

Cant it reboot by it self for some reason?

We used command boot system disk0:/asa8.2?k8.bin , asdm image disk0:/asdm?6.3.bin and wr to write to memory.

And the same problem after rebooting happend when there was 8.3 version. After power failure maybe or just by it self ASA booted old images?

What will happen if we erase all images and asdm and leave just 8.2 and 6.3 version.

I don't know what to do?Any suggestions?
 
I would try looking at the output of "show boot" through the CLI, or check the boot options under Configuration > Device Management > System Image/Configuration > Boot Image/Configuration in the ASDM. Make sure that the 8.2 image is set as the 1st boot image and that the latest ASDM image (6.3) is set as the ASDM image ("show asdm image", also shown in "show config" under "adsm image disk..." ).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top