It would be great if there were more guides that would help with the interpretation of debug output.
On a similar note - I see in the Debug Master Reference for IOS gives examples and some explanation to these. It would be good if there was example output and some explanation for the PIX/ASA guides as well.
Thanks for your feedback and sorry it's taken us awhile to research this.
If you haven't already checked the debug section of the Cisco ASA 5500 Series Command Reference http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/d1.html, you may find some useful information there, but admittedly the level of detail varies from command to command. Historically, product management has preferred to have Cisco TAC assist customers in debugging because of the performance impact on the system. Our understanding is that this is why self-sufficient debug documentation has not been a priority.
However, we have passed your comment along to the ASA/PIX group and it will be considered in the next reevaluation of documentation scope.
What do you do if you think you're running into a bug? Cisco makes it
possible for you to report bugs yourself. Learn how, and find out how
your contributions help us improve our software.Cisco publishes its
bugs. Before opening a TAC Support Case, use Bu...
Cisco Licensing is pleased to announce the new Licensing Portal. It
provides customers with an enhanced self-service experience by
stream-lining and automating many licensing activities. Please take a
moment to familiarize yourself with the features that ...