Generic debug commands

The following generic debug commands perform functions related to all debugging actions:

  • debug ? - Generates a list of debug options.
  • show debug - Shows all enabled debug settings.
  • debug destination - Allows you to select an output destination: Telnet, SSH, console, or logging (default).

debug ?

Syntax: debug ?

The debug ? command generates a list of available debug variables.

Attention: Many first-level variables have their own variable subsets. When you enter a debug command, the system indicates that there are additional variables available and you have entered an incomplete command. Add a space and a question mark to your original command to view the additional variables.
device# debug vlan?
vlan Enable/Disable VLAN debug

show debug

Syntax: show debug

This command displays all the enabled debug functions. The output resembles the following example, which shows that VLAN debugging is enabled, with the console as the output destination.

device# show debug
Debug message destination: Console
VLAN
VLAN: debugging is on

debug destination

Syntax: no debug destination [ console | logging | telnet num | ssh num ]

This command displays all the enabled debug functions. The output resembles the following example, which shows that VLAN debugging is enabled, with the console as the output destination.

  • console - Directs output to the system console.
  • logging - Directs output to the syslog buffer and to the syslog server (default).
  • telnet num - Directs debugging output to a specified Telnet session (a number from 1 through 5).
  • ssh num - Directs debugging output to a specified SSH session (a number from 1 through 5).

This command allows you to specify a destination for debugging output. The default destination is the system console, but you can redirect output to a syslog buffer, Telnet session, or SSH session.

To send debug output to a Telnet session, first determine your session number using the show who command.

device# show who
Console connections (by unit number):
1 established
4 minutes 29 seconds in idle
Telnet connections (inbound):
1 established, client ip address 172.31.0.1
you are connecting to this session
2 seconds in idle
2 closed
3 closed
4 closed
5 closed
Telnet connection (outbound):
6 closed
SSH connections:
1 closed
2 closed
3 closed
4 closed

This example indicates that you are connected through active Telnet session 1. To redirect the debug output to your Telnet session, enter the following command.

device# debug destination telnet 1