debug etherchannel
To enable debugging of EtherChannels, use the
debug etherchannel
command in privileged EXEC mode.
To disable debugging, use the
no
form of the command.
debug etherchannel
[
all | detail | error | event | idb
]
no debug etherchannel
[
all | detail | error | event | idb
]
Syntax Description
(Optional) Displays all EtherChannel debug messages.
all
(Optional) Displays detailed EtherChannel debug messages.
detail
(Optional) Displays EtherChannel error debug messages.
error
(Optional) Displays EtherChannel event messages.
event
(Optional) Displays PAgP interface descriptor block debug messages.
idb
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Modification
Release
This command was introduced.
Cisco IOS XE 3.2SE
Usage Guidelines
The
undebug etherchannel
command is the same as the
no debug etherchannel
command.
Although the
linecard
keyword is displayed in the command-line help, it is not supported.
Note
When you enable debugging on a stack, it is enabled only on the active controller. To enable debugging on
the standby controller, start a session from the active controller by using the
session switch-number
command
in privileged EXEC mode. Enter the
debug
command at the command-line prompt of the standby controller.
To enable debugging on the standby controller without first starting a session on the active controller, use the
remote command switch-number LINE
command in privileged EXEC mode.
Examples
This example shows how to display all EtherChannel debug messages:
Controller#
debug etherchannel all
Layer 2/3 Command Reference, Cisco IOS XE Release 3E (Cisco WLC 5700 Series)
20
OL-32323-01
Layer 2/3 Commands
debug etherchannel