Table Of Contents

debug cca

debug condition interface

debug condition standby

debug condition vlan

debug earl

debug ehsa

debug entry

debug etherchnl

debug ethernet-interface

debug fastethernet

debug fm

debug gssapi

debug icc

debug iccshim

debug interface

debug ipc

debug ip rgmp

debug l2-mgr events

debug l3-mgr

debug local-ack

debug ltl

debug mergeapi

debug mls ip multicast

debug mls rp

debug monitor

debug msc

debug netdr

debug nvram

debug pagp

debug pf

debug pm

debug priority

debug qm

debug qm-sp

debug rpc

debug scp

debug smf updates

debug spanning-tree

debug spanning-tree backbonefast

debug spanning-tree switch

debug spanning-tree uplinkfast

debug sw-vlan

debug sw-vlan ifs

debug sw-vlan notification

debug sw-vlan vtp

debug tcam

debug udld

debug vacl

debug vlog

define interface-range

diagnostic level

disconnect qdm

do

dot1x default

dot1x max-req

dot1x multi-hosts

dot1x port-control

dot1x reauthentication

dot1x system-auth-control

dot1x timeout

duplex

22

debug cca

To debug CCA register activity, use the debug cca command. Use the no form of this command to disable debugging output.

debug cca

no debug cca

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to debug CCA register activity:

Router# debug cca

CCA debugging is on

Router#

Related Commands

undebug cca (same as no debug cca)

debug condition interface

To limit the debugging output of interface-related activities, use the debug condition interface command. Use the no form of this command to disable debugging output.

debug condition interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id group-number}}

no debug condition interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id group-number}}

---

Note The vlan keyword for the debug condition interface command is only supported on the MSFC and can be entered only from the router console.

---

Syntax Description

interface	(Optional) Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan.
interface-number	(Optional) Module and port number; see the "Usage Guidelines" section for valid values.
null interface-number	Limits debugging to null interfaces; the valid value is 0.
port-channel number	Limits debugging to port-channel interfaces; see the "Usage Guidelines" section for valid values.
vlan vlan-id	Limits debugging to VLANs; see the "Usage Guidelines" section for valid values.
group-number	VLAN group number; valid values are from 0 to 255.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(3a)E3	The number of valid values for port-channel number was changed; see the "Usage Guidelines" section for valid values.
12.1(11b)E	This command was changed to include the pos, atm, and ge-wan keywords.

Usage Guidelines

The number of valid values for port-channel number depends on the software release. For releases prior to Release 12.1(3a)E3, valid values are from 1 to 256; for Releases 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Release 12.1(5c)EX and later support a maximum of 64 values ranging from 1 to 256.

The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module installed in a 13-slot chassis, valid values for the module number are from 2 to 13 and valid values for the port number are from 1 to 48.

If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.

Examples

This example shows how to limit debugging output to VLAN interface 1:

Router# debug condition interface vlan 1

Condition 2 set

Router#

Related Commands

debug interface
undebug condition interface (same as no debug condition interface)

debug condition standby

To limit the debugging output of Hot Standby Router Protocol state changes, use the debug condition standby command. Use the no form of this command to disable debugging output.

debug condition standby {{interface interface-number} | {port-channel number} | {vlan vlan-id group-number}}

no debug condition standby {{interface interface-number} | {port-channel number} | {vlan vlan-id group-number}}

Syntax Description

interface	(Optional) Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, atm, and ge-wan.
interface-number	(Optional) Module and port number; see the "Usage Guidelines" section for valid values.
port-channel number	Limits debugging output to port-channel interfaces; see the "Usage Guidelines" section for valid values.
vlan vlan-id	Limits debugging output to a VLAN interface; see the "Usage Guidelines" section for valid values.
group-number	VLAN group number; valid values are from 0 to 255.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(3a)E3	The number of valid values for port-channel number was changed; see the "Usage Guidelines" section for valid values.
12.1(11b)E	This command was changed to include the pos, atm, and ge-wan keywords.

Usage Guidelines

The number of valid values for port-channel number depends on the software release. For releases prior to Release 12.1(3a)E3, valid values are from 1 to 256; for Releases 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Release 12.1(5c)EX and later support a maximum of 64 values ranging from 1 to 256.

The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module installed in a 13-slot chassis, valid values for the module number are from 2 to 13 and valid values for the port number are from 1 to 48.

If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.

If you attempt to remove the only condition set, you will be prompted with a message asking if you want to abort operation. You can press n to abort or y to proceed with removal. Removing the only condition set may cause an excessive number of debugging messages.

Examples

This example shows how to limit the debugging output to group 0 in VLAN 1:

Router# debug condition standby vlan 1 0

Condition 3 set

Router#

This example shows the display if you try to turn off the last standby debug condition:

Router# no debug condition standby vlan 1 0

This condition is the last standby condition set.

Removing all conditions may cause a flood of debugging

messages to result, unless specific debugging flags

are first removed.

Proceed with removal? [yes/no]: n

% Operation aborted     

Router#                           

Related Commands

undebug condition standby (same as no debug condition standby)

debug condition vlan

To limit the VLAN debugging output to a specified VLAN, use the debug condition vlan command. Use the no form of this command to disable debugging output.

debug condition vlan {vlan-id}

no debug condition vlan {vlan-id}

Syntax Description

vlan-id

Number of the VLAN; see the "Usage Guidelines" section for valid values.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

If you attempt to remove the only VLAN condition set, you will be prompted with a message asking if you want to abort operation. You can press n to abort or y to proceed with removal. Removing the only condition set may cause an excessive number of debugging messages.

If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.

Examples

This example shows how to limit debugging output to VLAN 1:

Router# debug condition vlan 1

Condition 4 set

Router# 

This example shows the display if you try to turn off the last VLAN debug condition:

Router# no debug condition vlan 1

This condition is the last vlan condition set.

Removing all conditions may cause a flood of debugging

messages to result, unless specific debugging flags

are first removed.

Proceed with removal? [yes/no]: n

% Operation aborted     

Router# 

Related Commands

undebug condition vlan (same as no debug condition vlan)

debug earl

To enable debugging of EARL activity, use the debug earl command. Use the no form of this command to disable debugging output.

debug earl {L2 aging | L2 events | L3 aging | L3 control | L3 netflow}

no debug earl {L2 aging | L2 events | L3 aging | L3 control | L3 netflow}

Syntax Description

L2 aging	Enables debugging of EARL Layer 2 aging.
L2 events	Enables debugging of EARL Layer 2 events.
L3 aging	Enables debugging of EARL Layer 3 aging.
L3 control	Enables debugging of EARL Layer 3 control events.
L3 netflow	Enables debugging of EARL Layer 3 NDE.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

This command is supported by the supervisor engine only and can be entered only from the Catalyst 6500 series switch console (see the remote login command).

Examples

This example shows how to enable debugging of EARL events and provides a sample of the output:

Switch-sp# debug earl L2 events

EARL5 events debugging is on

Router#

*Sep 29 13:31:04: SP: cafe_general_isr: EARL5 INT

*Sep 29 13:31:04: SP: cafe_general_isr: intr source 0x4 with mask 0x3FEC6

*Sep 29 13:31:04: SP: cafe_general_isr: NMI intr source 0x3

.

.

.

Switch-sp#

Related Commands

undebug earl (same as no debug earl)
remote login

debug ehsa

To enable debugging of EHSA activity, use the debug ehsa command. Use the no form of this command to disable debugging output.

debug ehsa {all | config_sync | fsm | general}

no debug ehsa {all | config_sync | fsm | general}

Syntax Description

all	Enables debugging of all EHSA events.
config_sync	Enables debugging of EHSA configuration synchronization.
fsm	Enables debugging of EHSA FSM.
general	Enables debugging of EHSA general events.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

This command is supported by the supervisor engine only and can be entered only from the Catalyst 6500 series switch console (see the remote login command).

Examples

This example shows how to enable debugging of general EHSA events:

Switch-sp# debug ehsa general

EHSA general debugging is on

Switch-sp#

Related Commands

undebug ehsa (same as no debug ehsa)
remote login

debug entry

To debug incoming queue entries, use the debug entry command. Use the no form of this command to disable debugging output.

debug entry

no debug entry

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable debugging of incoming queue entries:

Router# debug entry

Incoming queue entry debugging is on

Router#

Related Commands

undebug entry (same as no debug entry)

debug etherchnl

To enable EtherChannel/PAgP shim debugging, use the debug etherchnl command. Use the no form of this command to disable debugging output.

debug etherchnl [all | detail | error | event | idb | linecard]

no debug etherchnl

Syntax Description

all	(Optional) Displays all EtherChannel debug messages.
detail	(Optional) Displays detailed EtherChannel debug messages.
error	(Optional) Displays EtherChannel error debug messages.
event	(Optional) Debugs major EtherChannel event messages.
idb	(Optional) Debugs PAgP IDB messages.
linecard	(Optional) Debugs SCP messages to the line card.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

If you do not specify a keyword, all debug messages are displayed.

Examples

This example shows how to display all EtherChannel debug messages:

Router# debug etherchnl

Sep 14 12:59:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/8

, changed state to down

Sep 14 12:59:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/9

, changed state to down

Sep 14 13:01:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/8

, changed state to up

Sep 14 13:11:03: %SYS-5-CONFIG_I: Configured from console by vty2 (171.69.200.22

7)

.

.

.

Router#

This example shows how to display EtherChannel IDB debug messages:

Router# debug etherchnl idb

Agport idb related debugging is on

Router#

Related Commands

undebug etherchnl (same as no debug etherchnl)

debug ethernet-interface

To debug Ethernet interface events, use the debug ethernet-interface command. Use the no form of this command to disable debugging output.

debug ethernet-interface

no debug ethernet-interface

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable debugging of Ethernet interface events and provides a sample of the output:

Router# debug ethernet-interface

Ethernet network interface debugging is on

Router# RX:(D)b000.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.0.80 (TL)6

RX:(D)b800.0000.0ffc (S)0000.0000.0000 (T)0x4000 (L)92 (IP)0.0.255.255 (TL)57344

RX:(D)c800.0008.0000 (S)0000.0000.0000 (T)0x6000 (L)124 (IP)0.0.255.255 (TL)3225

<... output truncated ...>                                                                              

Router#

Related Commands

undebug ethernet-interface (same as no debug ethernet-interface)

debug fastethernet

To debug Fast Ethernet interface events or packets, use the debug fastethernet command. Use the no form of this command to disable debugging output.

debug fastethernet {events | packets}

no debug fastethernet {events | packets}

Syntax Description

events	Debugs Fast Ethernet events.
packets	Debugs Fast Ethernet packets.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

These examples show how to debug Fast Ethernet events and packets:

Router# debug fastethernet events

Fast Ethernet events debugging is on

Router#

Router# debug fastethernet packets

Fast Ethernet packets debugging is on

Router#

Related Commands

undebug fastethernet (same as no debug fastethernet)

debug fm

To debug feature manager (fm) events and activities, use the debug fm command. Use the no form of this command to disable debugging output.

debug fm {all | event | queue-event | unusual | verbose}

no debug fm {all | event | queue-event | unusual | verbose}

Syntax Description

all	Debugs all FM activity.
event	Debugs FM events.
queue-event	Debugs only FM queue events.
unusual	Debugs only unusual FM events.
verbose	Displays verbose debug output for FM.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable verbose debugging output of feature manager events and activities:

Router# debug fm verbose

FM verbose debugging is on

Router#

Related Commands

undebug fm (same as no debug fm)

debug gssapi

To debug GSSAPI events, use the debug gssapi command. Use the no form of this command to disable debugging output.

debug gssapi

no debug gssapi

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable debugging of GSSAPI events:

Router# debug gssapi

GSSAPI debugging is on

Router#

Related Commands

undebug gssapi (same as no debug gssapi)

debug icc

To debug ICC events, use the debug icc command. Use the no form of this command to disable debugging output.

debug icc [all | async-requests | events | exceptions | requests]

no debug icc [all | async-requests | events | exceptions | requests]

Syntax Description

all	(Optional) Debugs all ICC events.
async-requests	(Optional) Debugs ICC asynchronous requests.
events	(Optional) Debugs only ICC events.
exceptions	(Optional) Debugs ICC exceptions.
requests	(Optional) Debugs ICC requests.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable debugging of ICC asynchronous requests and provides a sample of the output:

Router# debug icc async-requests

ICC Asynchronous Requests debugging is on

Router# #icc_append_async_request: msg 0x617E2058, id 0x62595448, cb 0x603E9CB8

icc_append_async_request: ar 0x618438E0

icc_append_async_request: head 0x0, tail 0x61479B50

icc_async_callback: msg=0x617E2058, err=0

icc_unlink_async_request: msg 0x617E2058

icc_unlink_async_request: head matches

<... output truncated ...>

Router#

Related Commands

undebug icc (same as no debug icc)

debug iccshim

To debug ICC shim events, use the debug iccshim command. Use the no form of this command to disable debugging output.

debug iccshim [all | event | packet]

no debug iccshim [all | event | packet]

Syntax Description

all	(Optional) Debugs all ICC shim events.
event	(Optional) Debugs only ICC shim events.
packet	(Optional) Debugs ICC shim packets.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable debugging of ICC shim packets and provides a sample of the output:

Router# debug iccshim packet

ICCSHIM packets debugging is on

Router# icc_append_async_request: msg 0x617E25AC, id 0x62595448, cb 0x603E9CB8

icc_append_async_request: ar 0x618438E0

icc_append_async_request: head 0x0, tail 0x61479B50

icc_async_callback: msg=0x617E25AC, err=0

icc_unlink_async_request: msg 0x617E25AC

icc_unlink_async_request: head matches

icc_unlink_async_request: took tail

icc_unlink_async_request: head 0x0, tail 0x61479B50, p 0x618438E0

icc_async_callback: ar 0x618438E0, cb 0x603E9CB8, id 0x62595448

icc_async_callback: got rpc respsonse, msg=0x617E2058

icc_async_callback: got rpc respsonse, pak=0x6176B770

icc_async_callback: calling callback

icc_async_callback: callback complete

<... output truncated ...>

Router#

Related Commands

undebug iccshim (same as no debug iccshim)

debug interface

To create a shortcut for the debug condition interface command, use the debug interface command. Use the no form of this command to disable debugging output.

debug interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id}}

no debug interface {{interface interface-number} | null interface-number | {port-channel number} | {vlan vlan-id}}

---

Note The vlan parameter for the debug interface command only applies to the MSFC and can be entered only from the router console.

---

Syntax Description

interface	Interface type; valid values are ethernet, fastethernet, gigabitethernet, tengigabitethernet, pos, ge-wan, and atm.
interface-number	Module and port number; see the "Usage Guidelines" section for valid values.
null interface-number	Limits debugging to null interfaces; the valid value is 0.
port-channel number	Limits debugging to port-channel interfaces; see the "Usage Guidelines" section for valid values.
vlan vlan-id	Specifies the VLAN interface number; see the "Usage Guidelines" section for valid values.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(3a)E3	The number of valid values for port-channel number was changed; see the "Usage Guidelines" section for valid values.
12.1(11b)E	This command was changed to include the pos, ge-wan, and atm keywords.

Usage Guidelines

The number of valid values for port-channel number depends on the software release. For releases prior to Release 12.1(3a)E3, valid values are from 1 to 256; for Releases 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Release 12.1(5c)EX and later support a maximum of 64 values ranging from 1 to 256.

The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module installed in a 13-slot chassis, valid values for the module number are from 2 to 13 and valid values for the port number are from 1 to 48.

If your system is configured with a Supervisor Engine 1, valid values for vlan-id are from 1 to 1005. If your system is configured with a Supervisor Engine 2, valid values for vlan-id are from 1 to 4094. Extended-range VLANs are not supported on systems configured with a Supervisor Engine 1.

Examples

This example shows how to limit debugging to interface VLAN 1:

Router# debug interface vlan 1

Condition 1 set

Router#

Related Commands

debug condition interface
undebug interface (same as no debug interface)

debug ipc

To debug IPC activity, use the debug ipc command. Use the no form of this command to disable debugging output.

debug ipc {all | errors | events | headers | packets | ports | seats}

no debug ipc {all | errors | events | headers | packets | ports | seats}

Syntax Description

all	Turns on all IPC debugging.
errors	Turns on IPC error debugging.
events	Turns on IPC event debugging.
headers	Turns on IPC header debugging.
packets	Turns on IPC packet debugging.
ports	Turns on debugging of creation and deletion of ports.
seats	Turns on debugging of creation and deletion of nodes.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable debugging of IPC events:

Router# debug ipc events

Special Events debugging is on

Router#

Related Commands

undebug ipc (same as no debug ipc)

debug ip rgmp

To debug RGMP activity, use the debug ip rgmp command. Use the no form of this command to disable debugging output.

debug ip rgmp [name | group-address]

no debug ip rgmp [name | group-address]

Syntax Description

name	(Optional) Multicast group name.
group-address	(Optional) Multicast group address.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(3a)E	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(8a)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable RGMP debugging:

Router# debug ip rgmp

RGMP debugging is on

Router# 

This example shows how to disable RGMP debugging:

Router# no debug ip rgmp

RGMP debugging is off

Router#

Related Commands

ip rgmp

debug l2-mgr events

To debug Layer 2 manager events, use the debug l2-mgr events command. Use the no form of this command to disable debugging output.

debug l2-mgr events

no debug l2-mgr events

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

This command is supported by the supervisor engine only and can be entered only from the Catalyst 6500 series switch console (see the remote login command).

Examples

This example shows how to enable debugging of Layer 2 manager events:

Switch-sp# debug l2-mgr events

L2 mgr events debugging is on

Switch-sp#

Related Commands

remote login
undebugl2-mgr events (same as no debug l2-mgr events)

debug l3-mgr

To debug Layer 3 manager activity, use the debug l3-mgr command. Use the no form of this command to disable debugging output.

debug l3-mgr {all | events | global | packets}

no debug l3-mgr {all | events | global | packets}

Syntax Description

all	Displays all Layer 3 manager debug messages.
events	Displays Layer 3 manager-related events.
global	Displays a bug trace of IP global purge events.
packets	Displays Layer 3 manager packets.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable global Layer 3 manager debugging:

Router# debug l3-mgr global

L3 mgr ip global purge debugging is on

Router#

Related Commands

undebugl3-mgr (same as no debug l3-mgr)

debug local-ack

To debug local acknowledgment activity, use the debug local-ack command. Use the no form of this command to disable debugging output.

debug local-ack {errors | packets | state}

no debug local-ack {errors | packets | state}

Syntax Description

errors	Displays all local acknowledgement errors.
packets	Displays local acknowledgment packets.
state	Displays local acknowledgment state changes.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to enable debugging of local acknowledgement state changes:

Router# debug local-ack state

Local Acknowledgement states debugging is on

Router#

Related Commands

undebug local-ack (same as no debug local-ack)

debug ltl

To enable debugging of LTL manager activity, use the debug ltl command. Use the no form of this command to disable debugging output.

debug ltl

no debug ltl

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

This command is supported by the supervisor engine only and can be entered only from the Catalyst 6500 series switch console (see the remote login command).

Examples

This example shows how to enable LTL manager debugging:

Switch-sp# debug ltl

ltl mgr debugging is on

Switch-sp#

Related Commands

remote login
undebug ltl (same as no debug ltl)

debug mergeapi

To debug ACL merge activity, use the debug mergeapi command. Use the no form of this command to disable debugging output.

debug mergeapi {all | normal | profile | verbose}

no debug mergeapi {all | normal | profile | verbose}

Syntax Description

all	Displays all ACL merge activity.
normal	Displays the main steps traversed by the ACL merge program.
profile	Displays a profile of the CUDD library internal cache.
verbose	Displays detailed information on ACL merge events.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History