Catalyst 4500 Series Switch Cisco IOS Command Reference, 12.2(31)SG

Cisco IOS Commands for the Catalyst 4500 Series Switches

This chapter contains an alphabetical listing of Cisco IOS commands for the Catalyst 4500 series switches. For information about Cisco IOS commands that are not included in this publication, refer to Cisco IOS Release 12.2 Configuration Guides and Command References at this URL:

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_product_indices_list.html

#macro keywords

To specify the help string for the macro keywords, use the #macro keywords command.

#macro keywords [keyword1] [keyword2] [keyword3]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Global configuration

Command History

Usage Guidelines

If you do not specify the mandatory keywords for a macro, the macro is to be considered invalid and fails when you attempt to apply it. By enteringthe #macro keywords command, you will receive a message indicating what you need to include to make the syntax valid.

Examples

This example shows how to specify the help string for keywords associated with a macro named test:

Switch(config)# macro name test

macro name test

Enter macro commands one per line. End with the character '@'.

#macro keywords $VLAN $MAX

swichport

@

Switch(config)# int gi1/1

Switch(config-if)# macro apply test ?

  WORD  Keyword to replace with a value e.g $VLAN, $MAX   << It is shown as help

  <cr>

Related Commands

macro apply cisco-desktop
macro apply cisco-phone
macro apply cisco-router
macro apply cisco-switch

aaa accounting dot1x default start-stop group radius

To enable accounting for 802.1X authentication sessions, use the aaa accounting dot1x default start-stop group radius command. To disable accounting, use the no form of this command.

aaa accounting dot1x default start-stop group radius

no aaa accounting dot1x default start-stop group radius

Syntax Description

This command has no arguments or keywords.

Defaults

Accounting is disabled.

Command Modes

Global configuration

Command History

Usage Guidelines

802.1X accounting requires a RADIUS server.

This command enables the Authentication, Authorization, and Accounting (AAA) client's accounting feature to forward 802.1X update and watchdog packets from the 802.1X supplicant (workstation client) to the authentication (RADIUS) server. (Watchdog packets are defined as EAPOL-LOGON, EAPOL-LOGOFF, and EAPOL-INTERIM messages.) Successful authentication and authorization of the supplicant by the authentication server is required before these packets are considered valid and are forwarded. When the client is reauthenticated, an interim-update accounting notice is sent to the accounting server.

Examples

This example shows how to configure 802.1X accounting:

Switch(config)# aaa accounting dot1x default start-stop group radius

Note The RADIUS authentication server must be properly configured to accept and log update or watchdog packets from the AAA client.

Related Commands

aaa accounting system default start-stop group radius

aaa accounting system default start-stop group radius

To receive the session termination messages after the switch reboots, use the aaa accounting system default start-stop group radius command. To disable accounting, use the no form of this command.

aaa accounting system default start-stop group radius

no aaa accounting system default start-stop group radius

Syntax Description

This command has no arguments or keywords.

Defaults

Accounting is disabled.

Command Modes

Global configuration mode

Command History

Usage Guidelines

802.1X accounting requires the RADIUS server.

This command enables the AAA client's accounting feature to forward 802.1X update and watchdog packets from the 802.1X supplicant (workstation client) to the authentication (RADIUS) server. (Watchdog packets are defined as EAPOL-LOGON, EAPOL-LOGOFF, and EAPOL-INTERIM messages.) Successful authentication and authorization of the supplicant by the authentication server is required before these packets are considered valid and are forwarded. When the client is reauthenticated, an interim-update accounting notice is sent to the accounting server.

Examples

This example shows how to generate a logoff after a switch reboots:

Switch(config)# aaa accounting system default start-stop group radius

Note The RADIUS authentication server must be properly configured to accept and log update or watchdog packets from the AAA client.

Related Commands

aaa accounting dot1x default start-stop group radius

access-group mode

To specify the override modes (for example, VACL overrides PACL) and the non-override modes (for example, merge or strict mode), use the access-group mode command. To return to preferred port mode, use the no form of this command.

access-group mode {prefer {port | vlan} | merge}

no access-group mode {prefer {port | vlan} | merge}

Syntax Description

Defaults

PACL override mode

Command Modes

Interface configuration

Command History

Usage Guidelines

On the Layer 2 interface, prefer port, prefer VLAN, and merge modes are supported. A Layer 2 interface can have one IP ACL applied in either direction (one inbound and one outbound).

Examples

This example shows how to make the PACL mode on the switch take effect:

(config-if)# access-group mode prefer port

This example shows how to merge applicable ACL features:

(config-if)# access-group mode merge

Related Commands

show access-group mode interface
show ip interface (refer to Cisco IOS documentation)
show mac access-group interface

access-list hardware entries

To designate how ACLs are programmed into the switch hardware, use the access-list hardware entries command.

access-list hardware entries {packed | scattered}

Syntax Description

Defaults

The ACLs are programmed as packed.

Command Modes

Global configuration

Command History

Usage Guidelines

Two types of hardware resources are used when ACLs are programmed: entries and masks. If one of these resources is consumed, no additional ACLs can be programmed into the hardware. If the masks are consumed, but the entries are available, change the programming algorithm from packed to scattered to make the masks available. This action allows additional ACLs to be programmed into the hardware.

The goal is to use TCAM resources more efficiently; that is, to minimize the number of masks per ACL entries. To compare TCAM utilization when using the scattered or packed algorithms, use the
show platform hardware acl statistics utilization brief command. To change the algorithm from packed to scattered, use the access-list hardware entries command.

Examples

This example shows how to program ACLs into the hardware as packed. After they are programmed, you will need 89 percent of the masks to program only 49 percent of the ACL entries.

Switch# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)# access-list hardware entries packed

Switch(config)# end

Switch#

01:15:34: %SYS-5-CONFIG_I: Configured from console by console

Switch#

Switch# show platform hardware acl statistics utilization brief

Entries/Total(%)  Masks/Total(%)

                                       -----------------  ---------------

            Input  Acl(PortAndVlan)  2016 / 4096 ( 49)   460 /  512 ( 89)

            Input  Acl(PortOrVlan)      6 / 4096 (  0)     4 /  512 (  0)

            Input  Qos(PortAndVlan)     0 / 4096 (  0)     0 /  512 (  0)

            Input  Qos(PortOrVlan)      0 / 4096 (  0)     0 /  512 (  0)

            Output Acl(PortAndVlan)     0 / 4096 (  0)     0 /  512 (  0)

            Output Acl(PortOrVlan)      0 / 4096 (  0)     0 /  512 (  0)

            Output Qos(PortAndVlan)     0 / 4096 (  0)     0 /  512 (  0)

            Output Qos(PortOrVlan)      0 / 4096 (  0)     0 /  512 (  0)

            L4Ops: used 2 out of 64

Switch# 

This example shows how to reserve space (scatter) between ACL entries in the hardware. The 
number of masks required to program 49 percent of the entries has decreased to 49 percent.

Switch# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)# access-list hardware entries scattered

Switch(config)# end

Switch#

01:39:37: %SYS-5-CONFIG_I: Configured from console by console

Switch#

Switch# show platform hardware acl statistics utilization brief

Entries/Total(%)  Masks/Total(%)

                                       -----------------  ---------------

            Input  Acl(PortAndVlan)  2016 / 4096 ( 49)   252 /  512 ( 49)

            Input  Acl(PortOrVlan)      6 / 4096 (  0)     5 /  512 (  0)

            Input  Qos(PortAndVlan)     0 / 4096 (  0)     0 /  512 (  0)

            Input  Qos(PortOrVlan)      0 / 4096 (  0)     0 /  512 (  0)

            Output Acl(PortAndVlan)     0 / 4096 (  0)     0 /  512 (  0)

            Output Acl(PortOrVlan)      0 / 4096 (  0)     0 /  512 (  0)

            Output Qos(PortAndVlan)     0 / 4096 (  0)     0 /  512 (  0)

            Output Qos(PortOrVlan)      0 / 4096 (  0)     0 /  512 (  0)

            L4Ops: used 2 out of 64

Switch# 

access-list hardware region

To modify the balance between TCAM regions in hardware, use the access-list hardware region command.

access-list hardware region {feature | qos} {input | output} balance {bal-num}

Syntax Description

Defaults

The default region balance for each TCAM is 50.

Command Modes

Global configuration

Command History

Usage Guidelines

PandV is a TCAM region containing entries which mask in both the port and VLAN tag portions of the flow label.

PorV is a TCAM region containing entries which mask in either the port or VLAN tag portion of the flow label, but not both.

A balance of 1 allocates the minimum number of PandV region entries and the maximum number of PorV region entries. A balance of 99 allocates the maximum number of PandV region entries and the minimum number of PorV region entries. A balance of 50 allocates equal numbers of PandV and PorV region entries in the specified TCAM.

Balances for the four TCAMs can be modified independently.

Examples

This example shows how to enable the MAC notification trap when a MAC address is added to a port:

Switch# configure terminal

Switch(config)# access-list hardware region feature input balance 75

Switch(config)# 

action

To specify an action to be taken when a match occurs in a VACL, use the action command. To remove an action clause, use the no form of this command.

action {drop | forward}

no action {drop | forward}

Syntax Description

Defaults

This command has no default settings.

Command Modes

VLAN access-map

Command History

Usage Guidelines

In a VLAN access map, if at least one ACL is configured for a packet type (IP or MAC), the default action for the packet type is drop (deny).

If an ACL is not configured for a packet type, the default action for the packet type is forward (permit).

If an ACL for a packet type is configured and the ACL is empty or undefined, the configured action will be applied to the packet type.

Examples

This example shows how to define a drop action:

Switch(config-access-map)# action drop 

Switch(config-access-map)# 

This example shows how to define a forward action:

Switch(config-access-map)# action forward 

Switch(config-access-map)# 

Related Commands

match
show vlan access-map
vlan access-map

apply

To implement a new VLAN database, increment the configuration number, save the configuration number in NVRAM, and propagate the configuration number throughout the administrative domain, use the apply command.

apply

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

VLAN configuration

Command History

Usage Guidelines

The apply command implements the configuration changes that you made after you entered VLAN database mode and uses them for the running configuration. This command keeps you in VLAN database mode.

You cannot use this command when the switch is in the VTP client mode.

You can verify that the VLAN database changes occurred by entering the show vlan command from privileged EXEC mode.

Examples

This example shows how to implement the proposed new VLAN database and to recognize it as the current database:

Switch(config-vlan)# apply

Switch(config-vlan)# 

Related Commands

abort (refer to Cisco IOS documentation)
exit (refer to Cisco IOS documentation)
reset
show vlan
shutdown vlan (refer to Cisco IOS documentation)
vtp (global configuration mode)

arp access-list

To define an ARP access list or add clauses at the end of a predefined list, use the arp access-list command.

arp access-list name

Syntax Description

Defaults

None

Command Modes

Configuration

Command History

Examples

This example shows how to define an ARP access list named static-hosts:

Switch(config)# arp access-list static-hosts

Switch(config)# 

Related Commands

deny
ip arp inspection filter vlan
permit

attach module

To remotely connect to a specific module, use the attach module configuration command.

attach module mod

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged

Command History

Usage Guidelines

This command applies only to the Access Gateway Module on Catalyst 4500 series switches.

The valid values for mod depend on the chassis that are used. For example, if you have a Catalyst 4006 chassis, valid values for the module are from 2 to 6. If you have a 4507R chassis, valid values are from 3 to 7.

When you execute the attach module mod command, the prompt changes to Gateway#.

This command is identical in the resulting action to the session module mod and the remote login module mod commands.

Examples

This example shows how to remotely log in to an Access Gateway Module:

Switch# attach module 5

Attaching console to module 5

Type 'exit' at the remote prompt to end the session

Gateway> 

Related Commands

remote login module
session module

auto qos voip

To automatically configure quality of service (auto-QoS) for voice over IP (VoIP) within a QoS domain, use the auto qos voip interface configuration command. To change the auto-QoS configuration settings to the standard QoS defaults, use the no form of this command.

auto qos voip {cisco-phone | trust}

no auto qos voip {cisco-phone | trust}

Syntax Description

Defaults

Auto-QoS is disabled on all interfaces.

Command Modes

Interface configuration

Command History

Usage Guidelines

Use this command to configure the QoS that is appropriate for VoIP traffic within the QoS domain. The QoS domain includes the switch, the interior of the network, and the edge devices that can classify incoming traffic for QoS.

Use the cisco-phone keyword on the ports at the edge of the network that are connected to Cisco IP phones. The switch detects the telephone through the Cisco Discovery Protocol (CDP) and trusts the CoS labels in packets that are received from the telephone.

Use the trust keyword on the ports that are connected to the interior of the network. Because it is assumed that the traffic has already been classified by the other edge devices, the CoS/DSCP labels in these packets are trusted.

When you enable the auto-QoS feature on the specified interface, these actions automatically occur:

•QoS is globally enabled (qos global configuration command).

•DBL is enabled globally (qos dbl global configuration command).

•When you enter the auto qos voip cisco-phone interface configuration command, the trusted boundary feature is enabled. It uses the Cisco Discovery Protocol (CDP) to detect the presence or absence of a Cisco IP phone. When a Cisco IP phone is detected, the ingress classification on the specific interface is set to trust the CoS label that is received in the packet because some old phones do not mark DSCP. When a Cisco IP phone is absent, the ingress classification is set to not trust the CoS label in the packet.

•When you enter the auto qos voip trust interface configuration command, the ingress classification on the specified interface is set to trust the CoS label that is received in the packet if the specified interface is configured as Layer 2 (and is set to trust DSCP if the interface is configured as Layer 3).

You can enable auto-QoS on static, dynamic-access, voice VLAN access, and trunk ports.

To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug auto qos privileged EXEC command to enable auto-QoS debugging.

To disable auto-QoS on an interface, use the no auto qos voip interface configuration command. When you enter this command, the switch enables standard QoS and changes the auto-QoS settings to the standard QoS default settings for that interface. This action will not change any global configuration performed by auto-QoS; the global configuration remains the same.

Examples

This example shows how to enable auto-QoS and to trust the CoS and DSCP labels that are received in the incoming packets when the switch or router that is connected to Gigabit Ethernet interface 1/1 is a trusted device:

Switch(config)# interface gigabitethernet1/1

Switch(config-if)# auto qos voip trust

This example shows how to enable auto-QoS and to trust the CoS labels that are received in incoming packets when the device connected to Fast Ethernet interface 2/1 is detected as a Cisco IP phone:

Switch(config)# interface fastethernet2/1

Switch(config-if)# auto qos voip cisco-phone

This example shows how to display the QoS configuration that is automatically generated when auto-QoS is enabled:

Switch# debug auto qos

AutoQoS debugging is on

Switch# config terminal

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)# interface gigabitethernet1/1

Switch(config-if)# auto qos voip trust

Switch(config-if)#

00:00:56:qos

00:00:57:qos map cos 3 to dscp 26

00:00:57:qos map cos 5 to dscp 46

00:00:58:qos map dscp 32 to tx-queue 1

00:00:58:qos dbl

00:01:00:policy-map autoqos-voip-policy

00:01:00:  class class-default

00:01:00:   dbl

00:01:00:interface GigabitEthernet1/1

00:01:00: qos trust cos

00:01:00: tx-queue 3

00:01:00:  priority high

00:01:00:  shape percent 33

00:01:00:  service-policy output autoqos-voip-policy

Switchconfig-if)# interface gigabitethernet1/1

Switch(config-if)# auto qos voip cisco-phone

Switch(config-if)#

00:00:55:qos

00:00:56:qos map cos 3 to dscp 26

00:00:57:qos map cos 5 to dscp 46

00:00:58:qos map dscp 32 to tx-queue 1

00:00:58:qos dbl

00:00:59:policy-map autoqos-voip-policy

00:00:59:  class class-default

00:00:59:   dbl

00:00:59:interface GigabitEthernet1/1

00:00:59: qos trust device cisco-phone

00:00:59: qos trust cos

00:00:59: tx-queue 3

00:00:59:  priority high

00:00:59:  shape percent 33

00:00:59:  bandwidth percent 33

00:00:59:  service-policy output autoqos-voip-policy

You can verify your settings by entering the show auto qos interface command.

Related Commands

debug auto qos (refer to Cisco IOS documentation)
qos map cos
qos trust
show auto qos
show qos
show qos interface
show qos maps

auto-sync

To enable automatic synchronization of the configuration files in NVRAM, use the auto-sync command. To disable automatic synchronization, use the no form of this command.

auto-sync {startup-config | config-register | bootvar | standard}

no auto-sync {startup-config | config-register | bootvar | standard}

Syntax Description

Defaults

Standard automatic synchronization of all configuration files

Command Modes

Redundancy main-cpu

Command History

Usage Guidelines

If you enter the no auto-sync standard command, no automatic synchronizations occur.

Examples

This example shows how (from the default configuration) to enable automatic synchronization of the configuration register in the main CPU:

Switch# config terminal

Switch (config)# redundancy

Switch (config-r)# main-cpu

Switch (config-r-mc)# no auto-sync standard

Switch (config-r-mc)# auto-sync configure-register

Switch (config-r-mc)# 

Related Commands

redundancy

channel-group

To assign and configure an EtherChannel interface to an EtherChannel group, use the channel-group command. To remove a channel group configuration from an interface, use the no form of this command.

channel-group number mode {active | on | auto [non-silent]} | {passive | desirable [non-silent]}

no channel-group

Syntax Description

Defaults

No channel groups are assigned.

Command Modes

Interface configuration

Command History

Usage Guidelines

You do not have to create a port-channel interface before assigning a physical interface to a channel group. If a port-channel interface has not been created, it is automatically created when the first physical interface for the channel group is created.

If a specific channel number is used for the PAgP-enabled interfaces of a channel group, that same channel number cannot be used for configuring a channel that has LACP-enabled interfaces or vice versa.

You can also create port channels by entering the interface port-channel command. This will create a Layer 3 port channel. To change the Layer 3 port channel into a Layer 2 port channel, use the switchport command before you assign physical interfaces to the channel group. A port channel cannot be changed from Layer 3 to Layer 2 or vice versa when it contains member ports.

You do not have to disable the IP address that is assigned to a physical interface that is part of a channel group, but we recommend that you do so.

Any configuration or attribute changes that you make to the port-channel interface are propagated to all interfaces within the same channel group as the port channel (for example, configuration changes are also propagated to the physical interfaces that are not part of the port channel, but are part of the channel group).

You can create in on mode a usable EtherChannel by connecting two port groups together.

Caution Do not enable Layer 3 addresses on the physical EtherChannel interfaces. Do not assign bridge groups on the physical EtherChannel interfaces because it creates loops.

Examples

This example shows how to add Gigabit Ethernet interface 1/1 to the EtherChannel group that is specified by port-channel 45:

Switch(config-if)# channel-group 45 mode on 

Creating a port-channel interface Port-channel45

Switch(config-if)# 

Related Commands

interface port-channel
show interfaces port-channel (refer to Cisco IOS documentation)

channel-protocol

To enable LACP or PAgP on an interface, use the channel-protocol command. To disable the protocols, use the no form of this command.

channel-protocol {lacp | pagp}

no channel-protocol {lacp | pagp}

Syntax Description

Defaults

PAgP

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is not supported on systems that are configured with a Supervisor Engine I.

You can also select the protocol using the channel-group command.

If the interface belongs to a channel, the no form of this command is rejected.

All ports in an EtherChannel must use the same protocol; you cannot run two protocols on one module.

PAgP and LACP are not compatible; both ends of a channel must use the same protocol.

You can manually configure a switch with PAgP on one side and LACP on the other side in the on mode.

You can change the protocol at any time, but this change causes all existing EtherChannels to reset to the default channel mode for the new protocol. You can use the channel-protocol command to restrict anyone from selecting a mode that is not applicable to the selected protocol.

Configure all ports in an EtherChannel to operate at the same speed and duplex mode (full duplex only for LACP mode).

For a complete list of guidelines, refer to the "Configuring EtherChannel" section of the Catalyst 4500 Series Switch Cisco IOS Software Configuration Guide.

Examples

This example shows how to select LACP to manage channeling on the interface:

Switch(config-if)# channel-protocol lacp

Switch(config-if)# 

Related Commands

channel-group
show etherchannel

class-map

To access the QoS class map configuration mode to configure QoS class maps, use the class-map command. To delete a class map, use the no form of this command.

class-map [match-all | match-any] name

no class-map [match-all | match-any] name

Syntax Description

Defaults

Match all criteria.

Command Modes

Global configuration

Command History

Usage Guidelines

The name and acl_name arguments are case sensitive.

Use the class-map command and its subcommands on individual interfaces to define packet classification, marking, aggregate, and flow policing as part of a globally named service policy.

These commands are available in QoS class map configuration mode:

•exit—Exits you from QoS class map configuration mode.

•no—Removes a match statement from a class map.

•match—Configures classification criteria.

These optional subcommands are also available:

–access-group {acl_index | name acl_name}

–ip {dscp | precedence} value1 value2... value8

–any

The following subcommands appear in the CLI help, but they are not supported on LAN interfaces:

•input-interface {interface interface_number | null number | vlan vlan_id}

•protocol linktype

•destination-address mac mac_address

•source-address mac mac_address

•qos-group

•mpls

•no

After you have configured the class map name and are in class map configuration mode, you can enter the match subcommands. The syntax for these subcommands is as follows:

match {[access-group {acl_index | name acl_name}] | [ip {dscp | precedence} value1 value2... value8]}

See Table 2-1 for a syntax description of the match subcommands.

Examples

This example shows how to access the class-map commands and subcommands and to configure a class map named ipp5 and enter a match statement for ip precedence 5:

Switch# config terminal

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)# class-map ipp5

Switch(config-cmap)# match ip precedence 5

Switch(config-cmap)# 

This example shows how to configure the class map to match an already configured access list:

Switch(config-cmap)# match access-group IPacl1

Switch(config-cmap)# 

Related Commands

policy-map
service-policy
show class-map
show policy-map
show policy-map interface

clear counters

To clear the interface counters, use the clear counters command.

clear counters [{FastEthernet interface_number} | {GigabitEthernet interface_number} |
{null interface_number} | {port-channel number} | {vlan vlan_id}]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

This command clears all the current interface counters from all the interfaces unless you specify an interface.

Note This command does not clear the counters that are retrieved using SNMP, but only those seen when you enter the show interface counters command.

Examples

This example shows how to clear all the interface counters:

Switch# clear counters

Clear "show interface" counters on all interfaces [confirm] y

Switch# 

This example shows how to clear the counters on a specific interface:

Switch# clear counters vlan 200

Clear "show interface" counters on this interface [confirm]y

Switch# 

Related Commands

show interface counters (refer to Cisco IOS documentation)

clear hw-module slot password

To clear the password on an intelligent line module, use the clear hw-module slot password command.

clear hw-module slot slot_num password

Syntax Description

Defaults

The password is not cleared.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

You only need to change the password once unless the password is reset.

Examples

This example shows how to clear the password from slot 5 on a line module:

Switch# clear hw-module slot 5 password

Switch# 

Related Commands

hw-module power

clear interface gigabitethernet

To clear the hardware logic from a Gigabit Ethernet IEEE 802.3z interface, use the clear interface gigabitethernet command.

clear interface gigabitethernet mod/port

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the hardware logic from a Gigabit Ethernet IEEE 802.3z interface:

Switch# clear interface gigabitethernet 1/1

Switch# 

Related Commands

show interfaces status

clear interface vlan

To clear the hardware logic from a VLAN, use the clear interface vlan command.

clear interface vlan number

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the hardware logic from a specific VLAN:

Switch# clear interface vlan 5

Switch# 

Related Commands

show interfaces status

clear ip access-template

To clear the statistical information in access lists, use the clear ip access-template command.

clear ip access-template access-list

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the statistical information for an access list:

Switch# clear ip access-template 201

Switch# 

clear ip arp inspection log

To clear the status of the log buffer, use the clear ip arp inspection log command.

clear ip arp inspection log

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the contents of the log buffer:

Switch# clear ip arp inspection log

Switch# 

Related Commands

arp access-list
show ip arp inspection log

clear ip arp inspection statistics

To clear the dynamic ARP inspection statistics, use the clear ip arp inspection statistics command.

clear ip arp inspection statistics [vlan vlan-range]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the DAI statistics from VLAN 1 and how to verify the removal:

Switch# clear ip arp inspection statistics vlan 1

Switch# show ip arp inspection statistics vlan 1

 Vlan      Forwarded        Dropped     DHCP Drops     ACL Drops 

 ----      ---------        -------     ----------     ----------

    1              0              0              0              0

 Vlan   DHCP Permits    ACL Permits   Source MAC Failures

 ----   ------------    -----------   -------------------

    1              0              0                    0

 Vlan   Dest MAC Failures   IP Validation Failures

 ----   -----------------   ----------------------

    1                  0                        0

Switch#

Related Commands

arp access-list
clear ip arp inspection log
show ip arp inspection

clear ip dhcp snooping database

To clear the DHCP binding database, use the clear ip dhcp snooping database command.

clear ip dhcp snooping database

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the DHCP binding database:

Switch# clear ip dhcp snooping database

Switch# 

Related Commands

ip dhcp snooping
ip dhcp snooping binding interface (refer to Cisco IOS documentation)
ip dhcp snooping information option
ip dhcp snooping trust
ip dhcp snooping vlan
show ip dhcp snooping
show ip dhcp snooping binding

clear ip dhcp snooping database statistics

To clear the DHCP binding database statistics, use the clear ip dhcp snooping database statistics command.

clear ip dhcp snooping database statistics

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the DHCP binding database:

Switch# clear ip dhcp snooping database statistics

Switch# 

Related Commands

ip dhcp snooping
ip dhcp snooping binding
ip dhcp snooping information option
ip dhcp snooping trust
ip dhcp snooping vlan
show ip dhcp snooping
show ip dhcp snooping binding

clear ip igmp group

To delete the IGMP group cache entries, use the clear ip igmp group command.

clear ip igmp group [{fastethernet mod/port} | {GigabitEthernet mod/port} | {host_name | group_address} {Loopback interface_number} | {null interface_number} |
{port-channel number} | {vlan vlan_id}]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The IGMP cache contains a list of the multicast groups of which hosts on the directly connected LAN are members.

To delete all the entries from the IGMP cache, enter the clear ip igmp group command with no arguments.

Examples

This example shows how to clear the entries for a specific group from the IGMP cache:

Switch# clear ip igmp group 224.0.255.1

Switch# 

This example shows how to clear the IGMP group cache entries from a specific interface:

Switch# clear ip igmp group gigabitethernet 2/2

Switch# 

Related Commands

ip host (refer to Cisco IOS documentation)
show ip igmp groups (refer to Cisco IOS documentation)
show ip igmp interface

clear ip igmp snooping membership

To clear the explicit host tracking database, use the clear ip igmp snooping membership command.

clear ip igmp snooping membership [vlan vlan_id]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

By default, the explicit host tracking database maintains a maximum of 1-KB entries. After you reach this limit, no additional entries can be created in the database. To create more entries, you will need to delete the database with the clear ip igmp snooping statistics vlan command.

Examples

This example shows how to display the IGMP snooping statistics for VLAN 25:

Switch# clear ip igmp snooping membership vlan 25

Switch#

Related Commands

ip igmp snooping vlan explicit-tracking
show ip igmp snooping membership

clear ip mfib counters

To clear the global MFIB counters and the counters for all active MFIB routes, use the clear ip mfib counters command.

clear ip mfib counters

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear all the active MFIB routes and global counters:

Switch# clear ip mfib counters

Switch# 

Related Commands

show ip mfib

clear ip mfib fastdrop

To clear all the MFIB fast-drop entries, use the clear ip mfib fastdrop command.

clear ip mfib fastdrop

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

If new fast-dropped packets arrive, the new fast-drop entries are created.

Examples

This example shows how to clear all the fast-drop entries:

Switch# clear ip mfib fastdrop

Switch# 

Related Commands

ip mfib fastdrop
show ip mfib fastdrop

clear lacp counters

To clear the statistics for all the interfaces belonging to a specific channel group, use the clear lacp counters command.

clear lacp [channel-group] counters

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC mode

Command History

Usage Guidelines

This command is not supported on systems that are configured with a Supervisor Engine I.

If you do not specify a channel group, all channel groups are cleared.

If you enter this command for a channel group that contains members in PAgP mode, the command is ignored.

Examples

This example shows how to clear the statistics for a specific group:

Switch# clear lacp 1 counters

Switch# 

Related Commands

show lacp

clear mac-address-table

To clear the global counter entries from the Layer 2 MAC address table, use the clear mac-address-table command.

clear mac-address-table {dynamic [{address mac_addr} | {interface interface}] [vlan vlan_id] | notification}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Enter the clear mac-address-table dynamic command with no arguments to remove all dynamic entries from the table.

The clear mac-address-table notification command only clears the global counters which are displayed with show mac-address-table notification command. It does not clear the global counters and the history table of the CISCO-MAC-NATIFICATION-MIB.

Examples

This example shows how to clear all the dynamic Layer 2 entries for a specific interface (gi1/1):

Switch# clear mac-address-table dynamic interface gi1/1

Switch# 

This example shows how to clear the MAC address notification counters:

Switch# clear mac-address-table notification

Switch# 

Related Commands

clear mac-address-table dynamic
mac-address-table aging-time
mac-address-table notification
main-cpu
show mac-address-table address
mac-address-table notification
snmp-server enable traps
snmp trap mac-notification change

clear mac-address-table dynamic

To clear the dynamic address entries from the Layer 2 MAC address table, use the clear mac-address-table dynamic command.

clear mac-address-table dynamic [{address mac_addr} | {interface interface}] [vlan vlan_id]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Enter the clear mac-address-table dynamic command with no arguments to remove all dynamic entries from the table.

Examples

This example shows how to clear all the dynamic Layer 2 entries for a specific interface (gi1/1):

Switch# clear mac-address-table dynamic interface gi1/1

Switch# 

Related Commands

mac-address-table aging-time
main-cpu
show mac-address-table address

clear pagp

To clear the port-channel information, use the clear pagp command.

clear pagp {group-number | counters}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to clear the port-channel information for a specific group:

Switch# clear pagp 32

Switch# 

This example shows how to clear all the port-channel traffic filters:

Switch# clear pagp counters

Switch# 

Related Commands

show pagp

clear port-security

To delete all configured secure addresses or a specific dynamic or sticky secure address on an interface from the MAC address table, use the clear port-security command.

clear port-security dynamic [address mac-addr [vlan vlan-id]] | [interface interface-id] [vlan access | voice]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Usage Guidelines

If you enter the clear port-security all command, the switch removes all the dynamic secure MAC addresses from the MAC address table.

Note You can clear sticky and static secure MAC addresses one at a time with the
no switchport port-security mac-address command.

If you enter the clear port-security dynamic interface interface-id command, the switch removes all the dynamic secure MAC addresses on an interface from the MAC address table.

Command History

Examples

This example shows how to remove all the dynamic secure addresses from the MAC address table:

Switch# clear port-security dynamic

This example shows how to remove a dynamic secure address from the MAC address table:

Switch# clear port-security dynamic address 0008.0070.0007

This example shows how to remove all the dynamic secure addresses learned on a specific interface:

Switch# clear port-security dynamic interface gigabitethernet0/1

You can verify that the information was deleted by entering the show port-security command.

Related Commands

show port-security
switchport port-security

clear qos

To clear the global and per-interface aggregate QoS counters, use the clear qos command.

clear qos [aggregate-policer [name] | interface {{fastethernet | GigabitEthernet} {mod/interface}} | vlan {vlan_num} | port-channel {number}]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

Note When you enter the clear qos command, the way that the counters work is affected and the traffic that is normally restricted could be forwarded for a short period of time.

The clear qos command resets the interface QoS policy counters. If no interface is specified, the clear qos command resets the QoS policy counters for all interfaces.

Examples

This example shows how to clear the global and per-interface aggregate QoS counters for all the protocols:

Switch# clear qos

Switch# 

This example shows how to clear the specific protocol aggregate QoS counters for all the interfaces:

Switch# clear qos aggregate-policer 

Switch# 

Related Commands

show qos

clear vlan counters

To clear the software-cached counter values to start from zero again for a specified VLAN or all existing VLANs, use the clear vlan counters command.

clear vlan [vlan-id] counters

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

If you do not specify a vlan-id value; the software-cached counter values for all the existing VLANs are cleared.

Examples

Switch# clear vlan 10 counters

Clear "show vlan" counters on this vlan [confirm]y

Switch# 

Related Commands

show vlan counters

clear vmps statistics

To clear the VMPS statistics, use the clear vmps statistics command.

clear vmps statistics

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

Switch# clear vmps statistics

Switch# 

Related Commands

show vmps
vmps reconfirm (privileged EXEC)

control-plane

To enter control-plane configuration mode, which allows users to associate or modify attributes or parameters (such as a service policy) that are associated with the control plane of the device, use the control-plane command.

control-plane

Syntax Description

This command has no arguments or keywords.

Defaults

Default service police named "system-cpp-policy" is attached.

Command Modes

Global configuration

Command History

Usage Guidelines

Note You must set a policy action for every class. If you do not set a policy action for every class, the traffic skips the class that does not have a policy action and matches against the subsequent classes.

After you enter the control-plane command, you can define control plane services for your route processor. For example, you can associate a service policy with the control plane to police all traffic that is destined to the control plane.

Examples

These examples show how to configure trusted hosts with source addresses 10.1.1.1 and 10.1.1.2 to forward Telnet packets to the control plane without constraint, while allowing all remaining Telnet packets to be policed at the specified rate:

Switch(config)# access-list 140 deny tcp host 10.1.1.1 any eq telnet 

! Allow 10.1.1.2 trusted host traffic. 

Switch(config)# access-list 140 deny tcp host 10.1.1.2 any eq telnet 

! Rate limit all other Telnet traffic.

Switch(config)# access-list 140 permit tcp any any eq telnet

! Define class-map "telnet-class."

Switch(config)# class-map telnet-class 

Switch(config-cmap)# match access-group 140

Switch(config-cmap)# exit

Switch(config)# policy-map control-plane

Switch(config-pmap)# class telnet-class

Switch(config-pmap-c)# police 32000 1000 conform transmit exceed drop

Switch(config-pmap-c)# exit

Switch(config-pmap)# exit

! Define aggregate control plane service for the active Route Processor.

Switch(config-cp)# macro global apply system-cpp

Switch(config)# control-plane

Switch(config-cp)# service-police input system-cpp-policy

Switch(config-cp)# exit

Related Commands

class (refer to the Cisco IOS Release 12.2 Command Reference)
class-map
drop (refer to the Cisco IOS Release 12.2 Command Reference)
match access-group (refer to the Cisco IOS Release 12.2 Command Reference)
policy-map
service-policy
show policy-map control-plane

debug adjacency

To display information about the adjacency debugging, use the debug adjacency command. To disable debugging output, use the no form of this command.

debug adjacency [ipc]

no debug adjacency

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to display the information in the adjacency database:

Switch# debug adjacency

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:00

<... output truncated...>

Switch# 

Related Commands

undebug adjacency (same as no debug adjacency)

debug backup

To debug the backup events, use the debug backup command. To disable the debugging output, use the no form of this command.

debug backup

no debug backup

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to debug the backup events:

Switch# debug backup

Backup events debugging is on

Switch# 

Related Commands

undebug backup (same as no debug backup)

debug condition interface

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

debug condition interface {fastethernet mod/port | GigabitEthernet mod/port |
null interface_num | port-channel interface-num | vlan vlan_id}

no debug condition interface {fastethernet mod/port | GigabitEthernet mod/port | null interface_num | port-channel interface-num | vlan vlan_id}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

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

Switch# debug condition interface vlan 1

Condition 2 set

Switch# 

Related Commands

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

debug condition standby

To limit the debugging output for the standby state changes, use the debug condition standby command. To disable the debugging output, use the no form of this command.

debug condition standby {fastethernet mod/port | GigabitEthernet mod/port |
port-channel interface-num | vlan vlan_id group-number}

no debug condition standby {fastethernet mod/port | GigabitEthernet mod/port |
port-channel interface-num | vlan vlan_id group-number}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

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

Examples

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

Switch# debug condition standby vlan 1 0

Condition 3 set

Switch# 

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

Switch# 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     

Switch#           

Related Commands

undebug condition standby (same as no debug condition standby)

debug condition vlan

To limit the VLAN debugging output for a specific VLAN, use the debug condition vlan command. To disable the debugging output, use the no form of this command.

debug condition vlan {vlan_id}

no debug condition vlan {vlan_id}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

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 the removal operation. You can enter n to abort the removal or y to proceed with the removal. If you remove the only condition set, it could result in the display of an excessive number of messages.

Examples

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

Switch# debug condition vlan 1

Condition 4 set

Switch# 

This example shows the message that is displayed when you attempt to disable the last VLAN debug condition:

Switch# 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     

Switch# 

Related Commands

undebug condition vlan (same as no debug condition vlan)

debug dot1x

To enable the debugging for the 802.1X feature, use the debug dot1x command. To disable the debugging output, use the no form of this command.

debug dot1x {all | errors | events | packets | registry | state-machine}

no debug dot1x {all | errors | events | packets | registry | state-machine}

Syntax Description

Defaults

Debugging is disabled.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable the 802.1X debugging for all conditions:

Switch# debug dot1x all

Switch# 

Related Commands

show dot1x
undebug dot1x (same as no debug dot1x)

debug etherchnl

To debug EtherChannel, use the debug etherchnl command. To disable the debugging output, use the no form of this command.

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

no debug etherchnl

Syntax Description

Defaults

The default settings are as follows:

•Debug is disabled.

•All messages are displayed.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

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

Examples

This example shows how to display all the EtherChannel debug messages:

Switch# debug etherchnl

PAgP Shim/FEC debugging is on

22:46:30:FEC:returning agport Po15 for port (Fa2/1)

22:46:31:FEC:returning agport Po15 for port (Fa4/14)

22:46:33:FEC:comparing GC values of Fa2/25 Fa2/15 flag = 1 1

22:46:33:FEC:port_attrib:Fa2/25 Fa2/15 same

22:46:33:FEC:EC - attrib incompatable for Fa2/25; duplex of Fa2/25 is half, Fa2/15 is full

22:46:33:FEC:pagp_switch_choose_unique:Fa2/25, port Fa2/15 in agport Po3 is incompatable

Switch# 

This example shows how to display the EtherChannel IDB debug messages:

Switch# debug etherchnl idb

Agport idb related debugging is on

Switch# 

This example shows how to disable the debugging:

Switch# no debug etherchnl

Switch# 

Related Commands

undebug etherchnl (same as no debug etherchnl)

debug interface

To abbreviate the entry of the debug condition interface command, use the debug interface command. To disable debugging output, use the no form of this command.

debug interface {FastEthernet mod/port | GigabitEthernet mod/port | null |
port-channel interface-num | vlan vlan_id}

no debug interface {FastEthernet mod/port | GigabitEthernet mod/port | null |
port-channel interface-num | vlan vlan_id}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

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

Switch# debug interface vlan 1

Condition 1 set

Switch# 

Related Commands

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

debug ipc

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

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

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

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable the debugging of the IPC events:

Switch# debug ipc events

Special Events debugging is on

Switch# 

Related Commands

undebug ipc (same as no debug ipc)

debug ip dhcp snooping event

To debug the DHCP snooping events, use the debug ip dhcp snooping event command. To disable debugging output, use the no form of this command.

debug ip dhcp snooping event

no debug ip dhcp snooping event

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging of snooping event is disabled.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable the debugging for the DHCP snooping events:

Switch# debug ip dhcp snooping event

Switch# 

This example shows how to disable the debugging for the DHCP snooping events:

Switch# no debug ip dhcp snooping event

Switch# 

Related Commands

debug ip dhcp snooping packet

debug ip dhcp snooping packet

To debug the DHCP snooping messages, use the debug ip dhcp snooping packet command. To disable the debugging output, use the no form of this command.

debug ip dhcp snooping packet

no debug ip dhcp snooping packet

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging of snooping packet is disabled.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable the debugging for the DHCP snooping packets:

Switch# debug ip dhcp snooping packet

Switch# 

This example shows how to disable the debugging for the DHCP snooping packets:

Switch# no debug ip dhcp snooping packet

Switch# 

Related Commands

debug ip dhcp snooping event

debug ip verify source packet

To debug the IP source guard messages, use the debug ip verify source packet command. To disable the debugging output, use the no form of this command.

debug ip verify source packet

no debug ip verify source packet

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging of snooping security packets is disabled.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable debugging for the IP source guard:

Switch# debug ip verify source packet

Switch# 

This example shows how to disable debugging for the IP source guard:

Switch# no debug ip verify source packet

Switch# 

Related Commands

ip dhcp snooping
ip dhcp snooping information option
ip dhcp snooping limit rate
ip dhcp snooping trust
ip verify source vlan dhcp-snooping (refer to Cisco IOS documentation)
show ip dhcp snooping
show ip dhcp snooping binding
show ip verify source (refer to Cisco IOS documentation)

debug lacp

To debug the LACP activity, use the debug lacp command. To disable the debugging output, use the no form of this command.

debug lacp [all | event | fsm | misc | packet]

no debug lacp

Syntax Description

Defaults

Debugging of LACP activity is disabled.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

This command is supported only by the supervisor engine and can be entered only from the Catalyst 4500 series switch console.

Examples

This example shows how to enable the LACP miscellaneous debugging:

Switch# debug lacp 

Port Aggregation Protocol Miscellaneous debugging is on

Switch#                                                           

Related Commands

undebug pagp (same as no debug pagp)

debug monitor

To display the monitoring activity, use the debug monitor command. To disable the debugging output, use the no form of this command.

debug monitor {all | errors | idb-update | list | notifications | platform | requests}

no debug monitor {all | errors | idb-update | list | notifications | platform | requests}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to debug the monitoring errors:

Switch# debug monitor errors

SPAN error detail debugging is on

Switch# 

Related Commands

undebug monitor (same as no debug monitor)

debug nvram

To debug the NVRAM activity, use the debug nvram command. To disable the debugging output, use the no form of this command.

debug nvram

no debug nvram

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to debug NVRAM:

Switch# debug nvram

NVRAM behavior debugging is on

Switch# 

Related Commands

undebug nvram (same as no debug nvram)

debug pagp

To debug the PAgP activity, use the debug pagp command. To disable the debugging output, use the no form of this command.

debug pagp [all | event | fsm | misc | packet]

no debug pagp

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

This command is supported only by the supervisor engine and can be entered only from the Catalyst 4500 series switch console.

Examples

This example shows how to enable the PAgP miscellaneous debugging:

Switch# debug pagp misc

Port Aggregation Protocol Miscellaneous debugging is on

Switch# 

*Sep 30 10:13:03: SP: PAgP: pagp_h(Fa5/6) expired

*Sep 30 10:13:03: SP: PAgP: 135 bytes out Fa5/6

*Sep 30 10:13:03: SP: PAgP: Fa5/6 Transmitting information packet

*Sep 30 10:13:03: SP: PAgP: timer pagp_h(Fa5/6) started with interval 30000

<... output truncated...>

Switch# 

Related Commands

undebug pagp (same as no debug pagp)

debug platform packet protocol lacp

To debug the LACP protocol packets, use the debug platform packet protocol lacp command. To disable the debugging output, use the no form of this command.

debug platform packet protocol lacp [receive | transmit | vlan]

no debug platform packet protocol lacp [receive | transmit | vlan]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable all PM debugging:

Switch# debug platform packet protocol lacp

Switch# 

Related Commands

undebug platform packet protocol lacp (same as no debug platform packet protocol lacp)

debug platform packet protocol pagp

To debug the PAgP protocol packets, use the debug platform packet protocol pagp command. To disable the debugging output, use the no form of this command.

debug platform packet protocol pagp [receive | transmit | vlan]

no debug platform packet protocol pagp [receive | transmit | vlan]

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable all PM debugging:

Switch# debug platform packet protocol pagp

Switch# 

Related Commands

undebug platform packet protocol pagp (same as no debug platform packet protocol pagp)

debug pm

To debug the port manager (PM) activity, use the debug pm command. To disable the debugging output, use the no form of this command.

debug pm {all | card | cookies | etherchnl | messages | port | registry | scp | sm | span | split |
vlan | vp}

no debug pm {all | card | cookies | etherchnl | messages | port | registry | scp | sm | span | split |
vlan | vp}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable all PM debugging:

Switch# debug pm all

Switch# 

Related Commands

undebug pm (same as no debug pm)

debug port-security

To debug port security, use the debug port-security command. To disable the debugging output, use the no form of this command.

debug port-security

no debug port-security

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to enable all PM debugging:

Switch# debug port-security

Switch# 

Related Commands

switchport port-security

debug redundancy

To debug the supervisor engine redundancy, use the debug redundancy command. To disable the debugging output, use the no form of this command.

debug redundancy {errors | fsm | kpa | msg | progression | status | timer}

no debug redundancy

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to debug the redundancy facility timer event debugging:

Switch# debug redundancy timer

Redundancy timer debugging is on

Switch# 

debug spanning-tree

To debug the spanning-tree activities, use the debug spanning-tree command. To disable the debugging output, use the no form of this command.

debug spanning-tree {all | backbonefast | pdu | bpdu-opt | etherchannel | config | events | exceptions | general | ha | mstp | pvst+ | root | snmp | synchronization | uplinkfast}

no debug spanning-tree {all | backbonefast | pdu | bpdu-opt | etherchannel | config | events | exceptions | general | ha | mstp | pvst+ | root | snmp | synchronization | uplinkfast}

Syntax Description

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Examples

This example shows how to debug the spanning-tree PVST+:

Switch# debug spanning-tree pvst+

Spanning Tree PVST+ debugging is on

Switch# 

Related Commands

undebug spanning-tree (same as no debug spanning-tree)

debug spanning-tree backbonefast

To enable debugging of the spanning-tree BackboneFast events, use the debug spanning-tree backbonefast command. To disable the debugging output, use the no form of this command.

debug spanning-tree backbonefast [detail | exceptions]

no debug spanning-tree backbonefast

Syntax Description