Obviously everybody's experience has been different but I have been running very nicely on 8.0.x code. I am running on the latest interim code on both ASAs and PIXs due to a security flaw though. (knock on wood) It has been very stable. 7.2.4 code was very buggy for me. I was upgrading probably every other month due to bugs until we jumped to 8.x code a while ago.
Justin, I believe I saw your posts on the RANCID list and although the 8.2 coredump problem can be a pain you can modify your rancid script to ignore the coredump file when rancid does a show flash. I do this for dhcp snooping since the db is small enough that I can keep it in flash. (Yes I know about the warning that they give when you configure like this) Every time a lease expires or a new lease is distributed the file is updated which would make rancid grab the change. Nick -----Original Message----- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Justin Shore Sent: Friday, September 25, 2009 9:09 AM To: Antonio Soares Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] ASA5520 which image should I use? Antonio Soares wrote: > Stay away from 8.2. We are experiencing crashes since July (TAC case > involved). Tomorrow we will install 8.2.1-10 to see if finally > we get rid of this. I've had good luck with 8.2.1-3 for our purposes. Any 8.2 prior to that has that nasty coredump feature that writes to flash every time you do a 'sh run' (RANCID users beware). Justin _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
