You are seeing the results of a PIX crashing. My suggestion would be to go ahead and capture all of the info sent to the console by the PIX during a reload cycle and open a TAC case. They can decode the traceback and start digging in to find out where the issue actually is. One thing you may be able to also do is disconnect all of the cables on the PIX and reload it. See if the PIX crashes in this setup as well. If it does not, we have a pretty good idea that the crash is being caused by something traffic related. Sorry for the vague answer, but this is something that is better handled via a TAC case than on this forum. Good luck!
Please do not let this concern you. We have bugs in every version of code that can cause a traceback to occur (even 5.2(5)). Most crashes or bugs are related to a specific traffic pattern triggering an event in the PIX or hardware issues. We have *many* people running 6.3(3) code without a problem. If you need any of the new features in the 6.3(3) code, then by all means, an upgrade should be fine. For backup purposes, make sure you have a good copy of 5.2(5) on your TFTP sevrer as well in case you need to roll back. Good luck!
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :