Troubleshooting guide

1-60
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Monitoring and Troubleshooting Your WAAS Network
Troubleshooting Tools
For tests that fail, error messages describe the problem and provide recommended solutions.
You can run the same diagnostic tests again and refresh the results by clicking the Refresh icon in the
taskbar.
To print the results, click the Print icon in the taskbar.
Diagnostic Testing Using the CLI
You can use the test EXEC command to perform diagnostic and connectivity tests.
You can use network-level tools to intercept and analyze packets as they pass through your network. Two
of these tools are TCPdump and Tethereal, which you can access from the CLI by using the tcpdump
and tethereal EXEC commands.
The WAAS device also supports multiple debugging modes, reached with the debug EXEC command.
These modes allow you to troubleshoot problems from configuration errors to print spooler problems.
We recommend that you use the debug command only at the direction of Cisco TAC.
The output associated with the debug command is written to either the syslog file in /local1/syslog.txt
or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.
The output associated with the debug accelerator name module command for an application accelerator
is written to the file nameao-errorlog.current, where name is the accelerator name. The accelerator
information manager debug output is written to the file aoim-errorlog.current.
The debug log file associated with a module will be rotated to a backup file when the current file reaches
its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file
number.
For any debug command, system logging must be enabled. The command to enable logging is the
logging disk enable global configuration command, which is enabled by default.
If a debug command module uses the syslog for debug output, the logging disk priority debug global
configuration command must be configured (the default is logging disk priority notice).
If a debug command module uses the debug log for output, the output can be filtered based on a priority
level configuration for the four different levels of debug log output, as follows:
• For filtering on critical debug messages only, use the following global configuration command:
logging disk priority critical.
• For filtering on critical and error level debug messages, use the following global configuration
command: logging disk priority error.
• For filtering on critical, error, and trace debug level debug messages, use the following global
configuration command: logging disk priority debug.
• For seeing all debug log messages, which include critical, error, trace and detail messages, use the
following global configuration command: logging disk priority detail.
Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher
priority will be automatically written to the debug log associated with a module.
For more details on these CLI commands, see the Cisco Wide Area Application Services Command
Reference.