Table Of Contents
clear controllers ethernet-controller
clear controllers lre link monitor
clear spanning-tree detected-protocols
deny (access-list configuration)
deny (MAC access-list configuration)
ip dhcp snooping information option
ip igmp snooping report-suppression
ip igmp snooping source-only-learning
ip igmp snooping source-only-learning age-timer
ip igmp snooping vlan immediate-leave
mac address-table notification
permit (access-list configuration)
permit (MAC access-list configuration)
profile (interface configuration)
profile (sequence configuration)
Cisco IOS Commands
aaa authentication dot1x
Use the aaa authentication dot1x global configuration command to specify one or more authentication, authorization, and accounting (AAA) methods for use on interfaces running IEEE 802.1X. Use the no form of this command to disable authentication.
aaa authentication dot1x {default} method1 [method2...]
no aaa authentication dot1x {default}
Syntax Description
Defaults
No authentication is performed.
Command Modes
Global configuration
Command History
Usage Guidelines
The method argument identifies the list of methods that the authentication algorithm tries in the given sequence to validate the password provided by the client. The only method that is truly 802.1X-compliant is the group radius method, in which the client data is validated against a RADIUS authentication server. The remaining methods enable AAA to authenticate the client by using locally configured data. For example, the local and local-case methods use the username and password that are saved in the Cisco IOS configuration file. The enable and line methods use the enable and line passwords for authentication.
If you specify group radius, you must configure the RADIUS server by entering the radius-server host global configuration command.
If you are not using a RADIUS server, you can use the local or local-case methods, which access the local username database to perform authentication. By specifying the enable or line methods, you can supply the clients with a password to provide access to the switch.
Use the show running-config privileged EXEC command to display the configured lists of authentication methods.
Examples
This example shows how to enable AAA and how to create an authentication list for 802.1X. This authentication first tries to contact a RADIUS server. If this action returns an error, the user is allowed access with no authentication.
Switch(config)# aaa new modelSwitch(config)# aaa authentication dot1x default group radius noneYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
access-list (IP extended)
Use the extended version of the access-list global configuration command to configure an extended IP access control list (ACL). Use the no form of this command to remove an extended IP ACL.
access-list access-list-number {deny | permit | remark} protocol {source source-wildcard | host source | any} [operator port] {destination destination-wildcard | host destination | any} [operator port] [dscp dscp-value] [time-range time-range-name]
no access-list access-list-number
This command is available on physical interfaces only if your switch is running the enhanced software image (EI).
Syntax Description
Defaults
The default extended ACL is always terminated by an implicit deny statement for all packets.
Command Modes
Global configuration
Command History
Usage Guidelines
Plan your access conditions carefully. The ACL is always terminated by an implicit deny statement for all packets.
You can use ACLs to control virtual terminal line access by controlling the transmission of packets on an interface.
Extended ACLs support only the TCP and UDP protocols.
Use the show ip access-lists command to display the contents of IP ACLs.
Use the show access-lists command to display the contents of all ACLs.
Note
For more information about configuring IP ACLs, refer to the "Configuring Network Security with ACLs" chapter in the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide for this release.
Examples
This example shows how to configure an extended IP ACL that allows only TCP traffic to the destination IP address 128.88.1.2 with a TCP port number of 25 and how to apply it to an interface:
Switch(config)# access-list 102 permit tcp any host 128.88.1.2 eq 25Switch(config)# interface fastethernet0/8Switch(config-if)# ip access-group 102 inThis is an example of an extended ACL that allows TCP traffic only from two specified networks. The wildcard bits apply to the host portions of the network addresses. Any host with a source address that does not match the ACL statements is denied.
access-list 104 permit tcp 192.5.0.0 0.0.255.255 anyaccess-list 104 permit tcp 128.88.0.0 0.0.255.255 any
Note
You can verify your settings by entering the show ip access-lists or show access-lists privileged EXEC command.
Related Commands
Configures a standard IP ACL.
Controls access to an interface.
Displays ACLs configured on the switch.
Displays IP ACLs configured on the switch.
access-list (IP standard)
Use the standard version of the access-list global configuration command to configure a standard IP access control list (ACL). Use the no form of this command to remove a standard IP ACL.
access-list access-list-number {deny | permit | remark} {source source-wildcard | host source | any}
no access-list access-list-number
This command is available on physical interfaces only if your switch is running the enhanced software image (EI).
Syntax Description
Defaults
The default standard ACL is always terminated by an implicit deny statement for all packets.
Command Modes
Global configuration
Command History
Usage Guidelines
Plan your access conditions carefully. The ACL is always terminated by an implicit deny statement for all packets.
You can use ACLs to control virtual terminal line access by controlling the transmission of packets on an interface.
Use the show ip access-lists command to display the contents of IP ACLs.
Use the show access-lists command to display the contents of all ACLs.
Note
Examples
This example shows how to configure a standard IP ACL that allows only traffic from the host network 128.88.1.10 and how to apply it to an interface:
Switch(config)# access-list 12 permit host 128.88.1.10Switch(config)# interface gigabitethernet0/1Switch(config-if)# ip access-group 12 inThis is an example of an standard ACL that allows traffic only from three specified networks. The wildcard bits apply to the host portions of the network addresses. Any host with a source address that does not match the ACL statements is denied.
access-list 14 permit 192.5.34.0 0.0.0.255access-list 14 permit 128.88.0.0 0.0.0.255access-list 14 permit 36.1.1.0 0.0.0.255
Note
You can verify your settings by entering the show ip access-lists or show access-lists privileged EXEC command.
Related Commands
Configures an extended IP ACL.
Controls access to an interface.
Displays ACLs configured on the switch.
Displays IP ACLs configured on the switch.
archive download-sw
Use the archive download-sw privileged EXEC command to download a new image to a Catalyst 2950 Long-Reach Ethernet (LRE) switch and to overwrite or to keep the existing image.
archive download-sw {/force-reload | /imageonly | /leave-old-sw | /no-set-boot | /overwrite | /reload | /safe} source-url
This command is available only on the Catalyst 2950 LRE switches.
Syntax Description
Defaults
Both the software image and CMS files are downloaded.
The new image is downloaded to the flash: file system.
The BOOT environment variable is changed to point to the new software image on the flash: file system.
Image names are case sensitive; the image file is provided in .tar format.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the /overwrite option to overwrite the image on the Flash device with the downloaded one.
If the Flash device has sufficient space to hold two images and you want to overwrite one of these images with the same version, you must specify the /overwrite option.
If you specify the command without the /overwrite option, the download algorithm verifies that the new image is not the same as the one on the switch Flash device. If the images are the same, the download does not occur. If the images are different, the old image is deleted, and the new one is downloaded.
The /imageonly option removes the CMS files for the existing image if the existing image is being removed or replaced. Only the software image (without the CMS files) is downloaded.
Using the /safe or /leave-old-sw option can cause the new image download to fail if there is insufficient Flash space.
If you used the /leave-old-sw option and did not overwrite the old image when you downloaded the new one, you can remove the old image by using the delete privileged EXEC command. For more information, see the delete command.
If you leave the existing software in place before downloading the new image, an error results if the existing software prevents the new image from fitting onto Flash memory.
After downloading a new image, enter the reload privileged EXEC command to begin using the new image, or specify the /reload or /force-reload option in the archive download-sw command.
Examples
This example shows how to download a new image from a TFTP server at 172.20.129.10 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://172.20.129.10/test-image.tarThis example shows how to download only the software image from a TFTP server at 172.20.129.10 to the switch:
Switch# archive download-sw /imageonly tftp://172.20.129.10/test-image.tarThis example shows how to keep the old software version after a successful download:
Switch# archive download-sw /leave-old-sw tftp://172.20.129.10/test-image.tarRelated Commands
archive tar
Use the archive tar privileged EXEC command to create a .tar file, to list files in a .tar file, or to extract the files from a .tar file.
archive tar {/create destination-url flash:/file-url} | {/table source-url} | {/xtract source-url flash:/file-url [dir/file...]}
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Filenames and directory names are case sensitive.
Image names are case sensitive.
Examples
This example shows how to create a .tar file. The command writes the contents of the new-configs directory on the local Flash device to a file named saved.tar on the TFTP server at 172.20.136.9:
Switch# archive tar /create tftp:172.20.136.9/saved.tar flash:/new-configsThis example shows how to display the contents of the saved.tar file that is in Flash memory. The contents of the .tar file appear on the screen:
Switch # archive tar /table tftp://172.20.136.9/saved.tarLoading saved.tar from 172.20.136.9 (via Vlan1):!info (247 bytes)c2950lre-i6l2q4-mz.121/ (directory)c2950lre-i6l2q4-mz.121/html/ (directory)c2950lre-i6l2q4-mz.121/html/homepage.htm (3990 bytes)!<output truncated>c2950lre-i6l2q4-mz.121/lre-bin/CISCO585-LRE_MC8051boot_01.03.00.bin (688bytes)c2950lre-i6l2q4-mz.121/lre-bin/CISCO585-LRE_vdslsngl_51.00.00.bin (8896bytes)!!c2950lre-i6l2q4-mz.121/pef22824.bin (32768 bytes)!!!!!!!c2950lre-i6l2q4-mz.121/info (247 bytes)info.ver (247 bytes)[OK - 4279808/8559616 bytes]Related Commands
Downloads a new image to the switch.
Uploads an existing image on the switch to a server.
archive upload-sw
Use the archive upload-sw privileged EXEC command to upload an existing Long-Reach Ethernet (LRE) switch image to a server.
archive upload-sw [/version version_string] destination-url
This command is supported only on Catalyst 2950 LRE switches.
Syntax Description
Defaults
The switch uploads the currently running image from the flash: file system.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The upload feature should be used only if the files associated with the Cluster Management Suite (CMS) have been installed with the existing image.
The files are uploaded in this sequence: info, the software image, the CMS files, LRE binary files, and info.ver. After these files are uploaded, the software creates the .tar file.
Image names are case sensitive.
Examples
This example shows how to upload the currently running image to a TFTP server at 172.20.140.2:
Switch# archive upload-sw tftp://172.20.140.2/test-image.tarRelated Commands
Downloads a new image to a Catalyst 2950 LRE switch.
Creates a .tar file, lists the files in a .tar file, or extracts the files from a .tar file.
auto qos voip
Use the auto qos voip interface configuration command to configure automatic quality of service (auto-QoS) for voice over IP (VoIP) within a QoS domain. Use the no form of this command to change the auto-QoS configuration settings to the standard-QoS defaults.
auto qos voip {cisco-phone | trust}
no auto qos voip
This command is available only if your switch is running the enhanced software image (EI).
Syntax Description
Defaults
Auto-QoS is disabled on all interfaces.
When auto-QoS is enabled, it uses the ingress packet label to categorize traffic and to configure the egress queues as summarized in Table 2-1.
Table 2-1 Traffic Types, Ingress Packet Labels, Assigned Packet Labels, and Egress Queues
Ingress DSCP3
46
26
-
-
-
Ingress CoS
5
3
6
7
-
Assigned DSCP
46
26
48
56
0
Assigned CoS
5
3
6
7
0
CoS-to-Queue Map
5
3, 6, 7
0, 1, 2, 4
Egress Queue
Expedite queue
80% WRR4
20% WRR
1 STP = Spanning Tree Protocol
2 BPDU = bridge protocol data unit
3 DSCP = Differentiated Services Code Point
4 WRR = weighted round robin
Table 2-2 lists the auto-QoS configuration for the egress queues.
Table 2-2 Auto-QoS Configuration for the Egress Queues
Expedite
4
5
-
80% WRR
3
3, 6, 7
80%
20% WRR
1
0, 1, 2, 4
20%
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to configure the QoS that is appropriate for VoIP traffic within the QoS domain. The QoS domain includes the switch, the interior of the network, and the edge devices that can classify incoming traffic for QoS.
Use the cisco-phone keyword on ports connected to Cisco IP phones at the edge of the network. The switch detects the phone through the Cisco Discovery Protocol (CDP) and trusts the QoS labels in packets received from the phone.
Use the trust keyword on ports connected to the interior of the network. Because it is assumed that traffic has already been classified by other edge devices, the QoS labels in these packets from the interior of the network are trusted.
When you enable the auto-QoS feature on the first interface, these automatic actions occur:
•
•
•
You can enable auto-QoS on static, dynamic-access, voice VLAN access, and trunk ports.
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug autoqos privileged EXEC command to enable auto-QoS debugging.
To disable auto-QoS on an interface, use the no auto qos voip interface configuration command. When you enter this command, the switch changes the auto-QoS settings to the standard-QoS default settings for that interface.
To disable auto-QoS on the switch and return to the default port trust state (untrusted), follow these steps:
1.
2.
•
•
•
Examples
This example shows how to enable auto-QoS and to trust the QoS labels received in incoming packets when the switch or router connected to Gigabit Ethernet interface 0/1 is a trusted device:
Switch(config)# interface gigabitethernet0/1Switch(config-if)# auto qos voip trustThis example shows how to enable auto-QoS and to trust the QoS labels received in incoming packets when the device connected to Fast Ethernet interface 0/1 is detected as a Cisco IP phone:
Switch(config)# interface fastethernet0/1Switch(config-if)# auto qos voip cisco-phoneThis example shows how to display the QoS configuration that is automatically generated when auto-QoS is enabled:
Switch# debug autoqosAutoQoS debugging is onSwitch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface fastethernet0/10Switch(config-if)# auto qos voip cisco-phone00:02:54:wrr-queue bandwidth 20 1 80 000:02:55:no wrr-queue cos-map00:02:55:wrr-queue cos-map 1 0 1 2 400:02:56:wrr-queue cos-map 3 3 6 700:02:58:wrr-queue cos-map 4 500:02:59:mls qos map cos-dscp 0 8 16 26 32 46 48 5600:03:00:interface FastEthernet0/1000:03:00: mls qos trust device cisco-phone00:03:00: mls qos trust cosSwitch(config-if)# interface fastethernet0/12Switch(config-if)# auto qos voip trust00:03:15:interface FastEthernet0/1200:03:15: mls qos trust cosSwitch(config-if)#You can verify your settings by entering the show auto qos interface interface-id privileged EXEC command.
Related Commands
boot boothlpr
Use the boot boothlpr global configuration command to load a special software image, which when loaded into memory, can load a second software image into memory and start it. This variable is used only for internal development and testing. Use the no form of this command to return to the default setting.
boot boothlpr filesystem:/file-url
no boot boothlpr
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
filesystem:
Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url
The path (directory) and name of a bootable helper image.
Defaults
No helper image is loaded.
Command Modes
Global configuration
Command History
Usage Guidelines
Filenames and directory names are case sensitive.
This command changes the setting of the BOOTHLPR environment variable. For more information, see "Boot Loader Commands."
Related Commands
boot buffersize
Use the boot buffersize global configuration command to specify the size of the file system-simulated nonvolatile RAM (NVRAM) in Flash memory. The buffer holds a copy of the configuration file in memory. Use the no form of this command to return to the default setting.
boot buffersize size
no boot buffersize
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
Defaults
The default is 32 KB.
Command Modes
Global configuration
Command History
Usage Guidelines
The configuration file cannot be larger than the buffer size allocation.
You must reload the switch by using the reload privileged EXEC command for this command to take effect.
This command changes the setting of the CONFIG_BUFSIZE environment variable. For more information, see "Boot Loader Commands."
Related Commands
boot config-file
Use the boot config-file global configuration command to specify the filename that the software uses to read and write a nonvolatile copy of the system configuration. Use the no form of this command to return to the default setting.
boot config-file flash:/file-url
no boot config-file
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
Defaults
The default configuration file is flash:config.text.
Command Modes
Global configuration
Command History
Usage Guidelines
Filenames and directory names are case sensitive.
This command changes the setting of the CONFIG_FILE environment variable. For more information, see "Boot Loader Commands."
Related Commands
boot enable-break
Use the boot enable-break global configuration command to enable interrupting the automatic boot process on a Catalyst 2950 Long-Reach Ethernet (LRE) switch. Use the no form of this command to return to the default setting.
boot enable-break
no boot enable-break
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
This command has no arguments or keywords.
Defaults
The automatic start up process cannot be interrupted by pressing the Break key on the console.
Command Modes
Global configuration
Command History
Usage Guidelines
When you enter this command, you can interrupt the automatic boot process by pressing the Break key on the console after the Flash file system is initialized.
Note
This command changes the setting of the ENABLE_BREAK environment variable. For more information, see "Boot Loader Commands."
Related Commands
boot helper
Use the boot helper global configuration command to dynamically load files during boot loader initialization to extend or to patch the functionality of the boot loader. Use the no form of this command to return to the default.
boot helper filesystem:/file-url ...
no boot helper
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
Defaults
No helper files are loaded.
Command Modes
Global configuration
Command History
Usage Guidelines
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER environment variable. For more information, see "Boot Loader Commands."
Related Commands
boot helper-config-file
Use the boot helper-config-file global configuration command to specify the name of the configuration file to be used by the Cisco IOS helper image. If this is not set, the file specified by the CONFIG_FILE environment variable is used by all versions of the software that are loaded. This variable is used only for internal development and testing. Use the no form of this command to return to the default setting.
boot helper-config-file filesystem:/file-url
no boot helper-config file
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
filesystem:
Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url
The path (directory) and helper configuration file to load.
Defaults
No helper configuration file is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER_CONFIG_FILE environment variable. For more information, see "Boot Loader Commands."
Related Commands
boot manual
Use the boot manual global configuration command to enable starting the Catalyst 2950 Long-Reach Ethernet (LRE) switch manually during the next power on cycle. Use the no form of this command to return to the default setting.
boot manual
no boot manual
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
This command has no arguments or keywords.
Defaults
During the next power on cycle, you cannot manually start an LRE switch.
Command Modes
Global configuration
Command History
Usage Guidelines
The next time you restart the system, the switch is in boot loader mode, which is shown by the switch: prompt. To power on the system, use the boot boot loader command, and specify the name of the bootable image.
This command changes the setting of the MANUAL_BOOT environment variable. For more information, see "Boot Loader Commands."
Related Commands
boot private-config-file
Use the boot private-config-file global configuration command to specify the filename that the software uses to read and write a nonvolatile copy of the private configuration. Use the no form of this command to return to the default setting.
boot private-config-file filename
no boot private-config-file
Syntax Description
Defaults
The default configuration file is private-config.text.
Command Modesb
Global configuration
Command History
Usage Guidelines
Only the software can read and write a copy of the private configuration file. You cannot read, write, delete, or display a copy of this file.
Filenames are case sensitive.
Examples
This example shows how to specify the name of the private configuration file as pconfig:
Switch(config)# boot private-config-file pconfigRelated Commands
boot system
Use the boot system global configuration command to specify the software image to load during the next power on cycle. Use the no form of this command to return to the default setting.
boot system filesystem:/file-url ...
no boot system
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
filesystem:
Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url
The path (directory) and name of a bootable image. Separate image names with a semicolon.
Defaults
The switch attempts to automatically power on the system by using information in the BOOT environment variable. If this variable is not set, the switch attempts to load and execute the first executable image it can by performing a recursive, depth-first search throughout the Flash file system. In a depth-first search of a directory, each encountered subdirectory is completely searched before the switch continues to search in the original directory.
Command Modes
Global configuration
Command History
Usage Guidelines
Filenames and directory names are case sensitive.
If you are using the archive download-sw privileged EXEC command to maintain system images, you do not ever need to use the boot system command. The boot system command is automatically manipulated to load the downloaded image.
This command changes the setting of the BOOT environment variable. For more information, see "Boot Loader Commands."
Related Commands
channel-group
Use the channel-group interface configuration command to assign an Ethernet interface to an EtherChannel group. Use the no form of this command to remove an Ethernet interface from an EtherChannel group.
channel-group channel-group-number mode {auto [non-silent] | desirable [non-silent] | on | active | passive}
no channel-group
Syntax Description
Defaults
No channel groups are assigned.
There is no default mode.
Command Modes
Interface configuration
Command History
12.1(6)EA2
This command was introduced. It replaced the port group command.
12.1(12c)EA1
The active and passive keywords were added.
Usage Guidelines
You must specify the mode when entering this command. If the mode is not entered, an Ethernet interface is not assigned to an EtherChannel group, and an error message appears.
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.
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 highly recommend that you do so.
You can create port channels by entering the interface port-channel global configuration command or when the channel group gets its first physical interface assignment. The port channels are not created at runtime or dynamically.
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).
With the on mode, a usable PAgP EtherChannel exists only when a port group in on mode is connected to another port group in on mode.
If you do not specify non-silent with the auto or desirable mode, silent is assumed. The silent mode is used when the switch is connected to a device that is not PAgP-capable and seldom, if ever, sends packets. A example of a silent partner is a file server or a packet analyzer that is not generating traffic. In this case, running PAgP on a physical port prevents that port from ever becoming operational; however, it allows PAgP to operate, to attach the interface to a channel group, and to use the interface for transmission. Both ends of the link cannot be set to silent.
Note
Caution
Examples
This example shows how to add an interface to the EtherChannel group specified as channel group 1:
Switch(config)# interface gigabitethernet0/1Switch(config-if)# channel-group 1 mode onThis example shows how to set an Etherchannel into PAgP mode:
Switch(config-if)# channel-group 1 mode autoCreating a port-channel interface Port-channel 1This example shows how to set an Etherchannel into LACP mode:
Switch(config-if)# channel-group 1 mode passiveCreating a port-channel interface Port-channel 1You can verify your settings by entering the show etherchannel or show running-config privileged EXEC command.
Related Commands
channel-protocol
Use the channel-protocol interface configuration command to configure an EtherChannel for the Port Aggregation Protocol (PAgP) or Link Aggregation Control Protocol (LACP). Use the no form of this command to disable PAgP or LACP on the EtherChannel.
channel-protocol {lacp | pagp}
no channel-protocol
Syntax Description
lacp
Configure an EtherChannel with the LACP protocol.
pagp
Configure an EtherChannel with the PAgP protocol.
Defaults
No protocol is assigned to the EtherChannel.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the channel-protocol command only to restrict a channel to LACP or PAgP.
You must use the channel-group interface command to configure the EtherChannel parameters. The channel-group command can also set the EtherChannel for a channel.
Note
Caution
Examples
This example shows how to set an EtherChannel into PAgP mode:
Switch(config-if)# channel-protocol pagpThis example shows how to set an EtherChannel into LACP mode:
Switch(config-if)# channel-protocol lacpYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
class
Use the class policy-map configuration command to define a traffic classification for the policy to act on using the class-map name or access group. Use the no form of this command to delete an existing class map.
class class-map-name [access-group name acl-index-or-name]
no class class-map-name
This command is available only if your switch is running the enhanced software image (EI).
Syntax Description
Defaults
No policy-map class maps are defined.
Command Modes
Policy-map configuration
Command History
Usage Guidelines
Before you use the class command, use the policy-map global configuration command to identify the policy map and to enter policy-map configuration mode. After you specify a policy map, you can configure a policy for new classes or modify a policy for any existing classes in that policy map. You attach the policy map to an interface by using the service-policy interface configuration command; however, you cannot attach one that uses an ACL classification to the egress direction.
The class name that you specify in the policy map ties the characteristics for that class to the class map and its match criteria as configured by using the class-map global configuration command.
The class command performs the same function as the class-map global configuration command. Use the class command when a new classification, which is not shared with any other ports, is needed. Use the class-map command when the map is shared among many ports.
Note
After entering the class command, you enter policy-map class configuration mode. These configuration commands are available:
•
•
•
•
•
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
Note
Examples
This example shows how to create a policy map named policy1. When attached to the ingress port, it matches all the incoming traffic defined in class1 and polices the traffic at an average rate of 1 Mbps and bursts at 131072 bytes. Traffic exceeding the profile is dropped.
Switch(config)# policy-map policy1Switch(config-pmap)# class class1Switch(config-pmap-c)# police 1000000 131072 exceed-action dropSwitch(config-pmap-c)# exitSwitch(config-pmap)#You can verify your settings by entering the show policy-map privileged EXEC command.
Related Commands
class-map
Use the class-map global configuration command to create a class map to be used for matching packets to the class whose name you specify and to enter class-map configuration mode. Use the no form of this command to delete an existing class map and to return to global configuration mode.
class-map class-map-name [match-all]
no class-map class-map-name [match-all]
This command is available only if your switch is running the enhanced software image (EI).
Syntax Description
class-map-name
Name of the class map.
match-all
(Optional) Perform a logical-AND of all matching statements under this class map. All criteria in the class map must be matched.
Defaults
No class maps are defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to specify the name of the class for which you want to create or modify class-map match criteria and to enter class-map configuration mode. In this mode, you can enter one match command to configure the match criteria for this class.
The class-map command and its subcommands are used to define packet classification and marking as part of a globally named service policy applied on a per-interface basis.
In quality of service (QoS) class-map configuration mode, these configuration commands are available:
•
•
•
Only one match criterion per class map is supported. For example, when defining a class map, only one match command can be entered.
Only one access control list (ACL) can be configured in a class map. The ACL can have multiple access control entries (ACEs).
Note
Note
Examples
This example shows how to configure the class map named class1. class1 has one match criteria, which is a numbered ACL.
Switch(config)# access-list 103 permit tcp any any eq 80Switch(config)# class-map class1Switch(config-cmap)# match access-group 103Switch(config-cmap)# exitYou can verify your settings by entering the show class-map privileged EXEC command.
Related Commands
clear controllers ethernet-controller
Use the clear controllers ethernet-controller privileged EXEC command to clear the Ethernet link transmit and receive statistics for a switch port and for a Long-Reach Ethernet (LRE) customer premises equipment (CPE) device.
clear controllers ethernet-controller interface-id [cpe [port port-id]]
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The CPE Ethernet link is the connection between the CPE Ethernet port and the remote Ethernet device (such as a PC) connected to it. It is not the link between the switch LRE port and the LRE CPE device.
It takes the switch several seconds to clear the CPE Ethernet ports. The CPE Ethernet ports on CPE devices take longer to clear than all the other port types.
If you enter the clear controllers ethernet-controller privileged EXEC command without specifying an interface-id, the switch clears the Ethernet link statistics for all ports on the switch. If you specify an an interface, the switch clears the Ethernet link statistics for the specified port.
On a Catalyst 2950 LRE switch, if you use the cpe keyword, the switch clears the Ethernet statistics of the LRE chipset and of all these CPE Ethernet ports:
•
•
If you enter the cpe port port-id keywords, the switch clears the Ethernet counters of the specified CPE Ethernet port.
Note
Examples
This example shows how to clear the Ethernet link statistics for LRE port 1:
Switch# clear controllers ethernet-controller longreachethernet0/1This example clears the Ethernet statistics for all the CPE Ethernet ports on a Cisco 585 LRE CPE:
Switch# clear controllers ethernet-controller longreachethernet0/1 cpeYou can verify that information was deleted by entering the show controllers ethernet-controller user EXEC command.
Related Commands
Displays per-interface transmit and receive statistics read from the hardware, the interface internal registers, the statistics read from LRE and CPE ports.
clear controllers lre
Use the clear controllers lre user EXEC command to reset an Long-Reach Ethernet (LRE) switch interface or a Cisco LRE customer premises equipment (CPE) device interface.
clear controllers lre {local link | remote [link | micro]} interface-id
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
Defaults
No default is defined.
Command Modes
User EXEC
Command History
Usage Guidelines
Use this command to reset a questionable local or remote interface.
The clear controllers lre remote micro command is not supported on the Cisco 575 LRE CPE and the Cisco 576 LRE 997 CPE devices.
Examples
This example shows how to reset the local LRE interfaces on the switch:
Switch> clear controllers lre local linkThis example shows how to reset the Cisco 575 LRE, Cisco 576 LRE 997 CPE, and the Cisco 585 LRE CPE devices connected to the switch:
Switch> clear controllers lre remote linkThis example shows how to reset the Cisco 585 LRE CPE micro-controller connected to the switch:
Switch> clear controllers lre remote microRelated Commands
clear controllers lre link monitor
Use the clear controllers lre link monitor privileged EXEC command to clear Long-Reach Ethernet (LRE) link monitor data.
clear controllers lre link monitor interface-id
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command clears all collected link monitor data. New entries are added when a new polling cycle starts.
Examples
This example shows how to clear link monitor data on LRE interface 0/2:
Switch# clear controllers lre link monitor longreachethernet 0/2Related Commands
clear controllers lre log
Use the clear controllers lre log privileged EXEC command to clear the history of link, configuration, and timer events for a specific Long-Reach Ethernet (LRE) port or for all switch LRE ports.
clear controllers lre log [interface-id]
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear controllers lre log command without specifying a switch LRE port to delete the history of events on all LRE ports.
Examples
This example shows how to delete the history of events on LRE switch port 3:
Switch# clear controllers lre log longreachethernet 0/3You can verify that the information was deleted by entering the show controllers lre log privileged EXEC command.
Related Commands
Sets the LRE logging level.
Displays the history of link, configuration, and timer events for a LRE specific switch port or for all LRE switch ports.
clear interface
Use the clear interface privileged EXEC command to clear the hardware logic on an interface or a VLAN.
clear interface {interface-id | vlan vlan-id}
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear the hardware logic on a Gigabit Ethernet interface:
Switch# clear interface gigabitethernet0/1This example shows how to clear the hardware logic on a specific VLAN:
Switch# clear interface vlan 5You can verify that the interface-reset counter for an interface is incremented by entering the show interfaces privileged EXEC command.
clear lacp
Use the clear lacp privileged EXEC command to clear Link Aggregration Control Protocol (LACP) channel-group information.
clear lacp {channel-group-number | counters}
Syntax Description
Defaults
This command has no default setting.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear channel-group information for a specific group:
Switch# clear lacp 4This example shows how to clear channel-group traffic counters:
Switch# clear lacp countersYou can verify that the information was deleted by entering the show lacp privileged EXEC command.
Related Commands
clear lre rate selection
Use the clear lre rate selection privileged EXEC command to reset the current rate selection setting and to restart rate selection for a specific Long-Reach Ethernet (LRE) port or for all switch LRE ports.
clear lre rate selection [lock] [interface-id]
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
lock
(Optional) Rate selection runs on all ports that have rate selection enabled, including ports that are locked.
interface-id
(Optional) ID of an LREs witch port.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you enter the lock keyword or specify an interface, the switch runs rate selection on all LRE switch ports that have rate selection enabled, except those ports with locked profiles. If you enter the lock keyword, the switch runs rate selection on all profiles, including those that are locked.
Examples
This example shows how to reset the rate selection setting and to restart rate selection on LRE port 1:
Switch# clear lre rate selection longreachethernet0/1This example shows how to rerun rate selection on all ports, including any locked ports:
Switch# clear lre rate selection lockThis example shows how to reset and to restart rate selection on LRE port 2, overriding the locked status:
Switch# clear lre rate selection lock longreachethernet0/2Related Commands
Enables rate selection on an LRE specific port
Assigns a rate selection sequence for a specific LRE port.
Assigns a rate selection sequence for the entire LRE switch.
clear mac address-table
Use the clear mac address-table privileged EXEC command to delete from the MAC address table a specific dynamic address, all dynamic addresses on a particular interface, or all dynamic addresses on a particular VLAN. This command also clears the MAC address notification global counters.
clear mac address-table {dynamic [address mac-addr | interface interface-id | vlan vlan-id] | notification}
Note
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to remove a specific dynamic address from the MAC address table:
Switch# clear mac address-table dynamic address 0008.0070.0007You can verify that the information was deleted by entering the show mac address-table privileged EXEC command.
Related Commands
clear pagp
Use the clear pagp privileged EXEC command to clear Port Aggregation Protocol (PAgP) channel-group information.
clear pagp {channel-group-number [counters] | counters}
Syntax Description
Defaults
This command has no default setting.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear channel-group information for a specific group:
Switch# clear pagp 4This example shows how to clear channel-group traffic counters:
Switch# clear pagp countersYou can verify that the information was deleted by entering the show pagp privileged EXEC command.
Related Commands
clear port-security
Use the clear port-security privileged EXEC command to delete from the MAC address table all secure addresses, all configured secure addresses, or a specific dynamic or sticky secure address on an interface.
clear port-security {all | configured | dynamic | sticky} [address mac-address] | [interface interface-id]
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
12.1(11)EA1
This command was introduced.
12.1(14)EA1
The all and configured keywords were added.
Usage Guidelines
If you enter the clear port-security all privileged EXEC command, the switch removes all secure MAC addresses from the MAC address table.
If you enter the clear port-security configured address mac-address command, the switch removes the specified secure MAC address from the MAC address table.
If you enter the clear port-security dynamic interface interface-id command, the switch removes all dynamic secure MAC addresses on an interface from the MAC address table.
If you enter the clear port-security sticky command, the switch removes all sticky secure MAC addresses from the MAC address table.
Examples
This example shows how to remove all secure addresses from the MAC address table:
Switch# clear port-security allThis example shows how to remove a configured secure address from the MAC address table:
Switch# clear port-security configured address 0008.0070.0007This example shows how to remove all the dynamic secure addresses learned on a specific interface:
Switch# clear port-security dynamic interface fastethernet0/1This example shows how to remove all the sticky secure addresses from the address table:
Switch# clear port-security stickyYou can verify that the information was deleted by entering the show port-security privileged EXEC command.
Related Commands
Displays the port security settings for an interface or for the switch.
Enables port security on an interface.
clear setup express
Use the clear setup express privileged EXEC command to exit Express Setup mode without saving the current configuration.
clear setup express
This command is available only on Catalyst 2950 switches.
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can use the clear setup express privileged EXEC command to exit Express Setup mode. For example, if you activate Express Setup and then decide to connect to the switch through the console port instead of through an Ethernet port, enter the clear setup express command. The switch exits Express Setup mode. The IP address 10.0.0.1 is no longer valid on the switch, and your connection using this IP address is ended.
This command is available only when the switch is in Express Setup mode.
Examples
This example shows how to exit Express Setup mode:
Switch# clear setup expressYou can verify that the switch has exited Express Setup mode by entering the show express setup privileged EXEC command.
Related Commands
Enables Express Setup mode on the switch.
Displays if Express Setup mode is active on the switch.
clear spanning-tree counters
Use the clear spanning-tree counters privileged EXEC command to clear the spanning-tree counters.
clear spanning-tree counters [interface interface-id]
Syntax Description
interface interface-id
(Optional) Clear all spanning-tree counters on the specified interface. If interface-id is not specified, spanning-tree counters are cleared for all interfaces.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear spanning-tree counters for all interfaces:
Switch# clear spanning-tree countersRelated Commands
clear spanning-tree detected-protocols
Use the clear spanning-tree detected-protocols privileged EXEC command to restart the protocol migration process (force the renegotiation with neighboring switches) on all interfaces or on the specified interface.
clear spanning-tree detected-protocols [interface interface-id]
This command is available only if your switch is running the enhanced software image (EI).
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A switch running the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol or the Multiple Spanning Tree Protocol (MSTP) supports a built-in protocol migration mechanism that enables it to interoperate with legacy 802.1D switches. If a rapid-PVST+ switch or an MSTP switch receives a legacy 802.1D configuration bridge protocol data unit (BPDU) with the protocol version set to 0, it sends only 802.1D BPDUs on that port. A multiple spanning-tree (MST) switch can also detect that a port is at the boundary of a region when it receives a legacy BPDU, an MST BPDU (version 3) associated with a different region, or an RST BPDU (version 2).
However, the switch does not automatically revert to the rapid-PVST+ or the MSTP mode if it no longer receives 802.1D BPDUs because it cannot determine whether the legacy switch has been removed from the link unless the legacy switch is the designated switch. Use the clear spanning-tree detected-protocols command in this situation.
Examples
This example shows how to restart the protocol migration process on Fast Ethernet interface 0/1:
Switch# clear spanning-tree detected-protocols interface fastethernet0/1clear vmps statistics
Use the clear vmps statistics privileged EXEC command to clear the statistics maintained by the VLAN Query Protocol (VQP) client.
clear vmps statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear VLAN Membership Policy Server (VMPS) statistics:
Switch# clear vmps statisticsYou can verify that the information was deleted by entering the show vmps statistics privileged EXEC command.
Related Commands
show vmps statistics
Displays the VQP version, reconfirmation interval, retry count, VMPS IP addresses, and the current and primary servers.
clear vtp counters
Use the clear vtp counters privileged EXEC command to clear the VLAN Trunking Protocol (VTP) and pruning counters.
clear vtp counters
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear the VTP counters:
Switch# clear vtp countersYou can verify that the information was deleted by entering the show vtp counters privileged EXEC command.
Related Commands
show vtp counters
Displays general information about the VTP management domain, status, and counters.
cluster commander-address
You do not need to enter this command. The command switch automatically provides its MAC address to member switches when these switches join the cluster. The member switch adds this information and other cluster information to its running configuration file. Enter the no form of this global configuration command from the member switch console port to remove it from a cluster only during debugging or recovery procedures.
cluster commander-address mac-address [member number name name]
no cluster commander-address
Syntax Description
Defaults
The switch is not a member of any cluster.
Command Modes
Global configuration
Command History
Usage Guidelines
A cluster member can have only one command switch.
The member switch retains the identity of the command switch during a system reload by using the mac-address parameter.
You can enter the no form on a member switch to remove it from the cluster during debugging or recovery procedures. You would normally use this command from the member switch console port only when the member has lost communication with the command switch. With normal switch configuration, we recommend that you remove member switches only by entering the no cluster member n global configuration command on the command switch.
When a standby command-switch becomes active (becomes the command switch), it removes the cluster commander-address line from its configuration.
Examples
This is an example of text from the running configuration of a cluster member:
Switch(config)# show running-config<output truncated>cluster commander-address 00e0.9bc0.a500 member 4 name my_cluster<output truncated>This example shows how to remove a member from the cluster by using the cluster member console:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# no cluster commander-addressYou can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
cluster discovery hop-count
Use the cluster discovery hop-count global configuration command on the command switch to set the hop-count limit for extended discovery of candidate switches. Use the no form of this command to set the hop count to the default value.
cluster discovery hop-count number
no cluster discovery hop-count
Syntax Description
number
Number of hops from the cluster edge that the command switch limits the discovery of candidates. The range is from 1 to 7.
Defaults
The hop count is set to 3.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the command switch. This command does not operate on member switches.
If the hop count is set to 1, it disables extended discovery. The command switch discovers only candidates that are one hop from the edge of the cluster. The edge of the cluster is the point between the last discovered member switch and the first discovered candidate switch.
Examples
This example shows how to set the hop count limit to 4. This command is entered on the command switch.
Switch(config)# cluster discovery hop-count 4You can verify your settings by entering the show cluster privileged EXEC command on the command switch.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
Displays a list of candidate switches.
cluster enable
Use the cluster enable global configuration command on a command-capable switch to enable it as the cluster command switch, assign a cluster name, and optionally assign a member number to it. Use the no form of this command to remove all members and make the command switch a candidate switch.
cluster enable name [command-switch-member-number]
no cluster enable
Syntax Description
Defaults
The switch is not a command switch.
No cluster name is defined.
The member number is 0 when this is the command switch.
Command Modes
Global configuration
Command History
Usage Guidelines
This command runs on any command-capable switch that is not part of any cluster. This command fails if a device is already configured as a member of the cluster.
You must name the cluster when you enable the command switch. If the switch is already configured as the command switch, this command changes the cluster name if it is different from the previous name.
Examples
This example shows how to enable the command switch, name the cluster, and set the command switch member number to 4:
Switch(config)# cluster enable Engineering-IDF4 4You can verify your settings by entering the show cluster privileged EXEC command on the command switch.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
cluster holdtime
Use the cluster holdtime global configuration command on the command switch to set the duration in seconds before a switch (either the command or member switch) declares the other switch down after not receiving heartbeat messages. Use the no form of this command to set the duration to the default value.
cluster holdtime holdtime-in-secs
no cluster holdtime
Syntax Description
holdtime-in-secs
Duration in seconds before a switch (either a command or member switch) declares the other switch down. The range is from 1 to 300 seconds.
Defaults
The holdtime is 80 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command with the cluster timer global configuration command only on the command switch. The command switch propagates the values to all its cluster members so that the setting is consistent among all switches in the cluster.
The holdtime is typically set as a multiple of the interval timer (cluster timer). For example, it takes (holdtime-in-secs divided by interval-in-secs) number of heartbeat messages to be missed in a row to declare a switch down.
Examples
This example shows how to change the interval timer and the duration on the command switch:
Switch(config)# cluster timer 3Switch(config)# cluster holdtime 30You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
cluster management-vlan
Use the cluster management-vlan global configuration command on the command switch to change the management VLAN for the entire cluster. Use the no form of this command to change the management VLAN to VLAN 1.
cluster management-vlan n
no cluster management-vlan
Syntax Description
n
VLAN ID of the new management VLAN. Valid VLAN IDs are from 1 to 4094 when the enhanced software image (EI) is installed and 1 to 1001 when the standard software image (SI) is installed.
Defaults
The default management VLAN is VLAN 1.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the command switch. This command changes the management VLAN of the command switch and member switches. Member switches must have either a trunk connection or connection to the new command-switch management VLAN to maintain communication with the command switch.
This command is not written to the configuration file.
Examples
This example shows how to change the management VLAN to VLAN 5 on the entire cluster:
Switch(config)# cluster management-vlan 5You can verify your settings by entering the show interfaces vlan vlan-id privileged EXEC command.
Related Commands
Displays the administrative and operational status of a switching (nonrouting) port.
cluster member
Use the cluster member global configuration command on the command switch to add members to a cluster. Use the no form of this command to remove members from the cluster.
cluster member [n] mac-address H.H.H [password enable-password] [vlan vlan-id]
no cluster member n
Syntax Description
Defaults
A newly enabled command switch has no associated cluster members.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the command switch to add a member to or remove a member from the cluster. If you enter this command on a switch other than the command switch, the switch rejects the command and displays an error message.
You must enter a member number to remove a switch from the cluster. However, you do not need to enter a member number to add a switch to the cluster. The command switch selects the next available member number and assigns it to the switch that is joining the cluster.
You must enter the enable password of the candidate switch for authentication when it joins the cluster. The password is not saved in the running or startup configuration. After a candidate switch becomes a member of the cluster, its password becomes the same as the command-switch password.
If a switch does not have a configured host name, the command switch appends a member number to the command-switch host name and assigns it to the member switch.
If you do not specify a VLAN ID, the command switch automatically chooses a VLAN and adds the candidate to the cluster.
Examples
This example shows how to add a switch as member 2 with MAC address 00E0.1E00.2222 and the password key to a cluster. The command switch adds the candidate to the cluster through VLAN 3.
Switch(config)# cluster member 2 mac-address 00E0.1E00.2222 password key vlan 3This example shows how to add a switch with MAC address 00E0.1E00.3333 to the cluster. This switch does not have a password. The command switch selects the next available member number and assigns it to the switch joining the cluster:
Switch(config)# cluster member mac-address 00E0.1E00.3333You can verify your settings by entering the show cluster members privileged EXEC command on the command switch.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
Displays a list of candidate switches.
Displays information about the cluster members.
cluster run
Use the cluster run global configuration command to enable clustering on a switch. Use the no form of this command to disable clustering on a switch.
cluster run
no cluster run
Defaults
Clustering is enabled on all switches.
Command Modes
Global configuration
Command History
Usage Guidelines
When you enter the no cluster run command on a command switch, the command switch is disabled. Clustering is disabled, and the switch cannot become a candidate switch.
When you enter the no cluster run command on a member switch, it is removed from the cluster. Clustering is disabled, and the switch cannot become a candidate switch.
When you enter the no cluster run command on a switch that is not part of a cluster, clustering is disabled on this switch. This switch cannot then become a candidate switch.
Examples
This example shows how to disable clustering on the command switch:
Switch(config)# no cluster runYou can verify that clustering is disabled by entering the show cluster privileged EXEC command.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
cluster standby-group
Use the cluster standby-group global configuration command to enable command switch redundancy by binding the Hot Standby Router Protocol (HSRP) standby group to the cluster. Use the no form of this command to unbind the cluster from the HSRP standby group.
cluster standby-group HSRP-group-name
no cluster standby-group
Syntax Description
HSRP-group-name
Name of the HSRP group that is bound to the cluster. The group name is limited to 32 characters.
Defaults
The cluster is not bound to any HSRP group.
Command Modes
Global configuration
Command History
Usage Guidelines
You must enter this command only on the command switch. If you enter it on a member switch, an error message appears.
The command switch propagates the cluster-HSRP binding information to all members. Each member switch stores the binding information in its nonvolatile RAM (NVRAM).
The HSRP group name must be a valid standby group; otherwise, the command entry produces an error.
Use the same group name on all members of the HSRP standby group that is to be bound to the cluster. Use the same HSRP group name on all cluster-HSRP capable members for the HSRP group that is to be bound. (When not binding a cluster to an HSRP group, you can use different names on the cluster command and the member switches.)
Examples
This example shows how to bind the HSRP group named my_hsrp to the cluster. This command is entered on the command switch.
Switch(config)# cluster standby-group my_hsrpThis example shows the error message when this command is entered on a command switch and the specified HSRP standby group does not exist:
Switch(config)# cluster standby-group my_hsrp%ERROR:Standby (my_hsrp) group does not existThis example shows the error message when this command is entered on a member switch:
Switch(config)# cluster standby-group my_hsrp%ERROR:This command runs on a cluster command switchYou can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
show standby
Displays standby group information.
standby ip
Enables HSRP on the interface.
cluster timer
Use the cluster timer global configuration command on the command switch to set the interval in seconds between heartbeat messages. Use the no form of this command to set the interval to the default value.
cluster timer interval-in-secs
no cluster timer
Syntax Description
Defaults
The interval is 8 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command with the cluster holdtime global configuration command only on the command switch. The command switch propagates the values to all its cluster members so that the setting is consistent among all switches in the cluster.
The holdtime is typically set as a multiple of the heartbeat interval timer (cluster timer). For example, it takes (holdtime-in-secs divided by the interval-in-secs) number of heartbeat messages to be missed in a row to declare a switch down.
Examples
This example shows how to change the heartbeat interval timer and the duration on the command switch.
Switch(config)# cluster timer 3Switch(config)# cluster holdtime 30You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
controller longreachethernet
Use the controller longreachethernet global configuration command to enter the controller configuration mode.
controller longreachethernet ctrlr-number
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
ctrlr-number
LRE controller number. Controller numbers are device specific. Valid entries are 0 to 2 on a 24-port LRE switch and 0 on an 8-port LRE switch.
Defaults
No default is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enter the controller configuration mode. An LRE controller is the LRE chipset in the switch.
Examples
This example shows how to enter the controller configuration mode for controller 0.
Switch(config)# controller longreachethernet 0Switch(config-controller)#Related Commands
Configures upgrades on either end of an LRE link.
Prevents an upgrade of the local customer premises equipment (CPE) controller and all remote CPE devices connected to it.
cpe duplex
Use the cpe duplex interface configuration command to specify the duplex mode of operation for all customer premises equipment (CPE) ports. Use the no form of this command to return the port to its default value.
cpe duplex {{auto | full | half} [port port-id]}
no cpe duplex {{auto | full | half} [port port-id]}
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
Defaults
The default duplex mode is half.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the cpe duplex full command to set the duplex mode to full for all the CPE Ethernet ports. Use the auto keyword to set the CPE Ethernet ports to autonegotiate, and use the half keyword to force the duplex mode to half for all the CPE Ethernet ports.
If you do not enter the port keyword, the duplex setting is applied globally to all the CPE Ethernet ports. If you enter the port port-id keywords, the setting is applied to the specified CPE Ethernet port and overrides any global speed settings.
Use the cpe duplex full port 2 command to set the duplex mode of port 2 on a CPE device to full duplex. If you enter both a switch-wide command, such as the cpe duplex full command, and a port-specific commands, such as the cpe duplex full port 2 command, the switch adds both the configuration file, and the port-specific command takes priority over the switch-wide command.
Examples
This example show how to set the CPE device to autonegotiate:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/2Switch(config-if)# cpe duplex autoThis example shows how to set port 3 of a Cisco 585 LRE CPE to full-duplex mode:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/3Switch(config-if)# cpe duplex full port 3This example shows how to restore port 3 of a Cisco 585 LRE CPE to the default mode of half duplex:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/3Switch(config-if)# no cpe duplex full port 3This example shows how the cpe duplex {auto | full | half} port port-id command works with the the cpe duplex {auto | full | half} command. Port 1 is set to full duplex, port 2 is set to half duplex, and the remainder of the ports are set to autonegotiate.
Switch# configure terminalSwitch(config)# interface longreachethernet 0/4Switch(config-if)# cpe duplex autoSwitch(config-if)# cpe duplex full port 1Switch(config-if)# cpe duplex half port 2After the commands in the previous example are entered, this example shows how to set port 1 is to autonegotiate.
Switch(config-if)# no cpe duplex full port 1Related Commands
Specifies the CPE port speed settings.
show interfaces cpe
Displays CPE Ethernet ports connection, speed, or duplex status.
cpe protected
Use the cpe protected interface configuration command to restrict data traffic to individual ports on Cisco 585 LRE customer premises equipment (CPE) ports. Use the no form of this command to allow different ports on the same CPE device to exchange data directly.
cpe protected [port port-id]
no cpe protected [port port-id]
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
port port-id
(Optional) CPE Ethernet port identifier. Valid values vary from 1
to 4, depending on CPE device.
Defaults
Traffic is not restricted to specific ports.
Command Modes
Interface configuration
Command History
Usage Guidelines
Even though you can protect an LRE interface by using the switchport protected interface configuration command, this command does not protect individual CPE Ethernet ports. Use the cpe protected command to ensure that data traffic from one CPE port is not accessed on any of the other three ports. Use the cpe protected command to restrict CPE traffic, either at the CPE device level or at the individual port level for data security. Use the cpe protected command without specifying a CPE port to protect data for all applicable CPE ports. Use the cpe protected port port-id command to protect a specific CPE Ethernet port.
When using this feature, always specify a minimum of two ports. A single port that is configured as protected has no effect. Data traffic does not flow between two ports that are protected.
Examples
This example show how to protect CPE port 1 on LRE port 0/1:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/1Switch(config-if)# cpe protected port 1Related Commands
Shows CPE protected port information.
Isolates unicast, multicast, and broadcast traffic at Layer 2 from other protected ports on the same switch.
cpe shutdown
Use the cpe shutdown interface configuration command to disable one or more customer premises equipment (CPE) ports. Use the no form of this command to enable a port.
cpe shutdown [port port-id]
no cpe shutdown [port port-id]
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
port port-id
(Optional) CPE Ethernet port identifier. Valid values vary from 1
to 4, depending on the CPE device.
Defaults
The CPE ports are enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
If the keyword port is not specified, the value is applied globally to all the CPE Ethernet ports. If the keyword port is specified, the value is applied to the specific CPE Ethernet port and overrides any global speed settings.
The CPE Ethernet ports can be shut down at the CPE device level and the port level. If you add a configuration at the CPE device level and at the port level, you must enter the no form of the command for both configurations to return the port to the default state.
Examples
This example shows how to disable all ports on the CPE device:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/2Switch(config-if)# cpe shutdownThis example shows how to disable port 2 on the CPE device:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/2Switch(config-if)# cpe shutdown port 2After the cpe shutdown port 2 command was entered in the previous example, this example shows how to enable all the CPE Ethernet ports that were not shut down. After the no cpe shutdown command is entered, port 2 is still shut down because the cpe shutdown port 2 command was entered in the previous example. Use the no cpe shutdown port 2 command to enable the port 2.
Switch# configure terminalSwitch(config)# interface longreahethernet 0/2Switch(config-if)# no cpe shutdownSwitch(config-if)#Related Commands
show interfaces cpe
Displays CPE Ethernet ports connection, speed, or duplex status.
Disables a port.
cpe speed
Use the cpe speed interface configuration command to set the speed of a customer premises equipment (CPE) port. Use the no form of this command to return the port to the default setting.
cpe speed {{auto | 10 | 100} [port port-id]}
no cpe speed {{auto | 10 | 100} [port port-id]}
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
Defaults
The default speed is auto.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you do not enter the port keyword, the speed setting is applied globally to all the CPE Ethernet ports. If you enter the port port-id keywords, the setting is applied to the specified CPE Ethernet port and overrides any global speed settings.
Examples
This example shows how to set port 1 on a CPE to 100 Mbps:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/2Switch(config-if)# cpe speed 100 port 1This example shows how to return the default speed setting on all CPE Ethernet ports that were not configured with the cpe speed {10 | 100} port port-id command:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/2Switch(config-if)# no cpe speed 100This example shows how to set port 1 to 10 Mbps, port 2 to 100 Mbps, and the remainder of the ports to autonegotiate.
Switch# configure terminalSwitch(config)# interface longreachethernet 0/4Switch(config-if)# cpe speed autoSwitch(config-if)# cpe speed 10 port 1Switch(config-if)# cpe speed 100 port 2This example shows how to set port 1 to autonegotiate after the cpe speed 10 command is entered:
Switch(config-if)# no cpe speed 10 portRelated Commands
Sets the port speed for LRE ports.
show interfaces cpe
Displays connection, speed, and duplex settings for CPE Ethernet ports attached to the specified LRE switch port
cpe toggle
Use the cpe toggle interface configuration command to enable the CPE toggle feature. When this feature is enabled, a remote customer premises equipment (CPE) link automatically transitions from down to up if the Long-Reach Ethernet (LRE) link comes up in less than 30 seconds. Use the no form of this command to disable the CPE toggle feature on a specific port or on the switch.
cpe toggle [port cpe-port-id]
no cpe toggle [port cpe-port-id]
This command is available only on Catalyst 2950 Long-Reach Ethernet (LRE) switches.
Syntax Description
Defaults
CPE toggle is enabled on all interfaces.
Command Modes
Interface configuration
Command History
Usage Guidelines
A CPE Ethernet link is the connection between the CPE Ethernet port and the remote Ethernet device (such as a PC) connected to it. It is not the link between the switch LRE port and the LRE CPE device, which is referred to as the LRE link.
CPE toggle cannot be disabled on a Cisco 575 LRE or Cisco 576 LRE 997 CPE link.
You can disable CPE toggle on a link from a Cisco 585 LRE CPE to a remote Ethernet device. You can disable CPE toggle on all interfaces or on a specific interface by using the no cpe toggle [port cpe-port-id] interface configuration command. If CPE toggle is disabled and the LRE link comes up in less than 30 seconds, the CPE link transitions from down to up.
If the port keyword is not specified, this command applies to all Fast Ethernet ports on a CPE device. If the port keyword and a port ID are specified, this command applies to the specific Fast Ethernet port on the CPE and overrides the global configuration.
Examples
This example shows how to disable CPE toggle on a CPE port:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/2Switch(config-if)# no cpe toggleRelated Commands
cpe type
Use the cpe type interface configuration command to set the type of customer premises equipment (CPE) port that is connected to a Long-Reach Ethernet (LRE) switch.
cpe type [cisco575-lre | cisco576-lre997 | cisco585-lre | unknown]
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
Defaults
The default CPE type is unknown.
Command Modes
Interface configuration
Command History
12.1(11)YJ
This command was introduced.
12.1(11)YJ4
The cisco576-lre997 keyword was added.
Usage Guidelines
This command can only be used when the port is shut down. If the link is active on a CPE device port, the switch detects the CPE device type and automatically modifies the configuration. You cannot change the CPE device type on active links. For example, if the active CPE device type is cisco575-lre, you cannot change the type to cisco585-lre or unknown.
Examples
This example shows how to set the CPE device type to cisco585-lre while the link is down:
Switch# configure terminalSwitch(config)# interface longreachethernet 0/2Switch(config-if)# cpe type cisco585-lreRelated Commands
show interfaces cpe
Displays connection, speed, and duplex settings for CPE Ethernet ports attached to the specified LRE switch port.
define interface-range
Use the define interface-range global configuration command to create an interface-range macro. Use the no form of this command to delete the defined macro.
define interface-range macro-name interface-range
no define interface-range macro-name interface-range
Syntax Description
macro-name
Name of the interface-range macro; up to 32 characters.
interface-range
Interface range; for valid values for interface ranges, see "Usage Guidelines."
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
Usage Guidelines
The macro name is a 32-character maximum character string.
A macro can contain up to five ranges.
All interfaces in a range must be the same type; that is, all Fast Ethernet ports, all Gigabit Ethernet ports, all EtherChannel ports, or all VLANs, but you can combine multiple interface types in a macro.
When entering the interface-range, use this format:
•
•
Valid values for type and interface:
•
•
•
•
•
VLAN interfaces must have been configured with the interface vlan command (the show running-config privileged EXEC command displays the configured VLAN interfaces). VLAN interfaces not displayed by the show running-config command cannot be used in interface-ranges.
For physical interfaces, the interface-id is defined as a slot/number (where slot is always 0 for the switch), and the range can be entered as type 0/number - number (for example, gigabitethernet0/1 - 2). You can also enter multiple ranges.
When you define a range, you must enter a space before and after the hyphen (-):
interface range gigabitethernet0/1 - 2When you define multiple ranges, you must enter a space before and after the comma (,):
interface range fastethernet0/3 - 7 , gigabitethernet0/1 - 2Examples
This example shows how to create a multiple-interface macro:
Switch(config)# define interface-range macro1 fastethernet 0/3 -7 , gigabitethernet 0/2Related Commands
delete
Use the delete privileged EXEC command to delete a file or directory on the Flash memory device.
delete [/force] [/recursive] filesystem:/file-url
Syntax Description
Command Modes
Privileged EXEC
Command History
12.0(5.2)WC(1)
This command was introduced.
12.1(6)EA2
The /force and /recursive keywords were added.
Usage Guidelines
If you use the /force keyword, you are prompted once at the beginning of the deletion process to confirm the deletion.
If you use the /recursive keyword without the /force keyword, you are prompted to confirm the deletion of every file.
The prompting behavior depends on the setting of the file prompt global configuration command. By default, the switch prompts for confirmation on destructive file operations. For more information about this command, refer to the Cisco IOS Command Reference for Cisco IOS Release 12.1.
Examples
This example shows how to delete a file from the switch Flash memory:
Switch# delete flash:filenameYou can verify that the directory was removed by entering the dir filesystem: privileged EXEC command.
Related Commands
deny (access-list configuration)
Use the deny access-list configuration command to configure conditions for a named or numbered IP access control list (ACL). Use the no form of this command to remove a deny condition from the IP ACL.
Use these commands with standard IP ACLs:
deny {source source-wildcard | host source | any}
no deny {source source-wildcard | host source | any}
Use these commands with extended IP ACLs:
deny protocol {source source-wildcard | host source | any} [operator port] {destination destination-wildcard | host source | any} [operator port] [dscp dscp-value] [time-range time-range-name]
no deny protocol {source source-wildcard | host source | any} [operator port] {destination destination-wildcard | host source | any} [operator port] [dscp dscp-value] [time-range time-range-name]
This command is available on physical interfaces only if your switch is running the enhanced software image (EI).
Syntax Description
Defaults
There are no specific conditions that deny packets in the named or numbered IP ACL.
The default ACL is always terminated by an implicit deny statement for all packets.
Command Modes
Access-list configuration
Command History
Usage Guidelines
Use this command after the ip access-list global configuration command to specify deny conditions for an IP ACL. You can specify a source IP address, destination IP address, IP protocol, TCP port, or UDP port. Specify the TCP and UDP port numbers only if protocol is tcp or udp and operator is eq.
Note
Examples
This example shows how to create an extended IP ACL and to configure deny conditions for it:
Switch(config)# ip access-list extended InternetfilterSwitch(config-ext-nacl)# deny tcp host 190.5.88.10 anySwitch(config-ext-nacl)# deny tcp host 192.1.10.10 anyThis is an example of a standard ACL that sets a deny condition:
ip access-list standard Acclist1deny 192.5.34.0 0.0.0.255deny 128.88.10.0 0.0.0.255deny 36.1.1.0 0.0.0.255
Note
You can verify your settings by entering the show ip access-lists or show access-lists privileged EXEC command.
Related Commands
Defines an IP ACL.
Sets conditions for an IP ACL.
Controls access to an interface.
Displays IP ACLs configured on the switch.
Displays ACLs configured on a switch.
deny (MAC access-list configuration)
Use the deny MAC access-list configuration command to prevent Layer 2 traffic from being forwarded if the conditions are matched. Use the no form of this command to remove a deny condition from the MAC named access control list (ACL).
{permit | deny} {any | host src-MAC-addr} {any | host dst-MAC-addr} [aarp | amber | appletalk | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | mop-console | mop-dump | msdos | mumps | netbios | vines-echo |vines-ip | xns-idp]
no {permit | deny} {any | host src-MAC-addr} {any | host dst-MAC-addr} [aarp | amber | appletalk | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | mop-console | mop-dump | msdos | mumps | netbios | vines-echo |vines-ip | xns-idp]
This command is available only if your switch is running the enhanced software image (EI).
Syntax Description
Defaults
This command has no defaults. However, the default action for a MAC named ACL is to deny.
Command Modes
MAC access-list configuration
Command History
Usage Guidelines
When an access control entry (ACE) is added to an ACL, an implied deny-any-any condition exists at the end of the list. That is, if there are no matches, the packets are denied. However, before the first ACE is added, the list permits all packets.
These options are not allowed:
•
•
•
Note
Examples
This example shows how to define the MAC named extended ACL to deny NETBIOS traffic from any source to MAC address 00c0.00a0.03fa. Traffic matching this list is denied.
Switch(config-ext-macl)# deny any host 00c0.00a0.03fa netbiosThis example shows how to remove the deny condition from the named MAC extended ACL:
Switch(config-ext-macl)# no deny any host 00c0.00a0.03fa netbiosYou can verify your settings by entering the show access-lists privileged EXEC command.
Related Commands
Creates an ACL based on MAC addresses for non-IP traffic.
Permits Layer 2 traffic to be forwarded if conditions are matched.
Displays ACLs configured on a switch.
dot1x default
Use the dot1x default interface configuration command to reset the configurable 802.1X parameters to their default values.
dot1x default
Syntax Description
This command has no arguments or keywords.
Defaults
These are the default values:
•
•
•
•
•
•
•
•
•
Command Modes
Interface configuration
Command History
12.1(6)EA2
This command was introduced.
12.1(14)EA1
This command was changed to the interface configuration mode.
Examples
This example shows how to reset the configurable 802.1X parameters on an interface:
Switch(config-if)# dot1x defaultYou can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
dot1x guest-vlan
Use the dot1x guest-vlan interface configuration command to specify an active VLAN as an 802.1X guest VLAN for switches running the enhanced software image (EI). Use the no form of this command to return to the default setting.
dot1x guest-vlan vlan-id
no dot1x guest-vlan
Syntax Description
Defaults
No guest VLAN is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you configure a guest VLAN, clients that are not 802.1X-capable are put into the guest VLAN when the server does not receive a response to its Extensible Authentication Protocol over LAN (EAPOL) request/identity frame. Clients that are 802.1X-capable but fail authentication are not granted access to the network.
Guest VLANs are supported on 802.1X ports in single-host mode and multiple-hosts mode.
Any VLAN can be configured as an 802.1X guest VLAN except RSPAN VLANs or voice VLANs.
Examples
This example shows how to specify VLAN 5 as an 802.1X guest VLAN:
Switch(config-if)# dot1x guest-vlan 5You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
dot1x host-mode
Use the dot1x host-mode interface configuration command to allow a single host (client) or multiple hosts on an 802.1X-authorized port that has the dot1x port-control interface configuration command set to auto. Use the no form of this command to return to the default setting.
dot1x host-mode {multi-host | single-host}
no dot1x host-mode [multi-host | single-host]
Syntax Description
multi-host
Enable multiple-hosts mode on the switch.
single-host
Enable single-host mode on the switch.
Defaults
The default is single-host mode.
Command Modes
Interface configuration
Command History
12.1(14)EA1
This command was introduced. It replaces the dot1x multiple-hosts interface configuration command.
Usage Guidelines
You can use this command to limit an 802.1X-enabled port to a single client or to attach multiple clients to an 802.1X-enabled port. In multiple-hosts 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.
Before entering this command, make sure that the dot1x port-control interface configuration command is set to auto for the specified interface.
Examples
This example shows how to enable 802.1X globally, enable 802.1X on Fast Ethernet interface 0/1, and enable multiple-hosts mode:
Switch(config)# dot1x system-auth-controlSwitch(config)# interface fastethernet0/1Switch(config-if)# dot1x port-control autoSwitch(config-if)# dot1x host-mode multi-hostYou can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
dot1x initialize
Use the dot1x initialize privileged EXEC command to manually return an 802.1X-enabled port to an unauthorized state before initiating a new authentication session on the interface.
dot1x initialize interface interface-id
Syntax Description
This command has no arguments or keywords.
Defaults
There is no default setting.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to manually return a device connected to a switch interface to an unauthorized state before initiating a new authentication session on the interface.
Examples
This example shows how to manually return a device connected to Fast Ethernet interface 0/1 to an unauthorized state:
Switch# dot1x initialize interface fastethernet0/1You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
dot1x max-req
Use the dot1x max-req interface configuration command to set the maximum number of times that the switch sends an Extensible Authentication Protocol (EAP)-request/identity frame (assuming that no response is received) to the client before restarting the authentication process. Use the no form of this command to return to the default setting.
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. The range is 1 to 10.
Defaults
The default is 2.
Command Modes
Interface configuration
Command History
12.1(6)EA2
This command was introduced.
12.1(14)EA1
This command was changed to the interface configuration mode.
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.
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 5You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
Sets the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request.
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
dot1x multiple-hosts
This is an obsolete command.
In past releases, the dot1x multiple-hosts interface configuration command was used to allow multiple hosts (clients) on an 802.1X-authorized port.
Command History
12.1(6)EA2
This command was introduced.
12.1(14)EA1
The dot1x multiple-hosts interface configuration command was replaced by the dot1x host-mode interface configuration command.
Related Commands
Set the 802.1X host mode on an interface.
Displays 802.1X statistics, administrative status, and operational status for the switch or for the specified interface.
dot1x port-control
Use the dot1x port-control interface configuration command to enable manual control of the authorization state of the port. Use the no form of this command to return to the default setting.
dot1x port-control {auto | force-authorized | force-unauthorized}
no dot1x port-control
Syntax Description
Defaults
The default is force-authorized.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must enable 802.1X globally on the switch by using the dot1x system-auth-control global configuration command before enabling 802.1X on a specific interface.
The 802.1X protocol is supported on Layer 2 static-access ports.
You can use the auto keyword only if the port is not configured as one of these:
•
•
•
•
•
To disable 802.1X globally on the switch, use the no dot1x system-auth-control global configuration command. To disable 802.1X on a specific interface, use the no dot1x port-control interface configuration command.
Examples
This example shows how to enable 802.1X on Fast Ethernet interface 0/1:
Switch(config)# interface fastethernet0/1Switch(config-if)# dot1x port-control autoYou can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
dot1x re-authenticate
Use the dot1x re-authenticate privileged EXEC command to manually initiate a re-authentication of all 802.1X-enabled ports or the specified 802.1X-enabled port.
dot1x re-authenticate {interface interface-id}
Syntax Description
Defaults
There is no default setting.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can use this command to re-authenticate a client without waiting for the configured number of seconds between re-authentication attempts (re-authperiod) and automatic re-authentication.
Examples
This example shows how to manually re-authenticate the device connected to Fast Ethernet interface 0/1:
Switch# dot1x re-authenticate interface fastethernet0/1Related Commands
Displays 802.1X statistics, administrative status, and operational status for the switch or for the specified interface.
dot1x re-authentication
This is an obsolete command.
In past releases, the dot1x re-authentication global configuration command was used to set the amount of time between periodic re-authentication attempts.
Command History
12.1(6)EA2
This command was introduced.
12.1(14)EA1
The dot1x reauthentication interface configuration command replaced the dot1x re-authentication global configuration command.
Related Commands
dot1x reauthentication
Use the dot1x reauthentication interface configuration command to enable periodic re-authentication of the client. Use the no form of this command to return to the default setting.
dot1x reauthentication
no dot1x reauthentication
Syntax Description
This command has no arguments or keywords.
Defaults
Periodic re-authentication is disabled.
Command Modes
Interface configuration
Command History
12.1(14)EA1
This command was introduced. It replaces the dot1x re-authentication global configuration command (with the hyphen).
Usage Guidelines
You configure the amount of time between periodic re-authentication attempts by using the dot1x timeout reauth-period interface configuration command.
Examples
This example shows how to disable periodic re-authentication of the client:
Switch(config-if)# no dot1x reauthenticationThis example shows how to enable periodic re-authentication and to set the number of seconds between re-authentication attempts to 4000 seconds:
Switch(config-if)# dot1x reauthenticationSwitch(config-if)# dot1x timeout reauth-period 4000You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
Sets the number of seconds between re-authentication attempts.
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
dot1x system-auth-control
Use the dot1x system-auth-control global configuration command to enable 802.1X globally. Use the no form of this command to return to the default setting.
dot1x system-auth-control
no dot1x system-auth-control
Syntax Description
This command has no arguments or keywords.
Defaults
802.1X is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You must enable authentication, authorization, and accounting (AAA) and specify the authentication method list before enabling 802.1X globally. A method list describes the sequence and authentication methods to be queried to authenticate a user.
Examples
This example shows how to enable 802.1X globally on a switch:
Switch(config)# dot1x system-auth-controlYou can verify your settings by entering the show dot1x privileged EXEC command.
Related Commands
Displays 802.1X statistics, administrative status, and operational status for the switch or for the specified interface.
dot1x timeout
Use the dot1x timeout interface configuration command to set the 802.1X timers. Use the no form of this command to return to the default setting.
dot1x timeout {quiet-period seconds | reauth-period seconds | server-timeout seconds | supp-timeout seconds | tx-period seconds}
no dot1x timeout {quiet-period | reauth-period | server-timeout | supp-timeout | tx-period}
Syntax Description
Defaults
These are the defaults:
quiet-period is 60 seconds.
reauth-period is 3600 seconds.
server-timeout is 30 seconds.
supp-timeout is 30 seconds.
tx-period is 30 seconds.
Command Modes
Interface configuration
Command History
12.1(6)EA2
This command was introduced.
12.1(14)EA1
The supp-timeout and server-timeout keywords were added, and the command was changed to the interface configuration mode.
Usage Guidelines
You should change the default values only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
The dot1x timeout reauth-period interface configuration command affects the behavior of the switch only if you have enabled periodic re-authentication by using the dot1x reauthentication interface configuration command.
During the quiet period, the switch does not accept or initiate any authentication requests. If you want to provide a faster response time to the user, enter a smaller number than the default.
Examples
This example shows how to enable periodic re-authentication and to set the number of seconds between re-authentication attempts to 4000 seconds:
Switch(config-if)# dot1x reauthenticationSwitch(config-if)# dot1x timeout reauth-period 4000This example shows how to set the quiet time on the switch to 30 seconds:
Switch(config-if)# dot1x timeout quiet-period 30This example shows how to set 60 as the number of seconds to wait for a response to an EAP-request/identity frame from the client before re-transmitting the request:
Switch(config-if)# dot1x timeout tx-period 60This example shows how to set the switch-to-client retransmission time for the EAP request frame to 25 seconds:
Switch(config-if)# dot1x timeout supp-timeout 25This example shows how to set the switch-to-authentication server retransmission time to 25 seconds:
Switch(config)# dot1x timeout server-timeout 25This example shows how to return to the default re-authorization period:
Switch(config-if)# no dot1x timeout reauth-periodYou can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
Sets the maximum number of times that the switch sends an EAP-request/identity frame before restarting the authentication process.
Enables periodic re-authentication of the client.
show dot1x [interface interface-id]
Displays 802.1X status for the specified interface.
duplex
Use the duplex interface configuration command to specify the duplex mode of operation for switch ports. Use the no form of this command to return the port to its default value.
duplex {auto | full | half}
no duplex
Syntax Description
auto
Port automatically detects whether it should run in full- or half-duplex mode.
full
Port is in full-duplex mode.
half
Port is in half-duplex mode.
Defaults
For Fast Ethernet and 10/100/1000 ports, the default is auto.
For the default duplex mode of the Gigabit Interface Converter (GBIC)-module ports, refer to the documentation that came with your GBIC module.
For small, form-factor pluggable (SFP) Gigabit Ethernet ports, the default is auto.
Command Modes
Interface configuration
Command History
Usage Guidelines
Certain ports, such as GBIC module ports, can be configured to be either full duplex or half duplex. The applicability of this command depends on the device to which the switch is attached.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.
If both the speed and duplex are set to specific values, autonegotiation is disabled.
For Fast Ethernet ports, setting the port to auto has the same effect as specifying half if the attached device does not autonegotiate the duplex parameter.
The 100BASE-FX ports on Catalyst 2950C-24 switches do not support the duplex interface configuration command. These ports only operate in full-duplex and 100-Mbps mode.
You can configure the 10/100/1000 ports on the Catalyst 2950T-24 and Catalyst 2950T-48-SI switches to autonegotiate the duplex mode by using the duplex auto interface configuration command. You can manually set the duplex mode to full by using the duplex full command. The 10/100/1000 ports support the half keyword only when the interface speed is 10 or 100 Mbps.
On Catalyst 2950 Long-Reach Ethernet (LRE) switches, use the duplex command to configure both the MAC and LRE chipsets.
A 10/100/1000 LRE switch port autonegotiates with the device at the other end of the link for the duplex setting and then forces the duplex setting to the negotiated value. A fiber-optic connection (SFP) also autonegotiates with the device at the other end of the link but only accepts a connection at full duplex.
The duplex setting for a SFP Gigabit Ethernet port has a close relationship to the setting for speed. Fiber-optic connections are always forced to 1000 Mbps and full-duplex mode. Copper connections can run at either full- or half-duplex mode for 10 or 100 Mbps but are can only run in full-duplex mode at 1000 Mbps. When you manually set the speed and duplex settings, autonegotiation is disabled, and speed and duplex settings can cause a mismatch.
Note
Examples
This example shows how to set a Fast Ethernet port to half duplex:
Switch(config)# interface fastethernet0/11Switch(config-if)# duplex halfThis example shows how to set a Gigabit Ethernet port to full duplex:
Switch(config)# interface gigabitethernet0/1Switch(config-if)# duplex fullYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
errdisable detect cause
Use the errdisable detect global configuration command to enable error disable detection. Use the no form of this command to disable this feature.
errdisable detect cause {all | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | loopback | pagp-flap}
no errdisable detect cause {all | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | loopback | pagp-flap}
Syntax Description
Defaults
The default is all, enabled for all causes.
Command Modes
Global configuration
Command History
Usage Guidelines
A cause (dhcp-rate-limit, dtp-flap, gbic-invalid, link-flap, loopback, and pagp-flap) is the reason why 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 errdisable recovery for the cause, the interface stays in the error-disabled state until you enter the shutdown and no shutdown interface configuration commands. If you enable the recovery for a cause, the interface is brought out of the error-disabled state and allowed to retry the operation again when all the causes have timed out.
You must enter the shutdown and then the no shutdown commands to manually recover an interface from the error-disabled state.
Examples
This example shows how to enable error disable detection for the link-flap error-disable cause:
Switch(config)# errdisable detect cause link-flapYou can verify your settings by entering the show errdisable detect privileged EXEC command.
Related Commands
Configures the recovery mechanism variables.
show errdisable detect
Displays errdisable detection status.
show interfaces trunk
Displays interface status or a list of interfaces in error-disabled state.
errdisable recovery
Use the errdisable recovery global configuration command to configure the recover mechanism variables. Use the no form of this command to return to the default setting.
errdisable recovery {cause {all | bpduguard | channel-misconfig | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | loopback | pagp-flap | psecure-violation | udld}} | {interval interval}
no errdisable recovery {cause {all | bpduguard | channel-misconfig | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | loopback | pagp-flap | psecure-violation | udld}}
| {interval interval}Syntax Description
Defaults
Recovery is disabled for all causes.
The default interval is 300 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
A cause (bpduguard, channel-misconfig, dhcp-rate-limit, dtp-flap, gbic-invalid, link-flap, loopback, pagp-flap, psecure-violation, and udld) is defined as the reason why 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 errdisable recovery for the cause, the interface stays in error-disabled state until you enter a shutdown and no shutdown interface configuration command. If you enable the recovery for a cause, the interface is brought out of the error-disabled state and allowed to retry the operation again when all the causes have timed out.
Otherwise, you must enter the shutdown and then no shutdown commands to manually recover an interface from the error-disabled state.
Examples
This example shows how to enable the recovery timer for the BPDU guard error-disable cause:
Switch(config)# errdisable recovery cause bpduguardThis example shows how to set the timer to 500 seconds:
Switch(config)# errdisable recovery interval 500You can verify your settings by entering the show errdisable recovery privileged EXEC command.
Related Commands
Displays errdisable recovery timer information.
show interfaces status
Displays interface status.
flowcontrol
Use the flowcontrol interface configuration command to set the receive or send flow-control value for an interface. When flow control send is on for a device and it detects any congestion at its end, it notifies the link partner or the remote device of the congestion by sending a pause frame. When flow control receive is on for the remote device and it receives a pause frame, it stops sending any data packets. This prevents any loss of data packets during the congestion period.
Use the receive off and send off keywords to disable flow control.
flowcontrol {receive | send} {desired | off | on}
Note
Syntax Description
Defaults
The defaults for 10/100/1000, GBIC-module ports, and SFP-module ports are flowcontrol receive off and flowcontrol send desired.
Command Modes
Interface configuration
Command History
12.0(5.2)WC(1)
This command was introduced.
12.1(6)EA2
The asymmetric and symmetric keywords were replaced with the receive, send, off, on, and desired keywords.
Usage Guidelines
Use the flowcontrol command only on 10/100/1000, GBIC-module ports, and SFP-module ports.
We strongly recommend that you do not configure IEEE 802.3X flowcontrol when quality of service (QoS) is configured on the switch. Before configuring flowcontrol on an interface, make sure to disable QoS on the switch.
Note that when used with receive, the on and desired keywords have the same result.
When you use the flowcontrol command to set a port to control traffic rates during congestion, you are setting flow control on a port to one of these conditions:
•
•
•
•
•
•
Table 2-3 shows the flow control resolution achieved on local and remote ports by a combination of settings. The table assumes that for receive, using the desired keyword has the same results as using the on keyword.
Examples
This example shows how to configure the local port to not support any level of flow control by the remote port:
Switch(config-if)# flowcontrol receive offSwitch(config-if)# flowcontrol send offYou can verify your settings by entering the show interfaces counters privileged EXEC command.
Related Commands
Displays the interface settings on a switch, including input and output flow control.
hw-module slot
Use the hw-module slot privileged EXEC command to perform firmware upgrades on Long-Reach Ethernet (LRE) systems.
hw-module slot module-slot-number upgrade lre [force] [{local ctrlr-unit-number | remote interface-id}]
This command is available only on Catalyst 2950 LRE switches.
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the hw-module slot command to start an LRE upgrade. You can start an LRE upgrade by using one of these methods:
•
•
•
You can use the force keyword to upgrade an LRE binary on a local LRE controller or a remote LRE CPE device, even though the device is already running the version of the desired LRE binary. The default behavior is to not upgrade LRE binaries that are already up to date.
During an upgrade, users on the LRE links being upgraded experience a temporary disruption of Ethernet connectivity. All LRE local and remote upgrades run concurrently and take 3 to 6 minutes to complete.
The command-line interface (CLI) is available while an LRE upgrade is in progress.
Once started, an LRE upgrade can only be stopped by physically changing the remote CPE device or by reloading the software on the Ethernet switch.
In most cases, configuration for upgrades is not necessary.
Examples
This example shows how to start a system-wide LRE upgrade:
Switch# hw-module slot 0 upgrade lreYou are about to start an LRE upgrade on all LRE interfaces.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:Starting remote upgrade on CPE Lo0/1.Starting remote upgrade on CPE Lo0/2Starting remote upgrade on CPE Lo0/3Starting remote upgrade on CPE Lo0/4Starting remote upgrade on CPE Lo0/5Starting remote upgrade on CPE Lo0/6Starting remote upgrade on CPE Lo0/7Starting remote upgrade on CPE Lo0/8Starting upgrade on local controller LongReachEthernet 0Starting remote upgrade on CPE Lo0/9<output truncated>Starting remote upgrade on CPE Lo0/23Starting remote upgrade on CPE Lo0/24Starting upgrade on local controller LongReachEthernet 2This example shows how to start an LRE upgrade on a single LRE controller in a switch. Specifying the interface-id as longreachethernet 0 causes an LRE upgrade to run on controller 0 in the switch.
Switch# hw-module slot 0 upgrade lre local longreachethernet 0You are about to start an LRE upgrade on local controller LongReachEthernet 0.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:
