Table Of Contents
Cisco IOS Commands for the Catalyst 4000 Family Switches
clear interface gigabitethernet
clear mac-address-table dynamic
debug platform packet protocol lacp
debug platform packet protocol pagp
debug spanning-tree backbonefast
debug spanning-tree uplinkfast
ip dhcp snooping information option
ip igmp snooping report-suppression
ip igmp snooping vlan immediate-leave
qos (global configuration mode)
qos (interface configuration mode)
Cisco IOS Commands for the Catalyst 4000 Family Switches
This chapter contains an alphabetical listing of Cisco IOS commands for the Catalyst 4000 family switches. For information about Cisco IOS commands that are not included in this publication, refer to Cisco IOS Release12.2 Configuration Guides and Command References at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_product_indices_list.html
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
drop
Sets the action to drop packets.
forward
Sets the action to forward packets to their destination.
Defaults
This command has no default settings.
Command Modes
VLAN access-map
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
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 dropSwitch(config-access-map)#This example shows how to define a forward action:
Switch(config-access-map)# action forwardSwitch(config-access-map)#Related Commands
match
show vlan access-map
vlan access-mapapply
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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
The apply command implements the configuration changes 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 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)# applySwitch(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)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
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch (Catalyst 4507R only).
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# configure terminalSwitch (config)# redundancySwitch (config-r)# main-cpuSwitch (config-r-mc)# no auto-sync standardSwitch (config-r-mc)# auto-sync configure-registerSwitch (config-r-mc)#Related Commands
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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(13)EW
Support for LACP was added.
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 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 a usable EtherChannel by connecting two port groups, in on mode, together.
CautionDo 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 specified by port channel 45:
Switch(config-if)# channel-group 45 mode onCreating a port-channel interface Port-channel45Switch(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
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
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 4000 Family Cisco IOS Software Configuration Guide.
Examples
This example shows how to select LACP to manage channeling on the interface:
Switch(config-if)# channel-protocol lacpSwitch(config-if)#Related Commands
channel-group
show etherchannelclass-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
match-all
(Optional) Specifies that all match criteria in the class map must be matched.
match-any
(Optional) Specifies that one or more match criteria must match.
name
Name of the class map.
Defaults
Match all criteria.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
The variables name and acl_name 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:
•
•
•
These optional subcommands are also available:
–
–
–
The following subcommands appear in the CLI help, but they are not supported on LAN interfaces:
•
•
•
•
•
•
•
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# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# class-map ipp5Switch(config-cmap)# match ip precedence 5Switch(config-cmap)#This example shows how to configure the class map to match an already configured access list:
Switch(config-cmap)# match access-group IPacl1Switch(config-cmap)#Related Commands
policy-map
service-policy
show class-map
show policy-map
show policy-map interfaceclear counters
To clear 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses was added.
Usage Guidelines
This command clears all the current interface counters from all interfaces unless you specify an interface.
Note
Examples
This example shows how to clear all interface counters:
Switch# clear countersClear "show interface" counters on all interfaces [confirm] ySwitch#This example shows how to clear counters on a specific interface:
Switch# clear counters vlan 200Clear "show interface" counters on this interface [confirm]ySwitch#Related Commands
show interface counters (refer to Cisco IOS documentation)
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 slot/port
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to clear the hardware logic from a Gigabit Ethernet IEEE 802.3z interface:
Switch# clear interface gigabitethernet 1/1Switch#Related Commands
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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses added.
Examples
This example shows how to clear the hardware logic from a specific VLAN:
Switch# clear interface vlan 5Switch#Related Commands
clear ip access-template
To clear statistical information in access lists, use the clear ip access-template command.
clear ip access-template access-list
Syntax Description
access-list
Number of the access list; valid values are from 100 to 199 for an IP extended access list, and from 2000 to 2699 for an expanded range IP extended access list.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to clear statistical information for an access list:
Switch# clear ip access-template 201Switch#clear ip flow stats
To clear the NetFlow statistics, use the clear ip flow stats command.
clear ip flow stats
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
To use these commands, you need to install the Supervisor Engine IV and the NetFlow Service Card. The show ip cache flow command displays the NetFlow statistics.
Examples
This example shows how to clear the NetFlow statistics:
Switch# clear ip flow statsSwitch#Related Commands
clear ip igmp group
To delete IGMP group cache entries, use the clear ip igmp group command.
clear ip igmp group [{fastethernet slot/port} | {GigabitEthernet slot/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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
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 entries from the IGMP cache, enter the clear ip igmp group command with no arguments.
Examples
This example shows how to clear entries for a specific group from the IGMP cache:
Switch# clear ip igmp group 224.0.255.1Switch#This example shows how to clear IGMP group cache entries from a specific interface:
Switch# clear ip igmp group gigabitethernet 2/2Switch#Related Commands
ip host (refer to Cisco IOS documentation)
show ip igmp groups (refer to Cisco IOS documentation)
show ip igmp interfaceclear ip mfib counters
To clear global MFIB counters and 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to clear all the active MFIB routes and global counters:
Switch# clear ip mfib countersSwitch#Related Commands
clear ip mfib fastdrop
To clear all 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
If new fast-dropped packets arrive, new fast drop entries are created.
Examples
This example shows how to clear all fast drop entries:
Switch# clear ip mfib fastdropSwitch#Related Commands
ip mfib fastdrop
show ip mfib fastdropclear lacp counters
To clear statistics for all 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
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
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 countersSwitch#Related Commands
clear mac-address-table dynamic
To clear 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses added.
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 dynamic L2 entries for a specific interface (gi1/1):
Switch# clear mac-address-table dynamic interface gi1/1Switch#Related Commands
mac-address-table aging-time
main-cpu
show mac-address-table addressclear pagp
To clear 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to clear port-channel information for a specific group:
Switch# clear pagp 32Switch#This example shows how to all clear port-channel traffic filters:
Switch# clear pagp countersSwitch#Related Commands
clear qos
To clear global and per-interface aggregate QoS counters, use the clear qos command.
clear qos [aggregate-policer [name] | interface {{fastethernet | GigabitEthernet} {slot/interface}} | vlan {vlan_num} | port-channel {number}]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
Note
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 global and per-interface aggregate QoS counters for all protocols:
Switch# clear qosSwitch#This example shows how to clear specific protocol aggregate QoS counters for all interfaces:
Switch# clear qos aggregate-policerSwitch#Related Commands
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
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
If you do not specify a vlan-id; the software-cached counter values for all existing VLANs are cleared.
Examples
Switch# clear vlan 10 countersClear "show vlan" counters on this vlan [confirm]ySwitch#Related Commands
clear vmps statistics
To clear 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
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
Switch# clear vmps statisticsSwitch#Related Commands
vmps reconfirm (privileged EXEC)
show vmpsdebug adjacency
To display adjacency debugging information, 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to display information in the adjacency database:
Switch# debug adjacency4d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:004d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:004d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:004d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:004d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:004d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:004d02h: ADJ: add 172.20.52.36 (GigabitEthernet1/1) via ARP will expire: 04:00:004d02h: 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 backup events, use the debug backup command. To disable 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to debug backup events:
Switch# debug backupBackup events debugging is onSwitch#Related Commands
undebug backup (same as no debug backup)
debug condition interface
To limit debugging output of interface-related activities, use the debug condition interface command. To disable debugging output, use the no form of this command.
debug condition interface {fastethernet slot/port | GigabitEthernet slot/port |
null interface_num | port-channel interface-num | vlan vlan_id}no debug condition interface {fastethernet slot/port | GigabitEthernet slot/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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses added.
Examples
This example shows how to limit debugging output to VLAN interface 1:
Switch# debug condition interface vlan 1Condition 2 setSwitch#Related Commands
debug interface
undebug condition interface (same as no debug condition interface)debug condition standby
To limit debugging output for standby state changes, use the debug condition standby command. To disable debugging output, use the no form of this command.
debug condition standby {fastethernet slot/port | GigabitEthernet slot/port |
port-channel interface-num | vlan vlan_id group-number}no debug condition standby {fastethernet slot/port | GigabitEthernet slot/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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses added.
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, it could cause an excessive number of debugging messages.
Examples
This example shows how to limit the debugging output to group 0 in VLAN 1:
Switch# debug condition standby vlan 1 0Condition 3 setSwitch#This example shows the display if you try to turn off the last standby debug condition:
Switch# no debug condition standby vlan 1 0This condition is the last standby condition set.Removing all conditions may cause a flood of debuggingmessages to result, unless specific debugging flagsare first removed.Proceed with removal? [yes/no]: n% Operation abortedSwitch#Related Commands
undebug condition standby (same as no debug condition standby)
debug condition vlan
To limit VLAN debugging output for a specific VLAN, use the debug condition vlan command. To disable 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses added.
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 debugging output to VLAN 1:
Switch# debug condition vlan 1Condition 4 setSwitch#This example shows the message that is displayed when you attempt to disable the last VLAN debug condition:
Switch# no debug condition vlan 1This condition is the last vlan condition set.Removing all conditions may cause a flood of debuggingmessages to result, unless specific debugging flagsare first removed.Proceed with removal? [yes/no]: n% Operation abortedSwitch#Related Commands
undebug condition vlan (same as no debug condition vlan)
debug dot1x
To enable debugging for the 802.1x feature, use the debug dot1x command. Use the no form of this command to disable debugging output.
debug dot1x {all | errors | events | packets | registry | state-machine}
no debug dot1x {all | errors | events | packets | registry | state-machine}
Syntax Description
Defaults
Debuggin is disabled.
Command Modes
Privileged EXEC
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Related Commands
show dot1x
undebug dot1x (same as no debug dot1x)debug etherchnl
To debug EtherChannel, use the debug etherchnl command. To disable 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:
•
•
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
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:
Switch# debug etherchnlPAgP Shim/FEC debugging is on22: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 122:46:33:FEC:port_attrib:Fa2/25 Fa2/15 same22:46:33:FEC:EC - attrib incompatable for Fa2/25; duplex of Fa2/25 is half, Fa2/15 is full22:46:33:FEC:pagp_switch_choose_unique:Fa2/25, port Fa2/15 in agport Po3 is incompatableSwitch#This example shows how to display EtherChannel IDB debug messages:
Switch# debug etherchnl idbAgport idb related debugging is onSwitch#This example shows how to disable debugging:
Switch# no debug etherchnlSwitch#Related Commands
undebug etherchnl (same as no debug etherchnl)
debug interface
To abbreviate 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 slot/port | GigabitEthernet slot/port | null |
port-channel interface-num | vlan vlan_id}no debug interface {FastEthernet slot/port | GigabitEthernet slot/port | null |
port-channel interface-num | vlan vlan_id}Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses added.
Examples
This example shows how to limit debugging to interface VLAN 1:
Switch# debug interface vlan 1Condition 1 setSwitch#Related Commands
debug condition interface
undebug interface (same as no debug interface)debug ipc
To debug IPC activity, use the debug ipc command. To disable 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
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable debugging of IPC events:
Switch# debug ipc eventsSpecial Events debugging is onSwitch#Related Commands
undebug ipc (same as no debug ipc)
debug ip dhcp snooping event
To debug 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
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable debugging for DHCP snooping events:
Switch# debug ip dhcp snooping eventSwitch#
This example shows how to disable debugging for DHCP snooping events:
Switch# no debug ip dhcp snooping eventSwitch#
Related Commands
debug ip dhcp snooping packet
To debug DHCP snooping messages, use the debug ip dhcp snooping packet command. To disable 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.
Privileged EXEC
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable debugging for DHCP snooping packets:
Switch# debug ip dhcp snooping packetSwitch#This example shows how to disable debugging for DHCP snooping packets:
Switch# no debug ip dhcp snooping packetSwitch#Related Commands
debug lacp
To debug LACP activity, use the debug lacp command. To disable 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
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console.
Examples
This example shows how to enable LACP miscellaneous debugging:
Switch# debug lacpPort Aggregation Protocol Miscellaneous debugging is onSwitch#Related Commands
undebug pagp (same as no debug pagp)
debug monitor
To display monitoring activity, use the debug monitor command. To disable 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to debug monitoring errors:
Switch# debug monitor errorsSPAN error detail debugging is onSwitch#Related Commands
undebug monitor (same as no debug monitor)
debug nvram
To debug NVRAM activity, use the debug nvram command. To disable 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to debug NVRAM:
Switch# debug nvramNVRAM behavior debugging is onSwitch#Related Commands
undebug nvram (same as no debug nvram)
debug pagp
To debug PAgP activity, use the debug pagp command. To disable 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console.
Examples
This example shows how to enable PAgP miscellaneous debugging:
Switch# debug pagp miscPort Aggregation Protocol Miscellaneous debugging is onSwitch#*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 LACP protocol packets, use the debug platform packet protocol lacp command. To disable 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
receive
Enables platform packet reception debugging functions.
transmit
Enables platform packet transmission debugging functions.
vlan
Enables platform packet VLAN debugging functions.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable all PM debugging:
Switch# debug platform packet protocol lacpSwitch#Related Commands
undebug platform packet protocol lacp (same as no debug platform packet protocol lacp)
debug platform packet protocol pagp
To debug PAgP protocol packets, use the debug platform packet protocol lacp command. To disable 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
receive
Enables platform packet reception debugging functions.
transmit
Enables platform packet transmission debugging functions.
vlan
Enables platform packet VLAN debugging functions.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable all PM debugging:
Switch# debug platform packet protocol pagpSwitch#Related Commands
undebug platform packet protocol pagp (same as no debug platform packet protocol pagp)
debug pm
To debug port manager (PM) activity, use the debug pm command. To disable 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
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable all PM debugging:
Switch# debug pm allSwitch#Related Commands
undebug pm (same as no debug pm)
debug psecure
To debug port security, use the debug psecure command. To disable debugging output, use the no form of this command.
debug psecure
no debug psecure
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable all PM debugging:
Switch# debug psecureSwitch#Related Commands
debug redundancy
To debug supervisor redundancy, use the debug redundancy command. To disable 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
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch (Catalyst 4507R only).
Examples
This example shows how to debug redundancy facility timer event debugging:
Switch# debug redundancy timerRedundancy timer debugging is onSwitch#debug smf updates
To debug software MAC filter (SMF) address insertions and deletions, use the debug smf updates command. To disable debugging output, use the no form of this command.
debug smf updates
no debug smf updates
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to debug SMF updates:
Switch# debug smf updatesSoftware MAC filter address insertions and deletions debugging is onSwitch#Related Commands
undebug smf (same as no debug smf)
debug spanning-tree
To debug spanning tree activities, use the debug spanning-tree command. To disable debugging output, use the no form of this command.
debug spanning-tree {all | bpdu | bpdu-opt | etherchannel | config | events | exceptions |
general | mst | pvst+ | root | snmp}no debug spanning-tree {all | bpdu | bpdu-opt | etherchannel | config | events | exceptions | general | mst | pvst+ | root | snmp}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to debug spanning tree PVST+:
Switch# debug spanning-tree pvst+Spanning Tree PVST+ debugging is onSwitch#Related Commands
undebug spanning-tree (same as no debug spanning-tree)
debug spanning-tree backbonefast
To enable debugging of spanning tree BackboneFast events, use the debug spanning-tree backbonefast command. To disable debugging output, use the no form of this command.
debug spanning-tree backbonefast [detail | exceptions]
no debug spanning-tree backbonefast
Syntax Description
detail
(Optional) Displays detailed BackboneFast debugging messages.
exceptions
(Optional) Enables debugging of spanning tree BackboneFast exceptions.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the switch console.
Examples
This example shows how to enable debugging and to display detailed spanning tree BackboneFast debugging information:
Switch# debug spanning-tree backbonefast detailSpanning Tree backbonefast detail debugging is onSwitch#Related Commands
undebug spanning-tree backbonefast (same as no debug spanning-tree backbonefast)
debug spanning-tree switch
To enable switch shim debugging, use the debug spanning-tree switch command. To disable debugging output, use the no form of this command.
debug spanning-tree switch {all | errors | general | pm | rx {decode | errors | interrupt |
process} | state | tx [decode]}no debug spanning-tree switch {all | errors | general | pm | rx {decode | errors | interrupt | process} | state | tx [decode]}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is supported only by the supervisor engine and can be entered only from the switch console.
Examples
This example shows how to enable transmit BPDU debugging on the spanning tree switch shim:
Switch# debug spanning-tree switch txSpanning Tree Switch Shim transmit bpdu debugging is on*Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/9 303*Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/9 304*Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/9 305*Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/9 349*Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/9 350*Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/9 351*Sep 30 08:47:33: SP: STP SW: TX: bpdu of type ieee-st size 92 on FastEthernet5/9 801<... output truncated...>Switch#Related Commands
undebug spanning-tree switch (same as no debug spanning-tree switch)
debug spanning-tree uplinkfast
To enable debugging of spanning tree UplinkFast events, use the debug spanning-tree uplinkfast command. To disable debugging output, use the no form of this command.
debug spanning-tree uplinkfast [exceptions]
no debug spanning-tree uplinkfast
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is supported only by the supervisor engine and can be entered only from the switch console.
Examples
This example shows how to debug spanning tree UplinkFast exceptions:
Switch# debug spanning-tree uplinkfast exceptionsSpanning Tree uplinkfast exceptions debugging is onSwitch#Related Commands
undebug spanning-tree uplinkfast (same as no debug spanning-tree uplinkfast)
debug sw-vlan
To debug VLAN manager activities, use the debug sw-vlan command. To disable debugging output, use the no form of this command.
debug sw-vlan {badpmcookies | events | management | packets | registries}
no debug sw-vlan {badpmcookies | events | management | packets | registries}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to debug software VLAN events:
Switch# debug sw-vlan eventsvlan manager events debugging is onSwitch#Related Commands
undebug sw-vlan (same as no debug sw-vlan)
debug sw-vlan ifs
To enable VLAN manager IOS file system (IFS) error tests, use the debug sw-vlan ifs command. To disable debugging output, use the no form of this command.
debug sw-vlan ifs {open {read | write} | read {1 | 2 | 3 | 4} | write}
no debug sw-vlan ifs {open {open | read} | read {1 | 2 | 3 | 4} | write}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
The following are four types of file read operations:
•
•
•
•
Examples
This example shows how to debug of TLV data errors during a file-read operation:
Switch# debug sw-vlan ifs read 4vlan manager ifs read # 4 errors debugging is onSwitch#Related Commands
undebug sw-vlan ifs (same as no debug sw-vlan ifs)
debug sw-vlan notification
To enable debugging messages that trace the activation and deactivation of ISL VLAN IDs, use the debug sw-vlan notification command. To disable debugging output, use the no form of this command.
debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | pruningcfgchange | statechange}
no debug sw-vlan notification {accfwdchange | allowedvlancfgchange | fwdchange | linkchange | modechange | pruningcfgchange | statechange}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to debug the software VLAN interface mode change notifications:
Switch# debug sw-vlan notification modechangevlan manager port mode change notification debugging is onSwitch#Related Commands
undebug sw-vlan notification (same as no debug sw-vlan notification)
debug sw-vlan vtp
To enable debugging messages to be generated by the VTP protocol code, use the debug sw-vlan vtp command. To disable debugging output, use the no form of this command.
debug sw-vlan vtp {events | packets | pruning [packets | xmit] | xmit}
no debug sw-vlan vtp {events | packets | pruning [packets | xmit] | xmit}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
If you do not enter any more parameters after entering pruning, the VTP pruning debugging messages are displayed.
Examples
This example shows how to debug software VLAN outgoing VTP packets:
Switch# debug sw-vlan vtp xmitvtp xmit debugging is onSwitch#Related Commands
undebug sw-vlan vtp (same as no debug sw-vlan vtp)
debug udld
To enable debugging of UDLD activity, use the debug udld command. To disable debugging output, use the no form of this command.
debug udld {events | packets | registries}
no debug udld {events | packets | registries}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command is supported by the supervisor engine only and can be entered only from the Catalyst 4000 family switch console.
Examples
This example shows how to enable debugging of UDLD events:
Switch# debug udld eventsUDLD events debugging is onSwitch#This example shows how to enable debugging of UDLD packets:
Switch# debug udld packetsUDLD packets debugging is onSwitch#This example shows how to enable debugging of UDLD registry events:
Switch# debug udld registriesUDLD registries debugging is onSwitch#Related Commands
undebug udld (same as no debug udld)
debug vqpc
To debug VLAN Query Protocol (VQP), use the debug vqpc command. To disable debugging output, use the no form of this command.
debug vqpc [all | cli | events | learn | packet]
no debug vqpc [all | cli | events | learn | packet]
Syntax Description
all
(Optional) Debugs all VQP events.
cli
(Optional) Debugs VQP command line interface.
events
Debugs VQP events.
learn
Debugs VQP address learning.
packet
Debugs VQP packets.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable all PM debugging:
Switch# debug vqpc allSwitch#Related Commands
vmps reconfirm (privileged EXEC)
define interface-range
To create a macro of interfaces, use the define interface-range command.
define interface-range macro-name interface-range
Syntax Description
macro-name
Name of the interface range macro; up to 32 characters.
interface-range
List of valid ranges when specifying interfaces; see "Usage Guidelines."
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
The macro name is a character string of up to 32 characters.
A macro can contain up to five ranges. An interface range cannot span modules.
When entering the interface-range, use these formats:
•
•
Valid values for interface-type are as follows:
•
•
•
Examples
This example shows how to create a multiple-interface macro:
Switch(config)# define interface-range macro1 gigabitethernet 4/1 - 6, fastethernet 2/1 - 5Switch(config)#Related Commands
dot1x initialize
To unauthorize an interface before reinitializing 802.1x, use the dot1x initialize command.
dot1x initialize interface
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
Use this command to initialize state machines and to set up the environment for fresh authentication.
Examples
This example shows how to initialize the 802.1x state machines on an interface:
Switch# dot1x initializeSwitch#Related Commands
dot1x max-req
To set the maximum times the switch sends an Extensible Authentication Protocol (EAP)-request/identity frame to the client before restarting the authentication process, use the dot1x max-req command. To return to the default setting, use the no form of this command.
dot1x max-req count
no dot1x max-req
Syntax Description
count
Number of times that the switch sends an EAP-request/identity frame before restarting the authentication process; valid values are from 1 to 10.
Defaults
The switch sends a frame request a maximum of two times.
Command Modes
Interface configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
You can verify your settings by entering the show dot1x privileged EXEC command.
Examples
This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity frame before restarting the authentication process:
Switch(config-if)# dot1x max-req 5Switch(config-if)#Related Commands
dot1x multiple-hosts
To allow multiple hosts (clients) on an 802.1x-authorized port that has the dot1x port-control interface configuration command set to auto, use the dot1x multiple-hosts command. To return to the default setting, use the no form of this command.
dot1x multiple-hosts
no dot1x multiple-hosts
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Interface configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
This command enables you to attach multiple clients to a single 802.1x-enabled port. In this mode, only one of the attached hosts must be successfully authorized for all hosts to be granted network access. If the port becomes unauthorized (re-authentication fails, or an Extensible Authentication Protocol over LAN [EAPOL]-logoff message is received), all attached clients are denied access to the network.
Examples
This example shows how to enable 802.1x on Gigabit Ethernet 1/1 and to allow multiple hosts:
Switch(config)# interface gigabitethernet1/1Switch(config-if)# dot1x port-control autoSwitch(config-if)# dot1x multiple-hostsYou can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
dot1x port-control
To enable manual control of the authorization state on a port, use the dot1x port-control command. To return to the default setting, use the no form of this command.
dot1x port-control {auto | force-authorized | force-unauthorized}
no dot1x port-control
Syntax Description
Defaults
The port 802.1x authorization is disabled.
Command Modes
Interface configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
The 802.1x protocol is supported on both Layer 2 static-access ports and Layer 3-routed ports.
You can use the auto keyword only if the port is not configured as one of these:
•
•
•
•
To globally disable 802.1x on the switch, you must disable it on each port. There is no global configuration command for this task.
Examples
This example shows how to enable 802.1x on Gigabit Ethernet 1/1:
Switch(config)# interface gigabitethernet1/1Switch(config-if)# dot1x port-control autoSwitch#You can verify your settings by using show dot1x all or show dot1x interface int to show the port-control status. An enabled status means the port-control value is set either to auto or to force-unauthorized.
Related Commands
dot1x re-authenticate
To manually initiate a reauthentication of all 802.1x-enabled ports or the specified 802.1x-enabled port, use the dot1x re-authenticate command.
dot1x re-authenticate [interface interface-id]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
You can use this command to reauthenticate a client without waiting for the configured number of seconds between reauthentication attempts (re-authperiod) and automatic reauthentication.
Examples
This example shows how to manually reauthenticate the device connected to Gigabit Ethernet interface 0/1:
Switch# dot1x re-authenticate interface gigabitethernet1/1Starting reauthentication on gigabitethernet1/1Switch#dot1x re-authentication
To enable periodic reauthentication of the client, use the dot1x re-authentication command. To return to the default setting, use the no form of this command.
dot1x re-authentication
no dot1x re-authentication
Syntax Description
This command has no arguments or keywords.
Defaults
The periodic reauthentication is disabled.
Command Modes
Interface configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
You configure the amount of time between periodic reauthentication attempts by using the dot1x timeout re-authperiod global configuration command.
Examples
This example shows how to disable periodic reauthentication of the client:
Switch(config-if)# no dot1x re-authenticationSwitch(config-if)#This example shows how to enable periodic reauthentication and set the number of seconds between reauthentication attempts to 4000 seconds:
Switch(config-if)# dot1x re-authenticationSwitch(config-if)# dot1x timeout re-authperiod 4000Switch#You can verify your settings by entering the show dot1x privileged EXEC command.
Related Commands
dot1x system-auth-control
To enable 802.1x authentication on the switch, use the dot1x system-auth-control command. To disable 802.1x authentication on the system, use the no form of this command.
dot1x system-auth-control
no dot1x system-auth-control
Syntax Description
This command has no arguments or keywords.
Defaults
The 802.1x authentication is disabled.
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
As the port-control value defaults to force-authorized, you can easily enable 802.1x on a port by setting the port-control value to auto.
When enabled, each port authorization status is controlled according to the value of the port-control parameter on the port.
When disabled, all ports function as though the port-control parameter is set to force-authorized.
Examples
This example shows how to enable 802.1x authentication:
Switch(config)# dot1x system-auth-controlSwitch(config)#Related Commands
dot1x timeout
To set the reauthentication timer, use the dot1x timeout command. To return to the default setting, use the no form of this command.
dot1x timeout {reauth-period seconds | quiet-period seconds | tx-period seconds |
supp-timeout seconds | server-timeout seconds}no dot1x timeout {reauth-period | quiet-period | tx-period | supp-timeout | server-timeout}
Syntax Description
Defaults
The default settings are as follows:
•
•
•
•
•
Command Modes
Interface configuration
Command History
12.1(12)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
Periodic reauthentication must be enabled before entering the dot1x timeout re-authperiod command. Enter the dot1x re-authentication command to enable periodic reauthentication.
This example shows how to set 60 as the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before retransmitting the request:
Switch(config-if)# dot1x timeout tx-period 60Switch(config-if)#You can verify your settings by entering the show dot1x privileged EXEC command.
Related Commands
dot1x initialize show dot1xshow dot1x
duplex
To configure the duplex operation on an interface, use the duplex command. To return to the default setting, use the no form of this command.
duplex {auto | full | half}
no duplex
Syntax Description
auto
Specifies autonegotiation operation.
full
Specifies full-duplex operation.
half
Specifies half-duplex operation.
Defaults
Half duplex operation
Command Modes
Interface configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
Table 2-2 lists the supported command options by interface.
If the transmission speed on a 16-port RJ-45 Gigabit Ethernet port is set to 1000, duplex mode is set to full. If the transmission speed is changed to 10 or 100, the duplex mode stays at full. You must configure the correct duplex mode on the switch when the transmission speed changes to 10 or 100 from 1000 Mbps.
Note
Caution
Table 2-3 describes the system performance for different combinations of the duplex and speed modes. The specified duplex command configured with the specified speed command produces the resulting action shown in the table.
Examples
This example shows how to configure the interface for full-duplex operation:
Switch(config-if)# duplex fullSwitch(config-if)#Related Commands
speed
interface (refer to Cisco IOS documentation)
show controllers (refer to Cisco IOS documentation)
show interfaces (refer to Cisco IOS documentation)errdisable detect
To enable error disable detection, use the errdisable detect command. To disable the error disable detection feature, use the no form of this command.
errdisable detect cause {all | dtp-flap | link-flap | pagp-flap}
no errdisable detect cause {all | dtp-flap | link-flap | pagp-flap}
Syntax Description
Defaults
All error disable causes are detected.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
A cause (dtp-flap, link-flap, pagp-flap) is defined as the reason the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in error-disabled state (an operational state similar to link down state).
You must enter the shutdown command and then the no shutdown command to recover an interface manually from error disable.
Examples
This example shows how to enable error disable detection for the link-flap error disable cause:
Switch(config)# errdisable detect cause link-flapSwitch(config)#Related Commands
show errdisable detect
show interfaces statuserrdisable recovery
To configure the recovery mechanism variables, use the errdisable recovery command. To return to the default setting, use the no form of this command.
errdisable recovery [cause {all | bpduguard | dtp-flap | link-flap | pagp-flap |
security-violation | udld}] | [interval {interval}]no errdisable recovery [cause {all | bpduguard | dtp-flap | link-flap | pagp-flap | security-violation | udld}] | [interval {interval}]
Syntax Description
Defaults
Error disable recovery is disabled.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
A cause (bpduguard, dtp-flap, link-flap, pagp-flap, udld) is defined as the reason the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in error-disabled state (an operational state similar to link down state). If you do not enable error-disable recovery for the cause, the interface stays in error-disabled state until a shutdown and no shutdown occurs. If you enable recovery for a cause, the interface is brought out of error-disabled state and allowed to retry operation again once all the causes have timed out.
You must enter the shutdown command and then the no shutdown command to recover an interface manually from error disable.
Examples
This example shows how to enable the recovery timer for the BPDU guard error disable cause:
Switch(config)# errdisable recovery cause bpduguardSwitch(config)#This example shows how to set the timer to 300 seconds:
Switch(config)# errdisable recovery interval 300Switch(config)#Related Commands
show errdisable recovery
show interfaces statusflowcontrol
To configure a gigabit interface to send or receive pause frames, use the flowcontrol command. To disable the flow control setting, use the no form of this command.
flowcontrol {receive | send} {off | on | desired}
no flowcontrol {receive | send} {off | on | desired}
Syntax Description
Defaults
The default settings for GigabitEthernet interfaces are as follows:
•
•
•
•
Table 2-4 shows the default settings for modules:
Command Modes
Interface configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
Pause frames are special packets that signal a source to stop sending frames for a specific period of time because the buffers are full.
Table 2-5 describes guidelines for using different configurations of the send and receive keywords with the flowcontrol command.
Table 2-6 identifies how flow control will be forced or negotiated on gigabit interfaces based on their speed settings.
Note
Examples
This example shows how to enable send flow control:
Switch(config-if)# flowcontrol receive onSwitch(config-if)#This example shows how to disable send flow control:
Switch(config-if)# flowcontrol send offSwitch(config-if)#This example shows how to set receive flow control to desired:
Switch(config-if)# flowcontrol receive desiredSwitch(config-if)#Related Commands
interface port-channel
interface range
interface vlan
show flowcontrol
show running-config (refer to Cisco IOS Documentation)
speedhw-module reset
To reset a module by turning the power off and then on, use the hw-module reset command.
hw-module {module num} reset
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to reload a specific module:
Switch# hw-module module 3 resetSwitch#instance
To map a VLAN or a set of VLANs to an MST instance, use the instance command. To return the VLANs to the common instance default, use the no form of this command.
instance instance-id {vlans vlan-range}
no instance instance-id
Syntax Description
Defaults
Mapping is disabled.
Command Modes
MST configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
The mapping is incremental, not absolute. This means that when you enter a range of VLANs, this range is added or removed to the existing ones.
Any unmapped VLAN is mapped to the CIST instance.
Examples
This example shows how to map a range of VLANs to instance 2:
Switch(config-mst)# instance 2 vlans 1-100Switch(config-mst)#This example shows how to map a VLAN to instance 5:
Switch(config-mst)# instance 5 vlans 1100Switch(config-mst)#This example shows how to move a range of VLANs from instance 2 to the CIST instance:
Switch(config-mst)# no instance 2 vlans 40-60Switch(config-mst)#This example shows how to move all the VLANs mapped to instance 2 back to the CIST instance:
Switch(config-mst)# no instance 2Switch(config-mst)#Related Commands
name
revision
show spanning-tree mst
spanning-tree mst configurationinterface port-channel
To access or create a port channel interface, use the interface port-channel command.
interface port-channel channel-group
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
You do not have to create a port channel interface before assigning a physical interface to a channel group. A port channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.
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.
Only one port channel in a channel group is allowed.
Caution
If you want to use CDP, you must configure it only on the physical Fast Ethernet interface and not on the port-channel interface.
Examples
This example creates a port channel interface with a channel group number of 64:
Switch(config)# interface port-channel 64Switch(config)#Related Commands
channel-group
show etherchannelinterface range
To run a command on multiple ports at the same time, use the interface range command.
interface range {vlan vlan_id - vlan_id} {port-range | macro name}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Interface configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended VLAN addresses added.
Usage Guidelines
You can use the interface range command on existing VLAN SVIs only. To display VLAN SVIs, enter the show running config command. VLANs not displayed cannot be used in the interface range command.
The values entered with the interface range command are applied to all existing VLAN SVIs.
Before you can use a macro, you must define a range using the define interface-range command.
All configuration changes made to a port range are saved to NVRAM, but port ranges created with the interface range command do not get saved to NVRAM.
You can enter the port range in two ways:
•
•
You can either specify the ports or the name of a port-range macro. A port range must consist of the same port type, and the ports within a range cannot span modules.
You can define up to five port ranges on a single command; separate each range with a comma.
When you define a range, you must enter a space between the first port and the hyphen (-):
interface range gigabitethernet 5/1 -20, gigabitethernet4/5 -20.Use these formats when entering the port-range:
•
•
Valid values for interface-type are as follows:
•
•
•
You cannot specify both a macro and an interface range in the same command. After creating a macro, you can enter additional ranges. Likewise, if you have already entered an interface range, the CLI does not allow you to enter a macro.
You can specify a single interface in the port-range value. This makes the command similar to the interface interface-number command.
Examples
This example shows how to use the interface range command to interface to FE 5/18 - 20:
Switch(config)# interface range fastethernet 5/18 - 20Switch(config-if)#This command shows how to run a port-range macro:
Switch(config)# interface range macro macro1Switch(config-if)#Related Commands
define interface-range
show running config (refer to Cisco IOS documentation)interface vlan
To create or access a Layer 3 switch virtual interface (SVI), use the interface vlan command. To delete an SVI, use the no form of this command.
interface vlan vlan_id
no interface vlan vlan_id
Syntax Description
Defaults
Fast EtherChannel is not specified.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
SVIs are created the first time you enter the interface vlan vlan_id command for a particular VLAN. The vlan_id value corresponds to the VLAN tag associated with data frames on an ISL or 802.1Q encapsulated trunk, or the VLAN ID configured for an access port. A message is displayed whenever a VLAN interface is newly created, so you can check that you entered the correct VLAN number.
If you delete an SVI by entering the no interface vlan vlan_id command, the associated interface is forced into an administrative down state and marked as deleted. The deleted interface will no longer be visible in a show interface command.
You can reinstate a deleted SVI by entering the interface vlan vlan_id command for the deleted interface. The interface comes back up, but much of the previous configuration will be gone.
Examples
This example shows the output when you enter the interface vlan vlan_id command for a new VLAN number:
Switch(config)# interface vlan 23% Creating new VLAN interface.Switch(config)#ip cef load-sharing algorithm
To configure the load-sharing hash function so that the source TCP/UDP port, the destination TCP/UDP port, or both can be included in the hash in addition to the source and destination IP addresses, use the ip cef load-sharing algorithm command. To revert back to the default, which does not include the ports, use the no form of this command.
ip cef load-sharing algorithm {include-ports {source source | destination dest} | original | tunnel | universal}
no ip cef load-sharing algorithm{include-ports {source source | destination dest} | original | tunnel | universal}
Syntax Description
Defaults
Default load-sharing algorithm is disabled.
Note
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
The original algorithm, tunnel algorithm, and universal algorithm are routed through hardware. For software-routed packets, they are treated differently. The include-ports option does not apply to software-switched traffic.
Examples
This example shows how to configure ip cef load-sharing algorithm with the include-ports option:
Switch(config)# ip cef load-sharing algorithm include-portsSwitch(config)#Related Commands
ip dhcp snooping
To enable DHCP snooping globally, use the ip dhcp snooping command. To disable DHCP snooping, use the no form of this command.
ip dhcp snooping
no ip dhcp snooping
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP snooping is disabled.
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
You must enable DHCP snooping globally before you can use DHCP snooping on a VLAN.
Examples
This example shows how to enable DHCP snooping:
Switch(config)# ip dhcp snoopingSwitch(config)#
This example shows how to disable DHCP snooping:
Switch(config)# no ip dhcp snoopingSwitch(config)#
Related Commands
ip dhcp snooping information option
ip dhcp snooping limit rate
ip dhcp snooping trust
ip dhcp snooping vlan
show ip dhcp snooping
show ip dhcp snooping bindingip dhcp snooping information option
To enable DHCP option 82 data insertion, use the ip dhcp snooping information option command. To disable DHCP option 82 data insertion, use the no form of this command.
ip dhcp snooping information option
no ip dhcp snooping information option
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP option 82 data insertion is enabled.
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable DHCP option 82 data insertion:
Switch(config)# ip dhcp snooping information optionSwitch(config)#
This example shows how to disable DHCP option 82 data insertion:
Switch(config)# no ip dhcp snooping information optionSwitch(config)#
Related Commands
ip dhcp snooping
ip dhcp snooping limit rate
ip dhcp snooping trust
ip dhcp snooping vlan
show ip dhcp snooping
show ip dhcp snooping bindingip dhcp snooping limit rate
To configure the number of DHCP messages an interface can receive per second, use the ip dhcp snooping limit rate command. To disable DHCP snooping rate limiting, use the no form of this command.
ip dhcp snooping limit rate rate
no ip dhcp snooping limit rate
Syntax Description
Defaults
DHCP snooping rate limiting is disabled.
Command Modes
Interface configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
Normally, the rate limit applies to untrusted interfaces. If you want to set up rate limiting for trusted interfaces, keep in mind that trusted interfaces aggregate all DHCP traffic in the switch, and you will need to adjust the interfaces rate limit to a higher value.
Examples
This example shows how to enable DHCP message rate limiting:
Switch(config-if)# ip dhcp snooping limit rate 150Switch(config-if)#
This example shows how to disable DHCP message rate limiting:
Switch(config-if)# no ip dhcp snooping limit rateSwitch(config-if)#
Related Commands
ip dhcp snooping
ip dhcp snooping information option
ip dhcp snooping trust
ip dhcp snooping vlan
show ip dhcp snooping
show ip dhcp snooping bindingip dhcp snooping trust
To configure an interface as trusted for DHCP snooping purposes, use the ip dhcp snooping trust command. To configure an interface as untrusted, use the no form of this command.
ip dhcp snooping trust
no ip dhcp snooping trust
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP snooping trust is disabled.
Command Modes
Interface configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable DHCP snooping trust on an interface:
Switch(config-if)# ip dhcp snooping trustSwitch(config-if)#
This example shows how to disable DHCP snooping trust on an interface:
Switch(config-if)# no ip dhcp snooping trustSwitch(config-if)#
Related Commands
ip dhcp snooping
ip dhcp snooping information option
ip dhcp snooping limit rate
ip dhcp snooping vlan
show ip dhcp snooping
show ip dhcp snooping bindingip dhcp snooping vlan
Use the ip dhcp snooping vlan command to enable DHCP snooping on a VLAN. To disable DHCP snooping on a VLAN, use the no form of this command.
ip dhcp snooping [vlan number]
no ip dhcp snooping [vlan number]
Syntax Description
Defaults
DHCP snooping is disabled.
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
DHCP snooping is enabled on a VLAN only if both the global snooping and the VLAN snooping are enabled.
Examples
This example shows how to enable DHCP snooping on a VLAN:
Switch(config)# ip dhcp snooping vlan 10Switch(config)#
This example shows how to disable DHCP snooping on a VLAN:
Switch(config)# no ip dhcp snooping vlan 10Switch(config)#
This example shows how to enable DHCP snooping on a group of VLANs:
Switch(config)# ip dhcp snooping vlan 10 55Switch(config)#
This example shows how to disable DHCP snooping on a group of VLANs:
Switch(config)# no ip dhcp snooping vlan 10 55Switch(config)#
Related Commands
ip dhcp snooping
ip dhcp snooping information option
ip dhcp snooping limit rate
ip dhcp snooping trust
show ip dhcp snooping
show ip dhcp snooping bindingip flow-cache timeout
To specify the period of time before flows should timeout, use the ip flow-cache command. To return to the default timeout period, use the no form of this command.
ip flow-cache timeout {active minutes | inactive seconds}
no ip flow-cache timeout {active minutes | inactive seconds}
Syntax Description
active minutes
Timeout period for the active flows; valid values are from 1 to 60.
inactive seconds
Timeout period for the inactive flows; valid values are from 10 to 600.
Defaults
The default settings are as follows:
•
•
Command Modes
Global configuration
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
To use these commands, you must install the Supervisor Engine IV and the NetFlow Service Card.
You can increase or decrease the timeout period for the active flows. The switch will export active flow cache entries to a workstation when the active flows reach this timeout value. To obtain information on your flow timeout, use the show ip cache flow command.
Examples
This example sets the timeout period for the active flows to be exported after 30 seconds and sets the inactive flows to be exported after 30 seconds:
Switch(config)# ip flow-cache timeout active 45Switch(config)# ip flow-cache timeout inactive 30Switch(config)# exitSwitch#Related Commands
ip route-cache flow
show ip igmp interface
show ip flow export
show ip cache flowip igmp filter
To control whether all hosts on a Layer 2 interface can join one or more IP multicast groups by applying an IGMP profile to the interface, use the ip igmp filter command. To remove a profile from the interface, use the no form of this command
ip igmp filter profile number
no ip igmp filter
Syntax Description
Defaults
Profiles are not applied.
Command Modes
Interface configuration
Command History
12.1(11b)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
You can apply IGMP filters only to Layer 2 physical interfaces; you cannot apply IGMP filters to routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
An IGMP profile can be applied to one or more switch port interfaces, but one port can have only one profile applied to it.
Examples
This example shows how to apply IGMP profile 22 to an interface.
Switch(config)# interface gigabitethernet1/1Switch(config-if)# ip igmp filter 22Switch(config-if)#Related Commands
ip igmp profile
show ip igmp profileip igmp max-groups
To set the maximum number of IGMP groups that a Layer 2 interface can join, use the ip igmp max-groups command. To set the maximum back to the default, use the no form of this command.
ip igmp max-groups number
no ip igmp max-groups
Syntax Description
number
Maximum number of IGMP groups that an interface can join; valid values are from 0 to 4294967294.
Defaults
No maximum limit.
Command Modes
Interface configuration
Command History
12.1(11b)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
You can use ip igmp max-groups command only on Layer 2 physical interfaces; you cannot set IGMP maximum groups for routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
Examples
This example shows how to limit the number of IGMP groups that an interface can join to 25.
Switch(config)# interface gigabitethernet1/1Switch(config-if)# ip igmp max-groups 25Switch(config-if)ip igmp profile
To create an IGMP profile, use the ip igmp profile command. To delete the IGMP profile, use the no form of this command.
ip igmp profile profile number
no ip igmp profile profile number
Syntax Description
Defaults
No profile created.
Command Modes
Global configuration
IGMP profile configuration
Command History
12.1(11b)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
When entering a range, enter the low IP multicast address, a space, and the high IP multicast address.
You can apply an IGMP profile to one or more Layer 2 interfaces, but each interface can have only one profile applied to it.
Examples
This example shows how to configure IGMP profile 40 that permits the specified range of IP multicast addresses.
Switch # config terminalSwitch(config)# ip igmp profile 40Switch(config-igmp-profile)# permitSwitch(config-igmp-profile)# range 233.1.1.1 233.255.255.255Switch(config-igmp-profile)#Related Commands
ip igmp filter
show ip igmp profileip igmp query-interval
To configure the frequency that the switch sends IGMP host-query messages, use the ip igmp query-interval command. To return to the default frequency, use the no form of this command.
ip igmp query-interval seconds
no ip igmp query-interval
Syntax Description
seconds
Frequency, in seconds, at which IGMP host query messages are transmitted; valid values depend on the IGMP snooping mode. See "Usage Guidelines" for more information.
Defaults
Query-interval is set to 60 seconds.
Command Modes
Interface configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
If you use the default IGMP snooping configuration, the valid query interval values are from 1 to 65535 seconds. If you have changed the default configuration to support CGMP as the IGMP snooping learning method, the valid query interval values are from 1 to 300 seconds.
The designated switch for a LAN is the only switch that sends IGMP host query messages. For IGMP version 1, the designated switch is elected according to the multicast routing protocol that runs on the LAN. For IGMP version 2, the designated querier is the lowest IP-addressed multicast switch on the subnet.
If no queries are heard for the timeout period (controlled by the ip igmp query-timeout command), the switch becomes the querier.
Note
Examples
This example shows how to change the frequency at which the designated switch sends IGMP host query messages:
Switch(config-if)# ip igmp query-interval 120Switch(config-if)#Related Commands
ip pim query-interval (refer to Cisco IOS documentation)
show ip igmp groups (refer to Cisco IOS documentation)
ip igmp query-timeout (refer to Cisco IOS documentation)ip igmp snooping
To enable IGMP snooping, use the ip igmp snooping command. To disable IGMP snooping, use the no form of this command.
ip igmp snooping [tcn {flood query count count | query solicit}]
no ip igmp snooping [tcn {flood query count count | query solicit}]
Syntax Description
Defaults
IGMP snooping is enabled.
Command Modes
Global configuration
Interface configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(11)EW
Support for flooding the spanning tree table was added.
Usage Guidelines
The tcn flood option applies only to Layer 2 switch ports and EtherChannels; it does not apply to routed ports, VLAN interfaces, or Layer 3 channels.
The ip igmp snooping command is disabled by default on multicast routers.
Note
Examples
This example shows how to enable IGMP snooping:
Switch(config)# ip igmp snoopingSwitch(config)#This example shows how to disable IGMP snooping:
Switch(config)# no ip igmp snoopingSwitch(config)#This example shows how to enable flooding the spanning-tree table to the network after 9 topology changes have occurred:
Switch(config)# ip igmp snooping tcn flood query count 9Switch(config)#This example shows how to disable flooding the spanning-tree table to the network:
Switch(config)# no ip igmp snooping tcn floodSwitch(config)#This example shows how to enable an IGMP general query:
Switch(config)# ip igmp snooping tcn query solicitSwitch(config)#This example shows how to disable an IGMP general query:
Switch(config)# no ip igmp snooping tcn query solicitSwitch(config)#Related Commands
ip igmp snooping vlan immediate-leave
ip igmp snooping vlan mrouter
ip igmp snooping vlan staticip igmp snooping report-suppression
To enable report suppression, use the ip igmp snooping report-suppression command. To disable report suppression and forward reports to multicast devices, use the no form of this command.
ip igmp snooping report-suppression
no igmp snooping report-suppression
Syntax Description
This command has no arguments or keywords.
Defaults
IGMP snooping report-suppression is enabled.
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
If the ip igmp snooping report-suppression command is disabled, all IGMP reports are forwarded to the multicast devices.
If the command is enabled, report suppression is done by IGMP snooping.
Examples
This example shows how to enable report suppression:
Switch(config)# ip igmp snooping report-suppressionSwitch(config)#This example shows how to disable report suppression:
Switch(config)# no ip igmp snooping report-suppressionSwitch(config)#This example shows how to display the system status for report suppression:
Switch# sh ip igmp snoopvlan 1----------IGMP snooping is globally enabledIGMP snooping TCN solicit query is globally disabledIGMP snooping global TCN flood query count is 2IGMP snooping is enabled on this VlanIGMP snooping immediate-leave is disabled on this VlanIGMP snooping mrouter learn mode is pim-dvmrp on this VlanIGMP snooping is running in IGMP_ONLY mode on this VlanIGMP snooping report suppression is enabled on this VlanSwitch#Related Commands
ip igmp snooping vlan immediate-leave
ip igmp snooping vlan mrouter
ip igmp snooping vlan staticip igmp snooping vlan
To enable IGMP snooping for a VLAN, use the ip igmp snooping vlan command. To disable IGMP snooping, use the no form of this command.
ip igmp snooping vlan vlan-id
no ip igmp snooping vlan vlan-id
Syntax Description
Defaults
IGMP snooping is disabled.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
Before you can enable IGMP snooping on the Catalyst 4006 switches, you must configure the VLAN interface for multicast routing.
This command is entered in VLAN interface configuration mode only.
The ip igmp snooping command is disabled by default on multicast routers.
Examples
This example shows how to enable IGMP snooping on a VLAN:
Switch(config)# ip igmp snooping vlan 200Switch(config)#This example shows how to disable IGMP snooping on a VLAN:
Switch(config)# no ip igmp snooping vlan 200Switch(config)#Related Commands
ip igmp snooping vlan immediate-leave
ip igmp snooping vlan mrouter
ip igmp snooping vlan staticip igmp snooping vlan immediate-leave
To enable IGMP immediate-leave processing, use the ip igmp snooping vlan immediate-leave command. To disable immediate-leave processing, use the no form of this command.
ip igmp snooping vlan vlan_num immediate-leave
no ip igmp snooping vlan vlan_num immediate-leave
Syntax Description
vlan_num
Number of the VLAN; valid values are from 1 to 4094.
immediate-leave
Enables immediate leave processing.
Defaults
Immediate leave processing is disabled.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
You enter this command in global configuration mode only.
Use the immediate-leave feature only when there is a single receiver for the MAC group for a specific VLAN.
The immediate-leave feature is supported only with IGMP version 2 hosts.
Examples
This example shows how to enable IGMP immediate-leave processing on VLAN 4:
Switch(config)# ip igmp snooping vlan 4 immediate-leaveSwitch(config)#This example shows how to disable IGMP immediate-leave processing on VLAN 4:
Switch(config)# no ip igmp snooping vlan 4 immediate-leaveSwitch(config)#Related Commands
ip igmp snooping
ip igmp snooping vlan mrouter
ip igmp snooping vlan static
show ip igmp interface (refer to Cisco IOS documentation)
show mac-address-table multicastip igmp snooping vlan mrouter
To statically configure an Layer 2 interface as a multicast router interface for a VLAN, use the ip igmp snooping vlan mrouter command. To remove the configuration, use the no form of this command.
ip igmp snooping vlan vlan-id mrouter {interface {{FastEthernet slot/port} |
{GigabitEthernet slot/port} | {port-channel number}} |
{learn {cgmp | pim-dvmrp}}no ip igmp snooping vlan vlan-id mrouter {interface {FastEthernet slot/port} |
{GigabitEthernet slot/port} | {port-channel number}} |
{learn {cgmp | pim-dvmrp}}Syntax Description
Defaults
Multicast switch snooping PIM-DVMRP packets are specified.
Command Modes
Interface configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
You enter this command in VLAN interface configuration mode only.
The interface to the switch must be in the VLAN where you are entering the command. It must be both administratively up and line protocol up.
The CGMP learning method can decrease control traffic.
The learning method you configure is saved in NVRAM.
Static connections to multicast interfaces are supported only on switch interfaces.
Examples
This example shows how to specify the next-hop interface to multicast switch:
Switch(config-if)# ip igmp snooping 400 mrouter interface fastethernet 5/6Switch(config-if)#This example shows how to specify the multicast switch learning method:
Switch(config-if)# ip igmp snooping 400 mrouter learn cgmpSwitch(config-if)#Related Commands
ip igmp snooping
ip igmp snooping vlan immediate-leave
ip igmp snooping vlan static
show ip igmp snooping mrouterip igmp snooping vlan static
To configure an Layer 2 interface as a member of a group, use the ip igmp snooping vlan static command. To remove the configuration, use the no form of this command.
ip igmp snooping vlan vlan_num static mac-address {interface {FastEthernet slot/port} | {GigabitEthernet slot/port} | {port-channel number}}
no ip igmp snooping vlan vlan_num static {{interface {FastEthernet slot/port} |
{GigabitEthernet slot/port} | {port-channel number}}Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to configure a host statically on an interface:
Switch(config)# ip igmp snooping vlan 4 static 0100.5e02.0203 interface fas 5/11Configuring port FastEthernet5/11 on group 0100.5e02.0203 vlan 4Switch(config)#Related Commands
ip igmp snooping
ip igmp snooping vlan immediate-leave
ip igmp snooping vlan mrouter
show mac-address-table multicastip local-proxy-arp
To enable the local proxy ARP feature, use the ip local-proxy-arp command. To disable the local proxy ARP feature, use the no form of this command.
ip local-proxy-arp
no ip local-proxy-arp
Syntax Description
This command has no arguments or keywords.
Defaults
Local proxy ARP is disabled.
Command Modes
Interface configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
Use this feature only on subnets where hosts are intentionally prevented from communicating directly to the switch on which they are connected.
ICMP redirect is disabled on interfaces where the local proxy ARP feature is enabled.
Examples
This example shows how to enable the local proxy ARP feature:
Switch(config-if)# ip local-proxy-arpSwitch(config-if)#ip mfib fastdrop
To enable MFIB fast drop, use the ip mfib fastdrop command. To disable MFIB fast drop, use the no form of this command.
ip mfib fastdrop
no ip mfib fastdrop
Syntax Description
This command has no arguments or keywords.
Defaults
MFIB fast drop is enabled.
Command Modes
EXEC
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Examples
This example shows how to enable MFIB fast drops:
Switch>ip mfib fastdropSwitch>Related Commands
clear ip mfib fastdrop
show ip mfib fastdropip route-cache flow
To enable NetFlow statistics for IP routing, use the ip route-cache flow command. To disable NetFlow statistics, use the no form of this command.
ip route-cache flow
no ip route-cache flow
Syntax Description
This command has no arguments or keywords.
Defaults
NetFlow statistics is disabled.
Command Modes
Global configuration
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
To use these commands, you need to install the Supervisor Engine IV and the NetFlow Service Card.
The NetFlow statistics feature captures a set of traffic statistics. These traffic statistics include user, protocol, port, and type of service information that can be used for network analysis and planning, accounting, and billing.
NetFlow switching is supported on IP and IP-encapsulated traffic over all interface types.
For additional information on NetFlow switching, refer to the Catalyst 4000 Family Cisco IOS Software Configuration Guide.
Note
Examples
This example shows how to enable NetFlow switching on the switch:
Switch# configure terminalSwitch(config)# ip route-cache flowSwitch(config)# exitSwitch#
Note
Related Commands
ip sticky-arp
To enable sticky ARP, use the ip sticky-arp command. Use the no form of this command to disable sticky ARP.
ip sticky-arp
no ip sticky-arp
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
This command is supported on PVLANs only.
ARP entries that are learned on Layer3 PVLAN interfaces are sticky ARP entries. (You should display and verify ARP entries on the PVLAN interface using the show arp command).
For security reasons, sticky ARP entries on the PVLAN interface do not age out. Connecting new equipment with the same IP address generates a message and the ARP entry is not created.
Because the ARP entries on the PVLAN interface do not age out, you must manually remove ARP entries on the PVLAN interface if a MAC address changes.
Unlike static entries, sticky-ARP entries are not stored and restored when you enter the reboot and restart commands.
Examples
This example shows how to enable sticky ARP:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config) ip sticky-arpSwitch(config)# endSwitch#This example shows how to disable sticky ARP:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config) no ip sticky-arpSwitch(config)# endSwitch#Related Commands
arp (refer to Cisco IOS documentation)
show arp (refer to Cisco IOS documentation)lacp port-priority
To set the LACP priority for physical interfaces, use the lacp port-priority command.
lacp system-priority priority
Syntax Description
Defaults
Priority is set to 32768.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
You must assign each port in the switch a port priority that can be specified automatically or by entering the lacp port-priority command. The port priority is used with the port number to form the port identifier. The port priority is used to decide which ports should be put in standby mode when there is a hardware limitation that prevents all compatible ports from aggregating.
Although this command is a global configuration command, priority is supported only on port channels with LACP-enabled physical interfaces.
This command is supported on LACP-enabled interfaces.
When setting the priority, the higher the number, the lower the priority.
Examples
This example shows how to set the priority for the interface:
Switch(config-if)# lacp port-priority 23748Switch(config-if)#Related Commands
channel-group
channel-protocol
lacp system-priority
show lacplacp system-priority
To set the priority of the system for LACP, use the lacp system-priority command.
lacp system-priority priority
Syntax Description
Defaults
Priority is set to 32768.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command is not supported on systems configured with a Supervisor Engine 1.
You must assign each switch running LACP a system priority that can be specified automatically or by entering the lacp system-priority command. The system priority is used with the switch MAC address to form the system ID and is also used during negotiation with other systems.
Although this command is a global configuration command, priority is supported on port channels with LACP-enabled physical interfaces.
When setting the priority, the higher the number, the lower the priority.
You can also enter the lacp system-priority command in interface configuration mode. After you enter the command, the system defaults to global configuration mode.
Examples
This example shows how to set the system priority:
Switch(config)# lacp system-priority 23748Switch(config)#Related Commands
channel-group
channel-protocol
lacp port-priority
show lacpmac access-list extended
To define extended MAC access lists, use the mac access-list extended command. To remove MAC access lists, use the no form of this command.
mac access-list extended name
no mac access-list extended name
Syntax Description
Defaults
MAC access lists are not defined.
Command Modes
Global configuration
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
When you enter the ACL name, follow these naming conventions:
•
•
•
•
•
When you enter the mac access-list extended name command, you use the [no] {permit | deny} {{src-mac mask | any} [dest-mac mask]} [protocol-family {appletalk | arp-non-ipv4 | decnet | ipx | ipv6 | rarp-ipv4 | rarp-non-ipv4 | vines | xns}] subset to create or delete entries in a MAC-Layer access list.
Table 2-7 describes the syntax of the mac access-list extended subcommands.
Table 2-8 describes mapping an Ethernet packet to a protocol family.
When you enter the src-mac mask or dest-mac mask value, follow these guidelines:
•
•
•
•
•
•
•
Examples
This example shows how to create a MAC-Layer access list named mac_layer that denies traffic from 0000.4700.0001, which is going to 0000.4700.0009, and permits all other traffic:
Switch(config)# mac access-list extended mac_layerSwitch(config-ext-macl)# deny 0000.4700.0001 0.0.0 0000.4700.0009 0.0.0 protocol-family appletalkSwitch(config-ext-macl)# permit any anyRelated Commands
mac-address-table aging-time
To configure aging time for entries in the Layer 2 table, use the mac-address-table aging-time command. To reset the seconds value to the default setting, use the no form of this command.
mac-address-table aging-time seconds [vlan vlan_id]
no mac-address-table aging-time seconds [vlan vlan_id]
Syntax Description
seconds
Aging time in seconds; valid values are 0 and from 10 to 1000000 seconds.
vlan vlan_id
(Optional) Specifies the VLAN to apply the changed aging time; valid values are from 1 to 4094.
Defaults
Aging time is set to 300 seconds.
Command Modes
Global configuration
Command History
12.1(8a)EW
Support for this command was introduced on the Catalyst 4000 family switch.
12.1(12c)EW
Support for extended addressing was added.
Usage Guidelines
If you do not enter a VLAN, the change is applied to all routed-port VLANs.
Enter 0 seconds to disable aging.
Examples
This example shows how to configure the aging time to 400 seconds:
Switch(config)# mac-address-table aging-time 400Switch(config)#This example shows how to disable aging:
Switch(config)# mac-address-table aging-time 0Switch(config)Related Commands
show mac-address-table aging-time
mac-address-table static
To configure static MAC addresses for a VLAN interface or drop unicast traffic for a MAC address for a VLAN interface, use the mac-address-table static command. To remove static MAC address configurations, use the no form of this command.
mac-address-table static mac-addr {vlan vlan-id} {interface type | drop}
no mac-address-table static mac-addr {vlan vlan-id}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.1(13)EW
Support for this command was introduced on the Catalyst 4000 family switch.
Usage Guidelines
When a static MAC address is installed, it is associated with a port.
The output interface specified must be a Layer 2 interface and not an SVI.
You can enter up to 15 interfaces per command entered, but you can enter more interfaces by repeating the command.
If you do not enter a protocol type, an entry is automatically created for each of the four protocol types.
Entering the no form of this command does not remove system MAC addresses.
When removing a MAC address, entering interface int is optional. For unicast entries, the entry is removed automatically. For multicast entries, if you do not specify an interface, the entire entry is removed. You can specify the selected ports to be removed by specifying the interface.
Examples
This example shows how to add static entries to the MAC address table:
Switch(config)# mac-address-table static 0050.3e8d.6400 vlan 100 interface fastethernet5/7Switch(config)#This example shows how to configure a static MAC address with IGMP snooping disabled for a specified address:
Switch(config)# mac-address-table static 0050.3e8d.6400 vlan 100 interface fastethernet5/7 disable-snoopingSwitch(config)#Related Commands
main-cpu
To enter the main CPU submode and manually synchronize the configurations on the two supervisor engines, use the main-cpu command.
main-cpu
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Redundancy
Command History
12.1(12c)EW
Support for this command was introduced on the Catalyst 4000 family switch. (Catalyst 4507R only)
Usage Guidelines
The main CPU submode is used to manually synchronize the configurations on the two supervisor engines.
From the main CPU submode, use the auto-sync command to enable automatic synchronization of the configuration files in NVRAM.
Note
Related Commands
auto-sync
match
To specify a match clause by selecting one or more ACLs for a VLAN access-map sequence, use the match subcommand. To remove the match clause, use the no form of this command.
match {ip address {acl-number | acl-name}} | {mac address acl-name}
no match {ip address {acl-number | acl-name}} | {mac address acl-name}
