Can anyone tell me the boot behavior of the PIX when it comes to recovering from a corrupt/invalid image in flash?
Example: In flash I have 2 images:
What (if possible) are my options to have 2 images and a boot sequence so it tries a specific image first. This would be useful in an upgrade situation in case the newly applied image is corrupt or for any other reason can't boot the PIX.
This may be the default behavior - I'm just looking for confirmation or more details. Do I specify it using: "boot system flash:/image1.bin" and then will it try another if "image1.bin" is not successful?
Sorry about that - I'm running v 8.0(3) on a PIX 525.
One issue I'm going to have is that the PIX only has 16MB of flash and between the ASDM and the Image itself I don't have enough room to store an alternate system boot image. Not sure if it's upgradable to 32mb+ I'll have to check. (Obviously I could always delete the asdm image and clear room for an upgrade - just thinking longer term.)
After reading the link you provided I'm still unclear on the "boot system flash:/pix803.bin" syntax. Can I enter multiple flash locations (repeat that command) or do I have to select a different location/medium? It seems the PIX525 can't boot from TFTP(?).
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...