Does the presence of the crashinfo file below indicate that my PIX has experienced an error it could not recover from (and so it reloaded itself to restore service) ? Or is it possible that the PIX lost power ?
If a PIX loses power does it generate the crashinfo file ?
Piaras Walsh, Ireland
pix_device# show crashinfo
Thread Name: Dispatch Unit (Old pc 0x001fe7c6 ebp 0x014d7b44)
I have come across this crash trace back with a scenario involving H.225 traffic going through the PIX. Do you have a lot of H.225 traffic on this PIX? Also, if you do not need inspect h225, would you be able to disable it and see if the problem is seen again?.
But up to my knowledge, I would suggest you to consider upgrading to a interim release with bug-fixes and monitor.
I just had the same problem. After upgrade the both PIXes crashed in 1-2 min after rebooting every time. We're tried to fix bug when PIX crash after failing failover interface. It was necessary to downgrade back to 7.0(4). Now I think version 7.0(5) is the best choice in my case. Am I right?
I have been advised by TAC that the problem which causes the traceback shown above is resolved in 7.0.5 and 22.214.171.124. Alternatively I have been told that switching off HTTP inspection if running 7.1.2 will prevent the PIX from crashing. I am upgrading the production PIX this week. I will update this thread with the results.
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...