Cisco ASA 5505 - Manual (Page 1870)

82-14
Cisco ASA 5500 Series Configuration Guide using the CLI
Chapter 82 Troubleshooting
Common Problems
of less network traffic and fewer users. Debugging during these periods decreases the likelihood that
increased debug command processing overhead will affect system use. To enable debugging messages,
see the debug commands in the command reference.
Capturing Packets
Capturing packets is sometimes useful when troubleshooting connectivity problems or monitoring
suspicious activity. We recommend that you contact the Cisco TAC if you want to use the packet capture
feature. See the capture command in the command reference.
Viewing the Crash Dump
If the ASA crashes, you can view the crash dump information. We recommend contacting Cisco TAC if
you want to interpret the crash dump. See the show crashdump command in the command reference.
Coredump
A coredump is a snapshot of the running program when the program has terminated abnormally, or
crashed. Coredumps are used to diagnose or debug errors and save a crash for future off-site analysis.
Cisco TAC may request that users enable the coredump feature to troubleshoot application or system
crashes on the ASA. See the coredump command in the command reference.
Monitoring Per-Process CPU Usage
You can monitor the processes that run on the CPU. You can obtain information about the percentage of
CPU that is used by a certain process. CPU usage statistics are sorted in descending order to display the
highest consumer at the top. Also included is information about the load on the CPU per process, at 5
seconds, 1 minute, and 5 minutes before the log time. This information is updated automatically every
5 seconds to provide real-time statistics.You can use the show process cpu-usage sorted command to
find a breakdown of the process-related load-to-CPU that is consumed by any configured contexts.
Common Problems
This section describes common problems with the ASA, and how you might resolve them.
Symptom The context configuration was not saved, and was lost when you reloaded.
Possible Cause You did not save each context within the context execution space. If you are
configuring contexts at the command line, you did not save the current context before you changed
to the next context.
Recommended Action Save each context within the context execution space using the copy start run
command. Load the startup configuration as your active configuration. Then change the password
and then enter the copy run start command. You cannot save contexts from the system execution
space.