You could try an upgrade to the latest release in your particular train. Otherwise, I would suggest opening a TAC case and providing the output of 'show crash', 'show tech', and the syslogs to the engineer so the bug can be identified.
The original poster does not indicate what version of code is running on the 5505 and it might be nice to know that. And it might also help to know whether this ASA is a new install or whether it has been in use for a while (in which case has the version recently changed).
A traceback is an indication of some software problem. So I agree with MIke that there are 2 options:
- change the version of code running on the 5505. I agree that newer is usually better, but I believe that in this case falling back to an older version of code might also get around the problem.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...