debug

Identifies an CNA subsystem to be debugged and causes CNA to begin generating debug messages for that system.

debug <subsystem>
 
no debug [ <subsystem> ]
 

• subsystem--name of the CNA subsystem to be debugged (can be any argument listed under debug on command, except all and services)

Must be in configuration mode (config), which requires privileged-level access.

The debug command adds a line to the running configuration which causes the specified subsystem of the CNA operating system to begin generating debug messages. Under normal operating conditions, these messages are undesirable because of their volume and the frequency with which they are generated. But they can be valuable in debugging or understanding unexpected behavior.

The debug command by itself only initiates the generation of the messages. It does not cause the messages to be sent to a destination, or to be displayed. You need to tell the operating system where the messages should be directed. This allows you to open multiple terminal displays or CLI sessions, with debug messages going to some, while others show normal program output.

There are three related commands that regulate access to debug information generated by CNA. The commands are:

• debug--causes the specified subsystem to begin generating debug messages
• debug on--causes CNA to send log messages for the specified subsystem to the current terminal session
• debug display--determines whether debug messages are intermingled with normal program output

Use the no form of the debug command to deactivate generation of debug messages for the specified subsystem. If no subsystem is specified, all debug messages will be deactivated.

To determine whether debugging messages are being generated for a subsystem, you will need to inspect the running configuration for the presence of a debug command which specifies that subsystem. The show debugging command lists the display status for the current session only.

See also the logging on command.