Cisco 3750 Switch Command Reference
Cisco 3750 Switch Command Reference
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.;
Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE,
CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems
logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ
Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX,
Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO
are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0304R)
Preface xv
Audience xv
Purpose xv
Conventions xvi
channel-group 2-28
channel-protocol 2-32
class 2-33
class-map 2-35
delete 2-60
deny 2-62
duplex 2-80
flowcontrol 2-86
ip access-group 2-95
ip address 2-98
permit 2-175
police 2-178
policy-map 2-182
queue-set 2-186
rcommand 2-187
reload 2-189
remote-span 2-191
service-policy 2-199
session 2-201
set 2-202
setup 2-204
shutdown 2-353
speed 2-407
storm-control 2-415
switchport 2-420
trust 2-453
boot A-2
cat A-4
copy A-5
delete A-6
dir A-7
flash_init A-9
format A-10
fsck A-11
help A-12
load_helper A-13
memory A-14
mkdir A-16
more A-17
rename A-18
reset A-19
rmdir A-20
set A-21
type A-24
unset A-25
version A-27
debug pm B-59
INDEX
Audience
This guide is for the networking professional using the Cisco IOS command-line interface (CLI) to
manage the Catalyst 3750 switch, hereafter referred to as the switch. Before using this guide, you should
have experience working with the Cisco IOS commands and the switch software features. Before using
this guide, you should have experience working with the concepts and terminology of Ethernet and local
area networking.
Purpose
The Catalyst 3750 switch is supported by either the standard multilayer image (SMI) or the enhanced
multilayer image (EMI). The SMI provides Layer 2+ features including access control lists (ACLs),
quality of service (QoS), static routing, and the Routing Information Protocol (RIP). The EMI provides
a richer set of enterprise-class features. It includes Layer 2+ features and full Layer 3 routing (IP unicast
routing, IP multicast routing, and fallback bridging). To distinguish it from the Layer 2+ static routing
and RIP, the EMI includes protocols such as the Enhanced Interior Gateway Routing Protocol (EIGRP)
and Open Shortest Path First (OSPF) Protocol.
This guide provides the information you need about the Layer 2 and Layer 3 commands that have been
created or changed for use with the Catalyst 3750 switches. For information about the standard IOS
Release 12.1 commands, refer to the IOS documentation set available from the Cisco.com home page by
selecting Service and Support > Technical Documents. On the Cisco Product Documentation home page,
select Release 12.1 from the Cisco IOS Software drop-down list.
This guide does not provide procedures for configuring your switch. For detailed configuration
procedures, refer to the software configuration guide for this release.
This guide does not describe system messages you might encounter. For more information, refer to the
system message guide for this release.
Conventions
This publication uses these conventions to convey instructions and information:
Command descriptions use these conventions:
• Commands and keywords are in boldface text.
• Arguments for which you supply values are in italic.
• Square brackets ([ ]) means optional elements.
• Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.
• Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional
element.
Interactive examples use these conventions:
• Terminal sessions and system displays are in screen font.
• Information you enter is in boldface screen font.
• Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).
Notes, cautions, and warnings use these conventions and symbols:
Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in
this manual.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Timesaver Means the following will help you solve a problem. The tips information might not be troubleshooting
or even an action, but could be useful information.
Related Publications
These documents provide complete information about the switch and are available from this Cisco.com
site:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/index.htm
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com site and
from the telephone numbers listed in the “Ordering Documentation” section on page xviii.
• Release Notes for the Catalyst 3750 Switch (not orderable but available on Cisco.com)
• Catalyst 3750 Switch Software Configuration Guide (order number DOC-7815164=)
• Catalyst 3750 Switch Command Reference (order number DOC-7815165=)
• Catalyst 3750 Switch System Message Guide (order number DOC-7815166=)
• Cluster Management Suite (CMS) online help (available only from the switch CMS software)
• Catalyst 3750 Switch Hardware Installation Guide (order number DOC-7815136=)
• Cisco Small Form-Factor Pluggable Modules Installation Notes (not orderable but available on
Cisco.com)
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical
resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
http://www.cisco.com
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM
package, which may have shipped with your product. The Documentation CD-ROM is updated regularly
and may be more current than printed documentation. The CD-ROM package is available as a single unit
or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number
DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order annual or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from
the Networking Products MarketPlace:
http://www.cisco.com/en/US/partner/ordering/index.shtml
• Nonregistered Cisco.com users can order documentation through a local account representative by
calling Cisco Systems Corporate Headquarters (California, USA.) at 408 526-7208 or, elsewhere in
North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click
Feedback at the top of the page.
You can send your comments in e-mail to [email protected].
You can submit comments by using the response card (if present) behind the front cover of your
document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
• Packet magazine is the Cisco quarterly publication that provides the latest networking trends,
technology breakthroughs, and Cisco products and solutions to help industry professionals get the
most from their networking investment. Included are networking deployment and troubleshooting
tips, configuration examples, customer case studies, tutorials and training, certification information,
and links to numerous in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/go/packet
• iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet
business strategies for executives. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering
professionals involved in designing, developing, and operating public and private internets and
intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
• Training—Cisco offers world-class networking training. Current offerings in network training are
listed at this URL:
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
The Catalyst 3750 switch is supported by Cisco IOS software. This chapter describes how to use the
switch command-line interface (CLI) to configure software features.
For a complete description of the commands that support these features, see Chapter 2, “Cisco IOS
Commands.” For information on the boot loader commands, see Appendix A, “Boot Loader
Commands.” For information on the debug commands, see Appendix B, “Debug Commands.” For
information on the show platform commands, see Appendix C, “Show Platform Commands.” For more
information on Cisco IOS Release 12.1, refer to the Cisco IOS Release 12.1 Command Summary.
For task-oriented configuration steps, refer to the software configuration guide for this release.
Note We recommend using one CLI session when managing the switch stack.
If you want to configure a specific stack member port, you must include the stack member number in the
CLI command interface notation. For more information about interface notations, refer to the
“Configuring Interfaces” chapter in the software configuration guide for this release.
To debug a specific stack member, you can access it from the stack master by using the session
stack-member-number privileged EXEC command. The stack member number is appended to the system
prompt. For example, Switch-2# is the prompt in privileged EXEC mode for stack member 2, and the
system prompt for the stack master is Switch. Only the show and debug commands are available in a
CLI session to a specific stack member.
The supported commands can vary depending on the version of software in use. To view a
comprehensive list of commands, enter a question mark (?) at the prompt.
Switch# ?
To return to user EXEC mode, enter the disable privileged EXEC command.
You can specify either the terminal or nonvolatile RAM (NVRAM) as the source of configuration
commands.
This example shows you how to access global configuration mode:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
The supported commands can vary depending on the version of software in use. To view a
comprehensive list of commands, enter a question mark (?) at the prompt.
Switch(config)# ?
To exit global configuration command mode and to return to privileged EXEC mode, enter the end or
exit command, or press Ctrl-Z.
The supported commands can vary depending on the version of software in use. To view a
comprehensive list of commands, enter a question mark (?) at the prompt.
Switch(config-if)# ?
To exit interface configuration mode and to return to global configuration mode, enter the exit command.
To exit interface configuration mode and to return to privileged EXEC mode, enter the end command,
or press Ctrl-Z.
config-vlan Mode
Use this mode to configure normal-range VLANs (VLAN IDs 1 to 1005) or, when VTP mode is
transparent, to configure extended-range VLANs (VLAN IDs 1006 to 4094). When VTP mode is
transparent, the VLAN and VTP configuration is saved in the running configuration file, and you can
save it to the switch startup configuration file by using the copy running-config startup-config
privileged EXEC command. The configurations of VLAN IDs 1 to 1005 are saved in the VLAN database
if VTP is in transparent or server mode. The extended-range VLAN configurations are not saved in the
VLAN database.
Enter the vlan vlan-id global configuration command to access config-vlan mode:
Switch(config)# vlan 2000
Switch(config-vlan)#
The supported keywords can vary but are similar to the commands available in VLAN configuration
mode. To view a comprehensive list of commands, enter a question mark (?) at the prompt.
Switch(config-vlan)# ?
For extended-range VLANs, all characteristics except the MTU size must remain at the default setting.
To return to global configuration mode, enter exit; to return to privileged EXEC mode, enter end. All
the commands except shutdown take effect when you exit config-vlan mode.
The supported commands can vary depending on the version of software in use. To view a
comprehensive list of commands, enter a question mark (?) at the prompt.
Switch(vlan)# ?
To return to privileged EXEC mode, enter the abort VLAN configuration command to abandon the
proposed database. Otherwise, enter exit to implement the proposed new VLAN database and to return
to privileged EXEC mode. When you enter exit or apply, the configuration is saved in the VLAN
database; configuration from VLAN configuration mode cannot be saved in the switch configuration file.
The supported commands can vary depending on the version of software in use. To view a
comprehensive list of commands, enter a question mark (?) at the prompt.
Switch(config-line)# ?
To exit line configuration mode and to return to global configuration mode, use the exit command. To
exit line configuration mode and to return to privileged EXEC mode, enter the end command, or press
Ctrl-Z.
Syntax Description default Use the listed authentication methods that follow this argument as the default
list of methods when a user logs in.
method1 At least one of the these keywords:
[method2...]
• enable—Use the enable password for authentication.
• group radius—Use the list of all Remote Authentication Dial-In User
Service (RADIUS) servers for authentication.
• line—Use the line password for authentication.
• local—Use the local username database for authentication.
• local-case—Use the case-sensitive local username database for
authentication.
• none—Use no authentication. The client is automatically authenticated by
the switch without using the information supplied by the client.
Note Though visible in the command-line help strings, the group tacacs+ keyword is not supported.
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 IOS configuration file. The enable and line methods use the enable and line passwords for
authentication.
If you specify group radius, you must configure the RADIUS server by entering the radius-server host
global configuration command.
If you are not using a RADIUS server, you can use the local or local-case methods, which access the
local username database to perform authentication. By specifying the enable or line methods, you can
supply the clients with a password to provide access to the switch.
Use the show running-config privileged EXEC command to display the configured lists of
authentication methods.
Examples This example shows how to enable AAA and how to create an authentication list for 802.1X. This
authentication first tries to contact a RADIUS server. If this action returns an error, the user is allowed
access with no authentication.
Switch(config)# aaa new-model
Switch(config)# aaa authentication dot1x default group radius none
You can verify your settings by entering the show running-config privileged EXEC command.
action
Use the action access map configuration command on the switch stack or on a standalone switch 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.
no action
Syntax Description drop Drop the packet when the specified conditions are matched.
forward Forward the packet when the specified conditions are matched.
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 vmap4
Switch(config-access-map)# match ip address al2
Switch(config-access-map)# action forward
Switch(config-access-map)# exit
Switch(config)# vlan filter vmap4 vlan-list 5-6
You can verify your settings by entering the show vlan access-map privileged EXEC command.
archive copy-sw
Use the archive copy-sw privileged EXEC command on the stack master to copy the running image
from the Flash memory on one stack member to the Flash memory on one or more other stack members.
Syntax Description /destination-system The number of the stack member to which to copy the running image. The
destination-stack- range is 1 to 9.
member-number
/force-reload Unconditionally force a system reload after successfully downloading the
software image.
/leave-old-sw Keep the old software version after a successful download.
/no-set-boot Do not alter the setting of the BOOT environment variable to point to the
new software image after it is successfully downloaded.
/overwrite Overwrite the software image in Flash memory with the downloaded one.
/reload Reload the system after successfully downloading the image unless the
configuration has been changed and not been saved.
/safe Keep the current software image; do not delete it to make room for the new
software image before the new image is downloaded. The current image is
deleted after the download.
source-stack-member- The number of the stack member from which to copy the running image. The
number range is 1 to 9.
Usage Guidelines The current software image is not overwritten with the downloaded image.
Both the software image and HTML files are downloaded.
The new image is downloaded to the flash: file system.
The BOOT environment variable is changed to point to the new software image on the flash: file system.
Image names are case sensitive; the image file is provided in tar format.
You can copy the image to more than one specific stack member by repeating the /destination-system
destination-stack-member-number option in the command for each stack member to be upgraded. If you
do not specify the destination-stack-member-number, the default is to copy the running image file to all
stack members.
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 would prevent 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 on page 2-60.
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 or is not running on any stack members. 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 copy the running image from stack member 6 to stack member 8:
Switch# archive copy-sw 6 /destination-system 8
archive download-sw
Use the archive download-sw privileged EXEC command on the switch stack or on a standalone switch
to download a new image to the switch or switch stack and to overwrite or keep the existing image.
Syntax Description /force-reload Unconditionally force a system reload after successfully downloading the
software image.
/imageonly Download only the software image but not the HTML files associated with
the Cluster Management Suite (CMS). The HTML files for the existing
version are deleted only if the existing version is being overwritten or
removed.
/leave-old-sw Keep the old software version after a successful download.
/no-set-boot Do not alter the setting of the BOOT environment variable to point to the
new software image after it is successfully downloaded.
/no-version-check Download the software image without checking the compatibility of the
stack protocol version on the image and on the switch stack.
/destination-system Specify the specific stack member to be upgraded. The range is 1 to 9.
stack-member-number
/only-system-type Specify the specific system type to be upgraded. The range is 0 to
system-type FFFFFFFF.
/overwrite Overwrite the software image in Flash memory with the downloaded one.
/reload Reload the system after successfully downloading the image unless the
configuration has been changed and not been saved.
/safe Keep the current software image; do not delete it to make room for the new
software image before the new image is downloaded. The current image is
deleted after the download.
source-url The source URL alias for a local or network file system. These options are
supported:
• The syntax for the local Flash file system on the standalone switch or the
stack master:
flash:
The syntax for the local Flash file system on a stack member:
flash member number:
• The syntax for the File Transfer Protocol (FTP):
ftp:[[//username[:password]@location]/directory]/image-name.tar
• The syntax for the Remote Copy Protocol (RCP):
rcp:[[//username@location]/directory]/image-name.tar
• The syntax for the Trivial File Transfer Protocol (TFTP):
tftp:[[//location]/directory]/image-name.tar
The image-name.tar is the software image to download and install on the
switch.
Defaults The current software image is not overwritten with the downloaded image.
Both the software image and HTML files are downloaded.
The new image is downloaded to the flash: file system.
The BOOT environment variable is changed to point to the new software image on the flash: file system.
Image names are case sensitive; the image file is provided in tar format.
Compatibility of the stack protocol version on the image to be downloaded is checked with the version
on the switch stack.
Usage Guidelines The /imageonly option removes the HTML files for the existing image if the existing image is being
removed or replaced. Only the IOS image (without the HTML files) is downloaded.
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 on page 2-60.
Use the /no-version-check option if you want to download an image that has a different stack protocol
version than the one existing on the switch stack. You must use this option with the /destination-system
option to specify the specific stack member to be upgraded with the image.
Note Use the /no-version-check option with care. All stack members, including the stack master, must have
the same stack protocol version to be in the same switch stack. This option allows an image to be
downloaded without first confirming the compatibility of its stack protocol version with the version of
the switch stack.
You can upgrade more than one specific stack member by repeating the /destination-system option in
the command for each stack member to be upgraded.
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 or is not running on any stack members. 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.tar
This 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 /image-only tftp://172.20.129.10/test-image.tar
This 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.tar
archive tar
Use the archive tar privileged EXEC command on the switch stack or on a standalone switch to create
a tar file, list files in a tar file, or extract the files from a tar file.
Syntax Description /create destination-url Create a new tar file on the local or network file system.
flash:/file-url For destination-url, specify the destination URL alias for the local or
network file system and the name of the tar file to create. These options
are supported:
• The syntax for the local Flash filesystem:
flash:
• The syntax for the File Transfer Protocol (FTP):
ftp:[[//username[:password]@location]/directory]/tar-filename.tar
• The syntax for the Remote Copy Protocol (RCP) is:
rcp:[[//username@location]/directory]/tar-filename.tar
• The syntax for the Trivial File Transfer Protocol (TFTP):
tftp:[[//location]/directory]/tar-filename.tar
The tar-filename.tar is the tar file to be created.
For flash:/file-url, specify the location on the local Flash file system from
which the new tar file is created.
An optional list of files or directories within the source directory can be
specified to write to the new tar file. If none are specified, all files and
directories at this level are written to the newly created tar file.
/table source-url Display the contents of an existing tar file to the screen.
For source-url, specify the source URL alias for the local or network file
system. These options are supported:
• The syntax for the local Flash file system:
flash:
• The syntax for the File Transfer Protocol (FTP)
ftp:[[//username[:password]@location]/directory]/tar-filename.tar
• The syntax for the Remote Copy Protocol (RCP):
rcp:[[//username@location]/directory]/tar-filename.tar
• The syntax for the Trivial File Transfer Protocol (TFTP):
tftp:[[//location]/directory]/tar-filename.tar
The tar-filename.tar is the tar file to display.
/xtract source-url Extract files from a tar file to the local or network file system.
flash:/file-url For source-url, specify the source URL alias for the local or network file
system. These options are supported:
• The syntax for the local Flash file system:
flash:
• The syntax for the File Transfer Protocol (FTP):
ftp:[[//username[:password]@location]/directory]/tar-filename.tar
• The syntax for the Remote Copy Protocol (RCP):
rcp:[[//username@location]/directory]/tar-filename.tar
• The syntax for the Trivial File Transfer Protocol (TFTP):
tftp:[[//location]/directory]/tar-filename.tar
The tar-filename.tar is the tar file from which to extract.
For flash:/file-url, specify the location on the local Flash file system into
which the tar file is extracted.
An optional list of files or directories within the tar file can be specified
for extraction. If none are specified, all files and directories are extracted.
Defaults None
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-configs
This example shows how to display the contents of the c3750-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:c3750-tv0-m.tar
info (219 bytes)
c3750-tv0-mz-121/ (directory)
c3750-tv0-mz-121/html/ (directory)
c3750-tv0-mz-121/html/foo.html (0 bytes)
c3750-tv0-mz-121/vegas-tv0-mz-121.bin (610856 bytes)
c3750-tv0-mz-121/info (219 bytes)
info.ver (219 bytes)
This example shows how to display only the c3750-tv0-mz-121/html directory and its contents:
Switch# archive tar /table flash:c3750-tv0-m.tar c3750-tv0-mz-121/html
c3750-tv0-mz-121/html/ (directory)
c3750-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-configs
archive upload-sw
Use the archive upload-sw privileged EXEC command on the switch stack or on a standalone switch to
upload an existing switch image to a server.
Syntax Description /source-system-num Specify the specific stack member containing the image that is to be
stack member number uploaded.
/version version_string (Optional) Specify the specific version string of the image to be uploaded.
destination-url The destination URL alias for a local or network file system. These options
are supported:
• The syntax for the local Flash file system on the standalone switch or
the stack master:
flash:
The syntax for the local Flash file system on a stack member:
flash member number:
• The syntax for the File Transfer Protocol (FTP):
ftp:[[//username[:password]@location]/directory]/image-name.tar
• The syntax for the Remote Copy Protocol (RCP):
rcp:[[//username@location]/directory]/image-name.tar
• The syntax for the Trivial File Transfer Protocol (TFTP):
tftp:[[//location]/directory]/image-name.tar
The image-name.tar is the name of software image to be stored on the
server.
Defaults Uploads the currently running image from the flash: file system.
Usage Guidelines You must specify the /source-system-num option to use the /version option. Using these options
together uploads the specified image, not the running image, of a specific stack member.
The upload feature is available only if the HTML files associated with the Cluster Management Suite
(CMS) have been installed with the existing image.
The files are uploaded in this sequence: the IOS image, the HTML files, and info. 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 on stack member 6 image to a TFTP server at
172.20.140.2:
Switch# archive upload-sw /source-system-num 6 tftp://172.20.140.2/test-image.tar
Syntax Description cisco-phone Identify this interface as connected to a Cisco IP phone, and automatically configure
QoS for VoIP. The QoS labels of incoming packets are trusted only when the phone
is detected.
trust Identify this interface as connected to a trusted switch or router, and automatically
configure QoS for VoIP. The QoS labels of incoming packets are trusted. For
nonrouted interfaces, the CoS value of the incoming packet is trusted. For routed
interfaces, the DSCP value of the incoming packet is trusted.
Table 2-1 Traffic Types, Ingress Packet Labels, Assigned Packet Labels, and Queues
Table 2-2 shows the generated auto-QoS configuration for the ingress queues.
Table 2-3 shows the generated auto-QoS configuration for the egress queues.
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 incoming
traffic for QoS.
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 The switch applies the auto-QoS-generated commands as if the commands were entered from the
command-line interface (CLI). An existing user configuration can cause the application of the generated
commands to fail or to be overridden by the generated commands. These actions occur without warning.
If all the generated commands are successfully applied, any user-entered configuration that was not
overridden remains in the running configuration. Any user-entered configuration that was overridden
can be retrieved by reloading the switch without saving the current configuration to memory. If the
generated commands fail to be applied, the previous running configuration is restored.
If this is the first interface 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 interface, only the auto-QoS-generated interface configuration commands for that
interface are executed.
When you enable the auto-QoS feature on the first interface, these automatic actions occur:
• QoS is globally enabled (mls qos global configuration command), and other global configuration
commands are added.
• When you enter the auto qos voip cisco-phone interface configuration command on a port at the
edge of the network that is connected to a Cisco IP phone, the switch enables the trusted boundary
feature. The switch uses the Cisco Discovery Protocol (CDP) to detect the presence or absence of a
Cisco IP phone. When a Cisco IP phone is detected, the ingress classification on the interface is set
to trust the QoS label received in the packet. When a Cisco IP phone is absent, the ingress
classification is set to not trust the QoS label in the packet. The switch configures ingress and egress
queues on the interface according to the settings in Table 2-2 and Table 2-3.
• When you enter the auto qos voip trust interface configuration command on a port connected to
the interior of the network, the switch trusts the CoS value for nonrouted interfaces or the DSCP
value for routed interfaces in ingress packets (the assumption is that traffic has already been
classified by other edge devices). The switch configures the ingress and egress queues on the
interface according to the settings in Table 2-2 and Table 2-3.
You can enable auto-QoS on static, dynamic-access, and voice VLAN access, and trunk ports.
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable
debugging before you enable auto-QoS. Use the debug autoqos privileged EXEC command to enable
auto-QoS debugging. For more information, see the “debug autoqos” section on page B-2.
To disable auto-QoS on an interface, use the no auto qos voip interface configuration command. Only
the auto-QoS-generated interface configuration commands for this interface are removed. If this is the
last interface 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 interfaces 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 and to trust the QoS labels received in incoming packets
when the switch or router connected to Gigabit Ethernet interface 0/1 on stack member 2 is a trusted
device:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# auto qos voip trust
You can verify your settings by entering the show auto qos interface interface-id privileged EXEC
command.
boot auto-copy-sw
Use the boot auto-copy-sw global configuration command from the stack master to automatically
upgrade switches in version-mismatch (VM) mode with the switch stack image. Use the no form of this
command to not automatically upgrade switches in VM mode.
boot auto-copy-sw
no boot auto-copy-sw
Defaults Enabled.
Usage Guidelines A switch in version-mismatch (VM) mode is a switch that has a different stack protocol version than the
version on the switch stack. Switches in VM mode cannot join the switch stack. If the switch stack has
an image that can be copied to a switch in VM mode, this command automatically copies the switch in
VM mode with the image from another stack member. The switch then exits VM mode, reboots, and
joins the switch stack.
This command affects only switches in VM mode. It does not affect existing stack members.
boot boothlpr
Use the boot boothlpr global configuration command on the switch stack or on a standalone switch to
load a special IOS image, which when loaded into memory, can load a second IOS 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.
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.
boot config-file
Use the boot config-file global configuration command on a standalone switch to specify the filename
that IOS 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.
no boot config-file
Syntax Description flash:/file-url The path (directory) and name of the configuration file.
Usage Guidelines This command works properly only from a standalone switch.
Filenames and directory names are case sensitive.
This command changes the setting of the CONFIG_FILE environment variable. For more information,
see Appendix A, “Boot Loader Commands.”
boot enable-break
Use the boot enable-break global configuration command on a standalone switch 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
Defaults Disabled. The automatic boot process cannot be interrupted by pressing the Break key on the console.
Usage Guidelines This command works properly only from a standalone switch.
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 Despite the setting of this command, you can interrupt the automatic boot process at any time by pressing
the MODE button on the switch front panel.
This command changes the setting of the ENABLE_BREAK environment variable. For more
information, see Appendix A, “Boot Loader Commands.”
boot helper
Use the boot helper global configuration command on the switch stack or on a standalone switch 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.
no boot helper
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url The path (directory) and a list of loadable files to dynamically load during
loader initialization. Separate each image name with a semicolon.
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
Appendix A, “Boot Loader Commands.”
boot helper-config-file
Use the boot helper-config-file global configuration command on the switch stack or on a standalone
switch to specify the name of the configuration file to be used by the IOS helper image. If this is not set,
the file specified by the CONFIG_FILE environment variable is used by all versions of IOS that are
loaded. Use the no form of this command to return to the default setting.
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.
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 Appendix A, “Boot Loader Commands.”
boot manual
Use the boot manual global configuration command on a standalone switch 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
Usage Guidelines This command works properly only from a standalone switch.
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 Appendix A, “Boot Loader Commands.”
boot private-config-file
Use the boot private-config-file global configuration command on a standalone switch to specify the
filename that IOS 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.
no boot private-config-file
Usage Guidelines This command works properly only from a standalone switch.
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 pconfig
boot system
Use the boot system global configuration command on a standalone switch to specify the IOS image to
load during the next boot cycle. Use the no form of this command to return to the default setting.
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.
Usage Guidelines This command works properly only from a standalone switch.
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
Appendix A, “Boot Loader Commands.”
channel-group
Use the channel-group interface configuration command on the switch stack or on a standalone switch
to assign an Ethernet interface to an EtherChannel group. Use the no form of this command to remove
an Ethernet interface from an EtherChannel group.
no channel-group
Syntax Description channel-group-number Specify the channel group number. The range is 1 to 12.
mode Specify the EtherChannel mode of the interface.
active Unconditionally enable Link Aggregation Protocol (LACP).
Active mode places an interface into a negotiating state in which the
interface initiates negotiations with other interfaces by sending LACP
packets. A channel is formed with another port group in either the active or
passive mode.
auto Enable the Port Aggregation Protocol (PAgP) only if a PAgP device is
detected.
Auto mode places an interface into a passive negotiating state in which the
interface responds to PAgP packets it receives but does not start PAgP
packet negotiation. A channel is formed only with another port group in
desirable mode. When auto is enabled, silent operation is the default.
desirable Unconditionally enable PAgP.
Desirable mode places an interface into an active negotiating state in which
the interface starts negotiations with other interfaces by sending PAgP
packets. A channel is formed with another port group in either the desirable
or auto mode. When desirable is enabled, silent operation is the default.
non-silent (Optional) Used with the auto or desirable keyword when traffic is
expected from the other device.
on Force the interface to channel without PAgP or the LACP.
With the on mode, a usable EtherChannel exists only when an interface
group in the on mode is connected to another interface group in the on
mode.
passive Enable LACP only if a LACP device is detected.
Passive mode places an interface into a negotiating state in which the
interface responds to LACP packets it receives but does not initiate LACP
packet negotiation. A channel is formed only with another port group in
active mode.
Usage Guidelines For Layer 2 EtherChannels, you do not have to create a port-channel interface first by using the interface
port-channel global configuration command before assigning a physical interface to a channel group.
Instead, you can use the channel-group interface configuration command. It automatically creates the
port-channel interface when the channel group gets its first physical interface if the logical interface is
not already created. If you create the port-channel interface 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 interface 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 interface
apply to all the physical interfaces assigned to the port-channel interface. Configuration changes applied
to the physical interface affect only the interface where you apply the configuration. To change the
parameters of all ports in an EtherChannel, apply configuration commands to the port-channel interface,
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 interface to a channel group, and to use the interface
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. The on keyword is the only setting that is supported when the
EtherChannel members are from different switches in the switch stack (cross-stack EtherChannel).
Caution You should exercise care when setting the mode to on (manual configuration). All ports configured in
the on mode are bundled together in the same group and are forced to have similar characteristics. If the
group is misconfigured, packet loss or spanning-tree loops might occur.
Do not configure an EtherChannel in both the PAgP and LACP modes. EtherChannel groups running
PAgP and LACP can coexist on the same switch or on different switches in the stack (but not in a
cross-stack configuration). 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.
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, refer to the “Configuring EtherChannels” chapter in the
software guide for this release.
Caution Do not enable Layer 3 addresses on the physical EtherChannel interfaces. Do not assign bridge groups
on the physical EtherChannel interfaces because it creates loops.
Examples This example shows how to configure EtherChannel on a single switch in the stack. It assigns Gigabit
Ethernet interfaces 0/4 and 0/5 on stack member 2 as static-access ports in VLAN 10 to channel 5 with
the PAgP mode desirable:
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/0/4 -5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode desirable
Switch(config-if-range)# end
This example shows how to configure EtherChannel on a single switch in the stack. It assigns Gigabit
Ethernet interfaces 0/4 and 0/5 on stack member 2 as static-access ports in VLAN 10 to channel 5 with
the LACP mode active:
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/0/4 -5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode active
Switch(config-if-range)# end
This example shows how to configure cross-stack EtherChannel. It assigns Gigabit Ethernet interfaces
0/4 and 0/5 on stack member 2 and Gigabit Ethernet interface 0/3 on stack member 3 as static-access
ports in VLAN 10 to channel 5 with the PAgP and LACP modes disabled (on):
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/0/4 -5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode on
Switch(config-if-range)# exit
Switch(config)# interface gigabitethernet3/0/3
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 10
Switch(config-if)# channel-group 5 mode on
Switch(config-if)# exit
You can verify your settings by entering the show running-config privileged EXEC command.
Command Description
show pagp Displays PAgP channel-group information.
show running-config Displays the current operating configuration. For syntax information,
select Cisco IOS Configuration Fundamentals Command
Reference for Release 12.1 > Cisco IOS File Management
Commands > Configuration File Commands.
channel-protocol
Use the channel-protocol interface configuration command on the switch stack or on a standalone
switch to restrict the protocol used on an interface to manage channeling. Use the no form of this
command to return to the default setting.
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).
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 lacp
You can verify your settings by entering the show etherchannel [channel-group-number] protocol
privileged EXEC command.
class
Use the class policy-map configuration command on the switch stack or on a standalone switch to define
a traffic classification match criteria (through the police, set, and trust policy-map class configuration
commands) for the specified class-map name. Use the no form of this command to delete an existing
class map.
class class-map-name
no class class-map-name
Usage Guidelines Before using the class command, you 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 policy for new classes or modify a policy for any existing classes in that policy map.
You attach the policy map to an interface by using the service-policy interface configuration command.
After entering the class command, you enter policy-map class configuration mode, and these
configuration commands are available:
• bandwidth: Although this command is displayed, it is not supported on Catalyst 3750 switches.
• exit: exits policy-map class configuration mode and returns to policy-map configuration mode.
• no: returns a command to its default setting.
• police: defines a policer or aggregate policer for the classified traffic. The policer specifies the
bandwidth limitations and the action to take when the limits are exceeded. For more information,
see the police and police aggregate policy-map class commands.
• set: specifies a value to be assigned to the classified traffic. For more information, see the set
command.
• trust: defines a trust state for traffic classified with the class or the class-map command. For more
information, see the trust command.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode,
use the end command.
The class command performs the same function as the class-map global configuration command. Use
the class command when a new classification, which is not shared with any other ports, is needed. Use
the class-map command when the map is shared among many ports.
Examples This example shows how to create a policy map called policy1. When attached to the ingress direction,
it matches all the incoming traffic defined in class1, sets the IP Differentiated Services Code Point
(DSCP) to 10, and polices the traffic at an average rate of 1 Mbps and bursts at 20 KB. Traffic exceeding
the profile is marked down to a DSCP value obtained from the policed-DSCP map and then sent.
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
class-map
Use the class-map global configuration command on the switch stack or on a standalone switch 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.
Syntax Description match-all (Optional) Perform a logical-AND of all matching statements under this class
map. All criteria in the class map must be matched.
match-any (Optional) Perform a logical-OR of the matching statements under this class
map. One or more criteria must be matched.
class-map-name Name of the class map.
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.
The class-map command and its subcommands are used to define packet classification, marking, and
aggregate policing as part of a globally named service policy applied on a per-interface basis.
After you are in quality of service (QoS) class-map configuration mode, these configuration commands
are available:
• description: describes the class map (up to 200 characters). The show class-map privileged EXEC
command displays the description and the name of the class-map.
• exit: exits from QoS class-map configuration mode.
• match: configures classification criteria. For more information, see the match (class-map
configuration) command.
• no: removes a match statement from a class map.
• rename: renames the current class map. If you rename a class map with a name that is already used,
the message A class-map with this name already exists appears.
To define packet classification on a physical-port basis, only one match command per class map is
supported. In this situation, the match-all and match-any keywords are equivalent.
Only one access control list (ACL) can be configured in a class map. The ACL can have multiple access
control entries (ACEs).
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 10
Switch(config)# class-map class1
Switch(config-cmap)# match access-group 103
Switch(config-cmap)# exit
You can verify your settings by entering the show class-map privileged EXEC command.
clear lacp
Use the clear lacp privileged EXEC command on the switch stack or on a standalone switch to clear
Link Aggregation Control Protocol (LACP) channel-group counters.
Syntax Description channel-group-number (Optional) Channel group number. The range is 1 to 12.
counters Clear traffic counters.
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.
This example shows how to clear LACP traffic counters for group 4:
Switch# clear lacp 4 counters
You can verify that the information was deleted by entering the show lacp counters or the show lacp 4
counters privileged EXEC command.
clear mac-address-table
Use the clear mac-address-table privileged EXEC command on the switch stack or on a standalone
switch to delete from the MAC address table a specific dynamic address, all dynamic addresses on a
particular interface, all dynamic addresses on stack members, or all dynamic addresses on a particular
VLAN. This command also clears the MAC address notification global counters.
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.0007
You can verify that the information was deleted by entering the show mac-address-table privileged
EXEC command.
clear pagp
Use the clear pagp privileged EXEC command on the switch stack or on a standalone switch to clear
Port Aggregation Protocol (PAgP) channel-group information.
Syntax Description channel-group-number (Optional) Channel group number. The range is 1 to 12.
counters Clear traffic counters.
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.
This example shows how to clear PAgP traffic counters for group 10:
Switch# clear pagp 10 counters
You can verify that information was deleted by entering the show pagp privileged EXEC command.
Usage Guidelines You can use the clear setup express command to exit Express Setup mode. For example, if you activate
Express Setup and then decide to connect to the switch through the console port instead of through an
Ethernet port, enter the clear setup express command. The switch exits Express Setup mode. The IP
address 10.0.0.1 is no longer valid on the switch, and your connection using this IP address is ended.
This command is available only when the switch is in Express Setup mode.
You can verify that the switch has exited Express Setup mode by entering the show express setup
privileged EXEC command.
Syntax Description interface interface-id (Optional) Clear all spanning-tree counters on the specified interface. Valid
interfaces include physical ports, VLANs, and port channels. The VLAN
range is 1 to 4094. The port-channel range is 1 to 12.
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 counters
Syntax Description interface interface-id (Optional) Restart the protocol migration process on the specified interface.
Valid interfaces include physical ports, VLANs, and port channels. The
VLAN range is 1 to 4094. The port-channel range is 1 to 12.
Usage Guidelines A switch running the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol or the Multiple
Spanning Tree Protocol (MSTP) supports a built-in protocol migration mechanism that enables it to
interoperate with legacy 802.1D switches. If a rapid-PVST+ switch or an MSTP switch receives a legacy
802.1D configuration bridge protocol data unit (BPDU) with the protocol version set to 0, it sends only
802.1D BPDUs on that port. A multiple spanning-tree (MST) switch can also detect that a port is at the
boundary of a region when it receives a legacy BPDU, an MST BPDU (version 3) associated with a
different region, or 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 because it cannot determine whether the legacy switch has been removed from
the link unless the legacy switch is the designated switch. Use the clear spanning-tree
detected-protocols command in this situation.
Examples This example shows how to restart the protocol migration process on an interface of stack member 2:
Switch# clear spanning-tree detected-protocols interface gigabitethernet2/0/1
Examples This example shows how to clear VLAN Membership Policy Server (VMPS) statistics:
Switch# clear vmps statistics
You can verify that information was deleted by entering the show vmps statistics privileged EXEC
command.
You can verify that information was deleted by entering the show vtp counters privileged EXEC
command.
cluster commander-address
You do not need to enter this command from the switch stack or from a standalone cluster member switch.
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.
no cluster commander-address
Usage Guidelines This command is available only on the cluster command switch stack or 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>
<output truncated>
This example shows how to remove a member from the cluster by using the cluster member console.
Switch # configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# no cluster commander-address
You can verify your settings by entering the show cluster privileged EXEC command.
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.
Usage Guidelines This command is available only on the cluster command switch stack or 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 4
You can verify your setting by entering the show cluster privileged EXEC command.
cluster enable
Use the cluster enable global configuration command on a command-capable switch or switch stack 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.
no cluster enable
Syntax Description name Name of the cluster up to 31 characters. Valid characters include
only alphanumerics, dashes, and underscores.
command-switch-member-number (Optional) Assign a member number to the cluster command
switch of the cluster. The range is 0 to 15.
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 4
You can verify your setting by entering the show cluster privileged EXEC command on the cluster
command switch.
cluster holdtime
Use the cluster holdtime global configuration command on the switch stack or on the a cluster command
switch 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.
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.
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 3
Switch(config)# cluster holdtime 30
You can verify your settings by entering the show cluster privileged EXEC command.
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.
no cluster member n
Syntax Description n The number that identifies a cluster member. The range is 0 to 15.
mac-address H.H.H MAC address of the cluster member switch in hexadecimal format.
password enable-password Enable password of the candidate switch. The password is not
required if there is no password on the candidate switch.
vlan vlan-id (Optional) VLAN ID through which the candidate is added to the
cluster by the cluster command switch. The range is 1 to 4094.
Defaults A newly enabled cluster command switch has no associated cluster members.
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 host name, the cluster command switch appends a member number
to the cluster command-switch host name 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 3
This 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.3333
You can verify your settings by entering the show cluster members privileged EXEC command on the
cluster command switch.
cluster outside-interface
Use the cluster outside-interface global configuration command on the switch stack or on the a cluster
command switch 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.
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.
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 1
You can verify your setting by entering the show running-config privileged EXEC command.
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
Usage Guidelines When you enter the no cluster run command on a cluster command switch or cluster command switch
stack, 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 run
You can verify your setting by entering the show cluster privileged EXEC command.
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.
no cluster standby-group
Syntax Description HSRP-group-name Name of the HSRP group that is bound to the cluster. The group name is
limited to 32 characters.
routing-redundancy (Optional) Enable the same HSRP standby group to be used for cluster
command-switch redundancy and routing redundancy.
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 nonvolatile RAM
(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_hsrp
This 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-redundancy
This 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 exist
This 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 switch
You can verify your settings by entering the show cluster privileged EXEC command. The output shows
whether redundancy is enabled in the cluster.
cluster timer
Use the cluster timer global configuration command on the switch stack or on the a cluster command
switch to set the interval in seconds between heartbeat messages. Use the no form of this command to
set the interval to the default value.
no cluster timer
Syntax Description interval-in-secs Interval in seconds between heartbeat messages. The range is 1 to 300
seconds.
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 3
Switch(config)# cluster holdtime 30
You can verify your settings by entering the show cluster privileged EXEC command.
define interface-range
Use the define interface-range global configuration command on the switch stack or on a standalone
switch to create an interface-range macro. Use the no form of this command to delete the defined macro.
delete
Use the delete privileged EXEC command on the switch stack or on a standalone switch to delete a file
or directory on the Flash memory device.
Syntax Description /force (Optional) Suppress the prompt that confirms the deletion.
/recursive (Optional) Delete the named directory and all subdirectories and the files
contained in it.
filesystem: Alias for a Flash file system.
The syntax for the local Flash file system on the stack member or the stack master:
flash:
From the stack master, the syntax for the local Flash file system on a stack
member:
flash member number:
/file-url The path (directory) and filename to delete.
Usage Guidelines If you use the /force keyword, you are prompted once at the beginning of the deletion process to confirm
the deletion.
If you use the /recursive keyword without the /force keyword, you are prompted to confirm the deletion
of every file.
The prompting behavior depends on the setting of the file prompt global configuration command. By
default, the switch prompts for confirmation on destructive file operations. For more information about
this command, refer to the Cisco IOS Command Reference for Release 12.1.
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-image
You can verify that the directory was removed by entering the dir filesystem: privileged EXEC
command.
deny
Use the deny MAC access list configuration command on the switch stack or on a standalone switch 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 any Keyword to specify to deny any source or destination MAC address.
host src MAC-addr | Define a host MAC address and optional subnet mask. If the source
src-MAC-addr mask address for a packet matches the defined address, non-IP traffic from that
address is denied.
host dst-MAC-addr | Define a destination MAC address and optional subnet mask. If the
dst-MAC-addr mask destination address for a packet matches the defined address, non-IP
traffic to that address is denied.
type mask (Optional) Use the Ethertype number of a packet with Ethernet II or
SNAP encapsulation to identify the protocol of the packet.
The type is 0 to 65535, specified in hexadecimal.
The mask is a mask of don’t care bits applied to the Ethertype before
testing for a match.
aarp (Optional) Select Ethertype AppleTalk Address Resolution Protocol that
maps a data-link address to a network address.
amber (Optional) Select EtherType DEC-Amber.
cos cos (Optional) Select a class of service (CoS) number from 0 to 7 to set
priority. Filtering on CoS can be performed only in hardware. A warning
message reminds the user if the cos option is configured.
dec-spanning (Optional) Select EtherType Digital Equipment Corporation (DEC)
spanning tree.
decnet-iv (Optional) Select EtherType DECnet Phase IV protocol.
diagnostic (Optional) Select EtherType DEC-Diagnostic.
dsm (Optional) Select EtherType DEC-DSM.
etype-6000 (Optional) Select EtherType 0x6000.
etype-8042 (Optional) Select EtherType 0x8042.
lat (Optional) Select EtherType DEC-LAT.
lavc-sca (Optional) Select EtherType DEC-LAVC-SCA.
lsap lsap-number mask (Optional) Use the LSAP number (0 to 65535) of a packet with 802.2
encapsulation to identify the protocol of the packet.
mask is a mask of don’t care bits applied to the LSAP number before
testing for a match.
mop-console (Optional) Select EtherType DEC-MOP Remote Console.
mop-dump (Optional) Select EtherType DEC-MOP Dump.
msdos (Optional) Select EtherType DEC-MSDOS.
mumps (Optional) Select EtherType DEC-MUMPS.
netbios (Optional) Select EtherType DEC- Network Basic Input/Output System
(NETBIOS).
vines-echo (Optional) Select EtherType Virtual Integrated Network Service (VINES)
Echo from Banyan Systems.
vines-ip (Optional) Select EtherType VINES IP.
xns-idp (Optional) Select EtherType Xerox Network Systems (XNS) protocol
suite (0 to 65535), an arbitrary Ethertype in decimal, hexadecimal, or
octal.
Note Though visible in the command-line help strings, appletalk is not supported as a matching condition.
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.
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 For more information about named MAC extended access lists, refer to the software configuration guide
for this release.
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.
You can verify your settings by entering the show access-lists privileged EXEC command.
dot1x default
Use the dot1x default interface configuration command on the switch stack or on a standalone switch
to reset the configurable 802.1X parameters to their default values.
dot1x default
Examples This example shows how to reset the configurable 802.1X parameters on an interface:
Switch(config-if)# dot1x default
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC
command.
dot1x guest-vlan
Use the dot1x guest-vlan interface configuration command on the switch stack or on a standalone switch
to specify an active VLAN as an 802.1X guest VLAN. Use the no form of this command to return to the
default setting.
no dot1x guest-vlan
Syntax Description vlan-id Specify an active VLAN as an 802.1X guest VLAN. The range is 1 to 4094.
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.
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 5
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC
command.
dot1x host-mode
Use the dot1x host-mode interface configuration command on the switch stack or on a standalone
switch 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.
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 interface.
Examples This example shows how to enable 802.1X globally, enable 802.1X on Gigabit Ethernet interface 0/1 on
stack member 2, and enable multiple-hosts mode:
Switch(config)# dot1x system-auth-control
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# dot1x port-control auto
Switch(config-if)# dot1x host-mode multi-host
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC
command.
dot1x initialize
Use the dot1x initialize privileged EXEC command on the switch stack or on a standalone switch to
manually return the specified 802.1X-enabled interface to an unauthorized state before initiating a new
authentication session on the interface.
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 Gigabit Ethernet interface 0/3 on stack member 2:
Switch# dot1x initialize interface gigabitethernet2/0/3
You can verify the unauthorized port status by entering the show dot1x [interface interface-id]
privileged EXEC command.
dot1x max-req
Use the dot1x max-req interface configuration command on the switch stack or on a standalone switch
to set the maximum number of times that the switch sends an Extensible Authentication Protocol
(EAP)-request/identity frame (assuming that no response is received) to the client before restarting the
authentication process. Use the no form of this command to return to the default setting.
no dot1x max-req
Syntax Description count Number of times that the switch sends an EAP-request/identity frame before
restarting the authentication process. The range is 1 to 10.
Usage Guidelines You should change the default value of this command only to adjust for unusual circumstances such as
unreliable links or specific behavioral problems with certain clients and authentication servers.
Examples This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity
frame before restarting the authentication process:
Switch(config-if)# dot1x max-req 5
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC
command.
dot1x multiple-hosts
This is an obsolete command.
In past releases, the dot1x multiple-hosts interface configuration command was used on the switch
stack or on a standalone switch to allow multiple hosts (clients) on an 802.1X-authorized port.
dot1x port-control
Use the dot1x port-control interface configuration command on the switch stack or on a standalone
switch to enable manual control of the authorization state of the port. Use the no form of this command
to return to the default setting.
no dot1x port-control
Syntax Description auto Enable 802.1X authentication on the interface and cause the port to transition
to the authorized or unauthorized state based on the 802.1X authentication
exchange between the switch and the client.
force-authorized Disable 802.1X authentication on the interface and cause the port to transition
to the authorized state without any authentication exchange required. The port
sends and receives normal traffic without 802.1X-based authentication of the
client.
force-unauthorized Deny all access through this interface by forcing the port to transition to the
unauthorized state, ignoring all attempts by the client to authenticate. The
switch cannot provide authentication services to the client through the interface.
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 interface.
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:
• Trunk port—If you try to enable 802.1X on a trunk port, an error message appears, and 802.1X is
not enabled. If you try to change the mode of an 802.1X-enabled port to trunk, an error message
appears, and the port mode is not changed.
• Dynamic ports—A port in dynamic mode can negotiate with its neighbor to become a trunk port. If
you try to enable 802.1X on a dynamic port, an error message appears, and 802.1X is not enabled.
If you try to change the mode of an 802.1X-enabled port to dynamic, an error message appears, and
the port mode is not changed.
• Dynamic-access ports—If you try to enable 802.1X on a dynamic-access (VLAN Query Protocol
[VQP]) port, an error message appears, and 802.1X is not enabled. If you try to change an
802.1X-enabled port to dynamic VLAN assignment, an error message appears, and the VLAN
configuration is not changed.
• EtherChannel port—Before enabling 802.1X on the port, you must first remove it from the
EtherChannel. If you try to enable 802.1X on an EtherChannel or on an active port in an
EtherChannel, an error message appears, and 802.1X is not enabled. If you enable 802.1X on a
not-yet active port of an EtherChannel, the port does not join the EtherChannel.
• Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination ports—You can enable
802.1X on a port that is a SPAN or RSPAN destination port. However, 802.1X is disabled until the
port is removed as a SPAN or RSPAN destination. You can enable 802.1X on a SPAN or RSPAN
source port.
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 interface, use the no dot1x port-control interface
configuration command.
Examples This example shows how to enable 802.1X on Fast Ethernet interface 0/1 on stack member 2:
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# dot1x port-control auto
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC
command.
dot1x re-authenticate
Use the dot1x re-authenticate privileged EXEC command on the switch stack or on a standalone switch
to manually initiate a re-authentication of all 802.1X-enabled ports or the specified 802.1X-enabled port.
Syntax Description interface interface-id Stack switch number, module, and port number of the interface to
re-authenticate.
Usage Guidelines You can use this command to re-authenticate a client without waiting for the configured number of
seconds between re-authentication attempts (re-authperiod) and automatic re-authentication.
Examples This example shows how to manually re-authenticate the device connected to Fast Ethernet interface 0/1
on stack member 2:
Switch# dot1x re-authenticate interface fastethernet2/0/1
dot1x re-authentication
This is an obsolete command.
In past releases, the dot1x re-authentication global configuration command was used on the switch
stack or on a standalone switch to set the amount of time between periodic re-authentication attempts.
dot1x reauthentication
Use the dot1x reauthentication interface configuration command on the switch stack or on a standalone
switch 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
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 reauthentication
This example shows how to enable periodic re-authentication and to set the number of seconds between
re-authentication attempts to 4000 seconds:
Switch(config-if)# dot1x reauthentication
Switch(config-if)# dot1x timeout reauth-period 4000
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC
command.
dot1x system-auth-control
Use the dot1x system-auth-control global configuration command on the switch stack or on a
standalone switch 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
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.
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC
command.
dot1x timeout
Use the dot1x timeout interface configuration command on the switch stack or on a standalone switch
to set 802.1X timers. Use the no form of this command to return to the default setting.
Syntax Description quiet-period seconds Number of seconds that the switch remains in the quiet state following a
failed authentication exchange with the client. The range is 1 to 65535.
reauth-period seconds Number of seconds between re-authentication attempts. The range is 1 to
65535.
server-timeout seconds Number of seconds that the switch waits for the retransmission of packets
by the switch to the authentication server. The range is 1 to 65535.
supp-timeout seconds Number of seconds that the switch waits for the retransmission of packets
by the switch to the 802.1X client. The range is 1 to 65535.
tx-period seconds Number of seconds that the switch waits for a response to an
EAP-request/identity frame from the client before retransmitting the
request. The range is 1 to 65535.
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 reauthentication
Switch(config-if)# dot1x timeout reauth-period 4000
This example shows how to set 30 seconds as the quiet time on the switch:
Switch(config-if)# dot1x timeout quiet-period 30
This example shows how to set 25 seconds as the switch-to-authentication server retransmission time:
Switch(config)# dot1x timeout server-timeout 25
This 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 25
This example shows how to set 60 as the number of seconds to wait for a response to an
EAP-request/identity frame from the client before re-transmitting the request:
Switch(config-if)# dot1x timeout tx-period 60
You can verify your settings by entering the show dot1x privileged EXEC command.
duplex
Use the duplex interface configuration command on the switch stack or on a standalone switch 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.
no duplex
Syntax Description auto Enable automatic duplex configuration; port automatically detects whether it
should run in full- or half-duplex mode, depending on the attached device mode.
full Enable full-duplex mode.
half Enable half-duplex mode (for Fast Ethernet ports only).
Usage Guidelines This command is not available on small form-factor pluggable (SFP) module ports unless a
1000BASE-T SFP module is in the port. All other SFP modules operate only in full-duplex mode.
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.
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.
You cannot configure duplex mode on SFP module interfaces. However, when a 1000BASE-T SFP
module is in the SFP module port, you can configure duplex mode to auto or full.
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/1000 Mbps ports, if both the speed and duplex are set to specific values, autonegotiation is
disabled.
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.
Caution Changing the interface speed and duplex mode configuration might shut down and reenable the interface
during the reconfiguration.
Note For guidelines on setting the switch speed and duplex parameters, refer to the software configuration
guide for this release.
Examples This example shows how to configure an interface for full duplex operation:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# duplex full
You can verify your setting by entering the show interfaces privileged EXEC command.
Syntax Description all Enable error detection for all error-disable cases.
dtp-flap Enable error detection for the Dynamic Trunking Protocol (DTP) flapping.
gbic-invalid Enable error detection for an invalid GBIC.
Note On the Catalyst 3750 switch, this error refers to an invalid small form-factor
pluggable (SFP) module interface cause.
link-flap Enable error detection for link-state flapping.
loopback Enable error detection for detected loopbacks.
pagp-flap Enable error detection for the Port Aggregation Protocol (PAgP) flap-error disable
cause.
Note Though visible in the command-line help strings, the dhcp-rate-limit keyword is not supported.
Usage Guidelines A cause (dtp-flap, gbic-invalid, link-flap, loopback, and pagp-flap) is the reason why the
error-disabled state occurred. When a cause is detected on an interface, the interface is placed in an
error-disabled state, an operational state 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 disable detection for the link-flap error-disable cause:
Switch(config)# errdisable detect cause link-flap
You can verify your setting by entering the show errdisable detect privileged EXEC command.
errdisable recovery
Use the errdisable recovery global configuration command on the switch stack or on a standalone
switch to configure the recover mechanism variables. Use the no form of this command to return to the
default setting.
Syntax Description cause Enable error disable to recover from a specific cause.
all Enable the timer to recover from all error-disable causes.
bpduguard Enable the timer to recover from the bridge protocol data unit (BPDU) guard
error-disable state.
dtp-flap Enable the timer to recover from the Dynamic Trunking Protocol (DTP) flap
error-disable state.
gbic-invalid Enable the timer to recover from an invalid GBIC error-disable state.
Note On the Catalyst 3750 switch, this error refers to an invalid small
form-factor pluggable (SFP) interface state.
link-flap Enable the timer to recover from the link-flap error-disable state.
loopback Enable the timer to recover from a loopback error-disable state.
pagp-flap Enable the timer to recover from the Port Aggregation Protocol (PAgP)-flap
error-disable state.
psecure-violation Enable the timer to recover from a port security violation disable state.
security-violation Enable the timer to recover from an 802.1X violation disable state
udld Enable the timer to recover from the UniDirectional Link Detection (UDLD)
error-disable state.
vmps Enable the timer to recover from the VLAN Membership Policy Server
(VMPS) error-disable state.
interval interval Specify the time to recover from the specified error-disable state. The range
is 30 to 86400 seconds. The same interval is applied to all causes. The default
interval is 300 seconds.
Note The errdisable recovery timer is initialized at a random differential from
the configured interval value. The difference between the actual timeout
value and the configured value can be up to 15 percent of the configured
interval.
Note Though visible in the command-line help strings, the dhcp-rate-limit, unicast-flood, and
channel-misconfig keywords are not supported.
Usage Guidelines A cause (bpduguard, dtp-flap, gbic-invalid, 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 bpduguard
You can verify your settings by entering the show errdisable recovery privileged EXEC command.
flowcontrol
Use the flowcontrol interface configuration command on the switch stack or on a standalone switch 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.
Note The Catalyst 3750 switch can only receive pause frames.
Syntax Description receive Sets whether the interface can receive flow-control packets from a remote device.
desired Allows an interface to operate with an attached device that is required to send
flow-control packets or with an attached device that is not required to but can send
flow-control packets.
off Turns off an attached device’s ability to send flow-control packets to an interface.
on Allows an interface to operate with an attached device that is required to send
flow-control packets or with an attached device that is not required to but can send
flow-control packets.
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:
• receive on or desired: The port cannot send out pause frames, but can operate with an attached
device that is required to or is able to send pause frames; the port is able to receive pause frames.
• receive off: Flow control does not operate in either direction. In case of congestion, no indication
is given to the link partner and no pause frames are sent or received by either device.
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.
Table 2-5 Flow Control Settings and Local and Remote Port Flow Control Resolution
Examples This example shows how to configure the local port to not support flow control by the remote port:
Switch(config-if)# flowcontrol receive off
You can verify your settings by entering the show interfaces privileged EXEC command.
interface port-channel
Use the interface port-channel global configuration command on the switch stack or on a standalone
switch to access or create the port-channel logical interface. Use the no form of this command to remove
the port-channel.
Usage Guidelines For Layer 2 EtherChannels, you do not have to create a port-channel interface first before assigning a
physical interface to a channel group. Instead, you can use the channel-group interface configuration
command. It automatically creates the port-channel interface when the channel group gets its first
physical interface. If you create the port-channel interface 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 When using a port-channel interface as a routed interface, do not assign Layer 3 addresses on the
physical interfaces that are assigned to the channel group.
Caution Do not assign bridge groups on the physical interfaces in a channel group used as a Layer 3 port-channel
interface because it creates loops. You must also disable spanning tree.
Follow these guidelines when you use the interface port-channel command:
• If you want to use the Cisco Discovery Protocol (CDP), you must configure it only on the physical
interface and not on the port-channel interface.
• 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.
For a complete list of configuration guidelines, refer to the “Configuring EtherChannels” chapter in the
software guide for this release.
Examples This example shows how to create a port-channel interface with a port channel number of 5:
Switch(config)# interface port-channel 5
You can verify your setting by entering the show running-config privileged EXEC or show
etherchannel channel-group-number detail privileged EXEC command.
interface range
Use the interface range global configuration command on the switch stack or on a standalone switch 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.
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.
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 nonvolatile RAM (NVRAM), but the
interface range itself is not saved to NVRAM.
You can enter the interface range in two ways:
• Specifying up to five interface ranges
• Specifying a previously defined interface-range macro
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.
Note When you use the interface range command with port channels, the first and last port channel number
in the range must be active port channels.
When you define a range, you must enter a space between the first entry and the hyphen (-):
interface range gigabitethernet1/0/1 -2
When 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 - 2
interface range gigabitethernet1/0/3 -5, gigabitethernet1/0/7 -8
You 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 For more information about configuring interface ranges, refer to the software configuration guide for
this release.
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 - 2
Switch(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 - 2
Switch(config)# interface range macro macro1
Switch(config-if-range)#
interface vlan
Use the interface vlan global configuration command on the switch stack or on a standalone switch 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.
Note When you create an SVI, it does not become active until it is associated with a physical port.
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 stack 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 23
Switch(config-if)#
You can verify your setting by entering the show interfaces and show interfaces vlan vlan-id privileged
EXEC commands.
ip access-group
Use the ip access-group interface configuration command on the switch stack or on a standalone switch
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.
Syntax Description access-list-number The number of the IP access control list (ACL). The range is 1 to 199 or
1300 to 2699.
name The name of an IP ACL, specified in the ip access-list global configuration
command.
in Specify filtering on inbound packets.
out Specify filtering on outbound packets. This keyword is valid only on
Layer 3 interfaces.
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 only apply ACLs in the inbound direction; the out keyword is not supported for Layer 2
interfaces.
• You can only apply one IP ACL and one MAC ACL per interface.
• Layer 2 interfaces do not support logging; if the log keyword is specified in the IP ACL, it is
ignored.
• An IP ACL applied to a Layer 2 interface only filters IP packets. To filter non-IP packets, use the
mac access-group interface configuration command with MAC extended 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.
• When an input port ACL is applied to an interface and a VLAN map is applied to a VLAN that the
interface is a member of, incoming packets received on ports with the ACL applied are filtered by
the port ACL. Other packets are filtered by the VLAN map.
• When an input router ACL and input port ACLs exist in an switch virtual interface (SVI), incoming
packets received on ports to which a port ACL is applied are filtered by the port ACL. Incoming
routed IP packets received on other ports are filtered by the router ACL. Other packets are not
filtered.
• When an output router ACL and input port ACLs exist in an SVI, incoming packets received on the
ports to which a port ACL is applied are filtered by the port ACL. Outgoing routed IP packets are
filtered by the router ACL. Other packets are not filtered.
• When a VLAN map, input router ACLs, and input port ACLs exist in an SVI, incoming packets
received on the ports to which a port ACL is applied are only filtered by the port ACL. Incoming
routed IP packets received on other ports are filtered by both the VLAN map and the router ACL.
Other packets are filtered only by the VLAN map.
• When a VLAN map, output router ACLs, and input port ACLs exist in an SVI, incoming packets
received on the ports to which a port ACL is applied are only filtered by the port ACL. Outgoing
routed IP packets are filtered by both the VLAN map and the router ACL. Other packets are filtered
only by the 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 Gigabit Ethernet interface
0/1 on stack member 1:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group 101 in
You can verify your settings by entering the show ip interface, show access-lists, or show ip
access-lists privileged EXEC command.
ip address
Use the ip address interface configuration command on the switch stack or on a standalone switch 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.
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 If any router on a network segment uses a secondary address, all other devices on that same segment
must also use a secondary address from the same network or subnet. Inconsistent use of secondary
addresses on a network segment can very quickly cause routing loops.
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 Dynamic Host
Configuration Protocol (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 1
Switch(config-if)# ip address 172.20.128.2 255.255.255.0
This example shows how to configure the IP address for a port on the Layer 3 switch:
Switch(config)# ip multicast-routing
Switch(config)# interface gigabitethernet6/0/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 172.20.128.2 255.255.255.0
You can verify your settings by entering the show running-config privileged EXEC command.
ip igmp filter
Use the ip igmp filter interface configuration command on the switch stack or on a standalone switch
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.
no ip igmp filter
Syntax Description profile number The IGMP profile number to be applied. The range is 1 to 4294967295.
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.
You can verify your setting by using the show running-config privileged EXEC command and by
specifying an interface.
ip igmp max-groups
Use the ip igmp max-groups interface configuration command on the switch stack or on a standalone
switch to set the maximum number of Internet Group Management Protocol (IGMP) groups that a
Layer 2 interface can join. Use the no form of this command to set the maximum back to the default,
which is to have no maximum limit.
no ip igmp max-groups
Syntax Description number The maximum number of IGMP groups that an interface can join. The range is 0 to
4294967294. The default is no limit.
Defaults No limit.
Usage Guidelines You can use this command only on Layer 2 physical interfaces; you cannot set IGMP maximum groups
for routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
Examples This example shows how to limit the number of IGMP groups that an interface can join to 25.
Switch(config)# interface gigabitethernet1/0/12
Switch(config-if)# ip igmp max-groups 25
You can verify your setting by using the show running-config privileged EXEC command and by
specifying an interface.
ip igmp profile
Use the ip igmp profile global configuration command on the switch stack or on a standalone switch 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.
Syntax Description profile number The IGMP profile number being configured. The range is 1 to 4294967295.
Defaults No IGMP profiles are defined. When configured, the default action for matching an IGMP profile is to
deny matching addresses.
Usage Guidelines When you are in IGMP profile configuration mode, you can create the profile by using these commands:
• deny: specifies that matching addresses are denied; this is the default condition.
• exit: exits from igmp-profile configuration mode.
• no: negates a command or resets to its defaults.
• permit: specifies that matching addresses are permitted.
• range: specifies a range of IP addresses for the profile. This can be a single IP address or a range
with a start and an end address.
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 40
Switch(config-igmp-profile)# permit
Switch(config-igmp-profile)# range 233.1.1.1 233.255.255.255
You can verify your settings by using the show ip igmp profile privileged EXEC command.
ip igmp snooping
Use the ip igmp snooping global configuration command on the switch stack or on a standalone switch
to globally enable Internet Group Management Protocol (IGMP) snooping on the switch or to enable it
on a VLAN. Use the command with keywords to enable and configure IGMP snooping on a VLAN
interface. Use the no form of this command to disable IGMP snooping or to reset the parameters to the
default settings.
ip igmp snooping [vlan vlan-id [immediate-leave | mrouter {interface interface-id | learn {cgmp
| pim-dvmrp}} | static ip-address interface interface-id]]
Syntax Description vlan vlan-id (Optional) When used with other keywords, enable IGMP snooping on a
VLAN interface. Use the no form of this command to disable IGMP
snooping on a VLAN interface. The range is 1 to 4094.
immediate-leave (Optional) Enable IGMP immediate-leave processing on a VLAN interface.
Use the no form of the command to disable the Immediate Leave feature on
the interface.
mrouter (Optional) Add a multicast router port or configure the multicast router
learning method. The no form of the command removes the configuration.
interface interface-id (Optional) With mrouter, specify the next-hop interface to the multicast
router.
With static, specify the interface of the member port. It can be one of these
values:
• fastethernet interface number—a Fast Ethernet 802.3 interface.
• gigabitethernet interface number—a Gigabit Ethernet 802.3Z interface.
• port-channel interface number—a channel interface. The range is 0 to
12.
learn (Optional) With mrouter, specify the multicast router learning method.
cgmp Set the switch to learn multicast router ports by snooping on Cisco Group
Management Protocol (CGMP) packets.
pim-dvmrp Set the switch to learn multicast router ports by snooping on IGMP queries
and Protocol-Independent Multicast-Distance Vector Multicast Routing
Protocol (PIM-DVMRP) packets.
static ip-address (Optional) Add a Layer 2 port as a member of a multicast group with the
specified group IP address.
Note Though visible in the command-line help string, the report-suppression, source-only-learning, and tcn
keywords are not supported.
Usage Guidelines When IGMP snooping is enabled globally, it is enabled in all the existing VLAN interfaces. When IGMP
snooping is disabled globally, it is disabled on all the existing VLAN interfaces.
You should only configure the Immediate Leave feature when there is a maximum of one receiver on
every port in the VLAN. The configuration is saved in nonvolatile RAM (NVRAM).
The Immediate Leave feature is supported only with IGMP version 2 hosts.
The CGMP learn method is useful for reducing control traffic.
The static keyword is used for configuring the IGMP member ports statically.
The enabled configuration (globally or per VLAN), the learn method, and the static ports and groups are
saved in nonvolatile RAM (NVRAM).
This example shows how to configure Gigabit Ethernet interface 2 on stack member 1 as a multicast
router port:
Switch(config)# ip igmp snooping vlan 1 mrouter interface gigabitethernet1/0/2
This example shows how to specify the multicast router learning method as CGMP:
Switch(config)# no ip igmp snooping vlan 1 mrouter learn cgmp
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
lacp port-priority
Use the lacp port-priority interface configuration command on the switch stack or on a standalone
switch 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.
no lacp port-priority
Syntax Description priority Port priority for LACP. The range is 1 to 65535.
Usage Guidelines This command takes effect only on EtherChannel interfaces that are already configured for LACP.
The software assigns to every link between systems that operate LACP a unique priority made up of the
system priority, system ID, port priority, and the port number. In priority comparisons, numerically
lower values have higher priority. The priority determines which ports should be put in standby mode
when there is a hardware limitation that prevents all compatible ports from aggregating.
Ports are considered for active use in aggregation in link-priority order starting with the port attached to
the highest priority link. Each port is selected for active use if the preceding higher priority selections
can also be maintained. Otherwise, the port is selected for standby mode. 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).
The lower the priority, the more likely that the interface will be used for LACP transmission.
For information about configuring LACP on physical interfaces, refer to the “Configuring
EtherChannels” chapter in the software configuration guide for this release.
Examples This example shows how to configure the LACP port priority on Gigabit Ethernet interface 0/1 on stack
member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# lacp port-priority 1000
You can verify your settings by entering the show lacp [channel-group-number] internal privileged
EXEC command.
lacp system-priority
Use the lacp system-priority global configuration command on the switch stack or on a standalone
switch 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.
no lacp system-priority
Syntax Description priority System priority for LACP. The range is 1 to 65535.
Usage Guidelines Although this is a global configuration command, the priority takes effect only on EtherChannels that
have physical interfaces that are already configured for LACP.
The software assigns to every link between systems that operate LACP a unique priority made up of the
system priority, system ID, port priority, and the port number. In priority comparisons, numerically
lower values have higher priority. The priority determines which ports should be put in standby mode
when there is a hardware limitation that prevents all compatible ports from aggregating.
Ports are considered for active use in aggregation in link-priority order, starting with the port attached
to the highest priority link. Each port is selected for active use if the preceding higher priority selections
can also be maintained. Otherwise, the port is selected for standby mode. 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).
The lower the priority, the more likely that the interface will be used for LACP transmission.
For more information about configuring LACP on physical interfaces, refer to 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 20000
You can verify your settings by entering the show lacp sys-id privileged EXEC command.
logging file
Use the logging file global configuration command on the switch stack or on a standalone switch to set
logging file parameters. Use the no form of this command to return to the default setting.
Syntax Description filesystem:filename Alias for a Flash file system. Contains the path and name of the file that
contains the log messages.
The syntax for the local Flash file system on the stack member or the stack
master:
flash:
From the stack master, the syntax for the local Flash file system on a stack
member:
flash member number
max-file-size (Optional) Specify the maximum logging file size. The range is 4096 to
2147483647.
min-file-size (Optional) Specify the minimum logging file size. The range is 1024 to
2147483647.
severity-level-number (Optional) Specify the logging severity level. The range is 0 to 7. See the
type option for the meaning of each level.
type (Optional) Specify the logging type. These keywords are valid:
• emergencies—System is unusable (severity 0).
• alerts—Immediate action needed (severity 1).
• critical—Critical conditions (severity 2).
• errors—Error conditions (severity 3).
• warnings—Warning conditions (severity 4).
• notifications—Normal but significant messages (severity 5).
• information—Information messages (severity 6).
• debugging—Debugging messages (severity 7).
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).
Usage Guidelines The log file is stored in ASCII text format in an internal buffer on a standalone switch, and in the case
of a switch stack, on the stack master. If a standalone switch or the stack master 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 informational
You can verify your setting by entering the show running-config privileged EXEC command.
mac access-group
Use the mac access-group interface configuration command on the switch stack or on a standalone
switch 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.
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 For more information about configuring MAC extended ACLs, refer to the “Configuring Network
Security with ACLs” chapter in the software configuration guide for this release.
Examples This example shows how to apply a MAC extended ACL named macacl2 to an interface:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mac access-group macacl2 in
You 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.
Note You cannot apply named MAC extended ACLs to Layer 3 interfaces.
Syntax Description name Assign a name to the MAC extended access list.
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:
• default: sets a command to its default.
• deny: specifies packets to reject. For more information, see the deny MAC-access list configuration
command.
• exit: exits from MAC-access list configuration mode.
• no: negates a command or sets its defaults.
• permit: specifies packets to forward. For more information, see the permit command.
Note For more information about MAC extended access lists, refer to the software configuration guide for this
release.
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 mac1
Switch(config-ext-macl)#
This example shows how to delete MAC named extended access list mac1:
Switch(config)# no mac access-list extended mac1
You can verify your settings by entering the show access-lists privileged EXEC command.
mac-address-table aging-time
Use the mac-address-table aging-time global configuration command on the switch stack or on a
standalone switch 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.
Syntax Description 0 This value disables aging. Static address entries are never aged or removed from
the table.
10-100000 Aging time in seconds. The range is 10 to 1000000 seconds.
vlan vlan-id (Optional) Specify the VLAN ID to which to apply the aging time. The range is
1 to 4094.
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 200
You can verify your setting by entering the show mac-address-table aging-time privileged EXEC
command.
mac-address-table notification
Use the mac-address-table notification global configuration command on the switch stack or on a
standalone switch to enable the MAC address notification feature on the switch stack. Use the no form
of this command to return to the default setting.
Syntax Description history-size value (Optional) Configure the maximum number of entries in the MAC
notification history table. The range is 1 to 500 entries.
interval value (Optional) Set the notification trap interval. The switch stack sends the
notification traps when this amount of time has elapsed. The range is 0 to
2147483647 seconds.
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 notification
Switch(config)# mac-address-table notification interval 60
Switch(config)# mac-address-table notification history-size 100
You can verify your settings by entering the show mac-address-table notification privileged EXEC
command.
mac-address-table static
Use the mac-address-table static global configuration command on the switch stack or on a standalone
switch to add static addresses to the MAC address table. Use the no form of this command to remove
static entries from the table.
Syntax Description mac-addr Destination MAC address (unicast or multicast) to add to the address
table. Packets with this destination address received in the specified
VLAN are forwarded to the specified interface.
vlan vlan-id Specify the VLAN for which the packet with the specified MAC address
is received. The range is 1 to 4094.
interface interface-id Interface to which the received packet is forwarded. Valid interfaces
include physical ports and port channels.
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
gigabitethernet6/0/1
You can verify your setting by entering the show mac-address-table privileged EXEC command.
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 ip address Set the access map to match packets against an IP address access list.
mac address Set the access map to match packets against a MAC address access list.
name Name of the access list to match packets against.
number Number of the access list to match packets against. This option is not valid for MAC
access lists.
Defaults The default action is to have no match parameters applied to a VLAN map.
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 vmap4
Switch(config-access-map)# match ip address al2
Switch(config-access-map)# action drop
Switch(config-access-map)# exit
Switch(config)# vlan filter vmap4 vlan-list 5-6
You can verify your settings by entering the show vlan access-map privileged EXEC command.
Syntax Description access-group Number or name of an IP standard or extended access control list (ACL) or
acl-index-or-name MAC ACL. For an IP standard ACL, the ACL index range is 1 to 99 and 1300
to 1999. For an IP extended ACL, the ACL index range is 100 to 199 and
2000 to 2699.
ip dscp dscp-list List of up to eight IP Differentiated Services Code Point (DSCP) values to
match against incoming packets. Separate each value with a space. The range
is 0 to 63. You also can enter a mnemonic name for a commonly-used value.
ip precedence List of up to eight IP-precedence values to match against incoming packets.
ip-precedence-list Separate each value with a space. The range is 0 to 7. You also can enter a
mnemonic name for a commonly-used value
Note Though visible in the command-line help strings, the any, class-map, destination-address,
input-interface, mpls, not, protocol, and source-address keywords are not supported.
Usage Guidelines The match command is used to specify which fields in the incoming packets are examined to classify
the packets. Only the IP access group or the MAC access group matching to the Ether Type/Len are
supported.
To define packet classification on a physical-port basis, only one match command per class map is
supported. In this situation, the match-all and match-any keywords are equivalent.
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.
This example shows how to create a class map called class2, which matches all the incoming traffic with
DSCP values of 10, 11, and 12:
Switch(config)# class-map class2
Switch(config-cmap)# match ip dscp 10 11 12
Switch(config-cmap)# exit
This example shows how to create a class map called class3, which matches all the incoming traffic with
IP-precedence values of 5, 6, and 7:
Switch(config)# class-map class3
Switch(config-cmap)# match ip precedence 5 6 7
Switch(config-cmap)# exit
This example shows how to delete the IP-precedence match criteria and to classify traffic using acl1:
Switch(config)# class-map class2
Switch(config-cmap)# match ip precedence 5 6 7
Switch(config-cmap)# no match ip precedence
Switch(config-cmap)# match access-group acl1
Switch(config-cmap)# exit
You can verify your settings by entering the show class-map privileged EXEC command.
mdix auto
Use the mdix auto interface configuration command on the switch stack or on a standalone switch to
enable the automatic media-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 auto
Usage Guidelines When you enable Auto-MDIX on an interface, you must also set the speed and duplex on the interface
to auto so that the feature operates correctly.
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 and 10/100/1000-Mbps 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.
Examples This example shows how to enable Auto-MDIX on Gigabit Ethernet interface 0/1 on stack member 1:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# speed auto
Switch(config-if)# duplex auto
Switch(config-if)# mdix auto
Switch(config-if)# end
You can verify the operational state of Auto-MDIX on the interface by entering the show controllers
ethernet-controller interface-id phy privileged EXEC command.
mls qos
Use the mls qos global configuration command on the switch stack or on a standalone switch 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
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 DSCP and 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 and egress queue settings are in effect.
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.
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.
You can verify your settings by entering the show mls qos privileged EXEC command.
Syntax Description aggregate-policer-name Name of the aggregate policer referenced by the police aggregate
policy-map class configuration command.
rate-bps Specify the average traffic rate in bits per second (bps). The range is
8000 to 1000000000.
burst-byte Specify the normal burst size in bytes. The range is 8000 to 1000000.
exceed-action drop When the specified rate is exceeded, specify that the switch drop the
packet.
exceed-action When the specified rate is exceeded, specify that the switch change the
policed-dscp-transmit Differentiated Services Code Point (DSCP) of the packet to that
specified in the policed-DSCP map and then send the packet.
Usage Guidelines 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.
The port ASIC supports 256 policers (255 policers plus 1 no policer). The maximum number of policers
supported per port is 64. 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.
Policing uses a token-bucket algorithm. 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) that 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, refer to 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 drop
Switch(config)# policy-map policy2
Switch(config-pmap)# class class1
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class3
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police aggregate agg_policer2
Switch(config-pmap-c)# exit
You can verify your settings by entering the show mls qos aggregate-policer privileged EXEC
command.
Syntax Description default-cos Assign a default CoS value to a port. If packets are untagged, the default CoS value
becomes the packet CoS value. The CoS range is 0 to 7.
override Override the CoS of the incoming packets, and apply the default CoS value on the
port to all incoming packets.
Usage Guidelines You can use the default value to assign a CoS and Differentiated Services Code Point (DSCP) value to
all incoming packets that are untagged (if the incoming packet does not have a CoS value). You also can
assign a default CoS and DSCP value to all incoming packets by using the override keyword.
Use the override keyword when all incoming 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 incoming CoS
values are assigned the default CoS value configured with the mls qos cos command. If an incoming
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 Gigabit Ethernet interface 0/1 of stack
member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos trust cos
Switch(config-if)# mls qos cos 4
This example shows how to assign all the packets entering a port to the default port CoS value of 4 on
Gigabit Ethernet interface 0/1 of stack member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos cos 4
Switch(config-if)# mls qos cos override
You can verify your settings by entering the show mls qos interface privileged EXEC command.
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 incoming DSCPs to the same
DSCP values.
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 interface (ingress mutation) at the
boundary of a quality of service (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 interface 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 class of service (CoS) or IP-precedence trusted port, the command has no immediate effect until
the port becomes DSCP-trusted.
Examples This example shows how to define the DSCP-to-DSCP-mutation map named dscpmutation1and to apply
the map to a port on stack member 3:
Switch(config)# mls qos map dscp-mutation dscpmutation1 10 11 12 13 to 30
Switch(config)# interface gigabitethernet3/0/1
Switch(config-if)# mls qos trust dscp
Switch(config-if)# mls qos dscp-mutation dscpmutation1
This 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 dscpmutation1
You can verify your settings by entering the show mls qos maps privileged EXEC command.
CoS Value 0 1 2 3 4 5 6 7
DSCP Value 0 8 16 24 32 40 48 56
DSCP Value 0–7 8–15 16–23 24–31 32–39 40–47 48–55 56–63
CoS Value 0 1 2 3 4 5 6 7
IP Precedence Value 0 1 2 3 4 5 6 7
DSCP Value 0 8 16 24 32 40 48 56
The default DSCP-to-DSCP-mutation map is a null map, which maps an incoming DSCP value to the
same DSCP value.
The default policed-DSCP map is a null map, which maps an incoming DSCP value to the same DSCP
value.
Usage Guidelines All the maps are globally defined. All the maps, except the DSCP-to-DSCP-mutation map, are applied
to all ports. The DSCP-to-DSCP-mutation map is applied to a specific port.
Examples This example shows how to define the IP-precedence-to-DSCP map and to map IP-precedence values 0
to 7 to DSCP values of 0, 10, 20, 30, 40, 50, 55, and 60:
Switch# configure terminal
Switch(config)# mls qos map ip-prec-dscp 0 10 20 30 40 50 55 60
This example shows how to define the policed-DSCP map. DSCP values 1, 2, 3, 4, 5, and 6 are marked
down to DSCP value 0. Marked DSCP values that not explicitly configured are not modified:
Switch# configure terminal
Switch(config)# mls qos map policed-dscp 1 2 3 4 5 6 to 0
This example shows how to define the DSCP-to-CoS map. DSCP values 20, 21, 22, 23, and 24 are
mapped to CoS 1. DSCP values 10, 11, 12, 13, 14, 15, 16, and 17 are mapped to CoS 0:
Switch# configure terminal
Switch(config)# mls qos map dscp-cos 20 21 22 23 24 to 1
Switch(config)# mls qos map dscp-cos 10 11 12 13 14 15 16 17 to 0
This example shows how to define the CoS-to-DSCP map. CoS values 0 to 7 are mapped to DSCP values
0, 5, 10, 15, 20, 25, 30, and 35:
Switch# configure terminal
Switch(config)# mls qos map cos-dscp 0 5 10 15 20 25 30 35
This example shows how to define the DSCP-to-DSCP-mutation map. All the entries that are not
explicitly configured are not modified (remain as specified in the null map):
Switch# configure terminal
Switch(config)# mls qos map dscp-mutation mutation1 1 2 3 4 5 6 7 to 10
Switch(config)# mls qos map dscp-mutation mutation1 8 9 10 11 12 13 to 10
Switch(config)# mls qos map dscp-mutation mutation1 20 21 22 to 20
Switch(config)# mls qos map dscp-mutation mutation1 0 31 32 33 34 to 30
You can verify your settings by entering the show mls qos maps privileged EXEC command.
Syntax Description qset-id ID of the queue-set. Each port belongs to a queue-set, which defines all the
characteristics of the four egress queues per port. The range is 1 to 2.
allocation1 ... Buffer space allocation (percentage) for each queue (four values for queues 1 to 4).
allocation4 The range is 0 to 100. Separate each value with a space.
Defaults All allocation values are equally mapped among the four queues (25, 25, 25, 25). Each queue has 1/4 of
the buffer space.
Usage Guidelines Specify four allocation values, and separate each with a space.
Allocate buffers according to the importance of the traffic; for example, give a large percentage of the
buffer to the queue with the highest-priority traffic.
To configure different classes of traffic with different characteristics, use this command with the mls qos
queue-set output qset-id threshold global configuration command.
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Examples This example shows how to map Fast Ethernet interface 0/1 on stack member 2 to queue-set 2. It
allocates 40 percent of the buffer space to egress queue 1 and 20 percent to egress queues 2, 3, and 4:
Switch(config)# mls qos queue-set output 2 buffers 40 20 20 20
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# queue-set 2
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show
mls qos queue-set privileged EXEC command.
Syntax Description qset-id ID of the queue-set. Each port belongs to a queue-set, which defines all the
characteristics of the four egress queues per port. The range is 1 to 2.
queue-id Specific queue in the queue-set on which the command is performed. The
range is 1 to 4.
drop-threshold1 Two WTD thresholds expressed as a percentage of the queue’s allocated
drop-threshold2 memory. The range is 1 to 400 percent.
reserved-threshold Amount of memory to be guaranteed (reserved) for the queue and expressed
as a percentage of the allocated memory. The range is 1 to 100 percent.
maximum-threshold Enable a queue in the full condition to obtain more buffers than are reserved
for it. This is the maximum memory the queue can have before the packets
are dropped. The range is 1 to 400 percent.
Usage Guidelines Use the mls qos queue-set output qset-id buffers global configuration command to allocate a fixed
number of buffers to the four queues in a queue-set.
The drop-threshold percentages can exceed 100 percent and can be up to the maximum (if the maximum
threshold exceeds 100 percent).
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
The switch uses a buffer allocation scheme to reserve a minimum amount of buffers for each egress
queue, to prevent any queue or port from consuming all the buffers and depriving other queues, and to
determine whether to grant buffer space to a requesting queue. The switch determines whether the target
queue has not consumed more buffers than its reserved amount (under-limit), whether it has consumed
all of its maximum buffers (over-limit), and whether the common pool is empty (no free buffers) or not
empty (free buffers). If the queue is not over-limit, the switch can allocate buffer space from the reserved
pool or from the common pool (if it is not empty). If there are no free buffers in the common pool or if
the queue is over-limit, the switch drops the frame.
Examples This example shows how to map Fast Ethernet interface 0/1 on stack member 2 to queue-set 2. It
configures the drop thresholds for queue 2 to 40 and 60 percent of the allocated memory, guarantees
(reserves) 100 percent of the allocated memory, and configures 200 percent as the maximum memory
this queue can have before packets are dropped:
Switch(config)# mls qos queue-set output 2 threshold 2 40 60 100 200
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# queue-set 2
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show
mls qos queue-set privileged EXEC command.
Syntax Description weight1 weight2 Ratio of weight1 and weight2 determines the ratio of the frequency in which the
SRR scheduler dequeues packets from ingress queues 1 and 2. The range is 1 to
100. Separate each value with a space.
Defaults Weight1 and weight2 are 4 (1/2 of the bandwidth is equally shared between the two queues).
Usage Guidelines SRR services the priority queue for its configured weight as specified by the bandwidth keyword in the
mls qos srr-queue input priority-queue queue-id bandwidth weight global configuration command.
Then SRR shares the remaining bandwidth with both ingress queues and services them as specified by
the weights configured with the mls qos srr-queue input bandwidth weight1 weight2 global
configuration command.
You specify which ingress queue is the priority queue by using the mls qos srr-queue input
priority-queue global configuration command.
Examples This example shows how to assign the ingress bandwidth for the queues in the stack. Priority queueing
is disabled, and the shared bandwidth ratio allocated to queue 1 is 25/(25+75) and to queue 2 is
75/(25+75):
Switch(config)# mls qos srr-queue input priority-queue 2 bandwidth 0
Switch(config)# mls qos srr-queue input bandwidth 25 75
In this example, queue 2 has three times the bandwidth of queue 1; queue 2 is serviced three times as
often as queue 1.
This example shows how to assign the ingress bandwidths for the queues in the stack. Queue 1 is the
priority queue with 10 percent of the bandwidth allocated to it. The bandwidth ratio allocated to queues
1 and 2 is 4/(4+4). SRR services queue 1 (the priority queue) first for its configured 10 percent
bandwidth. Then SRR equally shares the remaining 90 percent of the bandwidth between queues 1 and
2 by allocating 45 percent to each queue:
Switch(config)# mls qos srr-queue input priority-queue 1 bandwidth 10
Switch(config)# mls qos srr-queue input bandwidth 4 4
You can verify your settings by entering the show mls qos interface [interface-id] queueing or the show
mls qos input-queue privileged EXEC command.
Syntax Description percentage1 Percentage of buffers allocated to ingress queues 1 and 2. The range is 0 to
percentage2 100. Separate each value with a space.
Defaults Ninety percent of the buffers is allocated to queue 1, and 10 percent of the buffers is allocated to queue 2.
Usage Guidelines You should allocate the buffers so that the queues can handle any incoming bursty traffic.
Examples This example shows how to allocate 60 percent of the buffer space to ingress queue 1 and 40 percent of
the buffer space to ingress queue 2:
Switch(config)# mls qos srr-queue input buffers 60 40
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show
mls qos input-queue privileged EXEC command.
mls qos srr-queue input cos-map queue queue-id {cos1...cos8 | threshold threshold-id
cos1...cos8}
Defaults Table 2-10 shows the default CoS input queue threshold map:
Usage Guidelines The CoS assigned at the ingress port selects an ingress or egress queue and threshold.
The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state. You can
assign two weighted tail-drop (WTD) threshold percentages to an ingress queue by using the mls qos
srr-queue input threshold global configuration command.
You can map each CoS value to a different queue and threshold combination, allowing the frame to
follow different behavior.
Examples This example shows how to map CoS values 0 to 3 to ingress queue 1 and to threshold ID 1 with a drop
threshold of 50 percent. It maps CoS values 4 and 5 to ingress queue 1 and to threshold ID 2 with a drop
threshold of 70 percent:
Switch(config)# mls qos srr-queue input cos-map queue 1 threshold 1 0 1 2 3
Switch(config)# mls qos srr-queue input cos-map queue 1 threshold 2 4 5
Switch(config)# mls qos srr-queue input threshold 1 50 70
You can verify your settings by entering the show mls qos maps privileged EXEC command.
mls qos srr-queue input dscp-map queue queue-id {dscp1...dscp8 | threshold threshold-id
dscp1...dscp8}
Defaults Table 2-11 shows the default DSCP input queue threshold map:
Usage Guidelines The DSCP assigned at the ingress port selects an ingress or egress queue and threshold.
The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state. You can
assign two weighted tail-drop (WTD) threshold percentages to an ingress queue by using the mls qos
srr-queue input threshold global configuration command.
You can map each DSCP value to a different queue and threshold combination, allowing the frame to
follow different behavior.
You can map up to eight DSCP values per command.
Examples This example shows how to map DSCP values 0 to 6 to ingress queue 1 and to threshold 1 with a drop
threshold of 50 percent. It maps DSCP values 20 to 26 to ingress queue 1 and to threshold 2 with a drop
threshold of 70 percent:
Switch(config)# mls qos srr-queue input dscp-map queue 1 threshold 1 0 1 2 3 4 5 6
Switch(config)# mls qos srr-queue input dscp-map queue 1 threshold 2 20 21 22 23 24 25 26
Switch(config)# mls qos srr-queue input threshold 1 50 70
You can verify your settings by entering the show mls qos maps privileged EXEC command.
Defaults The priority queue is queue 2, and 10 percent of the bandwidth is allocated to it.
Usage Guidelines You should use the priority queue only for traffic that needs to be expedited (for example, voice traffic,
which needs minimum delay and jitter).
The priority queue is guaranteed part of the bandwidth on the stack ring, which reduces the delay and
jitter under heavy network traffic on an oversubscribed stack (when there is more traffic than the
backplane can carry, and the queues are full and dropping frames).
The amount of bandwidth that can be guaranteed is restricted because a large value affects the entire
stack and can degrade the stack performance.
Shaped round robin (SRR) services the priority queue for its configured weight as specified by the
bandwidth keyword in the mls qos srr-queue input priority-queue queue-id bandwidth weight global
configuration command. Then SRR shares the remaining bandwidth with both ingress queues and
services them as specified by the weights configured with the mls qos srr-queue input bandwidth
weight1 weight2 global configuration command.
To disable priority queueing, set the bandwidth weigh to 0, for example, mls qos srr-queue input
priority-queue queue-id bandwidth 0.
Examples This example shows how to assign the ingress bandwidths for the queues in the stack. Queue 1 is the
priority queue with 10 percent of the bandwidth allocated to it. The bandwidth ratio allocated to queues
1 and 2 is 4/(4+4). SRR services queue 1 (the priority queue) first for its configured 10 percent
bandwidth. Then SRR equally shares the remaining 90 percent of the bandwidth between queues 1 and
2 by allocating 45 percent to each queue:
Switch(config)# mls qos srr-queue input priority-queue 1 bandwidth 10
Switch(config)# mls qos srr-queue input bandwidth 4 4
You can verify your settings by entering the show mls qos interface [interface-id] queueing or the show
mls qos input-queue privileged EXEC command.
Usage Guidelines QoS uses the CoS-to-threshold map or the DSCP-to-threshold map to determine which class of service
(CoS) or Differentiated Services Code Points (DSCPs) values are mapped to threshold 1 and to threshold
2. If threshold 1 is exceeded, packets with CoS or DSCPs assigned to this threshold are dropped until
the threshold is no longer exceeded. However, packets assigned to threshold 2 continue to be queued and
sent as long as the second threshold is not exceeded.
Each queue has two configurable (explicit) drop threshold and one preset (implicit) drop threshold (full).
You configure the CoS-to-threshold map by using the mls qos srr-queue input cos-map global
configuration command. You configure the DSCP-to-threshold map by using the mls qos srr-queue
input dscp-map global configuration command.
Examples This example shows how to configure the tail-drop thresholds for the two queues. The queue 1
thresholds are 50 percent and 100 percent, and the queue 2 thresholds are 70 percent and 100 percent:
Switch(config)# mls qos srr-queue input threshold 1 50 100
Switch(config)# mls qos srr-queue input threshold 2 70 100
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show
mls qos input-queue privileged EXEC command.
mls qos srr-queue output cos-map queue queue-id {cos1...cos8 | threshold threshold-id
cos1...cos8}
Defaults Table 2-12 shows the default CoS output queue threshold map:
CoS Value 0, 1 2, 3 4 5 6, 7
Queue ID - Threshold ID 2-1 3-1 4-1 1 -1 4-1
Global configuration
Usage Guidelines The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state.
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your quality
of service (QoS) solution.
You can assign two weighted tail-drop (WTD) threshold percentages to an egress queue by using the mls
qos queue-set output qset-id threshold global configuration command.
You can map each CoS value to a different queue and threshold combination, allowing the frame to
follow different behavior.
Examples This example shows how to map Fast Ethernet interface 0/1 on stack member 2 to queue-set 1. It maps
CoS values 0 to 3 to egress queue 1 and to threshold ID 1. It configures the drop thresholds for queue 1
to 50 and 70 percent of the allocated memory, guarantees (reserves) 100 percent of the allocated memory,
and configures 200 percent as the maximum memory that this queue can have before packets are
dropped.
Switch(config)# mls qos srr-queue output cos-map queue 1 threshold 1 0 1 2 3
Switch(config)# mls qos queue-set output 1 threshold 1 50 70 100 200
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# queue-set 1
You can verify your settings by entering the show mls qos maps, the show mls qos interface
[interface-id] buffers, or the show mls qos queue-set privileged EXEC command.
mls qos srr-queue output dscp-map queue queue-id {dscp1...dscp8 | threshold threshold-id
dscp1...dscp8}
Defaults Table 2-13 shows the default DSCP output queue threshold map:
Usage Guidelines The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state.
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
You can assign two weighted tail-drop (WTD) threshold percentages to an egress queue by using the mls
qos queue-set output qset-id threshold global configuration command.
You can map each DSCP value to a different queue and threshold combination, allowing the frame to
follow different behavior.
You can map up to eight DSCP values per command.
Examples This example shows how to map Fast Ethernet interface 0/1 on stack member 2 to queue-set 1. It maps
DSCP values 0 to 3 to egress queue 1 and to threshold ID 1. It configures the drop thresholds for queue 1
to 50 and 70 percent of the allocated memory, guarantees (reserves) 100 percent of the allocated memory,
and configures 200 percent as the maximum memory that this queue can have before packets are
dropped.
Switch(config)# mls qos srr-queue output dscp-map queue 1 threshold 1 0 1 2 3
Switch(config)# mls qos queue-set output 1 threshold 1 50 70 100 200
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# queue-set 1
You can verify your settings by entering the show mls qos maps, the show mls qos interface
[interface-id] buffers, or the show mls qos queue-set privileged EXEC command.
Syntax Description cos (Optional) Classify an ingress packet by using the packet CoS value. For an
untagged packet, use the port default CoS value.
device cisco-phone (Optional) Classify ingress packets by trusting the value sent from the Cisco
IP phone (trusted boundary).
dscp (Optional) Classify an ingress packet by using the packet DSCP value (most
significant 6 bits of 8-bit service-type field). For a non-IP packet, the packet
CoS is used if the packet is tagged. For an untagged packet, the default port
CoS value is used.
ip-precedence (Optional) Classify an ingress packet by using the packet IP-precedence value
(most significant 3 bits of 8-bit service-type field). For a non-IP packet, the
packet CoS is used if the packet is tagged. For an untagged packet, the port
default CoS value is used.
Defaults The port is not trusted. If no keyword is specified when the command is entered, the default is dscp.
Usage Guidelines Packets entering a quality of service (QoS) domain are classified at the edge of the domain. When the
packets are classified at the edge, the switch port within the QoS domain can be configured to one of the
trusted states because there is no need to classify the packets at every switch within the domain. Use this
command to specify whether the port is trusted and which fields of the packet to use to classify traffic.
When a port is configured with trust DSCP or trust IP precedence and the incoming packet is a non-IP
packet, the CoS-to-DSCP map is used to derive the corresponding DSCP value from the CoS value. The
CoS can be the packet CoS for trunk ports or the port default CoS for nontrunk ports.
If the DSCP is trusted, the DSCP field of the IP packet is not modified. However, it is still possible that
the CoS value of the packet is modified (according to DSCP-to-CoS map).
If the CoS is trusted, the CoS field of the packet is not modified, but the DSCP can be modified
(according to CoS-to-DSCP map) if the packet is an IP packet.
The trusted boundary feature prevents security problems if users disconnect their PCs from networked
Cisco IP phones and connect them to the switch port to take advantage of trusted CoS settings. You must
globally enable the Cisco Discovery Protocol (CDP) on the switch and on the interface connected to the
IP phone. If the phone is not detected, trusted boundary disables the trusted setting on the switch port
and prevents misuse of a high-priority queue. If you configure the trust setting for DSCP or IP
precedence, the DSCP or IP precedence values in the incoming packets are trusted. If you configure the
mls qos cos override interface configuration command on the switch port connected to the IP phone,
the switch overrides the CoS of the incoming voice and data packets and assigns the default CoS value
to them.
For an inter-QoS domain boundary, you can configure the port to the DSCP-trusted state and apply the
DSCP-to-DSCP-mutation map if the DSCP values are different between the QoS domains.
Classification using a port trust state (for example, mls qos trust [cos | dscp | ip-precedence] and a
policy map (for example, service-policy input policy-map-name) are mutually exclusive. The last one
configured overwrites the previous configuration.
Examples This example shows how to configure a port on stack member 2 to trust the IP precedence field in the
incoming packet:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos trust ip-precedence
This example shows how to specify that the Cisco IP phone connected on a port on stack member 2 is a
trusted device:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos trust device cisco-phone
You can verify your settings by entering the show mls qos interface privileged EXEC command.
monitor session
Use the monitor session global configuration command on the switch stack or on a standalone switch
to start a new Switched Port Analyzer (SPAN) session or Remote SPAN (RSPAN) source or destination
session, to enable ingress traffic on the destination port for a network security device (such as a Cisco
IDS Sensor Appliance), to add or delete interfaces or VLANs to or from an existing SPAN or RSPAN
session, and to limit (filter) SPAN source traffic to specific VLANs. Use the no form of this command
to remove the SPAN or RSPAN session or to remove source or destination interfaces or filters from the
SPAN or RSPAN session. For destination interfaces, the encapsulation replicate keywords are ignored
with the no form of the command.
Syntax Description. session_number Specify the session number identified with the SPAN or RSPAN session.
The range is 1 to 66.
destination Specify the SPAN or RSPAN destination. A destination must be a physical
port.
interface interface-id Specify the destination or source interface for a SPAN or RSPAN session.
Valid interfaces are physical ports (including type, stack member, module,
and port number). For source interface, port channel is also a valid
interface type, and the valid range is 1 to 12.
encapsulation replicate (Optional) Specify that the destination interface replicates the source
interface encapsulation method. If not selected, the default is to send
packets in native form (untagged).
Note Entering these keywords is valid only for local SPAN; for RSPAN,
the RSPAN VLAN ID overwrites the original VLAN ID; therefore
packets are always sent untagged.
ingress (Optional) Enable ingress traffic forwarding.
dot1q vlan vlan-id Specify ingress forwarding using 802.1Q encapsulation with the specified
VLAN as the default VLAN for ingress traffic.
isl Specify ingress forwarding using ISL encapsulation.
untagged vlan vlan-id Specify ingress forwarding using untagged encapsulation with the specified
VLAN as the default VLAN for ingress traffic
vlan vlan-id When used with only the ingress keyword, set default VLAN for ingress
traffic.
remote vlan vlan-id Specify the remote VLAN for an RSPAN source or destination session. The
range is 2 to 1001 and 1006 to 4094.
Note The RSPAN VLAN cannot be VLAN 1 (the default VLAN) or
VLAN IDs 1002 to 1005 (reserved for Token Ring and FDDI
VLANs).
, (Optional) Specify a series of interfaces or VLANs, or separate a range of
interfaces or VLANs from a previous range. Enter a space before and after
the comma.
- (Optional) Specify a range of interfaces or VLANs. Enter a space before
and after the hyphen.
filter vlan vlan-id Specify a list of VLANs as filters on trunk source ports to limit SPAN
source traffic to specific VLANs. The vlan-id range is 1 to 4094.
source Specify the SPAN or RSPAN source. A source can be a physical port, a port
channel, or a VLAN.
both, rx, tx (Optional) Specify the traffic direction to monitor. If you do not specify a
traffic direction, the source interface sends both transmitted and received
traffic.
source vlan vlan-id Specify the SPAN source interface as a VLAN ID. The range is 1 to 4094.
all, local, remote Specify all, local, or remote with the no monitor session command to clear
all SPAN and RSPAN, all local SPAN, or all RSPAN sessions.
Usage Guidelines Traffic that enters or leaves source ports or source VLANs can be monitored by using SPAN or RSPAN.
Traffic routed to source ports or source VLANs cannot be monitored.
You can set a combined maximum of two local SPAN sessions and RSPAN source sessions. You can
have a total of 66 SPAN and RSPAN sessions on a switch or switch stack.
You can have a maximum of 64 destination ports on a switch stack.
Each session can include multiple ingress or egress source ports or VLANs, but you cannot combine
source ports and source VLANs in a single session. Each session can include multiple destination ports.
When you use VLAN-based SPAN (VSPAN) to analyze network traffic in a VLAN or set of VLANs, all
active ports in the source VLANs become source ports for the SPAN or RSPAN session. Trunk ports are
included as source ports for VSPAN, and only packets with the monitored VLAN ID are sent to the
destination port.
You can monitor traffic on a single port or VLAN or on a series or range of ports or VLANs. You select
a series or range of interfaces or VLANs by using the [, | -] options.
If you specify a series of VLANs or interfaces, you must enter a space before and after the comma. If
you specify a range of VLANs or interfaces, you must enter a space before and after the hyphen (-).
EtherChannel ports cannot be configured as SPAN or RSPAN destination ports. A physical port that is
a member of an EtherChannel group can be used as a destination port, but it cannot participate in the
EtherChannel group while it is as a SPAN destination.
You can monitor individual ports while they participate in an EtherChannel, or you can monitor the
entire EtherChannel bundle by specifying the port-channel number as the RSPAN source interface.
A port used as a destination port cannot be a SPAN or RSPAN source, nor can a port be a destination
port for more than one session at a time.
You can enable 802.1X on a port that is a SPAN or RSPAN destination port; however, 802.1X is disabled
until the port is removed as a SPAN destination. (If 802.1X is not available on the port, the switch returns
an error message.) You can enable 802.1X on a SPAN or RSPAN source port.
VLAN filtering refers to analyzing network traffic on a selected set of VLANs on trunk source ports. By
default, all VLANs are monitored on trunk source ports. You can use the monitor session
session_number filter vlan vlan-id command to limit SPAN traffic on trunk source ports to only the
specified VLANs.
VLAN monitoring and VLAN filtering are mutually exclusive. If a VLAN is a source, VLAN filtering
cannot be enabled. If VLAN filtering is configured, a VLAN cannot become a source.
If ingress traffic forwarding is enabled for a network security device, the destination port forwards traffic
at Layer 2.
Destination ports can be configured to act in these ways:
• When you enter monitor session session_number destination interface interface-id with no other
keywords, egress encapsulation is untagged, and ingress forwarding is not enabled.
• When you enter monitor session session_number destination interface interface-id encapsulation
replicate with no other keywords, egress encapsulation replicates the source interface
encapsulation; ingress forwarding is not enabled. (This applies to local SPAN only; RSPAN does
not support encapsulation replication.)
• When you enter monitor session session_number destination interface interface-id encapsulation
replicate ingress, egress encapsulation replicates the source interface encapsulation; ingress
encapsulation depends on the keywords that follow—dot1q, isl, or untagged. (This applies to local
SPAN only; RSPAN does not support encapsulation replication.)
• When you enter monitor session session_number destination interface interface-id ingress, egress
encapsulation is untagged; ingress encapsulation depends on the keywords that follow—dot1q, isl,
or untagged.
Examples This example shows how to create a local SPAN session 1 to monitor both sent and received traffic on
source interface Gigabit Ethernet 1 on stack member 1 to destination interface Gigabit Ethernet 8 on
stack member 2:
Switch(config)# monitor session 1 source interface gigabitethernet1/0/1 both
Switch(config)# monitor session 1 destination interface gigabitethernet2/0/8
This example shows how to delete a destination port from an existing local SPAN session:
Switch(config)# no monitor session 2 destination gigabitethernet1/0/4
This example shows how to limit SPAN traffic in an existing session only to specific VLANs:
Switch(config)# monitor session 1 filter vlan 100 - 304
This example shows how to configure RSPAN source session 1 to monitor multiple source interfaces and
to configure the destination RSPAN VLAN 900.
Switch(config)# monitor session 1 source interface gigabitethernet1/0/10 ,
gigabitethernet1/0/12
Switch(config)# monitor session 1 source interface gigabitethernet2/0/2 rx
Switch(config)# monitor session 1 source interface port-channel 2 tx
Switch(config)# monitor session 1 destination remote vlan 900
Switch(config)# end
This example shows how to configure an RSPAN destination session 10 in the switch receiving the
monitored traffic.
Switch(config)# monitor session 10 source remote vlan 900
Switch(config)# monitor session 10 destination interface gigabitethernet1/0/10
This example shows how to configure the destination port for ingress traffic on VLAN 5 by using a
security device that supports 802.1Q encapsulation. Egress traffic replicates the source; ingress traffic
uses 802.1Q encapsulation.
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/5 encapsulation
replicate ingress dot1q vlan 5
This example shows how to configure the destination port for ingress traffic on VLAN 5 by using a
security device that does not support encapsulation. Egress traffic replicates the source encapsulation;
ingress traffic is untagged.
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/5 encapsulation
replicate ingress untagged vlan 5
You can verify your settings by entering the show monitor privileged EXEC command. You can view
SPAN and RSPAN configuration on the switch by entering the show running-config privileged EXEC
command. SPAN information appears near the end of the output.
mvr [group ip-address [count] | mode [compatible | dynamic] | querytime value | vlan vlan-id]
no mvr [group ip-address | mode [compatible | dynamic] | querytime value | vlan vlan-id]
Syntax Description group ip-address Statically configure an MVR group IP multicast address on the switch.
Use the no form of this command to remove a statically configured IP
multicast address or contiguous addresses or, when no IP address is entered,
to remove all statically configured MVR IP multicast addresses.
count (Optional) Configure multiple contiguous MVR group addresses. The range
is 1 to 256; the default is 1.
mode (Optional) Specify the MVR mode of operation.
The default is compatible mode.
compatible Set MVR mode to provide compatibility with Catalyst 2900 XL and
3500 XL switches. This mode does not allow dynamic membership joins on
source ports.
dynamic Set MVR mode to allow dynamic MVR membership on source ports.
querytime value (Optional) Set the maximum time to wait for IGMP report memberships on
a receiver port. This time applies only to receiver-port leave processing.
When an IGMP query is sent from a receiver port, the switch waits for the
default or configured MVR querytime for an IGMP group membership
report before removing the port from multicast group membership.
The value is the response time in units of tenths of a second. The range is 1
to 100; the default is 5 tenths or one-half second.
Use the no form of the command to return to the default setting.
vlan vlan-id (Optional) Specify the VLAN on which MVR multicast data is expected to
be received. This is also the VLAN to which all the source ports belong. The
range is 1 to 4094; the default is VLAN 1.
Usage Guidelines A maximum of 256 MVR multicast groups can be configured on a switch.
Use the mvr group command to statically set up all the IP multicast addresses that will take part in
MVR. Any multicast data sent to a configured multicast address is sent to all the source ports on the
switch and to all receiver ports that have registered to receive data on that IP multicast address.
MVR supports aliased IP multicast addresses on the switch. However, if the switch is interoperating with
Catalyst 3550 or Catalyst 3500 XL switches, you should not configure IP addresses that alias between
themselves or with the reserved IP multicast addresses (in the range 224.0.0.xxx).
The mvr querytime command applies only to receiver ports.
If the switch MVR is interoperating with Catalyst 2900 XL or Catalyst 3500 XL switches, set the
multicast mode to compatible.
When operating in compatible mode, MVR does not support IGMP dynamic joins on MVR source ports.
MVR can coexist with IGMP snooping on a switch.
Multicast routing and MVR cannot coexist on a switch. If you enable multicast routing and a multicast
routing protocol while MVR is enabled, MVR is disabled and a warning message is displayed. If you try
to enable MVR while multicast routing and a multicast routing protocol are enabled, the operation to
enable MVR is cancelled with an Error message.
Use the show mvr privileged EXEC command to display the current setting for maximum multicast
groups.
This example shows how to configure 228.1.23.4 as an IP multicast address:
Switch(config)# mvr group 228.1.23.4
This example shows how to configure ten contiguous IP multicast groups with multicast addresses from
228.1.23.1 to 228.1.23.10:
Switch(config)# mvr group 228.1.23.1 10
This example shows how to delete the previously configured ten IP multicast addresses:
Switch(config)# no mvr group 228.1.23.1 10
This example shows how to delete all previously configured IP multicast addresses:
Switch(config)# no mvr group
Use the show mvr members privileged EXEC command to display the IP multicast group addresses
configured on the switch.
This example shows how to set the maximum query response time as one second (10 tenths):
Switch(config)# mvr querytime 10
This example shows how to return the maximum query response time to the default setting of one-half
second:
Switch(config)# no mvr querytime
You can verify your settings by entering the show mvr privileged EXEC command.
Syntax Description immediate (Optional) Enable the Immediate Leave feature of MVR on a port. Use
the no mvr immediate command to disable the feature.
type (Optional) Configure the port as an MVR receiver port or source port.
The default port type is neither an MVR source nor receiver port. The no
mvr type command resets the port as neither a source or receiver port.
receiver Configure the port as a subscriber port that can only receive multicast
data. Receiver ports cannot belong to the multicast VLAN.
source Configure the port as an uplink port that can send and receive multicast
data for the configured multicast groups. All source ports on a switch
belong to a single multicast VLAN.
vlan vlan-id group (Optional) Add the port as a static member of the multicast group with
the specified VLAN ID.
The no mvr vlan vlan-id group command removes a port on a VLAN
from membership in an IP multicast address group.
ip-address (Optional) Statically configure the specified MVR IP multicast group
address for the specified multicast VLAN ID. This is the IP address of
the multicast group that the port is joining.
Usage Guidelines Configure a port as a source port if that port should be able to both send and receive multicast data bound
for the configured multicast groups. Multicast data is received on all ports configured as source ports.
Receiver ports cannot be trunk ports. Receiver ports on a switch can be in different VLANs, but should
not belong to the multicast VLAN.
A port that is not taking part in MVR should not be configured as an MVR receiver port or source port.
A non-MVR port is a normal switch port, able to send and receive multicast data with normal switch
behavior.
When Immediate Leave is enabled, a receiver port leaves a multicast group more quickly. Without
Immediate Leave, when the switch receives an IGMP leave message from a group on a receiver port, it
sends out an IGMP MAC-based query on that port and waits for IGMP group membership reports. If no
reports are received in a configured time period, the receiver port is removed from multicast group
membership. With Immediate Leave, an IGMP MAC-based query is not sent from the receiver port on
which the IGMP leave was received. As soon as the leave message is received, the receiver port is
removed from multicast group membership, which speeds up leave latency.
The Immediate Leave feature should be enabled only on receiver ports to which a single receiver device
is connected.
The mvr vlan group command statically configures ports to receive multicast traffic sent to the IP
multicast address. A port statically configured as a member of group remains a member of the group
until statically removed. In compatible mode, this command applies only to receiver ports; in dynamic
mode, it can also apply to source ports. Receiver ports can also dynamically join multicast groups by
using IGMP join messages.
When operating in compatible mode, MVR does not support IGMP dynamic joins on MVR source ports.
Examples This example shows how to configure Gigabit Ethernet port 0/1 on stack member 1 as an MVR receiver
port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr type receiver
This example shows how to configure Gigabit Ethernet port 0/2 on stack member 1 as an MVR source
port:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr type source
This example shows how to remove port 0/1 on stack member 1 as an MVR port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if))# no mvr
This example shows how to display configured receiver ports and source ports.
Switch# show mvr interface
Port Type Status Immediate Leave
---- ---- ------- ---------------
Gi1/0/1 SOURCE ACTIVE/UP DISABLED
Gi1/0/2 RECEIVER ACTIVE/DOWN DISABLED
Gi1/0/5 RECEIVER ACTIVE/UP ENABLED
This example shows how to enable Immediate Leave on Gigabit Ethernet port 1/0/1:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr immediate
This example shows how to disable Immediate Leave on Gigabit Ethernet port 0/1on stack member 1:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr immediate
This example shows how to add Gigabit Ethernet port 1/0/2 on VLAN 1 as a static member of IP
multicast group 228.1.23.4:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr vlan1 group 230.1.23.4
This example shows how to remove this port from all IP multicast groups:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr vlan5 group
This example shows the result if Gigabit Ethernet port 0/2 on stack member 1 is not a receiver port:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr vlan 1 group 230.1.23.4
Interface Gi1/0/2 not configured as a receiver interface
You can verify your settings by entering the show mvr members privileged EXEC command.
pagp learn-method
Use the pagp learn-method interface configuration command on the switch stack or on a standalone
switch to learn the source address of incoming packets received from an EtherChannel port. Use the no
form of this command to return to the default setting.
no pagp learn-method
Syntax Description aggregation-port Specify address learning on the logical port-channel. The switch sends
packets to the source using any of the interfaces in the EtherChannel. This
setting is the default. With aggregate-port learning, it is not important on
which physical port the packet arrives.
physical-port Specify address learning on the physical port within the EtherChannel. The
switch sends packets to the source using the same interface in the
EtherChannel from which it learned the source address. The other end of the
channel uses the same port in the channel for a particular destination MAC or
IP address.
Usage Guidelines The learn method must be configured the same at both ends of the link.
Note The Catalyst 3750 switch supports address learning only on aggregate ports even though the
physical-port keyword is provided in the command-line interface (CLI). The pagp learn-method and
the pagp port-priority interface configuration commands have no effect on the switch hardware, but
they are required for PAgP interoperability with devices that only support address learning by physical
ports, such as the Catalyst 1900 switch.
When the link partner to the Catalyst 3750 switch is a physical learner, we recommend that you configure
the switch as a physical-port learner by using the pagp learn-method physical-port interface
configuration command and to set the load-distribution method based on the source MAC address by
using the port-channel load-balance src-mac global configuration command. Use the pagp
learn-method interface configuration command only in this situation.
Examples This example shows how to set the learning method to learn the address on the physical port within the
EtherChannel:
Switch(config-if)# pagp learn-method physical-port
This example shows how to set the learning method to learn the address on the port-channel within the
EtherChannel:
Switch(config-if)# pagp learn-method aggregation-port
You can verify your settings by entering the show running-config privileged EXEC command or the
show pagp channel-group-number internal privileged EXEC command.
pagp port-priority
Use the pagp port-priority interface configuration command on the switch stack or on a standalone
switch to select an interface over which all Port Aggregation Protocol (PAgP) traffic through the
EtherChannel is sent. If all unused interfaces in the EtherChannel are in hot-standby mode, they can be
placed into operation if the currently selected interface and link fails. Use the no form of this command
to return to the default setting.
no pagp port-priority
Usage Guidelines The physical port with the highest priority that is operational and has membership in the same
EtherChannel is the one selected for PAgP transmission.
Note The Catalyst 3750 switch supports address learning only on aggregate ports even though the
physical-port keyword is provided in the command-line interface (CLI). The pagp learn-method and
the pagp port-priority interface configuration commands have no effect on the switch hardware, but
they are required for PAgP interoperability with devices that only support address learning by physical
ports, such as the Catalyst 1900 switch.
When the link partner to the Catalyst 3750 switch is a physical learner, we recommend that you configure
the switch as a physical-port learner by using the pagp learn-method physical-port interface
configuration command and to set the load-distribution method based on the source MAC address by
using the port-channel load-balance src-mac global configuration command. Use the pagp
learn-method interface configuration command only in this situation.
Examples This example shows how to set the port priority to 200:
Switch(config-if)# pagp port-priority 200
You can verify your setting by entering the show running-config privileged EXEC command or the
show pagp channel-group-number internal privileged EXEC command.
permit
Use the permit MAC-access list configuration command on the switch stack or on a standalone switch
to allow non-IP traffic to be forwarded if the conditions are matched. Use the no form of this command
to remove a permit condition from the extended MAC access list.
{permit | deny} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr |
dst-MAC-addr mask} [type mask | cos cos | aarp | amber | 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 {permit | deny} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr |
dst-MAC-addr mask} [type mask | cos cos | aarp | amber | 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]
Note Though visible in the command-line help strings, appletalk is not supported as a matching condition.
Syntax Description any Keyword to specify to deny any source or destination MAC address.
host src-MAC-addr | Define a host MAC address and optional subnet mask. If the source
src-MAC-addr mask address for a packet matches the defined address, non-IP traffic from that
address is denied.
host dst-MAC-addr | Define a destination MAC address and optional subnet mask. If the
dst-MAC-addr mask destination address for a packet matches the defined address, non-IP
traffic to that address is denied.
type mask (Optional) Use the Ethertype number of a packet with Ethernet II or
SNAP encapsulation to identify the protocol of the packet.
• type is 0 to 65535, specified in hexadecimal.
• mask is a mask of don’t care bits applied to the Ethertype before
testing for a match.
aarp (Optional) Select Ethertype AppleTalk Address Resolution Protocol that
maps a data-link address to a network address.
amber (Optional) Select EtherType DEC-Amber.
cos cos (Optional) Select an arbitrary class of service (CoS) number from 0 to 7
to set priority. Filtering on CoS can be performed only in hardware. A
warning message appears if the cos option is configured.
dec-spanning (Optional) Select EtherType Digital Equipment Corporation (DEC)
spanning tree.
decnet-iv (Optional) Select EtherType DECnet Phase IV protocol.
diagnostic (Optional) Select EtherType DEC-Diagnostic.
dsm (Optional) Select EtherType DEC-DSM.
etype-6000 (Optional) Select EtherType 0x6000.
etype-8042 (Optional) Select EtherType 0x8042.
lat (Optional) Select EtherType DEC-LAT.
lavc-sca (Optional) Select EtherType DEC-LAVC-SCA.
lsap lsap-number mask (Optional) Use the LSAP number (0 to 65535) of a packet with 802.2
encapsulation to identify the protocol of the packet.
The mask is a mask of don’t care bits applied to the LSAP number before
testing for a match.
mop-console (Optional) Select EtherType DEC-MOP Remote Console.
mop-dump (Optional) Select EtherType DEC-MOP Dump.
msdos (Optional) Select EtherType DEC-MSDOS.
mumps (Optional) Select EtherType DEC-MUMPS.
netbios (Optional) Select EtherType DEC- Network Basic Input/Output System
(NETBIOS).
vines-echo (Optional) Select EtherType Virtual Integrated Network Service (VINES)
Echo from Banyan Systems.
vines-ip (Optional) Select EtherType VINES IP.
xns-idp (Optional) Select EtherType Xerox Network Systems (XNS) protocol
suite.
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-14.
Defaults This command has no defaults. However; the default action for a MAC-named ACL is to deny.
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 any or host
keywords, you must enter an address mask.
After 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 For more information about MAC named extended access lists, refer to the software configuration guide
for this release.
Examples This example shows how to define the MAC name extended access list to allow NETBIOS traffic from
any source to MAC address 00c0.00a0.03fa. Traffic matching this list is allowed.
Switch(config-ext-macl)# permit any host 00c0.00a0.03fa netbios
This example shows how to remove the permit condition from the MAC name extended access list:
Switch(config-ext-macl)# no permit any 00c0.00a0.03fa 0000.0000.0000 netbios
You can verify your settings by entering the show access-lists privileged EXEC command.
police
Use the police policy-map class configuration command on the switch stack or on a standalone switch
to define a policer for classified traffic. 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 remove an existing policer.
Syntax Description rate-bps Specify the average traffic rate in bits per second (bps). The range is 8000 to
1000000000.
burst-byte Specify the normal burst size in bytes. The range is 8000 to 1000000.
exceed-action drop (Optional) When the specified rate is exceeded, specify that the switch drop
the packet.
exceed-action (Optional) When the specified rate is exceeded, specify that the switch
policed-dscp-transmit change the Differentiated Services Code Point (DSCP) of the packet to that
specified in the policed-DSCP map and then send the packet.
Usage Guidelines The port ASIC supports 256 policers (255 policers plus 1 no policer). The maximum number of policers
supported per port is 64. 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.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode,
use the end command.
Policing uses a token-bucket algorithm. 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 quickly (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, refer to the software configuration guide for this release.
Examples This example shows how to configure a policer that drops packets if traffic exceeds 1 Mbps average rate
with a burst size of 20 KB. The DSCPs of incoming packets are trusted, and there is no packet
modification.
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 45
Switch(config-pmap-c)# police 1000000 20000 exceed-action drop
Switch(config-pmap-c)# exit
This example shows how to configure a policer, which marks down the DSCPs with the values defined
in policed-DSCP map and sends the packet:
Switch(config)# policy-map policy2
Switch(config-pmap)# class class2
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
police aggregate
Use the police aggregate policy-map class configuration command on the switch stack or on a
standalone switch to apply an aggregate policer to multiple classes in 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 remove the specified
policer.
Usage Guidelines The port ASIC supports 256 policers (255 policers plus 1 no policer). The maximum number of policers
supported per port is 64. 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 set aggregate policer parameters by using the mls qos aggregate-policer global configuration
command. You apply an aggregate policer to multiple classes in the same policy map; you cannot use an
aggregate policer across different policy maps.
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 define the aggregate policer parameters and to apply the policer to multiple
classes in a policy map:
Switch(config)# mls qos aggregate-policer agg_policer1 10000 1000000 exceed-action drop
Switch(config)# policy-map policy2
Switch(config-pmap)# class class1
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class3
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police aggregate agg_policer2
Switch(config-pmap-c)# exit
You can verify your settings by entering the show mls qos aggregate-policer privileged EXEC
command.
policy-map
Use the policy-map global configuration command on the switch stack or on a standalone switch to
create or modify a policy map that can be attached to multiple interfaces and to enter policy-map
configuration mode. Use the no form of this command to delete an existing policy map and to return to
global configuration mode.
policy-map policy-map-name
no policy-map policy-map-name
Usage Guidelines After entering the policy-map command, you enter policy-map configuration mode, and these
configuration commands are available:
• class: defines the classification match criteria for the specified class map. For more information, see
the “class” section on page 2-33.
• description: describes the policy map (up to 200 characters).
• exit: exits policy-map configuration mode and returns you to global configuration mode.
• no: removes a previously defined policy map.
• rename: renames the current policy map.
To return to global configuration mode, use the exit command. To return to privileged EXEC mode, use
the end command.
Before configuring policies for classes whose match criteria are defined in a class map, use the
policy-map command to specify the name of the policy map to be created, added to, or modified.
Entering the policy-map command also enables the policy-map configuration mode in which you can
configure or modify the class policies for that policy map.
You can configure class policies in a policy map only if the classes have match criteria defined for them.
To configure the match criteria for a class, use the class-map global configuration and match class-map
configuration commands. You define packet classification on a physical-port basis.
Only one policy map per ingress interface is supported. You can apply the same policy map to multiple
interfaces.
Examples This example shows how to create a policy map called policy1. When attached to the ingress direction,
it matches all the incoming traffic defined in class1, sets the IP DSCP to 10, and polices the traffic at an
average rate of 1 Mbps and bursts at 20 KB. Traffic exceeding the profile is marked down to a DSCP
value obtained from the policed-DSCP map and then sent.
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
This example shows how to configure multiple classes in a policy map called policymap2:
Switch(config)# policy-map policymap2
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police 100000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police 100000 20000 exceed-action drop
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class3
Switch(config-pmap-c)# set ip dscp 0 (no policer)
Switch(config-pmap-c)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
port-channel load-balance
Use the port-channel load-balance global configuration command on the switch stack or on a
standalone switch to set the load-distribution method among the ports in the EtherChannel. Use the no
form of this command to return to the default setting.
no port-channel load-balance
Syntax Description dst-ip Load distribution is based on the destination host IP address.
dst-mac Load distribution is based on the destination host MAC address. Packets to the same
destination are sent on the same port, but packets to different destinations are sent on
different ports in the channel.
src-dst-ip Load distribution is based on the source and destination host IP address.
src-dst-mac Load distribution is based on the source and destination host MAC address.
src-ip Load distribution is based on the source host IP address.
src-mac Load distribution is based on the source MAC address. Packets from different hosts use
different ports in the channel, but packets from the same host use the same port.
Usage Guidelines For information about when to use these forwarding methods, refer to the “Configuring EtherChannels”
chapter in the software guide for this release.
Examples This example shows how to set the load-distribution method to dst-mac:
Switch(config)# port-channel load-balance dst-mac
You can verify your setting by entering the show running-config privileged EXEC command or the
show etherchannel load-balance privileged EXEC command.
queue-set
Use the queue-set interface configuration command on the switch stack or on a standalone switch to map
a port to a queue-set. Use the no form of this command to return to the default setting.
queue-set qset-id
no queue-set qset-id
Syntax Description qset-id ID of the queue-set. Each port belongs to a queue-set, which defines all the
characteristics of the four egress queues per port. The range is 1 to 2.
Examples This example shows how to map Fast Ethernet port 0/1 on stack member 2 to queue-set 2:
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# queue-set 2
You can verify your settings by entering the show mls qos interface [interface-id] buffers privileged
EXEC command.
rcommand
Use the rcommand user EXEC command on the switch stack or on the cluster command switch to start a
Telnet session and to execute commands on a cluster member switch from the cluster command switch
or the switch stack. To end the session, enter the exit command.
Syntax Description n Provide the number that identifies a cluster member. The range is 0 to 15.
commander Provide access to the cluster command switch from a cluster member
switch.
mac-address hw-addr MAC address of the cluster member switch.
Usage Guidelines This command is available only on the cluster command switch stack or cluster command switch.
If the switch is the cluster command switch but the cluster member switch n does not exist, an error
message appears. To obtain the switch number, enter the show cluster members privileged EXEC
command on the cluster command switch.
You can use this command to access a cluster member switch from the cluster command-switch prompt
or to access a cluster command switch from the member-switch prompt.
For Catalyst 2900 XL, 3500 XL, 2950, 2970, 3550, and 3750 switches, the Telnet session accesses the
member-switch command-line interface (CLI) at the same privilege level as on the cluster command
switch. For example, if you execute this command at user level on the cluster command switch, the
cluster member switch is accessed at user level. If you use this command on the cluster command switch
at privileged level, the command accesses the remote device at privileged level. If you use an
intermediate enable-level lower than privileged, access to the cluster member switch is at user level.
For Catalyst 1900 and 2820 switches running standard edition software, the Telnet session accesses the
menu console (the menu-driven interface) if the cluster command switch is at privilege level 15. If the
cluster command switch is at privilege level 1, you are prompted for the password before being able to
access the menu console. Cluster command switch privilege levels map to the cluster member switches
running standard edition software as follows:
• If the cluster command switch privilege level is from 1 to 14, the cluster member switch is accessed
at privilege level 1.
• If the cluster command switch privilege level is 15, the cluster member switch is accessed at
privilege level 15.
The Catalyst 1900 and 2820 CLI is available only on switches running Enterprise Edition Software.
This command will not work if the vty lines of the cluster command switch have access-class
configurations.
You are not prompted for a password because the cluster member switches inherited the password of the
cluster command switch when they joined the cluster.
Examples This example shows how to start a session with member 3. All subsequent commands are directed to
member 3 until you enter the exit command or close the session.
Switch# rcommand 3
Switch-3# show version
Cisco Internet Operating System Software ...
...
Switch-3# exit
Switch#
reload
Use the reload privileged EXEC command to reset the stack member and applies a configuration change
into effect.
Defaults Immediately resets the stack member and puts a configuration change into effect.
remote command
Use the remote command privileged EXEC command to monitor all or specified stack members.
Usage Guidelines The commands (such as debug, show, or clear) you use in the LINE command-to-execute string apply
to a specific stack member or to the switch stack.
Examples This example shows how to execute the undebug command on the switch stack:
Switch(config)# remote command all undebug all
Switch :1 :
------------
All possible debugging has been turned off
Switch :5 :
------------
All possible debugging has been turned off
Switch :9 :
------------
All possible debugging has been turned off
This example shows how to execute the debug udld event command on stack member 5:
Switch(config)# remote command 5 undebug all
Switch :5 :
------------
UDLD events debugging is on
remote-span
Use the remote-span VLAN configuration command on the switch stack or on a standalone switch to
configure a VLAN as a Remote Switched Port Analyzer (RSPAN) VLAN. Use the no form of this
command to remove the RSPAN designation from the VLAN.
remote-span
no remote-span
Usage Guidelines You can configure RSPAN VLANs only in config-VLAN mode (entered by using the vlan global
configuration command), not the VLAN configuration mode entered by using the vlan database
privileged EXEC command.
If VTP is enabled, the RSPAN feature is propagated by VLAN Trunking Protocol (VTP) for VLAN-IDs
that are lower than 1005. If the RSPAN VLAN ID is in the extended range, you must manually configure
intermediate switches (those in the RSPAN VLAN between the source switch and the destination
switch).
Before you configure the RSPAN remote-span command, use the vlan (global configuration) command
to create the VLAN.
The RSPAN VLAN has these characteristics:
• No MAC address learning occurs on it.
• RSPAN VLAN traffic flows only on trunk ports.
• Spanning Tree Protocol (STP) can run in the RSPAN VLAN, but it does not run on RSPAN
destination ports.
When an existing VLAN is configured as an RSPAN VLAN, the VLAN is first deleted and then
recreated as an RSPAN VLAN. Any access ports are made inactive until the RSPAN feature is disabled.
This example shows how to remove the RSPAN feature from a VLAN.
Switch(config)# vlan 901
Switch(config-vlan)# no remote-span
You can verify your settings by entering the show vlan remote-span user EXEC command.
Syntax Description index Remote Network Monitoring (RMON) collection control index. The range is
1 to 65535.
owner name (Optional) Owner of the RMON collection.
Usage Guidelines The RMON statistics collection command is based on hardware counters.
Examples This example shows how to collect RMON statistics for the owner root on Gigabit Ethernet interface 0/1
of stack member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# rmon collection stats 2 owner root
You can verify your setting by entering the show rmon statistics privileged EXEC command.
sdm prefer
Use the sdm prefer global configuration command on the switch stack or on a standalone switch to
configure the template used in Switch Database Management (SDM) resource allocation. You can use a
template to allocate system resources to best support the features being used in your application. Use a
template to provide maximum system utilization for unicast routing or for VLAN configuration or to
change an aggregator template (Catalyst 3750-12S only) to a desktop template. Use the no form of this
command to return to the default template.
no sdm prefer
Syntax Description default Set the switch to use the default template (Catalyst 3750-12S only). This keyword
is not available on switches that do not allow the aggregator template (desktop
switches). On these switches, enter the no sdm prefer command to set the default
template.
routing Provide maximum system utilization for unicast routing. You would typically use
this template for a router or aggregator in the middle of a network.
vlan Provide maximum system utilization for VLANs. This template maximizes system
resources for use as a Layer 2 switch with no routing.
desktop Use only on a Catalyst 3750-12S switch (where aggregator templates are the
default), to select the default, routing, or VLAN desktop template.
Usage Guidelines You must reload the switch for the configuration to take effect. If you enter the show sdm prefer
command before you enter the reload privileged EXEC command, the show sdm prefer command shows
the template currently in use and the template that will become active after a reload.
Desktop switches support only desktop templates; an aggregator switch (Catalyst 3750-12S) supports
both desktop and aggregator templates. On an aggregator switch, if you do not enter the desktop
keyword, the aggregator templates are selected.
All stack members use the same SDM desktop or aggregator template, stored on the stack master. When
a new switch member is added to a stack, as with the switch configuration file and VLAN database file,
the SDM configuration that is stored on the stack master overrides the template configured on an
individual switch.
If a stack member cannot support the template that is running on the master switch, the switch goes into
SDM mismatch mode, the master switch does not attempt to change the SDM template, and the switch
cannot be a functioning member of the stack.
• If the master switch is a Catalyst 3750-12S, and you change the template from an aggregator
template to a desktop template and reload the switch, the entire stack operates with the selected
desktop template. This could cause configuration losses if the number of ternary content addressable
memory (TCAM) entries exceeds the desktop template sizes.
• If you change the template on a Catalyst 3750-12S master from a desktop template to an aggregator
template and reload the switch, any desktop switches that were part of the stack go into SDM
mismatch mode.
• If you add a Catalyst 3750-12S switch that is running the aggregator template to a stack that has a
desktop switch as the stack master, the stack operates with the desktop template selected on the stack
master. This could cause configuration losses on the Catalyst 3750-12S stack member if the number
of TCAM entries on it exceeds desktop template sizes.
Note For more information about stacking, refer to the “Managing Switch Stacks” chapter in the software
configuration guide.
Use the sdm prefer vlan [desktop] global configuration command only on switches intended for Layer
2 switching with no routing. When you use the VLAN template, no system resources are reserved for
routing entries and any routing is done through software. This overloads the central processing unit
(CPU) and severely degrades routing performance.
Do not use the routing template if you do not have routing enabled on your switch. Entering the sdm
prefer routing [desktop] global configuration command prevents other features from using the memory
allocated to unicast routing in the routing template.
Table 2-15 lists the approximate number of each resource supported in each of the three templates for a
desktop or aggregator switch. The first eight rows in the tables (unicast MAC addresses through security
ACEs) represent approximate hardware boundaries set when a template is selected. If a section of a
hardware resource is full, all processing overflow is sent to the CPU, seriously impacting switch
performance. The last row is a guideline used to calculate hardware resource consumption related to the
number of Layer 3 VLANs configured.
.
Table 2-15 Approximate Number of Feature Resources Allowed by Each Template
Table 2-15 Approximate Number of Feature Resources Allowed by Each Template (continued)
Examples This example shows how to configure the routing template on a desktop switch:
Switch(config)# sdm prefer routing
Switch(config)# exit
Switch# reload
This example shows how to configure the desktop routing template on an aggregator switch:
Switch(config)# sdm prefer routing desktop
Switch(config)# exit
Switch# reload
This example shows how to change a switch template to the default template. On an aggregator switch,
this is the default aggregator template; on a desktop switch, this is the default desktop template.
Switch(config)# no sdm prefer
Switch(config)# exit
Switch# reload
This example shows how to configure the desktop default template on an aggregator switch:
Switch(config)# sdm prefer default desktop
Switch(config)# exit
Switch# reload
You can verify your settings by entering the show sdm prefer privileged EXEC command.
service password-recovery
Use the service password-recovery global configuration command on the switch stack or on a standalone
switch to enable the password-recovery mechanism (the default). This mechanism allows a user with
physical access to the switch to hold down the Mode button and interrupt the boot process while the
switch is powering up and to assign a new password. Use the no form of this command to disable part
of the password-recovery functionality. When the password-recovery mechanism is disabled,
interrupting the boot process is allowed only if the user agrees to set the system back to the default
configuration.
service password-recovery
no service password-recovery
Usage Guidelines As a system administrator, you can use the no service password-recovery command to disable some of
the functionality of the password recovery feature by allowing an end user to reset a password only by
agreeing to return to the default configuration.
To use the password-recovery procedure, a user with physical access to the switch holds down the Mode
button while the unit powers up and for a second or two after the LED above port 1X goes off. When the
button is released, the system continues with initialization. If the password-recovery mechanism is disabled,
this message is displayed:
The password-recovery mechanism has been triggered, but
is currently disabled. Access to the boot loader prompt
through the password-recovery mechanism is disallowed at
this point. However, if you agree to let the system be
reset back to the default system configuration, access
to the boot loader prompt can still be allowed.
Would you like to reset the system back to the default configuration (y/n)?
If the user chooses not to reset the system back to the default configuration, the normal boot process
continues, as if the Mode button had not been pressed. If you choose to reset the system back to the default
configuration, the configuration file in flash memory is deleted and the VLAN database file, flash:vlan.dat
(if present) is deleted.
Note If you use the no service password-recovery command to control end user access to passwords, we
recommend that you save a copy of the config file in a location away from the switch in case the end
user uses the password recovery procedure and sets the system back to defaults. Do not keep a backup
copy of the config file on the switch.
If the switch is operating in VTP transparent mode, we recommend that you also save a copy of the
vlan.dat file in a location away from the switch.
When you enter the service password-recovery or no service password-recovery command on the
stack master, it is propagated throughout the stack and applied to all switches in the stack.
You can verify if password recovery is enabled or disabled by entering the show version privileged
EXEC command.
Examples This example shows how to disable password recovery on a switch or switch stack so that a user can
only reset a password by agreeing to return to the default configuration.
Switch(config)# no service-password recovery
Switch(config)# exit
service-policy
Use the service-policy interface configuration command on the switch stack or on a standalone switch
to apply a policy map defined by the policy-map command to the input of a particular interface. Use the
no form of this command to remove the policy map and interface association.
Syntax Description input policy-map-name Apply the specified policy-map to the input of an interface.
Note Though visible in the command-line help strings, the history keyword is not supported, and you should
ignore the statistics it gathers. The output keyword is also not supported.
Usage Guidelines Only one policy map per ingress interface is supported.
Classification using a port trust state (for example, mls qos trust [cos | dscp | ip-precedence] and a
policy map (for example, service-policy input policy-map-name) are mutually exclusive. The last one
configured overwrites the previous configuration.
Examples This example shows how to apply plcmap1 to an ingress interface on stack member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# service-policy input plcmap1
This example shows how to detach plcmap2 from an interface on stack member 2:
Switch(config)# interface gigabitethernet2/0/2
Switch(config-if)# no service-policy input plcmap2
You can verify your settings by entering the show running-config privileged EXEC command.
session
Use the session privileged EXEC command on the stack master to access a specific stack member.
session stack-member-number
Syntax Description stack-member-number Specify the current stack member number. The stack member number is
in the range from 1 through 9.
Usage Guidelines When you access the stack member, its stack member number is appended to the system prompt.
set
Use the set policy-map class configuration command on the switch stack or on a standalone switch to
classify IP traffic by setting a Differentiated Services Code Point (DSCP) or IP-precedence value in the
packet. Use the no form of this command to remove traffic classification.
Syntax Description ip dscp new-dscp New DSCP value assigned to the classified traffic. The range is
0 to 63. You also can enter a mnemonic name for a commonly-used
value.
ip precedence new-precedence New IP-precedence value assigned to the classified traffic. The
range is 0 to 7. You also can enter a mnemonic name for a
commonly-used value.
Note Though visible in the command-line help strings, the mpls keyword is not supported.
Usage Guidelines The set command is mutually exclusive with the trust policy-map class configuration command within
the same policy map.
For the set ip dscp new-dscp or the set ip precedence new-precedence command, you can enter a
mnemonic name for a commonly-used value. For example, you can enter the set ip dscp af11 command,
which is the as same entering the set ip dscp 10 command. You can enter the set ip precedence critical
command, which is the same as entering the set ip precedence 5 command. For a list of supported
mnemonics, enter the set ip dscp ? or the set ip precedence ? command to see the command-line help
strings.
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 assign DSCP 10 to all FTP traffic without any policers:
Switch(config)# policy-map policy_ftp
Switch(config-pmap)# class ftp_class
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
setup
Use the setup privileged EXEC command to configure the switch with its initial configuration.
setup
Usage Guidelines When you use the setup command, make sure that you have this information:
• IP address and network mask
• Password strategy for your environment
• Whether the switch will be used as the cluster command switch and the cluster name
When you enter the setup command, an interactive dialog, called the System Configuration Dialog,
appears. It guides you through the configuration process and prompts you for information. The values
shown in brackets next to each prompt are the default values last set by using either the setup command
facility or the configure privileged EXEC command.
Help text is provided for each prompt. To access help text, press the question mark (?) key at a prompt.
To return to the privileged EXEC prompt without making changes and without running through the
entire System Configuration Dialog, press Ctrl-C.
When you complete your changes, the setup program shows you the configuration command script that
was created during the setup session. You can save the configuration in nonvolatile RAM (NVRAM),
return to the setup program without saving, or return to the command-line prompt without saving the
configuration.
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
hostname host-name
enable secret 5 $1$LiBw$0Xc1wyT.PXPkuhFwqyhVi0
enable password enable-password
line vty 0 15
password terminal-password
snmp-server community public
!
no ip routing
!
interface GigabitEthernet6/0/1
no ip address
!
interface GigabitEthernet6/0/2
no ip address
!
...
interface GigabitEthernet6/0/12
no ip address
setup express
Use the setup express global configuration command to enable Express Setup mode on the switch stack
or on a standalone switch. Use the no form of this command to disable Express Setup mode.
setup express
no setup express
Usage Guidelines When Express Setup is enabled on a new (unconfigured) switch, pressing the Mode button for 2 seconds
activates Express Setup. You can access the switch through an Ethernet port by using the IP address
10.0.0.1 and then can configure the switch with the web-based Express Setup program or the
command-line interface (CLI)-based setup program.
When you press the Mode button for 2 seconds on a configured switch, the mode LEDs start flashing. If
you press the Mode button for a total of 10 seconds, the switch configuration is deleted, and the switch
reboots. The switch can then be configured like a new switch, either through the web-based Express
Setup program or the CLI-based setup program.
Note As soon as you make any change to the switch configuration (including entering no at the beginning of
the CLI-based setup program), configuration by Express Setup is no longer available. You can only run
Express Setup again by pressing the Mode button for 10 seconds. This deletes the switch configuration
and reboots the switch.
If Express Setup is active on the switch, entering the write memory or copy running-configuration
startup-configuration privileged EXEC commands deactivates Express Setup. The IP address 10.0.0.1
is no longer valid on the switch, and your connection using this IP address ends.
The primary purpose of the no setup express command is to prevent someone from deleting the switch
configuration by pressing the Mode button for 10 seconds.
You can verify that Express Setup mode is enabled by pressing the Mode button:
• On an unconfigured switch, the mode LEDs turn solid green after 3 seconds.
• On a configured switch, the mode LEDs begin flashing after 2 seconds and turn solid green after 10
seconds.
Caution If you hold the Mode button down for a total of 10 seconds, the configuration is deleted, and the switch
reboots.
You can verify that Express Setup mode is disabled by pressing the Mode button. The mode LEDs do
not turn solid green or begin flashing green if Express Setup mode is not enabled on the switch.
show access-lists
Use the show access-lists privileged EXEC command to display access control lists (ACLs) configured
on the switch.
show access-lists [name | number | hardware counters | ipc] [ | {begin | exclude | include}
expression]
Note Though visible in the command-line help strings, the rate-limit keywords are not supported.
Usage Guidelines The switch supports only IP standard and extended access lists. Therefore, the allowed numbers are only
1 to 199 and 1300 to 2699.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
This is an example of output from the show access-lists hardware counters command:
Switch# show access-lists hardware counters
L2 ACL INPUT Statistics
Drop: All frame count: 855
Drop: All bytes count: 94143
Drop And Log: All frame count: 0
Drop And Log: All bytes count: 0
Bridge Only: All frame count: 0
Bridge Only: All bytes count: 0
Bridge Only And Log: All frame count: 0
Bridge Only And Log: All bytes count: 0
Forwarding To CPU: All frame count: 0
Forwarding To CPU: All bytes count: 0
Forwarded: All frame count: 2121
Forwarded: All bytes count: 180762
Forwarded And Log: All frame count: 0
Forwarded And Log: All bytes count: 0
Syntax Description interface [interface-id] (Optional) Display auto-QoS information for the specified
interface or for all interfaces. Valid interfaces include physical
ports.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified
expression.
expression Expression in the output to use as a reference point.
Usage Guidelines The show auto qos [interface [interface-id]] command displays the initial auto-QoS configuration; it
does not display any user changes to the configuration that might be in effect. Use the show
running-config privileged EXEC command to display the auto-QoS configuration and the user
modifications.
To display information about the QoS configuration that might be affected by auto-QoS, use one of these
commands:
• show mls qos
• show mls qos maps cos-dscp
• show mls qos interface [interface-id] [buffers | queueing]
• show mls qos maps [cos-dscp | cos-input-q | cos-output-q | dscp-cos | dscp-input-q |
dscp-output-q]
• show mls qos input-queue
• show running-config
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show auto qos command when auto-QoS is enabled:
Switch# show auto qos
Initial configuration applied by AutoQoS:
mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos
no mls qos srr-queue input cos-map
no mls qos srr-queue output cos-map
mls qos srr-queue input cos-map queue 1 threshold 3 0
mls qos srr-queue input cos-map queue 1 threshold 2 1
mls qos srr-queue input cos-map queue 2 threshold 1 2
mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
mls qos srr-queue input cos-map queue 2 threshold 3 3 5
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 2 4
mls qos srr-queue output cos-map queue 4 threshold 2 1
mls qos srr-queue output cos-map queue 4 threshold 3 0
no mls qos srr-queue input dscp-map
no mls qos srr-queue output dscp-map
mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
mls qos srr-queue input dscp-map queue 1 threshold 3 32
mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
mls qos srr-queue input dscp-map queue 2 threshold 2 26 33 34 35 36 37 38 39
mls qos srr-queue input dscp-map queue 2 threshold 2 48 49 50 51 52 53 54 55
mls qos srr-queue input dscp-map queue 2 threshold 2 56 57 58 59 60 61 62 63
mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 27 28 29 30 31 40
mls qos srr-queue input dscp-map queue 2 threshold 3 41 42 43 44 45 46 47
mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 27 28 29 30 31 48
mls qos srr-queue output dscp-map queue 2 threshold 3 49 50 51 52 53 54 55 56
mls qos srr-queue output dscp-map queue 2 threshold 3 57 58 59 60 61 62 63
mls qos srr-queue output dscp-map queue 3 threshold 3 16 17 18 19 20 21 22 23
mls qos srr-queue output dscp-map queue 3 threshold 3 26 32 33 34 35 36 37 38
mls qos srr-queue output dscp-map queue 3 threshold 3 39
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
no mls qos srr-queue input priority-queue 1
no mls qos srr-queue input priority-queue 2
mls qos srr-queue input bandwidth 90 10
no mls qos srr-queue input buffers
mls qos queue-set output 1 buffers 20 20 20 40
!
interface GigabitEthernet2/0/2
mls qos trust device cisco-phone
mls qos trust cos
no queue-set 1
srr-queue bandwidth shape 10 0 0 0
srr-queue bandwidth share 10 10 60 20
This is an example of output from the show auto qos interface command after the auto qos voip
cisco-phone interface configuration command is entered:
Switch# show auto qos interface
Initial configuration applied by AutoQoS:
!
interface GigabitEthernet2/0/2
mls qos trust device cisco-phone
mls qos trust cos
no queue-set 1
srr-queue bandwidth shape 10 0 0 0
srr-queue bandwidth share 10 10 60 20
This is an example of output from the show auto qos interface gigabitethernet2/0/2 command after the
auto qos voip cisco-phone interface configuration command is entered:
Switch# show auto qos interface gigabitethernet2/0/2
mls qos trust device cisco-phone
mls qos trust cos
no queue-set 1
srr-queue bandwidth shape 10 0 0 0
srr-queue bandwidth share 10 10 60 20
show boot
Use the show boot privileged EXEC command to display the settings of the boot environment variables.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show boot command. Table 2-16 describes each field in the
display.
Switch# show boot
BOOT path-list: flash:c3750-i5q3l2-mz-121.11.AX/c3750-i5q3l2-mz-121.11.AX.bin
Config file: flash:config.text
Private Config file: private-config
Enable Break: no
Manual Boot: yes
HELPER path-list:
Auto upgrade : yes
NVRAM/Config file
buffer size: 32768
Field Description
BOOT path-list Displays a semicolon separated list of executable files to try to load and execute when
automatically booting.
If the BOOT environment variable is not set, the system attempts to load and execute
the first executable image it can find by using a recursive, depth-first search through 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.
If the BOOT variable is set but the specified images cannot be loaded, the system
attempts to boot the first bootable file that it can find in the Flash file system.
Config file Displays the filename that IOS uses to read and write a nonvolatile copy of the system
configuration.
Private Config file Displays the filename that IOS uses to read and write a nonvolatile copy of the system
configuration.
Enable Break Displays whether a break during booting is enabled or disabled. If it is set to yes, on, or
1, you can interrupt the automatic boot process by pressing the Break key on the console
after the Flash file system is initialized.
Manual Boot Displays whether the switch automatically or manually boots. If it is set to no or 0, the
boot loader attempts to automatically boot the system. If it is set to anything else, you
must manually boot the switch from the boot loader mode.
Helper path-list Displays a semicolon separated list of loadable files to dynamically load during the boot
loader initialization. Helper files extend or patch the functionality of the boot loader.
Auto upgrade Displays whether the switch stack is set to automatically copy its software version to an
incompatible switch so that it can join the stack.
A switch in version-mismatch (VM) mode is a switch that has a different stack protocol
version than the version on the switch stack. Switches in VM mode cannot join the
switch stack. If the switch stack has an image that can be copied to a switch in VM
mode, and if the boot auto-copy-sw feature is enabled, the switch stack automatically
copies the image from another stack member to the switch in VM mode. The switch then
exits VM mode, reboots, and joins the switch stack.
NVRAM/Config file buffer size Displays the buffer size that IOS uses to hold a copy of the configuration file in memory.
The configuration file cannot be larger than the buffer size allocation.
show class-map
Use the show class-map user EXEC command to display quality of service (QoS) class maps, which
define the match criteria to classify traffic.
Syntax Description class-map-name (Optional) Display the contents of the specified class map.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show cluster
Use the show cluster user EXEC command to display the cluster status and a summary of the cluster to
which the switch belongs. This command can be entered on the cluster command switch and cluster
member switches.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If you enter this command on a switch that is not a cluster member, the error message Not a management
cluster member appears.
On a cluster member switch, this command displays the identity of the cluster command switch, the
switch member number, and the state of its connectivity with the cluster command switch.
On a cluster command switch stack or cluster command switch, this command displays the cluster name
and the total number of members. It also shows the cluster status and time since the status changed. If
redundancy is enabled, it displays the primary and secondary command-switch information.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output when the show cluster command is entered on the active cluster command
switch:
Switch> show cluster
Command switch for cluster "Ajang"
Total number of members: 7
Status: 1 members are unreachable
Time since last status change: 0 days, 0 hours, 2 minutes
Redundancy: Enabled
Standby command switch: Member 1
Standby Group: Ajang_standby
Standby Group Number: 110
Heartbeat interval: 8
Heartbeat hold-time: 80
Extended discovery hop count: 3
This is an example of output when the show cluster command is entered on a cluster member switch:
Switch1> show cluster
Member switch for cluster "hapuna"
Member number: 3
Management IP address: 192.192.192.192
Command switch mac address: 0000.0c07.ac14
Heartbeat interval: 8
Heartbeat hold-time: 80
This is an example of output when the show cluster command is entered on a cluster member switch
that is configured as the standby cluster command switch:
Switch> show cluster
Member switch for cluster "hapuna"
Member number: 3 (Standby command switch)
Management IP address: 192.192.192.192
Command switch mac address: 0000.0c07.ac14
Heartbeat interval: 8
Heartbeat hold-time: 80
This is an example of output when the show cluster command is entered on the cluster command switch
that has lost connectivity with member 1:
Switch> show cluster
Command switch for cluster "Ajang"
Total number of members: 7
Status: 1 members are unreachable
Time since last status change: 0 days, 0 hours, 5 minutes
Redundancy: Disabled
Heartbeat interval: 8
Heartbeat hold-time: 80
Extended discovery hop count: 3
This is an example of output when the show cluster command is entered on a cluster member switch
that has lost connectivity with the cluster command switch:
Switch> show cluster
Member switch for cluster "hapuna"
Member number: <UNKNOWN>
Management IP address: 192.192.192.192
Command switch mac address: 0000.0c07.ac14
Heartbeat interval: 8
Heartbeat hold-time: 80
show cluster candidates [detail | mac-address H.H.H.] [ | {begin | exclude | include} expression]
Syntax Description detail (Optional) Display detailed information for all candidates.
mac-address H.H.H. (Optional) MAC address of the cluster candidate.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines This command is available only on the cluster command switch stack or cluster command switch.
If the switch is not a cluster command switch, the command displays an empty line at the prompt.
The SN in the display means switch member number. If E appears in the SN column, it means that the
switch is discovered through extended discovery. If E does not appear in the SN column, it means that
the switch member number is the upstream neighbor of the candidate switch. The hop count is the
number of devices the candidate is from the cluster command switch.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show cluster candidates command:
Switch> show cluster candidates
|---Upstream---|
MAC Address Name Device Type PortIf FEC Hops SN PortIf FEC
00d0.7961.c4c0 StLouis-2 WS-C3750-12T Gi6/0/1 2 1 Fa0/11
00d0.bbf5.e900 ldf-dist-128 WS-C3524-XL Fa0/7 1 0 Fa0/24
00e0.1e7e.be80 1900_Switch 1900 3 0 1 0 Fa0/11
00e0.1e9f.7a00 Surfers-24 WS-C2924-XL Fa0/5 1 0 Fa0/3
00e0.1e9f.8c00 Surfers-12-2 WS-C2912-XL Fa0/4 1 0 Fa0/7
00e0.1e9f.8c40 Surfers-12-1 WS-C2912-XL Fa0/1 1 0 Fa0/9
This is an example of output from the show cluster candidates command that uses the MAC address of
a cluster member switch directly connected to the cluster command switch:
Switch> show cluster candidates mac-address 00d0.7961.c4c0
Device 'Tahiti-12' with mac address number 00d0.7961.c4c0
Device type: cisco WS-C3750-12T
Upstream MAC address: 00d0.796d.2f00 (Cluster Member 0)
Local port: Gi6/0/1 FEC number:
Upstream port: GI6/0/11 FEC Number:
Hops from cluster edge: 1
Hops from command device: 1
This is an example of output from the show cluster candidates command that uses the MAC address of
a cluster member switch three hops from the cluster edge:
Switch> show cluster candidates mac-address 0010.7bb6.1cc0
Device 'Ventura' with mac address number 0010.7bb6.1cc0
Device type: cisco WS-C2912MF-XL
Upstream MAC address: 0010.7bb6.1cd4
Local port: Fa2/1 FEC number:
Upstream port: Fa0/24 FEC Number:
Hops from cluster edge: 3
Hops from command device: -
This is an example of output from the show cluster candidates detail command:
Switch> show cluster candidates detail
Device 'Tahiti-12' with mac address number 00d0.7961.c4c0
Device type: cisco WS-C3512-XL
Upstream MAC address: 00d0.796d.2f00 (Cluster Member 1)
Local port: Fa0/3 FEC number:
Upstream port: Fa0/13 FEC Number:
Hops from cluster edge: 1
Hops from command device: 2
Device '1900_Switch' with mac address number 00e0.1e7e.be80
Device type: cisco 1900
Upstream MAC address: 00d0.796d.2f00 (Cluster Member 2)
Local port: 3 FEC number: 0
Upstream port: Fa0/11 FEC Number:
Hops from cluster edge: 1
Hops from command device: 2
Device 'Surfers-24' with mac address number 00e0.1e9f.7a00
Device type: cisco WS-C2924-XL
Upstream MAC address: 00d0.796d.2f00 (Cluster Member 3)
Local port: Fa0/5 FEC number:
Upstream port: Fa0/3 FEC Number:
Hops from cluster edge: 1
Hops from command device: 2
Syntax Description n (Optional) Number that identifies a cluster member. The range is 0 to 15.
detail (Optional) Display detailed information for all cluster members.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines This command is available only on the cluster command switch stack or cluster command switch.
If the cluster has no members, this command displays an empty line at the prompt.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show cluster members command. The SN in the display means
switch number.
Switch# show cluster members
|---Upstream---|
SN MAC Address Name PortIf FEC Hops SN PortIf FEC State
0 0002.4b29.2e00 StLouis1 0 Up (Cmdr)
1 0030.946c.d740 tal-switch-1 Fa0/13 1 0 Gi0/1 Up
2 0002.b922.7180 nms-2820 10 0 2 1 Fa0/18 Up
3 0002.4b29.4400 SanJuan2 Gi0/1 2 1 Fa0/11 Up
4 0002.4b28.c480 GenieTest Gi0/2 2 1 Fa0/9 Up
This is an example of output from the show cluster members for cluster member 3:
Switch# show cluster members 3
Device 'SanJuan2' with member number 3
Device type: cisco WS-C3750-12T
MAC address: 0002.4b29.4400
Upstream MAC address: 0030.946c.d740 (Cluster member 1)
Local port: Gi6/0/1 FEC number:
Upstream port: GI6/0/11 FEC Number:
Hops from command device: 2
This is an example of output from the show cluster members detail command:
Switch# show cluster members detail
Device 'StLouis1' with member number 0 (Command Switch)
Device type: cisco WS-C3750-12T
MAC address: 0002.4b29.2e00
Upstream MAC address:
Local port: FEC number:
Upstream port: FEC Number:
Hops from command device: 0
Device 'tal-switch-14' with member number 1
Device type: cisco WS-C3548-XL
MAC address: 0030.946c.d740
Upstream MAC address: 0002.4b29.2e00 (Cluster member 0)
Local port: Fa0/13 FEC number:
Upstream port: Gi0/1 FEC Number:
Hops from command device: 1
Device 'nms-2820' with member number 2
Device type: cisco 2820
MAC address: 0002.b922.7180
Upstream MAC address: 0030.946c.d740 (Cluster member 1)
Local port: 10 FEC number: 0
Upstream port: Fa0/18 FEC Number:
Hops from command device: 2
Device 'SanJuan2' with member number 3
Device type: cisco WS-C3750-12T
MAC address: 0002.4b29.4400
Upstream MAC address: 0030.946c.d740 (Cluster member 1)
Local port: Gi6/0/1 FEC number:
Upstream port: Fa6/0/11 FEC Number:
Hops from command device: 2
Device 'GenieTest' with member number 4
Device type: cisco SeaHorse
MAC address: 0002.4b28.c480
Upstream MAC address: 0030.946c.d740 (Cluster member 1)
Local port: Gi0/2 FEC number:
Upstream port: Fa0/9 FEC Number:
Hops from command device: 2
Device 'Palpatine' with member number 5
Device type: cisco WS-C2924M-XL
MAC address: 00b0.6404.f8c0
Upstream MAC address: 0002.4b29.2e00 (Cluster member 0)
Local port: Gi2/1 FEC number:
Upstream port: Gi0/7 FEC Number:
Hops from command device: 1
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines This display provides information that might be useful for Cisco technical support representatives
troubleshooting the switch.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is a partial output example from the show controllers cpu-interface command:
Switch# show controllers cpu-interface
cpu-queue-frames retrieved dropped invalid hol-block
----------------- ---------- ---------- ---------- ----------
rpc 4523063 0 0 0
stp 1545035 0 0 0
ipc 1903047 0 0 0
routing protocol 96145 0 0 0
L2 protocol 79596 0 0 0
remote console 0 0 0 0
sw forwarding 5756 0 0 0
host 225646 0 0 0
broadcast 46472 0 0 0
cbt-to-spt 0 0 0 0
igmp snooping 68411 0 0 0
icmp 0 0 0 0
logging 0 0 0 0
rpf-fail 0 0 0 0
queue14 0 0 0 0
cpu heartbeat 1710501 0 0 0
<output truncated>
<output truncated>
MicTransmitFifoInfo:
Fifo0: StartPtrs: 038C2800 ReadPtr: 038C2C38
WritePtrs: 038C2C38 Fifo_Flag: 8A800800
Weights: 001E001E
Fifo1: StartPtr: 03A9BC00 ReadPtr: 03A9BC60
WritePtrs: 03A9BC60 Fifo_Flag: 89800400
writeHeaderPtr: 03A9BC60
Fifo2: StartPtr: 038C8800 ReadPtr: 038C88E0
WritePtrs: 038C88E0 Fifo_Flag: 88800200
writeHeaderPtr: 038C88E0
Fifo3: StartPtr: 03C30400 ReadPtr: 03C30638
WritePtrs: 03C30638 Fifo_Flag: 89800400
writeHeaderPtr: 03C30638
Fifo4: StartPtr: 03AD5000 ReadPtr: 03AD50A0
WritePtrs: 03AD50A0 Fifo_Flag: 89800400
writeHeaderPtr: 03AD50A0
Fifo5: StartPtr: 03A7A600 ReadPtr: 03A7A600
WritePtrs: 03A7A600 Fifo_Flag: 88800200
writeHeaderPtr: 03A7A600
Fifo6: StartPtr: 03BF8400 ReadPtr: 03BF87F0
WritePtrs: 03BF87F0 Fifo_Flag: 89800400
<output truncated>
Syntax Description interface-id The physical interface (including type, stack member, module, and port number).
phy (Optional) Display the status of the internal registers on the switch physical layer
device (PHY) for the device or the interface. This display includes the operational
state of the automatic media-dependent-interface crossover (Auto MDIX) feature
on an interface.
detail (Optional) Display details about the PHY internal registers.
port-asic (Optional) Display information about the port ASIC internal registers.
configuration Display port ASIC internal register configuration.
statistics Display port ASIC statistics, including the Rx/Sup Queue and miscellaneous
statistics.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Command Modes Privileged EXEC (supported with only the interface-id keywords in user EXEC mode)
Usage Guidelines This display without keywords provides traffic statistics, basically the RMON statistics for all interfaces
or for the specified interface.
When you enter the phy or port-asic keywords, the displayed information is useful primarily for Cisco
technical support representatives troubleshooting the switch.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show controllers ethernet-controller command for an interface:
Switch# show controllers ethernet-controller GigabitEthernet6/0/1
This is an example of output from the show controllers ethernet-controller phy command for a
specific interface. Note that the last line of the display is the setting for automatic
media-dependent-interface crossover (Auto-MDIX) for the interface.
Switch# show controllers ethernet-controller gigabitethernet1/0/3 phy
This is an example of output from the show controllers ethernet-controller port-asic configuration
command:
Switch# show controllers ethernet-controller port-asic configuration
========================================================================
Switch 4, PortASIC 0 Registers
------------------------------------------------------------------------
DeviceType : 000101BC
Reset : 00000000
PmadMicConfig : 00000001
PmadMicDiag : 00000003
SupervisorReceiveFifoSramInfo : 000007D0 000007D0 40000000
SupervisorTransmitFifoSramInfo : 000001D0 000001D0 40000000
GlobalStatus : 00000800
IndicationStatus : 00000000
IndicationStatusMask : FFFFFFFF
InterruptStatus : 00000000
InterruptStatusMask : 01FFE800
SupervisorDiag : 00000000
SupervisorFrameSizeLimit : 000007C8
SupervisorBroadcast : 000A0F01
GeneralIO : 000003F9 00000000 00000004
StackPcsInfo : FFFF1000 860329BD 5555FFFF FFFFFFFF
FF0FFF00 86020000 5555FFFF 00000000
StackRacInfo : 73001630 00000003 7F001644 00000003
24140003 FD632B00 18E418E0 FFFFFFFF
StackControlStatus : 18E418E0
stackControlStatusMask : FFFFFFFF
TransmitBufferFreeListInfo : 00000854 00000800 00000FF8 00000000
0000088A 0000085D 00000FF8 00000000
TransmitRingFifoInfo : 00000016 00000016 40000000 00000000
0000000C 0000000C 40000000 00000000
TransmitBufferInfo : 00012000 00000FFF 00000000 00000030
TransmitBufferCommonCount : 00000F7A
TransmitBufferCommonCountPeak : 0000001E
TransmitBufferCommonCommonEmpty : 000000FF
NetworkActivity : 00000000 00000000 00000000 02400000
DroppedStatistics : 00000000
FrameLengthDeltaSelect : 00000001
SneakPortFifoInfo : 00000000
MacInfo : 0EC0801C 00000001 0EC0801B 00000001
00C0001D 00000001 00C0001E 00000001
<output truncated>
This is an example of output from the show controllers ethernet-controller port-asic statistics
command:
Switch# show controllers ethernet-controller port-asic statistics
===========================================================================
Switch 1, PortASIC 0 Statistics
---------------------------------------------------------------------------
0 RxQ-0, wt-0 enqueue frames 0 RxQ-0, wt-0 drop frames
4118966 RxQ-0, wt-1 enqueue frames 0 RxQ-0, wt-1 drop frames
0 RxQ-0, wt-2 enqueue frames 0 RxQ-0, wt-2 drop frames
<output truncated>
show controllers tcam [asic [number]] [detail] [ | {begin | exclude | include} expression]
Usage Guidelines This display provides information that might be useful for Cisco technical support representatives
troubleshooting the switch.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show controllers tcam command:
Switch# show controllers tcam
------------------------------------------------------------------------
TCAM-0 Registers
------------------------------------------------------------------------
REV: 00B30103
SIZE: 00080040
ID: 00000000
CCR: 00000000_F0000020
RPID0: 00000000_00000000
RPID1: 00000000_00000000
RPID2: 00000000_00000000
RPID3: 00000000_00000000
HRR0: 00000000_E000CAFC
HRR1: 00000000_00000000
HRR2: 00000000_00000000
HRR3: 00000000_00000000
HRR4: 00000000_00000000
HRR5: 00000000_00000000
HRR6: 00000000_00000000
HRR7: 00000000_00000000
<output truncated>
GMR31: FF_FFFFFFFF_FFFFFFFF
GMR32: FF_FFFFFFFF_FFFFFFFF
GMR33: FF_FFFFFFFF_FFFFFFFF
=============================================================================
TCAM related PortASIC 1 registers
=============================================================================
LookupType: 89A1C67D_24E35F00
LastCamIndex: 0000FFE0
LocalNoMatch: 000069E0
ForwardingRamBaseAddress:
00022A00 0002FE00 00040600 0002FE00 0000D400
00000000 003FBA00 00009000 00009000 00040600
00000000 00012800 00012900
show dot1x
Use the show dot1x privileged EXEC command to display 802.1X statistics, administrative status, and
operational status for the switch or for the specified interface.
show dot1x [all | interface interface-id | statistics interface interface-id] [ | {begin | exclude |
include} expression]
Syntax Description all (Optional) Display the 802.1X status for all interfaces.
interface interface-id (Optional) Display the 802.1X status for the specified interface (including
type, stack member, module, and port number).
statistics interface (Optional) Display 802.1X statistics for the specified interface (including
interface-id type, stack member, module, and port number).
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If you do not specify an interface, global parameters and a summary are displayed. If you specify an
interface, details for that interface are displayed.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show dot1x and the show dot1x all privileged EXEC commands:
Switch# show dot1x
Sysauthcontrol = Enabled
Dot1x Protocol Version = 1
Dot1x Oper Controlled Directions = Both
Dot1x Admin Controlled Directions = Both
This is an example of output from the show dot1x interface gigabitethernet1/0/3 privileged EXEC
command:
Switch# show dot1x interface gigabitethernet1/0/3
Supplicant MAC 00d0.b71b.35de
AuthSM State = AUTHENTICATED
BendSM State = IDLE
PortStatus = AUTHORIZED
MaxReq = 2
HostMode = Single
Port Control = Auto
QuietPeriod = 60 Seconds
Re-authentication = Disabled
ReAuthPeriod = 3600 Seconds
ServerTimeout = 30 Seconds
SuppTimeout = 30 Seconds
TxPeriod = 30 Seconds
Guest-Vlan = 0
This is an example of output from the show dot1x statistics interface gigabitethernet1/0/3 command.
Table 2-17 describes the fields in the display.
Switch# show dot1x statistics interface gigabitethernet1/0/3
PortStatistics Parameters for Dot1x
--------------------------------------------
TxReqId = 15 TxReq = 0 TxTotal = 15
RxStart = 4 RxLogoff = 0 RxRespId = 1 RxResp = 1
RxInvalid = 0 RxLenErr = 0 RxTotal= 6
RxVersion = 1 LastRxSrcMac 00d0.b71b.35de
Field Description
TxReqId Number of Extensible Authentication Protocol (EAP)-request/identity frames
that have been sent.
TxReq Number of EAP-request frames (other than request/identity frames) that have
been sent.
TxTotal Number of Extensible Authentication Protocol over LAN (EAPOL) frames of any
type that have been sent.
RxStart Number of valid EAPOL-start frames that have been received.
RxLogoff Number of EAPOL-logoff frames that have been received.
RxRespId Number of EAP-response/identity frames that have been received.
RxResp Number of valid EAP-response frames (other than response/identity frames) that
have been received.
RxInvalid Number of EAPOL frames that have been received and have an unrecognized
frame type.
RxLenError Number of EAPOL frames that have been received in which the packet body
length field is invalid.
RxTotal Number of valid EAPOL frames of any type that have been received.
RxVersion Number of received packets in the 802.1X version 1 format.
LastRxSrcMac Source MAC address carried in the most recently received EAPOL frame.
show dtp
Use the show dtp privileged EXEC command to display Dynamic Trunking Protocol (DTP) information
for the switch or for a specified interface.
Syntax Description interface (Optional) Display port security settings for the specified interface. Valid interfaces
interface-id include physical ports (including type, stack member, module, and port number).
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Statistics
----------
3160 packets received (3160 good)
0 packets dropped
0 nonegotiate, 0 bad version, 0 domain mismatches, 0 bad TLVs, 0 other
6320 packets output (6320 good)
3160 native, 3160 software encap isl, 0 isl hardware native
0 output errors
0 trunk timeouts
1 link ups, last link up on Mon Mar 01 1993, 01:02:29
0 link downs
show env
Use the show env user EXEC command to display fan, temperature, redundant power system (RPS)
availability, and power information for the switch being accessed (standalone switch or stack master or
stack member). Use with the stack keyword to display all information for the stack or for a specified
switch in the stack.
show env {all | fan | power | rps | stack [switch-number] | temperature} [ | {begin | exclude |
include} expression]
Syntax Description all Display both fan and temperature environmental status.
fan Display the switch fan status.
power Display the switch power status.
rps Display whether an RPS 300 Redundant Power System is connected to the switch.
stack Display all environmental status for each switch in the stack or for the specified
[switch-number] switch. The range is 1 to 9, depending on the switch member numbers in the stack.
temperature Display the switch temperature status.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Use the show access-lists privileged EXEC command to access information from a specific switch other
than the master.
You can use the show env stack [switch-number] command to display information about any switch in
the stack from any switch member.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show env all command entered from the master switch or a
standalone switch:
Switch> show env all
FAN is OK
TEMPERATURE is OK
POWER is OK
RPS is AVAILABLE
This example shows how to display information about stack member 3 from the master switch:
Switch> show env stack 3
SWITCH: 3
FAN is OK
TEMPERATURE is OK
POWER is OK
RPS is NOT PRESENT
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
On the Catalyst 3750 switch, a displayed gbic-invalid error reason refers to an invalid small form-factor
pluggable (SFP) interface.
Examples This is an example of output from the show errdisable detect command:
Switch> show errdisable detect
ErrDisable Reason Detection status
----------------- ----------------
udld Enabled
bpduguard Enabled
security-violation Enabled
channel-misconfig Enabled
psecure-violation Enabled
dhcp-rate-limit Enabled
unicast-flood Enabled
vmps Enabled
pagp-flap Enabled
dtp-flap Enabled
link-flap Enabled
gbic-invalid Enabled
loopback Enabled
Note Though visible in the output, the dhcp-rate-limit and unicast-flood fields are not valid.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines The Flaps column in the display shows how many changes to the state within the specified time interval
will cause an error to be detected and a port to be disabled. For example, the display shows that an error
will be assumed and the port shut down if three Dynamic Trunking Protocol (DTP)-state (port mode
access/trunk) or Port Aggregation Protocol (PAgP) flap changes occur during a 30-second interval, or if
5 link-state (link up/down) changes occur during a 10-second interval.
ErrDisable Reason Flaps Time (sec)
----------------- ------ ----------
pagp-flap 3 30
dtp-flap 3 30
link-flap 5 10
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show errdisable flap-values command:
Switch> show errdisable flap-values
ErrDisable Reason Flaps Time (sec)
----------------- ------ ----------
pagp-flap 3 30
dtp-flap 3 30
link-flap 5 10
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
On the Catalyst 3750 switch, a gbic-invalid error-disable reason refers to an invalid small form-factor
pluggable (SFP) interface.
Examples This is an example of output from the show errdisable recovery command:
Switch> show errdisable recovery
ErrDisable Reason Timer Status
----------------- --------------
udld Disabled
bpduguard Disabled
security-violatio Disabled
channel-misconfig Disabled
vmps Disabled
pagp-flap Disabled
dtp-flap Disabled
link-flap Disabled
gbic-invalid Disabled
psecure-violation Disabled
gbic-invalid Disabled
dhcp-rate-limit Disabled
unicast-flood Disabled
loopback Disabled
show etherchannel
Use the show etherchannel user EXEC command to display EtherChannel information for a channel.
Syntax Description channel-group-number (Optional) Number of the channel group. The range is 1 to 12.
detail Display detailed EtherChannel information.
load-balance Display the load-balance or frame-distribution scheme among ports in the
port channel.
port Display EtherChannel port information.
port-channel Display port-channel information.
protocol Display the protocol that is being used in the EtherChannel.
summary Display a one-line summary per channel-group.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If you do not specify a channel-group, all channel groups are displayed.
In the output, the Passive port list field is displayed only for Layer 3 port channels. This field means that
the physical interface, which is still not up, is configured to be in the channel group (and indirectly is in
the only port channel in the channel group).
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show etherchannel 1 detail command:
Switch> show etherchannel 1 detail
Group state = L2
Ports: 2 Maxports = 16
Port-channels: 1 Max Port-channels = 16
Protocol: LACP
Ports in the group:
-------------------
Port: Gi1/0/1
------------
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi1/0/1 SA bndl 32768 0x1 0x1 0x101 0x3D
Gi1/0/2 SA bndl 32768 0x0 0x1 0x0 0x3D
------------
Group: 2
----------
Protocol: PAgP
show interfaces
Use the show interfaces privileged EXEC command to display the administrative and operational status
of all interfaces or a specified interface.
Syntax Description interface-id (Optional) Valid interfaces include physical ports (including type, stack member,
module, and port number) and port channels. The valid port-channel range is 1 to
12.
vlan vlan-id (Optional) VLAN identification. The range is 1 to 4094.
accounting (Optional) Display accounting information on the interface, including active
protocols and input and output packets and octets.
capabilities (Optional) Display the capabilities of all interfaces or the specified interface,
including the features and options that you can configure on the interface. Though
visible in the command line help, this option is not available for VLAN IDs.
module number (Optional) Display capabilities of all interfaces on the specified stack member.
The range is from 1 to 9. This option is not available if you enter a specific
interface ID before the capabilities keyword.
counters (Optional) See the show interfaces counters command.
description (Optional) Display the administrative status and description set for an interface.
etherchannel (Optional) Display interface EtherChannel information.
flowcontrol (Optional) Display interface flowcontrol information
pruning (Optional) Display interface trunk VTP pruning information.
stats (Optional) Display the input and output packets by switching path for the
interface.
status (Optional) Display the status of the interface.
err-disabled (Optional) Display interfaces in error-disabled state.
switchport (Optional) Display the administrative and operational status of a switching
(nonrouting) port, including port blocking and port protection settings.
trunk Display interface trunk information. If you do not specify an interface,
information for only active trunking ports is displayed.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Note Though visible in the command-line help strings, the crb, fair-queue, irb, mac-accounting,
precedence, private-vlan mapping, random-detect, rate-limit, and shape keywords are not
supported.
Usage Guidelines The show interfaces capabilities command with different keywords has these results:
• Entering show interface capabilities module number displays the capabilities of all interfaces on
that switch in the stack. If there is no switch with that module number in the stack, the output is
blank. Entering show interfaces interface-id capabilities displays the capabilities of the specified
interface.
• Entering show interfaces capabilities (with no module number or interface ID) displays the
capabilities of all interfaces in the stack.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show interfaces command for Gigabit Ethernet interface 3 on
stack member 3:
Switch# show interfaces gigabitethernet3/0/3
GigabitEthernet3/0/3 is down, line protocol is down
Hardware is Gigabit Ethernet, address is 0009.43a7.d085 (bia 0009.43a7.d085)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
2 packets input, 1040 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
4 packets output, 1040 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
GigabitEthernet1/0/1
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface.
GigabitEthernet1/0/2
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface.
GigabitEthernet1/0/3
Protocol Pkts In Chars In Pkts Out Chars Out
No traffic sent or received on this interface.
<output truncated>
This is an example of output from the show interfaces capabilities command for an interface.
Switch# show interfaces gigabitethernet1/0/3 capabilities
GigabitEthernet1/0/3
Model: WS-C3750G-24TS
Type: 10/100/1000BaseTX
Speed: 10,100,1000,auto
Duplex: full,auto
Trunk encap. type: 802.1Q,ISL
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Broadcast suppression: percentage(0-100)
Flowcontrol: rx-(off,on,desired),tx-(none)
Fast Start: yes
QoS scheduling: rx-(not configurable on per port basis),tx-(4q2t)
CoS rewrite: yes
ToS rewrite: yes
UDLD: yes
Inline power: no
SPAN: source/destination
PortSecure: yes
Dot1x: yes
Dot1x: yes
This is an example of output from the show interfaces gigabitethernet1/0/4 description command
when the interface has been described as Connects to Marketing by using the description interface
configuration command.
Switch# show interfaces gigabitethernet1/0/4 description
Interface Status Protocol Description
Gi1/0/4 up down Connects to Marketing
This is an example of output from the show interfaces etherchannel command when port channels are
configured on the switch:
Switch# show interfaces etherchannel
----
Port-channel1:
Age of the Port-channel = 03d:20h:17m:29s
Logical slot/port = 10/1 Number of ports = 0
GC = 0x00000000 HotStandBy port = null
Port state = Port-channel Ag-Not-Inuse
Port-channel2:
Age of the Port-channel = 03d:20h:17m:29s
Logical slot/port = 10/2 Number of ports = 0
GC = 0x00000000 HotStandBy port = null
Port state = Port-channel Ag-Not-Inuse
Port-channel3:
Age of the Port-channel = 03d:20h:17m:29s
Logical slot/port = 10/3 Number of ports = 0
GC = 0x00000000 HotStandBy port = null
Port state = Port-channel Ag-Not-Inuse
This is an example of output from the show interfaces gigabitethernet1/0/6 pruning command when
pruning is enabled in the VTP domain:
Switch# show interfaces gigibitethernet1/0/6 pruning
Port Vlans pruned for lack of request by neighbor
Gi1/0/6 3,4
This is an example of output from the show interfaces stats command for a specified interface.
Switch# show interfaces vlan 1 stats
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 1165354 136205310 570800 91731594
Route cache 0 0 0 0
Total 1165354 136205310 570800 91731594
This is an example of partial output from the show interfaces status command. It displays the status of
all interfaces.
Switch# show interfaces status
<output truncated>
This is an example of output from the show interfaces status err-disabled command. It displays the
status of interfaces in the error-disabled state.
Switch# show interfaces status err-disabled
Port Name Status Reason
Gi2/0/26 err-disabled gbic-invalid
This is an example of output from the show interfaces switchport command for a single interface.
Table 2-18 describes the fields in the display.
Note Private VLANs are not supported in this release, so those fields are not applicable.
Field Description
Name Displays the port name.
Switchport Displays the administrative and operational status of the port.
In this display, the port is in switchport mode.
Administrative Mode Displays the administrative and operational modes.
Operational Mode
Administrative Trunking Displays the administrative and operational encapsulation
Encapsulation method and whether trunking negotiation is enabled.
Operational Trunking Encapsulation
Negotiation of Trunking
Access Mode VLAN Displays the VLAN ID to which the port is configured.
Trunking Native Mode VLAN Lists the VLAN ID of the trunk that is in native mode. Lists the
Trunking VLANs Enabled allowed VLANs on the trunk. Lists the active VLANs on the
trunk.
Trunking VLANs Active
Pruning VLANs Enabled Lists the VLANs that are pruning-eligible.
Protected Displays whether or not protected port is enabled (True) or
disabled (False) on the interface.
Field Description
Unknown unicast blocked Displays whether or not unknown multicast and unknown
Unknown multicast blocked unicast traffic is blocked on the interface.
This is an example of output from the show interfaces interface trunk command. It displays trunking
information for the interface.
Switch# show interfaces fastethernet1/0/17 trunk
Port Mode Encapsulation Status Native vlan
Fa1/0/17 desirable n-isl trunking 1
show interfaces [interface-id | vlan vlan-id] counters [broadcast | errors | module switch- number
| multicast | trunk | unicast] [ | {begin | exclude | include} expression]
Syntax Descriptions interface-id (Optional) ID of the physical interface, including type, stack member,
module, and port number.
vlan vlan-id (Optional) VLAN number of the management VLAN. The range is 1 to 4094.
broadcast (Optional) Display discarded broadcast traffic.
errors (Optional) Display error counters.
module switch- number (Optional) Display counters for the specified stack member. The range is
from 1 to 9, depending upon the switch numbers in the stack.
Note In this command, the module keyword refers to the stack member
number (1–9). In other commands that contain an interface ID, the
module number is always zero.
multicast (Optional) Display discarded multicast traffic.
trunk (Optional) Display trunk counters.
unicast (Optional) Display discarded unicast traffic.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If you do not enter any keywords, all counters for all interfaces are included.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of partial output from the show interfaces counters command. It displays all
counters for the switch.
Switch# show interfaces counters
Port InOctets InUcastPkts InMcastPkts InBcastPkts
Fa6/0/1 0 0 0 0
Fa6/0/2 0 0 0 0
Fa6/0/3 0 0 0 0
Fa6/0/4 0 0 0 0
Fa6/0/5 0 0 0 0
<output truncated>
Fa6/0/24 0 0 0 0
Gi6/0/1 0 0 0 0
Gi6/0/2 0 0 0 0
Fa8/0/1 0 0 0 0
Fa8/0/2 0 0 0 0
<output truncated>
This is an example of partial output from the show interfaces counters broadcast command. It displays
dropped broadcast traffic for all interfaces.
Switch# show interfaces counters broadcast
Port BcastSuppDiscards
Fa1/0/1 0
Fa1/0/2 0
Fa1/0/3 0
Fa1/0/4 0
Fa1/0/5 0
Fa1/0/6 0
<output truncated>
This is an example of partial output from the show interfaces counters module command for stack
member 2. It displays all counters for the specified switch in the stack.
Switch# show interfaces counters module 2
Sauron#show interface counters
<output truncated>
This is an example of output from the show interfaces counters trunk command. It displays trunk
counters for all interfaces.
Switch# show interfaces counters trunk
<output truncated>
Syntax Description profile number (Optional) The IGMP profile number to be displayed. The range is 1 to
4294967295. If no profile number is entered, all IGMP profiles are displayed.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples These are examples of output from the show ip igmp profile privileged EXEC command, with and
without specifying a profile number. If no profile number is entered, the display includes all profiles
configured on the switch.
Switch# show ip igmp profile 40
IGMP Profile 40
permit
range 233.1.1.1 233.255.255.255
show ip igmp snooping [mrouter] [multicast] [vlan vlan-id] [ | {begin | exclude | include}
expression]
Syntax Description mrouter (Optional) See the show ip igmp snooping mrouter command.
multicast (Optional) See the show ip igmp snooping multicast command.
vlan vlan-id (Optional) Specify a VLAN; the range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Use this command to display snooping configuration for the switch or for a specific VLAN.
Although visible in the output display, output lines related to topology change notification (TCN),
source-only learning, and report suppression are not supported.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show ip igmp snooping vlan 1 command. It shows snooping
characteristics for a specific VLAN.
Switch# show ip igmp snooping vlan 1
----------
IGMP snooping is globally enabled
IGMP snooping TCN solicit query is globally disabled
IGMP snooping global TCN flood query count is 2
IGMP snooping is enabled on this Vlan
IGMP snooping immediate-leave is disabled on this Vlan
IGMP snooping mrouter learn mode is pim-dvmrp on this Vlan
IGMP snooping source only learning age timer is 10
IGMP snooping is running in IGMP_ONLY mode on this Vlan
IGMP snooping report suppression is enabled on this Vlan
Note TCN, source-only learning, and report suppression are not supported, and information displayed about
these features is not valid.
This is an example of output from the show ip igmp snooping command. It displays snooping
characteristics for all VLANs on the switch.
Switch# show ip igmp snooping
vlan 1
----------
IGMP snooping is globally enabled
IGMP snooping TCN solicit query is globally disabled
IGMP snooping global TCN flood query count is 2
IGMP snooping is enabled on this Vlan
IGMP snooping immediate-leave is disabled on this Vlan
IGMP snooping mrouter learn mode is pim-dvmrp on this Vlan
IGMP snooping source only learning age timer is 10
IGMP snooping is running in IGMP_ONLY mode on this Vlan
IGMP snooping report suppression is enabled on this Vlan
vlan 2
----------
IGMP snooping is globally enabled
IGMP snooping TCN solicit query is globally disabled
IGMP snooping global TCN flood query count is 2
IGMP snooping is enabled on this Vlan
IGMP snooping immediate-leave is disabled on this Vlan
IGMP snooping mrouter learn mode is pim-dvmrp on this Vlan
IGMP snooping source only learning age timer is 10
IGMP snooping is running in IGMP_ONLY mode on this Vlan
IGMP snooping report suppression is enabled on this Vlan
<output truncated>
show ip igmp snooping mrouter [vlan vlan-id] [ | {begin | exclude | include} expression]
Syntax Description vlan vlan-id (Optional) Specify a VLAN; the range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Use this command to display multicast router ports on the switch or for a specific VLAN.
When multicast VLAN registration (MVR) is enabled, the show ip igmp snooping mrouter command
displays MVR multicast router information and IGMP snooping information.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show ip igmp snooping mrouter command. It shows how to
display multicast router ports on the switch.
Switch# show ip igmp snooping mrouter
Vlan ports
---- -----
1 Gi2/0/1(dynamic)
show ip igmp snooping multicast [vlan vlan-id] [count | dynamic [count | group ip_address] |
group ip_address | user [count | group ip_address]] [ | {begin | exclude | include} expression]
Syntax Description vlan vlan-id (Optional) Specify a VLAN; the range is 1 to 4094.
count (Optional) Display the total number of entries for the specified command
options instead of the actual entries.
dynamic (Optional) Display entries learned through IGMP snooping.
group ip_address (Optional) Display characteristics of the multicast group with the specified group
IP address.
user (Optional) Display only the user-configured multicast entries.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Use this command to display multicast information and the multicast table for specified parameters.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show ip igmp snooping multicast command without any
keywords. It displays the multicast table for the switch.
Switch# show ip igmp snooping multicast
This is an example of output from the show ip igmp snooping multicast count command. It displays
the total number of multicast groups on the switch.
Switch# show ip igmp snooping multicast count
Total number of multicast groups: 3
This is an example of output from the show ip igmp snooping multicast dynamic command. It shows
only the entries learned through IGMP snooping.
Switch# show ip igmp snooping multicast dynamic
This is an example of output from the show ip igmp snooping multicast group command. It shows the
entries for the group with the specified IP address.
Switch# show ip igmp snooping multicast group 224.1.2.30
Vlan Group Address Type Ports
---- ------------- ---- -----
1 224.1.2.30 IGMP Fa4/0/1, Fa4/0/37
This is an example of output from the show ip igmp snooping multicast vlan command. It displays all
entries belonging to the specified VLAN.
Switch# show ip igmp snooping multicast vlan 1
show lacp
Use the show lacp user EXEC command to display Link Aggregation Control Protocol (LACP)
channel-group information.
Syntax Description channel-group-number (Optional) Number of the channel group. The range is 1 to 12.
counters Display traffic information.
internal Display internal information.
neighbor Display neighbor information.
sys-id Display the system identifier that is being used by LACP. The system
identifier is made up of the LACP system priority and the switch MAC
address.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You can enter any show lacp command to display the active channel-group information. To display
specific channel information, enter the show lacp command with a channel-group number.
If you do not specify a channel group, information for all channel groups appears.
You can enter the channel-group-number option to specify a channel group for all keywords except
sys-id.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
do not appear, but the lines that contain Output appear.
Examples This is an example of output from the show lacp counters command user EXEC command. Table 2-19
describes the fields in the display.
Switch> show lacp counters
LACPDUs Marker Marker Response LACPDUs
Port Sent Recv Sent Recv Sent Recv Pkts Err
---------------------------------------------------------------------
Channel group:1
Gi2/0/5 19 10 0 0 0 0 0
Gi2/0/6 14 6 0 0 0 0 0
Gi2/0/7 8 7 0 0 0 0 0
Field Description
LACPDUs Sent and Recv The number of LACP packets sent and received by an interface.
Marker Sent and Recv The number of LACP marker packets sent and received by an
interface.
Marker Response Sent and Recv The number of LACP marker response packets sent and received
by an interface.
LACPDUs Pkts and Err The number of unknown and illegal packets received by LACP
for an interface.
Channel group 1
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi2/0/5 SA bndl 32768 0x3 0x3 0x4 0x3D
Gi2/0/6 SA bndl 32768 0x3 0x3 0x5 0x3D
Gi2/0/7 SA bndl 32768 0x3 0x3 0x6 0x3D
Field Description
State State of the specific port. These are the allowed values:
• – —Port is in an unknown state.
• bndl—Port is attached to an aggregator and bundled with
other ports.
• susp—Port is in a suspended state; it is not attached to any
aggregator.
• hot-sby—Port is in a hot-standby state.
• indiv—Port is incapable of bundling with any other port.
• indep—Port is in an independent state (not bundled but able
to switch data traffic. In this case, LACP is not running on
the partner port).
• down—Port is down.
LACP Port Priority Port priority setting. LACP uses the port priority to put ports s
in standby mode when there is a hardware limitation that
prevents all compatible ports from aggregating.
Admin Key Administrative key assigned to this port. LACP automatically
generates an administrative key value as a hexadecimal number.
The administrative key defines the ability of a port to aggregate
with other ports. A port’s ability to aggregate with other ports is
determined by the port physical characteristics (for example,
data rate and duplex capability) and configuration restrictions
that you establish.
Oper Key Runtime operational key that is being used by this port. LACP
automatically generates this value as a hexadecimal number.
Port Number Port number.
Port State State variables for the port, encoded as individual bits within a
single octet with these meanings:
• bit0: LACP_Activity
• bit1: LACP_Timeout
• bit2: Aggregation
• bit3: Synchronization
• bit4: Collecting
• bit5: Distributing
• bit6: Defaulted
• bit7: Expired
Partner’s information:
Partner’s information:
The system identification is made up of the system priority and the system MAC address. The first two
bytes are the system priority, and the last six bytes are the globally administered individual MAC address
associated to the system.
Syntax Description interface interface-id (Optional) Display the MAC ACLs configured on a specific interface. Valid
interfaces are physical ports and port channels; the port channel range is 1 to
64.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Command Modes User EXEC; the interface keyword is available only in privileged EXEC mode.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-access group user EXEC command. In this display,
Gigabit Ethernet interface 1/0/12 has the MAC access list macl_e1 applied; no MAC ACLs are applied
to other interfaces.
Switch> show mac access-group
Interface GigabitEthernet1/0/1:
Inbound access-list is not set
Interface GigabitEthernet1/0/2:
Inbound access-list is macl_e1
Interface GigabitEthernet1/0/3:
Inbound access-list is not set
Interface GigabitEthernet1/0/4:
Inbound access-list is not set
<output truncated>
Interface GigabitEthernet1/0/10:
Inbound access-list is not set
Interface GigabitEthernet1/0/11:
Inbound access-list is not set
Interface GigabitEthernet1/0/12:
Inbound access-list is macl_e1
<output truncated>
This is an example of output from the show mac access-group interface gigabitethernet1/ 0/12
command:
Switch# show mac access-group interface gigabitethernet1/0/12
Interface GigabitEthernet1/0/12:
Inbound access-list is macl_e1
show mac-address-table
Use the show mac-address-table user EXEC command to display a specific MAC address table static
and dynamic entry or the MAC address table static and dynamic entries on a specific interface or VLAN.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description mac-address Specify the 48-bit MAC address; the valid format is H.H.H.
interface interface-id (Optional) Display information for a specific interface. Valid interfaces
include physical ports and port channels.
vlan vlan-id (Optional) Display entries for the specific VLAN only. The range is 1 to
4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table address command:
Switch# show mac-address-table address 0002.4b28.c482
Mac Address Table
------------------------------------------
Syntax Description vlan vlan-id (Optional) Display aging time information for a specific VLAN. The range
is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If no VLAN number is specified, then the aging time for all VLANs is displayed.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table aging-time command:
Switch> show mac-address-table aging-time
Vlan Aging Time
---- ----------
1 300
This is an example of output from the show mac-address-table aging-time vlan 10 command:
Switch> show mac-address-table aging-time vlan 10
Vlan Aging Time
---- ----------
10 300
Syntax Description vlan vlan-id (Optional) Display the number of addresses for a specific VLAN. The range is 1 to
4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If no VLAN number is specified, the address count for all VLANs is displayed.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table count command:
Switch# show mac-address-table count
Syntax Description address mac-address (Optional) Specify a 48-bit MAC address; the valid format is H.H.H
(available in privileged EXEC mode only).
interface interface-id (Optional) Specify an interface to match; valid interfaces include physical
ports and port channels.
vlan vlan-id (Optional) Display entries for a specific VLAN; the range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Command Modes User EXEC; address keyword available only in privileged EXEC mode.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table dynamic command:
Switch> show mac-address-table dynamic
Mac Address Table
------------------------------------------
Syntax Description interface-id Specify an interface type; valid interfaces include physical ports and port
channels.
vlan vlan-id (Optional) Display entries for a specific VLAN; the range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table interface command:
Switch> show mac-address-table interface gigabitethernet6/0/2
Mac Address Table
------------------------------------------
show mac-address-table multicast [vlan-id] [count | user [count]] [ | {begin | exclude | include}
expression]
Syntax Description vlan vlan-id (Optional) Display addresses for a specific VLAN. The range is 1 to 4094.
count (Optional) Display the total number of entries for the specified command
options instead of the actual entries.
user (Optional) Display only the user-configured multicast entries.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Note Though visible in the command-line help string, the igmp-snooping keyword is not supported. Use the
show ip igmp snooping multicast privileged EXEC command to display the Internet Group Management
Protocol (IGMP) snooping multicast table.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table multicast command. It shows how to
display all multicast entries for the switch.
Switch> show mac-address-table multicast
Vlan Mac Address Type Ports
---- ----------- ---- -----
1 0100.5e00.0128 IGMP Gi1/0/1
This is an example of output from the show mac-address-table multicast count command. It shows
how to display a total count of MAC address entries for the switch.
Switch> show mac-address-table multicast count
This is an example of output from the show mac-address-table multicast vlan 1 count command. It
shows how to display a total count of MAC address entries for a VLAN.
Switch> show mac-address-table multicast vlan 1 count
Syntax Description interface (Optional) Display information for all interfaces. Valid interfaces include
physical ports and port channels.
interface-id (Optional) Display information for the specified interface. Valid interfaces
include physical ports and port channels.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Use the show mac-address-table notification command without any keywords to display whether the
feature is enabled or disabled, the MAC notification interval, the maximum number of entries allowed
in the history table, and the history table contents.
Use the interface keyword to display the flags for all interfaces. If the interface-id is included, only the
flags for that interface are displayed.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table notification command:
Switch> show mac-address-table notification
MAC Notification Feature is Enabled on the switch
Interval between Notification Traps : 60 secs
Number of MAC Addresses Added : 4
Number of MAC Addresses Removed : 4
Number of Notifications sent to NMS : 3
Maximum Number of entries configured in History Table : 100
Current History Table Length : 3
MAC Notification Traps are Enabled
History Table contents
----------------------
History Index 0, Entry Timestamp 1032254, Despatch Timestamp 1032254
MAC Changed Message :
Operation: Added Vlan: 2 MAC Addr: 0000.0000.0001 Module: 0 Port: 1
Syntax Description address mac-address (Optional) Specify a 48-bit MAC address; the valid format is H.H.H
(available in privileged EXEC mode only).
interface interface-id (Optional) Specify an interface to match; valid interfaces include physical
ports and port channels.
vlan vlan-id (Optional) Display addresses for a specific VLAN. The range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Command Modes User EXEC; address keyword available only in privileged EXEC mode.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table static command:
Switch> show mac-address-table static
Mac Address Table
------------------------------------------
Syntax Description vlan-id (Optional) Display addresses for a specific VLAN. The range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mac-address-table vlan 1 command:
Switch> show mac-address-table vlan 1
Mac Address Table
------------------------------------------
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mls qos command:
Switch> show mls qos
Qos is enabled
Syntax Description aggregate-policer-name (Optional) Display the policer configuration for the specified name.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mls qos aggregate-policer command:
Switch> show mls qos aggregate-policer policer1
aggregate-policer policer1 88000 2000000 exceed-action drop
Not used by any policy map
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mls qos input-queue command:
Switch> show mls qos input-queue
Queue : 1 2
----------------------------------------------
buffers : 90 10
bandwidth : 4 4
priority : 0 10
threshold1: 100 100
threshold2: 100 100
Syntax Description interface-id (Optional) Display QoS information for the specified interface. Valid interfaces
include physical ports.
buffers (Optional) Display the buffer allocation among the queues.
queueing (Optional) Display the queueing strategy (shared or shaped) and the weights
corresponding to the queues.
statistics (Optional) Display statistics for sent and received Differentiated Services Code
Points (DSCPs) and class of service (CoS) values, the number of packets
enqueued or dropped per egress queue, and the number of in-profile and
out-of-profile packets for each policer.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Note Though visible in the command-line help string, the policers keyword is not supported.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mls qos interface command:
Switch# show mls qos interface fastethernet1/0/7
FastEthernet1/0/7
Attached policy-map for Ingress: videowizard_policy
trust state: not trusted
COS override: dis
default COS: 0
DSCP Mutation Map: Default DSCP Mutation Map
This is an example of output from the show mls qos interface fastethernet1/0/7 buffers command:
Switch> show mls qos interface fastethernet1/0/7 buffers
FastEthernet1/0/7
The port is mapped to qset : 1
The allocations between the queues are : 25 25 25 25
This is an example of output from the show mls qos interface fastethernet1/0/7 queueing command:
Switch> show mls qos interface fastethernet1/0/7 queueing
FastEthernet1/0/7
Shaped queue weights (absolute) : 25 0 0 0
Shared queue weights : 25 25 25 25
The port bandwidth is limited to: 100%
The port is mapped to qset : 1
This is an example of output from the show mls qos interface fastethernet1/0/7 statistics command.
Table 2-21 describes the fields in this display.
Switch> show mls qos interface fastethernet1/0/7 statistics
FastEthernet1/0/7
dscp: incoming
-------------------------------
0 - 4 : 4213 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 6 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
dscp: outgoing
-------------------------------
0 - 4 : 363949 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 0 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
cos: incoming
-------------------------------
0 - 4 : 132067 0 0 0 0
5 - 9 : 0 0 0
cos: outgoing
-------------------------------
0 - 4 : 739155 0 0 0 0
5 - 9 : 90 0 0
Field Description
DSCP incoming Number of received packets for each DSCP value.
outgoing Number of sent packets for each DSCP value.
CoS incoming Number of received packets for each CoS value.
outgoing Number of sent packets for each CoS value.
Policer Inprofile Number of in profile packets for each policer.
Outofprofile Number of out of profile packets for each policer.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
The policed-DSCP, DSCP-to-CoS, and the DSCP-to-DSCP-mutation maps are displayed as a matrix.
The d1 column specifies the most-significant digit in the DSCP. The d2 row specifies the least-significant
digit in the DSCP. The intersection of the d1 and d2 values provides the policed-DSCP, the CoS, or the
mutated-DSCP value. For example, in the DSCP-to-CoS map, a DSCP value of 43 corresponds to a CoS
value of 5.
The DSCP input queue threshold and the DSCP output queue threshold maps are displayed as a matrix.
The d1 column specifies the most-significant digit of the DSCP number. The d2 row specifies the
least-significant digit in the DSCP number. The intersection of the d1 and the d2 values provides the
queue ID and threshold ID. For example, in the DSCP input queue threshold map, a DSCP value of 43
corresponds to queue 2 and threshold 1 (02-01).
The CoS input queue threshold and the CoS output queue threshold maps show the CoS value in the top
row and the corresponding queue ID and threshold ID in the second row. For example, in the CoS input
queue threshold map, a CoS value of 5 corresponds to queue 2 and threshold 1 (2-1).
Examples This is an example of output from the show mls qos maps command:
Switch> show mls qos maps
Policed-dscp map:
d1 : d2 0 1 2 3 4 5 6 7 8 9
---------------------------------------
0 : 00 01 02 03 04 05 06 07 08 09
1 : 10 11 12 13 14 15 16 17 18 19
2 : 20 21 22 23 24 25 26 27 28 29
3 : 30 31 32 33 34 35 36 37 38 39
4 : 40 41 42 43 44 45 46 47 48 49
5 : 50 51 52 53 54 55 56 57 58 59
6 : 60 61 62 63
Dscp-cos map:
d1 : d2 0 1 2 3 4 5 6 7 8 9
---------------------------------------
0 : 00 00 00 00 00 00 00 00 01 01
1 : 01 01 01 01 01 01 02 02 02 02
2 : 02 02 02 02 03 03 03 03 03 03
3 : 03 03 04 04 04 04 04 04 04 04
4 : 05 05 05 05 05 05 05 05 06 06
5 : 06 06 06 06 06 06 07 07 07 07
6 : 07 07 07 07
Cos-dscp map:
cos: 0 1 2 3 4 5 6 7
--------------------------------
dscp: 0 8 16 24 32 40 48 56
IpPrecedence-dscp map:
ipprec: 0 1 2 3 4 5 6 7
--------------------------------
dscp: 0 8 16 24 32 40 48 56
Dscp-outputq-threshold map:
d1 :d2 0 1 2 3 4 5 6 7 8 9
--------------------------------------------------------------------
0 : 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01
1 : 02-01 02-01 02-01 02-01 02-01 02-01 03-01 03-01 03-01 03-01
2 : 03-01 03-01 03-01 03-01 03-01 03-01 03-01 03-01 03-01 03-01
3 : 03-01 03-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01
4 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 04-01 04-01
5 : 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01
6 : 04-01 04-01 04-01 04-01
Dscp-inputq-threshold map:
d1 :d2 0 1 2 3 4 5 6 7 8 9
--------------------------------------------------------------------
0 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01
1 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01
2 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01
3 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01
4 : 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01 01-01 01-01
5 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01
6 : 01-01 01-01 01-01 01-01
Cos-outputq-threshold map:
cos: 0 1 2 3 4 5 6 7
------------------------------------
queue-threshold: 2-1 2-1 3-1 3-1 4-1 1-1 4-1 4-1
Cos-inputq-threshold map:
cos: 0 1 2 3 4 5 6 7
------------------------------------
queue-threshold: 1-1 1-1 1-1 1-1 1-1 2-1 1-1 1-1
Syntax Description qset-id (Optional) ID of the queue-set. Each port belongs to a queue-set, which defines
all the characteristics of the four egress queues per port. The range is 1 to 2.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mls qos queue-set command:
Switch> show mls qos queue-set
Queueset: 1
Queue : 1 2 3 4
----------------------------------------------
buffers : 25 25 25 25
threshold1: 100 50 100 100
threshold2: 100 50 100 100
reserved : 50 100 50 50
maximum : 400 400 400 400
Queueset: 2
Queue : 1 2 3 4
----------------------------------------------
buffers : 25 25 25 25
threshold1: 100 50 100 100
threshold2: 100 50 100 100
reserved : 50 100 50 50
maximum : 400 400 400 400
show monitor
Use the show monitor user EXEC command to display information about all Switched Port Analyzer
(SPAN) and Remote SPAN (RSPAN) sessions on the switch. Use the command with keywords to show
a specific session, all sessions, all local sessions, or all remote sessions.
show monitor [session {session_number | all | local | range list | remote} [detail]] [ | {begin |
exclude | include} expression]
Syntax Description session (Optional) Display information about specified SPAN sessions.
session_number Specify the number of the SPAN or RSPAN session. The range is 1 to 66.
all Display all SPAN sessions.
local Display only local SPAN sessions.
range list Display a range of SPAN sessions, where list is the range of valid sessions,
either a single session or a range of sessions described by two numbers, the
lower one first, separated by a hyphen. Do not enter any spaces between
comma-separated parameters or in hyphen-specified ranges.
Note This keyword is available only in privileged EXEC mode.
remote Display only remote SPAN sessions.
detail (Optional) Display detailed information about the specified sessions.
| begin Display begins with the line that matches the expression.
| exclude Display excludes lines that match the expression.
| include Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
The output is the same for the show monitor command and the show monitor session all command.
Examples This is an example of output for the show monitor user EXEC command:
Switch# show monitor
Session 1
---------
Type :Local Session
Source Ports:
RX Only: Fa4/0/24
TX Only: None
Both: Fa2/0/1-2,Fa4/0/1-5
Source VLANs:
RX Only: None
TX Only: None
Both: None
Source RSPAN VLAN:None
Destination Ports:Fa2/0/18
Encapsulation:Replicate
Filter VLANs: None
Dest RSPAN VLAN: None
Session 2
---------
Type :Remote Source Session
Source Ports:
RX Only: None
TX Only: None
Both: None
Source VLANs:
RX Only: None
TX Only: 10
Both: 1-9
Source RSPAN VLAN:None
Destination Ports:None
Filter VLANs: None
Dest RSPAN VLAN: 105
This is an example of output for the show monitor user EXEC command for RSPAN source session 1:
Switch# show monitor session 1
Session 1
---------
Type :Local Session
Source Ports:
RX Only: Fa4/0/24
TX Only: None
Both: Fa2/0/1-2,Fa4/0/1-5
Source VLANs:
RX Only: None
TX Only: None
Both: None
Source RSPAN VLAN:None
Destination Ports:Fa2/0/18
Encapsulation:Replicate
Filter VLANs: None
Dest RSPAN VLAN: None
This is an example of output for the show monitor session all user EXEC command when ingress traffic
forwarding is enabled:
Switch# show monitor session all
Session 1
---------
Type :Local Session
Source Ports :
Both :Fa1/0/2
Destination Ports :Fa2/0/2
Encapsulation :Replicate
Ingress:Enabled, default VLAN = 5
Ingress encapsulation:DOT1Q
Session 2
---------
Type :Local Session
Source Ports :
Both :Fa3/0/2
Destination Ports :Fa3/0/4
Encapsulation :Replicate
Ingress:Enabled
Ingress encapsulation:ISL
show mvr
Use the show mvr privileged EXEC command without keywords to display the current Multicast VLAN
Registration (MVR) global parameter values, including whether or not MVR is enabled, the MVR
multicast VLAN, the maximum query response time, the number of multicast groups, and the MVR
mode (dynamic or compatible).
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
In the preceding display, the maximum number of multicast groups is fixed at 256. The MVR mode is
either compatible (for inter-operability with Catalyst 2900 XL and Catalyst 3500 XL switches) or
dynamic (where operation is consistent with IGMP snooping operation and dynamic MVR membership
on source ports is supported).
show mvr interface [interface-id [members [vlan vlan-id]]] [ | {begin | exclude | include}
expression]
Syntax Description interface-id (Optional) Display MVR type, status, and Immediate Leave setting for the
interface.
Valid interfaces include physical ports (including type, stack member,
module, and port number.
members (Optional) Display all MVR groups to which the specified interface belongs.
vlan vlan-id (Optional) Display all MVR group members on this VLAN. The range is 1
to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If the entered port identification is a non-MVR port or a source port, the command returns an error
message. For receiver ports, it displays the port type, per port status, and Immediate-Leave setting.
If you enter the members keyword, all MVR group members on the interface are displayed. If you enter
a VLAN ID, all MVR group members in the VLAN are displayed.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mvr interface command:
Switch# show mvr interface
Port Type Status Immediate Leave
---- ---- ------- ---------------
Gi1/0/1 SOURCE ACTIVE/UP DISABLED
Gi1/0/2 RECEIVER ACTIVE/DOWN DISABLED
Gi1/0/5 RECEIVER ACTIVE/UP ENABLED
This is an example of output from the show mvr interface gigabitethernet1/0/6 members command:
Switch# show mvr interface gigabitethernet1/0/6 members
239.255.0.0 DYNAMIC ACTIVE
239.255.0.1 DYNAMIC ACTIVE
239.255.0.2 DYNAMIC ACTIVE
239.255.0.3 DYNAMIC ACTIVE
239.255.0.4 DYNAMIC ACTIVE
239.255.0.5 DYNAMIC ACTIVE
239.255.0.6 DYNAMIC ACTIVE
239.255.0.7 DYNAMIC ACTIVE
239.255.0.8 DYNAMIC ACTIVE
239.255.0.9 DYNAMIC ACTIVE
Syntax Description ip-address (Optional) The IP multicast address. If the address is entered, all receiver and
source ports that are members of the multicast group are displayed. If no
address is entered, all members of all Multicast VLAN Registration (MVR)
groups are listed. If a group has no members, the group is listed as Inactive.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines The show mvr members command applies to receiver and source ports. For MVR compatible mode, all
source ports are members of all multicast groups.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show mvr members command:
Switch# show mvr members
MVR Group IP Status Members
------------ ------ -------
239.255.0.1 ACTIVE Gi1/0/1(d), Gi1/0/5(s)
239.255.0.2 INACTIVE None
239.255.0.3 INACTIVE None
239.255.0.4 INACTIVE None
239.255.0.5 INACTIVE None
239.255.0.6 INACTIVE None
239.255.0.7 INACTIVE None
239.255.0.8 INACTIVE None
239.255.0.9 INACTIVE None
239.255.0.10 INACTIVE None
<output truncated>
This is an example of output from the show mvr members 239.255.0.2 command. It shows how to view
the members of the IP multicast group 239.255.0.2:
Switch# show mvr members 239.255.0.2
239.255.003.--22 ACTIVE Gi1/0/1(d), Gi1/0/2(d), Gi1/0/3(d),
Gi1/0/4(d), Gi1/0/5(s)
show pagp
Use the show pagp user EXEC command to display Port Aggregation Protocol (PAgP) channel-group
information.
Syntax Description channel-group-number (Optional) Number of the channel group. The range is 1 to 12.
counters Display traffic information.
internal Display internal information.
neighbor Display neighbor information.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You can enter any show pagp command to display the active channel-group information. To display the
nonactive information, enter the show pagp command with a channel-group number.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show pagp 1 counters command:
Switch> show pagp 1 counters
Information Flush
Port Sent Recv Sent Recv
--------------------------------------
Channel group: 1
Gi1/0/1 45 42 0 0
Gi1/0/2 45 41 0 0
Channel group 1
Hello Partner PAgP Learning Group
Port Flags State Timers Interval Count Priority Method Ifindex
Gi1/0/1 SC U6/S7 H 30s 1 128 Any 16
Gi1/0/2 SC U6/S7 H 30s 1 128 Any 16
show policy-map
Use the show policy-map user EXEC command to display quality of service (QoS) policy maps, which
define classification criteria for incoming traffic. Policy maps can include policers that specify the
bandwidth limitations and the action to take if the limits are exceeded.
Note Though visible in the command-line help string, the interface keyword is not supported, and the
statistics shown in the display should be ignored.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show port-security
Use the show port-security privileged EXEC command to display port-security settings for an interface
or for the switch.
Syntax Description interface interface-id (Optional) Display port security settings for the specified interface. Valid
interfaces include physical ports (including type, stack member, module,
and port number).
address (Optional) Display all secure MAC addresses on all ports or a specified port.
vlan (Optional) Display port security settings for all VLANs on the specified
interface. This keyword is visible only on interfaces that have the switchport
mode set to trunk.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If you enter the command without keywords, the output includes the administrative and operational
status of all secure ports on the switch.
If you enter an interface-id, the command displays port security settings for the interface.
If you enter the address keyword, the show port-security address command displays the secure MAC
addresses for all interfaces and the aging information for each secure address.
If you enter an interface-id and the address keyword, the show port-security interface interface-id
address command displays all the MAC addresses for the interface with aging information for each
secure address. You can also use this command to display all the MAC addresses for an interface even
if you have not enabled port security on it.
If you enter the vlan keyword, the show port-security address interface interface-id vlan command
displays the configured maximum and the current number of secure MAC addresses for all VLANs on
the interface. This option is visible only on interfaces that have the switchport mode set to trunk.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of the output from the show port-security command:
Switch# show port-security
Secure Port MaxSecureAddr CurrentAddr SecurityViolation Security Action
(Count) (Count) (Count)
-------------------------------------------------------------------------------
Gi1/0/1 1 0 0 Shutdown
-------------------------------------------------------------------------------
Total Addresses in System (excluding one mac per port) : 1
Max Addresses limit in System (excluding one mac per port) : 6272
This is an example of output from the show port-security interface gigabitethernet1/0/1 command:
Switch# show port-security interface gigabitethernet1/0/1
Port Security : Enabled
Port status : SecureUp
Violation mode : Shutdown
Maximum MAC Addresses : 1
Total MAC Addresses : 0
Configured MAC Addresses : 0
Aging time : 0 mins
Aging type : Absolute
SecureStatic address aging : Disabled
Security Violation count : 0
This is an example of output from the show port-security interface gigabitethernet1/0/2 address
command:
Switch# show port-security interface gigabitethernet1/0/2 address
Secure Mac Address Table
-------------------------------------------------------------------
Vlan Mac Address Type Ports Remaining Age
(mins)
---- ----------- ---- ----- -------------
1 0006.0700.0800 SecureConfigured Gi1/0/2 1
-------------------------------------------------------------------
Total Addresses: 1
This is an example of output from the show port-security interface gigabitethernet1/0/2 vlan
command:
Switch# show port-security interface gigabitethernet1/0/2 vlan
Default maximum:not set, using 5120
VLAN Maximum Current
5 default 1
10 default 54
11 default 101
12 default 101
13 default 201
14 default 501
Syntax Description vlan-ids (Optional) Display configuration information for a single VLAN identified by
VLAN ID number or a range of VLANs separated by a hyphen. For vlan-id, the
range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show running-config vlan command:
Switch# show running-config vlan 220-2000
Building configuration...
Current configuration:
!
vlan 239
!
vlan 501
!
vlan 1000
!
vlan 1002
tb-vlan1 1
tb-vlan2 1003
!
vlan 1003
tb-vlan1 1
tb-vlan2 1002
!
vlan 1004
bridge 1
end
show sdm prefer [default | routing | vlan [desktop]] [| {begin | exclude | include} expression]
Syntax Description default (Optional) Display the template that balances system resources among
features.
routing (Optional) Display the template that maximizes system resources for routing.
vlan (Optional) Display the template that maximizes system resources for Layer 2
VLANs.
desktop (Optional) For Catalyst 3750-12S aggregator switches only, display the
desktop templates. For this switch, when you do not enter the desktop
keyword, the aggregator templates appear.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines When you change the SDM template by using the sdm prefer global configuration command, you must
reload the switch for the configuration to take effect. If you enter the show sdm prefer command before
you enter the reload privileged EXEC command, the show sdm prefer command shows the template
currently in use and the template that will become active after a reload.
The numbers displayed for each template represent an approximate maximum number for each feature
resource. The actual number might vary, depending on the actual number of other features configured.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show sdm prefer command, displaying the template in use:
Switch# show sdm prefer
The current template is "desktop default" template.
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
This is an example of output from the show sdm prefer routing command entered on an aggregator
switch:
Switch# show sdm prefer routing
"aggregate routing" template:
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
This is an example of output from the show sdm prefer routing command entered on a desktop switch:
Switch# show sdm prefer routing
"desktop routing" template:
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
This is an example of output from the show sdm prefer command when you have configured a new
template but have not reloaded the switch:
Switch# show sdm prefer
The current template is "desktop routing" template.
The selected template optimizes the resources in
the switch to support this level of features for
8 routed interfaces and 1024 VLANs.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Examples This is an example of output from the show setup express command:
Switch# show setup express
express setup mode is active
show spanning-tree
Use the show spanning-tree user EXEC command to display spanning-tree state information.
show spanning-tree vlan vlan-id [active [detail] | blockedports | bridge | detail [active] |
inconsistentports | interface interface-id | root | summary] [ | {begin | exclude | include}
expression]
show spanning-tree {vlan vlan-id | bridge-group} root [address | cost | detail | forward-time |
hello-time | id | max-age | port | priority [system-id] [ | {begin | exclude | include}
expression]
show spanning-tree interface interface-id [active [detail] | cost | detail [active] | inconsistency |
portfast | priority | rootcost | state] [ | {begin | exclude | include} expression]
Syntax Description bridge-group (Optional) Specify the bridge group number. The range is 1 to 255.
active [detail] (Optional) Display spanning-tree information only on active interfaces
(available only in privileged EXEC mode).
backbonefast (Optional) Display spanning-tree BackboneFast status.
blockedports (Optional) Display blocked port information (available only in privileged
EXEC mode).
bridge [address | detail | (Optional) Display status and configuration of this switch (optional
forward-time | hello-time | keywords available only in privileged EXEC mode).
id | max-age | priority
[system-id] | protocol]
detail [active] (Optional) Display a detailed summary of interface information (active
keyword available only in privileged EXEC mode).
inconsistentports (Optional) Display inconsistent port information (available only in
privileged EXEC mode).
interface interface-id (Optional) Display spanning-tree information for the specified interface
[active [detail] | cost | (all options except portfast and state available only in privileged EXEC
detail [active] | mode). Enter each interface separated by a space. Ranges are not
inconsistency | portfast | supported. Valid interfaces include physical ports, VLANs, and port
priority | rootcost | state] channels. The VLAN range is 1 to 4094. The port-channel range is 1 to
12.
Command Modes User EXEC; indicated keywords available only in privileged EXEC mode.
Usage Guidelines If the vlan-id variable is omitted, the command applies to the spanning-tree instance for all VLANs.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show spanning-tree active command:
Switch# show spanning-tree active
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32768
Address 0001.42e2.cdd0
Cost 3038
Port 24 (GigabitEthernet2/0/1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
This is an example of output from the show spanning-tree interface gigabitethernet2/0/1 command:
Switch# show spanning-tree interface gigabitethernet2/0/1
Vlan Role Sts Cost Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------------------
VLAN0001 Root FWD 3019 128.24 P2p
UplinkFast statistics
-----------------------
Number of transitions via uplinkFast (all VLANs) : 0
Number of proxy multicast addresses transmitted (all VLANs) : 0
BackboneFast statistics
-----------------------
Number of transition via backboneFast (all VLANs) : 0
Number of inferior BPDUs received (all VLANs) : 0
Number of RLQ request PDUs received (all VLANs) : 0
Number of RLQ response PDUs received (all VLANs) : 0
Number of RLQ request PDUs sent (all VLANs) : 0
Number of RLQ response PDUs sent (all VLANs) : 0
This is an example of output from the show spanning-tree mst configuration command:
Switch# show spanning-tree mst configuration
Name [region1]
Revision 1
Instance Vlans Mapped
-------- ------------------
0 1-9,21-4094
1 10-20
----------------------------
This is an example of output from the show spanning-tree mst interface gigabitethernet2/0/1
command:
Switch# show spanning-tree mst interface gigabitethernet2/0/1
GigabitEthernet2/0/1 of MST00 is root forwarding
Edge port: no (default) port guard : none (default)
Link type: point-to-point (auto) bpdu filter: disable (default)
Boundary : boundary (STP) bpdu guard : disable (default)
Bpdus sent 5, received 74
Command Description
spanning-tree mst max-age Sets the interval between messages that the spanning tree
receives from the root switch.
spanning-tree mst max-hops Sets the number of hops in an MST region before the
BPDU is discarded and the information held for a port is
aged.
spanning-tree mst port-priority Configures an interface priority.
spanning-tree mst priority Configures the switch priority for the specified
spanning-tree instance.
spanning-tree mst root Configures the MST root switch priority and timers based
on the network diameter.
spanning-tree port-priority Configures an interface priority.
spanning-tree portfast (global Globally enables the BPDU filtering or the BPDU guard
configuration) feature on Port Fast-enabled ports or enables the Port Fast
feature on all nontrunking ports.
spanning-tree portfast (interface Enables the Port Fast feature on an interface and all its
configuration) associated VLANs.
spanning-tree uplinkfast Accelerates the choice of a new root port when a link or
switch fails or when the spanning tree reconfigures itself.
spanning-tree vlan Configures spanning tree on a per-VLAN basis.
show storm-control
Use the show storm-control user EXEC command to display broadcast, multicast, or unicast storm
control settings on the switch or on the specified interface or to display storm-control history.
Syntax Description interface-id (Optional) Interface ID for the physical port (including type, stack member,
module, and port number).
broadcast (Optional) Display broadcast storm threshold setting.
multicast (Optional) Display multicast storm threshold setting.
unicast (Optional) Display unicast storm threshold setting.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines When you enter an interface-id, the storm control thresholds are displayed for the specified interface.
If you do not enter an interface-id, settings are displayed for one traffic type for all ports on the switch.
If you do not enter a traffic type, settings are displayed for broadcast storm control.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of a partial output from the show storm-control command when no keywords are
entered. Because no traffic type keyword was entered, the broadcast storm control settings are displayed.
Switch> show storm-control
<output truncated>
This is an example of output from the show storm-control command for a specified interface. Because
no traffic type keyword was entered, the broadcast storm control settings are displayed.
Switch> show storm-control gigabitethernet 2/0/1
This is an example of output from the show storm-control command for a specified interface and traffic
type, where no storm control threshold has been set for that traffic type on the specified interface.
Switch> show storm-control gigabitethernet1/0/5 multicast
Field Description
Interface Displays the ID of the interface.
Filter State Displays the status of the filter:
• Blocking—Storm control is enabled, and a storm has occurred.
• Forwarding—Storm control is enabled, and no storms have occurred.
• Inactive—Storm control is disabled.
Level Displays the threshold level set on the interface for broadcast traffic or the
specified traffic type (broadcast, multicast, or unicast).
Current Displays the bandwidth utilization of broadcast traffic or the specified traffic
type (broadcast, multicast, or unicast) as a percentage of total available
bandwidth. This field is only valid when storm control is enabled.
show switch
Use the show switch user EXEC command to display information related to the stack member or the
switch stack.
Syntax Description stack-member-number (Optional) Display information for the specified stack member. The
range is 1 to 9.
detail (Optional) Display detailed information about the stack ring.
neighbors (Optional) Display the neighbors for the entire switch stack.
stack-ports (Optional) Display port information for the entire switch stack.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
These are the states displayed from this command:
• Waiting—The stage when a switch is booting up and waiting for communication from other switches
in the stack. The switch has not yet determined whether it is a stack master or not.
Stack members not participating in a stack master election remain in the waiting state until the stack
master is elected and ready.
• Initializing—The stage when a switch has determined whether it is the stack master or not. If the
switch is not the stack master, it is receiving its system- and interface-level configuration from the
stack master and loading it.
• Ready—The stage when the stack member has completed loading the system- and interface-level
configuration and is ready to forward traffic.
• Master Re-Init—The stage immediately after a stack master re-election and a different stack
member is elected stack master. The new stack master is re-initializing its configuration. This state
applies only to the new stack master.
• Ver Mismatch—The stage of a switch in version mismatch (VM) mode. VM mode is when a switch
joining the switch stack has a different stack protocol minor version number from the stack master.
• SDM Mismatch—The stage of a switch in Switch Database Management (SDM) mismatch mode.
SDM mismatch is when a stack member does not support the SDM template running on the stack
master.
A typical state transition for a stack member (including a stack master) booting up is Waiting ->
Initializing -> Ready.
A typical state transition for a stack member becoming a stack master after a stack master election is
Ready -> Master Re-Init -> Ready.
A typical state transition for a stack member in version mismatch (VM) mode is Waiting ->
Ver Mismatch.
The word slave in the output refers to a stack member other than the stack master.
Examples This example shows how to display summary information about stack member 6:
Switch(config)# show switch 6
Current
Switch# Role Mac Address Priority State
--------------------------------------------------------
6 Slave 0003.e31a.1e00 1 Ready
This example shows how to display summary information about a switch stack:
Switch(config)# show switch
Current
Switch# Role Mac Address Priority State
--------------------------------------------------------
6 Slave 0003.e31a.1e00 1 Ready
*8 Master 0003.e31a.1200 1 Ready
This example shows how to display neighbor information for a switch stack:
Switch(config)# show switch neighbors
Switch # Port A Port B
-------- ------ ------
6 None 8
8 6 None
This example shows how to display stack-port information for a switch stack:
Switch(config)# show switch stack-ports
Switch # Port A Port B
-------- ------ ------
6 Down Ok
8 Ok Down
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If you have used the system mtu or system mtu jumbo global configuration command to change the
MTU setting, the new setting does not take effect until you reset the switch.
The system MTU refers to 10/100 ports; the system jumbo MTU refers to Gigabit ports.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show system mtu command:
Switch# show system mtu
show udld
Use the show udld user EXEC command to display UniDirectional Link Detection (UDLD)
administrative and operational status for all ports or the specified port.
Syntax Description interface-id (Optional) ID of the interface and port number. Valid interfaces include
physical ports and VLANs. The VLAN range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines If you do not enter an interface-id, administrative and operational UDLD status for all interfaces are
displayed.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show udld gigabitethernet6/0/11 command. For this display,
UDLD is enabled on both ends of the link, and UDLD detects that the link is bidirectional. Table 2-23
describes the fields in this display.
Switch> show udld gigabitethernet6/0/11
Interface gi6/0/11
---
Port enable administrative configuration setting: Follows device default
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement - Single Neighbor detected
Message interval: 60
Time out interval: 5
Entry 1
Expiration time: 146
Device ID: 1
Current neighbor state: Bidirectional
Device name: 0050e2826000
Port ID: Gi6/0/12
Neighbor echo 1 device: SAD03160954
Neighbor echo 1 port: Gi6/0/11
Message interval: 5
CDP Device name: 066527791
Field Description
Interface The interface on the local device configured for UDLD.
Port enable administrative How UDLD is configured on the port. If UDLD is enabled or
configuration setting disabled, the port enable configuration setting is the same as the
operational enable state. Otherwise, the enable operational setting
depends on the global enable setting.
Port enable operational state Operational state that shows whether UDLD is actually running on
this port.
Current bidirectional state The bidirectional state of the link. An unknown state is displayed if
the link is down or if it is connected to an UDLD-incapable device.
A bidirectional state is displayed if the link is a normal two-way
connection to a UDLD-capable device. All other values mean
miswiring.
Current operational state The current phase of the UDLD state machine. For a normal
bidirectional link, the state machine is most often in the
Advertisement phase.
Message interval How often advertisement messages are sent from the local device.
Measured in seconds.
Time out interval The time period, in seconds, that UDLD waits for echoes from a
neighbor device during the detection window.
Entry 1 Information from the first cache entry, which contains a copy of echo
information received from the neighbor.
Expiration time The amount of time in seconds remaining before this cache entry is
aged out.
Device ID The neighbor device identification.
Current neighbor state The neighbor’s current state. If both the local and neighbor devices
are running UDLD normally, the neighbor state and local state
should be bidirectional. If the link is down or the neighbor is not
UDLD-capable, no cache entries are displayed.
Device name The neighbor MAC address.
Port ID The neighbor port ID enabled for UDLD.
Neighbor echo 1 device The MAC address of the neighbors’ neighbor from which the echo
originated.
Neighbor echo 1 port The port number ID of the neighbor from which the echo originated.
Message interval The rate, in seconds, at which the neighbor is sending advertisement
messages.
CDP device name CDP name of the device.
show version
Use the show version user EXEC command to display version information for the hardware and
firmware.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Switch 01
---------
<output truncated>
show vlan
Use the show vlan user EXEC command to display the parameters for all configured VLANs or one
VLAN (if the VLAN ID or name is specified) on the switch.
show vlan [brief | id vlan-id | internal usage | name vlan-name | remote-span | summary]
[ | {begin | exclude | include} expression]
Syntax Description brief (Optional) Display one line for each VLAN with the VLAN name, status,
and its ports.
id vlan-id (Optional) Display information about a single VLAN identified by VLAN ID
number. For vlan-id, the range is 1 to 4094.
internal usage (Optional) Display list of VLANs being used internally by the switch. These
VLANs are always from the extended range (VLAN IDs 1006 to 4094), and
you cannot create VLANs with these IDS by using the vlan global
configuration command until you remove them from internal use.
name vlan-name (Optional) Display information about a single VLAN identified by VLAN
name. The VLAN name is an ASCII string from 1 to 32 characters.
remote-span (Optional) Display information about Remote SPAN (RSPAN) VLANs.
summary (Optional) Display VLAN summary information.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Note Though visible in the command-line help string, the ifindex and private-vlan keywords are not
supported.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show vlan command. Table 2-24 describes each field in the
display.
Switch> show vlan
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa1/0/1, Fa1/0/2, Fa1/0/3
Fa1/0/4, Fa1/0/5, Fa1/0/6
Fa1/0/7, Fa1/0/8, Fa1/0/9
Fa1/0/10, Fa1/0/11, Fa1/0/12
Fa1/0/13, Fa1/0/14, Fa1/0/15
Fa1/0/16, Fa1/0/17, Fa1/0/18
Fa1/0/19, Fa1/0/20, Fa1/0/21
Fa1/0/22, Fa1/0/23, Fa1/0/24
Fa1/0/25, Fa1/0/26, Fa1/0/27
Fa1/0/28, Fa1/0/29, Fa1/0/30
Fa1/0/31, Fa1/0/32, Fa1/0/33
Fa1/0/34, Fa1/0/35, Fa1/0/36
Fa1/0/46, Gi1/0/1, Gi1/0/2
Gi1/0/3, Gi1/0/4, Gi2/0/1
Gi2/0/2, Gi2/0/3, Gi2/0/4
Gi2/0/5, Gi2/0/6, Gi2/0/7
<output truncated>
2 VLAN0002 active
3 VLAN0003 active
<output truncated>
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 1002 1003
2 enet 100002 1500 - - - - - 0 0
3 enet 100003 1500 - - - - - 0 0
<output truncated>
Field Description
VLAN VLAN number.
Name Name, if configured, of the VLAN.
Status Status of the VLAN (active or suspend).
Ports Ports that belong to the VLAN.
Field Description
Type Media type of the VLAN.
SAID Security association ID value for the VLAN.
MTU Maximum transmission unit size for the VLAN.
Parent Parent VLAN, if one exists.
RingNo Ring number for the VLAN, if applicable.
BrdgNo Bridge number for the VLAN, if applicable.
Stp Spanning Tree Protocol type used on the VLAN.
BrdgMode Bridging mode for this VLAN—possible values are source-route bridging
(SRB) and source-route transparent (SRT); the default is SRB.
Trans1 Translation bridge 1.
Trans2 Translation bridge 2.
Remote SPAN VLANs Identifies any RSPAN VLANs that have been configured.
Primary/Secondary/ Not applicable to this release.
Type/Ports
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
2 enet 100002 1500 - - - - - 0 0
This is an example of output from the show vlan internal usage command. It shows that VLANs 1025
and 1026 are being used as internal VLANs for Fast Ethernet routed ports 23 and 24 on stack member
1. If you want to use one of these VLAN IDs, you must first shut down the routed port, which releases
the internal VLAN, and then create the extended-range VLAN. When you start up the routed port,
another internal VLAN number is assigned to it.
Switch> show vlan internal usage
VLAN Usage
---- -------------
1025 FastEthernet1/0/23
1026 FastEthernet1/0/24
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show vlan access-map command:
Switch# show vlan access-map
Vlan access-map "SecWiz" 10
Match clauses:
ip address: SecWiz_Fa1_0_3_in_ip
Action:
forward
show vlan filter [access-map name | vlan vlan-id] [ | {begin | exclude | include} expression]
Syntax Description access-map name (Optional) Display filtering information for the specified VLAN access map.
vlan vlan-id (Optional) Display filtering information for the specified VLAN. The range is
1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show vlan filter command:
Switch# show vlan filter
VLAN Map map_1 is filtering VLANs:
20-22
show vmps
Use the show vmps user EXEC command without keywords to display the VLAN Query Protocol (VQP)
version, reconfirmation interval, retry count, VLAN Membership Policy Server (VMPS) IP addresses,
and the current and primary servers, or use the statistics keyword to display client-side statistics.
Syntax Description statistics (Optional) Display VQP client-side statistics and counters.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Reconfirmation status
---------------------
VMPS Action: other
This is an example of output from the show vmps statistics command. Table 2-25 describes each field
in the display.
Switch> show vmps statistics
VMPS Client Statistics
----------------------
VQP Queries: 0
VQP Responses: 0
VMPS Changes: 0
VQP Shutdowns: 0
VQP Denied: 0
VQP Wrong Domain: 0
VQP Wrong Version: 0
VQP Insufficient Resource: 0
Field Description
VQP Queries Number of queries sent by the client to the VMPS.
VQP Responses Number of responses sent to the client from the VMPS.
VMPS Changes Number of times that the VMPS changed from one server to another.
VQP Shutdowns Number of times the VMPS sent a response to shut down the port. The client
disables the port and removes all dynamic addresses on this port from the
address table. You must administratively re-enable the port to restore
connectivity.
VQP Denied Number of times the VMPS denied the client request for security reasons. When
the VMPS response denies an address, no frame is forwarded to or from the
workstation with that address (broadcast or multicast frames are delivered to the
workstation if the port has been assigned to a VLAN). The client keeps the
denied address in the address table as a blocked address to prevent more queries
from being sent to the VMPS for each new packet received from this
workstation. The client ages the address if no new packets are received from this
workstation on this port within the aging time period.
VQP Wrong Domain Number of times the management domain in the request does not match the one
for the VMPS. Any previous VLAN assignments of the port are not changed.
This response means that the server and the client have not been configured with
the same VTP management domain.
VQP Wrong Version Number of times the version field in the query packet contains a value that is
higher than the version supported by the VMPS. The VLAN assignment of the
port is not changed. The switches send only VMPS version 1 requests.
VQP Insufficient Number of times the VMPS is unable to answer the request because of a
Resource resource availability problem. If the retry limit has not yet been reached, the
client repeats the request with the same server or with the next alternate server,
depending on whether the per-server retry count has been reached.
show vtp
Use the show vtp user EXEC command to display general information about the VLAN Trunking
Protocol (VTP) management domain, status, and counters.
Syntax Description counters Display the VTP statistics for the switch.
password Display the configured VTP password.
status Display general information about the VTP management domain status.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples This is an example of output from the show vtp counters command. Table 2-26 describes each field in
the display.
Switch> show vtp counters
VTP statistics:
Summary advertisements received : 0
Subset advertisements received : 0
Request advertisements received : 0
Summary advertisements transmitted : 0
Subset advertisements transmitted : 0
Request advertisements transmitted : 0
Number of config revision errors : 0
Number of config digest errors : 0
Number of V1 summary errors : 0
Field Description
Summary advertisements Number of summary advertisements received by this switch on its trunk
received ports. Summary advertisements contain the management domain name,
the configuration revision number, the update timestamp and identity, the
authentication checksum, and the number of subset advertisements to
follow.
Subset advertisements Number of subset advertisements received by this switch on its trunk
received ports. Subset advertisements contain all the information for one or more
VLANs.
Request advertisements Number of advertisement requests received by this switch on its trunk
received ports. Advertisement requests normally request information on all
VLANs. They can also request information on a subset of VLANs.
Summary advertisements Number of summary advertisements sent by this switch on its trunk
transmitted ports. Summary advertisements contain the management domain name,
the configuration revision number, the update timestamp and identity, the
authentication checksum, and the number of subset advertisements to
follow.
Subset advertisements Number of subset advertisements sent by this switch on its trunk ports.
transmitted Subset advertisements contain all the information for one or more
VLANs.
Request advertisements Number of advertisement requests sent by this switch on its trunk ports.
transmitted Advertisement requests normally request information on all VLANs.
They can also request information on a subset of VLANs.
Number of configuration Number of revision errors.
revision errors
Whenever you define a new VLAN, delete an existing one, suspend or
resume an existing VLAN, or modify the parameters on an existing
VLAN, the configuration revision number of the switch increments.
Revision errors increment whenever the switch receives an
advertisement whose revision number matches the revision number of
the switch, but the MD5 digest values do not match. This error means
that the VTP password in the two switches is different or that the
switches have different configurations.
These errors means that the switch is filtering incoming advertisements,
which causes the VTP database to become unsynchronized across the
network.
Field Description
Number of configuration Number of MD5 digest errors.
digest errors Digest errors increment whenever the MD5 digest in the summary packet
and the MD5 digest of the received advertisement calculated by the
switch do not match. This error usually means that the VTP password in
the two switches is different. To solve this problem, make sure the VTP
password on all switches is the same.
These errors mean that the switch is filtering incoming advertisements,
which causes the VTP database to become unsynchronized across the
network.
Number of V1 summary Number of version 1 errors.
errors Version 1 summary errors increment whenever a switch in VTP V2 mode
receives a VTP version 1 frame. These errors mean that at least one
neighboring switch is either running VTP version 1 or VTP version 2
with V2-mode disabled. To solve this problem, change the configuration
of the switches in VTP V2-mode to disabled.
Join Transmitted Number of VTP pruning messages sent on the trunk.
Join Received Number of VTP pruning messages received on the trunk.
Summary Advts Received Number of VTP summary messages received on the trunk from devices
from non-pruning-capable that do not support pruning.
device
This is an example of output from the show vtp status command. Table 2-27 describes each field in the
display.
Switch> show vtp status
VTP Version : 2
Configuration Revision : 0
Maximum VLANs supported locally : 1005
Number of existing VLANs : 45
VTP Operating Mode : Transparent
VTP Domain Name : shared_testbed1
VTP Pruning Mode : Disabled
VTP V2 Mode : Disabled
VTP Traps Generation : Enabled
MD5 digest : 0x3A 0x29 0x86 0x39 0xB4 0x5D 0x58 0xD7
Field Description
VTP Version Displays the VTP version operating on the switch. By default, the switch
implements version 1 but can be set to version 2.
Configuration Revision Current configuration revision number on this switch.
Maximum VLANs Maximum number of VLANs supported locally.
Supported Locally
Number of Existing Number of existing VLANs.
VLANs
Field Description
VTP Operating Mode Displays the VTP operating mode, which can be server, client, or
transparent.
Server: a switch in VTP server mode is enabled for VTP and sends
advertisements. You can configure VLANs on it. The switch guarantees
that it can recover all the VLAN information in the current VTP database
from nonvolatile RAM (NVRAM) after reboot. By default, every switch
is a VTP server.
Note The switch automatically changes from VTP server mode to VTP
client mode if it detects a failure while writing the configuration
to NVRAM and cannot return to server mode until the NVRAM
is functioning.
Client: a switch in VTP client mode is enabled for VTP, can send
advertisements, but does not have enough nonvolatile storage to store
VLAN configurations. You cannot configure VLANs on it. When a VTP
client starts up, it does not send VTP advertisements until it receives
advertisements to initialize its VLAN database.
Transparent: a switch in VTP transparent mode is disabled for VTP, does
not send or learn from advertisements sent by other devices, and cannot
affect VLAN configurations on other devices in the network. The switch
receives VTP advertisements and forwards them on all trunk ports except
the one on which the advertisement was received.
VTP Domain Name Name that identifies the administrative domain for the switch.
VTP Pruning Mode Displays whether pruning is enabled or disabled. Enabling pruning on a
VTP server enables pruning for the entire management domain. Pruning
restricts flooded traffic to those trunk links that the traffic must use to
access the appropriate network devices.
VTP V2 Mode Displays if VTP version 2 mode is enabled. All VTP version 2 switches
operate in version 1 mode by default. Each VTP switch automatically
detects the capabilities of all the other VTP devices. A network of VTP
devices should be configured to version 2 only if all VTP switches in the
network can operate in version 2 mode.
VTP Traps Generation Displays whether VTP traps are sent to a network management station.
MD5 Digest A 16-byte checksum of the VTP configuration.
Configuration Last Displays the date and time of the last configuration modification.
Modified Displays the IP address of the switch that caused the configuration change
to the database.
shutdown
Use the shutdown interface configuration command on the switch stack or on a standalone switch to
disable an interface. Use the no form of this command to restart a disabled interface.
shutdown
no shutdown
Usage Guidelines The shutdown command for a port causes it to stop forwarding. You can enable the port with the no
shutdown command.
The no shutdown command has no effect if the port is a static-access port assigned to a VLAN that has
been deleted, suspended, or shut down. The port must first be a member of an active VLAN before it can
be re-enabled.
The shutdown command disables all functions on the specified interface.
This command also marks the interface as unavailable. To see if an interface is disabled, use the show
interfaces privileged EXEC command. An interface that has been shut down is shown as
administratively down in the display.
You can verify your settings by entering the show interfaces privileged EXEC command.
shutdown vlan
Use the shutdown vlan global configuration command on the switch stack or on a standalone switch to
shut down (suspend) local traffic on the specified VLAN. Use the no form of this command to restart
local traffic on the VLAN.
Syntax Description vlan-id ID of the VLAN to be locally shut down. The range is 2 to 1001. VLANs defined as
default VLANs under the VLAN Trunking Protocol (VTP), as well as
extended-range VLANs (greater than 1005) cannot be shut down. The default
VLANs are 1 and 1002 to 1005.
Usage Guidelines The shutdown vlan command does not change the VLAN information in the VTP database. It shuts
down traffic locally, but the switch still advertises VTP information.
You can verify your setting by entering the show vlan privileged EXEC command.
snmp-server enable traps [bgp | bridge | cluster | config | copy-config | entity | envmon [fan |
shutdown | supply | temperature] | flash [insertion | removal] | fru-ctrl | hsrp |
mac-notification | port-security [trap-rate value] | rtr | snmp [authentication | coldstart |
linkdown | linkup | warmstart] | stpx | syslog| vlancreate| vlandelete | vlan-membership |
vtp]
no snmp-server enable traps [bgp | bridge | cluster | config | copy-config | entity | envmon [fan
| shutdown | supply | temperature] | flash [insertion | removal] | fru-ctrl | hsrp |
mac-notification | port-security [trap-rate] | rtr | snmp [authentication | coldstart |
linkdown | linkup | warmstart] | stpx | syslog| vlancreate| vlandelete | vlan-membership |
vtp]
Syntax Description bgp (Optional) Enable Border Gateway Protocol (BGP) state change traps.
Note This keyword is available only when the enhanced multilayer image
is installed on the stack master.
bridge (Optional) Generate STP bridge MIB traps.
cluster (Optional) Enable cluster traps.
config (Optional) Enable SNMP configuration traps.
copy-config (Optional) Enable SNMP copy configuration traps.
entity (Optional) Enable SNMP entity traps.
envmon (Optional) Generate environmental monitor traps.
fan (Optional) Generate environmental fan trap.
shutdown (Optional) Generate environmental monitor shutdown traps.
supply (Optional) Generate environmental monitor power supply traps.
temperature (Optional) Generate environmental monitor temperature traps.
flash (Optional) Enable SNMP FLASH notifications.
insertion (Optional) Generate a trap when a switch (flash) is inserted into a stack,
either physically or because of a power cycle or reload.
removal (Optional) Generate a trap when a switch (flash) is removed from a stack,
either physically or because of a power cycle or reload.
fru-ctrl (Optional) Generate entity FRU control traps. In the Catalyst 3750 switch
stack, this trap refers to the insertion or removal of a switch in the stack.
hsrp (Optional) Enable Hot Standby Router Protocol (HSRP) traps.
mac-notification (Optional) Enable MAC address notification traps.
port-security (Optional) Enable SNMP port security traps.
trap-rate value (Optional) Set the maximum number of port-security traps sent per second.
The range is from 0 to 1000; the default is 0 (no limit imposed; a trap is sent
at every occurrence).
Note Though visible in the command-line help strings, the snmp-server enable informs command is not
supported. To enable the sending of SNMP inform notifications, use the snmp-server enable traps
command combined with the snmp-server host host-addr informs command.
Usage Guidelines Specify the host (NMS) that receives the traps by using the snmp-server host global configuration
command. If no trap types are specified, all trap types are sent.
Use the snmp-server enable traps command to enable sending of traps or informs, when supported.
To enable more than one type of trap, you must enter a separate snmp-server enable traps command
for each trap type.
Examples This example shows how to send VTP traps to the NMS:
Switch(config)# snmp-server enable traps vtp
You can verify your setting by entering the show vtp status or the show running-config privileged
EXEC command.
snmp-server host
Use the snmp-server host global configuration command on the switch stack or on a standalone switch to
specify the recipient (host) of a Simple Network Management Protocol (SNMP) notification operation.
Use the no form of this command to remove the specified host.
Syntax Description host-addr Name or Internet address of the host (the targeted recipient).
informs | traps (Optional) Send SNMP traps or informs to this host.
version 1 | 2c | 3 (Optional) Version of the Simple Network Management Protocol (SNMP)
used to send the traps.
These keywords are supported:
1—SNMPv1. This option is not available with informs.
2c—SNMPv2C.
3—SNMPv3. These optional keywords can follow the version 3 keyword:
• auth (Optional). Enables Message Digest 5 (MD5) and Secure Hash
Algorithm (SHA) packet authentication.
• noauth (Default). The noAuthNoPriv security level. This is the default
if the [auth | noauth | priv] keyword choice is not specified.
• priv (Optional). Enables Data Encryption Standard (DES) packet
encryption (also called privacy).
Note The priv keyword is available only when the crypto (encrypted)
software image is installed.
community-string Password-like community string sent with the notification operation. Though
you can set this string by using the snmp-server host command, we
recommend that you define this string by using the snmp-server community
global configuration command before using the snmp-server host
command.
bgp (Optional) Send Border Gateway Protocol (BGP) state change traps.
Note This keyword is available only when the enhanced multilayer image
is installed on the stack master.
bridge (Optional) Send SNMP Spanning Tree Protocol (STP) bridge MIB traps.
cluster (Optional) Send cluster member status traps.
config (Optional) Send SNMP configuration traps.
copy-config (Optional) Send SNMP copy configuration traps.
entity (Optional) Send SNMP entity traps.
envmon (Optional) Generate environmental monitor traps.
Note If the community-string is not defined by using the snmp-server community global configuration
command before using this command, the default form of the snmp-server community command is
automatically inserted into the configuration. The password (community-string) used for this automatic
configuration of the snmp-server community will be the same as that specified in the snmp-server host
command.
Usage Guidelines SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver
does not send acknowledgments when it receives traps. The sender cannot determine if the traps were
received. However, an SNMP entity that receives an inform request acknowledges the message with an
SNMP response PDU. If the sender never receives the response, the inform request can be sent again.
Thus, informs are more likely to reach their intended destinations.
However, informs consume more resources in the agent and in the network. Unlike a trap, which is
discarded as soon as it is sent, an inform request must be held in memory until a response is received or
the request times out. Traps are also sent only once, but an inform might be retried several times. The
retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. To configure the switch to
send SNMP notifications, you must enter at least one snmp-server host command. If you enter the
command with no keywords, all trap types are enabled for the host. To enable multiple hosts, you must
enter a separate snmp-server host command for each host. You can specify multiple notification types
in the command for each host.
When multiple snmp-server host commands are given for the same host and kind of notification (trap
or inform), each succeeding command overwrites the previous command. Only the last snmp-server
host command is in effect. For example, if you enter an snmp-server host inform command for a host
and then enter another snmp-server host inform command for the same host, the second command
replaces the first.
The snmp-server host command is used with the snmp-server enable traps global configuration
command. Use the snmp-server enable traps command to specify which SNMP notifications are sent
globally. For a host to receive most notifications, at least one snmp-server enable traps command and
the snmp-server host command for that host must be enabled. Some notification types cannot be
controlled with the snmp-server enable traps command. For example, some notification types are
always enabled. Other notification types are enabled by a different command.
The no snmp-server host command with no keywords disables traps, but not informs, to the host. To
disable informs, use the no snmp-server host informs command.
Examples This example shows how to configure a unique SNMP community string named comaccess for traps and
prevent SNMP polling access with this string through access-list 10:
Switch(config)# snmp-server community comaccess ro 10
Switch(config)# snmp-server host 172.20.2.160 comaccess
Switch(config)# access-list 10 deny any
This example shows how to send the SNMP traps to the host specified by the name myhost.cisco.com.
The community string is defined as comaccess:
Switch(config)# snmp-server enable traps
Switch(config)# snmp-server host myhost.cisco.com comaccess snmp
This example shows how to enable the switch to send all traps to the host myhost.cisco.com by using the
community string public:
Switch(config)# snmp-server enable traps
Switch(config)# snmp-server host myhost.cisco.com public
You can verify your settings by entering the show running-config privileged EXEC command.
Syntax Description added Enable the MAC notification trap whenever a MAC address is added on this
interface.
removed Enable the MAC notification trap whenever a MAC address is removed from this
interface.
Defaults By default, the traps for both address addition and address removal are disabled.
Usage Guidelines Even though you enable the notification trap for a specific interface by using the snmp trap
mac-notification command, the trap is generated only when you enable the snmp-server enable traps
mac-notification and the mac-address-table notification global configuration commands.
Examples This example shows how to enable the MAC notification trap when a MAC address is added to Gigabit
Ethernet interface1/ 0/4 on stack member 1:
Switch(config)# interface gigabitethernet1/0/4
Switch(config-if)# snmp trap mac-notification added
You can verify your settings by entering the show mac-address-table notification interface privileged
EXEC command.
spanning-tree backbonefast
Use the spanning-tree backbonefast global configuration command on the switch stack or on a
standalone switch to enable the BackboneFast feature. Use the no form of the command to return to the
default setting.
spanning-tree backbonefast
no spanning-tree backbonefast
Usage Guidelines The BackboneFast feature is supported only when the switch is running per-VLAN spanning-tree plus
(PVST+). It is not supported when the switch is operating in the rapid-PVST+ or multiple spanning-tree
(MST) mode.
BackboneFast starts when a root port or blocked port on a switch receives inferior BPDUs from its
designated switch. An inferior BPDU identifies a switch that declares itself as both the root bridge and
the designated switch. When a switch receives an inferior BPDU, it means that a link to which the switch
is not directly connected (an indirect link) has failed (that is, the designated switch has lost its connection
to the root switch. If there are alternate paths to the root switch, BackboneFast causes the maximum
aging time on the ports on which it received the inferior BPDU to expire and allows a blocked port to
move immediately to the listening state. BackboneFast then transitions the interface to the forwarding
state. For more information, refer to the software configuration guide for this release.
Enable BackboneFast on all supported switches to allow the detection of indirect link failures and to start
the spanning-tree reconfiguration sooner.
You can verify your setting by entering the show spanning-tree summary privileged EXEC command.
spanning-tree bpdufilter
Use the spanning-tree bpdufilter interface configuration command on the switch stack or on a
standalone switch to prevent a port from sending or receiving bridge protocol data units (BPDUs). Use
the no form of this command to return to the default setting.
no spanning-tree bpdufilter
Usage Guidelines You can enable the BPDU filtering feature when the switch is operating in the per-VLAN spanning-tree
plus (PVST+), rapid-PVST+, or the multiple spanning-tree (MST) mode.
Caution Enabling BPDU filtering on an interface is the same as disabling spanning tree on it and can result in
spanning-tree loops.
You can globally enable BPDU filtering on all Port Fast-enabled ports by using the spanning-tree
portfast bpdufilter default global configuration command.
You can use the spanning-tree bpdufilter interface configuration command to override the setting of
the spanning-tree portfast bpdufilter default global configuration command.
Examples This example shows how to enable the BPDU filtering feature on a port on stack member 2:
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# spanning-tree bpdufilter enable
You can verify your setting by entering the show running-config privileged EXEC command.
spanning-tree bpduguard
Use the spanning-tree bpduguard interface configuration command on the switch stack or on a
standalone switch to put a port in the error-disabled state when it receives a bridge protocol data unit
(BPDU). Use the no form of this command to return to the default setting.
no spanning-tree bpduguard
Usage Guidelines The BPDU guard feature provides a secure response to invalid configurations because you must
manually put the port back in service. Use the BPDU guard feature in a service-provider network to
prevent a port from being included in the spanning-tree topology.
You can enable the BPDU guard feature when the switch is operating in the per-VLAN spanning-tree
plus (PVST+), rapid-PVST+, or the multiple spanning-tree (MST) mode.
You can globally enable BPDU guard on all Port Fast-enabled ports by using the spanning-tree portfast
bpduguard default global configuration command.
You can use the spanning-tree bpduguard interface configuration command to override the setting of
the spanning-tree portfast bpduguard default global configuration command.
Examples This example shows how to enable the BPDU guard feature on a port on stack member 2:
Switch(config)# interface fastethernet2/0/1
Switch(config-if)# spanning-tree bpduguard enable
You can verify your setting by entering the show running-config privileged EXEC command.
spanning-tree cost
Use the spanning-tree cost interface configuration command on the switch stack or on a standalone
switch to set the path cost for spanning-tree calculations. If a loop occurs, spanning tree considers the
path cost when selecting an interface to place in the forwarding state. Use the no form of this command
to return to the default setting.
Syntax Description vlan vlan-id (Optional) VLAN range associated with a spanning-tree instance. 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.
cost Path cost. The range is 1 to 200000000, with higher values meaning higher costs.
Defaults The default path cost is computed from the interface bandwidth setting. These are the IEEE default path
cost values:
• 1000 Mbps—4
• 100 Mbps—19
• 10 Mbps—100
Usage Guidelines When you configure the cost, higher values represent higher costs.
If you configure an interface with both the spanning-tree vlan vlan-id cost cost command and the
spanning-tree cost cost command, the spanning-tree vlan vlan-id cost cost command takes effect.
Examples This example shows how to set the path cost to 250 on an interface on stack member 2:
Switch(config)# interface fastethernet2/0/4
Switch(config-if)# spanning-tree cost 250
This example shows how to set a path cost to 300 for VLANs 10, 12 to 15, and 20:
Switch(config-if)# spanning-tree vlan 10,12-15,20 cost 300
You can verify your settings by entering the show spanning-tree interface interface-id privileged
EXEC command.
Note Though visible in the command-line help strings, the no version of this command is not supported.
You cannot disable the extended system ID feature.
Usage Guidelines The Catalyst 3750 switch supports the 802.1T spanning-tree extensions. Some of the bits previously
used for the switch priority are now used for the extended system ID (VLAN identifier for the per-VLAN
spanning-tree plus [PVST+] and rapid PVST+ or an instance identifier for the multiple spanning tree
[MST]).
The spanning tree uses the extended system ID, the switch priority, and the allocated spanning-tree MAC
address to make the bridge ID unique for each VLAN or multiple spanning-tree instance. Because the
Catalyst 3750 switch stack appears as a single switch to the rest of the network, all switches in the stack
use the same bridge ID for a given spanning tree. If the stack master fails, the stack members recalculate
their bridge IDs of all running spanning trees based on the new MAC address of the stack master.
Support for the extended system ID affects how you manually configure the root switch, the secondary
root switch, and the switch priority of a VLAN. For more information, see the “spanning-tree mst root”
and the “spanning-tree vlan” sections.
If your network consists of switches that do not support the extended system ID and switches that do
support it, it is unlikely that the switch with the extended system ID support will become the root switch.
The extended system ID increases the switch priority value every time the VLAN number is greater than
the priority of the connected switches.
spanning-tree guard
Use the spanning-tree guard interface configuration command on the switch stack or on a standalone
switch to enable root guard or loop guard on all the VLANs associated with the selected interface. Root
guard restricts which interface is allowed to be the spanning-tree root port or the path-to-the root for the
switch. Loop guard prevents alternate or root ports from becoming designated ports when a failure
creates a unidirectional link. Use the no form of this command to return to the default setting.
no spanning-tree guard
Usage Guidelines You can enable root guard or loop guard when the switch is operating in the per-VLAN spanning-tree
plus (PVST+), rapid-PVST+, or the multiple spanning-tree (MST) mode.
When root guard is enabled, if spanning-tree calculations cause a port to be selected as the root port, the
port transitions to the root-inconsistent (blocked) state to prevent the customer’s switch from becoming
the root switch or being in the path to the root. The root port provides the best path from the switch to
the root switch.
When the no spanning-tree guard or the no spanning-tree guard none command is entered, root guard
is disabled for all VLANs on the selected interface. If this interface is in the root-inconsistent (blocked)
state, it automatically transitions to the listening state.
Do not enable root guard on interfaces that will be used by the UplinkFast feature. With UplinkFast, the
backup interfaces (in the blocked state) replace the root port in the case of a failure. However, if root
guard is also enabled, all the backup interfaces used by the UplinkFast feature are placed in the
root-inconsistent state (blocked) and prevented from reaching the forwarding state. The UplinkFast
feature is not available when the switch is operating in the rapid-PVST+ or MST mode.
Loop guard is most effective when it is configured on the entire switched network. When the switch is
operating in PVST+ or rapid-PVST+ mode, loop guard prevents alternate and root ports from becoming
designated ports, and spanning tree does not send bridge protocol data units (BPDUs) on root or alternate
ports. When the switch is operating in MST mode, BPDUs are not sent on nonboundary ports if the port
is blocked by loop guard in all MST instances. On a boundary port, loop guard blocks the port in all MST
instances.
To disable root guard or loop guard, use the spanning-tree guard none interface configuration
command. You cannot enable both root guard and loop guard at the same time.
You can override the setting of the spanning-tree loopguard default global configuration command by
using the spanning-tree guard loop interface configuration command.
Examples This example shows how to enable root guard on all the VLANs associated with the specified interface
on stack member 2:
Switch(config)# interface fastethernet2/0/3
Switch(config-if)# spanning-tree guard root
This example shows how to enable loop guard on all the VLANs associated with the specified interface
on stack member 2:
Switch(config)# interface fastethernet2/0/3
Switch(config-if)# spanning-tree guard loop
You can verify your settings by entering the show running-config privileged EXEC command.
spanning-tree link-type
Use the spanning-tree link-type interface configuration command on the switch stack or on a
standalone switch to override the default link-type setting, which is determined by the duplex mode of
the port, and to enable rapid spanning-tree transitions to the forwarding state. Use the no form of this
command to return to the default setting.
no spanning-tree link-type
Syntax Description point-to-point Specify that the link type of a port is point-to-point.
shared Specify that the link type of a port is shared.
Defaults The switch derives the link type of a port from the duplex mode. A full-duplex port is considered a
point-to-point link, and a half-duplex port is considered a shared link.
Usage Guidelines You can override the default setting of the link type by using the spanning-tree link-type command; for
example, a half-duplex link can be physically connected point-to-point to a single port on a remote
switch running the Multiple Spanning Tree Protocol (MSTP) or the rapid per-VLAN spanning-tree plus
(rapid-PVST+) protocol and be enabled for rapid transitions.
Examples This example shows how to specify the link type as shared (regardless of the duplex setting) and to
prevent rapid transitions to the forwarding state:
Switch(config-if)# spanning-tree link-type shared
You can verify your setting by entering the show spanning-tree mst interface interface-id or the show
spanning-tree interface interface-id privileged EXEC command.
Usage Guidelines You can enable the loop guard feature when the switch is operating in the per-VLAN spanning-tree plus
(PVST+), rapid-PVST+, or the multiple spanning-tree (MST) mode.
Loop guard is most effective when it is configured on the entire switched network. When the switch is
operating in PVST+ or rapid-PVST+ mode, loop guard prevents alternate and root ports from becoming
designated ports, and spanning tree does not send bridge protocol data units (BPDUs) on root or alternate
ports. When the switch is operating in MST mode, BPDUs are not sent on nonboundary ports if the port
is blocked by loop guard in all MST instances. On a boundary port, loop guard blocks the port in all MST
instances.
Loop guard operates only on ports that are considered point-to-point by the spanning tree.
You can override the setting of the spanning-tree loopguard default global configuration command by
using the spanning-tree guard loop interface configuration command.
You can verify your settings by entering the show running-config privileged EXEC command.
spanning-tree mode
Use the spanning-tree mode global configuration command on the switch stack or on a standalone
switch to enable per-VLAN spanning-tree plus (PVST+), rapid PVST+, or multiple spanning tree (MST)
on your switch. Use the no form of this command to return to the default setting.
no spanning-tree mode
Syntax Description mst Enable MST and Rapid Spanning Tree Protocol (RSTP) (based on IEEE 802.1S and
IEEE 802.1W).
pvst Enable PVST+ (based on IEEE 802.1D).
rapid-pvst Enable rapid PVST+ (based on IEEE 802.1W).
Usage Guidelines The switch supports PVST+, rapid PVST+, and MSTP, but only one version can be active at any time:
All VLANs run PVST+, all VLANs run rapid PVST+, or all VLANs run MSTP. All stack members run
the same version of spanning-tree.
When you enable the MST mode, RSTP is automatically enabled.
Caution Changing spanning-tree modes can disrupt traffic because all spanning-tree instances are stopped for
the previous mode and restarted in the new mode.
Examples This example shows to enable MST and RSTP on the switch:
Switch(config)# spanning-tree mode mst
You can verify your setting by entering the show running-config privileged EXEC command.
Defaults The default mapping is that all VLANs are mapped to the common and internal spanning-tree (CIST)
instance (instance 0).
The default name is an empty string.
The revision number is 0.
Usage Guidelines The spanning-tree mst configuration command enables the MST configuration mode. These
configuration commands are available:
• abort: exits the MST region configuration mode without applying configuration changes.
• exit: exits the MST region configuration mode and applies all configuration changes.
• instance instance-id vlan vlan-range: maps VLANs to an MST instance. The range for the
instance-id is 1 to 15. The range for vlan-range is 1 to 4094. 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.
• name name: sets the configuration name. The name string has a maximum length of 32 characters
and is case sensitive.
• no: negates the instance, name, and revision commands or sets them to their defaults.
• private-vlan: Though visible in the command-line help strings, this command is not supported.
• revision version: sets the configuration revision number. The range is 0 to 65535.
• show [current | pending]: displays the current or pending MST region configuration.
In MST mode, the switch stack supports up to 16 MST instances. The number of VLANs that can be
mapped to a particular MST instance is unlimited.
When you map VLANs to an MST instance, the mapping is incremental, and VLANs specified in the
command are added to or removed from the VLANs that were previously mapped. To specify a range,
use a hyphen; for example, instance 1 vlan 1-63 maps VLANs 1 to 63 to MST instance 1. To specify a
series, use a comma; for example, instance 1 vlan 10, 20, 30 maps VLANs 10, 20, and 30 to MST
instance 1.
All VLANs that are not explicitly mapped to an MST instance are mapped to the common and internal
spanning tree (CIST) instance (instance 0) and cannot be unmapped from the CIST by using the no form
of the command.
For two or more switches to be in the same MST region, they must have the same VLAN mapping, the
same configuration revision number, and the same name.
Examples This example shows how to enter MST configuration mode, map VLANs 10 to 20 to MST instance 1,
name the region region1, set the configuration revision to 1, display the pending configuration, apply the
changes, and return to global configuration mode:
Switch# spanning-tree mst configuration
Switch(config-mst)# instance 1 vlan 10-20
Switch(config-mst)# name region1
Switch(config-mst)# revision 1
Switch(config-mst)# show pending
Pending MST configuration
Name [region1]
Revision 1
Instance Vlans Mapped
-------- ---------------------
0 1-9,21-4094
1 10-20
-------------------------------
Switch(config-mst)# exit
Switch(config)#
This example shows how to add VLANs 1 to 100 to the ones already mapped (if any) to instance 2, to
move VLANs 40 to 60 that were previously mapped to instance 2 to the CIST instance, to add VLAN
10 to instance 10, and to remove all the VLANs mapped to instance 2 and map them to the CIST instance:
Switch(config-mst)# instance 2 vlan 1-100
Switch(config-mst)# no instance 2 vlan 40-60
Switch(config-mst)# instance 10 vlan 10
Switch(config-mst)# no instance 2
You can verify your settings by entering the show pending MST configuration command.
Syntax Description instance-id Range of spanning-tree instances. You can specify a single instance, a range of
instances separated by a hyphen, or a series of instances separated by a comma. The
range is 0 to 15.
cost Path cost is 1 to 200000000, with higher values meaning higher costs.
Defaults The default path cost is computed from the interface bandwidth setting. These are the IEEE default path
cost values:
• 1000 Mbps—20000
• 100 Mbps—200000
• 10 Mbps—2000000
Usage Guidelines When you configure the cost, higher values represent higher costs.
Examples This example shows how to set a path cost of 250 on an interface associated with instances 2 and 4:
Switch(config)# interface gigabitethernet1/0/4
Switch(config-if)# spanning-tree mst 2,4 cost 250
You can verify your settings by entering the show spanning-tree mst interface interface-id privileged
EXEC command.
Syntax Description seconds Length of the listening and learning states. The range is 4 to 30 seconds.
Usage Guidelines Changing the spanning-tree mst forward-time command affects all spanning-tree instances.
Examples This example shows how to set the spanning-tree forwarding time to 18 seconds for all MST instances:
Switch(config)# spanning-tree mst forward-time 18
You can verify your setting by entering the show spanning-tree mst privileged EXEC command.
Syntax Description seconds Interval between hello BPDUs sent by root switch configuration messages. The
range is 1 to 10 seconds.
Usage Guidelines After you set the spanning-tree mst max-age seconds global configuration command, if a switch does
not receive BPDUs from the root switch within the specified interval, the switch recomputes the
spanning-tree topology. The max-age setting must be greater than the hello-time setting.
Changing the spanning-tree mst hello-time command affects all spanning-tree instances.
Examples This example shows how to set the spanning-tree hello time to 3 seconds for all multiple spanning-tree
(MST) instances:
Switch(config)# spanning-tree mst hello-time 3
You can verify your setting by entering the show spanning-tree mst privileged EXEC command.
Syntax Description seconds Interval between messages the spanning tree receives from the root switch. The range is
6 to 40 seconds.
Usage Guidelines After you set the spanning-tree mst max-age seconds global configuration command, if a switch does
not receive BPDUs from the root switch within the specified interval, the switch recomputes the
spanning-tree topology. The max-age setting must be greater than the hello-time setting.
Changing the spanning-tree mst max-age command affects all spanning-tree instances.
Examples This example shows how to set the spanning-tree max-age to 30 seconds for all multiple spanning-tree
(MST) instances:
Switch(config)# spanning-tree mst max-age 30
You can verify your setting by entering the show spanning-tree mst privileged EXEC command.
Syntax Description hop-count Number of hops in a region before the BPDU is discarded. The range is 1 to 40 hops.
Usage Guidelines The root switch of the instance always sends a BPDU (or M-record) with a cost of 0 and the hop count
set to the maximum value. When a switch receives this BPDU, it decrements the received remaining hop
count by one and propagates the decremented count as the remaining hop count in the generated
M-records. A switch discards the BPDU and ages the information held for the port when the count
reaches 0.
Changing the spanning-tree mst max-hops command affects all spanning-tree instances.
Examples This example shows how to set the spanning-tree max-hops to 10 for all multiple spanning-tree (MST)
instances:
Switch(config)# spanning-tree mst max-hops 10
You can verify your setting by entering the show spanning-tree mst privileged EXEC command.
Syntax Description instance-id Range of spanning-tree instances. You can specify a single instance, a range of
instances separated by a hyphen, or a series of instances separated by a comma. The
range is 0 to 15.
priority The range is 0 to 240 in increments of 16. Valid priority values are 0, 16, 32, 48, 64,
80, 96, 112, 128, 144, 160, 176, 192, 208, 224, and 240. All other values are rejected.
The lower the number, the higher the priority.
Usage Guidelines You can assign higher priority values (lower numerical values) to interfaces that you want selected first
and lower priority values (higher numerical values) that you want selected last. If all interfaces have the
same priority value, the multiple spanning tree (MST) puts the interface with the lowest interface number
in the forwarding state and blocks other interfaces.
If your switch is a member of a switch stack, you must use the spanning-tree mst [instance-id] cost cost
interface configuration command instead of the spanning-tree mst [instance vlan-id] port-priority
priority interface configuration command to select an interface to put in the forwarding state. Assign
lower cost values to interfaces that you want selected first and higher cost values to interfaces that you
want selected last.
Examples This example shows how to increase the likelihood that the interface associated with spanning-tree
instances 20 and 22 is placed into the forwarding state if a loop occurs:
Switch(config)# interface gigabitethernet2/0/2
Switch(config-if)# spanning-tree mst 20,22 port-priority 0
You can verify your settings by entering the show spanning-tree mst interface interface-id privileged
EXEC command.
Syntax Description instance-id Range of spanning-tree instances. You can specify a single instance, a range of
instances separated by a hyphen, or a series of instances separated by a comma. The
range is 0 to 15.
priority Set the switch priority for the specified spanning-tree instance. This setting affects
the likelihood that the switch is selected as the root switch. A lower value increases
the probability that the switch is selected as the root switch.
The range is 0 to 61440 in increments of 4096. Valid priority values are 0, 4096,
8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 49152,
53248, 57344, and 61440. All other values are rejected.
Examples This example shows how to set the spanning-tree priority to 8192 for multiple spanning-tree instances
(MST) 20 to 21:
Switch(config)# spanning-tree mst 20-21 priority 8192
You can verify your settings by entering the show spanning-tree mst instance-id privileged EXEC
command.
Syntax Description instance-id Range of spanning-tree instances. You can specify a single instance, a range
of instances separated by a hyphen, or a series of instances separated by a
comma. The range is 0 to 15.
root primary Force this switch to be the root switch.
root secondary Set this switch to be the root switch should the primary root switch fail.
diameter net-diameter (Optional) Set the maximum number of switches between any two end
stations. The range is 2 to 7. This keyword is available only for MST
instance 0.
hello-time seconds (Optional) Set the interval between hello bridge protocol data units
(BPDUs) sent by the root switch configuration messages. The range is 1 to 10
seconds. This keyword is available only for MST instance 0.
Usage Guidelines Use the spanning-tree mst instance-id root command only on backbone switches.
When you enter the spanning-tree mst instance-id root command, the software tries to set a high
enough priority to make this switch the root of the spanning-tree instance. Because of the extended
system ID support, the switch sets the switch priority for the instance to 24576 if this value will cause
this switch to become the root for the specified instance. If any root switch for the specified instance has
a switch priority lower than 24576, the switch sets its own priority to 4096 less than the lowest switch
priority. (4096 is the value of the least-significant bit of a 4-bit switch priority value.)
When you enter the spanning-tree mst instance-id root secondary command, because of support for
the extended system ID, the software changes the switch priority from the default value (32768) to
28672. If the root switch fails, this switch becomes the next root switch (if the other switches in the
network use the default switch priority of 32768 and are therefore unlikely to become the root switch).
Examples This example shows how to configure the switch as the root switch for instance 10 with a network
diameter of 4:
Switch(config)# spanning-tree mst 10 root primary diameter 4
This example shows how to configure the switch as the secondary root switch for instance 10 with a
network diameter of 4:
Switch(config)# spanning-tree mst 10 root secondary diameter 4
You can verify your settings by entering the show spanning-tree mst instance-id privileged EXEC
command.
spanning-tree port-priority
Use the spanning-tree port-priority interface configuration command on the switch stack or on a
standalone switch to configure an interface priority. If a loop occurs, spanning tree can determine which
interface to put in the forwarding state. Use the no form of this command to return to the default setting.
Syntax Description vlan vlan-id (Optional) VLAN range associated with a spanning-tree instance. 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.
priority Number from 0 to 240, in increments of 16. Valid values are 0, 16, 32, 48, 64, 80,
96, 112, 128, 144, 160, 176, 192, 208, 224, and 240. All other values are rejected.
The lower the number, the higher the priority.
Usage Guidelines If the variable vlan-id is omitted, the command applies to the spanning-tree instance associated with
VLAN 1.
You can set the priority on a VLAN that has no interfaces assigned to it. The setting takes effect when
you assign the interface to the VLAN.
If you configure an interface with both the spanning-tree vlan vlan-id port-priority priority command
and the spanning-tree port-priority priority command, the spanning-tree vlan vlan-id port-priority
priority command takes effect.
If your switch is a member of a switch stack, you must use the spanning-tree [vlan vlan-id] cost cost
interface configuration command instead of the spanning-tree [vlan vlan-id] port-priority priority
interface configuration command to select an interface to put in the forwarding state. Assign lower cost
values to interfaces that you want selected first and higher cost values that you want selected last.
Examples This example shows how to increase the likelihood that Fast Ethernet interface 0/2 on stack member 2
will be put in the forwarding state if a loop occurs:
Switch(config)# interface fastethernet2/0/2
Switch(config-if)# spanning-tree vlan 20 port-priority 0
This example shows how to set the port-priority value on VLANs 20 to 25:
Switch(config-if)# spanning-tree vlan 20-25 port-priority 0
You can verify your settings by entering the show spanning-tree interface interface-id privileged
EXEC command.
Syntax Description bpdufilter default Globally enable BPDU filtering on Port Fast-enabled ports and prevent the
switch port connected to end stations from sending or receiving BPDUs.
bpduguard default Globally enable the BPDU guard feature on Port Fast-enabled ports and place
the ports that receive BPDUs in an error-disabled state.
default Globally enable the Port Fast feature on all nontrunking ports. When the Port
Fast feature is enabled, the port changes directly from a blocking state to a
forwarding state without making the intermediate spanning-tree state
changes.
Defaults The BPDU filtering, the BPDU guard, and the Port Fast features are disabled on all ports unless they are
individually configured.
Usage Guidelines You can enable these features when the switch is operating in the per-VLAN spanning-tree plus (PVST+)
rapid-PVST+, or the multiple spanning-tree (MST) mode.
Use the spanning-tree portfast bpdufilter default global configuration command to globally enable
BPDU filtering on ports that are Port Fast-enabled (the ports are in a Port Fast-operational state). The
ports still send a few BPDUs at link-up before the switch begins to filter outbound BPDUs. You should
globally enable BPDU filtering on a switch so that hosts connected to switch ports do not receive
BPDUs. If a BPDU is received on a Port Fast-enabled port, the port loses its Port Fast-operational status
and BPDU filtering is disabled.
You can override the spanning-tree portfast bpdufilter default global configuration command by
using the spanning-tree bdpufilter interface configuration command.
Caution Enabling BPDU filtering on an interface is the same as disabling spanning tree on it and can result in
spanning-tree loops.
Use the spanning-tree portfast bpduguard default global configuration command to globally enable
BPDU guard on ports that are in a Port Fast-operational state. In a valid configuration, Port Fast-enabled
ports do not receive BPDUs. Receiving a BPDU on a Port Fast-enabled port signals an invalid
configuration, such as the connection of an unauthorized device, and the BPDU guard feature puts the
port in the error-disabled state. The BPDU guard feature provides a secure response to invalid
configurations because you must manually put the port back in service. Use the BPDU guard feature in
a service-provider network to prevent an access port from participating in the spanning tree.
You can override the spanning-tree portfast bpduguard default global configuration command by
using the spanning-tree bdpuguard interface configuration command.
Use the spanning-tree portfast default global configuration command to globally enable the Port Fast
feature on all nontrunking ports. Configure Port Fast only on ports that connect to end stations;
otherwise, an accidental topology loop could cause a data packet loop and disrupt switch and network
operation. A Port Fast-enabled port moves directly to the spanning-tree forwarding state when linkup
occurs without waiting for the standard forward-delay time.
You can override the spanning-tree portfast default global configuration command by using the
spanning-tree portfast interface configuration command. You can use the no spanning-tree portfast
default global configuration command to disable Port Fast on all ports unless they are individually
configured with the spanning-tree portfast interface configuration command.
Examples This example shows how to globally enable the BPDU filtering feature:
Switch(config)# spanning-tree portfast bpdufilter default
This example shows how to globally enable the BPDU guard feature:
Switch(config)# spanning-tree portfast bpduguard default
This example shows how to globally enable the Port Fast feature on all nontrunking ports:
Switch(config)# spanning-tree portfast default
You can verify your settings by entering the show running-config privileged EXEC command.
no spanning-tree portfast
Syntax Description disable (Optional) Disable the Port Fast feature on the specified interface.
trunk (Optional) Enable the Port Fast feature on a trunking interface.
Defaults The Port Fast feature is disabled on all interfaces; however, it is automatically enabled on
dynamic-access ports.
Usage Guidelines Use this feature only on interfaces that connect to end stations; otherwise, an accidental topology loop
could cause a data packet loop and disrupt switch and network operation.
You can enable this feature when the switch is operating in the per-VLAN spanning-tree plus (PVST+),
rapid-PVST+, or the multiple spanning-tree (MST) mode.
This feature affects all VLANs on the interface.
A port with the Port Fast feature enabled is moved directly to the spanning-tree forwarding state without
waiting the standard forward-time delay.
You can use the spanning-tree portfast default global configuration command to globally enable the
Port Fast feature on all nontrunking interfaces. However, the spanning-tree portfast interface
configuration command can override the global setting.
If you configure the spanning-tree portfast default global configuration command, you can enable Port
Fast on a port that is not a trunk port by using the no spanning-tree portfast interface configuration
command.
The no spanning-tree portfast interface configuration command is the same as the spanning-tree
portfast disable interface configuration command.
Examples This example shows how to enable the Port Fast feature on an interface on stack member 2:
Switch(config)# interface fastethernet2/0/2
Switch(config-if)# spanning-tree portfast
You can verify your settings by entering the show running-config privileged EXEC command.
spanning-tree uplinkfast
Use the spanning-tree uplinkfast global configuration command on the switch stack or on a standalone
switch to accelerate the choice of a new root port when a link or switch fails or when the spanning tree
reconfigures itself. Use the no form of this command to return to the default setting.
Syntax Description max-update-rate pkts-per-second (Optional) The number of packets per second at which update
packets are sent. The range is 0 to 32000.
Do not enable the root guard on interfaces that will be used by the UplinkFast feature. With UplinkFast,
the backup interfaces (in the blocked state) replace the root port in the case of a failure. However, if root
guard is also enabled, all the backup interfaces used by the UplinkFast feature are placed in the
root-inconsistent state (blocked) and prevented from reaching the forwarding state.
If you set the max-update-rate to 0, station-learning frames are not generated, so the spanning-tree
topology converges more slowly after a loss of connectivity.
You can verify your setting by entering the show spanning-tree summary privileged EXEC command.
spanning-tree vlan
Use the spanning-tree vlan global configuration command on the switch stack or on a standalone switch
to configure spanning tree on a per-VLAN basis. Use the no form of this command to return to the
default setting.
Syntax Description vlan-id VLAN range associated with a spanning-tree instance. 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.
forward-time seconds (Optional) Set the forward-delay time for the specified spanning-tree
instance. The forwarding time determines how long each of the listening
and learning states last before the interface begins forwarding. The range is
4 to 30 seconds.
hello-time seconds (Optional) Set the interval between hello bridge protocol data units
(BPDUs) sent by the root switch configuration messages. The range is 1 to 10
seconds.
max-age seconds (Optional) Set the interval between messages the spanning tree receives
from the root switch. If a switch does not receive a BPDU message from the
root switch within this interval, it recomputes the spanning-tree topology.
The range is 6 to 40 seconds.
priority priority (Optional) Set the switch priority for the specified spanning-tree instance.
This setting affects the likelihood that a standalone switch or a switch in the
stack is selected as the root switch. A lower value increases the probability
that the switch is selected as the root switch.
The range is 0 to 61440 in increments of 4096. Valid priority values are
4096, 8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960,
45056, 49152, 53248, 57344, and 61440. All other values are rejected.
root primary (Optional) Force this switch to be the root switch.
root secondary (Optional) Set this switch to be the root switch should the primary root switch
fail.
diameter net-diameter (Optional) Set the maximum number of switches between any two end
stations. The range is 2 to 7.
Usage Guidelines Disabling the STP causes the VLAN to stop participating in the spanning-tree topology. Interfaces that
are administratively down remain down. Received BPDUs are forwarded like other multicast frames.
The VLAN does not detect and prevent loops when STP is disabled.
You can disable the STP on a VLAN that is not currently active and verify the change by using the show
running-config or the show spanning-tree vlan vlan-id privileged EXEC command. The setting takes
effect when the VLAN is activated.
When disabling or re-enabling the STP, you can specify a range of VLANs that you want to disable or
enable.
When a VLAN is disabled and then enabled, all assigned VLANs continue to be its members. However,
all spanning-tree bridge parameters are returned to their previous settings (the last setting before the
VLAN was disabled).
You can enable spanning-tree options on a VLAN that has no interfaces assigned to it. The setting takes
effect when you assign interfaces to it.
When setting the max-age seconds, if a switch does not receive BPDUs from the root switch within the
specified interval, it recomputes the spanning-tree topology. The max-age setting must be greater than
the hello-time setting.
The spanning-tree vlan vlan-id root command should be used only on backbone switches.
When you enter the spanning-tree vlan vlan-id root command, the software checks the switch priority
of the current root switch for each VLAN. Because of the extended system ID support, the switch sets
the switch priority for the specified VLAN to 24576 if this value will cause this switch to become the
root for the specified VLAN. If any root switch for the specified VLAN has a switch priority lower than
24576, the switch sets its own priority for the specified VLAN to 4096 less than the lowest switch
priority. (4096 is the value of the least-significant bit of a 4-bit switch priority value.)
When you enter the spanning-tree vlan vlan-id root secondary command, because of support for the
extended system ID, the software changes the switch priority from the default value (32768) to 28672.
If the root switch should fail, this switch becomes the next root switch (if the other switches in the
network use the default switch priority of 32768, and therefore, are unlikely to become the root switch).
You can verify your setting by entering the show spanning-tree privileged EXEC command. In this
instance, VLAN 5 does not appear in the list.
This example shows how to set the spanning-tree forwarding time to 18 seconds for VLANs 20 and 25:
Switch(config)# spanning-tree vlan 20,25 forward-time 18
This example shows how to set the spanning-tree hello-delay time to 3 seconds for VLANs 20 to 24:
Switch(config)# spanning-tree vlan 20-24 hello-time 3
This example shows how to set spanning-tree max-age to 30 seconds for VLAN 20:
Switch(config)# spanning-tree vlan 20 max-age 30
This example shows how to reset the max-age parameter to the default value for spanning-tree instance
100 and 105 to 108:
Switch(config)# no spanning-tree vlan 100, 105-108 max-age
This example shows how to set the spanning-tree priority to 8192 for VLAN 20:
Switch(config)# spanning-tree vlan 20 priority 8192
This example shows how to configure the switch as the root switch for VLAN 10 with a network
diameter of 4:
Switch(config)# spanning-tree vlan 10 root primary diameter 4
This example shows how to configure the switch as the secondary root switch for VLAN 10 with a
network diameter of 4:
Switch(config)# spanning-tree vlan 10 root secondary diameter 4
You can verify your settings by entering the show spanning-tree vlan vlan-id privileged EXEC
command.
speed
Use the speed interface configuration command on the switch stack or on a standalone switch to specify
the speed of a 10/100 Mbps or 10/100/1000 Mbps port. Use the no or default form of this command to
return the port to its default value.
no speed
Note You cannot configure speed on small form-factor pluggable (SFP) module ports, but you can configure
speed to not negotiate (nonegotiate) if they are connected to a device that does not support
autonegotiation. See “Usage Guidelines” for exceptions when a 1000BASE-T SFP module is in the SFP
module port.
Usage Guidelines You can configure the Fast Ethernet port speed as either 10 or 100 Mbps. You can configure the Gigabit
Ethernet port speed as 10, 100, or 1000 Mbps. You cannot configure speed on SFP module ports, but you
can configure speed to not negotiate (nonegotiate) if connected to a device that does not support
autonegotiation. However, when a 1000BASE-T SFP module is in the SFP module port, you can
configure speed as 10, 100, or 1000 Mbps.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed
setting and then forces the speed setting to the negotiated value. The duplex setting remains as
configured on each end of the link, which could result in a duplex setting mismatch.
If both ends of the line support autonegotiation, we highly recommend the default autonegotiation
settings. If one interface supports autonegotiation and the other end does not, do use the auto setting on
the supported side, but set the duplex and speed on both interfaces.
For 10/100/1000 Mbps ports, if both the speed and duplex are set to specific values, autonegotiation is
disabled.
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.
Caution Changing the interface speed and duplex mode configuration might shut down and re-enable the
interface during the reconfiguration.
Note For guidelines on setting the switch speed and duplex parameters, refer to the software configuration
guide for this release.
Examples This example shows how to set the specified interface to 100 Mbps:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# speed 100
You can verify your settings by entering the show interfaces privileged EXEC command.
Syntax Description weight1 Percentage of the port speed to which the port should be limited. The range is 10 to 90.
Defaults The port is not rate limited and is set to 100 percent.
Usage Guidelines If you configure this command to 80 percent, the port is idle 20 percent of the time. The line rate drops
to 80 percent of the connected speed. These values are not exact because the hardware adjusts the line
rate in increments of six.
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Examples This example shows how to limit Gigabit Ethernet port 0/1 on stack member 2 to 800 Mbps:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# srr-queue bandwidth limit 80
You can verify your settings by entering the show mls qos interface [interface-id] queueing privileged
EXEC command.
Syntax Description weight1 weight2 Specify the weights to determine the percentage of the port that is shaped. The
weight3 weight4 inverse ratio (1/weight) determines the shaping bandwidth for this queue.
Separate each value with a space. The range is 0 to 65535.
Defaults Weight1 is set to 25. Weight2, weight3, and weight4 are set to 0, and these queues are in shared mode.
Usage Guidelines In shaped mode, the queues are guaranteed a percentage of the bandwidth, and they are rate-limited to
that amount. Shaped traffic does not use more than the allocated bandwidth even if the link is idle. Use
shaping to smooth bursty traffic or to provide a smoother output over time.
The shaped mode overrides the shared mode.
If you configure a shaped queue weight to 0 by using the srr-queue bandwidth shape interface
configuration command, this queue participates in shared mode. The weight specified with the
srr-queue bandwidth shape command is ignored, and the weights specified with the srr-queue
bandwidth share interface configuration command for a queue come into effect.
When configuring queues for the same port for both shaping and sharing, make sure that you configure
the lowest numbered queue for shaping.
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Examples This example shows how to configure the queues for the same port for both shaping and sharing. Because
the weight ratios for queues 2, 3, and 4 are set to 0, these queues operate in shared mode. The bandwidth
weight for queue 1 is 1/8, which is 12.5 percent. Queue 1 is guaranteed this bandwidth and limited to it;
it does not extend its slot to the other queues even if the other queues have no traffic and are idle. Queues
2, 3, and 4 are in shared mode, and the setting for queue 1 is ignored. The bandwidth ratio allocated for
the queues in shared mode is 4/(4+4+4), which is 33 percent:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# srr-queue bandwidth shape 8 0 0 0
Switch(config-if)# srr-queue bandwidth share 4 4 4 4
You can verify your settings by entering the show mls qos interface [interface-id] queueing privileged
EXEC command.
Syntax Description weight1 weight2 The ratios of weight1, weight2, weight3, and weight4 determine the ratio of the
weight3 weight4 frequency in which the SRR scheduler dequeues packets. Separate each value
with a space. The range is 1 to 255.
Defaults Weight1, weight2, weight3, and weight4 are 25 (1/4 of the bandwidth is allocated to each queue).
Usage Guidelines The absolute value of each weight is meaningless, and only the ratio of parameters is used.
In shared mode, the queues share the bandwidth among them according to the configured weights. The
bandwidth is guaranteed at this level but not limited to it. For example, if a queue empties and does not
require a share of the link, the remaining queues can expand into the unused bandwidth and share it
among themselves.
If you configure a shaped queue weight to 0 by using the srr-queue bandwidth shape interface
configuration command, this queue participates in SRR shared mode. The weight specified with the
srr-queue bandwidth shape command is ignored, and the weights specified with the srr-queue
bandwidth share interface configuration command for a queue take effect.
When configuring queues for the same port for both shaping and sharing, make sure that you configure
the lowest numbered queue for shaping.
Note The egress queue default settings are suitable for most situations. You should change them only when
you have a thorough understanding of the egress queues and if these settings do not meet your QoS
solution.
Examples This example shows how to configure the weight ratio of the SRR scheduler running on egress port
Gigabit Ethernet 0/1 on stack member 2. Four queues are used. The bandwidth ratio allocated for each
queue in shared mode is 1/(1+2+3+4), 2/(1+2+3+4), 3/(1+2+3+4), and 4/(1+2+3+4), which is
10 percent, 20 percent, 30 percent, and 40 percent for queues 1, 2, 3, and 4. This means that queue 4 has
four times the bandwidth of queue 1, twice the bandwidth of queue 2, and one-and-a-third times the
bandwidth of queue 3.
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# srr-queue bandwidth share 1 2 3 4
You can verify your settings by entering the show mls qos interface [interface-id] queueing privileged
EXEC command.
storm-control
Use the storm-control interface configuration command on the switch stack or on a standalone switch to
enable broadcast, multicast, or unicast storm control on an interface with the specified threshold level.
Use the no form of this command to disable broadcast, multicast, or unicast storm control on an
interface.
Usage Guidelines Storm control is supported only on physical interfaces; it is not supported on EtherChannel port
channels, even though it is available in the command-line interface (CLI).
Storm-control suppression level is entered as a percentage of total bandwidth. A threshold value of
100 percent means that no limit is placed on the specified traffic type. A value of 0.0 means that all
broadcast, multicast, or unicast traffic on that port is blocked.
When the storm control threshold for multicast traffic is reached, all multicast traffic except control
traffic, such as bridge protocol data unit (BDPU) and Cisco Discovery Protocol (CDP) frames, are
blocked. However, the switch does not differentiate between routing updates, such as Open Shortest Path
First (OSPF) and regular multicast data traffic, so both types of traffic are blocked.
Note For more information about storm control suppression levels, refer to the software configuration guide
for this release.
Examples This example shows how to enable multicast storm control with a 75.5 percent threshold level:
Switch(config-if)# storm-control multicast level 75.5
You can verify your settings by entering the show storm-control privileged EXEC command.
switch priority
Use the switch priority global configuration command on the stack master to change the stack member
priority value.
Syntax Description priority new-priority-value Specify the new stack member priority value. The range is 1 to 15.
stack-member-number Specify the current stack member number. The range 1 to 9.
Usage Guidelines If you do not specify a priority value, the default value is assigned.
The new priority value is a factor during a stack-master re-election. Therefore, changing the priority
value does not change the stack master immediately.
Use the reload slot current stack member number privileged EXEC to reset the stack member and apply
this configuration change into effect.
Examples This example shows how to change the priority value of stack member 6 to 9:
Switch(config)# switch 6 priority 9
Changing the Switch Priority of Switch Number 6 to 9
Do you want to continue?[confirm]
switch renumber
Use the switch renumber global configuration command on the stack master to change the stack
member number.
Syntax Description renumber Specify the new stack member number for the stack member. The
new-stack-member-number range is 1 to 9.
current-stack-member-number Specify the current stack member number. The range is 1 to 9.
Usage Guidelines If another stack member is already using the member number that you just specified, the stack master
assigns the lowest available number when you reset the stack member.
Note If you change the number of a stack member, and no configuration is associated with the new stack
member number, that stack member loses its current configuration and resets to its default configuration.
For more information about stack member numbers and configurations, see the software configuration
guide.
Use the reload slot current stack member number privileged EXEC to reset the stack member and apply
this configuration change into effect.
Examples This example shows how to change the member number of stack member 6 to 7:
Switch(config)# switch 6 renumber 7
WARNING: Changing the switch number may result in lost
or changed configuration for that switch!
Do you want to continue?[confirm]
switchport
Use the switchport interface configuration command with no keywords on the switch stack or on a
standalone switch to put an interface that is in Layer 3 mode into Layer 2 mode for Layer 2 configuration.
Use the no form of this command to put an interface in Layer 3 mode.
switchport
no switchport
Use the no switchport command (without parameters) to set the interface to the routed-interface status
and to erase all Layer 2 configurations. You must use this command before assigning an IP address to a
routed port.
Note If an interface is configured as a Layer 3 interface, you must first enter this switchport command with
no keywords to configure the interface as a Layer 2 port. Then you can enter additional switchport
commands with keywords, as shown on the pages that follow.
Usage Guidelines Entering the no switchport command shuts the port down and then re-enables it, which might generate
messages on the device to which the port is connected.
Examples This example shows how to cause an interface to cease operating as a Layer 2 port and become a
Cisco-routed port.
Switch(config-if)# no switchport
This example shows how to cause the port interface to cease operating as a Cisco-routed port and convert
to a Layer 2-switched interface:
Switch(config-if)# switchport
Note The switchport command without keywords is not used on platforms that do not support Cisco-routed
ports. All physical ports on such platforms are assumed to be Layer 2-switched interfaces.
You can verify the switchport status of an interface by entering the show running-config privileged
EXEC command.
switchport access
Use the switchport access interface configuration command on the switch stack or on a standalone switch
to configure a port as a static-access or dynamic-access port. If the switchport mode is set to access, the
port operates as a member of the specified VLAN. If set to dynamic, the port starts discovery of VLAN
assignment based on the incoming packets it receives. Use the no form of this command to reset the
access mode to the default VLAN for the switch.
Syntax Description vlan vlan-id Configure the interface as a static access port with the VLAN ID of the
access mode VLAN; the range is 1 to 4094.
vlan dynamic Specify that the access mode VLAN is dependent on the VLAN Membership
Policy Server (VMPS) protocol. The port is assigned to a VLAN based on
the source MAC address of a host (or hosts) connected to the port. The switch
sends every new MAC address received to the VMPS server to obtain the
VLAN name to which the dynamic-access port should be assigned. If the port
already has a VLAN assigned and the source has already been approved by
the VMPS, the switch forwards the packet to the VLAN.
Defaults The default access VLAN and trunk interface native VLAN is a default VLAN corresponding to the
platform or interface hardware.
A dynamic-access port is initially a member of no VLAN and receives its assignment based on the packet
it receives.
Usage Guidelines The no switchport access command resets the access mode VLAN to the appropriate default VLAN for
the device.
The port must be in access mode before the switchport access vlan command can take effect.
An access port can be assigned to only one VLAN.
The VMPS server (such as a Catalyst 6000 series switch) must be configured before a port is configured
as dynamic.
Examples This example shows how to cause a port interface that has already been configured as a switched
interface to operate in VLAN 2 instead of the platform’s default VLAN when in access mode:
Switch(config-if)# switchport access vlan 2
You can verify your setting by entering the show interfaces interface-id switchport privileged EXEC
command and examining information in the Administrative Mode and Operational Mode rows.
switchport block
Use the switchport block interface configuration command on the switch stack or on a standalone switch
to prevent unknown multicast or unicast packets from being forwarded. Use the no form of this command
to allow forwarding unknown multicast or unicast packets.
Syntax Description multicast Specify that unknown multicast traffic should be blocked.
unicast Specify that unknown unicast traffic should be blocked.
Usage Guidelines By default, all traffic with unknown MAC addresses is sent to all ports. You can block unknown multicast
or unicast traffic on protected or nonprotected ports. If unknown multicast or unicast traffic is not
blocked on a protected port, there could be security issues.
Blocking unknown multicast or unicast traffic is not automatically enabled on protected ports; you must
explicitly configure it.
Note For more information about blocking packets, refer to the software configuration guide for this release.
Examples This example shows how to block unknown multicast traffic on an interface:
Switch(config-if)# switchport block multicast
You can verify your setting by entering the show interfaces interface-id switchport privileged EXEC
command.
switchport host
Use the switchport host interface configuration command on the switch stack or on a standalone switch
to optimize a Layer 2 port for a host connection. The no form of this command has no affect on the
system.
switchport host
Defaults The default is for the port to not be optimized for a host connection.
Usage Guidelines To optimize the port for a host connection, the switchport host command sets switch port mode to
access, enables spanning tree Port Fast, and disables channel grouping. Only an end station can accept
this configuration.
Because spanning tree Port Fast is enabled, you should enter the switchport host command only on ports
that are connected to a single host. Connecting other switches, hubs, concentrators, or bridges to a
fast-start port can cause temporary spanning-tree loops.
Enable the switchport host command to decrease the time that it takes to start up packet forwarding.
Examples This example shows how to optimize the port configuration for a host connection:
Switch(config-if)# switchport host
switchport mode will be set to access
spanning-tree portfast will be enabled
channel group will be disabled
Switch(config-if)#
You can verify your setting by entering the show interfaces interface-id switchport privileged EXEC
command.
switchport mode
Use the switchport mode interface configuration command on the switch stack or on a standalone switch
to configure the VLAN membership mode of a port. Use the no form of this command to reset the mode
to the appropriate default for the device.
Syntax Description access Set the port to access mode (either static-access or dynamic-access depending
on the setting of the switchport access vlan interface configuration command).
The port is set to access unconditionally and operates as a nontrunking, single
VLAN interface that sends and receives nonencapsulated (non-tagged) frames.
An access port can be assigned to only one VLAN.
dynamic auto Set the interface trunking mode dynamic parameter to auto to specify that the
interface convert the link to a trunk link. This is the default switchport mode.
dynamic desirable Set the interface trunking mode dynamic parameter to desirable to specify that
the interface actively attempt to convert the link to a trunk link.
trunk Set the port to trunk unconditionally. The port is a trunking VLAN Layer-2
interface. The port sends and receives encapsulated (tagged) frames that
identify the VLAN of origination. A trunk is a point-to-point link between two
switches or between a switch and a router.
Usage Guidelines A configuration that uses the access or trunk keywords takes effect only when you configure the port in
the appropriate mode by using the switchport mode command. The static-access and trunk
configuration are saved, but only one configuration is active at a time.
When you enter access mode, the interface changes to permanent nontrunking mode and negotiates to
convert the link into a nontrunk link even if the neighboring interface does not agree to the change.
When you enter trunk mode, the interface changes to permanent trunking mode and negotiates to
convert the link into a trunk link even if the interface connecting to it does not agree to the change.
When you enter dynamic auto mode, the interface converts the link to a trunk link if the neighboring
interface is set to trunk or desirable mode.
When you enter dynamic desirable mode, the interface becomes a trunk interface if the neighboring
interface is set to trunk, desirable, or auto mode.
To autonegotiate trunking, the interfaces must be in the same VTP domain. Trunk negotiation is managed
by the Dynamic Trunking Protocol (DTP), which is a point-to-point protocol. However, some
internetworking devices might forward DTP frames improperly, which could cause misconfigurations.
To avoid this, you should configure interfaces connected to devices that do not support DTP to not
forward DTP frames, which turns off DTP.
• If you do not intend to trunk across those links, use the switchport mode access interface
configuration command to disable trunking.
• To enable trunking to a device that does not support DTP, use the switchport mode trunk and
switchport nonegotiate interface configuration commands to cause the interface to become a trunk
but to not generate DTP frames.
Access port and trunk ports are mutually exclusive.
The 802.1X feature interacts with switchport modes in these ways:
• If you try to enable 802.1X on a trunk port, an error message appears, and 802.1X is not enabled. If
you try to change the mode of an 802.1X-enabled port to trunk, the port mode is not changed.
• If you try to enable 802.1X on a port set to dynamic auto or dynamic desirable, an error message
appears, and 802.1X is not enabled. If you try to change the mode of an 802.1X-enabled port to
dynamic auto or dynamic desirable, the port mode is not changed.
• If you try to enable 802.1X on a dynamic-access (VLAN Query Protocol [VQP]) port, an error
message appears, and 802.1X is not enabled. If you try to change an 802.1X-enabled port to dynamic
VLAN assignment, an error message appears, and the VLAN configuration is not changed.
Examples This example shows how to configure a port for access mode:
Switch(config-if)# switchport mode access
This example shows how set the interface to dynamic desirable mode:
Switch(config-if)# switchport mode dynamic desirable
You can verify your settings by entering the show interfaces interface-id switchport privileged EXEC
command and examining information in the Administrative Mode and Operational Mode rows.
switchport nonegotiate
Use the switchport nonegotiate interface configuration command on the switch stack or on a standalone
switch to specify that Dynamic Trunking Protocol (DTP) negotiation packets are not sent on the Layer 2
interface. The switch does not engage in DTP negotiation on this interface. Use the no form of this
command to return to the default setting.
switchport nonegotiate
no switchport nonegotiate
Usage Guidelines The no form of the switchport nonegotiate command removes nonegotiate status.
This command is valid only when the interface switchport mode is access or trunk (configured by using
the switchport mode access or the switchport mode trunk interface configuration command). This
command returns an error if you attempt to execute it in dynamic (auto or desirable) mode.
Internetworking devices that do not support DTP might forward DTP frames improperly and cause
misconfigurations. To avoid this, you should turn off DTP by using the switchport no negotiate
command to configure the interfaces connected to devices that do not support DTP to not forward DTP
frames.
When you enter the switchport nonegotiate command, DTP negotiation packets are not sent on the
interface. The device does or does not trunk according to the mode parameter: access or trunk.
• If you do not intend to trunk across those links, use the switchport mode access interface
configuration command to disable trunking.
• To enable trunking on a device that does not support DTP, use the switchport mode trunk and
switchport nonegotiate interface configuration commands to cause the interface to become a trunk
but to not generate DTP frames.
Examples This example shows how to cause a port interface to refrain from negotiating trunking mode and to act
as a trunk or access port (depending on the mode set):
Switch(config-if)# switchport nonegotiate
You can verify your setting by entering the show interfaces interface-id switchport privileged EXEC
command.
switchport port-security
Use the switchport port-security interface configuration command without keywords on the switch
stack or on a standalone switch to enable port security on the interface. Use the keywords to configure
secure MAC addresses, sticky MAC address learning, a maximum number of secure MAC addresses, or
the violation mode. Use the no form of this command to disable port security or to set the parameters to
their default states.
Syntax Description aging (Optional) See the switchport port-security aging command.
mac-address mac-address (Optional) Specify a secure MAC address for the interface by entering
a 48-bit MAC address. You can add additional secure MAC addresses
up to the maximum value configured.
vlan vlan-id (Optional) On a trunk port only, specify the VLAN ID and the MAC
address. If no VLAN ID is specified, the native VLAN is used.
mac-address sticky (Optional) Enable the interface for sticky learning by entering only the
[mac-address] mac-address sticky keywords. When sticky learning is enabled, the
interface adds all secure MAC addresses that are dynamically learned to
the running configuration and converts these addresses to sticky secure
MAC addresses.
(Optional) Enter a mac-address to specify a sticky secure MAC address.
maximum value (Optional) Set the maximum number of secure MAC addresses for the
interface.The maximum number of secure MAC addresses that you can
configure on a switch stack is determined by the maximum number of
available MAC addresses allowed in the system. This number is
determined by the active Switch Database Management (SDM)
template. See the sdm prefer command. This number represents the
total of available MAC addresses, including those used for other Layer
2 functions and any other secure MAC addresses configured on
interfaces.
The default setting is 1.
vlan [vlan-list] (Optional) For trunk ports, you can set the maximum number of secure
MAC addresses on a VLAN. If the vlan keyword is not entered, the
default value is used.
• vlan—set a per-VLAN maximum value.
• vlan vlan-list—set a per-VLAN maximum value on a range of
VLANs separated by a hypen or a series of VLANs separated by
commas. For nonspecified VLANs, the per-VLAN maximum value
is used.
violation (Optional) Set the security violation mode or the action to be taken if
port security is violated. The default is shutdown.
protect Set the security violation protect mode. In this mode, when the number
of port secure MAC addresses reaches the maximum limit allowed on
the port, packets with unknown source addresses are dropped until you
remove a sufficient number of secure MAC addresses to drop below the
maximum value or increase the number of maximum allowable
addresses. You are not notified that a security violation has occurred.
Note We do not recommend configuring the protect mode on a trunk
port. The protect mode disables learning when any VLAN
reaches its maximum limit, even if the port has not reached its
maximum limit.
restrict Set the security violation restrict mode. In this mode, when the number
of secure MAC addresses reaches the limit allowed on the port, packets
with unknown source addresses are dropped until you remove a
sufficient number of secure MAC addresses or increase the number of
maximum allowable addresses. An SNMP trap is sent, a syslog message
is logged, and the violation counter increments.
shutdown Set the security violation shutdown mode. In this mode, the interface is
error-disabled when a violation occurs and the port LED turns off. An
SNMP trap is sent, a syslog message is logged, and the violation counter
increments. When a secure port is in the error-disabled state, you can
bring it out of this state by entering the errdisable recovery cause
psecure-violation global configuration command, or you can manually
re-enable it by entering the shutdown and no shut down interface
configuration commands.
• A secure port cannot belong to a Fast EtherChannel or Gigabit EtherChannel port group.
• You cannot configure static secure or sticky secure MAC addresses in the voice VLAN.
• When you enable port security on an interface that is also configured with a voice VLAN, you must
set the maximum allowed secure addresses on the port to two plus the maximum number of secure
addresses allowed on the access VLAN. When the port is connected to a Cisco IP phone, the Cisco
IP phone requires up to two MAC addresses. The Cisco IP phone address is learned on the voice
VLAN and might also be learned on the access VLAN. Connecting a PC to the Cisco IP phone
requires additional MAC addresses.
• If any type of port security is enabled on the access VLAN, dynamic port security is automatically
enabled on the voice VLAN. You cannot configure port security on a per-VLAN basis.
Note Voice VLAN is supported only on access ports and not on trunk ports.
• When a voice VLAN is configured on a secure port that is also configured as a sticky secure port,
all addresses on the voice VLAN are learned as dynamic secure addresses, and all addresses seen on
the access VLAN to which the port belongs are learned as sticky secure addresses.
• You cannot configure static secure MAC addresses in the voice VLAN.
• When you enter a maximum secure address value for an interface, if the new value is greater than
the previous value, the new value overrides the previously configured value. If the new value is less
than the previous value and the number of configured secure addresses on the interface exceeds the
new value, the command is rejected.
• The switch does not support port security aging of sticky secure MAC addresses.
A security violation occurs when the maximum number of secure MAC addresses are in the address table
and a station whose MAC address is not in the address table attempts to access the interface, or when a
station whose MAC address is configured as a secure MAC address on another secure port attempts to
access the interface.
If you enable port security on a voice VLAN port and if there is a PC connected to the IP phone, you
should set the maximum allowed secure addresses on the port to more than 1.
When a secure port is in the error-disabled state, you can bring it out of this state by entering the
errdisable recovery cause psecure-violation global configuration command, or you can manually
re-enable it by entering the shutdown and no shut down interface configuration commands.
Setting a maximum number of addresses to one and configuring the MAC address of an attached device
ensures that the device has the full bandwidth of the port.
When you enter a maximum secure address value for an interface, this occurs:
• If the new value is greater than the previous value, the new value overrides the previously configured
value.
• If the new value is less than the previous value and the number of configured secure addresses on
the interface exceeds the new value, the command is rejected.
Sticky secure MAC addresses have these characteristics:
• When you enable sticky learning on an interface by using the switchport port-security
mac-address sticky interface configuration command, the interface converts all the dynamic secure
MAC addresses, including those that were dynamically learned before sticky learning was enabled,
to sticky secure MAC addresses and adds all sticky secure MAC addresses to the running
configuration.
• If you disable sticky learning by using the no switchport port-security mac-address sticky
interface configuration command or the running configuration is removed, the sticky secure MAC
addresses remain part of the running configuration but are removed from the address table. The
addresses that were removed can be dynamically reconfigured and added to the address table as
dynamic addresses.
• When you configure sticky secure MAC addresses by using the switchport port-security
mac-address sticky mac-address interface configuration command, these addresses are added to the
address table and the running configuration. If port security is disabled, the sticky secure MAC
addresses remain in the running configuration.
• If you save the sticky secure MAC addresses in the configuration file, when the switch restarts or
the interface shuts down, the interface does not need to relearn these addresses. If you do not save
the sticky secure addresses, they are lost. If sticky learning is disabled, the sticky secure MAC
addresses are converted to dynamic secure addresses and are removed from the running
configuration.
• If you disable sticky learning and enter the switchport port-security mac-address sticky
mac-address interface configuration command, an error message appears, and the sticky secure
MAC address is not added to the running configuration.
Examples This example shows how to enable port security on Gigabit Ethernet port 12 on stack member 2 and to
set the maximum number of secure addresses to 5. The violation mode is the default, and no secure MAC
addresses are configured.
Switch(config)# interface gigahitethernet 2/0/12
Switch(config-if)# switchport mode access
Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security maximum 5
This example shows how to configure a secure MAC address and a VLAN ID on Gigabit Ethernet port
12 on stack member 2.
Switch(config)# interface gigabitethernet 2/0/12
Switch(config-if)# switchport mode trunk
Switch(config-if)# switchport port-security
Switch(config-if)# switchport port-security mac-address 1000.2000.3000 vlan 3
This example shows how to enable sticky learning and to enter two sticky secure MAC addresses:
Switch(config-if)# switchport port-security mac-address sticky
Switch(config-if)# switchport port-security mac-address sticky 0000.0000.4141
Switch(config-if)# switchport port-security mac-address sticky 0000.0000.000f
You can verify your settings by using the show port-security privileged EXEC command.
Syntax Description static Enable aging for statically configured secure addresses on this port.
time time Specify the aging time for this port. The range is 0 to 1440 minutes. If the time
is 0, aging is disabled for this port.
type Set the aging type.
absolute Set absolute aging type. All the secure addresses on this port age out exactly after
the time (minutes) specified and are removed from the secure address list.
inactivity Set the inactivity aging type. The secure addresses on this port age out only if there
is no data traffic from the secure source address for the specified time period.
Defaults The port security aging feature is disabled. The default time is 0 minutes.
The default aging type is absolute.
The default static aging behavior is disabled.
Usage Guidelines To enable secure address aging for a particular port, set the aging time to a value other than 0 for that
port.
To allow limited time access to particular secure addresses, set the aging type as absolute. When the
aging time lapses, the secure addresses are deleted.
To allow continuous access to a limited number of secure addresses, set the aging type as inactivity. This
removes the secure address when it become inactive, and other addresses can become secure.
To allow unlimited access to a secure address, configure it as a secure address, and disable aging for the
statically configured secure address by using the no switchport port-security aging static interface
configuration command.
Examples This example sets the aging time as 2 hours for absolute aging for all the secure addresses on Gigabit
Ethernet interface 0/1 on stack member 1.
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# switchport port-security aging time 120
This example sets the aging time as 2 minutes for inactivity aging type with aging enabled for configured
secure addresses on Gigabit Ethernet interface 0/2 on stack member 1.
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# switchport port-security aging time 2
Switch(config-if)# switchport port-security aging type inactivity
Switch(config-if)# switchport port-security aging static
This example shows how to disable aging for configured secure addresses.
Switch(config-if)# no switchport port-security aging static
Syntax Description cos value Set the IP phone port to override the 802.1P priority received from the PC or the
attached device with the specified class of service (CoS) value. The range is 0 to 7.
Seven is the highest priority. The default is 0.
trust Set the IP phone port to trust the 802.1P priority received from the PC or the attached
device.
Defaults The default port priority is set to a CoS value of 0 for untagged frames received on the port.
Usage Guidelines When voice VLAN is enabled, you can configure the switch to send the Cisco Discovery Protocol (CDP)
packets to instruct the IP phone how to send data packets from the device attached to the access port on
the Cisco IP Phone. You must enable CDP on the switch port connected to the Cisco IP Phone to send
the configuration to the Cisco IP Phone. (CDP is enabled by default globally and on all switch
interfaces.)
You should configure voice VLAN on switch access ports. You can only configure a voice VLAN on
Layer 2 ports.
Before you enable voice VLAN, we recommend that you enable quality of service (QoS) on the switch
by entering the mls qos global configuration command and configure the port trust state to trust by
entering the mls qos trust cos interface configuration command.
Examples This example shows how to configure the IP phone connected to the specified port to trust the received
802.1P priority:
Switch(config-if)# switchport priority extend trust
You can verify your settings by entering the show interfaces interface-id switchport privileged EXEC
command.
switchport protected
Use the switchport protected interface configuration command on the switch stack or on a standalone
switch to isolate unicast, multicast, and broadcast traffic at Layer 2 from other protected ports on the
same switch. Use the no form of this command to disable protection on the port.
switchport protected
no switchport protected
Usage Guidelines The switchport protection feature is local to the switch; communication between protected ports on the
same switch is possible only through a Layer 3 device. To prevent communication between protected
ports on different switches, you must configure the protected ports for unique VLANs on each switch
and configure a trunk link between the switches. A protected port is different from a secure port.
A protected port does not forward any unicast, multicast, or broadcast traffic to any other protected port.
A protected port continues to forward unicast, multicast, and broadcast traffic to unprotected ports and
vice versa.
Because a switch stack represents a single logical switch, Layer 2 traffic is not forwarded between any
protected ports in the switch stack, whether they are on the same or different switches in the stack.
Port monitoring does not work if both the monitor and monitored ports are protected ports.
You can verify your settings by entering the show interfaces interface-id switchport privileged EXEC
command.
switchport trunk
Use the switchport trunk interface configuration command on the switch stack or on a standalone switch
to set the trunk characteristics when the interface is in trunking mode. Use the no form of this command
to reset a trunking characteristic to the default.
Syntax Description allowed vlan vlan-list Set the list of allowed VLANs that can receive and send traffic on this
interface in tagged format when in trunking mode. See the following vlan-list
format. The none keyword is not valid. The default is all.
encapsulation dot1q Set the encapsulation format on the trunk port to 802.1Q. With this format,
the switch supports simultaneous tagged and untagged traffic on a port.
encapsulation isl Set the encapsulation format on the trunk port to Inter-Switch Link (ISL).
The switch encapsulates all received and sent packets with an ISL header and
filters native frames received from an ISL trunk port.
encapsulation Specify that if Dynamic Inter-Switch Link (DISL) and Dynamic Trunking
negotiate Protocol (DTP) negotiation do not resolve the encapsulation format, ISL is
the selected format.
native vlan vlan-id Set the native VLAN for sending and receiving untagged traffic when the
interface is in 802.1Q trunking mode. The range is 1 to 4094.
pruning vlan vlan-list Set the list of VLANs that are eligible for VTP pruning when in trunking
mode. The all keyword is not valid.
The vlan-list format is all | none | [add | remove | except] vlan-atom [,vlan-atom...] where:
• all specifies all VLANs from 1 to 4094. This keyword is not allowed on commands that do not
permit all VLANs in the list to be set at the same time.
• none means an empty list. This keyword is not allowed on commands that require certain VLANs
to be set or at least one VLAN to be set.
• add adds the defined list of VLANs to those currently set instead of replacing the list. Valid IDs are
from 1 to 1005; extended-range VLANs (VLAN IDs greater than 1005) are valid in some cases.
Note You can add extended-range VLANs to the allowed VLAN list, but not to the
pruning-eligible VLAN list.
Separate nonconsecutive VLAN IDs with a comma; use a hyphen to designate a range of IDs.
• remove removes the defined list of VLANs from those currently set instead of replacing the list.
Valid IDs are from 1 to 1005; extended-range VLAN IDs are valid in some cases.
Note You can remove extended-range VLANs from the allowed VLAN list, but you cannot
remove them from the pruning-eligible list.
Separate nonconsecutive VLAN IDs with a comma; use a hyphen to designate a range of IDs.
• except lists the VLANs that should be calculated by inverting the defined list of VLANs. (VLANs
are added except the ones specified.) Valid IDs are from 1 to 1005. Separate nonconsecutive VLAN
IDs with a comma; use a hyphen to designate a range of IDs.
• vlan-atom is either a single VLAN number from 1 to 4094 or a continuous range of VLANs
described by two VLAN numbers, the lesser one first, separated by a hyphen.
Native VLANs:
• All untagged traffic received on an 802.1Q trunk port is forwarded with the native VLAN configured
for the port.
• If a packet has a VLAN ID that is the same as the sending-port native VLAN ID, the packet is sent
without a tag; otherwise, the switch sends the packet with a tag.
• The no form of the native vlan command resets the native mode VLAN to the appropriate default
VLAN for the device.
Allowed VLAN:
• To reduce the risk of spanning-tree loops or storms, you can disable VLAN 1 on any individual
VLAN trunk port by removing VLAN 1 from the allowed list. When you remove VLAN 1 from a
trunk port, the interface continues to send and receive management traffic, for example, Cisco
Discovery Protocol (CDP), Port Aggregation Protocol (PAgP), Link Aggregation Control Protocol
(LACP), Dynamic Trunking Protocol (DTP), and VLAN Trunking Protocol (VTP) in VLAN 1.
• The no form of the allowed vlan command resets the list to the default list, which allows all VLANs.
Trunk pruning:
• The pruning-eligible list applies only to trunk ports.
• Each trunk port has its own eligibility list.
• If you do not want a VLAN to be pruned, remove it from the pruning-eligible list. VLANs that are
pruning-ineligible receive flooded traffic.
• VLAN 1, VLANs 1002 to 1005, and extended-range VLANs (VLANs 1006 to 4094) cannot be
pruned.
Examples This example shows how to cause a port interface configured as a switched interface to encapsulate in
802.1Q trunking format regardless of its default trunking format in trunking mode:
Switch(config-if)# switchport trunk encapsulation dot1q
This example shows how to configure VLAN 3 as the default port to send all untagged traffic:
Switch(config-if)# switchport trunk native vlan 3
This example shows how to add VLANs 1, 2, 5, and 6 to the allowed list:
Switch(config-if)# switchport trunk allowed vlan add 1,2,5,6
This example shows how to remove VLANs 3 and 10 to 15 from the pruning-eligible list:
Switch(config-if)# switchport trunk pruning vlan remove 3,10-15
You can verify your settings by entering the show interfaces interface-id switchport privileged EXEC
command.
Syntax Description vlan-id Specify the VLAN to be used for voice traffic. The range is 1 to 4094. By default, the
IP phone forwards the voice traffic with an 802.1Q priority of 5.
dot1p Configure the telephone to use 802.1P priority tagging and uses VLAN 0 (the native
VLAN). By default, the Cisco IP phone forwards the voice traffic with an 802.1P
priority of 5.
none Do not instruct the IP telephone about the voice VLAN. The telephone uses the
configuration from the telephone key pad.
untagged Configure the telephone to send untagged voice traffic. This is the default for the
telephone.
Defaults The switch default is not to automatically configure the telephone (none).
The telephone default is not to tag frames.
Usage Guidelines You should configure voice VLAN on Layer 2 access ports.
You must enable Cisco Discovery Protocol (CDP) on the switchport connected to the Cisco IP phone for
the switch to send configuration information to the phone. CDP is enabled by default globally and on the
interface.
Before you enable voice VLAN, we recommend you enable quality of service (QoS) on the switch by
entering the mls qos global configuration command and configure the port trust state to trust by entering
the mls qos trust cos interface configuration command.
When you enter a VLAN ID, the IP phone forwards voice traffic in 802.1Q frames, tagged with the
specified VLAN ID. The switch puts 802.1Q voice traffic in the voice VLAN.
When you select dot1q, none, or untagged, the switch puts the indicated voice traffic in the access
VLAN.
In all configurations, the voice traffic carries a Layer 2 IP precedence value. The default is 5 for voice
traffic.
When you enable port security on an interface that is also configured with a voice VLAN, you must set
the maximum allowed secure addresses on the port to at least two. When the port is connected to a Cisco
IP phone, the IP phone requires two MAC addresses: one for the access VLAN and the other for the voice
VLAN. Connecting a PC to the IP phone requires additional MAC addresses.
If any type of port security is enabled on the access VALN, dynamic port security is automatically
enabled on the voice VLAN.
You cannot configure static secure MAC addresses in the voice VLAN.
The Port Fast feature is automatically enabled when voice VLAN is configured. When you disable voice
VLAN, the Port Fast feature is not automatically disabled.
Examples This example shows how to configure VLAN 2 as the voice VLAN:
Switch(config-if)# switchport voice vlan 2
You can verify your settings by entering the show interfaces interface-id switchport privileged EXEC
command.
system mtu
Use the system global configuration command on the switch stack or on a standalone switch to set the
maximum packet size or maximum transmission unit (MTU) size for Gigabit Ethernet ports or for Fast
Ethernet (10/100) ports. Use the no form of this command to restore the global MTU value to its default
value.
no system mtu
Syntax Description bytes Set the system MTU for Fast Ethernet (10/100) ports. The range is 1500 to
1546 bytes.
jumbo bytes Set the system jumbo frame size (MTU) for Gigabit Ethernet ports. The
range is 1500 to 9000 bytes.
Defaults The default MTU size for all ports is 1500 bytes.
Usage Guidelines When you use this command to change the MTU size, you must reset the switch before the new
configuration takes effect.
Gigabit Ethernet ports are not affected by the system mtu command; Fast Ethernet ports are not affected
by the system mtu jumbo command.
If you enter a value that is outside the range for the specific type of switch, the value is not accepted.
Note The switch does not support setting the MTU on a per-interface basis.
The size of frames that can be received by the switch CPU is limited to 1500 bytes, no matter what value
was entered with the system mtu command. Although frames that are forwarded or routed typically are
not received by the CPU, in some cases packets are sent to the CPU, such as traffic sent to control traffic,
SNMP, Telnet, or routing protocols.
Examples This example shows how to set the maximum packet size for Gigabit Ethernet ports to 1800 bytes:
Switch(config)# system mtu jumbo 1800
Switch(config)# exit
Switch# reload
You can verify your setting by entering the show system mtu privileged EXEC command.
traceroute mac
Use the traceroute mac privileged EXEC command on the switch stack or on a standalone switch to
display the Layer 2 path taken by the packets from the specified source MAC address to the specified
destination MAC address.
Syntax Description interface interface-id (Optional) Specify an interface on the source or destination switch.
source-mac-address Specify the MAC address of the source switch in hexadecimal format.
destination-mac-address Specify the MAC address of the destination switch in hexadecimal format.
vlan vlan-id (Optional) Specify the VLAN on which to trace the Layer 2 path that the
packets take from the source switch to the destination switch. Valid VLAN
IDs are from 1 to 4094.
detail (Optional) Specify that detailed information appears.
Layer 2 traceroute supports only unicast traffic. If you specify a multicast source or destination MAC
address, the physical path is not identified, and an error message appears.
The traceroute mac command output shows the Layer 2 path when the specified source and destination
addresses belong to the same VLAN. If you specify source and destination addresses that belong to
different VLANs, the Layer 2 path is not identified, and an error message appears.
If the source or destination MAC address belongs to multiple VLANs, you must specify the VLAN to
which both the source and destination MAC addresses belong. If the VLAN is not specified, the path is
not identified, and an error message appears.
The Layer 2 traceroute feature is not supported when multiple devices are attached to one port through
hubs (for example, multiple CDP neighbors are detected on a port). When more than one CDP neighbor
is detected on a port, the Layer 2 path is not identified, and an error message appears.
This feature is not supported in Token Ring VLANs.
Examples This example shows how to display the Layer 2 path by specifying the source and destination MAC
addresses:
Switch# traceroute mac 0000.0201.0601 0000.0201.0201
This example shows how to display the Layer 2 path by using the detail keyword:
Switch# traceroute mac 0000.0201.0601 0000.0201.0201 detail
Source 0000.0201.0601 found on con6[WS-C3750-12T] (2.2.6.6)
con6 / WS-C3750-12T / 2.2.6.6 :
Gi0/0/2 [auto, auto] => Gi0/0/3 [auto, auto]
con5 / WS-C2950G-24-EI / 2.2.5.5 :
Fa0/3 [auto, auto] => Gi0/1 [auto, auto]
con1 / WS-C3550-12G / 2.2.1.1 :
Gi0/1 [auto, auto] => Gi0/2 [auto, auto]
con2 / WS-C3550-24 / 2.2.2.2 :
Gi0/2 [auto, auto] => Fa0/1 [auto, auto]
Destination 0000.0201.0201 found on con2[WS-C3550-24] (2.2.2.2)
Layer 2 trace completed.
This example shows how to display the Layer 2 path by specifying the interfaces on the source and
destination switches:
Switch# traceroute mac interface fastethernet0/1 0000.0201.0601 interface fastethernet0/3
0000.0201.0201
Source 0000.0201.0601 found on con6[WS-C3750-12T] (2.2.6.6)
con6 (2.2.6.6) :Gi0/0/1 => Gi0/0/3
con5 (2.2.5.5 ) : Gi0/0/3 => Gi0/0/1
con1 (2.2.1.1 ) : Gi0/0/1 => Gi0/0/2
con2 (2.2.2.2 ) : Gi0/0/2 => Gi0/0/1
Destination 0000.0201.0201 found on con2[WS-C3550-24] (2.2.2.2)
Layer 2 trace completed
This example shows the Layer 2 path when the switch is not connected to the source switch:
Switch# traceroute mac 0000.0201.0501 0000.0201.0201 detail
Source not directly connected, tracing source .....
Source 0000.0201.0501 found on con5[WS-C3750-12T] (2.2.5.5)
con5 / WS-C3750-12T / 2.2.5.5 :
Gi0/0/1 [auto, auto] => Gi0/0/3 [auto, auto]
con1 / WS-C3550-12G / 2.2.1.1 :
Gi0/1 [auto, auto] => Gi0/2 [auto, auto]
con2 / WS-C3550-24 / 2.2.2.2 :
Gi0/2 [auto, auto] => Fa0/1 [auto, auto]
Destination 0000.0201.0201 found on con2[WS-C3550-24] (2.2.2.2)
Layer 2 trace completed.
This example shows the Layer 2 path when the switch cannot find the destination port for the source
MAC address:
Switch# traceroute mac 0000.0011.1111 0000.0201.0201
Error:Source Mac address not found.
Layer2 trace aborted.
This example shows the Layer 2 path when the source and destination devices are in different VLANs:
Switch# traceroute mac 0000.0201.0601 0000.0301.0201
Error:Source and destination macs are on different vlans.
Layer2 trace aborted.
This example shows the Layer 2 path when the destination MAC address is a multicast address:
Switch# traceroute mac 0000.0201.0601 0100.0201.0201
Invalid destination mac address
This example shows the Layer 2 path when source and destination switches belong to multiple VLANs:
Switch# traceroute mac 0000.0201.0601 0000.0201.0201
Error:Mac found on multiple vlans.
Layer2 trace aborted.
traceroute mac ip
Use the traceroute mac ip privileged EXEC command on the switch stack or on a standalone switch to
display the Layer 2 path taken by the packets from the specified source IP address or hostname to the
specified destination IP address or hostname.
Syntax Description source-ip-address Specify the IP address of the source switch as a 32-bit quantity in
dotted-decimal format.
destination-ip-address Specify the IP address of the destination switch as a 32-bit quantity in
dotted-decimal format.
source-hostname Specify the IP hostname of the source switch.
destination-hostname Specify the IP hostname of the destination switch.
detail (Optional) Specify that detailed information appears.
The traceroute mac ip command output shows the Layer 2 path when the specified source and
destination IP addresses are in the same subnet. When you specify the IP addresses, the switch uses
Address Resolution Protocol (ARP) to associate the IP addresses with the corresponding MAC addresses
and the VLAN IDs.
• If an ARP entry exists for the specified IP address, the switch uses the associated MAC address and
identifies the physical path.
• If an ARP entry does not exist, the switch sends an ARP query and tries to resolve the IP address.
The IP addresses must be in the same subnet. If the IP address is not resolved, the path is not
identified, and an error message appears.
The Layer 2 traceroute feature is not supported when multiple devices are attached to one port through
hubs (for example, multiple CDP neighbors are detected on a port). When more than one CDP neighbor
is detected on a port, the Layer 2 path is not identified, and an error message appears.
This feature is not supported in Token Ring VLANs.
Examples This example shows how to display the Layer 2 path by specifying the source and destination IP
addresses and by using the detail keyword:
Switch# traceroute mac ip 2.2.66.66 2.2.22.22 detail
Translating IP to mac .....
2.2.66.66 => 0000.0201.0601
2.2.22.22 => 0000.0201.0201
This example shows how to display the Layer 2 path by specifying the source and destination hostnames:
Switch# traceroute mac ip con6 con2
Translating IP to mac .....
2.2.66.66 => 0000.0201.0601
2.2.22.22 => 0000.0201.0201
This example shows the Layer 2 path when ARP cannot associate the source IP address with the
corresponding MAC address:
Switch# traceroute mac ip 2.2.66.66 2.2.77.77
Arp failed for destination 2.2.77.77.
Layer2 trace aborted.
trust
Use the trust policy-map class configuration command on the switch stack or on a standalone switch to
define a trust state for traffic classified through the class policy-map configuration or the class-map
global configuration command. Use the no form of this command to return to the default setting.
Syntax Description cos (Optional) Classify an ingress packet by using the packet class of service (CoS)
value. For an untagged packet, the port default CoS value is used.
dscp (Optional) Classify an ingress packet by using the packet Differentiated Services
Code Point (DSCP) values (most significant 6 bits of 8-bit service-type field). For
a non-IP packet, the packet CoS value is used if the packet is tagged. If the packet
is untagged, the default port CoS value is used to map CoS to DSCP.
ip-precedence (Optional) Classify an ingress packet by using the packet IP-precedence value
(most significant 3 bits of 8-bit service-type field). For a non-IP packet, the packet
CoS value is used if the packet is tagged. If the packet is untagged, the port default
CoS value is used to map CoS to DSCP.
Defaults The action is not trusted. If no keyword is specified when the command is entered, the default is dscp.
Usage Guidelines Use this command to distinguish the quality of service (QoS) trust behavior for certain traffic from other
traffic. For example, incoming traffic with certain DSCP values can be trusted. You can configure a class
map to match and trust the DSCP values in the incoming traffic.
Trust values set with this command supersede trust values set with the mls qos trust interface
configuration command.
The trust command is mutually exclusive with set policy-map class configuration command within the
same policy map.
If you specify trust cos, QoS uses the received or default port CoS value and the CoS-to-DSCP map to
generate a DSCP value for the packet.
If you specify trust dscp, QoS uses the DSCP value from the ingress packet. For non-IP packets that are
tagged, QoS uses the received CoS value; for non-IP packets that are untagged, QoS uses the default port
CoS value. In either case, the DSCP value for the packet is derived from the CoS-to-DSCP map.
If you specify trust ip-precedence, QoS uses the IP precedence value from the ingress packet and the
IP-precedence-to-DSCP map. For non-IP packets that are tagged, QoS uses the received CoS value; for
non-IP packets that are untagged, QoS uses the default port CoS value. In either case, the DSCP for the
packet is derived from the CoS-to-DSCP map.
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 define a port trust state to trust incoming DSCP values for traffic classified
with class1:
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
Syntax Description aggressive Enable UDLD in aggressive mode on all fiber-optic interfaces.
enable Enable UDLD in normal mode on all fiber-optic interfaces.
message time Configure the period of time between UDLD probe messages on ports that
message-timer-interval are in the advertisement phase and are determined to be bidirectional. The
range is 7 to 90 seconds.
Usage Guidelines In normal mode, if UDLD is in the advertisement or in the detection phase and all the neighbor cache
entries are aged out, UDLD restarts the link-up sequence to try to resynchronize with any potentially
out-of-sync neighbors.
If you enable aggressive mode, when all the neighbors of a port have aged out either in the advertisement
or in the detection phase, UDLD restarts the link-up sequence to resynchronize with any potentially
out-of-sync neighbor. UDLD shuts down the port if, after the fast train of messages, the link state is still
undetermined. Use aggressive mode on point-to-point links where no failure between two neighbors is
allowed. In this situation, UDLD probe packets can be considered as a heart beat whose presence
guarantees the health of the link. Conversely, the link must be shut down if it is not possible to
re-establish a bidirectional link.
If you change the message time between probe packets, you are making a trade-off between the detection
speed and the CPU load. By decreasing the time, you can make the detection-response faster but increase
the load on the CPU.
This command affects fiber-optic interfaces only. Use the udld interface configuration command to
enable UDLD on other interface types.
Examples This example shows how to enable UDLD on all fiber-optic interfaces:
Switch(config)# udld enable
You can verify your setting by entering the show udld privileged EXEC command.
Syntax Description aggressive Enable UDLD in aggressive mode on the specified interface.
disable Disable UDLD on the specified interface. This keyword applies only to
fiber-optic interfaces.
enable Enable UDLD in normal mode on the specified interface.
Defaults On fiber-optic interfaces, UDLD is not enabled, in aggressive mode, or disabled. For this reason,
fiber-optic interfaces enable UDLD according to the state of the udld enable or udld aggressive global
configuration command.
On nonfiber-optic interfaces, UDLD is disabled.
Usage Guidelines A UDLD-capable port cannot detect a unidirectional link if it is connected to a UDLD-incapable port of
another switch.
In normal mode, if UDLD is in the advertisement or in the detection phase and all the neighbor cache
entries are aged out, UDLD restarts the link-up sequence to try to resynchronize with any potentially
out-of-sync neighbors.
If you enable aggressive mode, after all the neighbors of a port have aged out either in the advertisement
or in the detection phase, UDLD restarts the link-up sequence to resynchronize with any potentially
out-of-sync neighbor. UDLD disables the port if, after the fast train of messages, the link state is still
undetermined. Use aggressive mode on point-to-point links where no failure between two neighbors is
allowed. In this situation, UDLD probe packets can be considered as a heart beat whose presence
guarantees the health of the link. Conversely, the loss of the heart beat that the link must be shut down
if it is not possible to re-establish a bidirectional link.
Use the no udld enable command on fiber-optic ports to return control of UDLD to the udld enable
global configuration command or to disable UDLD on nonfiber-optic ports.
Use the udld aggressive command on fiber-optic ports to override the setting of the udld enable or udld
aggressive global configuration command. Use the no form on fiber-optic ports to remove this setting
and to return control of UDLD enabling to the udld global configuration command or to disable UDLD
on nonfiber-optic ports.
The disable keyword is supported on fiber-optic ports only. Use the no form of this command to remove
this setting and to return control of UDLD to the udld global configuration command.
If the switch software detects a GBIC module change and the port changes from fiber optic to nonfiber
optic or vice versa, all configurations are maintained.
Examples This example shows how to enable UDLD on an port 11 of stack member 6:
Switch(config)# interface gigabitethernet6/0/11
Switch(config-if)# udld enable
This example shows how to disable UDLD on a fiber-optic interface despite the setting of the udld
global configuration command:
Switch(config)# interface gigabitethernet6/0/11
Switch(config-if)# udld disable
You can verify your settings by entering the show running-config or the show udld interface privileged
EXEC command.
udld reset
Use the udld reset privileged EXEC command to reset all interfaces disabled by the UniDirectional Link
Detection (UDLD) and permit traffic to begin passing through them again (though other features, such
as spanning tree, Port Aggregation Protocol (PAgP), and Dynamic Trunking Protocol (DTP) still have
their normal effects, if enabled).
udld reset
Usage Guidelines If the interface configuration is still enabled for UDLD, these ports begin to run UDLD again and are
disabled for the same reason if the problem has not been corrected.
Examples This example shows how to reset all interfaces disabled by UDLD:
Switch# udld reset
1 ports shutdown by UDLD were reset.
You can verify your setting by entering the show udld privileged EXEC command.
vlan vlan-id
no vlan vlan-id
Syntax Description vlan-id ID of the VLAN to be added and configured. For vlan-id, the range is 1 to 4094. You
can enter a single VLAN ID, a series of VLAN IDs separated by commas, or a range
of VLAN IDs separated by hyphens.
Usage Guidelines You must use the vlan vlan-id global configuration command to add extended-range VLANs (VLAN IDs
1006 to 4094). Before configuring VLANs in the extended range, you must use the vtp transparent
global configuration or VLAN configuration command to put the switch in VTP transparent mode.
Extended-range VLANs are not learned by VTP and are not added to the VLAN database, but when VTP
mode is transparent, VTP mode and domain name and all VLAN configurations are saved in the running
configuration, and you can save them in the switch startup configuration file.
When you save the VLAN and VTP configurations in the startup configuration file and reboot the switch,
the configuration is determined in these ways:
• If both the VLAN database and the configuration file show the VTP mode as transparent and the
VTP domain names match, the VLAN database is ignored. The VTP and VLAN configurations in
the startup configuration file are used. The VLAN database revision number remains unchanged in
the VLAN database.
• If the VTP mode is server, or if the startup VTP mode or domain names do not match the VLAN
database, the VTP mode and the VLAN configuration for the first 1005 VLANs use the VLAN
database information.
If you try to create an extended-range VLAN when the switch is not in VTP transparent mode, the VLAN
is rejected, and you receive an error message.
If you enter an invalid VLAN ID, you receive an error message and do not enter config-vlan mode.
Entering the vlan command with a VLAN ID enables config-vlan mode. When you enter the VLAN ID
of an existing VLAN, you do not create a new VLAN, but you can modify VLAN parameters for that
VLAN. The specified VLANs are added or modified when you exit the config-vlan mode. Only the
shutdown command (for VLANs 1 to 1005) takes effect immediately.
These configuration commands are available in config-vlan mode. The no form of each command returns
the characteristic to its default state.
Note Although all commands are visible, the only config-vlan command supported on extended-range VLANs
is mtu mtu-size. For extended-range VLANs, all other characteristics must remain at the default state.
• are are-number: defines the maximum number of all-routes explorer (ARE) hops for this VLAN.
This keyword applies only to TrCRF VLANs.The range is 0 to 13. The default is 7. If no value is
entered, 0 is assumed to be the maximum.
• backupcrf: specifies the backup CRF mode. This keyword applies only to TrCRF VLANs.
– enable backup CRF mode for this VLAN.
– disable backup CRF mode for this VLAN (the default).
• bridge {bridge-number| type}: specifies the logical distributed source-routing bridge, the bridge
that interconnects all logical rings having this VLAN as a parent VLAN in FDDI-NET, Token
Ring-NET, and TrBRF VLANs. The range is 0 to 15. The default bridge number is 0 (no
source-routing bridge) for FDDI-NET, TrBRF, and Token Ring-NET VLANs. The type keyword
applies only to TrCRF VLANs and is one of these:
– srb (source-route bridging)
– srt (source-route transparent) bridging VLAN
• exit: applies changes, increments the VLAN database revision number (VLANs 1 to 1005 only), and
exits config-vlan mode.
• media: defines the VLAN media type. See Table 2-28 for valid commands and syntax for different
media types.
Note The switch supports only Ethernet ports. You configure only FDDI and Token Ring
media-specific characteristics for VLAN Trunking Protocol (VTP) global advertisements to
other switches. These VLANs are locally suspended.
• name vlan-name: names the VLAN with an ASCII string from 1 to 32 characters that must be unique
within the administrative domain. The default is VLANxxxx where xxxx represents four numeric
digits (including leading zeros) equal to the VLAN ID number.
• no: negates a command or returns it to the default setting.
• parent parent-vlan-id: specifies the parent VLAN of an existing FDDI, Token Ring, or TrCRF
VLAN. This parameter identifies the TrBRF to which a TrCRF belongs and is required when
defining a TrCRF. The range is 0 to 1005. The default parent VLAN ID is 0 (no parent VLAN) for
FDDI and Token Ring VLANs. For both Token Ring and TrCRF VLANs, the parent VLAN ID must
already exist in the database and be associated with a Token Ring-NET or TrBRF VLAN.
Note Though visible in the command-line interface, the private-vlan command is not supported.
• remote-span: configure the VLAN as a Remote SPAN (RSPAN) VLAN. When the RSPAN feature
is added to an existing VLAN, the VLAN is first deleted and is then recreated with the RSPAN
feature. Any access ports are deactivated until the RSPAN feature is removed. If VTP is enabled, the
new RSPAN VLAN is propagated by VTP for VLAN-IDs that are lower than 1024. Learning is
disabled on the VLAN. See the remote-span command for more information.
• ring ring-number: defines the logical ring for an FDDI, Token Ring, or TrCRF VLAN. The range is
1 to 4095. The default for Token Ring VLANs is 0. For FDDI VLANs, there is no default.
• said said-value: specifies the security association identifier (SAID) as documented in IEEE 802.10.
The range is 1 to 4294967294, and the number must be unique within the administrative domain.
The default value is 100000 plus the VLAN ID number.
• shutdown: shuts down VLAN switching on the VLAN. This command takes effect immediately.
Other commands take effect when you exit config-vlan mode.
• state: specifies the VLAN state:
– active means the VLAN is operational (the default).
– suspend means the VLAN is suspended. Suspended VLANs do not pass packets.
• ste ste-number: defines the maximum number of spanning-tree explorer (STE) hops. This keyword
applies only to TrCRF VLANs. The range is 0 to 13. The default is 7.
• stp type: defines the spanning-tree type for FDDI-NET, Token Ring-NET, or TrBRF VLANs. For
FDDI-NET VLANs, the default STP type is ieee. For Token Ring-NET VLANs, the default STP
type is ibm. For FDDI and Token Ring VLANs, the default is no type specified.
– ieee for IEEE Ethernet STP running source-route transparent (SRT) bridging.
– ibm for IBM STP running source-route bridging (SRB).
– auto for STP running a combination of source-route transparent bridging (IEEE) and
source-route bridging (IBM).
• tb-vlan1 tb-vlan1-id and tb-vlan2 tb-vlan2-id: specifies the first and second VLAN to which this
VLAN is translationally bridged. Translational VLANs translate FDDI or Token Ring to Ethernet,
for example. The range is 0 to 1005. If no value is specified, 0 (no transitional bridging) is assumed.
Table 2-28 Valid Commands and Syntax for Different Media Types
Configuration Rule
VTP v2 mode is enabled, and you Specify a parent VLAN ID of a TrBRF that already exists in the
are configuring a TrCRF VLAN database.
media type. Specify a ring number. Do not leave this field blank.
Specify unique ring numbers when TrCRF VLANs have the same
parent VLAN ID. Only one backup concentrator relay function
(CRF) can be enabled.
VTP v2 mode is enabled, and you Do not specify a backup CRF.
are configuring VLANs other than
TrCRF media type.
VTP v2 mode is enabled, and you Specify a bridge number. Do not leave this field blank.
are configuring a TrBRF VLAN
media type.
VTP v1 mode is enabled. No VLAN can have an STP type set to auto.
This rule applies to Ethernet, FDDI, FDDI-NET, Token Ring, and
Token Ring-NET VLANs.
Add a VLAN that requires The translational bridging VLAN IDs that are used must already
translational bridging (values are exist in the database.
not set to zero). The translational bridging VLAN IDs that a configuration points
to must also contain a pointer to the original VLAN in one of the
translational bridging parameters (for example, Ethernet points to
FDDI, and FDDI points to Ethernet).
The translational bridging VLAN IDs that a configuration points
to must be different media types than the original VLAN (for
example, Ethernet can point to Token Ring).
If both translational bridging VLAN IDs are configured, these
VLANs must be different media types (for example, Ethernet can
point to FDDI and Token Ring).
Examples This example shows how to add an Ethernet VLAN with default media characteristics. The default
includes a vlan-name of VLANxxx, where xxxx represents four numeric digits (including leading zeros)
equal to the VLAN ID number. The default media option is ethernet; the state option is active. The
default said-value variable is 100000 plus the VLAN ID; the mtu-size variable is 1500; the stp-type
option is ieee. When you enter the exit config-vlan configuration command, the VLAN is added if it did
not already exist; otherwise, this command does nothing.
This example shows how to create a new VLAN with all default characteristics and enter config-vlan
mode:
Switch(config)# vlan 200
Switch(config-vlan)# exit
Switch(config)#
This example shows how to create a new extended-range VLAN with all the default characteristics, to
enter config-vlan mode, and to save the new VLAN in the switch startup configuration file:
Switch(config)# vtp mode transparent
Switch(config)# vlan 2000
Switch(config-vlan)# end
Switch# copy running-config startup config
You can verify your setting by entering the show vlan privileged EXEC command.
Extended-range VLANs (with VLAN IDs from 1006 to 4094) cannot be added or modified by using
these commands. To add extended-range VLANs, use the vlan (global configuration) command to enter
config-vlan mode.
Note The switch supports only Ethernet ports. You configure only FDDI and Token Ring media-specific
characteristics for VLAN Trunking Protocol (VTP) global advertisements to other switches. These
VLANs are locally suspended.
Syntax Description vlan-id ID of the configured VLAN. The range is 1 to 1005 and must be unique
within the administrative domain. Do not enter leading zeros.
are are-number (Optional) Specify the maximum number of all-routes explorer (ARE)
hops for this VLAN. This keyword applies only to TrCRF VLANs. The
range is 0 to 13. If no value is entered, 0 is assumed to be the maximum.
backupcrf {enable | disable} (Optional) Specify the backup CRF mode. This keyword applies only
to TrCRF VLANs.
• enable backup CRF mode for this VLAN.
• disable backup CRF mode for this VLAN.
bridge bridge-number| (Optional) Specify the logical distributed source-routing bridge, the
type {srb | srt} bridge that interconnects all logical rings having this VLAN as a parent
VLAN in FDDI-NET, Token Ring-NET, and TrBRF VLANs.
The range is 0 to 15.
The type keyword applies only to TrCRF VLANs and is one of these:
• srb (source-route bridging)
• srt (source-route transparent) bridging VLAN
media {ethernet | fddi | (Optional) Specify the VLAN media type. Table 2-30 lists the valid
fd-net | tokenring | tr-net} syntax for each media type.
• ethernet is Ethernet media type (the default).
• fddi is FDDI media type.
• fd-net is FDDI network entity title (NET) media type.
• tokenring is Token Ring media type if the VTP v2 mode is
disabled, or TrCRF if the VTP v2 mode is enabled.
• tr-net is Token Ring network entity title (NET) media type if the
VTP v2 mode is disabled or TrBRF media type if the VTP v2 mode
is enabled.
mtu mtu-size (Optional) Specify the maximum transmission unit (MTU) (packet size
in bytes). The range is 1500 to 18190.
name vlan-name (Optional) Specify the VLAN name, an ASCII string from 1 to 32
characters that must be unique within the administrative domain.
parent parent-vlan-id (Optional) Specify the parent VLAN of an existing FDDI, Token Ring,
or TrCRF VLAN. This parameter identifies the TrBRF to which a
TrCRF belongs and is required when defining a TrCRF. The range is 0
to 1005.
ring ring-number (Optional) Specify the logical ring for an FDDI, Token Ring, or TrCRF
VLAN. The range is 1 to 4095.
said said-value (Optional) Enter the security association identifier (SAID) as
documented in IEEE 802.10. The range is 1 to 4294967294, and the
number must be unique within the administrative domain.
state {suspend | active} (Optional) Specify the VLAN state:
• If active, the VLAN is operational.
• If suspend, the VLAN is suspended. Suspended VLANs do not
pass packets.
ste ste-number (Optional) Specify the maximum number of spanning-tree explorer
(STE) hops. This keyword applies only to TrCRF VLANs. The range
is 0 to 13.
stp type {ieee | ibm | auto} (Optional) Specify the spanning-tree type for FDDI-NET, Token
Ring-NET, or TrBRF VLAN.
• ieee for IEEE Ethernet STP running source-route transparent
(SRT) bridging.
• ibm for IBM STP running source-route bridging (SRB).
• auto for STP running a combination of source-route transparent
bridging (IEEE) and source-route bridging (IBM).
tb-vlan1 tb-vlan1-id (Optional) Specify the first and second VLAN to which this VLAN is
translationally bridged. Translational VLANs translate FDDI or Token
and tb-vlan2 tb-vlan2-id
Ring to Ethernet, for example. The range is 0 to 1005. Zero is assumed
if no value is specified.
Table 2-30 shows the valid syntax options for different media types.
Configuration Rule
VTP v2 mode is enabled, and you Specify a parent VLAN ID of a TrBRF that already exists in the
are configuring a TrCRF VLAN database.
media type. Specify a ring number. Do not leave this field blank.
Specify unique ring numbers when TrCRF VLANs have the same
parent VLAN ID. Only one backup concentrator relay function
(CRF) can be enabled.
VTP v2 mode is enabled, and you Do not specify a backup CRF.
are configuring VLANs other than
TrCRF media type.
Configuration Rule
VTP v2 mode is enabled, and you Specify a bridge number. Do not leave this field blank.
are configuring a TrBRF VLAN
media type.
VTP v1 mode is enabled. No VLAN can have an STP type set to auto.
This rule applies to Ethernet, FDDI, FDDI-NET, Token Ring, and
Token Ring-NET VLANs.
Add a VLAN that requires The translational bridging VLAN IDs that are used must already
translational bridging (values are exist in the database.
not set to zero).
The translational bridging VLAN IDs that a configuration points
to must also contain a pointer to the original VLAN in one of the
translational bridging parameters (for example, Ethernet points to
FDDI, and FDDI points to Ethernet).
The translational bridging VLAN IDs that a configuration points
to must be different media types than the original VLAN (for
example, Ethernet can point to Token Ring).
If both translational bridging VLAN IDs are configured, these
VLANs must be different media types (for example, Ethernet can
point to FDDI and Token Ring).
Usage Guidelines You can only use this command mode for configuring normal-range VLANs, that is, VLAN IDs 1 to
1005.
Note To configure extended-range VLANs (VLAN IDs 1006 to 4094), use the vlan global configuration
command.
VLAN configuration is always saved in the VLAN database. If VTP mode is transparent, it is also saved
in the switch running configuration file, along with the VTP mode and domain name. You can then save
it in the switch startup configuration file by using the copy running-config startup-config privileged
EXEC command.
When you save VLAN and VTP configuration in the startup configuration file and reboot the switch, the
configuration is determined in these ways:
• If both the VLAN database and the configuration file show the VTP mode as transparent and the
VTP domain names match, the VLAN database is ignored. The VTP and VLAN configurations in
the startup configuration file are used. The VLAN database revision number remains unchanged in
the VLAN database.
• If the VTP mode is server, or if the startup VTP mode or domain names do not match the VLAN
database, the VTP mode and the VLAN configuration for the first 1005 VLANs use VLAN database
information.
The following are the results of using the no vlan commands:
• When the no vlan vlan-id form is used, the VLAN is deleted. Deleting VLANs automatically resets
to zero any other parent VLANs and translational bridging parameters that refer to the deleted
VLAN.
• When the no vlan vlan-id bridge form is used, the VLAN source-routing bridge number returns to
the default (0). The vlan vlan-id bridge command is used only for FDDI-NET and Token Ring-NET
VLANs and is ignored in other VLAN types.
• When the no vlan vlan-id media form is used, the media type returns to the default (ethernet).
Changing the VLAN media type (including the no form) resets the VLAN MTU to the default MTU
for the type (unless the mtu keyword is also present in the command). It also resets the VLAN parent
and translational bridging VLAN to the default (unless the parent, tb-vlan1, or tb-vlan2 are also
present in the command).
• When the no vlan vlan-id mtu form is used, the VLAN MTU returns to the default for the applicable
VLAN media type. You can also modify the MTU by using the media keyword.
• When the no vlan vlan-id name vlan-name form is used, the VLAN name returns to the default
name (VLANxxxx, where xxxx represent four numeric digits [including leading zeros] equal to the
VLAN ID number).
• When the no vlan vlan-id parent form is used, the parent VLAN returns to the default (0). The
parent VLAN resets to the default if the parent VLAN is deleted or if the media keyword changes
the VLAN type or the VLAN type of the parent VLAN.
• When the no vlan vlan-id ring form is used, the VLAN logical ring number returns to the default
(0).
• When the no vlan vlan-id said form is used, the VLAN SAID returns to the default (100,000 plus
the VLAN ID).
• When the no vlan vlan-id state form is used, the VLAN state returns to the default (active).
• When the no vlan vlan-id stp type form is used, the VLAN spanning-tree type returns to the default
(ieee).
• When the no vlan vlan-id tb-vlan1 or no vlan vlan-id tb-vlan2 form is used, the VLAN
translational bridge VLAN (or VLANs, if applicable) returns to the default (0). Translational bridge
VLANs must be a different VLAN type than the affected VLAN, and if two are specified, the two
must be different VLAN types from each other. A translational bridge VLAN resets to the default if
the translational bridge VLAN is deleted, if the media keyword changes the VLAN type, or if the
media keyword changes the VLAN type of the corresponding translation bridge VLAN.
Examples This example shows how to add an Ethernet VLAN with default media characteristics. The default
includes a vlan-name of VLANxxx, where xxxx represents four numeric digits (including leading zeros)
equal to the VLAN ID number. The default media option is ethernet; the state option is active. The
default said-value variable is 100000 plus the VLAN ID; the mtu-size variable is 1500; the stp-type
option is ieee. When you enter the exit or apply vlan configuration command, the VLAN is added if it
did not already exist; otherwise, this command does nothing.
Switch(vlan)# vlan 2
VLAN 2 added:
Name: VLAN0002
Switch(vlan)# exit
APPLY completed.
Exiting....
This example shows how to modify an existing VLAN by changing its name and MTU size:
Switch(vlan)# no vlan name engineering mtu 1200
You can verify your settings by entering the show vlan privileged EXEC command.
vlan access-map
Use the vlan access-map global configuration command on the switch stack or on a standalone switch
to create or modify a VLAN map entry for VLAN packet filtering. This entry changes the mode to the
VLAN access map configuration. Use the no form of this command to delete a VLAN map entry. Use
the vlan filter interface configuration command to apply a VLAN map to one or more VLANs.
Defaults There are no VLAN map entries and no VLAN maps applied to a VLAN.
Usage Guidelines In global configuration mode, use this command to create or modify a VLAN map. This entry changes
the mode to VLAN access-map configuration, where you can use the match access-map configuration
command to specify the access lists for IP or non-IP traffic to match and use the action command to set
whether a match causes the packet to be forwarded or dropped.
In VLAN access map configuration mode, these commands are available:
• action: sets the action to be taken (forward or drop).
• default: sets a command to its defaults
• exit: exits from VLAN access-map configuration mode
• match: sets the values to match (IP address or MAC address).
• no: negates a command or set its defaults
When you do not specify an entry number (sequence number), it is added to the end of the map.
There can be only one VLAN map per VLAN and it is applied as packets are received by a VLAN.
You can use the no vlan access-map name [number] command with a sequence number to delete a single
entry.
In global configuration mode, use the vlan filter interface configuration command to apply the map to
one or more VLANs.
Note For more information about VLAN map entries, refer to the software configuration guide for this release.
Examples This example shows how to create a VLAN map named vac1 and apply matching conditions and actions
to it. If no other entries already exist in the map, this will be entry 10.
Switch(config)# vlan access-map vac1
Switch(config-access-map)# match ip address acl1
Switch(config-access-map)# action forward
vlan database
Use the vlan database privileged EXEC command on the switch stack or on a standalone switch to enter
VLAN configuration mode. From this mode, you can add, delete, and modify VLAN configurations for
normal-range VLANs and globally propagate these changes by using the VLAN Trunking Protocol
(VTP). Configuration information is saved in the VLAN database.
vlan database
Note VLAN configuration mode is only valid for VLAN IDs 1 to 1005.
Usage Guidelines You can use the VLAN database configuration commands to configure VLANs 1 to 1005. To configure
extended-range VLANs (VLAN IDs 1006 to 4094), use the vlan (global configuration) command to
enter config-vlan mode. You can also configure VLAN IDs 1 to 1005 by using the vlan global
configuration command.
To return to the privileged EXEC mode from the VLAN configuration mode, enter the exit command.
Note This command mode is different from other modes because it is session-oriented. When you add, delete,
or modify VLAN parameters, the changes are not applied until you exit the session by entering the apply
or exit command. When the changes are applied, the VTP configuration version is incremented. You can
also not apply the changes to the VTP database by entering abort.
When you are in VLAN configuration mode, you can access the VLAN database and make changes by
using these commands:
• vlan: accesses subcommands to add, delete, or modify values associated with a single VLAN. For
more information, see the vlan (VLAN configuration) command.
• vtp: accesses subcommands to perform VTP administrative functions. For more information, see the
vtp (VLAN configuration) command.
When you have modified VLAN or VTP parameters, you can use these editing buffer manipulation
commands:
• abort: exits the mode without applying the changes. The VLAN configuration that was running
before you entered VLAN configuration mode continues to be used.
• apply: applies current changes to the VLAN database, increments the database configuration
revision number, propagates it throughout the administrative domain, and remains in VLAN
configuration mode.
Note You cannot use this command when the switch is in VTP client mode.
• exit: applies all configuration changes to the VLAN database, increments the database configuration
number, propagates it throughout the administrative domain, and returns to privileged EXEC mode.
• no: negates a command or set its defaults; valid values are vlan and vtp.
• reset: abandons proposed changes to the VLAN database, resets the proposed database to the
implemented VLAN database on the switch, and remains in VLAN configuration mode.
• show: displays VLAN database information.
• show changes [vlan-id]: displays the differences between the VLAN database on the switch and the
proposed VLAN database for all normal-range VLAN IDs (1 to 1005) or the specified VLAN ID (1
to 1005).
• show current [vlan-id]: displays the VLAN database on the switch or on a selected VLAN (1 to
1005).
• show proposed [vlan-id]: displays the proposed VLAN database or a selected VLAN (1 to 1005)
from the proposed database. The proposed VLAN database is not the running configuration until
you use the exit or apply VLAN configuration command.
You can verify that VLAN database changes have been made or aborted by using the show vlan
privileged EXEC command. This output is different from the show VLAN database configuration
command output.
Examples This example shows how to enter the VLAN configuration mode from the privileged EXEC mode and
to display VLAN database information:
Switch# vlan database
Switch(vlan)# show
VLAN ISL Id: 1
Name: default
Media Type: Ethernet
VLAN 802.10 Id: 100001
State: Operational
MTU: 1500
Translational Bridged VLAN: 1002
Translational Bridged VLAN: 1003
<output truncated>
DELETED:
VLAN ISL Id: 4
Name: VLAN0004
Media Type: Ethernet
VLAN 802.10 Id: 100004
State: Operational
MTU: 1500
MODIFIED:
VLAN ISL Id: 7
Current State: Operational
Modified State: Suspended
This example shows how to display the differences between VLAN 7 in the current database and the
proposed database.
Switch(vlan)# show changes 7
MODIFIED:
VLAN ISL Id: 7
Current State: Operational
Modified State: Suspended
This is an example of output from the show current 20 command. It displays only VLAN 20 of the
current database.
Switch(vlan)# show current 20
VLAN ISL Id: 20
Name: VLAN0020
Media Type: Ethernet
VLAN 802.10 Id: 100020
State: Operational
MTU: 1500
vlan filter
Use the vlan filter global configuration command on the switch stack or on a standalone switch to apply
a VLAN map to one or more VLANs. Use the no form of this command to remove the map.
Usage Guidelines To avoid accidentally dropping too many packets and disabling connectivity in the middle of the
configuration process, we recommend that you completely define the VLAN access map before applying
it to a VLAN.
Note For more information about VLAN map entries, refer to the software configuration guide for this release.
Examples This example applies VLAN map entry map1 to VLANs 20 and 30:
Switch(config)# vlan filter map1 vlan-list 20, 30
This example shows how to delete VLAN map entry mac1 from VLAN 20:
Switch(config)# no vlan filter map1 vlan-list 20
You can verify your settings by entering the show vlan filter privileged EXEC command.
vmps reconfirm
Examples This example shows how to immediately send VQP queries to the VMPS:
Switch# vmps reconfirm
You can verify your setting by entering the show vmps privileged EXEC command and examining the
VMPS Action row of the Reconfirmation Status section. The show vmps command shows the result of
the last time the assignments were reconfirmed either because the reconfirmation timer expired or
because the vmps reconfirm command was entered.
no vmps reconfirm
Syntax Description interval Reconfirmation interval for VQP client queries to the VLAN Membership Policy
Server (VMPS) to reconfirm dynamic VLAN assignments. The range is 1 to 120
minutes.
Examples This example shows how to set the VQP client to reconfirm dynamic VLAN entries every 20 minutes:
Switch(config)# vmps reconfirm 20
You can verify your setting by entering the show vmps privileged EXEC command and examining
information in the Reconfirm Interval row.
vmps retry
Use the vmps retry global configuration command on the switch stack or on a standalone switch to
configure the per-server retry count for the VLAN Query Protocol (VQP) client. Use the no form of this
command to return to the default setting.
no vmps retry
Syntax Description count Number of attempts to contact the VLAN Membership Policy Server (VMPS) by the
client before querying the next server in the list. The range is 1 to 10.
You can verify your setting by entering the show vmps privileged EXEC command and examining
information in the Server Retry Count row.
vmps server
Use the vmps server global configuration command on the switch stack or on a standalone switch to
configure the primary VLAN Membership Policy Server (VMPS) and up to three secondary servers. Use
the no form of this command to remove a VMPS server.
Syntax Description ipaddress IP address or host name of the primary or secondary VMPS servers. If you specify
a host name, the Domain Name System (DNS) server must be configured.
primary (Optional) Determines whether primary or secondary VMPS servers are being
configured.
Usage Guidelines The first server entered is automatically selected as the primary server whether or not primary is
entered. The first server address can be overridden by using primary in a subsequent command.
If a member switch in a cluster configuration does not have an IP address, the cluster does not use the
VMPS server configured for that member switch. Instead, the cluster uses the VMPS server on the
command switch, and the command switch proxies the VMPS requests. The VMPS server treats the
cluster as a single switch and uses the IP address of the command switch to respond to requests.
When using the no form without specifying the ipaddress, all configured servers are deleted. If you
delete all servers when dynamic-access ports are present, the switch cannot forward packets from new
sources on these ports because it cannot query the VMPS.
Examples This example shows how to configure the server with IP address 191.10.49.20 as the primary VMPS
server. The servers with IP addresses 191.10.49.21 and 191.10.49.22 are configured as secondary
servers:
Switch(config)# vmps server 191.10.49.20 primary
Switch(config)# vmps server 191.10.49.21
Switch(config)# vmps server 191.10.49.22
This example shows how to delete the server with IP address 191.10.49.21:
Switch(config)# no vmps server 191.10.49.21
You can verify your setting by entering the show vmps privileged EXEC command and examining
information in the VMPS Domain Server row.
vtp {domain domain-name | file filename | interface name [only] | mode {client | server |
transparent} | password password | pruning | version number}
Syntax Description domain domain-name Specify the VTP domain name, an ASCII string from 1 to 32 characters that
identifies the VTP administrative domain for the switch. The domain name
is case sensitive.
file filename Specify the IOS file system file where the VTP VLAN configuration is
stored.
interface name Specify the name of the interface providing the VTP ID updated for this
device.
only (Optional) Use only the IP address of this interface as the VTP IP updater.
mode Specify the VTP device mode as client, server, or transparent.
client Place the switch in VTP client mode. A switch in VTP client mode is enabled
for VTP, and can send advertisements, but does not have enough nonvolatile
storage to store VLAN configurations. You cannot configure VLANs on the
switch. When a VTP client starts up, it does not send VTP advertisements
until it receives advertisements to initialize its VLAN database.
server Place the switch in VTP server mode. A switch in VTP server mode is
enabled for VTP and sends advertisements. You can configure VLANs on the
switch. The switch can recover all the VLAN information in the current VTP
database from nonvolatile storage after reboot.
transparent Place the switch in VTP transparent mode. A switch in VTP transparent
mode is disabled for VTP, does not send advertisements or learn from
advertisements sent by other devices, and cannot affect VLAN
configurations on other devices in the network. The switch receives VTP
advertisements and forwards them on all trunk ports except the one on which
the advertisement was received.
When VTP mode is transparent, the mode and domain name are saved in the
switch running configuration file, and you can save them in the switch
startup configuration file by entering the copy running-config startup
config privileged EXEC command.
password password Set the administrative domain password for the generation of the 16-byte
secret value used in MD5 digest calculation to be sent in VTP advertisements
and to validate received VTP advertisements. The password can be an ASCII
string from 1 to 32 characters. The password is case sensitive.
pruning Enable VTP pruning on the switch.
version number Set VTP version to version 1 or version 2.
Usage Guidelines When you save VTP mode, domain name, and VLAN configurations in the switch startup configuration
file and reboot the switch, the VTP and VLAN configurations are determined by these conditions:
• If both the VLAN database and the configuration file show the VTP mode as transparent and the
VTP domain names match, the VLAN database is ignored. The VTP and VLAN configurations in
the startup configuration file are used. The VLAN database revision number remains unchanged in
the VLAN database.
• If the startup VTP mode is server mode, or the startup VTP mode or domain names do not match the
VLAN database, VTP mode and VLAN configuration for the first 1005 VLANs are determined by
VLAN database information, and VLANs greater than 1005 are configured from the switch
configuration file.
The vtp file filename cannot be used to load a new database; it renames only the file in which the existing
database is stored.
Follow these guidelines when configuring a VTP domain name:
• The switch is in the no-management-domain state until you configure a domain name. While in the
no-management-domain state, the switch does not send any VTP advertisements even if changes
occur to the local VLAN configuration. The switch leaves the no-management-domain state after it
receives the first VTP summary packet on any port that is trunking or after you configure a domain
name by using the vtp domain command. If the switch receives its domain from a summary packet,
it resets its configuration revision number to 0. After the switch leaves the no-management-domain
state, it can no be configured to re-enter it until you clear the nonvolatile RAM (NVRAM) and reload
the software.
• Domain names are case-sensitive.
• After you configure a domain name, it cannot be removed. You can only reassign it to a different
domain.
Follow these guidelines when setting VTP mode:
• The no vtp mode command returns the switch to VTP server mode.
• The vtp mode server command is the same as no vtp mode except that it does not return an error
if the switch is not in client or transparent mode.
• If the receiving switch is in client mode, the client switch changes its configuration to duplicate the
configuration of the server. If you have switches in client mode, be sure to make all VTP or VLAN
configuration changes on a switch in server mode. If the receiving switch is in server mode or
transparent mode, the switch configuration is not changed.
• Switches in transparent mode do not participate in VTP. If you make VTP or VLAN configuration
changes on a switch in transparent mode, the changes are not propagated to other switches in the
network.
• If you change the VTP or VLAN configuration on a switch that is in server mode, that change is
propagated to all the switches in the same VTP domain.
• The vtp mode transparent command disables VTP from the domain but does not remove the
domain from the switch.
• The VTP mode must be transparent for you to add extended-range VLANs or for VTP and VLAN
information to be saved in the running configuration file.
• If extended-range VLANs are configured on the switch and you attempt to set the VTP mode to
server or client, you receive an error message, and the configuration is not allowed.
• VTP can be set to either server or client mode only when dynamic VLAN creation is disabled.
Follow these guidelines when setting a VTP password:
• Passwords are case sensitive. Passwords should match on all switches in the same domain.
• When you use the no vtp password form of the command, the switch returns to the no-password
state.
Follow these guidelines when setting VTP pruning:
• VTP pruning removes information about each pruning-eligible VLAN from VTP updates if there
are no stations belonging to that VLAN.
• If you enable pruning on the VTP server, it is enabled for the entire management domain for VLAN
IDs 1 to 1005.
• Only VLANs in the pruning-eligible list can be pruned.
• Pruning is supported with VTP version 1 and version 2.
Follow these guidelines when setting the VTP version:
• Toggling the version 2 (v2) mode state modifies parameters of certain default VLANs.
• Each VTP switch automatically detects the capabilities of all the other VTP devices. To use version
2, all VTP switches in the network must support version 2; otherwise, you must configure them to
operate in VTP version 1 mode.
• If all switches in a domain are VTP version 2-capable, you need only to configure version 2 on one
switch; the version number is then propagated to the other version-2 capable switches in the VTP
domain.
• If you are using VTP in a Token Ring environment, VTP version 2 must be enabled.
• If you are configuring a Token Ring bridge relay function (TrBRF) or Token Ring concentrator relay
function (TrCRF) VLAN media type, you must use version 2.
• If you are configuring a Token Ring or Token Ring-NET VLAN media type, you must use version 1.
You cannot save password, pruning, and version configurations in the switch configuration file.
Examples This example shows how to rename the filename for VTP configuration storage to vtpfilename:
Switch(config)# vtp file vtpfilename
This example shows how to specify the name of the interface providing the VTP updater ID for this
device:
Switch(config)# vtp interface gigabitethernet
This example shows how to set the administrative domain for the switch:
Switch(config)# vtp domain OurDomainName
This example shows how to place the switch in VTP transparent mode:
Switch(config)# vtp mode transparent
This example shows how to enable version 2 mode in the VLAN database:
Switch(config)# vtp version 2
You can verify your settings by entering the show vtp status privileged EXEC command.
Note VTP configuration in VLAN configuration mode is saved in the VLAN database when applied.
Syntax Description domain domain-name Set the VTP domain name by entering an ASCII string from 1 to 32
characters that identifies the VTP administrative domain for the switch. The
domain name is case sensitive.
password password Set the administrative domain password for the generation of the 16-byte
secret value used in MD5 digest calculation to be sent in VTP advertisements
and to validate received VTP advertisements. The password can be an ASCII
string from 1 to 32 characters. The password is case sensitive.
pruning Enable pruning in the VTP administrative domain. VTP pruning causes
information about each pruning-eligible VLAN to be removed from VTP
updates if there are no stations belonging to that VLAN.
v2-mode Enable VLAN Trunking Protocol (VTP) version 2 in the administrative
domains.
client Place the switch in VTP client mode. A switch in VTP client mode is enabled
for VTP, can send advertisements, but does not have enough nonvolatile
storage to store VLAN configurations. You cannot configure VLANs on it.
When a VTP client starts up, it does not send VTP advertisements until it
receives advertisements to initialize its VLAN database.
server Place the switch in VTP server mode. A switch in VTP server mode is
enabled for VTP and sends advertisements. You can configure VLANs on it.
The switch can recover all the VLAN information in the current VTP
database from nonvolatile storage after reboot.
transparent Place the switch in VTP transparent mode. A switch in VTP transparent
mode is disabled for VTP, does not send advertisements or learn from
advertisements sent by other devices, and cannot affect VLAN
configurations on other devices in the network. The switch receives VTP
advertisements and forwards them on all trunk ports except the one on which
the advertisement was received.
Usage Guidelines If the VTP mode is transparent, the mode and domain name are saved in the switch running configuration
file, and you can save the configuration in the switch startup configuration file by using the copy
running-config startup-config privileged EXEC command.
Follow these guidelines when setting the VTP mode:
• The no vtp client and no vtp transparent forms of the command return the switch to VTP server
mode.
• The vtp server command is the same as no vtp client or no vtp transparent except that it does not
return an error if the switch is not in client or transparent mode.
• If the receiving switch is in client mode, the client switch changes its configuration to duplicate the
configuration of the server. If you have switches in client mode, make sure to make all VTP or
VLAN configuration changes on a switch in server mode. If the receiving switch is in server mode
or transparent mode, the switch configuration is not changed.
• Switches in transparent mode do not participate in VTP. If you make VTP or VLAN configuration
changes on a switch in transparent mode, the changes are not propagated to other switches in the
network.
• If you make a change to the VTP or VLAN configuration on a switch in server mode, that change is
propagated to all the switches in the same VTP domain.
• The vtp transparent command disables VTP from the domain but does not remove the domain from
the switch.
• The VTP mode must be transparent for you to add extended-range VLANs or for the VTP and the
VLAN configurations to be saved in the running configuration file.
• If extended-range VLANs are configured on the switch and you attempt to set the VTP mode to
server or client, you receive an error message and the configuration is not allowed.
• VTP can be set to either server or client mode only when dynamic VLAN creation is disabled.
Examples This example shows how to place the switch in VTP transparent mode:
Switch(vlan)# vtp transparent
Setting device to VTP TRANSPARENT mode.
This example shows how to set the administrative domain for the switch:
Switch(vlan)# vtp domain OurDomainName
Changing VTP domain name from cisco to OurDomainName
This example shows how to enable pruning in the proposed new VLAN database:
Switch(vlan)# vtp pruning
Pruning switched ON
This example shows how to enable v2 mode in the proposed new VLAN database:
Switch(vlan)# vtp v2-mode
V2 mode enabled.
You can verify your settings by entering the show vtp status privileged EXEC command.
This appendix describes the boot loader commands on the Catalyst 3750 switches. Unless otherwise
noted, the term switch refers to a standalone switch and to a switch stack.
During normal boot loader operation, you are not presented with the boot loader command-line prompt.
You gain access to the boot loader command line if the switch is set to manually boot, if an error occurs
during power-on self test (POST) DRAM testing, or if an error occurs while loading the operating system
(a corrupted IOS image). You can also access the boot loader if you have lost or forgotten the switch
password.
Note The default configuration for Catalyst 3750 switches allows an end user with physical access to the
switch to recover from a lost password by interrupting the boot process while the switch is powering up
and then entering a new password. The password recovery disable feature allows the system
administrator to protect access to the switch password by disabling part of this functionality and allowing
the user to interrupt the boot process only by agreeing to set the system back to the default configuration.
With password recovery disabled, the user can still interrupt the boot process and change the password,
but the configuration file (config.text) and the VLAN database file (vlan.dat) are deleted. For more
information, refer to the software configuration guide for this release.
You can access the boot loader through a switch console connection at 9600 bps. Unplug the switch
power cord, and press the switch Mode button while reconnecting the power cord. You can release the
Mode button a second or two after the LED above port 1X goes off. You should then see the boot loader
Switch: prompt. The boot loader performs low-level CPU initialization, performs POST, and loads a
default operating system image into memory.
boot
Use the boot boot loader command to load and boot an executable image and to enter the command-line
interface.
Syntax Description -post (Optional) Run the loaded image with an extended or comprehensive power-on
self-test (POST). Using this keyword causes POST to take longer to complete.
-n (Optional) Pause for the IOS debugger immediately after launching.
-p (Optional) Pause for the JTAG debugger right after loading the image.
filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url (Optional) 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.
Usage Guidelines When you enter the boot command without any arguments, the switch attempts to automatically boot the
system by using the information in the BOOT environment variable, if any. If you supply an image name for
the file-url variable, the boot command attempts to boot the specified image.
When you set boot loader boot command options, they are executed immediately and apply only to the current
boot loader session. These settings are not saved for the next boot operation.
Filenames and directory names are case sensitive.
Examples This example shows how to boot the switch using the new-image.bin image:
switch: boot flash:/new-images/new-image.bin
After entering this command, you are prompted to start the setup program.
cat
Use the cat boot loader command to display the contents of one or more files.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url Path (directory) and name of the files to display. Separate each filename with a space.
Examples This example shows how to display the contents of two files:
switch: cat flash:/new-images/info flash:env_vars
version_suffix: i5q3l2-121-11.AX
version_directory: c3750-i5q3l2-mz.121-11.AX
image_name: c3750-i5q3l2-mz.121-11.AX.bin
ios_image_file_size: 3049472
total_image_file_size: 4551168
image_feature: LAYER_3|MIN_DRAM_MEG=64
image_family: C3750
info_end:
BAUD=57600
MANUAL_BOOT=no
copy
Use the copy boot loader command to copy a file from a source to a destination.
Syntax Description -b block-size (Optional) This option is used only for internal development and testing.
filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/source-file-url Path (directory) and filename (source) to be copied.
/destination-file-url Path (directory) and filename of the destination.
You can verify that the file was copied by entering the dir filesystem: boot loader command.
delete
Use the delete boot loader command to delete one or more files from the specified file system.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url Path (directory) and filename to delete. Separate each filename with a space.
You can verify that the files were deleted by entering the dir flash: boot loader command.
dir
Use the dir boot loader command to display a list of files and directories on the specified file system.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url (Optional) Path (directory) and directory name whose contents you want to
display. Separate each directory name with a space.
Examples This example shows how to display the files in Flash memory:
switch: dir flash:
Directory of flash:/
Field Description
2 Index number of the file.
-rwx File permission, which can be any or all of the following:
• d—directory
• r—readable
• w—writable
• x—executable
1644045 Size of the file.
<date> Last modification date.
env_vars Filename.
flash_init
Use the flash_init boot loader command to initialize the Flash file system.
flash_init
Defaults The Flash file system is automatically initialized during normal system operation.
Usage Guidelines During the normal boot process, the Flash file system is automatically initialized.
Use this command to manually initialize the Flash file system. For example, you use this command
during the recovery procedure for a lost or forgotten password.
format
Use the format boot loader command to format the specified file system and destroy all data in that file
system.
format filesystem:
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
Usage Guidelines
Caution Use this command with care; it destroys all data on the file system and renders your system unusable.
fsck
Use the fsck boot loader command to check the file system for consistency.
Syntax Description -test (Optional) Initialize the file system code and perform extra POST on Flash memory.
An extensive, nondestructive memory test is performed on every byte that makes up
the file system.
-f (Optional) Initialize the file system code and perform a fast file consistency check.
Cyclic redundancy checks (CRCs) in the flashfs sectors are not checked.
filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
Usage Guidelines To stop an in-progress file system consistency check, disconnect the switch power and then reconnect
the power.
Examples This example shows how to perform an extensive file system check on Flash memory:
switch: fsck -test flash:
help
Use the help boot loader command to display the available commands.
help
Usage Guidelines You can also use the question mark (?) to display a list of available boot loader commands.
load_helper
Use the load_helper boot loader command to load and initialize one or more helper images, which
extend or patch the functionality of the boot loader.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url Path (directory) and a list of loadable helper files to dynamically load during
loader initialization. Separate each image name with a semicolon.
Usage Guidelines The load_helper command searches for loadable files only if the HELPER environment variable is set.
Filenames and directory names are case sensitive.
memory
Use the memory boot loader command to display memory heap utilization information.
memory
Examples This example shows how to display memory heap utilization information:
switch: memory
Text: 0x00700000 - 0x0071cf24 (0x0001cf24 bytes)
Rotext: 0x00000000 - 0x00000000 (0x00000000 bytes)
Data: 0x0071cf24 - 0x00723a0c (0x00006ae8 bytes)
Bss: 0x0072529c - 0x00746f94 (0x00021cf8 bytes)
Stack: 0x00746f94 - 0x00756f94 (0x00010000 bytes)
Heap: 0x00756f98 - 0x00800000 (0x000a9068 bytes)
Field Description
Text Beginning and ending address of the text storage area.
Rotext Beginning and ending address of the read-only text storage area. This part of the data
segment is grouped with the Text entry.
Data Beginning and ending address of the data segment storage area.
Bss Beginning and ending address of the block started by symbol (Bss) storage area. It
is initialized to zero.
Stack Beginning and ending address of the area in memory allocated to the software to
store automatic variables, return addresses, and so forth.
Heap Beginning and ending address of the area in memory that memory is dynamically
allocated to and freed from.
mkdir
Use the mkdir boot loader command to create one or more new directories on the specified file system.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/directory-url Name of the directories to create. Separate each directory name with a space.
You can verify that the directory was created by entering the dir filesystem: boot loader command.
more
Use the more boot loader command to display the contents of one or more files.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url Path (directory) and name of the files to display. Separate each filename with
a space.
Examples This example shows how to display the contents of two files:
switch: more flash:/new-images/info flash:env_vars
version_suffix: i5q3l2-121-11.AX
version_directory: c3750-i5q3l2-mz.121-11.AX
image_name: c3750-i5q3l2-mz.121-11.AX.bin
ios_image_file_size: 3049472
total_image_file_size: 4551168
image_feature: LAYER_3|MIN_DRAM_MEG=64
image_family: C3750
info_end:
BAUD=57600
MANUAL_BOOT=no
rename
Use the rename boot loader command to rename a file.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/source-file-url Original path (directory) and filename.
/destination-file-url New path (directory) and filename.
Examples This example shows a file named config.text being renamed to config1.text:
switch: rename flash:config.text flash:config1.text
You can verify that the file was renamed by entering the dir filesystem: boot loader command.
reset
Use the reset boot loader command to perform a hard reset on the system. A hard reset is similar to
power-cycling the switch, clearing the processor, registers, and memory.
reset
rmdir
Use the rmdir boot loader command to remove one or more empty directories from the specified file
system.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/directory-url Path (directory) and name of the empty directories to remove. Separate each
directory name with a space.
Usage Guidelines Directory names are case sensitive and limited to 45 characters between the slashes (/); the name cannot
contain control characters, spaces, deletes, slashes, quotes, semicolons, or colons.
Before removing a directory, you must first delete all the files in the directory.
The switch prompts you for confirmation before deleting each directory.
You can verify that the directory was deleted by entering the dir filesystem: boot loader command.
set
Use the set boot loader command to set or display environment variables, which can be used to control
the boot loader or any other software running on the switch.
Note Under normal circumstances, it is not necessary to alter the setting of the environment variables.
Syntax Description variable value Use one of these keywords for variable and value:
MANUAL_BOOT—Determines whether the switch automatically or manually
boots.
Valid values are 1, yes, 0, and no. If it is set to no or 0, the boot loader attempts to
automatically boot the system. If it is set to anything else, you must manually boot
the switch from the boot loader mode.
BOOT filesystem:/file-url— A semicolon-separated list of executable files to try to
load and execute when automatically booting.
If the BOOT environment variable is not set, the system attempts to load and execute
the first executable image it can find by using a recursive, depth-first search through
the flash: file system. If the BOOT variable is set but the specified images cannot be
loaded, the system attempts to boot the first bootable file that it can find in the Flash
file system.
ENABLE_BREAK—Determines whether the automatic boot process can be
interrupted by using the Break key on the console.
Valid values are 1, yes, on, 0, no, and off. If it is set to 1, yes, or on, you can interrupt
the automatic boot process by pressing the Break key on the console after the Flash
file system has initialized.
HELPER filesystem:/file-url— A semicolon-separated list of loadable files to
dynamically load during the boot loader initialization. Helper files extend or patch
the functionality of the boot loader.
PS1 prompt—A string that is used as the command-line prompt in boot loader mode.
CONFIG_FILE flash:/file-url—The filename that IOS uses to read and write a
nonvolatile copy of the system configuration.
BAUD rate—The rate in bits per second (bps) used for the console. The IOS
software inherits the baud rate setting from the boot loader and continues to use this
value unless the configuration file specifies another setting. The range is from 0 to
4294967295 bps. Valid values are 50, 75, 110, 150, 300, 600, 1200, 1800, 2000,
2400, 3600, 4800, 7200, 9600, 14400, 19200, 28800, 38400, 56000, 57600, 115200,
and 128000.
The most commonly used values are 300, 1200, 2400, 9600, 19200, 57600, and
115200.
Note Environment variables that have values are stored in the Flash file system in various files. The format of
these files is that each line contains an environment variable name and an equal sign followed by the
value of the variable. A variable has no value if it is not listed in this file; it has a value if it is listed in
the file even if the value is a null string. A variable that is set to a null string (for example, “ ”) is a
variable with a value. Many environment variables are predefined and have default values.
Usage Guidelines Environment variables are case sensitive and must be entered as documented.
Environment variables that have values are stored in Flash memory outside of the Flash file system.
The MANUAL_BOOT environment variable can also be set by using the boot manual global
configuration command.
The BOOT environment variable can also be set by using the boot system filesystem:/file-url global
configuration command.
The ENABLE_BREAK environment variable can also be set by using the boot enable-break global
configuration command.
The HELPER environment variable can also be set by using the boot helper filesystem:/file-url global
configuration command.
The CONFIG_FILE environment variable can also be set by using the boot config-file flash:/file-url
global configuration command.
The BOOTHLPR environment variable can also be set by using the boot boothlpr filesystem:/file-url
global configuration command.
The HELPER_CONFIG_FILE environment variable can also be set by using the boot helper-config-file
filesystem:/file-url global configuration command.
The HELPER_CONFIG_FILE environment variable can also be set by using the boot helper-config-file
filesystem:/file-url global configuration command.
The SWITCH_NUMBER environment variable can also be set by using the switch
current-stack-member-number renumber new-stack-member-number global configuration command.
The SWITCH_PRIORITY environment variable can also be set by using the switch
stack-member-number priority priority-number global configuration command.
The boot loader prompt string (PS1) can be up to 120 printable characters except the equal sign (=).
Examples This example shows how to change the boot loader prompt:
switch: set PS1 loader:
loader:
You can verify your setting by using the set boot loader command.
type
Use the type boot loader command to display the contents of one or more files.
Syntax Description filesystem: Alias for a Flash file system. Use flash: for the system board Flash device.
/file-url Path (directory) and name of the files to display. Separate each filename with
a space.
Examples This example shows how to display the contents of two files:
switch: type flash:/new-images/info flash:env_vars
version_suffix: i5q3l2-121-11.AX
version_directory: c3750-i5q3l2-mz.121-11.AX
image_name: c3750-i5q3l2-mz.121-11.AX.bin
ios_image_file_size: 3049472
total_image_file_size: 4551168
image_feature: LAYER_3|MIN_DRAM_MEG=64
image_family: C3750
info_end:
BAUD=57600
MANUAL_BOOT=no
unset
Use the unset boot loader command to reset one or more environment variables.
Note Under normal circumstances, it is not necessary to alter the setting of the environment variables.
Usage Guidelines The MANUAL_BOOT environment variable can also be reset by using the no boot manual global
configuration command.
The BOOT environment variable can also be reset by using the no boot system global configuration
command.
The ENABLE_BREAK environment variable can also be reset by using the no boot enable-break
global configuration command.
The HELPER environment variable can also be reset by using the no boot helper global configuration
command.
The CONFIG_FILE environment variable can also be reset by using the no boot config-file global
configuration command.
The BOOTHLPR environment variable can also be reset by using the no boot boothlpr global
configuration command.
The HELPER_CONFIG_FILE environment variable can also be reset by using the no boot
helper-config-file global configuration command.
Examples This example shows how to reset the prompt string to its previous setting:
switch: unset PS1
switch:
version
Use the version boot loader command to display the boot loader version.
version
Examples This example shows how to display the boot loader version:
switch: version
C3750 Boot Loader (C3750-HBOOT-M) Version 12.1(11)AX
Compiled Wed 21-Feb-02 14:58 by devgoyal
switch:
This appendix describes the debug privileged EXEC commands that have been created or changed for
use with the Catalyst 3750 switch. These commands are helpful in diagnosing and resolving
internetworking problems and should be enabled only under the guidance of Cisco technical support
staff.
Caution Because debugging output is assigned high priority in the CPU process, it can render the system
unusable. For this reason, use the debug commands only to troubleshoot specific problems or during
troubleshooting sessions with Cisco technical support staff. It is best to use the debug commands during
periods of lower network traffic and fewer users. Debugging during these periods decreases the
likelihood that increased debug command processing overhead will affect system use.
debug autoqos
Use the debug autoqos privileged EXEC command to enable debugging of the automatic quality of
service (auto-QoS) feature. Use the no form of this command to disable debugging output.
debug autoqos
no debug autoqos
Usage Guidelines To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable
debugging before you enable auto-QoS. You enable debugging by entering the debug autoqos privileged
EXEC command.
The undebug autoqos command is the same as the no debug autoqos command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Examples This example shows how to display the QoS configuration that is automatically generated when
auto-QoS is enabled:
Switch# debug autoqos
AutoQoS debugging is on
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# auto qos voip cisco-phone
debug cluster
Use the debug cluster privileged EXEC command to enable debugging of cluster-specific events. Use
the no form of this command to disable debugging output.
debug cluster {discovery | events | extended | hsrp | http | ip [packet] | members | nat | neighbors
| platform | snmp | vqpxy}
no debug cluster {discovery | events | extended | hsrp | http | ip [packet] | members | nat |
neighbors | platform | snmp | vqpxy}
Usage Guidelines This command is available only on the cluster command switch stack or cluster command switch.
The undebug cluster command is the same as the no debug cluster command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug dot1x
Use the debug dot1x privileged EXEC command to enable debugging of the 802.1X feature. Use the no
form of this command to disable debugging output.
Usage Guidelines The undebug dot1x command is the same as the no debug dot1x command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug dtp
Use the debug dtp privileged EXEC command to enable debugging of the Dynamic Trunking Protocol
(DTP) activity. Use the no form of this command to disable debugging output.
debug dtp {aggregation | all | decision | events | oserrs | packets | queue | states | timers}
no debug dtp {aggregation | all | decision | events | oserrs | packets | queue | states | timers}
Usage Guidelines The undebug dtp command is the same as the no debug dtp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug etherchannel
Use the debug etherchannel privileged EXEC command to enable debugging of the
EtherChannel/PAgP shim. This shim is the software module that is the interface between the Port
Aggregation Protocol (PAgP) software module and the port manager software module. Use the no form
of this command to disable debugging output.
Note Though visible in the command-line help strings, the linecard keyword is not supported.
Usage Guidelines If you do not specify a keyword, all debug messages are displayed.
The undebug etherchannel command is the same as the no debug etherchannel command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug interface
Use the debug interface privileged EXEC command to enable debugging of interface-related activities.
Use the no form of this command to disable debugging output.
Syntax Description interface-id Display debug messages for the specified physical interface, identified by
type switch number/module number/ port, for example gigabitethernet
6/0/3.
null interface-number Display debug messages for null interfaces. The interface-number is always
0.
port-channel Display debug messages for the specified EtherChannel port-channel
port-channel-number interface. The port-channel-number range is 1 to 12.
vlan vlan-id Display debug messages for the specified VLAN. The vlan-id range is 1 to
4094.
Usage Guidelines If you do not specify a keyword, all debug messages are displayed.
The undebug interface command is the same as the no debug interface command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug ip igmp filter command is the same as the no debug ip igmp filter command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug ip igmp max-groups command is the same as the no debug ip igmp max-groups
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description group (Optional) Display IGMP snooping group activity debug messages.
management (Optional) Display IGMP snooping management activity debug messages.
router (Optional) Display IGMP snooping router activity debug messages.
timer (Optional) Display IGMP snooping timer event debug messages.
Usage Guidelines The undebug ip igmp snooping command is the same as the no debug ip igmp snooping command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug lacp
Use the debug lacp privileged EXEC command to enable debugging of Link Aggregation Control
Protocol (LACP) activity. Use the no form of this command to disable debugging output.
Usage Guidelines The undebug lacp command is the same as the no debug lacp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug mac-notification
Use the debug mac-notification privileged EXEC command to enable debugging of MAC notification
events. Use the no form of this command to disable debugging output.
debug mac-notification
no debug mac-notification
Usage Guidelines The undebug mac-notification command is the same as the no debug mac-notification command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug matm
Use the debug matm privileged EXEC command to enable debugging of platform-independent MAC
address management. Use the no form of this command to disable debugging output.
debug matm
no debug matm
Usage Guidelines The undebug matm command is the same as the no debug matm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug monitor
Use the debug monitor privileged EXEC command to enable debugging of the Switched Port Analyzer
(SPAN) feature. Use the no form of this command to disable debugging output.
debug monitor {all | errors | idb-update | info | list | notifications | platform | requests | snmp}
no debug monitor {all | errors | idb-update | info | list | notifications | platform | requests | snmp}
Usage Guidelines The undebug monitor command is the same as the no debug monitor command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug mvrdbg
Use the debug mvrdbg privileged EXEC command to enable debugging of Multicast VLAN
Registration (MVR). Use the no form of this command to disable debugging output.
Usage Guidelines The undebug mvrdbg command is the same as the no debug mvrdbg command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug nvram
Use the debug nvram privileged EXEC command to enable debugging of nonvolatile random-access
memory (NVRAM) activity. Use the no form of this command to disable debugging output.
debug nvram
no debug nvram
Usage Guidelines The undebug nvram command is the same as the no debug nvram command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug pagp
Use the debug pagp privileged EXEC command to enable debugging of Port Aggregation Protocol
(PAgP) activity. Use the no form of this command to disable debugging output.
Usage Guidelines The undebug pagp command is the same as the no debug pagp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform acl {all | exit | label | main | racl | stack | vacl | vlmap | warn}
no debug platform acl {all | exit | label | main | racl | stack | vacl | vlmap | warn}
Usage Guidelines The undebug platform acl command is the same as the no debug platform acl command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform cli-redirection main command is the same as the no debug platform
cli-redirection main command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description all Display debug messages for all configuration file transmission and reception events
throughout the stack.
reception Display debug messages for configuration file reception from other stack members.
transmission Display debug messages for configuration file transmission to other stack members.
Usage Guidelines The undebug platform configuration command is the same as the no debug platform configuration
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description broadcast-q Display debug messages about packets received by the broadcast queue.
cbt-to-spt-q Display debug messages about packets received by the core-based tree to
shortest-path tree (cbt-to-spt) queue.
cpuhub-q Display debug messages about packets received by the CPU heartbeat queue.
host-q Display debug messages about packets received by the host queue.
icmp-q Display debug messages about packets received by the Internet Control Message
Protocol (ICMP) queue.
igmp-snooping-q Display debug messages about packets received by the Internet Group
Management Protocol (IGMP)-snooping queue.
layer2-protocol-q Display debug messages about packets received by the Layer 2 protocol queue.
logging-q Display debug messages about packets received by the logging queue.
remote-console-q Display debug messages about packets received by the remote console queue.
routing-protocol-q Display debug messages about packets received by the routing protocol queue.
rpffail-q Display debug messages about packets received by the reverse path forwarding
(RFP) failure queue.
software-fwd-q Debug packets received by the software forwarding queue.
stp-q Debug packets received by the Spanning Tree Protocol (STP) queue.
Usage Guidelines The undebug platform cpu-queues command is the same as the no debug platform cpu-queues
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description all Display all platform device manager debug messages.
device-info Display platform device manager device structure debug messages.
poll Display platform device manager 1-second poll debug messages.
port-download Display platform device manager remote procedure call (RPC) usage debug
messages.
trace Trace platform device manager function entry and exit debug messages.
Usage Guidelines The undebug platform device-manager command is the same as the no debug platform
device-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform dot1x command is the same as the no debug platform dot1x command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform etherchannel command is the same as the no debug platform etherchannel
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description error (Optional) Display fallback bridging manager error condition messages.
retry (Optional) Display fallback bridging manager retry messages.
rpc {events | messages} (Optional) Display fallback bridging debugging information. The
keywords have these meanings:
• events—Display remote procedure call (RPC) events.
• messages—Display RPC messages.
Usage Guidelines If you do not specify a keyword, all fallback bridging manager debug messages are displayed.
The undebug platform fallback-bridging command is the same as the no debug platform
fallback-bridging command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform forw-tcam [adjustment | allocate | audit | error | move | read | write]
no debug platform forw-tcam [adjustment | allocate | audit | error | move | read | write]
Syntax Description adjustment (Optional) Display TCAM manager adjustment debug messages.
allocate (Optional) Display TCAM manager allocation debug messages.
audit (Optional) Display TCAM manager audit messages.
error (Optional) Display TCAM manager error messages.
move (Optional) Display TCAM manager move messages.
read (Optional) Display TCAM manager read messages.
write (Optional) Display TCAM manager write messages.
Usage Guidelines If you do not specify a keyword, all forwarding TCAM manager debug messages are displayed.
The undebug platform forw-tcam command is the same as the no debug platform forw-tcam
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform ip igmp snooping {all | di | error | event | group | mgmt | pak | retry | rpc | warn}
debug platform ip igmp snooping pak {ip-address | error | ipopt | leave| query | report | rx | svi
| tx}
no debug platform ip igmp snooping {all | di | error | event | group | mgmt | pak | retry | rpc |
warn}
rpc [cfg | l3mm | misc Display IGMP snooping remote procedure call (RPC) event debug messages.
| vlan] The keywords have these meanings:
• cfg—(Optional) Display IGMP snooping RPC debug messages.
• l3mm—(Optional) IGMP snooping Layer 3 multicast router group RPC
debug messages.
• misc—(Optional) IGMP snooping miscellaneous RPC debug messages.
• vlan—(Optional) IGMP snooping VLAN assert RPC debug messages.
warn Display IGMP snooping warning messages.
Usage Guidelines The undebug platform ip igmp snooping command is the same as the no debug platform ip igmp
snooping command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform ip multicast {all | mdb | mdfs-rp-retry | midb | mroute-rp | resources | retry |
rpf-throttle | snoop-events | software-forward | swidb-events | vlan-locks}
no debug platform ip multicast {all | mdb | mdfs-rp-retry | midb | mroute-rp | resources | retry
| rpf-throttle | snoop-events | software-forward | swidb-events | vlan-locks}
Syntax Description all Display all platform IP-multicast event debug messages.
Note Using this command can degrade the performance of the switch.
mdb Display IP-multicast debug messages for multicast distributed fast switching
(MDFS) multicast descriptor block (mdb) events.
mdfs-rp-retry Display IP-multicast MDFS rendezvous point (RP) retry event debug messages.
midb Display IP-multicast MDFS multicast interface descriptor block (MIDB) debug
messages.
mroute-rp Display IP-multicast RP event debug messages.
resources Display IP-multicast hardware resource debug messages.
retry Display IP-multicast retry processing event debug messages.
rpf-throttle Display IP-multicast reverse path forwarding (RPF) throttle event debug
messages.
snoop-events Display IP-multicast IGMP snooping event debug messages.
software-forward Display IP-multicast software forwarding event debug messages.
swidb-events Display IP-multicast MDFS software interface descriptor block (swidb) or
global event debug messages.
vlan-locks Display IP-multicast VLAN lock and unlock event debug messages.
Usage Guidelines The undebug platform ip multicast command is the same as the no debug platform ip multicast
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform ip unicast {adjacency | all | arp | dhcp | errors | events | interface | mpath |
registries | retry | route | rpc | standby | statistics}
no debug platform ip unicast {adjacency | all | arp | dhcp | errors | events | interface | mpath |
registries | retry | route | rpc | standby | statistics}
Syntax Description adjacency Display IP unicast routing adjacency programming event debug messages.
all Display all platform IP unicast routing debug messages.
Note Using this command can degrade the performance of the switch.
arp Display IP unicast routing Address Resolution Protocol (ARP) and ARP throttling debug
messages.
dhcp Display IP unicast routing Dynamic Host Configuration Protocol (DHCP) dynamic
address-related event debug messages.
errors Display all IP unicast routing error debug messages, including resource allocation
failures.
events Display all IP unicast routing event debug messages, including registry and
miscellaneous events.
interface Display IP unicast routing interface event debug messages.
mpath Display IP unicast routing multi-path adjacency programming event debug messages
(present when performing equal or unequal cost routing).
registries Display IP unicast routing forwarding information database (FIB), adjacency add,
update, and delete registry event debug messages.
retry Display IP unicast routing reprogram FIBs with ternary content addressable memory
(TCAM) allocation failure debug messages.
route Display IP unicast routing FIB TCAM programming event debug messages.
rpc Display IP unicast routing Layer 3 unicast remote procedure call (RPC) interaction
debug messages.
standby Display IP unicast routing standby event debug messages, helpful in troubleshooting Hot
Standby Routing Protocol (HSRP) issues.
statistics Display IP unicast routing statistics gathering-related event debug messages.
Usage Guidelines The undebug platform ip unicast command is the same as the no debug platform ip unicast command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform ipc command is the same as the no debug platform ipc.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform led command is the same as the no debug platform led command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform matm {aging | all | ec-aging | errors | learning | rpc | secure-address | warnings}
no debug platform matm {aging | all | ec-aging | errors | learning | rpc | secure-address |
warnings}
Usage Guidelines The undebug platform matm command is the same as the no debug platform matm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform messaging application {all | badpak | cleanup | events | memerr | messages |
stackchg | usererr}
no debug platform messaging application {all | badpak | cleanup | events | memerr | messages
| stackchg | usererr}
Usage Guidelines The undebug platform messaging application command is the same as the no debug platform
messaging application command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform phy {automdix | flowcontrol | forced | init-seq | link-status | read | sfp |
show-controller | speed | write}
no debug platform phy {automdix | flowcontrol | forced | init-seq | link-status | read | sfp |
show-controller | speed | write}
Syntax Description automdix Display PHY automatic media-dependent-interface crossover (Auto MDIX)
debug messages.
flowcontrol Display PHY flowcontrol debug messages.
forced Display PHY forced-mode debug messages.
init-seq Display PHY initialization-sequence debug messages.
link-status Display PHY link-status debug messages.
read Display PHY-read debug messages.
sfp Display PHY small form-factor pluggable (SFP) modules debug messages.
show-controller Display PHY show-controller debug messages.
speed Display PHY speed-change debug messages.
write Display PHY-write debug messages.
Usage Guidelines The undebug platform phy command is the same as the no debug platform phy command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform pm
Use the debug platform pm privileged EXEC command to enable debugging of the platform-dependent
port manager software module. Use the no form of this command to disable debugging output.
Usage Guidelines The undebug platform pm command is the same as the no debug platform pm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform port-asic command is the same as the no debug platform port-asic command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform port-security {add | aging | all | delete | errors | rpc | warnings}
no debug platform port-security {add | aging | all | delete | errors | rpc | warnings}
Usage Guidelines The undebug platform port-security command is the same as the no debug platform port-security
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform qos-acl-tcam {all | ctcam | errors | labels | mask | rpc | tcam}
no debug platform qos-acl-tcam {all | ctcam | errors | labels | mask | rpc | tcam}
Syntax Description all Display all QoS and ACL TCAM (QATM) manager debug messages.
ctcam Display Cisco TCAM (CTCAM) related-events debug messages.
errors Display QATM error-related-events debug messages.
labels Display QATM label-related-events debug messages.
mask Display QATM mask-related-events debug messages.
rpc Display QATM remote procedure call (RPC) related-events debug messages.
tcam Display QATM TCAM-related events debug messages.
Usage Guidelines The undebug platform qos-acl-tcam command is the same as the no debug platform qos-acl-tcam
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform remote-commands command is the same as the no debug platform
remote-commands command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform resource-manager command is the same as the no debug platform
resource-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform snmp command is the same as the no debug platform snmp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform span command is the same as the no debug platform span command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform stack-manager command is the same as the no debug platform
stack-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform supervisor-asic command is the same as the no debug platform
supervisor-asic command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform sw-bridge command is the same as the no debug platform sw-bridge
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug platform tcam log l3 {acl {input | output} | ipv6 {acl {input | output} | local | qos |
secondary} | local | qos | secondary}
no debug platform tcam log l3 {acl {input | output} | ipv6 {acl {input | output} | local | qos |
secondary} | local | qos | secondary}
Syntax Description log l2 {acl {input | output} | Display Layer-2 field-based CAM look-up type debug messages. The
local | qos} keywords have these meanings:
• acl {input | output}—Display input or output ACL look-up debug
messages.
• local—Display local forwarding look-up debug messages.
• qos—Display classification and quality of service (QoS) look-up
debug messages.
l3 {acl {input | output} | Display Layer-3 field-based CAM look-up type debug messages. The
ipv6 {acl {input | output} | keywords have these meanings:
local | qos | secondary} |
• acl {input | output}—Display input or output ACL look-up debug
local | qos | secondary}
messages.
• ipv6 {acl {input | output} | local | qos | secondary}—Display
IPv6-based look-up debug messages. Options include displaying
input or output ACL look-up, local forwarding look-up,
classification and QoS look-up, or secondary forwarding look-up
debug messages.
• local—Display local forwarding look-up debug messages.
• qos—Display classification and quality of service (QoS) look-up
debug messages.
• secondary—Display secondary forwarding look-up debug
messages.
read {reg | ssram | tcam} Display TCAM-read debug messages. The keywords have these
meanings:
• reg—Display TCAM-register read debug messages.
• ssram—Display synchronous static RAM (SSRAM)-read debug
messages.
• tcam—Display TCAM-read debug messages.
search Display supervisor-initiated TCAM-search results debug messages.
write {forw-ram | reg | Display TCAM-write debug messages. The keywords have these
tcam} meanings:
forw-ram—Display forwarding-RAM write debug messages.
reg—Display TCAM-register write debug messages.
tcam—Display TCAM-write debug messages.
Usage Guidelines The undebug platform tcam command is the same as the no debug platform tcam command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform udld command is the same as the no debug platform udld command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug platform vlan command is the same as the no debug platform vlan command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug pm
Use the debug pm privileged EXEC command to enable debugging of port manager (PM) activity. The
port manager is a state machine that controls all the logical and physical interfaces. All features, such as
VLANs, UniDirectional Link Detection (UDLD), and so forth, work with the port manager to provide
switch functions. Use the no form of this command to disable debugging output.
debug pm {all | assert | card | cookies | etherchnl | messages | port | registry | sm | span | split |
vlan | vp}
no debug pm {all | assert | card | cookies | etherchnl | messages | port | registry | sm | span | split |
vlan | vp}
Note Though visible in the command-line help strings, the scp and pvlan keywords are not supported.
Usage Guidelines The undebug pm command is the same as the no debug pm command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug port-security
Use the debug port-security privileged EXEC command to enable debugging of the allocation and
states of the port security subsystem. Use the no form of this command to disable debugging output.
debug port-security
no debug port-security
Usage Guidelines The undebug port-security command is the same as the no debug port-security command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug qos-manager
Use the debug qos-manager privileged EXEC command to enable debugging of the quality of service
(QoS) manager software. Use the no form of this command to disable debugging output.
Usage Guidelines The undebug qos-manager command is the same as the no debug qos-manager command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug spanning-tree
Use the debug spanning-tree privileged EXEC command to enable debugging of spanning-tree
activities. Use the no form of this command to disable debugging output.
Usage Guidelines The undebug spanning-tree command is the same as the no debug spanning-tree command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug spanning-tree backbonefast command is the same as the no debug spanning-tree
backbonefast command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description receive (Optional) Display the nonoptimized path for received BPDU debug messages.
transmit (Optional) Display the nonoptimized path for transmitted BPDU debug messages.
Usage Guidelines The undebug spanning-tree bpdu command is the same as the no debug spanning-tree bpdu
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description detail (Optional) Display detailed optimized BPDU-handling debug messages.
packet (Optional) Display packet-level optimized BPDU-handling debug messages.
Usage Guidelines The undebug spanning-tree bpdu-opt command is the same as the no debug spanning-tree bpdu-opt
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug spanning-tree mstp {all | boundary | bpdu-rx | bpdu-tx | errors | flush | init | migration |
pm | proposals | region | roles | sanity_check | sync | tc | timers}
no debug spanning-tree mstp {all | boundary | bpdu-rx | bpdu-tx | errors | flush | init | migration
| pm | proposals | region | roles | sanity_check | sync | tc | timers}
Usage Guidelines The undebug spanning-tree mstp command is the same as the no debug spanning-tree mstp
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug spanning-tree switch {all | errors | flush | general | helper | pm | rx {decode | errors |
interrupt | process} | state | tx [decode] | uplinkfast}
no debug spanning-tree switch {all | errors | flush | general | helper | pm | rx {decode | errors |
interrupt | process} | state | tx [decode] | uplinkfast}
Usage Guidelines The undebug spanning-tree switch command is the same as the no debug spanning-tree switch
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Usage Guidelines The undebug spanning-tree uplinkfast command is the same as the no debug spanning-tree
uplinkfast command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
debug sw-vlan
Use the debug sw-vlan privileged EXEC command to enable debugging of VLAN manager activities.
Use the no form of this command to disable debugging output.
debug sw-vlan {badpmcookies | cfg-vlan {bootup | cli} | events | ifs | management | notification
| packets | registries | vtp}
Syntax Description badpmcookies Display debug messages for VLAN manager incidents of bad port manager
cookies.
cfg-vlan {bootup | cli} Display config-vlan debug messages. The keywords have these meanings:
• bootup—Display messages when the switch is booting up.
• cli—Display messages when the command-line interface (CLI) is in
config-vlan mode.
events Display debug messages for VLAN manager events.
ifs See the debug sw-vlan ifs command.
management Display debug messages for VLAN manager management of internal
VLANs.
notification See the debug sw-vlan notification command.
packets Display debug messages for packet handling and encapsulation processes.
registries Display debug messages for VLAN manager registries.
vtp See the debug sw-vlan vtp command.
Usage Guidelines The undebug sw-vlan command is the same as the no debug sw-vlan command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description open {read | write} Display VLAN manager IFS file-open operation debug messages. The
keywords have these meanings:
• read—Display VLAN manager IFS file-read operation debug messages.
• write—Display VLAN manager IFS file-write operation debug messages.
read {1 | 2 | 3 | 4} Display file-read operation debug messages for the specified error test (1, 2, 3,
or 4).
write Display file-write operation debug messages.
Usage Guidelines The undebug sw-vlan ifs command is the same as the no debug sw-vlan ifs command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
When determining the file read operation, Operation 1 reads the file header, which contains the header
verification word and the file version number. Operation 2 reads the main body of the file, which
contains most of the domain and VLAN information. Operation 3 reads type length version (TLV)
descriptor structures. Operation 4 reads TLV data.
Syntax Description accfwdchange Display debug messages for VLAN manager notification of aggregated
access interface spanning-tree forward changes.
allowedvlancfgchange Display debug messages for VLAN manager notification of changes to the
allowed VLAN configuration.
fwdchange Display debug messages for VLAN manager notification of spanning-tree
forwarding changes.
linkchange Display debug messages for VLAN manager notification of interface
link-state changes.
modechange Display debug messages for VLAN manager notification of interface mode
changes.
pruningcfgchange Display debug messages for VLAN manager notification of changes to the
pruning configuration.
statechange Display debug messages for VLAN manager notification of interface state
changes.
Usage Guidelines The undebug sw-vlan notification command is the same as the no debug sw-vlan notification
command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
Syntax Description events Display debug messages for general-purpose logic flow and detailed VTP
messages generated by the VTP_LOG_RUNTIME macro in the VTP
code.
packets Display debug messages for the contents of all incoming VTP packets
that have been passed into the VTP code from the IOS VTP
platform-dependent layer, except for pruning packets.
pruning [packets | xmit] Display debug messages generated by the pruning segment of the VTP
code. The keywords have these meanings:
• packets—(Optional) Display debug messages for the contents of all
incoming VTP pruning packets that have been passed into the VTP
code from the IOS VTP platform-dependent layer.
• xmit—(Optional) Display debug messages for the contents of all
outgoing VTP packets that the VTP code requests the IOS VTP
platform-dependent layer to send.
xmit Display debug messages for the contents of all outgoing VTP packets that
the VTP code requests the IOS VTP platform-dependent layer to send,
except for pruning packets.
Usage Guidelines The undebug sw-vlan vtp command is the same as the no debug sw-vlan vtp command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
If no further parameters are entered after the pruning keyword, VTP pruning debugging messages are
displayed. They are generated by the VTP_PRUNING_LOG_NOTICE, VTP_PRUNING_LOG_INFO,
VTP_PRUNING_LOG_DEBUG, VTP_PRUNING_LOG_ALERT, and
VTP_PRUNING_LOG_WARNING macros in the VTP pruning code.
debug udld
Use the debug udld privileged EXEC command to enable debugging of the UniDirectional Link
Detection (UDLD) feature. Use the no form of this command to disable UDLD debugging.
Syntax Description events Display debug messages for UDLD process events as they occur.
packets Display debug messages for the UDLD process as it receives packets from the
packet queue and tries to send them at the request of the UDLD protocol code.
registries Display debug messages for the UDLD process as it processes registry calls from
the UDLD process-dependent module and other feature modules.
Usage Guidelines The undebug udld command is the same as the no debug udld command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
For debug udld events, these debugging messages are displayed:
• General UDLD program logic flow
• State machine state changes
• Program actions for the set and clear ErrDisable state
• Neighbor cache additions and deletions
• Processing of configuration commands
• Processing of link-up and link-down indications
For debug udld packets, these debugging messages are displayed:
• General packet processing program flow on receipt of an incoming packet
• Indications of the contents of the various pieces of packets received (such as type length versions
[TLVs]) as they are examined by the packet reception code
• Packet transmission attempts and the outcome
For debug udld registries, these categories of debugging messages are displayed:
• Sub-block creation
• Fiber-port status changes
• State change indications from the port manager software
• MAC address registry calls
debug vqpc
Use the debug vqpc privileged EXEC command to enable debugging of the VLAN Query Protocol
(VQP) client. Use the no form of this command to disable debugging output.
Syntax Description all (Optional) Display all VQP client debug messages.
cli (Optional) Display the VQP client command-line interface (CLI) debug
messages.
events (Optional) Display VQP client event debug messages.
learn (Optional) Display VQP client address learning debug messages.
packet (Optional) Display VQP client packet information debug messages.
Usage Guidelines The undebug vqpc command is the same as the no debug vqpc command.
When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack
member, you must start a session from the stack master by using the session switch-number privileged
EXEC command. Then enter the debug command at the command-line prompt of the stack member.
This appendix describes the show platform privileged EXEC commands that have been created or
changed for use with the Catalyst 3750 switch. These commands display information helpful in
diagnosing and resolving internetworking problems and should be used only under the guidance of Cisco
technical support staff.
show platform acl {interface interface-id | label label-number [detail] | statistics asic-number |
vlan vlan-id} [ | {begin | exclude | include} expression]
Syntax Description interface interface-id Display per-interface ACL manager information for the specified interface.
The interface can be a physical interface or a VLAN.
label label-number Display per-label ACL manager information. The label-number range is 0 to
[detail] 255. The keyword has this meaning:
• detail—(Optional) Display detailed ACL manager label information.
statistics asic-number Display per-ASIC ACL manager information. The asic-number is the port
ASIC number, either 0 or 1.
vlan vlan-id Display per-VLAN ACL manager information. The vlan-id range is from 1 to
4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description config-output Display the output of the last auto-configuration application.
default Display whether or not the system is running the default configuration.
running Display a snapshot of the backed-up running configuration on the local
switch.
startup Display a snapshot of the backed-up startup configuration on the local switch.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform forward interface-id [vlan vlan-id] src-mac dst-mac [l3protocol-id] [sap | snap]
[cos cos] [ip src-ip dst-ip [frag field] [dscp dscp] {l4protocol-id | icmp icmp-type icmp-code |
igmp igmp-version igmp-type | tcp src-port dst-port flags | udp src-port dst-port} [ | {begin |
exclude | include} expression]
Syntax Description interface-id The input physical interface, the port on which the packet comes in to the
switch (including type, stack member, module, and port number).
vlan vlan-id (Optional) Input VLAN ID. The range is 1 to 4094. If not specified, and
the input interface is not a routed port, the default is 1.
src-mac 48-bit source MAC address.
dst-mac 48-bit destination MAC address.
l3protocol-id (Optional) The Layer 3 protocol used in the packet. The number is a
value 0 to 65535.
sap (Optional) Service access point (SAP) encapsulation type.
snap (Optional) Subnetwork Access Protocol (SNAP) encapsulation type.
cos cos (Optional) Class of service (CoS) value of the frame. The range is 0 to 7.
ip src-ip dst-ip (Optional, but required for IP packets) Source and destination IP
addresses in dotted decimal notation.
frag field (Optional) The IP fragment field for a fragmented IP packet. The range
is 0 to 65535.
dscp dscp (Optional) Differentiated Services Code Point (DSCP) field in the IP
header. The range is 0 to 63.
l4protocol-id The numeric value of the Layer 4 protocol field in the IP header. The
range is 0 to 255. For example, 47 is generic routing encapsulation
(GRE), and 89 is Open Shortest Path First (OSPF). If the protocol is TCP,
UDP, ICMP, or IGMP, you should use the appropriate keyword instead
of a numeric value.
icmp icmp-type Internet Control Message Protocol (ICMP) parameters. The icmp-type
icmp-code and icmp-code ranges are 0 to 255.
igmp igmp-version Internet Group Management Protocol (IGMP) parameters. The
igmp-type igmp-version range is 1 to 15; the igmp-type range is 0 to 15.
tcp src-port dst-port Transmission Control Protocol (TCP) parameters: TCP source port,
flags destination port, and the numeric value of the TCP flags byte in the
header. The src-port and dst-port ranges are 0 to 65535. The flag range
is from 0 to 1024.
udp src-port dst-port User Datagram Protocol (UDP) parameters. The src-port and dst-port
ranges are 0 to 65535.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Examples Refer to the “Troubleshooting” chapter of the software configuration guide for this release for examples
of the show platform forward command output displays and what they mean.
show platform ip igmp snooping {all | control [di] | counters | flood [vlan vlan-id] | group
ip-address | hardware | retry [count | local [count] | remote [count]]} [ | {begin | exclude |
include} expression]
Syntax Description all Display all IGMP snooping platform IP multicast information.
control [di] Display IGMP snooping control entries. The keyword has this meaning:
• di—(Optional) Display IGMP snooping control destination index
entries.
counters Display IGMP snooping counters.
flood [vlan vlan-id] Display IGMP snooping flood information. The keyword has this meaning:
• vlan vlan-id—(Optional) Display flood information for the specified
VLAN. The range is 1 to 4094.
group ip-address Display the IGMP snooping multicast group information, where ip-address is
the IP address of the group.
hardware Display IGMP snooping information loaded into hardware.
retry [count | local Display IGMP snooping retry information. The keywords have these
[count] meanings:
• count—(Optional) Display only the retry count.
• local—(Optional) Display local retry entries.
remote [count] Display remote entries. The keyword has this meaning:
• count—(Optional) Display only the remote count.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform ip unicast {adjacency | cef-idb | counts | dhcp | failed {adjacency | arp [A.B.C.D]
| route} | mpaths | route | standby | statistics | trace} [ | {begin | exclude | include}
expression]
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform layer4op {acl | qos [port-asic]} {and-or | map | or-and | vcu} [ | {begin | exclude
| include} expression]
Syntax Description acl Display access control list (ACL) Layer 4 operators information.
qos [port-asic] Display quality of service (QoS) Layer 4 operators information. The keyword has
this meaning:
• port-asic—(Optional) QoS port ASIC number. The value can be 0 or 1.
and-or Display AND-OR registers information.
map Display select map information.
or-and Display OR-AND registers information.
vcu Display value compare unit (VCU) register information.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description aging-array (Optional) Display the MAC address table aging array.
hash-table (Optional) Display the MAC address table hash table.
mac-address mac-address (Optional) Display the MAC address table MAC address information,
where mac-address is the 48-bit hardware address.
vlan vlan-id (Optional) Display information for the specified VLAN. The range is 1
to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description application [incoming | Display application message information. The keywords have these
outgoing | summary] meanings:
• incoming—(Optional) Display only information about incoming
application messaging requests.
• outgoing—(Optional) Display only information about incoming
application messaging requests.
• summary—(Optional) Display summary information about all
application messaging requests.
hiperf [class-number] Display outgoing high-performance message information. Specify the
class-number option to display information about high-performance
messages for this class number. The range is 0 to 36.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description session (Optional) Display SPAN information for the specified SPAN session. The
session-number range is 1 to 66.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform pm
Use the show platform pm privileged EXEC command to display platform-dependent port-manager
information.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform port-asic {cpu-queue-map-table [asic number | port number [asic number]] |
dest-map index number |
etherchannel-info [asic number | port number [asic number]] |
exception [asic number | port number [asic number]] |
global-status [asic number | port number [asic number]] |
learning [asic number | port number [asic number]] |
mac-info [asic number | port number [asic number]] |
mvid [asic number] |
packet-info-ram [asic number | index number [asic number]] |
port-info [asic number | port number [asic number]] |
prog-parser [asic number | port number [asic number]] |
receive {buffer-queue | port-fifo | supervisor-sram} [asic number | port number [asic
number]] |
span [vlan-id [asic number] | [asic number]
stack {control | dest-map | learning | messages | mvid | prog-parser | span | stats [asic
number | port number [asic number]]
stats {drop | enqueue | miscellaneous | supervisor} [asic number | port number [asic
number]] |
transmit {port-fifo | queue | supervisor-sram} [asic number | port number [asic number]]
vct [asic number | port number [asic number]]}
[ | {begin | exclude | include} expression]
Syntax Description cpu-queue-map-table Display the CPU queue-map table entries. The keywords have
[asic number | port number these meanings:
[asic number]] • asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27.
dest-map index number Display destination-map information for the specified index. The
range is 0 to 65535.
etherchannel-info [asic number | Display the contents of the EtherChannel information register. The
port number [asic number]] keywords have these meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
exception [asic number | port Display the exception-index register information. The keywords
number [asic number]] have these meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
global-status [asic number | Display global and interrupt status. The keywords have these
port number [asic number]] meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
learning [asic number | port Display entries in the learning cache. The keywords have these
number [asic number]] meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
mac-info [asic number | Display the contents of the MAC information register. The
port number [asic number]] keywords have these meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
mvid [asic number] Display the mapped VLAN ID table. The keyword has this
meaning:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
packet-info-ram [asic number | Display the packet information RAM. The keywords have these
index number [asic number]] meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• index number—(Optional) Display information for the
specified packet RAM index number and ASIC number. The
range is 0 to 63.
port-info [asic number | port Display port information register values. The keywords have these
number [asic number]] meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
prog-parser [asic number | port Display the programmable parser tables. The keywords have these
number [asic number]] meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
receive {buffer-queue | port-fifo | Display receive information. The keywords have these meanings:
supervisor-sram} [asic number |
• buffer-queue—Display the buffer queue information.
port number [asic number]]
• port-fifo—Display the port-FIFO information.
• supervisor-sram—Display the supervisor static RAM
(SRAM) information.
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
span [vlan-id | asic number] Display the Switched Port Analyzer (SPAN)-related information.
The keywords have these meanings:
• vlan-id—(Optional) Display information for the specified
VLAN. The range is 0 to 1023.
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
stack {control | dest-map | Display stack-related information. The keywords have these
learning | messages | mvid | meanings:
prog-parser | span | stats [asic
• control—Display stack control-status register information.
number | port number [asic
number]] • dest-map—Display destination-map information.
• learning—Display entries in the learning-cache.
• messages—Display the stack-message register information.
• mvid—Display entries in the mapped VLAN-ID table.
• prog-parser—Display the programmable parser tables.
• span—Display SPAN-related information.
• stats—Display raw statistics for the port ASIC.
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
stats {drop | enqueue | Display raw statistics for the port ASIC. The keywords have these
miscellaneous | supervisor} [asic meanings:
number | port number [asic
• drop—Display drop statistics.
number]]
• enqueue—Display enqueue statistics.
• miscellaneous—Display miscellaneous statistics.
• supervisor—Display supervisor statistics.
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
transmit {port-fifo | queue | Display transmit information. The keywords have these meanings:
supervisor-sram} [asic number |
• port-fifo—Display the contents of the port-FIFO information
port number [asic number]]
register.
• queue—Display the contents of the queue information
register.
• supervisor-sram—Display supervisor SRAM information.
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
vct [asic number | port number Display the VLAN compression table entries for the specified
[asic number]] ASIC or for the specified port and ASIC. The keywords have these
meanings:
• asic number—(Optional) Display information for the
specified ASIC. The range is 0 to 1.
• port number—(Optional) Display information for the
specified port and ASIC number. The range is 0 to 27, where
0 is the supervisor and 1 to 25 are the ports.
| begin (Optional) Display begins with the line that matches the
expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified
expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform qos {label asic number | policer {parameters asic number |
port alloc number asic number}} [ | {begin | exclude | include} expression]
Syntax Description label asic number Display QoS label maps for the specified ASIC.
(Optional) For asic number, the range is 0 to 1.
policer {parameters asic number | Display policer information. The keywords have these
port alloc number asic number} meanings:
• parameters asic number—Display parameter
information for the specified ASIC. The range is 0 to 1.
• port alloc number asic number—Display port allocation
information for the specified port and ASIC. The port
allocation range is 0 to 25. The ASIC range is 0 to 1.
| begin (Optional) Display begins with the line that matches the
expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified
expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description dm [index number] Display the destination map. The keyword has this meaning:
• index number—(Optional) Display the specified index. The range is 0 to
65535.
erd [index number] Display the equal-cost-route descriptor table for the specified index. The
keyword has this meaning:
• index number—(Optional) Display the specified index. The range is 0 to
65535.
mad [index number] Display the MAC-address descriptor table for the specified index. The
keyword has this meaning:
• index number—(Optional) Display the specified index. The range is 0 to
65535.
med [index number] Display the multi-expansion descriptor table for the specified index. The
keyword has this meaning:
• index number—(Optional) Display the specified index. The range is 0 to
65535.
mod Display the resource-manager module information.
sd [index number] Display the station descriptor table for the specified index. The keyword has
this meaning:
• index number—(Optional) Display the specified index. The range is 0 to
65535.
vld [index number] Display the VLAN-list descriptor table for the specified index. The keyword
has this meaning:
• index number—(Optional) Display the specified index. The range is 0 to
65535.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description synchronization Display spanning-tree state synchronization information. The keywords have
[detail | vlan these meanings:
vlan-id] • detail—(Optional) Display detailed spanning-tree information.
• vlan vlan-id—(Optional) Display VLAN switch spanning-tree information
for the specified VLAN. The range is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
Syntax Description vlan-id Display spanning-tree instance information for the specified VLAN. The range
is 1 to 4094.
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform stack-manager {all | counters | trace [sdp [reverse] | state [reverse]]}
[ | {begin | exclude | include} expression]
Syntax Description all Display all information for the entire switch stack.
counters Display the stack manager counters.
trace [sdp [reverse]] Display trace information. The keywords have these meanings:
• sdp—(Optional) Display Stack Discovery Protocol (SDP) information.
• reverse—(Optional) Display trace information in reverse chronological
order (from recent to older chronological sequence).
trace [state [reverse]] Display trace information. The keywords have these meanings:
• state—(Optional) Display stack state machine information.
• reverse—(Optional) Display trace information in reverse chronological
order (from recent to older chronological sequence).
| begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
These are the states displayed in the summary information about the switch stack:
• Waiting—The stage when a switch is booting up and waiting for communication from other switches
in the stack. The switch has not yet determined whether it is a stack master or not.
Stack members not participating in a stack master election remain in the waiting state until the stack
master is elected and ready.
• Initializing—The stage when a switch has determined whether it is the stack master or not. If the
switch is not the stack master, it is receiving its system- and interface-level configuration from the
stack master and loading it.
• Ready—The stage when the stack member has completed loading the system- and interface-level
configuration and is ready to forward traffic.
• Master Re-Init—The stage immediately after a stack master re-election and a different stack
member is elected stack master. The new stack master is re-initializing its configuration. This state
applies only to the new stack master.
• Ver Mismatch—The stage of a switch in version mismatch (VM) mode. VM mode is when a switch
joining the switch stack has a different stack protocol minor version number from the stack master.
A typical state transition for a stack member (including a stack master) booting up is Waiting ->
Initializing -> Ready.
A typical state transition for a stack member becoming a stack master after a stack master election is
Ready -> Master Re-Init -> Ready.
A typical state transition for a stack member in version mismatch (VM) mode is Waiting ->
Ver Mismatch.
show platform tb
Use the show platform tb privileged EXEC command to display platform-dependent trusted-boundary
information during a stack master change to a new stack master.
Syntax Description | begin (Optional) Display begins with the line that matches the expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform tcam {handle number | log-results | table {acl | all | equal-cost-route | ipv6 {acl |
qos | secondary} local | mac-address | multicast-expansion | qos | secondary | station |
vlan-list} | usage} [asic number [detail [invalid]] | [index number [detail [invalid]] | invalid
| num number [detail [invalid]] | invalid] | [invalid] | [num number [detail [invalid]] |
invalid]] [ | {begin | exclude | include} expression]
show platform tcam table acl [asic number [detail [invalid]] | [index number [detail [invalid]] |
invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail [invalid]]
| invalid]] [ | {begin | exclude | include} expression]
show platform tcam table all [asic number [detail [invalid]] | [index number [detail [invalid]] |
invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail [invalid]]
| invalid]] [ | {begin | exclude | include} expression]
show platform tcam table equal-cost-route [asic number [detail [invalid]] | [index number
[detail [invalid]] | invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number
[detail [invalid]] | invalid]] [ | {begin | exclude | include} expression]
show platform tcam table ipv6 {acl | qos | secondary} [asic number [detail [invalid]] | [index
number [detail [invalid]] | invalid | num number [detail [invalid]] | invalid] | [invalid] | [num
number [detail [invalid]] | invalid]] [ | {begin | exclude | include} expression]
show platform tcam table local [asic number [detail [invalid]] | [index number [detail [invalid]]
| invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail [invalid]]
| invalid]] [ | {begin | exclude | include} expression]
show platform tcam table mac-address [asic number [detail [invalid]] | [index number [detail
[invalid]] | invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail
[invalid]] | invalid]] [ | {begin | exclude | include} expression]
show platform tcam table multicast-expansion [asic number [detail [invalid]] | [index number
[detail [invalid]] | invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number
[detail [invalid]] | invalid]] [ | {begin | exclude | include} expression]
show platform tcam table qos [asic number [detail [invalid]] | [index number [detail [invalid]] |
invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail [invalid]]
| invalid]] [ | {begin | exclude | include} expression]
show platform tcam table secondary [asic number [detail [invalid]] | [index number [detail
[invalid]] | invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail
[invalid]] | invalid]] [ | {begin | exclude | include} expression]
show platform tcam table station [asic number [detail [invalid]] | [index number [detail
[invalid]] | invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail
[invalid]] | invalid]] [ | {begin | exclude | include} expression]
show platform tcam table vlan-list [[asic number [detail [invalid]] | [index number [detail
[invalid]] | invalid | num number [detail [invalid]] | invalid] | [invalid] | [num number [detail
[invalid]] | invalid]] [ | {begin | exclude | include} expression]
Syntax Description handle number Display the TCAM handle. The range is 0 to 4294967295.
log-results Display the TCAM log results.
table {acl | all | equal-cost-route Display lookup and forwarding table information. The keywords
| ipv6 {acl | qos | secondary} have these meanings:
local | mac-address |
• acl—Display the access-control list (ACL) table.
multicast-expansion | qos |
secondary | station | vlan-list} • all—Display all the TCAM tables.
• equal-cost-route—Display the equal-cost-route table.
• ipv6—Display IPv6 information.
– acl—Display the IPv6 ACL-table information.
– qos—Display the IPv6 QoS-table information.
– secondary—Display the IPv6 secondary-table
information.
• local—Display the local table.
• mac-address—Display the MAC-address table.
• multicast-expansion—Display the IPv6 multicast-expansion
table.
• qos—Display the QoS table.
• secondary—Display the secondary table.
• station—Display the station table.
• vlan-list—Display the VLAN list table.
usage Display the CAM and forwarding table usage.
[[asic number [detail [invalid]] | Display information. The keywords have these meanings:
[index number [detail [invalid]] |
• asic number—Display information for the specified ASIC
invalid | num number [detail
device ID. The range is 0 to 15.
[invalid]] | invalid] | [invalid] |
[num number [detail [invalid]] | • detail [invalid]—(Optional) Display valid or invalid details.
invalid]] • index number—(Optional) Display information for the
specified TCAM table index. The range is 0 to 32768.
• num number—(Optional) Display information for the
specified TCAM table number. The range is 0 to 32768.
| begin (Optional) Display begins with the line that matches the
expression.
| exclude (Optional) Display excludes lines that match the expression.
| include (Optional) Display includes lines that match the specified
expression.
expression Expression in the output to use as a reference point.
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
show platform vlan {misc | mvid | prune | refcount | rpc {receive | transmit}} [ | {begin | exclude
| include} expression]
Usage Guidelines You should use this command only when you are working directly with your technical support
representative while troubleshooting a problem. Do not use this command unless your technical support
representative asks you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output are displayed.
boot loader
C
accessing A-1
booting candidate switches
helper image 2-23 See clusters
IOS image A-2 cat (boot loader) command A-4
directories caution, description xvi
creating A-16 channel-group command 2-28
displaying a list of A-7 channel-protocol command 2-32
removing A-20 class command 2-33
displaying class-map command 2-35
available commands A-12 class maps
memory heap utilization A-14 creating 2-35
version A-27 defining the match criteria 2-123
environment variables displaying 2-217
described A-21 class of service
displaying settings A-21 See CoS
location of A-23 clear lacp command 2-37
setting A-21 clear mac-address-table command 2-38
unsetting A-25 clear pagp command 2-39
files clear setup express command 2-40
copying A-5 clear spanning-tree counters command 2-41
deleting A-6 clear spanning-tree detected-protocols command 2-42
displaying a list of A-7 clear vmps statistics command 2-43
displaying the contents of A-4, A-17, A-24 clear vtp counters command 2-44
renaming A-18 cluster commander-address command 2-45
file system cluster discovery hop-count command 2-47
formatting A-10 cluster enable command 2-48
initializing Flash A-9 cluster holdtime command 2-50
running a consistency check A-11 cluster member command 2-51
loading helper images A-13 cluster outside-interface command 2-53
prompt A-1 cluster run command 2-54
resetting the system A-19 clusters
boot manual command 2-25 adding candidates 2-51
boot private-config-file command 2-26 binding to HSRP group 2-55
boot system command 2-27 building manually 2-51
BPDU filtering, for spanning tree 2-365, 2-398 communicating with
BPDU guard, for spanning tree 2-367, 2-398 devices outside the cluster 2-53
broadcast storm control 2-415 members by using Telnet 2-187
broadcast traffic counters 2-254 debug messages, display B-4
clusters (continued)
D
displaying
candidate switches 2-220 debug autoqos command B-2
debug messages B-4 debug cluster command B-4
member switches 2-222 debug dot1x command B-6
status 2-218 debug dtp command B-7
hop-count limit for extended discovery 2-47 debug etherchannel command B-8
HSRP standby groups 2-55 debug interface command B-9
redundancy 2-55 debug ip igmp filter command B-10
SNMP trap 2-355 debug ip igmp max-groups command B-11
cluster standby-group command 2-55 debug ip igmp snooping command B-12
cluster timer command 2-57 debug lacp command B-13
command modes defined 1-2 debug mac-notification command B-14
command switch debug matm command B-15
See clusters debug monitor command B-16
configuration files debug mvrdbg command B-17
password recovery disable considerations A-1 debug nvram command B-18
specifying the name 2-21, 2-26 debug pagp command B-19
configuring multiple interfaces 2-90 debug platform acl command B-20
config-vlan mode debug platform cli-redirection main command B-21
commands 2-461 debug platform configuration command B-22
description 1-5 debug platform cpu-queues command B-23
entering 2-460 debug platform device-manager command B-25
summary 1-2 debug platform dot1x command B-26
conventions debug platform etherchannel command B-27
command xvi debug platform fallback-bridging command B-28
for examples xvi debug platform forw-tcam command B-29
publication xvi debug platform ipc command B-36
text xvi debug platform ip igmp snooping command B-30
copy (boot loader) command A-5 debug platform ip multicast command B-32
CoS debug platform ip unicast command B-34
assigning default value to incoming packets 2-131 debug platform led command B-37
overriding the incoming value 2-131 debug platform matm command B-38
CoS-to-DSCP map 2-135 debug platform messaging application command B-39
CPU ASIC statistics, displaying 2-224 debug platform phy command B-40
debug platform pm command B-42
debug platform port-asic command B-44
policy maps
N
applying to an interface 2-199, 2-204
native VLANs 2-440 creating 2-182
nonegotiate displaying 2-312
DTP messaging 2-428 policers
speed 2-407 displaying 2-290
non-IP protocols for a single class 2-178
denying 2-62 for multiple classes 2-129, 2-180
forwarding 2-175 policed-DSCP map 2-135
non-IP traffic access lists 2-115 traffic classification
non-IP traffic forwarding defining the class 2-33
denying 2-62 defining trust states 2-453
permitting 2-175 setting DSCP or IP precedence values 2-202
normal-range VLANs 2-460, 2-466 Port Aggregation Protocol
note, description xvi See EtherChannel
no vlan command 2-460, 2-470 port-based authentication
AAA method list 2-1
debug messages, display B-6
P
enabling 802.1X
PAgP globally 2-77
See EtherChannel per interface 2-72
pagp learn-method command 2-171 guest VLAN 2-66
pagp port-priority command 2-173 host modes 2-67
password, VTP 2-484, 2-488 initialize an interface 2-69
password-recovery mechanism, enabling and manual control of authorization state 2-72
disabling 2-197 multiple hosts on authorized port 2-67
permit command 2-175
periodic re-authentication
per-VLAN spanning-tree plus enabling 2-76
See STP time between attempts 2-78
physical-port learner 2-171
quiet period between failed authentication
PIM-DVMRP, as multicast router learning method 2-104 exchanges 2-78
police aggregate command 2-180 re-authenticating 802.1X-enabled ports 2-74
police command 2-178 resetting configurable 802.1X parameters 2-65
policed-DSCP map 2-135 statistics and status display 2-232
policy-map command 2-182 switch-to-authentication server retransmission
time 2-78
switch-to-client frame-retransmission number 2-70
switch-to-client retransmission time 2-78
VTP (continued)
status 2-349
status display fields 2-351
vtp (global configuration) command 2-484
vtp (VLAN configuration) command 2-488