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.
What's the command for removing old image (no boot image or ...I tried that but it isn't accepted by ASA). What will happen if I remove all images from disk and leave just 8.2 version. The problem is that I can go tomorrow on the site to take sh run and config. But I belive you are right for not removing old image from booting. What I shoud do?
Thanks for quick answers. I will go tomorrow on site and grab sh run and other info to discuss.
Tips for 8.3 version: The NAT is different, network objects with network ranges are great thing,...BUT I found that this version has higher security because we couldn't ping outside interface, vpn didn't work, etc. (we permited everything, icmp on policy, acl on outside interface...). When we downgrade on 8.2(2) version ASA erased NAT and some acl with network object (ranges), and after configuring with old way everything worked like a charm till above problem.
I am new to ASA and maybe I just didn't write the right line, but I think that 8.2 version is stable for working.
After sh run boot I noticed that 8.2 and 8.3 versions are both there for booting. With no boot system disk0:/8.3 I removed it. ASA is still working without any problem.I hope that there won't be any problems. Thanks again.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...