Specifications

3-474
Cisco Wide Area Application Services Command Reference
OL-16451-01
Chapter 3 CLI Commands
(config) kernel
(config) kernel
To enable access to the kernel debugger (kdb), use the kernel kdb global configuration command. To
disable access to the kernel debugger, use the no form of this command.
kernel kdb
no kernel kdb
Syntax Description This command has no arguments or keywords.
Defaults The kernel debugger is disabled by default.
Command Modes global configuration
Device Modes application-accelerator
central-manager
Usage Guidelines Once enabled, kdb is automatically activated if kernel problems occur, or you can manually activate it
from the local console for the WAAS device. Once activated, all normal functioning of the WAAS device
is suspended until kdb is manually deactivated. The kdb prompt looks like this:
[0]kdb>
To deactivate kdb, enter the go command at the kdb prompt. If kdb was automatically activated because
of kernel problems, the system generates a core dump and restarts. If you activated kdb manually for
diagnostic purposes, the system resumes normal functioning in whatever state it was when you activated
kdb. In either case, if you enter the reboot command, the system restarts and normal operation resumes.
kdb is disabled by default and you must enter the kernel kdb command in global configuration mode to
enable it. If kdb has been previously enabled, you can enter the no kernel kdb global configuration
command to disable it. When kdb is enabled, you can activate it manually from the local console by
pressing Ctrl-_ followed by Ctrl-B.
The WAAS device is often unattended at many sites, and it is desirable for the WAAS device to
automatically reboot after generating a core dump instead of requiring user intervention. Disabling the
kernel debugger allows automatic recovery.
Examples The following example shows how to enable, and then disable, access to the kernel debugger:
WAE(config)# kernel kdb
WAE(config)# no kernel kdb