-
Catalyst 3750 Metro Switch Command Reference, 12.2(35)SE
-
Index
-
Preface
-
Using the Command-Line Interface
-
Catalyst 3750 Metro Switch Cisco IOS Commands - aaa through renew ip dhcp snooping database
-
Catalyst 3750 Metro Switch Cisco IOS Commands - rmon collection stats through show vtp
-
Catalyst 3750 Metro Switch Cisco IOS Commands - shutdown through xconnect
-
Catalyst 3750 Metro Switch Boot Loader Commands
-
Catalyst 3750 Metro Switch Cisco IOS Commands Debug Commands
-
Catalyst 3750 Metro Switch Cisco IOS Commands Show Platform Commands
-
Feedback
Table Of Contents
Catalyst 3750 Metro Switch Cisco IOS Commands
clear ip arp inspection statistics
clear ip dhcp snooping database
clear l2protocol-tunnel counters
clear mac address-table move update
clear spanning-tree detected-protocols
deny (ARP access-list configuration)
ip arp inspection vlan logging
ip dhcp snooping information option
ip dhcp snooping information option allowed-untrusted
ip dhcp snooping information option format remote-id
ip dhcp snooping vlan information option format-type circuit-id string
ip igmp snooping report-suppression
ip igmp snooping vlan immediate-leave
ip vrf (interface configuration)
mac address-table learning vlan
mac address-table notification
match (access-map configuration)
match (class-map configuration)
mls qos queue-set output buffers
mls qos queue-set output threshold
mls qos srr-queue input bandwidth
mls qos srr-queue input buffers
mls qos srr-queue input cos-map
mls qos srr-queue input dscp-map
mls qos srr-queue input priority-queue
mls qos srr-queue input threshold
mls qos srr-queue output cos-map
mls qos srr-queue output dscp-map
permit (ARP access-list configuration)
random-detect exponential-weighting-constant
renew ip dhcp snooping database
Catalyst 3750 Metro Switch Cisco IOS Commands
aaa accounting dot1x
Use the aaa accounting dot1x global configuration command to enable authentication, authorization, and accounting (AAA) accounting and to create method lists defining specific accounting methods on a per-line or per-interface basis for 802.1x sessions. Use the no form of this command to disable 802.1x accounting.
aaa accounting dot1x {name | default} start-stop {broadcast group {name | radius | tacacs+} [group {name | radius | tacacs+} ... ] | group {name | radius | tacacs+} [group {name | radius | tacacs+} ... ]}
no aaa accounting dot1x {name | default}
Syntax Description
Defaults
AAA accounting is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command requires access to a RADIUS server.
Note
We recommend that you enter the dot1x reauthentication interface configuration command before configuring 802.1x RADIUS accounting on an interface.
Examples
This example shows how to configure 802.1x accounting:
Switch(config)# aaa accounting dot1x default start-stop group radiusSwitch(config)#
Note
Related Commands
Specifies one or more AAA methods for use on interfaces running 802.1x.
Enables or disables periodic reauthentication.
dot1x timeout reauth-period
Sets the number of seconds between re-authentication attempts.
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 ports 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
Note
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 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
action
Use the action access map configuration command to set the action for the VLAN access map entry. Use the no form of this command to set the action to the default value, which is to forward.
action {drop | forward}
no action
Syntax Description
drop
Drop the packet when the specified conditions are matched.
forward
Forward the packet when the specified conditions are matched.
Defaults
The default action is to forward packets.
Command Modes
Access-map configuration
Command History
Usage Guidelines
You enter access-map configuration mode by using the vlan access-map global configuration command.
If the action is drop, you should define the access map, including configuring any access control list (ACL) names in match clauses, before applying the map to a VLAN, or all packets could be dropped.
In access map configuration mode, use the match access map configuration command to define the match conditions for a VLAN map. Use the action command to set the action that occurs when a packet matches the conditions.
The drop and forward parameters are not used in the no form of the command.
Examples
This example shows how to identify and apply a VLAN access map vmap4 to VLANs 5 and 6 that causes the VLAN to forward an IP packet if the packet matches the conditions defined in access list al2:
Switch(config)# vlan access-map vmap4Switch(config-access-map)# match ip address al2Switch(config-access-map)# action forwardSwitch(config-access-map)# exitSwitch(config)# vlan filter vmap4 vlan-list 5-6You can verify your settings by entering the show vlan access-map privileged EXEC command.
Related Commands
archive download-sw
Use the archive download-sw privileged EXEC command to download a new image to the switch and to overwrite or keep the existing image.
archive download-sw {/force-reload | /imageonly | /leave-old-sw | /no-set-boot | /overwrite | /reload | /safe} source-url
Syntax Description
Note
Defaults
The current software image is not overwritten with the downloaded image.
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
Using the /safe or /leave-old-sw option can cause the new image download to fail if there is insufficient flash memory. If leaving the software in place prevents the new image from fitting in flash memory due to space constraints, an error results.
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" section.
Use the /overwrite option to overwrite the image on the flash device with the downloaded one.
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.
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 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, list files in a tar file, or 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
None
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.10.30.
Switch# archive tar /create tftp:172.20.10.30/saved.tar flash:/new-configsThis example shows how to display the contents of the image-tv0-m.tar file that is in flash memory. The contents of the tar file are displayed on the screen.
Switch# archive tar /table flash:image-tv0-m.tarinfo (219 bytes)image-tv0-mz-121/ (directory)image-tv0-mz-121/html/ (directory)image-tv0-mz-121/html/foo.html (0 bytes)image-tv0-mz-121/image-tv0-mz-121.bin (610856 bytes)image-tv0-mz-121/info (219 bytes)info.ver (219 bytes)This example shows how to display only the image-tv0-mz-121/html directory and its contents:
Switch# archive tar /table flash:image-tv0-m.tar image-tv0-mz-121/htmlimage-tv0-mz-121/html/ (directory)image-tv0-mz-121/html/foo.html (0 bytes)This example shows how to extract the contents of a tar file on the TFTP server at 172.20.10.30. This command extracts just the new-configs directory into the root directory on the local flash file system. The remaining files in the saved.tar file are ignored.
Switch# archive tar /xtract tftp:/172.20.10.30/saved.tar flash:/ new-configsRelated 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 switch image to a server.
archive upload-sw destination-url
Syntax Description
Defaults
Uploads the currently running image from the flash: file system.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The files are uploaded in this sequence: the Cisco IOS image and the info file. 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 the switch.
Creates a tar file, lists the files in a tar file, or extracts the files from a tar file.
arp access-list
Use the arp access-list global configuration command on the switch stack or on a standalone switch to define an Address Resolution Protocol (ARP) access control list (ACL) or to add clauses to the end of a previously defined list. Use the no form of this command to delete the specified ARP access list.
arp access-list acl-name
no arp access-list acl-name
This command is available only if your switch is running the enhanced multilayer image (EMI).
Syntax Description
Defaults
No ARP access lists are defined.
Command Modes
Global configuration
Command History
Usage Guidelines
After entering the arp access-list command, you enter ARP access-list configuration mode, and these configuration commands are available:
•
•
•
•
•
Use the permit and deny access-list configuration commands to forward and to drop ARP packets based on the specified matching criteria.
When the ARP ACL is defined, you can apply it to a VLAN by using the ip arp inspection filter vlan global configuration command. ARP packets containing only IP-to-MAC address bindings are compared to the ACL. All other types of packets are bridged in the ingress VLAN without validation. If the ACL permits a packet, the switch forwards it. If the ACL denies a packet because of an explicit deny statement, the switch drops the packet. If the ACL denies a packet because of an implicit deny statement, the switch compares the packet to the list of DHCP bindings (unless the ACL is static, which means that packets are not compared to the bindings).
Examples
This example shows how to define an ARP access list and to permit both ARP requests and ARP responses from a host with an IP address of 1.1.1.1 and a MAC address of 0000.0000.abcd:
Switch(config)# arp access-list static-hostsSwitch(config-arp-nacl)# permit ip host 1.1.1.1 mac host 00001.0000.abcdSwitch(config-arp-nacl)# endYou can verify your settings by entering the show arp access-list privileged EXEC command.
Related Commands
auto qos voip
Use the auto qos voip interface configuration command to automatically configure quality of service (QoS) for voice over IP (VoIP) within a QoS domain. Use the no form of this command to return to the default setting.
auto qos voip {cisco-phone | cisco-softphone | trust}
no auto qos voip [cisco-phone | cisco-softphone | trust]
Syntax Description
Defaults
Auto-QoS is disabled on the port.
When auto-QoS is enabled, it uses the ingress packet label to categorize traffic, to assign packet labels, and to configure the ingress queues and egress queue-sets. Table 2-1 shows the default settings.
Table 2-1 Traffic Types, Packet Labels, and Queues
TrafficDSCP3
46
24, 26
48
56
34
-
CoS4
5
3
6
7
3
-
CoS-to-Ingress Queue Map
2, 3, 4, 5, 6, 7 (queue 2)
0, 1 (queue 1)
CoS-to-Egress Queue Map
5 (queue 1)
3, 6, 7 (queue 2)
4 (queue 3)
2
(queue 3)0, 1 (queue 4)
1 STP = Spanning Tree Protocol
2 BPDU = bridge protocol data unit
3 DSCP = Differentiated Services Code Point
4 CoS = class of service
Table 2-2 shows the generated auto-QoS configuration for the ingress queues.
Table 2-2 Auto-QoS Configuration for the Ingress Queues
SRR1 shared
1
0, 1
81 percent
67 percent
Priority
2
2, 3, 4, 5, 6, 7
19 percent
33 percent
1 SRR = shaped round robin. Ingress queues support shared mode only.
Table 2-3 shows the generated auto-QoS configuration for the egress queue-set.
Table 2-3 Auto-QoS Configuration for the Egress Queue-Set
Priority (shaped)
1
5
10 percent
10 percent
SRR shared
2
3, 6, 7
10 percent
10 percent
SRR shared
3
2, 4
60 percent
26 percent
SRR shared
4
0, 1
20 percent
54 percent
1 On an enhanced-services (ES) port, the srr-queue bandwidth shape interface configuration command is not part of the generated auto qos voip command list.
Command Modes
Interface configuration
Command History
12.1(14)AX
This command was introduced.
12.2(25)EY
The cisco-softphone keyword was added, and the generated auto-QoS configuration changed.
Usage Guidelines
Use this command to configure the QoS appropriate for VoIP traffic within the QoS domain. The QoS domain includes the switch, the interior of the network, and edge devices that can classify inbound traffic for QoS.
In releases earlier than Cisco IOS Release 12.2(25)EY, auto-QoS configures the switch only for VoIP with Cisco IP Phones on switch ports.
In Cisco IOS Release 12.2(25)EY or later, auto-QoS configures the switch for VoIP with Cisco IP Phones on switch and routed ports and for VoIP with devices running the Cisco SoftPhone application. These releases support only Cisco IP SoftPhone Version 1.3(3) or later. Connected devices must use Cisco Call Manager Version 4 or later.
To take advantage of the auto-QoS defaults, you should enable auto-QoS before you configure other QoS commands. You can fine-tune the auto-QoS configuration after you enable auto-QoS.
Note
If this is the first port on which you have enabled auto-QoS, the auto-QoS-generated global configuration commands are executed, followed by the interface configuration commands. If you enable auto-QoS on another port, only the auto-QoS-generated interface configuration commands for that port are executed.
When you enable the auto-QoS feature on the first port, these automatic actions occur:
•
•
•
•
You can enable auto-QoS on static, dynamic-access, voice VLAN access, and trunk ports. When enabling auto-QoS with a Cisco IP Phone on a routed port, you must assign a static IP address to the IP phone.
To display the QoS commands that are automatically generated when auto-QoS is enabled or disabled, enable debugging before you enable auto-QoS. Use the debug auto qos privileged EXEC command to enable auto-QoS debugging. For more information, see the debug auto qos command.
Note
After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS in its name. If you need to modify the policy map or aggregate policer, make a copy of it, and change the copied policy map or policer. To use the new policy map instead of the generated one, remove the generated policy map from the interface, and apply the new policy map.
To disable auto-QoS on a port, use the no auto qos voip interface configuration command. Only the auto-QoS-generated interface configuration commands for this port are removed. If this is the last port on which auto-QoS is enabled and you enter the no auto qos voip command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other ports affected by the global configuration). You can use the no mls qos global configuration command to disable the auto-QoS-generated global configuration commands. With QoS disabled, there is no concept of trusted or untrusted ports because the packets are not modified (the CoS, DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing).
Examples
This example shows how to enable auto-QoS on a port and to trust the QoS labels received in inbound packets when the switch or router connected to a port is a trusted device:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# auto qos voip trustYou can verify your settings by entering the show auto qos interface interface-id privileged EXEC command.
Related Commands
Enables debugging of the auto-QoS feature.
Defines the default CoS value of a port or assigns the default CoS to all inbound packets on the port.
mls qos map {cos-dscp dscp1 ... dscp8 | dscp-cos dscp-list to cos}
Defines the CoS-to-DSCP map or the DSCP-to-CoS map.
Allocates buffers to a queue-set.
Assigns SRR weights to an ingress queue.
Allocates the buffers between the ingress queues.
Maps CoS values to an ingress queue or maps CoS values to a queue and to a threshold ID.
Maps DSCP values to an ingress queue or maps DSCP values to a queue and to a threshold ID.
Configures the ingress priority queue and guarantees bandwidth.
Maps CoS values to an egress queue or maps CoS values to a queue and to a threshold ID.
Maps DSCP values to an egress queue or maps DSCP values to a queue and to a threshold ID.
Configures the port trust state.
Maps a port to a queue-set.
Displays the initial configuration that is generated by the auto-QoS feature.
Displays QoS information at the port level.
Assigns the shaped weights and enables bandwidth shaping on the four egress queues mapped to a standard port.
Assigns the shared weights and enables bandwidth sharing on the four egress queues mapped to a port.
bandwidth
Use the bandwidth policy-map class configuration command to specify or modify the minimum bandwidth provided to a class belonging to a hierarchical policy map attached to an enhanced-services (ES) port. Use the no form of this command to return to the default setting.
bandwidth {bandwidth-kbps | percent percent}
no bandwidth
Syntax Description
Defaults
No bandwidth is specified.
Command Modes
Policy-map class configuration
Command History
12.1(14)AX
This command was introduced.
12.2(25)EY
Hierarchical service policies can be applied to inbound traffic received on an ES port.
Usage Guidelines
Use the bandwidth command only in a hierarchical policy map attached to an ES port. This command is not valid for the class-default class in a physical-level policy map.
Use the bandwidth command when you configure a policy map for a class defined by the class-map global configuration command. The bandwidth command specifies the minimum bandwidth for traffic in that class when there is traffic congestion in the switch. If the switch is not congested, the class receives more bandwidth than you specify with this command. Class-based weighted fair queueing (CBWFQ) derives the weight for packets belonging to the class from the bandwidth allocated to the class. CBWFQ then uses the weight to ensure that the queue for the class is serviced fairly.
Note
These restrictions apply to the bandwidth command:
•
•
•
•
•
•
When you configure the bandwidth command in a class policy, you must also configure the bandwidth or shape policy-map class configuration command in the parent VLAN-level policy.
You must configure the bandwidth or the shape policy-map class configuration command before you configure either the queue-limit or the random-detect policy-map class configuration command in a class policy.
You cannot use the bandwidth, queue-limit, random-detect, and the shape policy-map class configuration commands with the priority policy-map class configuration command in the same class within the same policy map. However, you can use these commands in the same policy map.
When you use the service-policy interface configuration command to attach the policy map containing class configurations to an ES port, the switch determines the available bandwidth.
Examples
This example shows how to set the minimum bandwidth to 2000 kbps for a class called silver-class. The class already exists in the switch configuration.
Switch(config)# policy-map polmap6Switch(config-pmap)# class silver-classSwitch(config-pmap-c)# bandwidth 2000This example shows how to guarantee 30 percent of the bandwidth for class1 and 25 percent of the bandwidth for class2 when CBWFQ is configured. A policy map with two classes is created and is then attached to an ES port.
Switch(config)# policy-map policy1Switch(config-pmap)# class class1Switch(config-pmap-c)# bandwidth percent 50Switch(config-pmap-c)# exitSwitch(config-pmap)# class class2Switch(config-pmap-c)# bandwidth percent 25Switch(config-pmap-c)# exitSwitch(config-pmap)# endSwitch(config)# interface gigabitethernet1/1/1Switch(config-if)# service-policy input policy1This example shows how bandwidth is guaranteed if low-latency queueing (LLQ) and CBWFQ are configured. In this example, LLQ is enabled in a class called voice1.
Switch(config)# policy-map policy1Switch(config-pmap)# class class1Switch(config-pmap-c)# bandwidth percent 50Switch(config-pmap-c)# exitSwitch(config-pmap)# class class2Switch(config-pmap-c)# bandwidth percent 25Switch(config-pmap-c)# exitSwitch(config-pmap)# class voice1Switch(config-pmap-c)# prioritySwitch(config-pmap-c)# exitSwitch(config-pmap)# endSwitch(config)# interface gigabitethernet1/1/1Switch(config-if)# service-policy output policy1You can verify your settings by entering the show policy-map privileged EXEC command.
Related Commands
boot boothlpr
Use the boot boothlpr global configuration command to load a special image, which when loaded into memory, can load a second image into memory and launch 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
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 "Catalyst 3750 Metro Switch Boot Loader Commands."
Related Commands
boot config-file
Use the boot config-file global configuration command to specify the filename that 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
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 "Catalyst 3750 Metro Switch Boot Loader Commands."
Related Commands
boot enable-break
Use the boot enable-break global configuration command to enable interrupting the automatic boot process. Use the no form of this command to return to the default setting.
boot enable-break
no boot enable-break
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled. The automatic boot 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 "Catalyst 3750 Metro Switch 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 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
Syntax Description
Defaults
No helper files are loaded.
Command Modes
Global configuration
Command History
Usage Guidelines
This variable is used only for internal development and testing.
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER environment variable. For more information, see "Catalyst 3750 Metro Switch 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 helper image. If this is not set, the file specified by the CONFIG_FILE environment variable is used by all versions of software that are loaded. 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
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
This variable is used only for internal development and testing.
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER_CONFIG_FILE environment variable. For more information, see "Catalyst 3750 Metro Switch Boot Loader Commands."
Related Commands
boot manual
Use the boot manual global configuration command to enable manually booting the switch during the next boot cycle. Use the no form of this command to return to the default setting.
boot manual
no boot manual
Syntax Description
This command has no arguments or keywords.
Defaults
Manual booting is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The next time you reboot the system, the switch is in boot loader mode, which is shown by the switch: prompt. To boot 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 "Catalyst 3750 Metro Switch Boot Loader Commands."
Related Commands
boot private-config-file
Use the boot private-config-file global configuration command to specify the filename that 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.
Command Modes
Global configuration
Command History
Usage Guidelines
Filenames are case sensitive.
Examples
This example shows how to specify the name of the private configuration file to be pconfig:
Switch(config)# boot private-config-file pconfigRelated Commands
boot system
Use the boot system global configuration command to specify the image to load during the next boot cycle. Use the no form of this command to return to the default setting.
boot system filesystem:/file-url ...
no boot system
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 boot 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 continuing the 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 never 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 "Catalyst 3750 Metro Switch Boot Loader Commands."
Related Commands
channel-group
Use the channel-group interface configuration command to assign a port to an EtherChannel group and to enable an EtherChannel mode. Use the no form of this command to remove a port from an EtherChannel group.
channel-group channel-group-number mode {active | {auto [non-silent]} | {desirable [non-silent]} | on | passive}
no channel-group
PAgP modes:
channel-group channel-group-number mode {{auto [non-silent]} | {desirable [non-silent}}LACP modes:
channel-group channel-group-number mode {active | passive}On mode:
channel-group channel-group-number mode onSyntax Description
Defaults
No channel groups are assigned.
No mode is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
For Layer 2 EtherChannels, you do not have to create a port-channel first by using the interface port-channel global configuration command before assigning a physical port to a channel group. Instead, you can use the channel-group interface configuration command. It automatically creates the port-channel when the channel group gets its first physical port if the logical interface is not already created. If you create the port-channel first, the channel-group-number can be the same as the port-channel-number, or you can use a new number. If you use a new number, the channel-group command dynamically creates a new port channel.
You do not have to disable the IP address that is assigned to a physical port that is part of a channel group, but we strongly recommend that you do so.
You create Layer 3 port channels by using the interface port-channel command followed by the no switchport interface configuration command. You should manually configure the port-channel logical interface before putting the interface into the channel group.
After you configure an EtherChannel, configuration changes that you make on the port-channel apply to all the physical ports assigned to the port-channel. Configuration changes applied to the physical port affect only the port where you apply the configuration. To change the parameters of all ports in an EtherChannel, apply configuration commands to the port-channel, for example, spanning-tree commands or commands to configure a Layer 2 EtherChannel as a trunk.
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 port to a channel group, and to use the port for transmission. Both ends of the link cannot be set to silent.
With the on mode, a usable EtherChannel exists only when a port group in the on mode is connected to another port group in the on mode.
Caution
Note
Do not configure an EtherChannel in both the PAgP and LACP modes. EtherChannel groups running PAgP and LACP can coexist on the same switch. Individual EtherChannel groups can run either PAgP or LACP, but they cannot interoperate.
If you set the protocol by using the channel-protocol interface configuration command, the setting is not overridden by the channel-group interface configuration command
Do not configure a port that is an active member of an EtherChannel as an 802.1x port. If 802.1x is enabled on a not-yet active port of an EtherChannel, the port does not join the EtherChannel.
Note
Do not configure a secure port as part of an EtherChannel or an EtherChannel port as a secure port.
For a complete list of configuration guidelines, see the "Configuring EtherChannels" chapter in the software guide for this release.
Caution
Examples
This example shows how to configure EtherChannel. It assigns ports as static-access ports in VLAN 10 to channel 5 with the PAgP mode desirable.
Switch# configure terminalSwitch(config)# interface range fastethernet1/0/4 -5Switch(config-if-range)# switchport mode accessSwitch(config-if-range)# switchport access vlan 10Switch(config-if-range)# channel-group 5 mode desirableSwitch(config-if-range)# endThis example shows how to configure EtherChannel. It assigns ports as static-access ports in VLAN 10 to channel 5 with the LACP mode active.
Switch# configure terminalSwitch(config)# interface range fastethernet1/0/4 -5Switch(config-if-range)# switchport mode accessSwitch(config-if-range)# switchport access vlan 10Switch(config-if-range)# channel-group 5 mode activeSwitch(config-if-range)# endYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
channel-protocol
Use the channel-protocol interface configuration command to restrict the protocol used on a port to manage channeling. Use the no form of this command to return to the default setting.
channel-protocol {lacp | pagp}
no channel-protocol
Syntax Description
lacp
Configure an EtherChannel with the Link Aggregation Control Protocol (LACP).
pagp
Configure an EtherChannel with the Port Aggregation Protocol (PAgP).
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. If you set the protocol by using the channel-protocol command, the setting is not overridden by the channel-group interface configuration command.
You must use the channel-group interface configuration command to configure the EtherChannel parameters. The channel-group command also can set the mode for the EtherChannel.
You cannot enable both the PAgP and LACP modes on an EtherChannel group.
PAgP and LACP are not compatible; both ends of a channel must use the same protocol.
Examples
This example shows how to specify LACP as the protocol that manages the EtherChannel:
Switch(config-if)# channel-protocol lacpYou can verify your settings by entering the show etherchannel [channel-group-number] protocol privileged EXEC command.
Related Commands
Assigns an Ethernet port to an EtherChannel group.
show etherchannel protocol
Displays protocol information the EtherChannel.
class
Use the class policy-map configuration command to specify the name of the class whose traffic policy you want to create or change. Use the no form of this command to delete an existing class from a policy map.
class class-name
no class class-name
Syntax Description
Defaults
No classes are defined.
Command Modes
Policy-map configuration
Command History
Usage Guidelines
Before using the class command, you must create a class map for matching packets to the class by using the class-map global configuration command. You also must use the policy-map global configuration command to identify the policy map and to enter policy-map configuration mode. After specifying a policy map, you can configure a traffic policy for new classes or modify a traffic policy for any existing classes in that policy map. The class name that you specify with the class command in the policy map ties the characteristics for that class—that is, its policy—to the class map and its match criteria, as configured through the class-map global configuration command. You attach the policy map to a port by using the service-policy interface configuration command.
After you enter the class command, the switch enters policy-map class configuration mode, and these configuration commands are available:
•
•
•
•
•
•
•
•
•
•
•
The switch supports up to eight classes, including the default class, in a policy map. Packets that fail to meet any of the matching criteria are classified as members of the default traffic class. You configure the default traffic class by specifying class-default as the class name in the class policy-map class configuration command. You can manipulate the default traffic class (for example, set policies to police or to shape it) just like any other traffic class, but you cannot delete it.
Within a policy map, the class-default applies to all traffic that is not explicitly matched within the policy map but that does match the parent policy. If no parent policy is configured, the parent policy represents the physical port. In the physical-level policy map, class-default is the only class that can be configured.
In a hierarchical policy map attached to an ES port, you define a class policy to use either tail drop or WRED packet drop by using either the queue-limit policy-map class configuration command or the random-detect policy-map class configuration command, respectively. You cannot use the queue-limit and random-detect commands in the same class policy, but they can be used in two class policies in the same policy map.
In a hierarchical policy map attached to an ES port, you must configure the bandwidth or the shape policy-map class configuration command before you configure either the queue-limit or the random-detect policy-map class configuration command in a class policy.
When you configure a policy for a class, specify its bandwidth, and attach the policy map to an ES port, class-based weighted fair queueing (CBWFQ) determines if the bandwidth requirement of the class can be satisfied. If so, CBWFQ creates the necessary internal data structures to maintain the state for the class and allocates a queue for it. If CBWFQ decides that the bandwidth requirement for the class cannot be satisfied, an error message appears, and the policy is not attached. When a class is removed, available bandwidth for the port is incremented by the amount previously allocated to the class.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
Examples
This example shows how to create a policy map called policy1. When attached to an ingress port, the policy matches all the inbound traffic defined in class1, sets the IP DSCP to 10, and polices the traffic at an average rate of 1 Mbps and bursts of 20 KB. Traffic exceeding the profile is marked down to a Traffic exceeding the profile is marked down to a DSCP value obtained from the policed-DSCP map and then sent.
Switch(config)# class-map class1Switch(config-cmap)# exitSwitch(config)# policy-map policy1Switch(config-pmap)# class class1Switch(config-pmap-c)# set ip dscp 10Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmitSwitch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# interface fastethernet1/0/4Switch(config-if)# service-policy input policy1This example configures two class policies included in the egress policy map called policy1. Class1 specifies a policy for 802.1Q tunneling traffic that matches packets based on the outer VLAN ID (VLAN 2) and the inner VLAN IDs (3 to 8).
Switch(config)# class-map match-all class1Switch(config-cmap)# match vlan 2Switch(config-cmap)# match vlan inner 3 - 8Switch(config-cmap)# exitSwitch(config)# policy-map policy1Switch(config-pmap)# class class1Switch(config-pmap-c)# bandwidth 2000Switch(config-pmap-c)# queue-limit 40Switch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# interface gigabitethernet1/1/1Switch(config-if)# service-policy output policy1For class1, a minimum of 2000 kbps of bandwidth is expected to be delivered to this class in the event of congestion. The queue reserved for this class can contain 40 packets before tail drop occurs.
This example shows how to shape the default class. This configuration associates a class-level policy map with a VLAN-level policy map and then associates the VLAN-level policy map with a physical-level policy map.
Switch(config)# class-map my-classSwitch(config-cmap)# match ip precedence 1Switch(config-cmap)# exitSwitch(config)# class-map my-logical-classSwitch(config-cmap)# match vlan 5Switch(config-cmap)# exitSwitch(config)# policy-map my-class-policySwitch(config-pmap)# class my-classSwitch(config-pmap-c)# set ip precedence 2Switch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# policy-map my-logical-policySwitch(config-pmap)# class my-logical-classSwitch(config-pmap-c)# shape average 400000000Switch(config-pmap-c)# service-policy my-class-policySwitch(config-pmap-c)# exitSwitch(config-pmap)# exitSwitch(config)# policy-map my-physical-policySwitch(config-pmap)# class class-defaultSwitch(config-pmap-c)# shape average 500000000Switch(config-pmap-c)# service-policy my-logical-policyThis example shows how to create a hierarchical class-level policy map with two traffic classes. One of the classes has a class-level classification and a two-rate policer, and the other is the default traffic class. Packets that fail to meet the matching criteria are classified as members of the default traffic class, and the IP precedence in this traffic is reset to 0.
Switch(config)# class-map match-all classprece1Switch(config-cmap)# match ip precedence 1Switch(config-cmap)# exitSwitch-config)# policy-map precedencepoliceSwitch(config-pmap)# class classprece1Switch(config-pmap-c)# police cir 100000000 pir 200000000 conform-action set-prec-transmit 2 exceed-action set-prec-transmit 3 violate-action set-prec-transmit 4Switch(config-pmap-c)# exitSwitch(config-pmap)# class class-defaultSwitch(config-pmap-c)# set ip precedence 0In the previous hierarchical QoS example, the first traffic class has only one match statement. However, hierarchical policy maps can support multiple match statements.
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 [match-all | match-any] class-map-name
no class-map [match-all | match-any] class-map-name
Syntax Description
Defaults
No class maps are defined.
If neither the match-all nor the match-any keyword is specified, the default is match-all.
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. Packets are checked against the match criteria configured for a class map to decide if the packet belongs to that class. If a packet matches the specified criteria, the packet is considered a member of the class and is forwarded according to the quality of service (QoS) specifications set in the traffic policy.
You can create up to 4093 class maps.
After you enter the class-map command, the switch enters class-map configuration mode, and these configuration commands are available:
•
•
•
•
•
Only one access control list (ACL) can be configured in a class map. The ACL can have multiple access control entries (ACEs). Class maps that contain ACLs are not supported in an egress policy attached to an enhanced-services (ES) port or in a hierarchical ingress policy attached to an ES port.
Examples
This example shows how to configure the class map called class1 with one match criterion, which is an access list called 103:
Switch(config)# access-list 103 permit any any dscp 10Switch(config)# class-map class1Switch(config-cmap)# match access-group 103Switch(config-cmap)# exitThis example shows how to delete the class1 class map:
Switch(config)# no class-map class1You can verify your settings by entering the show class-map privileged EXEC command.
Related Commands
clear ip arp inspection log
Use the clear ip arp inspection log privileged EXEC command on the switch stack or on a standalone switch to clear the dynamic Address Resolution Protocol (ARP) inspection log buffer.
clear ip arp inspection log
This command is available only if your switch is running the enhanced multilayer image (EMI).
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 contents of the log buffer:
Switch# clear ip arp inspection logYou can verify that the log was cleared by entering the show ip arp inspection log privileged command.
Related Commands
clear ip arp inspection statistics
Use the clear ip arp inspection statistics privileged EXEC command on the switch stack or on a standalone switch to clear the dynamic Address Resolution Protocol (ARP) inspection statistics.
clear ip arp inspection statistics [vlan vlan-range]
This command is available only if your switch is running the enhanced multilayer image (EMI).
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear the statistics for VLAN 1:
Switch# clear ip arp inspection statistics vlan 1You can verify that the statistics were deleted by entering the show ip arp inspection statistics vlan 1 privileged EXEC command.
Related Commands
show ip arp inspection statistics
Displays statistics for forwarded, dropped, MAC validation failure, and IP validation failure packets for all VLANs or the specified VLAN.
clear ip dhcp snooping database
Use the clear ip dhcp snooping database privileged EXEC command to clear the DHCP binding database agent statistics.
clear ip dhcp snooping database statistics
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When you enter the clear ip dhcp snooping database statistics command, the switch does not update the entries in the binding database and in the binding file before clearing the statistics.
Examples
This example shows how to clear the DHCP snooping binding database agent statistics:
Switch# clear ip dhcp snooping database statisticsYou can verify that the statistics were cleared by entering the show ip dhcp snooping database privileged EXEC command.
Related Commands
Enables DHCP snooping on a VLAN.
Configures the DHCP snooping binding database agent or the binding file.
Displays the status of DHCP snooping database agent.
clear l2protocol-tunnel counters
Use the clear l2protocol-tunnel counters privileged EXEC command to clear the protocol counters in protocol tunnel ports.
clear l2protocol-tunnel counters [interface-id]
Syntax Description
interface-id
(Optional) Specify interface for which protocol counters are to be cleared. The interface can be a physical interface or a port channel.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear protocol tunnel counters on the switch or on the specified interface.
Examples
This example shows how to clear Layer 2 protocol tunnel counters on a port:
Switch # clear l2protocol-tunnel counters gigabitethernet1/0/2You can verify that the information was deleted by entering the show l2protocol-tunnel privileged EXEC command.
Related Commands
clear lacp
Use the clear lacp privileged EXEC command to clear Link Aggregation Control Protocol (LACP) channel-group counters.
clear lacp {channel-group-number counters | counters}
Syntax Description
channel-group-number
(Optional) Channel group number. The range is 1 to 12.
counters
Clear traffic counters.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can clear all counters by using the clear lacp counters command, or you can clear only the counters for the specified channel group by using the clear lacp channel-group-number counters command.
Examples
This example shows how to clear all channel-group information:
Switch# clear lacp countersThis example shows how to clear LACP traffic counters for group 4:
Switch# clear lacp 4 countersYou can verify that the information was deleted by entering the show lacp counters or the show lacp 4 counters privileged EXEC command.
Related Commands
clear mac address-table
Use the clear mac address-table privileged EXEC command to delete from the MAC address table all dynamic MAC addresses, a specific dynamic MAC 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}
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to remove a specific MAC address from the dynamic 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 mac address-table move update
Use the clear mac address-table move update privileged EXEC command to clear the mac address-table-move update-related counters.
clear mac address-table move update
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 mac address-table move update related counters.
Switch# clear mac address-table move updateYou can verify that the information was cleared by entering the show mac address-table move update privileged EXEC command.
Related Commands
Configures MAC address-table move update on the switch.
Displays the MAC address-table move update information on the switch.
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
channel-group-number
(Optional) Channel group number. The range is 1 to 12.
counters
Clear traffic counters.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can clear all counters by using the clear pagp counters command, or you can clear only the counters for the specified channel group by using the clear pagp channel-group-number counters command.
Examples
This example shows how to clear all channel-group information:
Switch# clear pagp countersThis example shows how to clear PAgP traffic counters for group 10:
Switch# clear pagp 10 countersYou can verify that information was deleted by entering the show pagp privileged EXEC command.
Related Commands
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
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If the interface-id is not specified, spanning-tree counters are cleared for all interfaces.
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]
Syntax Description
Defaults
No default is defined.
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 interface. A multiple spanning-tree (MST) switch can also detect that an interface is at the boundary of a region when it receives a legacy BPDU, an MST BPDU (version 3) associated with a different region, or a rapid spanning-tree (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. It cannot detect 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 a port:
Switch# clear spanning-tree detected-protocols interface gigabitethernet1/0/1Related Commands
Displays spanning-tree state information.
Overrides the default link-type setting and enables rapid spanning-tree transitions to the forwarding state.
clear 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 information was deleted by entering the show vmps statistics privileged EXEC command.
Related Commands
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 information was deleted by entering the show vtp counters privileged EXEC command.
Related Commands
Displays general information about the VTP management domain, status, and counters.
cluster commander-address
You do not need to enter this command. The cluster command switch automatically provides its MAC address to cluster member switches when these switches join the cluster. The cluster member switch adds this information and other cluster information to its running configuration file. Use the no form of this global configuration command from the cluster member switch console port to remove the switch from a cluster only during debugging or recovery procedures.
cluster commander-address mac-address [member number name name vlan vlan-id]
no cluster commander-address
Syntax Description
Defaults
The switch is not a member of any cluster.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is available only on the cluster command switch.
A cluster member can have only one cluster command switch.
The cluster member switch retains the identity of the cluster command switch during a system reload by using the mac-address parameter.
You can enter the no form on a cluster member switch to remove it from the cluster during debugging or recovery procedures. You would normally use this command from the cluster member switch console port only when the member has lost communication with the cluster command switch. With normal switch configuration, we recommend that you remove cluster member switches only by entering the no cluster member n global configuration command on the cluster command switch.
When a standby cluster command switch becomes active (becomes the cluster command switch), it removes the cluster commander address line from its configuration.
Examples
This is partial sample output from the running configuration of a cluster member.
Switch(config)# show running-configuration<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
Displays the cluster status and a summary of the cluster to which the switch belongs.
cluster discovery hop-count
Use the cluster discovery hop-count global configuration command on the cluster command switch to set the hop-count limit for extended discovery of candidate switches. Use the no form of this command to return to the default setting.
cluster discovery hop-count number
no cluster discovery hop-count
Syntax Description
number
Number of hops from the cluster edge that the cluster command switch limits the discovery of candidates. The range is 1 to 7.
Defaults
The hop count is set to 3.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is available only on the cluster command switch. This command does not operate on cluster member switches.
If the hop count is set to 1, it disables extended discovery. The cluster 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 cluster member switch and the first discovered candidate switch.
Examples
This example shows how to set hop count limit to 4. This command is executed on the cluster command switch.
Switch(config)# cluster discovery hop-count 4You can verify your setting 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.
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 to optionally assign a member number to it. Use the no form of the command to remove all members and to make the cluster command switch a candidate switch.
cluster enable name [command-switch-member-number]
no cluster enable
Syntax Description
Defaults
The switch is not a cluster command switch.
No cluster name is defined.
The member number is 0 when the switch is the cluster command switch.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command 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 cluster command switch. If the switch is already configured as the cluster command switch, this command changes the cluster name if it is different from the previous cluster name.
Examples
This example shows how to enable the cluster command switch, name the cluster, and set the cluster command switch member number to 4.
Switch(config)# cluster enable Engineering-IDF4 4You can verify your setting by entering the show cluster privileged EXEC command on the cluster 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 to set the duration in seconds before a switch (either the command or cluster 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 cluster member switch) declares the other switch down. The range is 1 to 300 seconds.
Defaults
The default holdtime is 80 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command with the cluster timer global configuration command only on the cluster command switch. The cluster 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 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 interval timer and the duration on the cluster 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 member
Use the cluster member global configuration command on the cluster command switch to add candidates to a cluster. Use the no form of the 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 cluster command switch has no associated cluster members.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the cluster command switch to add a candidate to or remove a member from the cluster. If you enter this command on a switch other than the cluster 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 cluster 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 cluster command-switch password.
If a switch does not have a configured hostname, the cluster command switch appends a member number to the cluster command-switch hostname and assigns it to the cluster member switch.
If you do not specify a VLAN ID, the cluster 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 cluster 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 cluster command switch selects the next available member number and assigns it to the switch that is 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 cluster 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 outside-interface
Use the cluster outside-interface global configuration command to configure the outside interface for cluster Network Address Translation (NAT) so that a member without an IP address can communicate with devices outside the cluster. Use the no form of this command to return to the default setting.
cluster outside-interface interface-id
no cluster outside-interface
Syntax Description
interface-id
Interface to serve as the outside interface. Valid interfaces include physical interfaces, port-channels, or VLANs. The port-channel range is 1 to 12. The VLAN range is 1 to 4094.
Defaults
The default outside interface is automatically selected by the cluster command switch.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the cluster command switch. If you enter this command on a cluster member switch, an error message appears.
Examples
This example shows how to set the outside interface to VLAN 1:
Switch(config)# cluster outside-interface vlan 1You can verify your setting by entering the show running-config privileged EXEC command.
Related Commands
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
Syntax Description
This command has no arguments or keywords.
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 cluster command switch, the cluster 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 cluster 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 cluster command switch:
Switch(config)# no cluster runYou can verify your setting 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 cluster command-switch redundancy by binding the cluster to an existing Hot Standby Router Protocol (HSRP). Entering the routing-redundancy keyword enables the same HSRP group to be used for cluster command-switch redundancy and routing redundancy. Use the no form of this command to return to the default setting.
cluster standby-group HSRP-group-name [routing-redundancy]
no cluster standby-group
Syntax Description
Defaults
The cluster is not bound to any HSRP group.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the cluster command switch. If you enter it on a cluster member switch, an error message appears.
The cluster command switch propagates the cluster-HSRP binding information to all cluster-HSRP capable members. Each cluster member switch stores the binding information in its NVRAM.
The HSRP group name must be a valid standby group; otherwise, the command exits with an error.
The same group name should be used on all members of the HSRP standby group that is to be bound to the cluster. The same HSRP group name should also be used 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 commander and the members.)
Examples
This example shows how to bind the HSRP group named my_hsrp to the cluster. This command is executed on the cluster command switch.
Switch(config)# cluster standby-group my_hsrpThis example shows how to use the same HSRP group named my_hsrp for routing redundancy and cluster redundancy:
Switch(config)# cluster standby-group my_hsrp routing-redundancyThis example shows the error message when this command is executed on a cluster 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 executed on a cluster member switch:
Switch(config)# cluster standby-group my_hsrp routing-redundancy%ERROR: This command runs on a cluster command switchYou can verify your settings by entering the show cluster privileged EXEC command. The output shows whether redundancy is enabled in the cluster.
Related Commands
cluster timer
Use the cluster timer global configuration command 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
Enter this command with the cluster holdtime global configuration command only on the cluster command switch. The cluster 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 cluster 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.
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
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:
•
•
•
When you define a range, you must enter a space before the hyphen (-), for example:
gigabitethernet1/0/1 - 2
You can also enter multiple ranges. When you define multiple ranges, you must enter a space after the first entry before the comma (,). The space after the comma is optional, for example:
fastethernet1/0/3 , gigabitethernet1/0/1 - 2
fastethernet1/0/3 -4 , gigabitethernet1/0/1 - 2
Examples
This example shows how to create a multiple-interface macro:
Switch(config)# define interface-range macro1 fastethernet1/0/1 -2 , fastethernet1/0/5Related 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
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, see the Cisco IOS Command Reference for Release 12.2.
Examples
This example shows how to remove the directory that contains the old software image after a successful download of a new image:
Switch# delete /force /recursive flash:/old-imageYou can verify that the directory was removed by entering the dir filesystem: privileged EXEC command.
Related Commands
deny
Use the deny MAC access list configuration command to prevent non-IP traffic from being forwarded if the conditions are matched. Use the no form of this command to remove a deny condition from the named MAC access list.
{deny | permit} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr | dst-MAC-addr mask} [type mask | aarp | amber | cos cos | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask | mop-console | mop-dump | msdos | mumps | netbios | vines-echo | vines-ip | xns-idp]
no {deny | permit} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr | dst-MAC-addr mask} [type mask | aarp | amber | cos cos | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask | mop-console | mop-dump | msdos | mumps | netbios | vines-echo | vines-ip | xns-idp]
Syntax Description
Note
To filter IPX traffic, you use the type mask or lsap lsap mask keywords, depending on the type of IPX encapsulation being used. Filter criteria for IPX encapsulation types as specified in Novell terminology and Cisco IOS terminology are listed in Table 2-4.
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
You enter MAC-access list configuration mode by using the mac access-list extended global configuration command.
If you use the host keyword, you cannot enter an address mask; if you do not use the host keyword, you must enter an address mask.
When an access control entry (ACE) is added to an access control list, 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.
Note
Examples
This example shows how to define the named MAC extended access list 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 netbios.This example shows how to remove the deny condition from the named MAC extended access list:
Switch(config-ext-macl)# no deny any 00c0.00a0.03fa 0000.0000.0000 netbios.This example denies all packets with Ethertype 0x4321:
Switch(config-ext-macl)# deny any any 0x4321 0You can verify your settings by entering the show access-lists privileged EXEC command.
Related Commands
deny (ARP access-list configuration)
Use the deny Address Resolution Protocol (ARP) access-list configuration command on the switch stack or on a standalone switch to deny an ARP packet based on matches against the DHCP bindings. Use the no form of this command to remove the specified access control entry (ACE) from the access list.
deny {[request] ip {any | host sender-ip | sender-ip sender-ip-mask} mac {any | host sender-mac | sender-mac sender-mac-mask} | response ip {any | host sender-ip | sender-ip sender-ip-mask} [{any | host target-ip | target-ip target-ip-mask}] mac {any | host sender-mac | sender-mac sender-mac-mask} [{any | host target-mac | target-mac target-mac-mask}]} [log]
no deny {[request] ip {any | host sender-ip | sender-ip sender-ip-mask} mac {any | host sender-mac | sender-mac sender-mac-mask} | response ip {any | host sender-ip | sender-ip sender-ip-mask} [{any | host target-ip | target-ip target-ip-mask}] mac {any | host sender-mac | sender-mac sender-mac-mask} [{any | host target-mac | target-mac target-mac-mask}]} [log]
This command is available only if your switch is running the enhanced multilayer image (EMI).
Syntax Description
Defaults
There are no default settings. However, at the end of the ARP access list, there is an implicit deny ip any mac any command.
Command Modes
ARP access-list configuration
Command History
Usage Guidelines
You can add deny clauses to drop ARP packets based on matching criteria.
Examples
This example shows how to define an ARP access list and to deny both ARP requests and ARP responses from a host with an IP address of 1.1.1.1 and a MAC address of 0000.0000.abcd:
Switch(config)# arp access-list static-hostsSwitch(config-arp-nacl)# deny ip host 1.1.1.1 mac host 0000.0000.abcdSwitch(config-arp-nacl)# endYou can verify your settings by entering the show arp access-list privileged EXEC command.
Related Commands
dot1x auth-fail max-attempts
Use the dot1x auth-fail max-attempts interface configuration command to configure the maximum allowable authentication attempts before a port is moved to the restricted VLAN. To return to the default setting, use the no form of this command.
dot1x auth-fail max-attempts max-attempts
no dot1x auth-fail max-attempts
Syntax Description
max-attempts
Specify a maximum number of authentication attempts allowed before a port is moved to the restricted VLAN. The range is 1 to 3, the default value is 3.
Defaults
The default value is 3 attempts.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you reconfigure the maximum number of authentication attempts allowed by the VLAN, the change takes effect after the re-authentication timer expires.
Examples
This example shows how to set 2 as the maximum number of authentication attempts allowed before the port is moved to the restricted VLAN on port 3:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitethernet1/0/3Switch(config-if)# dot1x auth-fail max-attempts 2Switch(config-if)# endSwitch(config)# endSwitch#You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
dot1x auth-fail vlan [vlan id]
Enables the optional restricted VLAN feature.
dot1x max-reauth-req [count]
Sets the maximum number of times that the switch restarts the authentication process before a port changes to the unauthorized state.
show dot1x [interface interface-id]
Displays IEEE 802.1x status for the specified port.
dot1x auth-fail vlan
Use the dot1x auth-fail vlan interface configuration command to enable the restricted VLAN on a port. To return to the default setting, use the no form of this command.
dot1x auth-fail vlan vlan-id
no dot1x auth-fail vlan vlan-id
Syntax Description
Defaults
No restricted VLAN is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can configure a restricted VLAN on ports configured as follows:
•
•
You should enable re-authentication. The ports in restricted VLANs do not receive re-authentication requests if it is disabled. To start the re-authentication process, the restricted VLAN must receive a link-down event or an Extensible Authentication Protocol (EAP) logoff event from the port. If a host is connected through a hub, the port might never receive a link-down event when that host is disconnected, and, as a result, might not detect any new hosts until the next re-authentication attempt occurs.
If the supplicant fails authentication, the port is moved to a restricted VLAN, and an EAP success message is sent to the supplicant. Because the supplicant is not notified of the actual authentication failure, there might be confusion about this restricted network access. An EAP success message is sent for these reasons:
•
•
A supplicant might cache an incorrect username and password combination after receiving an EAP success message from the authenticator and re-use that information in every re-authentication. Until the supplicant sends the correct username and password combination, the port remains in the restricted VLAN.
Internal VLANs used for Layer 3 ports cannot be configured as restricted VLANs.
You cannot configure a VLAN to be both a restricted VLAN and a voice VLAN. If you do this, a syslog message is generated.
When a restricted VLAN port is moved to an unauthorized state, the authentication process restarts. If the supplicant fails the authentication process again, the authenticator waits in the held state. After the supplicant has correctly re-authenticated, all IEEE 802.1x ports are reinitialized and treated as normal IEEE 802.1x ports.
When you reconfigure a restricted VLAN as a different VLAN, any ports in the restricted VLAN are also moved, and the ports stay in their currently authorized state.
When you shut down or remove a restricted VLAN from the VLAN database, any ports in the restricted VLAN are immediately moved to an unauthorized state, and the authentication process restarts. The authenticator does not wait in a held state because the restricted VLAN configuration still exists. While the restricted VLAN is inactive, all authentication attempts are counted so that when the restricted VLAN becomes active, the port is immediately placed in the restricted VLAN.
The restricted VLAN is supported only in single host mode (the default port mode). For this reason, when a port is placed in a restricted VLAN, the supplicant's MAC address is added to the MAC address table, and any other MAC address that appears on the port is treated as a security violation.
Examples
This example shows how to configure a restricted VLAN on port 1:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# dot1x auth-fail vlan 40Switch(config-if)# endSwitch(config)# endSwitch#You can verify your configuration by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
dot1x auth-fail max-attempts [max-attempts]
Configures the number of authentication attempts allowed before assigning a supplicant to the restricted VLAN.
show dot1x [interface interface-id]
Displays IEEE 802.1x status for the specified port.
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
Examples
This example shows how to reset the configurable 802.1x parameters:
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 port.
dot1x guest-vlan
Use the dot1x guest-vlan interface configuration command to specify an active VLAN as an 802.1x guest VLAN. 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.
The switch maintains the EAPOL packet history. If another EAPOL packet is detected on the interface during the lifetime of the link, the guest VLAN feature is disabled. If the port is already in the guest VLAN state, the port is returned to the unauthorized state, and authentication is restarted. The EAPOL history is reset upon loss of link.
Entering the dot1x guest-vlan supplicant global configuration command disables this behavior.
Any number of non-IEEE 802.1x-capable clients are allowed access when the switch port is moved to the guest VLAN. If an IEEE 802.1x-capable client joins the same port on which the guest VLAN is configured, the port is put into the unauthorized state in the user-configured access VLAN, and authentication is restarted.
Guest VLANs are supported on IEEE 802.1x ports in single-host or multiple-hosts mode.
You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802.1x guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports.
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 port.
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
Usage Guidelines
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 port.
Examples
This example shows how to enable 802.1x globally, enable 802.1x on a port, and enable multiple-hosts mode:
Switch(config)# dot1x system-auth-controlSwitch(config)# interface gigabitethernet1/0/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 port.
dot1x initialize
Use the dot1x initialize privileged EXEC command to manually return the specified 802.1x-enabled port to an unauthorized state before initiating a new authentication session on the port.
dot1x initialize interface interface-id
Syntax Description
Defaults
There is no default setting.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to initialize the 802.1x state machines and to set up a fresh environment for authentication. After you enter this command, the port status becomes unauthorized.
There is no no form of this command.
Examples
This example shows how to manually initialize a port:
Switch# dot1x initialize interface gigabitethernet1/0/2You can verify the unauthorized port status 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 port.
dot1x max-reauth-req
Use the dot1x max-reauth-req interface configuration command to set the maximum number of times that the switch restarts the authentication process before a port transitions to the unauthorized state. Use the no form of this command to return to the default setting.
dot1x max-reauth-req count
no dot1x max-reauth-req
Syntax Description
count
Number of times that the switch restarts the authentication process before the port transitions to the unauthorized state. The range is 1 to 10.
Defaults
The default is 2 times.
Command Modes
Interface configuration
Command History
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 4 as the number of times that the switch restarts the authentication process before the port transitions to the unauthorized state:
Switch(config-if)# dot1x max-reauth-req 4You 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 forwards an EAP frame (assuming that no response is received) to the authentication server before restarting the authentication process.
dot1x timeout tx-period
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 port.
dot1x max-req
Use the dot1x max-req interface configuration command to set the maximum number of times that the switch retransmits an Extensible Authentication Protocol (EAP) frame from the authentication server (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 retransmits an EAP frame from the authentication server before restarting the authentication process. The range is 1 to 10.
Defaults
The default is 2 times.
Command Modes
Interface configuration
Command History
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 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
dot1x timeout tx-period
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 port.
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 globally enable 802.1x on the switch by using the dot1x system-auth-control global configuration command before enabling 802.1x on a specific port.
The 802.1x protocol is supported on Layer 2 static-access ports, voice VLAN ports, and Layer 3 routed ports.
You can use the auto keyword only if the port is not configured as one of these:
•
•
•
•
•
To globally disable 802.1x on the switch, use the no dot1x system-auth-control global configuration command. To disable 802.1x on a specific port, use the no dot1x port-control interface configuration command.
Examples
This example shows how to enable 802.1x on a port:
Switch(config)# interface fastethernet1/0/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 port.
dot1x re-authenticate
Use the dot1x re-authenticate privileged EXEC command to manually initiate a re-authentication of 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 a port:
Switch# dot1x re-authenticate interface fastethernet1/0/1dot1x 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
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
dot1x timeout reauth-period
Sets the number of seconds between re-authentication attempts.
show dot1x [interface interface-id]
Displays 802.1x status for the specified port.
dot1x system-auth-control
Use the dot1x system-auth-control global configuration command to globally enable 802.1x. 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 globally enabling 802.1x. A method list describes the sequence and authentication methods to be queried to authenticate a user.
Examples
This example shows how to globally enable 802.1x on a switch:
Switch(config)# dot1x system-auth-controlYou can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
Enables manual control of the authorization state of the port.
show dot1x [interface interface-id]
Displays 802.1x status for the specified port.
dot1x timeout
Use the dot1x timeout interface configuration command to set 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 default settings:
reauth-period is 3600 seconds.
quiet-period is 60 seconds.
tx-period is 30 seconds.
supp-timeout is 30 seconds.
server-timeout is 30 seconds.
Command Modes
Interface configuration
Command History
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.
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 4000 as the number of seconds between re-authentication attempts:
Switch(config-if)# dot1x reauthenticationSwitch(config-if)# dot1x timeout reauth-period 4000This example shows how to set 30 seconds as the quiet time on the switch:
Switch(config-if)# dot1x timeout quiet-period 30This example shows how to set 25 seconds as the switch-to-authentication server retransmission time:
Switch(config)# dot1x timeout server-timeout 25This example shows how to set 25 seconds as the switch-to-client retransmission time for the EAP request frame:
Switch(config-if)# dot1x timeout supp-timeout 25This 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 resending the request:
Switch(config-if)# dot1x timeout tx-period 60You can verify your settings by entering the show dot1x privileged EXEC command.
Related Commands
duplex
Use the duplex interface configuration command to specify the duplex mode of operation for Fast Ethernet and Gigabit Ethernet ports. Use the no form of this command to return the port to its default value.
duplex {auto | full | half}
no duplex
Syntax Description
Defaults
The default is auto for Fast Ethernet ports and for 1000BASE-T small form-factor pluggable (SFP) modules.
The default is half for 100BASE-FX MMF SFP modules.
Command Modes
Interface configuration
Command History
12.1(14)AX
This command was introduced.
12.2(25)EY
Support for the half keyword was added for the 100BASE-FX SFP module.
Usage Guidelines
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.
For Gigabit Ethernet ports, setting the port to auto has the same effect as specifying full if the attached device does not autonegotiate the duplex parameter.
Certain ports can be configured to be either full duplex or half duplex. Applicability of this command depends on the device to which the switch is attached.
If both ends of the line support autonegotiation, we highly recommend using the default autonegotiation settings. If one interface supports autonegotiation and the other end does not, configure duplex and speed on both interfaces; do use the auto setting on the supported side.
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.
For 10/100 Mbps ports, if both speed and duplex are set to specific values, the link operates at the negotiated speed and duplex value.
For 10/100/1000 Mbps ports, if both the speed and duplex are set to specific values, autonegotiation is disabled.
Beginning with Cisco IOS Release 12.2(25)EY, you can configure the duplex setting when the speed is set to auto.
This command is not available on SFP module ports unless a 1000BASE-T SFP module or a 100BASE-FX MMF SFP module is in the port. All other SFP modules operate only in full-duplex mode.
•
•
Note
Caution
For guidelines on setting the switch speed and duplex parameters, see the "Configuring Interface Characteristics" chapter in the software configuration guide for this release.
Examples
This example shows how to configure a port for full duplex operation:
Switch(config)# interface fastethernet1/0/11Switch(config-if)# duplex fullYou can verify your setting by entering the show interfaces privileged EXEC command.
Related Commands
Displays the interface settings on the switch.
Sets the speed on a 10/100 or 10/100/1000 Mbps interface.
errdisable detect cause
Use the errdisable detect cause global configuration command to enable error-disabled detection for a specific cause or all causes. Use the no form of this command to disable the error-disabled detection feature.
errdisable detect cause {all | dtp-flap | gbic-invalid | l2ptguard| link-flap | loopback | pagp-flap}
no errdisable detect cause {all | dtp-flap | gbic-invalid | l2ptguard | link-flap | loopback | pagp-flap}
Syntax Description
Note
Defaults
Detection is enabled for all causes.
Command Modes
Global configuration
Command History
Usage Guidelines
A cause (dtp-flap, gbic-invalid, l2ptguard, 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 an error-disabled state, an operational state that is similar to link-down state.
If you set a recovery mechanism for the cause by entering the errdisable recovery global configuration command for the cause, the interface is brought out of the error-disabled state and allowed to retry the operation when all causes have timed out. If you do not set a recovery mechanism, 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-disabled detection for the link-flap error-disabled cause:
Switch(config)# errdisable detect cause link-flapYou can verify your setting by entering the show errdisable detect privileged EXEC command.
Related Commands
Displays errdisable detection information.
show interfaces status err-disabled
Displays interface status or a list of interfaces in the 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 | arp-inspection | bpduguard | channel-misconfig | dtp-flap | gbic-invalid | l2ptguard| link-flap | loopback | pagp-flap | psecure-violation | security-violation | udld | vmps} | {interval interval}
no errdisable recovery {cause {all |arp-inspection | bpduguard | channel-misconfig | dtp-flap | gbic-invalid | l2ptguard| link-flap | loopback | pagp-flap | psecure-violation | security-violation | udld | vmps} | {interval interval}
Syntax Description
Note
Defaults
Recovery is disabled for all causes.
The default recovery interval is 300 seconds.
Command Modes
Global configuration
Command History
12.1(14)AX
This command was introduced.
12.2(25)EY
The arp-inspection keyword was added.
Usage Guidelines
A cause (bpduguard, dtp-flap, gbic-invalid, l2ptguard, link-flap, loopback, pagp-flap, psecure-violation, security-violation, udld, vmps) 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 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 err-disabled
Displays interface status or a list of interfaces in error-disabled state.
ethernet evc
Use the ethernet evc global configuration command to define an Ethernet virtual connection (EVC) and to enter EVC configuration mode. Use the no form of this command to delete the EVC.
ethernet evc evc-id
no ethernet evc evc-id
Syntax Description
Defaults
No EVCs are defined.
Command Modes
Global configuration
Command History
Usage Guidelines
After you enter the ethernet evc evc-id command, the switch enters EVC configuration mode, and these configuration commands are available:
•
•
•
•
•
Examples
This example shows how to define an EVC and to enter EVC configuration mode:
Switch(config)# ethernet evc test1Switch(config-evc)#Related Commands
service instance id ethernet evc-id
Configures an Ethernet service instance and attaches an EVC to it.
Displays information about configured EVCs.
ethernet lmi ce-vlan map
Use the ethernet lmi ce-vlan map Ethernet service configuration command to configure Ethernet Local Management Interface (E-LMI) parameters. Use the no form of this command to remove the configuration.
ethernet lmi ce-vlan map {vlan-id | any | default | untagged}
no ethernet lmi ce-vlan map {vlan-id | any | default | untagged}
Syntax Description
Defaults
No E-LMI mapping parameters are defined.
Command Modes
Ethernet service configuration
Command History
Usage Guidelines
Use this command to configure an E-LMI customer VLAN-to-EVC map for a particular user-network interface (UNI).
E-LMI mapping parameters are related to the bundling characteristics set by entering the ethernet uni {bundle [all-to-one] | multiplex} interface configuration command.
•
•
•
•
Examples
This example shows how to configure an E-LMI customer VLAN-to-EVC map to map EVC test to customer VLAN 101 in service instance 333 on the interface:
Switch(config-if)# service instance 333 ethernet testSwitch(config-if-srv)# ethernet lmi ce-vlan map 101Related Commands
service instance id ethernet
Defines an Ethernet service instance and enters Ethernet service configuration mode.
Displays information about configured Ethernet service instances.
ethernet oam remote-failure
Use the ethernet oam remote-failure interface configuration or configuration template command to configure Ethernet operations, maintenance, and administration (EOM) remote failure indication. Use the no form of this command to remove the configuration.
ethernet oam remote-failure {critical-event | dying-gasp | link-fault} action error-disable-interface
no ethernet oam remote-failure {critical-event | dying-gasp | link-fault} action
Syntax Description
Defaults
Configuration template
Interface configuration
Command Modes
Ethernet service configuration
Command History
Usage Guidelines
You can apply this command to an Ethernet OAM template and to an interface. The interface configuration takes precedence over template configuration. To enter OAM template configuration mode, use the template template-name global configuration command.
You can configure an error-disable action to occur if the remote link goes down, if the remote device is disabled, or if the remote device disables Ethernet OAM on the interface.
The Catalyst 3750 Metro switch does not generate Link Fault or Critical Event OAM PDUs. However, if these PDUs are received from a link partner, they are processed. The switch supports sending and receiving Dying Gasp OAM PDUs.
For complete command and configuration for the Ethernet OAM protocol, see the Cisco IOS feature module at this URL:
http://www.cisco.com/en/US/products/ps6922/products_feature_guide09186a008067344c.htmlFor documentation for the CFM and Ethernet OAM commands, see this URL:
http://www.cisco.com/en/US/products/ps6922/products_command_reference_book09186a0080699104.htmlExamples
This example shows how to configure an Ethernet OAM template for remote-failure indication when an unrecoverable error has occurred and how to apply it to an interface:
Switch(config)# template oam1Switch(config-template)# ethernet oam remote-failure dying-gasp action error-disable interfaceSwitch(config-template)# exitSwitch(config)# interface gigabitethernet 0/1Switch(config-if)# source template oam1Switch(config-if)# exitThis example shows how to configure an Ethernet OAM remote-failure indication on one interface for unrecoverable errors:
Switch(config)# interface gigabitethernet 0/1Switch(config-if)# ethernet oam remote-failure dying-gasp action error-disable interfaceSwitch(config-if)# exitRelated Commands
show ethernet oam status [interface interface-id]
Displays configured Ethernet OAM remote failure conditions on all interfaces or on the specified interface.
ethernet uni
Use the ethernet uni interface configuration command to set UNI bundling attributes. Use the no form of this command to return to the default bundling configuration.
ethernet uni {bundle [all-to-one] | multiplex}
no ethernet uni {bundle | multiplex}
Syntax Description
Defaults
If bundling or multiplexing attributes are not configured, the default is bundling with multiplexing. The UNI then has one or more EVCs with one or more CE VLANs mapped to each EVC.
Command Modes
Interface configuration
Command History
Usage Guidelines
The UNI attributes determine the functionality that the interface has regarding bundling VLANs, multiplexing EVCs, and the combination of these.
If you want both bundling and multiplexing services for a UNI, you do not need to configure bundling or multiplexing. If you want only bundling, or only multiplexing, you need to configure it appropriately.
When you configure, change, or remove a UNI service type, the EVC and CE-VLAN ID configurations are checked to ensure that the configurations and the UNI service types match. If the configurations do not match, the command is rejected.
If you intend to use the ethernet lmi ce-vlan map any service configuration command, you must first configure all-to-one bundling on the interface. See the ethernet lmi ce-vlan map section for more information.
Examples
This example shows how to configure bundling without multiplexing:
Switch(config-if)# ethernet uni bundleTo verify UNI service type, enter the show ethernet service interface detail privileged EXEC command.
Related Commands
Displays information about Ethernet service instances on an interface, including service type.
ethernet uni id
Use the ethernet uni interface configuration command to create an Ethernet user-network interface (UNI) ID. Use the no form of this command to remove the UNI ID.
ethernet uni id name
no ethernet uni id
Syntax Description
name
Identify an Ethernet UNI ID. The name should be unique for all UNIs that are part of a given service instance and can be up to 64 characters in length.
Defaults
No UNI IDs are created.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you configure a UNI ID on a port, that ID is used as the default name for all maintenance end points (MEPs) configured on the port.
You must enter the ethernet uni id name command on all ports that are directly connected to customer-edge (CE) devices. If the specified ID is not unique on the device, an error message appears.
Examples
This example shows how to identify a unique UNI:
Switch(config-if)# ethernet uni id test2Related Commands
Displays information about Ethernet service instances on an interface, including service type.
flowcontrol
Use the flowcontrol interface configuration command to set the receive flow-control state for an interface. When flow control send is operable and 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 a 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 keywords to disable flow control.
flowcontrol receive {desired | off | on}
Note
Syntax Description
Defaults
The default is flowcontrol receive off.
Command Modes
Interface configuration
Command History
Usage Guidelines
The switch does not support sending flow-control pause frames.
Note that 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-5 shows the flow control results on local and remote ports for a combination of settings. The table assumes that receive desired has the same results as using the receive on keywords.
Examples
This example shows how to configure the local port to not support flow control by the remote port:
Switch(config-if)# flowcontrol receive offYou can verify your settings by entering the show interfaces privileged EXEC command.
Related Commands
Displays the interface settings on the switch, including input and output flow control.
interface port-channel
Use the interface port-channel global configuration command to access or create the port-channel logical interface. Use the no form of this command to remove the port-channel.
interface port-channel port-channel-number
no interface port-channel port-channel-number
Syntax Description
Defaults
No port-channel logical interfaces are defined.
Command Modes
Global configuration
Command History
Usage Guidelines
For Layer 2 EtherChannels, you do not have to create a port-channel first before assigning a physical port to a channel group. Instead, you can use the channel-group interface configuration command. It automatically creates the port-channel when the channel group gets its first physical port. If you create the port-channel first, the channel-group-number can be the same as the port-channel-number, or you can use a new number. If you use a new number, the channel-group command dynamically creates a new port channel.
You create Layer 3 port channels by using the interface port-channel command followed by the no switchport interface configuration command. You should manually configure the port-channel logical interface before putting the interface into the channel group.
Only one port channel in a channel group is allowed.
Caution
Caution
Follow these guidelines when you use the interface port-channel command:
•
•
For a complete list of configuration guidelines, see the "Configuring EtherChannels" chapter in the software guide for this release.
Examples
This example shows how to create port-channel 5:
Switch(config)# interface port-channel 5You can verify your setting by entering the show running-config privileged EXEC or show etherchannel channel-group-number detail privileged EXEC command.
Related Commands
interface range
Use the interface range global configuration command to enter interface range configuration mode and to execute a command on multiple ports at the same time. Use the no form of this command to remove an interface range.
interface range {port-range | macro name}
no interface range {port-range | macro name}
Syntax Description
port-range
Port range. For a list of valid values for port-range, see the "Usage Guidelines" section.
macro name
Specify the name of a macro.
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
Usage Guidelines
When you enter interface range configuration mode, all interface parameters you enter are attributed to all interfaces within the range.
For VLANs, you can use the interface range command only on existing VLAN switch virtual interfaces (SVIs). To display VLAN SVIs, enter the show running-config privileged EXEC command. VLANs not displayed cannot be used in the interface range command. The commands entered under interface range command are applied to all existing VLAN SVIs in the range.
All configuration changes made to an interface range are saved to NVRAM, but the interface range itself is not saved to NVRAM.
You can enter the interface range in two ways:
•
•
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. However, you can define up to five interface ranges with a single command, with each range separated by a comma.
Valid values for port-range type and interface:
•
•
Note
•
•
For physical interfaces:
•
•
•
When you define a range, you must enter a space between the first entry and the hyphen (-):
interface range gigabitethernet1/0/1 -2When you define multiple ranges, you must still enter a space after the first entry, before the comma (,):
interface range fastethernet1/0/3 , gigabitethernet1/0/1 - 2interface range fastethernet1/0/3 -5, fastethernet1/0/7 -8You cannot specify both a macro and an interface range in the same command.
A single interface can also be specified in port-range (this would make the command similar to the interface interface-id global configuration command).
Note
Examples
This example shows how to use the interface range command to enter interface range configuration mode to apply commands to two ports:
Switch(config)# interface range gigabitethernet1/0/1 - 2Switch(config-if-range)#This example shows how to use a port-range macro macro1 for the same function. The advantage is that you can reuse macro1 until you delete it.
Switch(config)# define interface-range macro1 gigabitethernet1/0/1 - 2Switch(config)# interface range macro macro1Switch(config-if-range)#Related Commands
interface vlan
Use the interface vlan global configuration command to create or access a dynamic switch virtual interface (SVI) and to enter interface configuration mode. Use the no form of this command to delete an SVI.
interface vlan vlan-id
no interface vlan vlan-id
Syntax Description
Defaults
The default VLAN interface is VLAN 1.
Command Modes
Global configuration
Command History
Usage Guidelines
You cannot delete the VLAN 1 interface.
SVIs are created the first time that you enter the interface vlan vlan-id command for a particular VLAN. The vlan-id corresponds to the VLAN-tag associated with data frames on an ISL or 802.1Q encapsulated trunk or the VLAN ID configured for an access port.
Note
If you delete an SVI by entering the no interface vlan vlan-id command, the deleted interface is no longer visible in the output from the show interfaces privileged EXEC command.
You can reinstate a deleted SVI by entering the interface vlan vlan-id command for the deleted interface. The interface comes back up, but much of the previous configuration will be gone.
The interrelationship between the number of SVIs configured on a switch and the number of other features being configured might have an impact on CPU utilization due to hardware limitations. You can use the sdm prefer global configuration command to reallocate system hardware resources based on templates and feature tables. For more information, see the sdm prefer command.
Examples
This example shows how to create a new SVI with VLAN ID 23 and enter interface configuration mode:
Switch(config)# interface vlan 23Switch(config-if)#You can verify your setting by entering the show interfaces and show interfaces vlan vlan-id privileged EXEC commands.
Related Commands
show interfaces vlan vlan-id
Displays the administrative and operational status of all interfaces or the specified VLAN.
ip access-group
Use the ip access-group interface configuration command to control access to a Layer 2 or Layer 3 interface. Use the no form of this command to remove all access groups or the specified access group from the interface.
ip access-group {access-list-number | name} {in | out}
no ip access-group [access-list-number | name] {in | out}
Syntax Description
Defaults
No access list is applied to the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can apply named or numbered standard or extended IP access lists to an interface. To define an access list by name, use the ip access-list global configuration command. To define a numbered access list, use the access list global configuration command. You can used numbered standard access lists ranging from 1 to 99 and 1300 to 1999 or extended access lists ranging from 100 to 199 and 2000 to 2699.
You can use this command to apply an access list to a Layer 2 or Layer 3 interface. However, note these limitations for Layer 2 interfaces (port ACLs):
•
•
•
•
You can use router ACLs, input port ACLs, and VLAN maps on the same switch. However, a port ACL takes precedence over a router ACL or VLAN map.
•
•
•
•
•
You can apply IP ACLs to both outbound or inbound Layer 3 interfaces.
A Layer 3 interface can have one IP ACL applied in each direction.
You can configure only one VLAN map and one router ACL in each direction (input/output) on a VLAN interface.
For standard inbound access lists, after the switch receives a packet, it checks the source address of the packet against the access list. IP extended access lists can optionally check other fields in the packet, such as the destination IP address, protocol type, or port numbers. If the access list permits the packet, the switch continues to process the packet. If the access list denies the packet, the switch discards the packet. If the access list has been applied to a Layer 3 interface, discarding a packet (by default) causes the generation of an Internet Control Message Protocol (ICMP) Host Unreachable message. ICMP Host Unreachable messages are not generated for packets discarded on a Layer 2 interface.
For standard outbound access lists, after receiving a packet and sending it to a controlled interface, the switch checks the packet against the access list. If the access list permits the packet, the switch sends the packet. If the access list denies the packet, the switch discards the packet and, by default, generates an ICMP Host Unreachable message.
If the specified access list does not exist, all packets are passed.
Examples
This example shows how to apply IP access list 101 to inbound packets on a port:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# ip access-group 101 inYou can verify your settings by entering the show ip interface, show access-lists, or show ip access-lists privileged EXEC command.
Related Commands
ip address
Use the ip address interface configuration command to set an IP address for the Layer 2 switch or an IP address for each switch virtual interface (SVI) or routed port on the Layer 3 switch. Use the no form of this command to remove an IP address or to disable IP processing.
ip address ip-address subnet-mask [secondary]
no ip address [ip-address subnet-mask] [secondary]
Syntax Description
Defaults
No IP address is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you remove the switch IP address through a Telnet session, your connection to the switch will be lost.
Hosts can determine subnet masks using the Internet Control Message Protocol (ICMP) Mask Request message. Routers respond to this request with an ICMP Mask Reply message.
You can disable IP processing on a particular interface by removing its IP address with the no ip address command. If the switch detects another host using one of its IP addresses, it will send an error message to the console.
You can use the optional keyword secondary to specify an unlimited number of secondary addresses. Secondary addresses are treated like primary addresses, except the system never generates datagrams other than routing updates with secondary source addresses. IP broadcasts and ARP requests are handled properly, as are interface routes in the IP routing table.
Note
When you are routing Open Shortest Path First (OSPF), ensure that all secondary addresses of an interface fall into the same OSPF area as the primary addresses.
If your switch receives its IP address from a Bootstrap Protocol (BOOTP) or DHCP server and you remove the switch IP address by using the no ip address command, IP processing is disabled, and the BOOTP or DHCP server cannot reassign the address.
A Layer 3 switch can have an IP address assigned to each routed port and SVI. The number of routed ports and SVIs that you can configure is not limited by software; however, the interrelationship between this number and the number of other features being configured might have an impact on CPU utilization due to hardware limitations. You can use the sdm prefer global configuration command to reallocate system hardware resources based on templates and feature tables. For more information, see the sdm prefer command.
Examples
This example shows how to configure the IP address for the Layer 2 switch on a subnetted network:
Switch(config)# interface vlan 1Switch(config-if)# ip address 172.20.128.2 255.255.255.0This example shows how to configure the IP address for a port on the Layer 3 switch:
Switch(config)# ip multicast-routingSwitch(config)# interface gigabitethernet1/0/1Switch(config-if)# no switchportSwitch(config-if)# ip address 172.20.128.2 255.255.255.0You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
ip arp inspection filter vlan
Use the ip arp inspection filter vlan global configuration command on the switch stack or on a standalone switch to permit or deny Address Resolution Protocol (ARP) requests and responses from a host configured with a static IP address when dynamic ARP inspection is enabled. Use the no form of this command to return to the default settings.
ip arp inspection filter arp-acl-name vlan vlan-range [static]
no ip arp inspection filter arp-acl-name vlan vlan-range [static]
This command is available only if your switch is running the enhanced multilayer image (EMI).
Syntax Description
Defaults
No defined ARP ACLs are applied to any VLAN.
Command Modes
Global configuration
Command History
Usage Guidelines
When an ARP ACL is applied to a VLAN for dynamic ARP inspection, only the ARP packets with IP-to-MAC address bindings are compared against the ACL. If the ACL permits a packet, the switch forwards it. All other packet types are bridged in the ingress VLAN without validation.
If the switch denies a packet because of an explicit deny statement in the ACL, the packet is dropped. If the switch denies a packet because of an implicit deny statement, the packet is then compared against the list of DHCP bindings (unless the ACL is static, which means that packets are not compared against the bindings).
Use the arp access-list acl-name global configuration command to define the ARP ACL or to add clauses to the end of a predefined list.
Examples
This example shows how to apply the ARP ACL static-hosts to VLAN 1 for dynamic ARP inspection:
Switch(config)# ip arp inspection filter static-hosts vlan 1You can verify your settings by entering the show ip arp inspection vlan 1 privileged EXEC command.
Related Commands
Defines an ARP ACL.
Denies an ARP packet based on matches against the DHCP bindings.
Permits an ARP packet based on matches against the DHCP bindings.
Displays detailed information about ARP access lists.
show ip arp inspection vlan vlan-range
Displays the configuration and the operating state of dynamic ARP inspection for the specified VLAN.
ip arp inspection limit
Use the ip arp inspection limit interface configuration command on the switch stack or on a standalone switch to limit the rate of incoming Address Resolution Protocol (ARP) requests and responses on an interface. It prevents dynamic ARP inspection from using all of the switch resources if a denial-of-service attack occurs. Use the no form of this command to return to the default settings.
ip arp inspection limit {rate pps [burst interval seconds] | none}
no ip arp inspection limit
This command is available only if your switch is running the enhanced multilayer image (EMI).
Syntax Description
Defaults
The rate is 15 pps on untrusted interfaces, assuming that the network is a switched network with a host connecting to as many as 15 new hosts per second.
The rate is unlimited on all trusted interfaces.
The burst interval is 1 second.
Command Modes
Interface configuration
Command History
Usage Guidelines
The rate applies to both trusted and untrusted interfaces. Configure appropriate rates on trunks to process packets across multiple dynamic ARP inspection-enabled VLANs, or use the none keyword to make the rate unlimited.
After a switch receives more than the configured rate of packets every second consecutively over a number of burst seconds, the interface is placed into an error-disabled state.
Unless you explicitly configure a rate limit on an interface, changing the trust state of the interface also changes its rate limit to the default value for that trust state. After you configure the rate limit, the interface retains the rate limit even when its trust state is changed. If you enter the no ip arp inspection limit interface configuration command, the interface reverts to its default rate limit.
You should configure trunk ports with higher rates to reflect their aggregation. When the rate of incoming packets exceeds the user-configured rate, the switch places the interface into an error-disabled state. The error-disable recovery feature automatically removes the port from the error-disabled state according to the recovery setting.
The rate of incoming ARP packets on EtherChannel ports equals the sum of the incoming rate of ARP packets from all channel members. Configure the rate limit for EtherChannel ports only after examining the rate of incoming ARP packets on all the channel members.
Examples
This example shows how to limit the rate of incoming ARP requests on a port to 25 pps and to set the interface monitoring interval to 5 consecutive seconds:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# ip arp inspection limit rate 25 burst interval 5You can verify your settings by entering the show ip arp inspection interfaces interface-id privileged EXEC command.
Related Commands
show ip arp inspection interfaces
Displays the trust state and the rate limit of ARP packets for the specified interface or all interfaces.
ip arp inspection log-buffer
Use the ip arp inspection log-buffer global configuration command on the switch stack or on a standalone switch to configure the dynamic Address Resolution Protocol (ARP) inspection logging buffer. Use the no form of this command to return to the default settings.
ip arp inspection log-buffer {entries number | logs number interval seconds}
no ip arp inspection log-buffer {entries | logs}
Syntax Description
Defaults
When dynamic ARP inspection is enabled, denied or dropped ARP packets are logged.
The number of log entries is 32.
The number of system messages is limited to 5 per second.
The logging-rate interval is 1 second.
Command Modes
Global configuration
Command History
Usage Guidelines
A value of 0 is not allowed for both the logs and the interval keywords.
The logs and interval settings interact. If the logs number X is greater than interval seconds Y, X divided by Y (X/Y) system messages are sent every second. Otherwise, one system message is sent every Y divided by X (Y/X) seconds. For example, if the logs number is 20 and the interval seconds is 4, the switch generates system messages for five entries every second while there are entries in the log buffer.
A log buffer entry can represent more than one packet. For example, if an interface receives many packets on the same VLAN with the same ARP parameters, the switch combines the packets as one entry in the log buffer and generates a system message as a single entry.
If the log buffer overflows, it means that a log event does not fit into the log buffer, and the output display for the show ip arp inspection log privileged EXEC command is affected. A -- in the display appears in place of all data except the packet count and the time. No other statistics are provided for the entry. If you see this entry in the display, increase the number of entries in the log buffer, or increase the logging rate.
Examples
This example shows how to configure the logging buffer to hold up to 45 entries:
Switch(config)# ip arp inspection log-buffer entries 45This example shows how to configure the logging rate to 20 log entries per 4 seconds. With this configuration, the switch generates system messages for five entries every second while there are entries in the log buffer.
Switch(config)# ip arp inspection log-buffer logs 20 interval 4You can verify your settings by entering the show ip arp inspection log privileged EXEC command.
Related Commands
ip arp inspection trust
Use the ip arp inspection trust interface configuration command on the switch stack or on a standalone switch to configure an interface trust state that determines which incoming Address Resolution Protocol (ARP) packets are inspected. Use the no form of this command to return to the default setting.
ip arp inspection trust
no ip arp inspection trust
This command is available only if your switch is running the enhanced multilayer image (EMI).
Syntax Description
This command has no arguments or keywords.
Defaults
The interface is untrusted.
Command Modes
Interface configuration
Command History
Usage Guidelines
The switch does not check ARP packets that it receives on the trusted interface; it simply forwards the packets.
For untrusted interfaces, the switch intercepts all ARP requests and responses. It verifies that the intercepted packets have valid IP-to-MAC address bindings before updating the local cache and before forwarding the packet to the appropriate destination. The switch drops invalid packets and logs them in the log buffer according to the logging configuration specified with the ip arp inspection vlan logging global configuration command.
Examples
This example shows how to configure a port to be trusted:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# ip arp inspection trustYou can verify your setting by entering the show ip arp inspection interfaces interface-id privileged EXEC command.
Related Commands
Configures the dynamic ARP inspection logging buffer.
show ip arp inspection interfaces
Displays the trust state and the rate limit of ARP packets for the specified interface or all interfaces.
Displays the configuration and contents of the dynamic ARP inspection log buffer.
ip arp inspection validate
Use the ip arp inspection validate global configuration command on the switch stack or on a standalone switch to perform specific checks for dynamic Address Resolution Protocol (ARP) inspection. Use the no form of this command to return to the default settings.
ip arp inspection validate {[src-mac] [dst-mac] [ip]}
no ip arp inspection validate [src-mac] [dst-mac] [ip]
Syntax Description
Defaults
No checks are performed.
Command Modes
Global configuration
Command History
Usage Guidelines
You must specify at least one of the keywords. Each command overrides the configuration of the previous command; that is, if a command enables src-mac and dst-mac validations, and a second command enables IP validation only, the src-mac and dst-mac validations are disabled as a result of the second command.
If you first specify the src-mac keyword, you also can specify the dst-mac and ip keywords. If you first specify the ip keyword, no other keywords can be specified.
The no form of the command disables only the specified checks. If none of the options are enabled, all checks are disabled.
Examples
This example show how to enable source MAC validation:
Switch(config)# ip arp inspection validate src-macYou can verify your setting by entering the show ip arp inspection vlan vlan-range privileged EXEC command.
Related Commands
show ip arp inspection vlan vlan-range
Displays the configuration and the operating state of dynamic ARP inspection for the specified VLAN.
ip arp inspection vlan
Use the ip arp inspection vlan global configuration command on the switch stack or on a standalone switch to enable dynamic Address Resolution Protocol (ARP) inspection on a per-VLAN basis. Use the no form of this command to return to the default setting.
ip arp inspection vlan vlan-range
no ip arp inspection vlan vlan-range
This command is available only if your switch is running the enhanced multilayer image (EMI).
Syntax Description
vlan-range
VLAN number or range.
You can specify a single VLAN identified by VLAN ID number, a range of VLANs separated by a hyphen, or a series of VLANs separated by a comma. The range is 1 to 4094.
Defaults
ARP inspection is disabled on all VLANs.
Command Modes
Global configuration
Command History
Usage Guidelines
You must specify the VLANs on which to enable dynamic ARP inspection.
Dynamic ARP inspection is supported on access ports, trunk ports, EtherChannel ports, and private VLAN ports.
Examples
This example shows how to enable dynamic ARP inspection on VLAN 1:
Switch(config)# ip arp inspection vlan 1You can verify your setting by entering the show ip arp inspection vlan vlan-range privileged EXEC command.
Related Commands
Defines an ARP access control list (ACL).
show ip arp inspection vlan vlan-range
Displays the configuration and the operating state of dynamic ARP inspection for the specified VLAN.
ip arp inspection vlan logging
Use the ip arp inspection vlan logging global configuration command on the switch stack or on a standalone switch to control the type of packets that are logged per VLAN. Use the no form of this command to disable this logging control.
ip arp inspection vlan vlan-range logging {acl-match {matchlog | none} | dhcp-bindings {all | none | permit}}
no ip arp inspection vlan vlan-range logging {acl-match | dhcp-bindings}
Syntax Description
Defaults
All denied or all dropped packets are logged.
Command Modes
Global configuration
Command History
Usage Guidelines
The term logged means that the entry is placed into the log buffer and that a system message is generated.
The acl-match and dhcp-bindings keywords merge with each other; that is, when you configure an ACL match, the DHCP bindings configuration is not disabled. Use the no form of the command to reset the logging criteria to their defaults. If neither option is specified, all types of logging are reset to log when ARP packets are denied. These are the options:
•
•
If neither the acl-match or the dhcp-bindings keywords are specified, all denied packets are logged.
The implicit deny at the end of an ACL does not include the log keyword. This means that when you use the static keyword in the ip arp inspection filter vlan global configuration command, the ACL overrides the DHCP bindings. Some denied packets might not be logged unless you explicitly specify the deny ip any mac any log ACE at the end of the ARP ACL.
Examples
This example shows how to configure ARP inspection on VLAN 1 to log packets that match the permit commands in the ACL:
Switch(config)# arp access-list test1Switch(config-arp-nacl)# permit request ip any mac any logSwitch(config-arp-nacl)# permit response ip any any mac any any logSwitch(config-arp-nacl)# exitSwitch(config)# ip arp inspection vlan 1 logging acl-match matchlogYou can verify your settings by entering the show ip arp inspection vlan vlan-range privileged EXEC command.
Related Commands
Defines an ARP ACL.
Clears the dynamic ARP inspection log buffer.
Configures the dynamic ARP inspection logging buffer.
Displays the configuration and contents of the dynamic ARP inspection log buffer.
show ip arp inspection vlan vlan-range
Displays the configuration and the operating state of dynamic ARP inspection for the specified VLAN.
ip dhcp snooping
Use the ip dhcp snooping global configuration command to globally enable DHCP snooping. Use the no form of this command to return to the default setting.
ip dhcp snooping
no ip dhcp snooping
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP snooping is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
For any DHCP snooping configuration to take effect, you must globally enable DHCP snooping.
DHCP snooping is not active until you enable snooping on a VLAN by using the ip dhcp snooping vlan vlan-id global configuration command.
Examples
This example shows how to enable DHCP snooping:
Switch(config)# ip dhcp snoopingYou can verify your settings by entering the show ip dhcp snooping privileged EXEC command.
Related Commands
Enables DHCP snooping on a VLAN.
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding information.
ip dhcp snooping binding
Use the ip dhcp snooping binding privileged EXEC command to configure the DHCP snooping binding database and to add binding entries to the database. Use the no form of this command to delete entries from the binding database.
ip dhcp snooping binding mac-address vlan vlan-id ip-address interface interface-id expiry seconds
no ip dhcp snooping binding mac-address vlan vlan-id ip-address interface interface-id
Syntax Description
Defaults
No default database is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when you are testing or debugging the switch.
In the DHCP snooping binding database, each database entry, also referred to a binding, has an IP address, an associated MAC address, the lease time (in hexadecimal format), the interface to which the binding applies, and the VLAN to which the interface belongs. The database can have up to 512 bindings.
Use the show ip dhcp snooping binding privileged EXEC command to display only the dynamically configured bindings. Use the show ip source binding privileged EXEC command to display the dynamically and statically configured bindings.
Examples
This example shows how to generate a DHCP binding configuration with an expiration time of 1000 seconds on a port in VLAN 1:
Switch# ip dhcp snooping binding 0001.1234.1234 vlan 1 172.20.50.5 interface gigabitethernet1/0/1 expiry 1000You can verify your settings by entering the show ip dhcp snooping binding or the show ip dhcp source binding privileged EXEC command.
Related Commands
ip dhcp snooping database
Use the ip dhcp snooping database global configuration command to configure the DHCP snooping binding database agent. Use the no form of this command to disable the agent, to reset the timeout value, or to reset the write-delay value.
ip dhcp snooping database {{flash:/filename | ftp://user:password@host/filename | rcp://user@host/filename | tftp://host/filename} | timeout seconds | write-delay seconds}
no ip dhcp snooping database [timeout | write-delay]
Syntax Description
Defaults
The URL for the database agent or binding file is not defined.
The timeout value is 300 seconds (5 minutes).
The write-delay value is 300 seconds (5 minutes).
Command Modes
Global configuration
Command History
Usage Guidelines
The DHCP snooping binding database can have up to 512 bindings.
To ensure that the lease time in the database is accurate, we recommend that Network Time Protocol (NTP) is enabled and configured for these features:
•
•
•
•
•
If NTP is configured, the switch writes binding changes to the binding file only when the switch system clock is synchronized with NTP.
Because both NVRAM and the flash memory have limited storage capacity, we recommend that you store a binding file on a TFTP server. You must create an empty file at the configured URL on network-based URLs (such as TFTP and FTP) before the switch can write bindings to the binding file at that URL for the first time.
Use the ip dhcp snooping database flash:/filename command to save the DHCP snooping binding database in the stack master NVRAM. The database is not saved in a stack member NVRAM.
Use the no ip dhcp snooping database command to disable the agent.
Use the no ip dhcp snooping database timeout command to reset the timeout value.
Use the no ip dhcp snooping database write-delay command to reset the write-delay value.
Examples
This example shows how to store a binding file at an IP address of 10.1.1.1 that is in a directory called directory. A file named file must be present on the TFTP server.
Switch(config)# ip dhcp snooping database tftp://10.1.1.1/directory/fileThis example shows how to store a binding file called file01.txt in the stack master NVRAM.
Switch(config)# ip dhcp snooping database flash:file01.txtYou can verify your settings by entering the show ip dhcp snooping database privileged EXEC command.
Related Commands
Enables DHCP snooping on a VLAN.
Configures the DHCP snooping binding database.
Displays the status of DHCP snooping database agent.
ip dhcp snooping information option
Use the ip dhcp snooping information option global configuration command to enable DHCP option-82 data insertion. Use the no form of this command to disable DHCP option-82 data insertion.
ip dhcp snooping information option
no ip dhcp snooping information option
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP option-82 data insertion is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
You must globally enable DHCP snooping by using the ip dhcp snooping global configuration command for any DHCP snooping configuration to take effect.
When the option-82 feature is enabled and a switch receives a DHCP request from a host, it adds the option-82 information in the packet. The option-82 information contains the switch MAC address (the remote ID suboption) and the port identifier, vlan-mod-port, from which the packet is received (circuit ID suboption). The switch forwards the DHCP request that includes the option-82 field to the DHCP server.
When the DHCP server receives the packet, it can use the remote ID, the circuit ID, or both to assign IP addresses and implement policies, such as restricting the number of IP addresses that can be assigned to a single remote ID or a circuit ID. Then the DHCP server echoes the option-82 field in the DHCP reply.
The DHCP server unicasts the reply to the switch if the request was relayed to the server by the switch. When the client and server are on the same subnet, the server broadcasts the reply. The switch inspects the remote ID and possibly the circuit ID fields to verify that it originally inserted the option-82 data. The switch removes the option-82 field and forwards the packet to the switch port that connects to the DHCP host that sent the DHCP request.
Examples
This example shows how to enable DHCP option-82 data insertion:
Switch(config)# ip dhcp snooping information optionYou can verify your settings by entering the show ip dhcp snooping privileged EXEC command.
Related Commands
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding information.
ip dhcp snooping information option allowed-untrusted
Use the ip dhcp snooping information option allowed-untrusted global configuration command on an aggregation switch to configure it to accept DHCP packets with option-82 information that are received on untrusted ports that might be connected to an edge switch. Use the no form of this command to configure the switch to drop these packets from the edge switch.
ip dhcp snooping information option allowed-untrusted
no ip dhcp snooping information option allowed-untrusted
Syntax Description
This command has no arguments or keywords.
Defaults
The switch drops DHCP packets with option-82 information that are received on untrusted ports that might be connected to an edge switch.
Command Modes
Global configuration
Command History
Usage Guidelines
You might want an edge switch to which a host is connected to insert DHCP option-82 information at the edge of your network. You might also want to enable DHCP security features, such as DHCP snooping, IP source guard, or dynamic Address Resolution Protocol (ARP) inspection, on an aggregation switch. However, if DHCP snooping is enabled on the aggregation switch, the switch drops packets with option-82 information that are received on an untrusted port and does not learn DHCP snooping bindings for connected devices on a trusted interface.
If the edge switch to which a host is connected inserts option-82 information and you want to use DHCP snooping on an aggregation switch, enter the ip dhcp snooping information option allowed-untrusted command on the aggregation switch. The aggregation switch can learn the bindings for a host even though the aggregation switch receives DHCP snooping packets on an untrusted port. You can also enable DHCP security features on the aggregation switch. The port on the edge switch to which the aggregation switch is connected must be configured as a trusted port.
Note
Examples
This example shows how to configure an access switch to not check the option-82 information in untrusted packets from an edge switch and to accept the packets:
Switch(config)# ip dhcp snooping information option allowed-untrustedYou can verify your settings by entering the show ip dhcp snooping privileged EXEC command.
Related Commands
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding information.
ip dhcp snooping information option format remote-id
Use the ip dhcp snooping information option format remote-id global configuration command on the switch to configure the option-82 remote-ID suboption. Use the no form of this command to configure the default remote-ID suboption.
ip dhcp snooping information option format remote-id [string ASCII string | hostname]
no ip dhcp snooping information option format remote-id
Syntax Description
string ASCII-string
Specify a remote ID, using from 1 to 63 ASCII characters (no spaces).
hostname
Specify the switch hostname as the remote ID.
Defaults
The switch MAC address is the remote ID.
Command Modes
Global configuration
Command History
Usage Guidelines
You must globally enable DHCP snooping by using the ip dhcp snooping global configuration command for any DHCP snooping configuration to take effect.
When the option-82 feature is enabled, the default remote-ID suboption is the switch MAC address. This command allows you to configure either the switch hostname or a string of up to 63 ASCII characters (but no spaces) to be the remote ID.
Note
Examples
This example shows how to configure the option- 82 remote-ID suboption:
Switch(config)# ip dhcp snooping information option format remote-id hostnameYou can verify your settings by entering the show ip dhcp snooping user EXEC command.
Related Commands
ip dhcp snooping vlan information option format-type circuit-id string
Configures the option-82 circuit-ID suboption.
Displays the DHCP snooping configuration.
ip dhcp snooping limit rate
Use the ip dhcp snooping limit rate interface configuration command to configure the number of DHCP messages an interface can receive per second. Use the no form of this command to return to the default setting.
ip dhcp snooping limit rate rate
no ip dhcp snooping limit rate
Syntax Description
Defaults
DHCP snooping rate limiting is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Normally, the rate limit applies to untrusted interfaces. If you want to configure rate limiting for trusted interfaces, keep in mind that trusted interfaces might aggregate DHCP traffic on multiple VLANs (some of which might not be snooped) in the switch, and you will need to adjust the interface rate limits to a higher value.
If the rate limit is exceeded, the interface is error-disabled. If you enabled error recovery by entering the errdisable recovery dhcp-rate-limit global configuration command, the interface retries the operation again when all the causes have timed out. If the error-recovery mechanism is not enabled, the interface stays in the error-disabled state until you enter the shutdown and no shutdown interface configuration commands.
Examples
This example shows how to set a message rate limit of 150 messages per second on an interface:
Switch(config-if)# ip dhcp snooping limit rate 150You can verify your settings by entering the show ip dhcp snooping privileged EXEC command.
Related Commands
Configures the recover mechanism.
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding information.
ip dhcp snooping trust
Use the ip dhcp snooping trust interface configuration command to configure a port as trusted for DHCP snooping purposes. Use the no form of this command to return to the default setting.
ip dhcp snooping trust
no ip dhcp snooping trust
Syntax Description
This command has no arguments or keywords.
Defaults
DHCP snooping trust is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Configure as trusted ports those that are connected to a DHCP server or to other switches or routers. Configure as untrusted ports those that are connected to DHCP clients.
Examples
This example shows how to enable DHCP snooping trust on a port:
Switch(config-if)# ip dhcp snooping trustYou can verify your settings by entering the show ip dhcp snooping privileged EXEC command.
Related Commands
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding information.
ip dhcp snooping verify
Use the ip dhcp snooping verify global configuration command to configure the switch to verify on an untrusted port that the source MAC address in a DHCP packet matches the client hardware address. Use the no form of this command to configure the switch to not verify the MAC addresses.
ip dhcp snooping verify mac-address
no ip dhcp snooping verify mac-address
Syntax Description
This command has no arguments or keywords.
Defaults
The switch verifies the source MAC address in a DHCP packet that is received on untrusted ports matches the client hardware address in the packet.
Command Modes
Global configuration
Command History
Usage Guidelines
In a service-provider network, when a switch receives a packet from a DHCP client on an untrusted port, it automatically verifies that the source MAC address and the DHCP client hardware address match. If the addresses match, the switch forwards the packet. If the addresses do not match, the switch drops the packet.
Examples
This example shows how to disable the MAC address verification:
Switch(config)# no ip dhcp snooping verify mac-addressYou can verify your settings by entering the show ip dhcp snooping privileged EXEC command.
Related Commands
ip dhcp snooping vlan
Use the ip dhcp snooping vlan global configuration command to enable DHCP snooping on a VLAN. Use the no form of this command to disable DHCP snooping on a VLAN.
ip dhcp snooping vlan vlan-range
no ip dhcp snooping vlan vlan-range
Syntax Description
Defaults
DHCP snooping is disabled on all VLANs.
Command Modes
Global configuration
Command History
Usage Guidelines
You must first globally enable DHCP snooping before enabling DHCP snooping on a VLAN.
Examples
This example shows how to enable DHCP snooping on VLAN 10:
Switch(config)# ip dhcp snooping vlan 10You can verify your settings by entering the show ip dhcp snooping privileged EXEC command.
Related Commands
Displays the DHCP snooping configuration.
Displays the DHCP snooping binding information.
ip dhcp snooping vlan information option format-type circuit-id string
Use the ip dhcp snooping vlan information option format-type circuit-id string interface configuration command on the switch to configure the option-82 circuit-ID suboption. Use the no form of this command to configure the default circuit-ID suboption.
ip dhcp snooping vlan vlan information option format-type circuit-id string ASCII-string
no ip dhcp snooping vlan vlan information option format-type circuit-id string
Syntax Description
vlan vlan
Specify the VLAN ID. The range is 1 to 4094.
string ASCII-string
Specify a circuit ID, using from 3 to 63 ASCII characters (no spaces).
Defaults
The switch VLAN and the port identifier, in the format vlan-mod-port, is the default circuit ID.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must globally enable DHCP snooping by using the ip dhcp snooping global configuration command for any DHCP snooping configuration to take effect.
When the option-82 feature is enabled, the default circuit-ID suboption is the switch VLAN and port identifier, in the format vlan-mod-port. This command allows you to configure a string of ASCII characters to be the circuit ID.
Note
Examples
This example shows how to configure the option-82 circuit-ID suboption:
Switch(config-if)# ip dhcp snooping vlan 250 information option format-type circuit-id string customerABC-250-0-0You can verify your settings by entering the show ip dhcp snooping user EXEC command.
Note
Related Commands
Configures the option-82 remote-ID suboption.
Displays the DHCP snooping configuration.
ip igmp filter
Use the ip igmp filter interface configuration command to control whether or not all hosts on a Layer 2 interface can join one or more IP multicast groups by applying an Internet Group Management Protocol (IGMP) profile to the interface. Use the no form of this command to remove the specified profile from the interface.
ip igmp filter profile number
no ip igmp filter
Syntax Description
Defaults
No IGMP filters are applied.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can apply IGMP filters only to Layer 2 physical interfaces; you cannot apply IGMP filters to routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
An IGMP profile can be applied to one or more switch port interfaces, but one port can have only one profile applied to it.
Examples
This example shows how to apply IGMP profile 22 to a port.
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# ip igmp filter 22You can verify your setting by using the show running-config privileged EXEC command and by specifying an interface.
Related Commands
ip igmp max-groups
Use the ip igmp max-groups interface configuration command to set the maximum number of Internet Group Management Protocol (IGMP) groups that a Layer 2 interface can join or to configure the IGMP throttling action when the maximum number of entries is in the forwarding table . Use the no form of this command to set the maximum back to the default, which is to have no maximum limit, or to return to the default throttling action, which is to drop the report.
ip igmp max-groups {number | action {deny | replace}}
no ip igmp max-groups {number | action}
Syntax Description
Defaults
The default maximum number of groups is no limit.
After the switch learns the maximum number of IGMP group entries on an interface, the default throttling action is to drop the next IGMP report that the interface receives and to not add an entry for the IGMP group to the interface.
Command Modes
Interface configuration
Command History
12.1(14)AX
This command was introduced.
12.2(25)EY
The action, deny, and replace keywords were introduced.
Usage Guidelines
You can use this command only on Layer 2 physical interfaces and on logical EtherChannel interfaces. You cannot set IGMP maximum groups for routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
Follow these guidelines when configuring the IGMP throttling action:
•
•
•
Examples
This example shows how to limit to 25 the number of IGMP groups that a port can join.
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# ip igmp max-groups 25This example shows how to configure the switch to replace the existing group with the new group for which the IGMP report was received when the maximum number of entries is in the forwarding table:
Switch(config)# interface gigabitethernet2/0/1Switch(config-if)# ip igmp max-groups action replaceYou can verify your setting by using the show running-config privileged EXEC command and by specifying an interface.
Related Commands
ip igmp profile
Use the ip igmp profile global configuration command to create an Internet Group Management Protocol (IGMP) profile and enter IGMP profile configuration mode. From this mode, you can specify the configuration of the IGMP profile to be used for filtering IGMP membership reports from a switchport. Use the no form of this command to delete the IGMP profile.
ip igmp profile profile number
no ip igmp profile profile number
Syntax Description
Defaults
No IGMP profiles are defined. When configured, the default action for matching an IGMP profile is to deny matching addresses.
Command Modes
Global configuration
Command History
Usage Guidelines
When you are in IGMP profile configuration mode, you can create the profile by using these commands:
•
•
•
•
•
When entering a range, enter the low IP multicast address, a space, and the high IP multicast address.
You can apply an IGMP profile to one or more Layer 2 interfaces, but each interface can have only one profile applied to it.
Examples
This example shows how to configure IGMP profile 40 that permits the specified range of IP multicast addresses:
Switch(config)# ip igmp profile 40Switch(config-igmp-profile)# permitSwitch(config-igmp-profile)# range 233.1.1.1 233.255.255.255You can verify your settings by using the show ip igmp profile privileged EXEC command.
Related Commands
Applies the IGMP profile to the specified interface.
Displays the characteristics of all IGMP profiles or the specified IGMP profile number.
ip igmp snooping
Use the ip igmp snooping global configuration command to globally enable Internet Group Management Protocol (IGMP) snooping on the switch or to enable it on a per-VLAN basis. Use the no form of this command to return to the default setting.
ip igmp snooping [vlan vlan-id]
no ip igmp snooping [vlan vlan-id]
Syntax Description
vlan vlan-id
(Optional) Enable IGMP snooping on the specified VLAN. The range is 1 to 1001 and 1006 to 4094.
Defaults
IGMP snooping is globally enabled on the switch.
IGMP snooping is enabled on VLAN interfaces.
Command Modes
Global configuration
Command History
Usage Guidelines
.When IGMP snooping is enabled globally, it is enabled in all the existing VLAN interfaces. When IGMP snooping is globally disabled, it is disabled on all the existing VLAN interfaces.
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
Examples
This example shows how to globally enable IGMP snooping:
Switch(config)# ip igmp snoopingThis example shows how to enable IGMP snooping on VLAN 1:
Switch(config)# ip igmp snooping vlan 1You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
ip igmp snooping querier
Use the ip igmp snooping querier global configuration command to globally enable the Internet Group Management Protocol (IGMP) querier function in Layer 2 networks. Use the command with keywords to enable and configure the IGMP querier feature on a VLAN interface. Use the no form of this command to return to the default settings.
ip igmp snooping querier [vlan vlan-id] [address ip-address | max-response-time response-time | query-interval interval-count | tcn query [count count | interval interval] | timer expiry | version version]
no ip igmp snooping querier [vlan vlan-id] [address | max-response-time | query-interval | tcn query { count count | interval interval} | timer expiry | version]
Syntax Description
Defaults
The IGMP snooping querier feature is globally disabled on the switch.
When enabled, the IGMP snooping querier disables itself if it detects IGMP traffic from a multicast-enabled device.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enable IGMP snooping to detect the IGMP version and IP address of a device that sends IGMP query messages, which is also called a querier.
By default, the IGMP snooping querier is configured to detect devices that use IGMP Version 2 (IGMPv2) but does not detect clients that are using IGMP Version 1 (IGMPv1). You can manually configure the max-response-time value when devices use IGMPv2. You cannot configure the max-response-time when devices use IGMPv1. (The value cannot be configured and is set to zero).
Non-RFC compliant devices running IGMPv1 might reject IGMP general query messages that have a non-zero value as the max-response-time value. If you want the devices to accept the IGMP general query messages, configure the IGMP snooping querier to run IGMPv1.
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
Examples
This example shows how to globally enable the IGMP snooping querier feature:
Switch(config)# ip igmp snooping querierThis example shows how to set the IGMP snooping querier maximum response time to 25 seconds:
Switch(config)# ip igmp snooping querier max-response-time 25This example shows how to set the IGMP snooping querier interval time to 60 seconds:
Switch(config)# ip igmp snooping querier query-interval 60This example shows how to set the IGMP snooping querier TCN query count to 25:
Switch(config)# ip igmp snooping querier tcn count 25This example shows how to set the IGMP snooping querier timeout to 60 seconds:
Switch(config)# ip igmp snooping querier timeout expiry 60This example shows how to set the IGMP snooping querier feature to version 2:
Switch(config)# ip igmp snooping querier version 2You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
Enables IGMP report suppression.
Displays the IGMP snooping configuration.
Displays IGMP snooping multicast information.
Displays the IGMP snooping router ports.
ip igmp snooping report-suppression
Use the ip igmp snooping report-suppression global configuration command to enable Internet Group Management Protocol (IGMP) report suppression. Use the no form of this command to disable IGMP report suppression and forward all IGMP reports to multicast routers.
ip igmp snooping report-suppression
no ip igmp snooping report-suppression
Syntax Description
This command has no arguments or keywords.
Defaults
IGMP report suppression is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
IGMP report suppression is supported only when the multicast query has IGMPv1 and IGMPv2 reports. This feature is not supported when the query includes IGMPv3 reports.
The switch uses IGMP report suppression to forward only one IGMP report per multicast router query to multicast devices. When IGMP router suppression is enabled (the default), the switch sends the first IGMP report from all hosts for a group to all the multicast routers. The switch does not send the remaining IGMP reports for the group to the multicast routers. This feature prevents duplicate reports from being sent to the multicast devices.
If the multicast router query includes requests only for IGMPv1 and IGMPv2 reports, the switch forwards only the first IGMPv1 or IGMPv2 report from all hosts for a group to all the multicast routers. If the mulitcast router query also includes requests for IGMPv3 reports, the switch forwards all IGMPv1, IGMPv2, and IGMPv3 reports for a group to the multicast devices.
If you disable IGMP report suppression by entering the no ip igmp snooping report-suppression command, all IGMP reports are forwarded to all the multicast routers.
Examples
This example shows how to disable report suppression:
Switch(config)# no ip igmp snooping report-suppressionYou can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
Enables IGMP snooping on the switch or on a VLAN.
Displays the IGMP snooping configuration of the switch or the VLAN.
ip igmp snooping vlan immediate-leave
Use the ip igmp snooping immediate-leave global configuration command to enable Internet Group Management Protocol (IGMP) snooping immediate-leave processing on a per-VLAN basis. Use the no form of this command to return to the default setting.
ip igmp snooping vlan vlan-id immediate-leave
no ip igmp snooping vlan vlan-id immediate-leave
Syntax Description
vlan-id
Enable IGMP snooping and the Immediate-Leave feature on the specified VLAN. The range is 1 to 1001 and 1006 to 4094.
Defaults
IGMP immediate-leave processing is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
You should configure the Immediate- Leave feature only when there is a maximum of one receiver on every port in the VLAN. The configuration is saved in NVRAM.
The Immediate-Leave feature is supported only with IGMP Version 2 hosts.
Examples
This example shows how to enable IGMP immediate-leave processing on VLAN 1:
Switch(config)# ip igmp snooping vlan 1 immediate-leaveYou can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
ip igmp snooping vlan mrouter
Use the ip igmp snooping mrouter global configuration command to add a multicast router port or to configure the multicast learning method. Use the no form of this command to return to the default settings.
ip igmp snooping vlan vlan-id mrouter {interface interface-id | learn {cgmp | pim-dvmrp}}
no ip igmp snooping vlan vlan-id mrouter {interface interface-id | learn {cgmp | pim-dvmrp}}
Syntax Description
Defaults
By default, there are no multicast router ports.
The default learning method is pim-dvmrp—to snoop IGMP queries and PIM-DVMRP packets.
Command Modes
Global configuration
Command History
Usage Guidelines
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
The CGMP learn method is useful for reducing control traffic.
The configuration is saved in NVRAM.
Examples
This example shows how to configure a port as a multicast router port:
Switch(config)# ip igmp snooping vlan 1 mrouter interface gigabitethernet1/0/2This example shows how to specify the multicast router learning method as CGMP:
Switch(config)# ip igmp snooping vlan 1 mrouter learn cgmpYou can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
ip igmp snooping vlan static
Use the ip igmp snooping static global configuration command to enable Internet Group Management Protocol (IGMP) snooping and to statically add a Layer 2 port as a member of a multicast group. Use the no form of this command to remove ports specified as members of a static multicast group.
ip igmp snooping vlan vlan-id static ip-address interface interface-id
no ip igmp snooping vlan vlan-id static ip-address interface interface-id
Syntax Description
Defaults
By default, there are no ports statically configured as members of a multicast group.
Command Modes
Global configuration
Command History
Usage Guidelines
VLAN IDs 1002 to 1005 are reserved for Token Ring and FDDI VLANs and cannot be used in IGMP snooping.
The configuration is saved in NVRAM.
Examples
This example shows how to statically configure a host on an interface:
Switch(config)# ip igmp snooping vlan 1 static 0100.5e02.0203 interface gigabitethernet1/0/1Configuring port gigabitethernet1/0/1 on group 0100.5e02.0203You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
ip source binding
Use the ip source binding global configuration command to configure static IP source bindings on the switch. Use the no form of this command to delete static bindings.
ip source binding mac-address vlan vlan-id ip-address interface interface-id
no source binding mac-address vlan vlan-id ip-address interface interface-id
Syntax Description
Defaults
No IP source bindings are configured.
Command Modes
Global configuration
Command History
Usage Guidelines
A static IP source binding entry has an IP address, its associated MAC address, and its associated VLAN number. The entry is based on the MAC address and the VLAN number. If you modify an entry by changing only the IP address, the switch updates the entry instead creating a new one.
Examples
This example shows how to add a static IP source binding:
Switch(config)# ip source binding 0001.1234.1234 vlan 1 172.20.50.5 interface gigabitethernet1/0/1This example shows how to add a static binding and then modify the IP address for it:
Switch(config)# ip source binding 0001.1357.0007 vlan 1 172.20.50.25 interface gigabitethernet1/0/1Switch(config)# ip source binding 0001.1357.0007 vlan 1 172.20.50.30 interface gigabitethernet1/0/1You can verify your settings by entering the show ip source binding privileged EXEC command.
Related Commands
Enables IP source guard on an interface.
Displays the IP source bindings on the switch.
Displays the IP source guard configuration on the switch or on a specific interface.
ip ssh
Use the ip ssh global configuration command to configure the switch to run Secure Shell (SSH) Version 1 or SSH Version 2. This command is available only when your switch is running the cryptographic (encrypted) software image. Use the no form of this command to return to the default setting.
ip ssh version [1 | 2]
no ip ssh version [1 | 2]
Syntax Description
1
(Optional) Configure the switch to run SSH Version 1 (SSHv1).
2
(Optional) Configure the switch to run SSH Version 2 (SSHv1).
Defaults
The default version is the latest SSH version supported by the SSH client.
Command Modes
Global configuration
Command History
Usage Guidelines
If you do not enter this command or if you do not specify a keyword, the SSH server selects the latest SSH version supported by the SSH client. For example, if the SSH client supports SSHv1 and SSHv2, the SSH server selects SSHv2.
The switch supports an SSHv1 or an SSHv2 server. It also supports an SSHv1 client. For more information about the SSH server and the SSH client, see the software configuration guide for this release.
A Rivest, Shamir, and Adelman (RSA) key pair generated by an SSHv1 server can be used by an SSHv2 server and the reverse.
Examples
This example shows how to configure the switch to run SSH Version 2:
Switch(config)# ip ssh version 2You can verify your settings by entering the show ip ssh or show ssh privileged EXEC command.
Related Commands
ip verify source
Use the ip verify source interface configuration command to enable IP source guard on an interface. Use the no form of this command to disable IP source guard.
ip verify source [port-security]
no ip verify source
Syntax Description
port-security
(Optional) Enable IP source guard with IP and MAC address filtering.
If you do not enter the port-security keyword, IP source guard with IP address filtering is enabled.
Defaults
IP source guard is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
To enable IP source guard with source IP address filtering, use the ip verify source interface configuration command.
To enable IP source guard with source IP and MAC address filtering, use the ip verify source port-security interface configuration command.
To enable IP source guard with source IP and MAC address filtering, you must enable port security on the interface.
Examples
This example shows how to enable IP source guard with source IP address filtering:
Switch(config-if)# ip verify sourceThis example shows how to enable IP source guard with source IP and MAC address filtering:
Switch(config-if)# ip verify source port-securityYou can verify your settings by entering the show ip source binding privileged EXEC command.
Related Commands
Configures static bindings on the switch.
Displays the IP source guard configuration on the switch or on a specific interface.
ip vrf (global configuration)
Use the ip-vrf global configuration command to configure a virtual private network (VPN) routing/forwarding (VRF) routing table and to enter VRF configuration mode. Use the no form of this command to remove a VRF routing table and to return to global configuration mode.
ip vrf vrf-name
no ip vrf vrf-name
Note
Syntax Description
Defaults
No VRFs are defined.
No import or export lists are associated with a VRF.
No route maps are associated with a VRF.
Command Modes
Global configuration or router configuration
Command History
Usage Guidelines
Entering the ip vrf command enables the VRF configuration mode. These configuration commands are available:
•
•
•
•
•
•
•
•
–
–
•
To return to global configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
The switch supports a total of 26 VRFs and VPNs.
Use an import route map when an application requires finer control over the routes imported into a VRF than provided by the import and export extended communities configured for the importing and exporting VRF. The import map command associates a route map with the specified VRF. By using a route map, you can filter routes that are eligible for import into a VRF, based on the route target extended community attributes of the route. The route map might deny access to selected routes from a community that is on the import list.
If you set a maximum routes threshold, the switch rejects routes when the threshold limit is reached. If you enter warn-only, the switch issues a syslog error message when the maximum number of VRF routes exceeds the allowed limit, but still allows additional routes.
An RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN. You must configure a route distinguisher for a VRF to be functional. The RD is added to the beginning of the customer's IPv4 prefixes to change them into globally unique VPN-IPv4 prefixes.
The route target specifies a target VPN extended community. Like a route-distinguisher, an extended community is composed of either an autonomous system number and an arbitrary number or an IP address and an arbitrary number.
The ip vrf vrf-name command creates a VRF routing table and a Cisco Express Forwarding (CEF) forwarding table, both named vrf-name. Associated with these tables is the default route distinguisher value route-distinguisher.
Examples
This example shows how to create the VRF named vpn1, enter VRF configuration mode, and import a route map to the VRF:
Switch(config)# ip vrf vpn1Switch(config-vrf)# rd 100:2Switch(config-vrf)# route-target both 100:2Switch(config-vrf)# route-target import 100:1Related Commands
ip vrf (interface configuration)
Use the ip-vrf interface configuration command to associate a virtual private network (VPN) routing/forwarding (VRF) routing table or a route map with an interface. Use the no form of this command to disassociate the VRF routing table or route map.
ip vrf {forwarding table-name | sitemap route-map-name}
no ip vrf {forwarding table-name | sitemap route-map-name}
Note
Syntax Description
forwarding table-name
Specify a VRF forwarding table name for the interface.
sitemap route-map-name
Specify a VRF route map for routes received from this site.
Defaults
The default for an interface is the global routing table.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ip vrf forwarding command to associate an interface with a VRF. Executing this command on an interface removes the IP address. You should then reconfigure the IP address.
Examples
This example shows how to link the VRF named vpn1 to a port:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# ip vrf forwarding vpn1Related Commands
l2protocol-tunnel
Use the l2protocol-tunnel interface configuration command to enable tunneling of Layer 2 protocols on an access or 802.1Q tunnel port. You can enable tunneling for Cisco Discovery Protocol (CDP), Spanning Tree Protocol (STP), or VLAN Trunking Protocol (VTP) packets, or configure the maximum number of incoming Layer 2 protocol packets to be received before the port is disabled or the interface drops packets. If no keyword is entered, tunneling is enabled for all three Layer 2 protocols. You can also enable point-to-point tunneling for Port Aggregation Protocol (PAgP), Link Aggregation Control Protocol (LACP), or UniDirectional Link Detection (UDLD) packets. Use the no form of this command to disable tunneling on the interface, to return to having no shutdown threshold, or to return to having no drop threshold.
l2protocol-tunnel [cdp | stp | vtp] [point-to-point [pagp | lacp | udld]] | [shutdown-threshold [cdp | stp | vtp] [point-to-point [pagp | lacp | udld]] value] | [drop-threshold [cdp | stp | vtp] [point-to-point [pagp | lacp | udld]] value]
no l2protocol-tunnel [cdp | stp | vtp] [point-to-point [pagp | lacp | udld]] | [shutdown-threshold [cdp | stp | vtp] [point-to-point [pagp | lacp | udld]] value] | [drop-threshold [cdp | stp | vtp] [point-to-point [pagp | lacp | udld]] value]
Syntax Description
Note
Defaults
The default is that no Layer 2 protocol packets are tunneled.
If you enter the command with no keyword, the default is to tunnel CDP, STP, and VTP packets.
If you enable point-to-point protocol tunneling with no keyword is entered, tunneling is enabled for all three point-to-point protocols.
The default is to have no shutdown threshold for the number of Layer 2 protocol packets.
The default is to have no drop threshold for the number of Layer 2 protocol packets.
Command Modes
Interface configuration
Command History
12.1(14)AX
This command was introduced.
12.1(14)AX1
Support was added for the point-to-point [pagp | lacp | udld] keywords.
Usage Guidelines
You must enter this command, with or without protocol types, to tunnel Layer 2 protocol packets.
Layer 2 protocol tunneling across a service-provider network ensures that Layer 2 protocol information is propagated across the network to all customer locations. When protocol tunneling is enabled, protocol packets are encapsulated with a well-known Cisco multicast address for transmission across the network. When the packets reach their destination, the well-known MAC address is replaced by the Layer 2 protocol MAC address.
When Layer 2 protocol tunneling is enabled on ingress ports on a switch, egress trunk ports forward the tunneled packets with a special encapsulation. If you also enable Layer 2 protocol tunneling on the egress trunk port, this behavior is bypassed and the switch forwards control protocol data units (PDUs) without any processing or modification. The Layer 2 protocol-tunnel bypass feature can provide interoperability with third-party vendors. Bypass mode transparently forwards control PDUs to vendor switches that have different ways of controlling protocol tunneling.
You can enable Layer 2 protocol tunneling individually for CDP, STP, VTP, or for all three protocols.
You can enable Layer 2 protocol tunneling on ports that are configured as access ports, 802.1Q tunnel ports, or trunk ports. You cannot enable Layer 2 protocol tunneling on ports configured with switchport mode dynamic auto or dynamic desirable.
EtherChannel port groups are compatible with tunnel ports as long as the 802.1Q configuration is consistent within an EtherChannel port group.
In a service-provider network, you can use Layer 2 protocol tunneling to enhance the creation of EtherChannels by emulating a point-to-point network topology. When protocol tunneling is enabled on the service-provider switch for PAgP or LACP, remote customer switches receive the protocol data units (PDUs) and can negotiate automatic creation of EtherChannels.
To enable tunneling of PAgP, LACP, and UDLD packets, you must have a point-to-point network topology. To decrease the link-down detection time, you should also enable UDLD on the interface when you enable tunneling of PAgP or LACP packets.
Protocol tunneling is disabled by default but can be enabled for the individual protocols on 802.1Q tunnel ports, access ports. or trunk ports
You can enable point-to-point protocol tunneling individually for PAgP, LACP, UDLD, or for all three protocols.
Loopback detection is not supported on Layer 2 protocol tunneling of PAgP, LACP, or UDLD packets.
Caution
Dynamic Trunking Protocol (DTP) is not compatible with Layer 2 protocol tunneling because you must manually configure asymmetric links with tunnel ports and trunk ports.
Edge switches on the outbound side of the service-provider network restore the proper Layer 2 protocol and MAC address information and forward the packets to all tunnel, access, and Layer 2 protocol-enabled trunk ports in the same metro VLAN.
Enter the shutdown-threshold keyword to control the number of protocol packets per second that are received on an interface before it shuts down. When no protocol option is specified with the keyword, the threshold is applied to each of the tunneled Layer 2 protocol types. If you also set a drop threshold on the interface, the shutdown-threshold value must be greater than or equal to the drop-threshold value.
When the shutdown threshold is reached, the interface is error-disabled. If you enabled error recovery by entering the errdisable recovery cause l2ptguard global configuration command, the interface is brought out of the error-disabled state and allowed to retry the operation when all the causes have timed out. If the error recovery mechanism is not enabled for l2ptguard, the interface stays in the error-disabled state until you enter the shutdown and no shutdown interface configuration commands.
Enter the drop-threshold keyword to control the number of protocol packets per second that are received on an interface before it drops packets. When no protocol option is specified with a keyword, the threshold is applied to each of the tunneled Layer 2 protocol types. If you also set a shutdown threshold on the interface, the drop-threshold value must be less than or equal to the shutdown-threshold value.
When the drop threshold is reached, the interface drops Layer 2 protocol packets until the rate at which they are received is below the drop threshold.
The configuration is saved in NVRAM.
Note
Examples
This example shows how to enable protocol tunneling for CDP packets and to configure the shutdown threshold as 50 packets per second:
Switch(config-if)# l2protocol-tunnel cdpSwitch(config-if)# l2protocol-tunnel shutdown-threshold cdp 50This example shows how to enable protocol tunneling for STP packets and to configure the drop threshold as 400 packets per second:
Switch(config-if)# l2protocol-tunnel stpSwitch(config-if)# l2protocol-tunnel drop-threshold stp 400This example shows how to enable point-to-point protocol tunneling for PAgP and UDLD packets and to configure the PAgP drop threshold as 1000 packets per second:
Switch(config-if)# l2protocol-tunnel point-to-point pagpSwitch(config-if)# l2protocol-tunnel point-to-point udldSwitch(config-if)# l2protocol-tunnel drop-threshold point-to-point pagp 1000Related Commands
l2protocol-tunnel cos
Use the l2protocol-tunnel cos global configuration command to configure a class of service (CoS) value for all tunneled Layer 2 protocol packets. Use the no form of this command to return to the default value of 5.
l2protocol-tunnel cos value
no l2protocol-tunnel cos
Syntax Description
Defaults
The default is to use the CoS value configured for data on the interface. If no CoS value is configured, the default is 5 for all tunneled Layer 2 protocol packets.
Command Modes
Global configuration
Command History
Usage Guidelines
When enabled, the tunneled Layer 2 protocol packets use the configured CoS value.
The value is saved in NVRAM.
Examples
This example shows how to configure a Layer-2 protocol-tunnel CoS value of 7:
Switch(config)# l2protocol-tunnel cos 7Related Commands
Displays information about ports configured for Layer 2 protocol tunneling, including CoS.
lacp port-priority
Use the lacp port-priority interface configuration command to configure the port priority for the Link Aggregation Control Protocol (LACP). Use the no form of this command to return to the default setting.
lacp port-priority priority
no lacp port-priority
Syntax Description
Defaults
The default is 32768.
Command Modes
Interface configuration
Command History
Usage Guidelines
The lacp port-priority interface configuration command determines which ports are bundled and which ports are put in hot-standby mode when there are more than eight ports in an LACP channel group.
An LACP channel group can have up to 16 Ethernet ports of the same type. Up to eight ports can be active, and up to eight ports can be in standby mode.
In port-priority comparisons, a numerically lower value has a higher priority: When there are more than eight ports in an LACP channel-group, the eight ports with the numerically lowest values (highest priority values) for LACP port priority are bundled into the channel group, and the lower-priority ports are put in hot-standby mode. If two or more ports have the same LACP port priority (for example, they are configured with the default setting of 65535) an internal value for the port number determines the priority.
Note
Use the show lacp internal privileged EXEC command to display LACP port priorities and internal port number values.
For information about configuring LACP on physical ports, see the "Configuring EtherChannels" chapter in the software configuration guide for this release.
Examples
This example shows how to configure the LACP port priority on a port:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# lacp port-priority 1000You can verify your settings by entering the show lacp [channel-group-number] internal privileged EXEC command.
Related Commands
Assigns an Ethernet port to an EtherChannel group.
Configures the LACP system priority.
show lacp [channel-group-number] internal
Displays internal information for all channel groups or for the specified channel group.
lacp system-priority
Use the lacp system-priority global configuration command to configure the system priority for the Link Aggregation Control Protocol (LACP). Use the no form of this command to return to the default setting.
lacp system-priority priority
no lacp system-priority
Syntax Description
Defaults
The default is 32768.
Command Modes
Global configuration
Command History
Usage Guidelines
The lacp system-priority command determines which switch in an LACP link controls port priorities.
An LACP channel group can have up to 16 Ethernet ports of the same type. Up to eight ports can be active, and up to eight ports can be in standby mode. When there are more than eight ports in an LACP channel-group, the switch on the controlling end of the link uses port priorities to determine which ports are bundled into the channel and which ports are put in hot-standby mode. Port priorities on the other switch (the noncontrolling end of the link) are ignored.
In priority comparisons, numerically lower values have higher priority. Therefore, the system with the numerically lower value (higher priority value) for LACP system priority becomes the controlling system. If both switches have the same LACP system priority (for example, they are both configured with the default setting of 32768), the LACP system ID (the switch MAC address) determines which switch is in control.
The lacp system-priority command applies to all LACP EtherChannels on the switch.
Use the show etherchannel summary privileged EXEC command to see which ports are in the hot-standby mode (denoted with an H port-state flag in the output display).
For more information about configuring LACP on physical ports, see the "Configuring EtherChannels" chapter in the software configuration guide for this release.
Examples
This example shows how to set the LACP system priority:
Switch(config)# lacp system-priority 20000You can verify your settings by entering the show lacp sys-id privileged EXEC command.
Related Commands
Assigns an Ethernet port to an EtherChannel group.
Configures the LACP port priority.
show lacp sys-id
Display the system identifier that is being used by LACP.
link state group
Use the link state group interface configuration command to configure a port as a member of a link-state group. Use the no form of this command to remove the port from the link-state group.
link state group [number] {upstream | downstream}
no link state group [number] {upstream | downstream}
Syntax Description
Defaults
The default group is group 1.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the link state group interface configuration command to configure a port as an upstream or downstream port for a specific link-state group. If the group number is omitted, the default group is assumed.
An interface can be an aggregation of ports (an EtherChannel), a single switch port in access or trunk mode, or a routed port. Each downstream interface can be associated with one or more upstream interfaces. Upstream interfaces can be bundled together, and each downstream interface can be associated with a single group consisting of multiple upstream interfaces, referred to as link-state groups.
The link state of the downstream interfaces are dependent on the link state of the upstream interfaces in the associated link-state group. If all of the upstream interfaces in a link-state group are in a link-down state, the associated downstream interfaces are forced into a link-down state. If any one of the upstream interfaces in the link-state group is in a link-up state, the associated downstream interfaces are allowed to change to, or remain in, a link-up state.
Follow these guidelines to avoid configuration problems:
•
•
•
Examples
This example shows how to configure the interfaces as upstream in group 2:
Switch# configure terminalSwitch(config)# interface range fastethernet1/0/11 - 14Switch(config-if-range)# link state group 2 downstreamSwitch(config-if-range)# endSwitch(config-if)# endYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
link state track
Use the link state track user EXEC command to enable a link-state group. Use the no form of this command to disable a link-state group.
link state track [number]
no link state track [number]
Syntax Description
number
(Optional) Specify the link-state group number. The group number can be 1 to 10. The default is 1.
Defaults
Link-state tracking is disabled for all groups.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the link state track global configuration command to enable a link-state group.
Examples
This example shows how enable link-state group 2:
Switch(config)# link state track 2You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
logging event
Use the logging event interface configuration command to enable notification of interface link status changes. Use the no form of this command to disable notification.
logging event {bundle-status | link-status | spanning-tree | status | trunk status}
no logging event {bundle-status | link-status | spanning-tree | status | trunk status}
Syntax Description
Defaults
Event logging is disabled.
Command Modes
Interface configuration
Command History
Examples
This example shows how to enable spanning-tree logging:
Switch(config-if)# logging event spanning-treelogging file
Use the logging file global configuration command to set logging file parameters. Use the no form of this command to return to the default setting.
logging file filesystem:filename [max-file-size [min-file-size]] [severity-level-number | type]
no logging file filesystem:filename [severity-level-number | type]
Syntax Description
Defaults
The minimum file size is 2048 bytes; the maximum file size is 4096 bytes.
The default severity level is 7 (debugging messages and numerically lower levels).
Command Modes
Global configuration
Command History
Usage Guidelines
The log file is stored in ASCII text format in an internal buffer on the switch. You can access logged system messages by using the switch command-line interface (CLI) or by saving them to a properly configured syslog server. If the switch fails, the log is lost unless you had previously saved it to flash memory by using the logging file flash:filename global configuration command.
After saving the log to flash memory by using the logging file flash:filename global configuration command, you can use the more flash:filename privileged EXEC command to display its contents.
The command rejects the minimum file size if it is greater than the maximum file size minus 1024; the minimum file size then becomes the maximum file size minus 1024.
Specifying a level causes messages at that level and numerically lower levels to be displayed.
Examples
This example shows how to save informational log messages to a file in flash memory:
Switch(config)# logging file flash:logfile informationalYou can verify your setting by entering the show running-config privileged EXEC command.
Related Commands
mac access-group
Use the mac access-group interface configuration command to apply a MAC access control list (ACL) to a Layer 2 interface. Use the no form of this command to remove all MAC ACLs or the specified MAC ACL from the interface. You create the MAC ACL by using the mac access-list extended global configuration command.
mac access-group {name} in
no mac access-group
Syntax Description
name
Specify a named MAC access list.
in
Specify that the ACL is applied in the ingress direction. Outbound ACLs are not supported on Layer 2 interfaces.
Defaults
No MAC ACL is applied to the interface.
Command Modes
Interface configuration (Layer 2 interfaces only)
Command History
Usage Guidelines
You can apply MAC ACLs only to ingress Layer 2 interfaces. You cannot apply MAC ACLs to Layer 3 interfaces.
On Layer 2 interfaces, you can filter IP traffic by using IP access lists and non-IP traffic by using MAC access lists. You can filter both IP and non-IP traffic on the same Layer 2 interface by applying both an IP ACL and a MAC ACL to the interface. You can apply no more than one IP access list and one MAC access list to the same Layer 2 interface.
If a MAC ACL is already configured on a Layer 2 interface and you apply a new MAC ACL to the interface, the new ACL replaces the previously configured one.
If you apply an ACL to a Layer 2 interface on a switch, and the switch has an input Layer 3 ACL or a VLAN map applied to a VLAN that the interface is a member of, the ACL applied to the Layer 2 interface takes precedence.
When an inbound packet is received on an interface with a MAC ACL applied, the switch checks the match conditions in the ACL. If the conditions are matched, the switch forwards or drops the packet, according to the ACL.
If the specified ACL does not exist, the switch forwards all packets.
Note
Examples
This example shows how to apply a MAC extended ACL named macacl2 to a port:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# mac access-group macacl2 inYou can verify your settings by entering the show mac access-group privileged EXEC command. You can view configured ACLs on the switch by entering the show access-lists privileged EXEC command.
Related Commands
mac access-list extended
Use the mac access-list extended global configuration command to create an access list based on MAC addresses for non-IP traffic. Using this command puts you in the extended MAC access list configuration mode. Use the no form of this command to return to the default setting.
Note
mac access-list extended name
no mac access-list extended name
Syntax Description
Defaults
By default, there are no MAC access lists created.
Command Modes
Global configuration
Command History
Usage Guidelines
MAC named extended lists are used with VLAN maps and class maps.
You can apply named MAC extended ACLs to VLAN maps or to Layer 2 interfaces; you cannot apply named MAC extended ACLs to Layer 3 interfaces.
Entering the mac access-list extended command enables the MAC-access list configuration mode. These configuration commands are available:
•
•
•
•
•
Note
Examples
This example shows how to create a MAC named extended access list named mac1 and to enter extended MAC access list configuration mode:
Switch(config)# mac access-list extended mac1Switch(config-ext-macl)#This example shows how to delete MAC named extended access list mac1:
Switch(config)# no mac access-list extended mac1You can verify your settings by entering the show access-lists privileged EXEC command.
Related Commands
mac address-table aging-time
Use the mac address-table aging-time global configuration command to set the length of time that a dynamic entry remains in the MAC address table after the entry is used or updated. Use the no form of this command to return to the default setting. The aging time applies to all VLANs or a specified VLAN.
mac address-table aging-time {0 | 10-1000000} [vlan vlan-id]
no mac address-table aging-time {0 | 10-1000000} [vlan vlan-id]
Syntax Description
Defaults
The default is 300 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
If hosts do not send continuously, increase the aging time to record the dynamic entries for a longer time. Increasing the time can reduce the possibility of flooding when the hosts send again.
If you do not specify a specific VLAN, this command sets the aging time for all VLANs.
Examples
This example shows how to set the aging time to 200 seconds for all VLANs:
Switch(config)# mac address-table aging-time 200You can verify your setting by entering the show mac address-table aging-time privileged EXEC command.
Related Commands
mac address-table learning vlan
Use the mac address-table learning global configuration command to enable MAC address learning on a VLAN. This is the default state. Use the no form of this command to disable MAC address learning on a VLAN to control which VLANs can learn MAC addresses.
mac address-table learning vlan vlan-id
no mac address-table notification vlan vlan-id
Syntax Description
Defaults
By default, MAC address learning is enabled on all VLANs.
Command Modes
Global configuration
Command History
Usage Guidelines
Customers in a service provider network can tunnel a large number of MAC addresses through the network and fill the available MAC address table space. When you control MAC address learning on a VLAN, you can manage the available MAC address table space by controlling which VLANs, and therefore which ports, can learn MAC addresses.
Before you disable MAC address learning, be sure that you are familiar with the network topology and the switch system configuration. Disabling MAC address learning on a VLAN could cause flooding in the network. For example, if you disable MAC address learning on a VLAN with a configured switch virtual interface (SVI), the switch floods all IP packets in the Layer 2 domain. If you disable MAC address learning on a VLAN that includes more than two ports, every packet entering the switch is flooded in that VLAN domain. We recommend that you disable MAC address learning only in VLANs that contain two ports and that you use caution before disabling MAC address learning on a VLAN with an SVI.
You cannot disable MAC address learning on a VLAN that the switch uses internally. If the VLAN ID that you enter in the no mac address-table learning vlan vlan-id command is an internal VLAN, the switch generates an error message and rejects the command. To view used internal VLANs, enter the show vlan internal usage privileged EXEC command.
If you disable MAC address learning on a VLAN configured as a private VLAN primary or secondary VLAN, the MAC addresses are still learned on the other VLAN (primary or secondary) that belongs to the private VLAN.
You cannot disable MAC address learning on an RSPAN VLAN. The configuration is not allowed.
If you disable MAC address learning on a VLAN that includes a secure port, MAC address learning is not disabled on the secure port. If you later disable port security on the interface, the disabled MAC address learning state becomes active.
To display MAC address learning status of all VLANs or a specified VLAN, enter the show mac-address-table learning [vlan vlan-id command].
Examples
This example shows how to disable MAC address learning on VLAN 2003:
Switch(config)# no mac address-table learning vlan 2003To display MAC address learning status of all VLANs or a specified VLAN, enter the show mac address-table learning [vlan vlan-id] command.
Related Commands
mac address-table move update
Use the mac address-table move update global configuration command to enable the MAC address-table move update feature. Use the no form of this command to return to the default setting.
mac address-table move update {receive | transmit}
no mac address-table move update {receive | transmit}
Syntax Description
Command Modes
Global configuration.
Defaults
By default, the MAC address-table move update feature is disabled.
Command History
Usage Guidelines
The MAC address-table move update feature allows the switch to provide rapid bidirectional convergence if a primary (forwarding) link goes down and the standby link begins forwarding traffic.
You can configure the access switch to send the MAC address-table move update messages if the primary link goes down and the standby link comes up. You can configure the uplink switches to receive and process the MAC address-table move update messages.
Examples
This example shows how to configure an access switch to send MAC address-table move update messages:
Switch# configure terminalSwitch(conf)# mac address-table move update transmitSwitch(conf)# endThis example shows how to configure an uplink switch to get and process MAC address-table move update messages:
Switch# configure terminalSwitch(conf)# mac address-table move update receiveSwitch(conf)# endYou can verify your settings by entering the show mac address-table move update privileged EXEC command.
Related Commands
mac address-table notification
Use the mac address-table notification global configuration command to enable the MAC address notification feature on the switch. Use the no form of this command to return to the default setting.
mac address-table notification [history-size value] | [interval value]
no mac address-table notification [history-size | interval]
Syntax Description
Defaults
By default, the MAC address notification feature is disabled.
The default trap interval value is 1 second.
The default number of entries in the history table is 1.
Command Modes
Global configuration
Command History
Usage Guidelines
The MAC address notification feature sends Simple Network Management Protocol (SNMP) traps to the network management system (NMS) whenever a new MAC address is added or an old address is deleted from the forwarding tables. MAC notifications are generated only for dynamic and secure MAC addresses. Events are not generated for self addresses, multicast addresses, or other static addresses.
When you configure the history-size option, the existing MAC address history table is deleted, and a new table is created.
You enable the MAC address notification feature by using the mac address-table notification command. You must also enable MAC address notification traps on an interface by using the snmp trap mac-notification interface configuration command and configure the switch to send MAC address traps to the NMS by using the snmp-server enable traps mac-notification global configuration command.
Examples
This example shows how to enable the mac address-table notification feature, set the interval time to 60 seconds, and set the history size to 100 entries:
Switch(config)# mac address-table notificationSwitch(config)# mac address-table notification interval 60Switch(config)# mac address-table notification history-size 100You can verify your settings by entering the show mac address-table notification privileged EXEC command.
Related Commands
clear mac address-table notification
Clears the MAC address notification global counters.
Displays the MAC address notification settings on all interfaces or on the specified interface.
Sends the SNMP MAC notification traps when the mac-notification keyword is appended.
Enables the SNMP MAC notification trap on a specific interface.
mac address-table static
Use the mac address-table static global configuration command to add static addresses to the MAC address table. Use the no form of this command to remove static addresses from the table.
mac address-table static mac-addr vlan vlan-id interface interface-id
no mac address-table static mac-addr vlan vlan-id interface interface-id
Syntax Description
Defaults
No static addresses are configured.
Command Modes
Global configuration
Command History
Examples
This example shows how to add the static address c2f3.220a.12f4 to the MAC address table. When a packet is received in VLAN 4 with this MAC address as its destination, the packet is forwarded to the specified interface.
Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 interface gigabitethernet1/0/1You can verify your setting by entering the show mac address-table privileged EXEC command.
Related Commands
mac address-table static drop
Use the mac address-table static drop global configuration command to enable unicast MAC address filtering and to configure the switch to drop traffic with a specific source or destination MAC address. Use the no form of this command to return to the default setting.
mac address-table static mac-addr vlan vlan-id drop
no mac address-table static mac-addr vlan vlan-id
Syntax Description
Defaults
Unicast MAC address filtering is disabled. The switch does not drop traffic for specific source or destination MAC addresses.
Command Modes
Global configuration
Command History
Usage Guidelines
Follow these guidelines when using this feature:
•
•
For example, if you enter the mac address-table static mac-addr vlan vlan-id interface interface-id global configuration command followed by the mac address-table static mac-addr vlan vlan-id drop command, the switch drops packets with the specified MAC address as a source or destination.
If you enter the mac address-table static mac-addr vlan vlan-id drop global configuration command followed by the mac address-table static mac-addr vlan vlan-id interface interface-id command, the switch adds the MAC address as a static address.
Examples
This example shows how to enable unicast MAC address filtering and to configure the switch to drop packets that have a source or destination address of c2f3.220a.12f4. When a packet is received in VLAN 4 with this MAC address as its source or destination, the packet is dropped:
Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 dropThis example shows how to disable unicast MAC address filtering:
Switch(config)# no mac address-table static c2f3.220a.12f4 vlan 4You can verify your setting by entering the show mac address-table static privileged EXEC command.
Related Commands
macro apply
Use the macro apply interface configuration command to apply a macro to an interface or to apply and trace a macro configuration on an interface.
macro {apply | trace} macro-name [parameter {value}] [parameter {value}]
[parameter {value}]Syntax Description
Defaults
This command has no default setting.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can use the macro trace macro-name interface configuration command to apply and show the macros running on an interface or to debug the macro to find any syntax or configuration errors.
If a command fails because of a syntax error or a configuration error when you apply a macro, the macro continues to apply the remaining commands to the interface.
When creating a macro that requires the assignment of unique values, use the parameter value keywords to designate values specific to the interface.
Keyword matching is case sensitive. All matching occurrences of the keyword are replaced with the corresponding value. Any full match of a keyword, even if it is part of a larger string, is considered a match and is replaced by the corresponding value.
Some macros might contain keywords that require a parameter value. You can use the macro apply macro-name ? command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied.
There are Cisco-default Smartports macros embedded in the switch software. You can display these macros and the commands they contain by using the show parser macro user EXEC command.
Follow these guidelines when you apply a Cisco-default Smartports macro on an interface:
•
•
The Cisco-default macros use the $ character to help identify required keywords. There is no restriction on using the $ character to define keywords when you create a macro.
When you apply a macro to an interface, the macro name is automatically added to the interface. You can display the applied commands and macro names by using the show running-configuration interface interface-id user EXEC command.
A macro applied to an interface range behaves the same way as a macro applied to a single interface. When you use an interface range, the macro is applied sequentially to each interface within the range. If a macro command fails on one interface, it is still applied to the remaining interfaces.
You can delete a macro-applied configuration on an interface by entering the default interface interface-id interface configuration command.
Examples
After you have created a macro by using the macro name global configuration command, you can apply it to an interface. This example shows how to apply a user-created macro called duplex to an interface:
Switch(config-if)# macro apply duplexTo debug a macro, use the macro trace interface configuration command to find any syntax or configuration errors in the macro as it is applied to an interface. This example shows how troubleshoot the user-created macro called duplex on an interface:
Switch(config-if)# macro trace duplexApplying command...`duplex auto'%Error Unknown error.Applying command...`speed nonegotiate'This example shows how to display the Cisco-default cisco-desktop macro and how to apply the macro and set the access VLAN ID to 25 on an interface:
Switch# show parser macro cisco-desktop--------------------------------------------------------------Macro name : cisco-desktopMacro type : default# Basic interface - Enable data VLAN only# Recommended value for access vlan (AVID) should not be 1switchport access vlan $AVIDswitchport mode access# Enable port security limiting port to a single# MAC address -- that of desktopswitchport port-securityswitchport port-security maximum 1# Ensure port-security age is greater than one minute# and use inactivity timerswitchport port-security violation restrictswitchport port-security aging time 2switchport port-security aging type inactivity# Configure port as an edge network portspanning-tree portfastspanning-tree bpduguard enable--------------------------------------------------------------Switch#Switch# configure terminalSwitch(config)# interface fastethernet1/0/4Switch(config-if)# macro apply cisco-desktop $AVID 25Related Commands
macro description
Use the macro description interface configuration command to enter a description about which macros are applied to an interface. Use the no form of this command to remove the description.
macro description text
no macro description text
Syntax Description
Defaults
This command has no default setting.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the description keyword to associate comment text, or the macro name, with an interface. When multiple macros are applied on a single interface, the description text will be from the last applied macro.
This example shows how to add a description to an interface:
Switch(config-if)# macro description duplex settingsYou can verify your settings by entering the show parser macro description privileged EXEC command.
Related Commands
macro global
Use the macro global global configuration command to apply a macro to a switch or to apply and trace a macro configuration on a switch.
macro global {apply | trace} macro-name [parameter {value}] [parameter {value}]
[parameter {value}]Syntax Description
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
Usage Guidelines
You can use the macro trace macro-name global configuration command to apply and to show the macros running on a switch or to debug the macro to find any syntax or configuration errors.
If a command fails because of a syntax error or a configuration error when you apply a macro, the macro continues to apply the remaining commands to the switch.
When creating a macro that requires the assignment of unique values, use the parameter value keywords to designate values specific to the switch.
Keyword matching is case sensitive. All matching occurrences of the keyword are replaced with the corresponding value. Any full match of a keyword, even if it is part of a larger string, is considered a match and is replaced by the corresponding value.
Some macros might contain keywords that require a parameter value. You can use the macro global apply macro-name ? command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied.
There are Cisco-default Smartports macros embedded in the switch software. You can display these macros and the commands they contain by using the show parser macro user EXEC command.
Follow these guidelines when you apply a Cisco-default Smartports macro on a switch:
•
•
The Cisco-default macros use the $ character to help identify required keywords. There is no restriction on using the $ character to define keywords when you create a macro.
When you apply a macro to a switch, the macro name is automatically added to the switch. You can display the applied commands and macro names by using the show running-configuration user EXEC command.
You can delete a global macro-applied configuration on a switch only by entering the no version of each command contained in the macro.
Examples
After you have created a new macro by using the macro name global configuration command, you can apply it to a switch. This example shows how see the snmp macro and how to apply the macro and set the hostname to test-server and set the IP precedence value to 7:
Switch# show parser macro name snmpMacro name : snmpMacro type : customizable#enable port security, linkup, and linkdown trapssnmp-server enable traps port-securitysnmp-server enable traps linkupsnmp-server enable traps linkdown#set snmp-server hostsnmp-server host ADDRESS#set SNMP trap notifications precedencesnmp-server ip precedence VALUE--------------------------------------------------Switch(config)# macro global apply snmp ADDRESS test-server VALUE 7To debug a macro, use the macro global trace global configuration command to find any syntax or configuration errors in the macro when it is applied to a switch. In this example, the ADDRESS parameter value was not entered, causing the snmp-server host command to fail while the remainder of the macro is applied to the switch:
Switch(config)# macro global trace snmp VALUE 7Applying command...`snmp-server enable traps port-security'Applying command...`snmp-server enable traps linkup'Applying command...`snmp-server enable traps linkdown'Applying command...`snmp-server host'%Error Unknown error.Applying command...`snmp-server ip precedence 7'Related Commands
macro global description
Use the macro global description global configuration command to enter a description about the macros that are applied to the switch. Use the no form of this command to remove the description.
macro global description text
no macro global description text
Syntax Description
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the description keyword to associate comment text, or the macro name, with a switch. When multiple macros are applied on a switch, the description text will be from the last applied macro.
This example shows how to add a description to a switch:
Switch(config)# macro global description udld aggressive mode enabledYou can verify your settings by entering the show parser macro description privileged EXEC command.
Related Commands
macro name
Use the macro name global configuration command to create a configuration macro. Use the no form of this command to delete the macro definition.
macro name macro-name
no macro name macro-name
Syntax Description
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
Usage Guidelines
A macro can contain up to 3000 characters. Enter one macro command per line. Use the @ character to end the macro. Use the # character at the beginning of a line to enter comment text within the macro.
You can define mandatory keywords within a macro by using a help string to specify the keywords. Enter # macro keywords word to define the keywords that are available for use with the macro. You can enter up to three help string keywords separated by a space. If you enter more than three macro keywords, only the first three are shown.
Macro names are case sensitive. For example, the commands macro name Sample-Macro and macro name sample-macro will result in two separate macros.
When creating a macro, do not use the exit or end commands or change the command mode by using interface interface-id. This could cause commands that follow exit, end, or interface interface-id to execute in a different command mode.
The no form of this command only deletes the macro definition. It does not affect the configuration of those interfaces on which the macro is already applied. You can delete a macro-applied configuration on an interface by entering the default interface interface-id interface configuration command. Alternatively, you can create an anti-macro for an existing macro that contains the no form of all the corresponding commands in the original macro. Then apply the anti-macro to the interface.
You can modify a macro by creating a new macro with the same name as the existing macro. The newly created macro overwrites the existing macro but does not affect the configuration of those interfaces on which the original macro was applied.
Examples
This example shows how to create a macro that defines the duplex mode and speed:
Switch(config)# macro name duplexEnter macro commands one per line. End with the character `@'.duplex fullspeed auto@This example shows how create a macro with # macro keywords:
Switch(config)# macro name testswitchport access vlan $VLANIDswitchport port-security maximum $MAX#macro keywords $VLANID $MAX@This example shows how to display the mandatory keyword values before you apply the macro to an interface:
switch(config)# interface fa1/0/1switch(config-if)# macro apply test ?WORD keyword to replace with a value e.g $VLANID,$MAX<cr>Switch(config-if)# macro apply test $VLANID ?WORD Value of first keyword to replaceSwitch(config-if)# macro apply test $VLANID 2WORD keyword to replace with a value e.g $VLANID,$MAX<cr>Switch(config-if)# macro apply test $VLANID 2 $MAX ?WORD Value of second keyword to replaceRelated Commands
match (access-map configuration)
Use the match access-map configuration command to set the VLAN map to match packets against one or more access lists. Use the no form of this command to remove the match parameters.
match {ip address {name | number} [name | number] [name | number]...} | {mac address {name} [name] [name]...}
no match {ip address {name | number} [name | number] [name | number]...} | {mac address {name} [name] [name]...}
Syntax Description
Defaults
The default action is to have no match parameters applied to a VLAN map.
Command Modes
Access-map configuration
Command History
Usage Guidelines
You enter access-map configuration mode by using the vlan access-map global configuration command.
You must enter one access list name or number; others are optional. You can match packets against one or more access lists. Matching any of the lists counts as a match of the entry.
In access-map configuration mode, use the match command to define the match conditions for a VLAN map applied to a VLAN. Use the action command to set the action that occurs when the packet matches the conditions.
Packets are matched only against access lists of the same protocol type; IP packets are matched against IP access lists, and all other packets are matched against MAC access lists.
Both IP and MAC addresses can be specified for the same map entry.
Examples
This example shows how to define and apply a VLAN access map vmap4 to VLANs 5 and 6 that will cause the interface to drop an IP packet if the packet matches the conditions defined in access list al2:
Switch(config)# vlan access-map vmap4Switch(config-access-map)# match ip address al2Switch(config-access-map)# action dropSwitch(config-access-map)# exitSwitch(config)# vlan filter vmap4 vlan-list 5-6You can verify your settings by entering the show vlan access-map privileged EXEC command.
Related Commands
match (class-map configuration)
Use the match class-map configuration command to define the match criteria for a class map. Use the no form of this command to remove the match criteria.
match {access-group acl-index-or-name | cos [inner] cos-list | input-interface interface-id-list | ip dscp dscp-list | ip precedence ip-precedence-list | mpls experimental exp-list | vlan [inner] vlan-id}
no match {access-group acl-index-or-name | cos [inner] cos-list | input-interface interface-id-list | ip dscp dsc-list | ip precedence ip-precedence-list | mpls experimental exp-list | vlan [inner] vlan-id}
Syntax Description
Note
Defaults
No match criteria are defined.
Command Modes
Class-map configuration
Command History
12.1(14)AX
This command was introduced.
12.2(25)EY
The inner and the input-interface keywords were added.
Usage Guidelines
Before entering the match command, you must first enter the class-map global configuration command to specify the name of the class whose match criteria you want to establish. The match command is used to specify which fields in the packets are examined to classify the packets. If a packet matches the specified criteria, the packet is considered a member of the class and is forwarded according to the quality of service (QoS) specifications set in the traffic policy.
For the match ip dscp dscp-list or the match ip precedence ip-precedence-list command, you can enter a mnemonic name for a commonly used value. For example, you can enter the match ip dscp af11 command, which is the same as entering the match ip dscp 10 command. You can enter the match ip precedence critical command, which is the same as entering the match ip precedence 5 command. For a list of supported mnemonics, enter the match ip dscp ? or the match ip precedence ? command to see the command-line help strings.
You can configure the match cos [inner] cos-list, match ip dscp dscp-list, match ip precedence ip-precedence-list, match mpls experimental exp-list, or the match vlan command in a class map within a policy map attached to an enhanced-services (ES) port. The match access-group acl-index-or-name command is not supported in an egress policy attached to an ES port or in a hierarchical ingress policy attached to an ES port. You can configure only the match access-group acl-index-or-name command and the match input-interface interface-id-list command in a single-level ingress policy map attached to a standard port or to an ES port.
The match cos inner cos-list command has no effect on non-802.1Q tunneling traffic.
If you want to match the CoS of traffic received on an ES port that is in 802.1Q tunneling mode, use the match cos cos-list command rather than the match cos inner cos-list command. The traffic is not tagged twice at the time that the match takes place.
You cannot mix VLAN-level and class-level matches within a class map.
To configure a class map that matches an 802.1Q tunneling pair (instead of matching a single VLAN), you must configure the class-map global configuration command with the match-all keyword. You must enter the match vlan command before the match vlan inner command.
If you enter the match vlan or the match vlan inner command, the class-map match-any command is not supported.
Use the input-interface interface-id-list keyword when you are configuring an interface-level class map in a hierarchical dual-level policy map. For the interface-id-list, you can specify up to six entries.
Packets that do not meet any of the matching criteria are classified as members of the default traffic class. You configure it by specifying class-default as the class name in the class policy-map configuration command. For more information, see the "class" section.
Examples
This example shows how to create a class map called class2, which matches all the inbound traffic with DSCP values of 10, 11, and 12:
Switch(config)# class-map class2Switch(config-cmap)# match ip dscp 10 11 12Switch(config-cmap)# exitThis example shows how to create a class map called class3, which matches all the inbound traffic with IP-precedence values of 5, 6, and 7:
Switch(config)# class-map class3Switch(config-cmap)# match ip precedence 5 6 7Switch(config-cmap)# exitThis example shows how to create a class map called dot1q, which matches all outbound traffic with an outer VLAN ID of 5 and an inner VLAN ID of 3 to 8:
Switch(config)# class-map match-all dot1qSwitch(config-cmap)# match vlan 5Switch(config-cmap)# match vlan inner 3 - 8Switch(config-cmap)# exitThis example shows how to delete the IP-precedence match criteria and to classify traffic using acl1:
Switch(config)# class-map class2Switch(config-cmap)# match ip precedence 5 6 7Switch(config-cmap)# no match ip precedenceSwitch(config-cmap)# match access-group acl1Switch(config-cmap)# exitThis example shows how to specify a list of physical ports to which an interface-level class map in a hierarchical dual-level policy map applies:
Switch(config)# class-map match-all class4Switch(config-cmap)# match input-interface gigabitethernet1/0/1 gigabitethernet1/0/2Switch(config-cmap)# exitThis example shows how to specify a range of physical ports to which an interface-level class map in a dual-level policy map applies:
Switch(config)# class-map match-all class4Switch(config-cmap)# match input-interface gigabitethernet1/0/1 - gigabitethernet1/0/2Switch(config-cmap)# exitYou can verify your settings by entering the show class-map privileged EXEC command.
Related Commands
Creates a class map to be used for matching packets to the class whose name you specify.
Displays QoS class maps.
mdix auto
Use the mdix auto interface configuration command to enable the automatic medium-dependent-interface crossover (Auto-MDIX) feature on the interface. When Auto-MDIX is enabled, the interface automatically detects the required cable connection type (straight-through or crossover) and configures the connection appropriately. Use the no form of this command to disable Auto-MDIX.
mdix auto
no mdix
Syntax Description
This command has no arguments or keywords.
Defaults
The default is Auto-MDIX is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enable Auto-MDIX on an interface, you must also set the interface speed and duplex to auto.
When Auto-MDIX (along with autonegotiation of speed and duplex) is enabled on one or both of connected interfaces, link up occurs, even if the cable type (straight through or crossover) is incorrect.
Auto-MDIX is supported on all 10/100 interfaces and on 10/100/1000BASE-T/TX small form-factor pluggable (SFP) module interfaces. It is not supported on 1000BASE-SX or -LX SFP module interfaces.
Caution
Examples
This example shows how to enable Auto-MDIX on a port:
Switch# configure terminalSwitch(config)# interface fastethernet1/0/1Switch(config-if)# speed autoSwitch(config-if)# duplex autoSwitch(config-if)# mdix autoSwitch(config-if)# endYou can verify the operational state of Auto-MDIX on the interface by entering the show controllers ethernet-controller interface-id phy privileged EXEC command.
Related Commands
show controllers ethernet-controller interface-id phy
Displays general information about internal registers of an interface, including the operational state of Auto-MDIX.
mls qos
Use the mls qos global configuration command to enable quality of service (QoS) for the entire switch. When the mls qos command is entered, QoS is enabled with the default parameters on all ports in the system. Use the no form of this command to reset all the QoS-related statistics and to disable the QoS features for the entire switch.
mls qos
no mls qos
Syntax Description
This command has no arguments or keywords.
Defaults
QoS is disabled. There is no concept of trusted or untrusted ports because the packets are not modified (the CoS, DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing).
When QoS is enabled with the mls qos global configuration command and all other QoS settings are set to their defaults, traffic is classified as best effort (the Differentiated Services Code Point [DSCP) and class of service [CoS] value is set to 0) without any policing. No policy maps are configured. The default port trust state on all ports is untrusted. The default ingress queue, egress queue-set, and hierarchical egress queue settings are in effect.
Command Modes
Global configuration
Command History
Usage Guidelines
QoS must be globally enabled to use QoS classification, policing, mark down or drop, queueing, and traffic shaping features. You can create a policy map and attach it to a port before entering the mls qos command. However, until you enter the mls qos command, QoS processing is disabled.
Policy maps and class maps used to configure QoS are not deleted from the configuration by the no mls qos command, but entries corresponding to policy maps are removed from the switch hardware to save system resources. To re-enable QoS with the previous configurations, use the mls qos command.
When QoS is disabled, ingress traffic is switched in pass-through mode, which means packets are switched without any rewrites and are classified to best effort without any policing.
Toggling the QoS status of the switch with this command modifies (reallocates) the sizes of the queues. During the queue size modification, the queue is temporarily shut down during the hardware reconfiguration, and the switch drops newly arrived packets for this queue.
Examples
This example shows how to enable QoS on the switch:
Switch(config)# mls qosYou can verify your settings by entering the show mls qos privileged EXEC command.
Related Commands
mls qos aggregate-policer
Use the mls qos aggregate-policer global configuration command to define policer parameters, which can be shared by multiple classes within the same policy map. A policer defines a maximum permissible rate of transmission, a maximum burst size for transmissions, and an action to take if either maximum is exceeded. Use the no form of this command to delete an aggregate policer.
mls qos aggregate-policer aggregate-policer-name rate-bps burst-byte exceed-action {drop | policed-dscp-transmit}
no mls qos aggregate-policer aggregate-policer-name
Syntax Description
Defaults
No aggregate policers are defined.
Command Modes
Global configuration
Command History
Usage Guidelines
The switch supports aggregate policers only in nonhierarchical single-level policy maps. Define an aggregate policer if the policer is shared with multiple classes.
Policers for a port cannot be shared with other policers for another port. Traffic from two different ports cannot be aggregated for policing purposes.
For standard port and enhanced-services (ES) ports, the port ASIC device that controls the ports supports 256 policers on the switch (255 user-configurable policers plus 1 policer reserved for system internal use). The maximum number of policers that can be configured per port is 63. Policers are allocated on demand by the software and are constrained by the hardware and ASIC boundaries. You cannot reserve policers per port (there is no guarantee that a port will be assigned to any policer).
You apply an aggregate policer to multiple classes in the same policy map. You cannot use an aggregate policer across different policy maps.
You cannot delete an aggregate policer if it is being used in a policy map. You must first use the no police aggregate aggregate-policer-name policy-map class configuration command to delete the aggregate policer from all policy maps before using the no mls qos aggregate-policer aggregate-policer-name command.
Ingress policing uses a token-bucket algorithm on a standard or an ES port. You configure the bucket depth (the maximum burst that is tolerated before the bucket overflows) by using the burst-byte option of the police policy-map class configuration command or the mls qos aggregate-policer global configuration command. You configure how fast (the average rate) the tokens are removed from the bucket by using the rate-bps option of the police policy-map class configuration command or the mls qos aggregate-policer global configuration command. For more information, see the software configuration guide for this release.
Examples
This example shows how to define the aggregate policer parameters and how to apply the policer to multiple classes in a policy map:
Switch(config)# mls qos aggregate-policer agg_policer1 10000 1000000 exceed-action dropSwitch(config)# policy-map policy2Switch(config-pmap)# class class1Switch(config-pmap-c)# police aggregate agg_policer1Switch(config-pmap-c)# exitSwitch(config-pmap)# class class2Switch(config-pmap-c)# set ip dscp 10Switch(config-pmap-c)# police aggregate agg_policer1Switch(config-pmap-c)# exitSwitch(config-pmap)# class class3Switch(config-pmap-c)# trust dscpSwitch(config-pmap-c)# police aggregate agg_policer2Switch(config-pmap-c)# exitYou can verify your settings by entering the show mls qos aggregate-policer privileged EXEC command.
Related Commands
Creates a policer that is shared by different classes.
Displays the quality of service (QoS) aggregate policer configuration.
mls qos cos
Use the mls qos cos interface configuration command to define the default class of service (CoS) value of a port or to assign the default CoS to all inbound packets on the port. Use the no form of this command to return to the default setting.
mls qos cos {default-cos | override}
no mls qos cos {default-cos | override}
Syntax Description
Defaults
The default CoS value for a port is 0.
CoS override is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can use the default value to assign a CoS and Differentiated Services Code Point (DSCP) value to all inbound packets that are untagged (if the inbound packet does not have a CoS value). You also can assign a default CoS and DSCP value to all inbound packets by using the override keyword.
Use the override keyword when all inbound packets on certain ports deserve higher or lower priority than packets entering from other ports. Even if a port is previously set to trust DSCP, CoS, or IP precedence, this command overrides the previously configured trust state, and all the inbound CoS values are assigned the default CoS value configured with the mls qos cos command. If an inbound packet is tagged, the CoS value of the packet is modified with the default CoS of the port at the ingress port.
Examples
This example shows how to configure the default port CoS to 4 on a port:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# mls qos trust cosSwitch(config-if)# mls qos cos 4This example shows how to assign all the packets entering a port to the default port CoS value of 4 on a port:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# mls qos cos 4Switch(config-if)# mls qos cos overrideYou can verify your settings by entering the show mls qos interface privileged EXEC command.
Related Commands
mls qos dscp-mutation
Use the mls qos dscp-mutation interface configuration command to apply a Differentiated Services Code Point (DSCP)-to-DSCP-mutation map to a DSCP-trusted port. Use the no form of this command to return the map to the default settings (no DSCP mutation).
mls qos dscp-mutation dscp-mutation-name
no mls qos dscp-mutation dscp-mutation-name
Syntax Description
dscp-mutation-name
Name of the DSCP-to-DSCP-mutation map. This map was previously defined with the mls qos map dscp-mutation global configuration command.
Defaults
The default DSCP-to-DSCP-mutation map is a null map, which maps inbound DSCP values to the same DSCP values.
Command Modes
Interface configuration
Command History
Usage Guidelines
If two quality of service (QoS) domains have different DSCP definitions, use the DSCP-to-DSCP-mutation map to translate one set of DSCP values to match the definition of another domain. You apply the DSCP-to-DSCP-mutation map to the receiving port (ingress mutation) at the boundary of a QoS administrative domain.
With ingress mutation, the new DSCP value overwrites the one in the packet, and QoS handles the packet with this new value. The switch sends the packet out the port with the new DSCP value.
You can configure multiple DSCP-to-DSCP-mutation maps on ingress ports.
You apply the map only to DSCP-trusted ports. If you apply the DSCP mutation map to an untrusted port, to a class of service (CoS) or an IP-precedence trusted port, the command has no immediate effect until the port becomes DSCP-trusted.
When port trust policies are used with 802.1Q tunneling, all ports sharing the same tunnel VLAN must be configured with the same trust policy, and the ports involved must use the same DSCP-to-DSCP mutation map. For more information, see the "mls qos map" section and the "mls qos trust" section.
Examples
This example shows how to define the DSCP-to-DSCP-mutation map named dscpmutation1and to apply the map to a port:
Switch(config)# mls qos map dscp-mutation dscpmutation1 10 11 12 13 to 30Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# mls qos trust dscpSwitch(config-if)# mls qos dscp-mutation dscpmutation1This example show how to remove the DSCP-to-DSCP-mutation map name dscpmutation1 from the port and to reset the map to the default:
Switch(config-if)# no mls qos dscp-mutation dscpmutation1You can verify your settings by entering the show mls qos maps privileged EXEC command.
Related Commands
mls qos map dscp-mutation
Defines the DSCP-to-DSCP-mutation map.
Configures the port trust state.
Displays QoS mapping information.
mls qos enhanced
Use the mls qos enhanced interface configuration command to take the internal bandwidth from one enhanced-services (ES) port and apply it to the other ES port. Use the no form of this command to return to the default setting.
mls qos enhanced
no mls qos enhanced
Syntax Description
This command has no arguments or keywords
Defaults
The internal bandwidth is shared between the ES ports.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can apply this command to only one ES port at a time. Applying the bandwidth to only a single ES port enables the existing quality of service (QoS) features to function more effectively.
Before applying this command to an ES port, disable the other ES port by using the shutdown interface configuration command. As long as the enhanced QoS functionality is applied to one ES port, the other ES port cannot be brought back up.
When you configure an ES port with the mls qos enhanced command, the port goes down and comes back up.
Examples
This example shows how to apply the internal bandwidth to one ES port:
Switch(config)# interface gigabitethernet1/1/1Switch(config-if)# shutdownSwitch(config-if)# exitSwitch(config)# interface gigabitethernet1/1/2Switch(config-if)# mls qos enhancedYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
mls qos map
Use the mls qos map global configuration command to define the class of service (CoS)-to-Differentiated Services Code Point (DSCP) map, the DSCP-to-CoS map, the DSCP-to-DSCP-mutation map, the IP-precedence-to-DSCP map, and the policed-DSCP map. Use the no form of this command to return to the default map.
mls qos map {cos-dscp dscp1...dscp8 | dscp-cos dscp-list to cos | dscp-mutation dscp-mutation-name in-dscp to out-dscp | ip-prec-dscp dscp1...dscp8 | policed-dscp dscp-list to mark-down-dscp}
no mls qos map {cos-dscp | dscp-cos | dscp-mutation dscp-mutation-name | ip-prec-dscp | policed-dscp}
Syntax Description
