 Feedback
|
Table Of Contents
Finding the Software Version and Feature Set
Upgrading a Switch by Using CMS
Upgrading a Switch by Using the CLI
Copying the Current Startup Configuration from the Switch to a PC or Server
Using the CLI to Upgrade a Catalyst 2950 LRE or Catalyst 2940 Switch
Using the CLI to Upgrade a Catalyst 2955 Switch or Non-LRE Catalyst 2950 Switch
Recovering from Software Failure
Cisco IOS Limitations and Restrictions
LRE Limitations and Restrictions
Cluster Limitations and Restrictions
CMS Limitations and Restrictions
Catalyst 2950 Hardware and Software Compatibility Matrixes
Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA2
CMS Caveats Resolved in Cisco IOS Release 12.1(22)EA1
CMS Caveats Resolved in Cisco IOS Release 12.1(20)EA2
Additions to the System Messages Guides for All Switches
Addition to the Dynamic Trunking Protocol (DTP) Messages
Addition to the SW_VLAN Messages
Corrections for the Software Configuration Guides and Command References for All Switches
Correction to the Software Configuration Guides for All Switches
Revisions to the Catalyst 2950 and Catalyst 2955 Command Reference
Revisions to the Catalyst 2940 Switch Software Configuration Guide
Configuring Extended-Range VLANs
Extended-Range VLAN Configuration Guidelines
Creating an Extended-Range VLAN
Full-Range of VLAN IDs Supported
Chapter 8, Configuring 802.1x Port-Based Authentication
Revisions to the Catalyst 2940 Command Reference
Corrections and Additions to the Catalyst 2950 Hardware Installation Guide
Corrections and Additions to the Catalyst 2940 Hardware Installation Guide
Managing the Switch by Using the Cluster Management Suite Chapter
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Catalyst 2955, Catalyst 2950, and Catalyst 2940 Switches, Cisco IOS Release 12.1(22)EA1
Revised April, 2005
Cisco IOS Release 12.1(22)EA1 runs on Catalyst 2955, Catalyst 2950, and Catalyst 2940 switches.
Review the new software features, open caveats, and resolved caveats sections for information specific to your switch. The information in this document refers to all the switches, unless otherwise noted.
These release notes include important information about this release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:
•
If you are installing a new switch, refer to the Cisco IOS release label on the rear panel of your switch.
•
•
For the complete list of Catalyst 2955, Catalyst 2950, and Catalyst 2940 switch documentation, see the "Related Documentation" section.
You can download the switch software from these sites:
•
(for registered Cisco.com users with a login password)
•
(for nonregistered Cisco.com users)
This release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future releases become available, they will be posted to Cisco.com (previously Cisco Connection Online [CCO]) in the Cisco IOS software area.
Contents
This information is in the release notes:
•
•
•
•
•
•
•
•
•
System Requirements
The system requirements for this release are described in these sections:
•
•
•
Hardware Supported
The Catalyst 2950 switch is supported by either the standard software image (SI) or the enhanced software image (EI). The Catalyst 2950 Long-Reach Ethernet (LRE) and Catalyst 2955 switches are supported only by the EI. The Catalyst 2940 switch supports some of the features supported by a Catalyst 2950 switch running the SI.
The EI provides a richer set of features, including access control lists (ACLs), enhanced quality of service (QoS) features, and extended-range VLANs. The enhanced cryptographic software image supports the Secure Shell Version 2 (SSHv2) protocol.
For information about the software releases that support the switches listed in Table 1, see the "Catalyst 2950 Hardware and Software Compatibility Matrixes" section.
Table 1 and Table 2 list the hardware supported by this software release:
Table 1 Catalyst 2940, Catalyst 2950, and Catalyst 2955 Hardware Supported
Catalyst 2940-8TT-S
—1
8 10/100 Ethernet ports and 1 10/100/1000 Ethernet port
Catalyst 2940-8TF-S
—1
8 10/100 Ethernet ports, 1 SFP2 module slot, and 1 100BASE-FX port
Catalyst 2950-12
SI
12 fixed autosensing 10/100 Ethernet ports
Catalyst 2950-24
SI
24 fixed autosensing 10/100 Ethernet ports
Catalyst 2950C-24
EI
24 fixed autosensing 10/100 Ethernet ports and 2 100BASE-FX ports
Catalyst 2950G-12-EI
EI
12 fixed autosensing 10/100 Ethernet ports and 2 GBIC3 module slots
Catalyst 2950G-24-EI
EI
24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots
Catalyst 2950G-24-EI-DC
EI
24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots with DC-input power
Catalyst 2950G-48-EI
EI
48 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots
Catalyst 2950ST-8 LRE
EI
8 LRE ports, 2 10/100/1000 Ethernet ports4 , and 2 SFP module slots
Catalyst 2950ST-24 LRE
EI
24 LRE ports, 2 10/100/1000 Ethernet ports4, and 2 SFP module slots
Catalyst 2950ST-24 LRE 997
EI
24 LRE ports, 2 10/100/1000 Ethernet ports4, and 2 SFP module slots with DC-input power
Catalyst 2950SX-24
SI
24 fixed autosensing 10/100 Ethernet ports and 2 1000BASE-SX ports
Catalyst 2950SX-48-SI
SI
48 fixed autosensing10/100 Ethernet ports and 2 1000BASE-SX ports
Catalyst 2950T-24
EI
24 fixed autosensing 10/100 Ethernet ports and 2 10/100/1000 Ethernet ports5
Catalyst 2950T-48-SI
SI
48 fixed autosensing 10/100 Ethernet ports and 2 10/100/1000 Ethernet ports
Catalyst 2955C-12
EI
12 fixed autosensing 10/100 ports and 2 MM6 100BASE-FX ports
Catalyst 2955S-12
EI
12 fixed autosensing 10/100 ports and 2 SM7 100BASE-LX ports
Catalyst 2955T-12
EI
12 fixed autosensing 10/100 ports and 2 10/100/1000 Ethernet ports4
1 The Catalyst 2940 switch supports some of the features supported by a Catalyst 2950 switch running the SI.
2 SFP = small form-factor pluggable
3 GBIC = Gigabit Interface Converter
4 The 10/100/1000 ports on a Catalyst 2950 LRE or Catalyst 2955T-12 switch operate at 10 or 100 Mbps in either full- or half-duplex mode and at 1000 Mbps only in full-duplex mode.
5 The 10/100/1000 interfaces on the Catalyst 2950T-24 switch do not support the half keyword in the duplex command.
6 MM = multimode
7 SM = single mode
Table 2 Other Hardware Supported
Cisco 575 LRE CPE1
—
1 fixed 10/100 port
Cisco 576 LRE CPE 997
—
1 fixed 10/100 port
Cisco 585 LRE CPE
—
4 fixed 10/100 ports
GBIC modules
—
•
•
•
•
•
•
Redundant power system
—
•
•
SFP devices
—
•
•
•
•
•
1 CPE = customer premises equipment
2 CDWM = coarse wavelength-division multiplexing
3 This feature is only supported when your switch is running the EI.
4 DWDM = dense wavelength-division multiplexing
Hardware Not Supported
Table 3 lists the hardware that is not supported by this release.
Table 3 Hardware Not Supported
GBIC module
1000BASE-T GBIC (model WS-G4582)
Redundant power system
Cisco RPS 600 Redundant Power System
Software Compatibility
For information about the recommended platforms for web-based management, operating systems and browser support, the Cluster Management Suite (CMS) plug-in guidelines, and installation procedures, refer to the "Getting Started with CMS" chapter of the software configuration guide.
Windows
This release uses a CMS plug-in (Windows only) to run CMS. You can download the latest CMS plug-in for Windows from this URL:
http://www.cisco.com/pcgi-bin/Support/ClusterMgmtSuite/cms_plugin_redirect.cgi?platform=windows&version=1.1
Solaris
This release uses a CMS plug-in (Solaris only) that replaces the Java plug-in. You must download the CMS plug-in to run CMS. You can download the latest CMS plug-in for Solaris from this URL:
http://www.cisco.com/pcgi-bin/Support/ClusterMgmtSuite/cms_plugin_redirect.cgi?platform=solaris&version=1.1
Cluster Compatibility
This section describes how to choose command and standby command switches when a cluster consists of a mixture of Catalyst switches. When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
Table 4 Switch Software and Cluster Capability
Catalyst 3750
12.1(11)AX or later
Member or command switch
Catalyst 3750 Metro
12.1(14)AX or later
Member or command switch
Catalyst 3560
12.1(19)EA1b
Member or command switch
Catalyst 3550
12.1(4)EA1 or later
Member or command switch
Catalyst 2970
12.1(11)AX or later
Member or command switch
Catalyst 2955
12.1(12c)EA1 or later
Member or command switch
Catalyst 2950
12.0(5.2)WC(1) or later
Member or command switch
Catalyst 2950 LRE
12.1(11)JY or later
Member or command switch
Catalyst 2940
12.1(13)AY or later
Member or command switch
Catalyst 3500 XL
12.0(5.1)XU or later
Member or command switch
Catalyst 2900 XL (8-MB switches)
12.0(5.1)XU or later
Member or command switch
Catalyst 2900 XL (4-MB switches)
11.2(8.5)SA6 (recommended)
Member switch only1
Catalyst 1900 and 2820
9.00(-A or -EN) or later
Member switch only
1 Catalyst 2900 XL (4-MB) switches appear in the front-panel and topology views of the Cluster Management Suite (CMS). However, CMS does not support configuration or monitoring of these switches.
CMS is not forward-compatible on command switches running Cisco IOS Release 12.1(14)EA1 and earlier. This means that if a member switch is running a release that is earlier than the release running on the command switch, the new features are not available on the member switch. If the member switch is a new device running a release that is later than the release on the command switch, the command switch cannot recognize the member switch, and the Front Panel view displays it as an unknown device. You cannot configure any parameters or generate a report through CMS for that member; instead, you must launch the Device Manager application to configure and to obtain reports for that member.
Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of Cisco IOS software, software features added on the latest release might not be reflected on switches running the older releases. For example, if you start CMS on a Catalyst 2900 XL switch running Cisco IOS Release 11.2(8)SA6, the windows and functionality can be different from a switch running Cisco IOS Release 12.0(5)WC(1) or later.
Downloading Software
Before downloading software, read this section for important information. This section describes these procedures for downloading software:
•
•
•
•
•
For information about the software releases that support the switches, see the "Catalyst 2950 Hardware and Software Compatibility Matrixes" section.
Note
When you upgrade a switch, the switch continues to operate while the new software is copied to flash memory. If flash memory has enough space, the new image is copied to the selected switch but does not replace the running image until you reboot the switch. If a failure occurs during the copy process, you can still reboot your switch by using the old image. If flash memory does not have enough space for two images, the new image is copied over the existing one. Features provided by the new software are not available until you reload the switch.
If a failure occurs while copying a new image to the switch, and the old image has already been deleted, refer to the "Recovering from Corrupted Software" section in the "Troubleshooting" chapter of the software configuration guide for this release.
For information about upgrading the LRE switch firmware, refer to the "Upgrading LRE Switch Firmware" section in the software configuration guide for this release.
Caution
Caution
Finding the Software Version and Feature Set
The image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version user EXEC command to see the software version that is running on your switch. In the display, check the line that begins with System image file is. This line shows the directory name in flash memory where the image is stored. A couple of lines below the image name, you see Running Enhanced Image if you are running the EI or Running Standard Image if you are running the SI.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains both the Cisco IOS image file and the CMS files. You must use the combined tar file to upgrade the switch through the CMS.
The tar file is an archive file from which you can extract files by using the archive tar command.
Note
Table 5 lists the software filenames for this Cisco IOS release.
Table 5 Catalyst 2955, 2950, and Catalyst 2940 Cisco IOS Software Files
c2955-i6k2l2q4-tar.121-22.EA1.tar
Catalyst 2955 EI files. This includes the cryptographic Cisco IOS image and the CMS files.
c2955-i6q4l2-tar.121-22.EA1.tar
Catalyst 2955 EI files. This includes the Cisco IOS image and the CMS files.
c2950-i6k2l2q4-tar.121-22.EA1.tar
Catalyst 2950 SI1 and EI files. This includes the cryptographic Cisco IOS image and the CMS files.
c2950-i6q4l2-tar.121-22.EA1.tar
Catalyst 2950 SI and EI files. This includes the Cisco IOS image and the CMS files.
c2950lre-i6k2l2q4-tar.121-22.EA1.tar
Catalyst 2950 LRE EI files. This includes the cryptographic Cisco IOS image and the CMS files.
c2950lre-i6l2q4-tar.121-22.EA1.tar
Catalyst 2950 LRE EI files. This includes the Cisco IOS image and the CMS files.
c2940-i6q4l2-tar.121-22.EA1.tar
Catalyst 2940 files. This includes the Cisco IOS image and the CMS files.
1 Switches that support only the SI cannot run the cryptographic image. For more information, see the SI-only switches listed in Table 1 and the "Cisco IOS Limitations and Restrictions" section.
Upgrading a Switch by Using CMS
You can upgrade switch software by using CMS. From the menu bar, select Administration > Software Upgrade. For detailed instructions, click Help.
Upgrading a Switch by Using the CLI
To upgrade the switch software by using the CLI, see Table 5 to decide which software files that you need, and then follow these procedures in this order:
1.
2.
3.
–
–
Downloading the Software
This procedure is for copying the combined tar file to a switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
Follow these steps to download the software from Cisco.com to your management station:
Step 1
•
http://www.cisco.com/public/sw-center/sw-lan.shtml
•
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the files, click the link for your switch platform, and then follow the links on the page to select the correct tar image file.
Step 2
New features provided by the software are not available until you reload the software.
Copying the Current Startup Configuration from the Switch to a PC or Server
When you make changes to a switch configuration, your changes become part of the running configuration. When you enter the command to save those changes to the startup configuration, the switch copies the configuration to the config.text file in flash memory. To ensure that you can recreate the configuration if a switch fails, you might want to copy the config.text file from the switch to a TFTP server.
Beginning in privileged EXEC mode, follow these steps to copy a switch configuration file to the TFTP server.
Step 1
switch# copy flash:config.text tftpStep 2
Address or name of remote host []? ip_addressStep 3
Destination filename [config.text]? yes/noStep 4
Using the CLI to Upgrade a Catalyst 2950 LRE or Catalyst 2940 Switch
Use this procedure for upgrading your Catalyst 2950 LRE or Catalyst 2940 switch by using the archive download-sw privileged EXEC command to automatically extract and download the Cisco IOS image and the CMS files to the switch. The archive download-sw command initiates this process:
•
•
•
•
•
For further information on this command, see the command reference for this release.
Follow these steps to upgrade the switch software by using a TFTP transfer:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enable switch#Enter the password if you are prompted to do so.
Step 4
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, refer to the software configuration guide for this release.
Step 5
archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
Note
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case-sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/c2940-i612-tar.121-20.EA1.tarYou can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
Your Telnet session ends when the switch reloads.
After the switch reboots, use Telnet to return to the switch, and enter the show version user EXEC command to verify the upgrade procedure. If you have a previously opened browser session to the upgraded switch, close the browser, and start it again to ensure that you are using the latest HTML files.
Using the CLI to Upgrade a Catalyst 2955 Switch or Non-LRE Catalyst 2950 Switch
Use this procedure for upgrading your Catalyst 2955 or non-LRE Catalyst 2950 switch by copying the tar file to the switch. You copy the Cisco IOS image and the CMS files to the switch from a TFTP server and then extract the files by entering the archive tar command, with these results:
•
•
•
Caution
Before downloading the new image, use the dir user EXEC command to confirm that you have enough space on the flash. The new image and HTML files will be slightly larger than the size of the tar file.
If you do not have enough space on the flash for the tar file, delete any old unused IOS images. If that does not free up enough flash space, delete the HTML files.
Caution
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enable switch#Enter the password if you are prompted to do so.
Step 4
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 5
Caution
switch# archive tar /x tftp://server_ip_address/path/filename.tar flash: Loading /path/filename.tar from server_ip_address (via VLAN1):!) extracting info (110 bytes)extracting c2950-i6q4l2-mz.121-13.EA1c.bin (2239579 bytes)!!!!!!!!!!!!!!!!!!!!html/ (directory)extracting html/Detective.html.gz (1139 bytes)!extracting html/ieGraph.html.gz (553 bytes)extracting html/DrawGraph.html.gz (787 bytes)extracting html/GraphFrame.html.gz (802 bytes)!...Depending on the TFTP server being used, you might need to enter only one slash (/) after the server_ip_address in the archive tar command.
Step 6
switch# show boot BOOT path-list: flash:current_image Config file: flash:config.text Enable Break: 1 Manual Boot: no HELPER path-list: NVRAM/Config file buffer size: 32768Step 7
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 8
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2950-i6q4l2-mz.121-13.EA1c.bin
Note
Step 9
switch(config)# endStep 10
switch# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Step 11
Your Telnet session ends when the switch reloads.
After the switch reboots, use Telnet to return to the switch, and enter the show version user EXEC command to verify the upgrade procedure. If you have a previously opened browser session to the upgraded switch, close the browser, and start it again to ensure that you are using the latest CMS files.
Recovering from Software Failure
If the software fails, you can reload the software. For detailed recovery procedures, refer to the "Troubleshooting" chapter in the software configuration guide for your switch.
Installation Notes
You can assign IP information to your switch by using one of these methods:
•
Refer to the "Quick Setup" chapter in the Catalyst 2950 and Catalyst 2940 hardware installation guides for more information about Express Setup.
•
This procedure is described in the Catalyst 2955, Catalyst 2950, and Catalyst 2940 hardware installation guides.
•
•
New Features
These are the supported hardware and the software features provided in Cisco IOS Release 12.1(22)EA1.
New Hardware Features
For a complete list of supported hardware, see the "Hardware Supported" section.
New Software Features
This release contains these new Catalyst 2940 switch enhancements:
•
–
–
•
•
•
This release contains these new Catalyst 2940, 2950, and 2955 switch enhancements:
•
•
•
For more information about these feature enhancements, see the "Documentation Updates" section.
Limitations and Restrictions
You should review this section before you begin working with the switches. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
Note
These are the limitations and restrictions:
•
•
•
•
•
Cisco IOS Limitations and Restrictions
These limitations and restrictions apply to the Cisco IOS configuration:
•
•
•
The workaround is to make sure that the DHCP server contains reserved addresses that are bound to each switch by the switch hardware address so that the switch does not obtain its IP address from the dynamic pool. (CSCds58369)
•
•
•
•
–
–
There is no workaround. (CSCdt48011)
•
•
The workaround is to enable BackboneFast on all switches. (CSCdv02941)
•
The workaround is to manually re-initiate authentication by either logging off or detaching the link and then reconnecting it. (CSCdv19671)
•
The workaround is to not cross-connect VLANs. For example, do not use an access port to connect VLAN 1 to VLAN 65 on either the same switch or from one switch to another switch. (CSCdv27247)
•
•
The workaround is to set the mode to dynamic for Catalyst 2950 switches that are connected to IGMP-capable devices. The new group can join the multicast stream if another stream is dynamically removed from the group. (CSCdv45190)
•
The workaround is to connect Catalyst 3550 switches by using the access link on the command switches management VLAN or to configure an 802.1Q trunk with a native VLAN that is the same as the management VLAN of the command switch. (CSCdv49871)
•
The workaround is to configure both sides of a link to the same speed or use autonegotiation. (CSCdv62271)
•
The workaround is to manually enter the command again after a reboot. (CSCdv67047)
•
The workaround is to make sure that the management VLANs of all Catalyst 2900 XL or 3500 XL switches in the stack are set to VLAN 1. (CSCdv82224)
•
•
–
–
–
–
Note
There is no workaround. (CSCdw48441)
•
•
–
If the switch has 2 trunk ports, it can have up to 64 VLANs.
If the switch has 32 VLANs, it can have up to 4 trunk ports.
–
Note
If your switch has a saved configuration that does not meet the previous conditions and you upgrade the switch software to the cryptographic software image, the switch might run out of memory. If this happens, the switch does not operate properly. For example, it might continuously reload.
If the switch runs out of memory, this message appears:
%SYS-2-MALLOCFAIL: Memory allocation of (number_of_bytes) bytes failed ...The workaround is to check your switch configuration and ensure that it meets the previous conditions. (CSCdw66805)
•
The workaround is to specify an action in the policy map. (CSCdx75308)
•
If the join and leave messages arrive at high rate, the CPU can become busy processing these messages. For example, the CPU usage is approximately 50 percent when 50 pairs of join and leave messages are received each second. Depending on the rate at which join and leave messages are received, the CPU usage can go very high, even up to 100 percent, as the switch continues processing these messages.
The workaround is to only use the Immediate Leave processing feature on VLANs where a single host is connected to each port. (CSCdx95638)
•
The workaround is to manually assign an IP address to the switch. (CSCdy08716)
•
These are the workarounds:
–
–
•
•
The workaround is to configure the port as a static access port. (CSCdz32556)
•
There is no workaround. The number of interrupts does not affect the switch functionality. (CSCdz34545)
•
•
–
–
•
These are the workarounds:
–
switch# terminal length 0
–
–
•
The workaround is to match the configured VLANs on each side of the trunk port. (CSCea23138)
•
The workaround is to configure Port Fast globally by using the spanning-tree portfast global configuration command. (CSCea24969)
•
•
•
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to upThen the switch that restarted does not forward traffic until the spanning-tree state enters the forwarding state. This can occur on a switch running Cisco IOS Release 12.1(13)EA1 or later. (CSCea47230)
•
The workaround is to enter the shutdown and then the no shutdown interface configuration commands on the interface. (CSCeb36925)
•
Note
The workaround is to place the ports in static-access mode for a single VLAN, if the topology supports this configuration. (CSCec13986)
•
There is no workaround. (CSCed19922)
•
The workaround is to configure the port for 10 Mbps and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•
These are the workarounds:
–
–
•
Table 6 Port Security Incompatibility with Other Switch Features
No
No
No
No
No
Trunk port
No
No
Yes
Yes
Yes
Dynamic-access port3
No
No
No
No
No
Routed port
—
—
—
No
No
SPAN source port
Yes
Yes
Yes
Yes
Yes
SPAN destination port
No
No
No
No
No
EtherChannel
No
No
No
No
No
Tunneling port
—
—
—
Yes
—
Protected port
Yes
Yes
Yes
Yes
Yes
802.1x port
—
Yes4
Yes
Yes
Yes
Voice VLAN port5
Yes
Yes
Yes
Yes
Yes
Private VLAN port
—
—
—
—
No6
IP source guard
—
—
—
—
Yes6
Dynamic ARP7 inspection
—
—
—
—
Yes6
Flex Links
—
—
Yes
—
Yes
1 DTP = Dynamic Trunking Protocol
2 A port configured with the switchport mode dynamic interface configuration command.
3 A VLAN Query Protocol (VQP) port configured with the switchport access vlan dynamic interface configuration command.
4 The switch must be running the enhanced software image (EI).
5 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.
6 The switch must be running the enhanced multilayer image (EMI).
7 ARP = Address Resolution Protocol
LRE Limitations and Restrictions
These limitations only apply to Catalyst 2950 LRE switches:
•
There is no workaround. The Ethernet port on the Cisco 585 LRE CPE does not support VLANs. All the ports are assumed to be in the same VLAN. (CSCdx03708)
•
There is no workaround. You must ensure that the network does not send ISL tagged frames of sizes between 1537 and 1544 bytes to an LRE switch. (CSCdx25940)
•
There is no workaround; only 1000 buckets per interface are supported. (CSCdy38390)
•
http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/1000gbic/1000comp.htm.
The workaround is to use the Cisco 1000BASE-T GBIC only with compatible switches. (CSCdy53369)
•
•
The workaround is to use the switchport port-security maximum value interface configuration command to change the default value. For interfaces connected to Cisco 575 LRE and Cisco 576 LRE 997 CPEs, the default value can be 1. For interfaces connected to Cisco 585 LRE CPEs, the value can be 5 because the CPE has four Fast Ethernet ports and one additional MAC address. (CSCdy73748)
•
There is no workaround. These CPE Fast Ethernet statistics are supported by the Cisco 575 LRE CPE and the Cisco 576 LRE 997 CPE (CSCdy89348):
1 Transmit receive 0 bytes0 Bytes0 Unicast frames0 Broadcast frames0 Pause frames0 Alignment errors0 One collision frames0 Multiple collisions0 Undersize frames0 Late collisions0 Oversize frames0 Excess collisions0 FCS errors0 Deferred frames•
There is no workaround. (CSCdz06748)
•
•
There is no workaround. (CSCea41362)
•
•
The workaround is to reset the CPE port by using the cpe shutdown followed by the no cpe shutdown interface configuration command. This activates the Fast Ethernet link on the CPE port. (CSCeb35007)
Cluster Limitations and Restrictions
These limitations and restrictions apply to the cluster configuration:
•
•
The workaround is to ensure that the ports on the standby cluster members are not in the STP blocking state. Refer to the "Configuring STP" chapter in the software configuration guide for information about verifying port status. (CSCec31495)
CMS Limitations and Restrictions
These limitations apply to the Catalyst 2955, 2950, and 2940 switches:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The workaround is to add the address by using the router ospf <process-id>, area <area-id>, and range <address> <mask> configuration commands. (CSCed87031)
•
There is no workaround. (CSCee11710)
•
The workaround is to open the Port Settings dialog with CMS in read-write mode. (CSCee25870)
•
•
Catalyst 2950 Hardware and Software Compatibility Matrixes
Some Catalyst 2950 switches are not supported by certain software releases.
Table 7 lists the Catalyst 2950-12, 2950-24, 2950C-24, and 2950T-24 switches and the software releases supporting them. The serial numbers are on the switch rear panel. In this table, Yes means that the switch is supported by the software release; No means that the switch is not supported by the release.
The Catalyst 2950G-12-EI, 2950G-24-EI, 2950G-24-EI-DC, and 2950G-48-EI switches are supported by Cisco IOS Release 12.1(6)EA2 or later.
The Catalyst 2950SX-24 switches are supported by Cisco IOS Release 12.1(9)EA1d or later.
The Catalyst 2955 switches are supported by Cisco IOS Release 12.1(12c)EA1 or later.
The Catalyst 2950ST-8 LRE and 2950ST-24 LRE switches are supported by Cisco IOS Release 12.1(11)YJ or later.
The Catalyst 2950ST-24 LRE 997 switches are supported by Cisco IOS Release 12.1(11)YJ4 or later.
The Cisco LRE CPE devices are not supported by certain Catalyst 2950 LRE switches. In Table 8, Yes means that the CPE is supported by the switch; No means that the CPE is not supported by the switch.
Important Notes
Note
This section describes important information related to this release. These sections are included:
Cisco IOS Notes
These notes applies to Cisco IOS configuration:
•
If you have 802.1x configured on the switch and you upgrade to Cisco IOS Release 12.1(14)EA1 or later, the configuration file will not contain the new commands, and 802.1x will not operate. After the upgrade is complete, make sure to globally enable 802.1x by using the dot1x system-auth-control global configuration command. For more information, refer to the software configuration guide for this release.
•
•
•
•
The workaround is to change the number of seconds between re-authentication attempts by using the dot1x timeout re-authperiod seconds global configuration command. (CSCdz38483)
•
The workaround is to either release and renew the IP address or to change the default timers. These examples show typical interface timer changes:
dot1x timeout quiet-period 3
dot1x timeout tx-period 5
CMS Notes
These notes apply to CMS configuration:
•
•
•
•
•
•
The workaround is to resize the browser window again when CMS is not busy.
•
–
–
–
In the Front Panel view, if the switch is running one of the software releases listed previously, the device LEDs do not appear. In Topology view, if the member is an LRE switch, the CPE devices that are connected to the switch do not appear. The Bandwidth and Link graphs also do not appear in these views.
Open Caveats
These are the open caveats in this release:
•
Note
Open Cisco IOS Caveats
These are the open Cisco IOS configuration caveats:
•
When a community string is assigned by the cluster command switch, you cannot get any dot1dBridge MIB objects by using a community string with a VLAN entity from a cluster member switch.
The workaround is to manually add the cluster community string with the VLAN entity on the member switches for all active VLANs shown in the show spanning-tree summary display. This is an example of such a change, where cluster member 3 has spanning-tree on vlan 1-3 and the cluster commander community string is public@es3.
Switch(config)#snmp community public@es3@1 ROSwitch(config)#snmp community public@es3@2 ROSwitch(config)#snmp community public@es3@3 RO•
When UplinkFast is configured on a Catalyst 2950 or Catalyst 3550 switch, the MAC address of the switch is not forwarded to the uplink switch through the new link. This temporarily interrupts communication with the management VLAN and delays convergence of UplinkFast.
There is no workaround.
•
When a Catalyst 2950 is connected through a 100BASE-FX port to a media converter, it does not link up after being reloaded. You have to cycle power to the media converter to establish the link. This problem does not occur when the other device is a Catalyst 2950T or 3458-XL switch.
There is no workaround.
•
On specified ingress ports on a Catalyst 2950 switch, DSCP values are not marked correctly.
There is no workaround.
•
When the transmit period is configured to be greater than the quiet period, users can access a guest VLAN even though authentication of 802.1 x fails.
Workaround: Do not configure the transmit period to be greater than the quiet period.
•
If the VTP password is configured but the VTP domain name is not configured and if the switch reloads twice, the switch does not retain the VLAN information.
Use one of these workarounds:
–
–
–
•
If a 10/100/1000 port on a Catalyst 2950 switch is configured for 100 Mbps and full duplex and you change the flow-control configuration on the interface, the show interfaces privileged EXEC command output incorrectly shows the speed and duplex settings as 100 Mbps and half duplex. The show controllers privileged EXEC command output correctly shows the speed and duplex settings (100 Mbps and full duplex).
The workaround is to set the speed and duplex to autonegotiate.
•
When you shut down the 100BASE-FX port on the Catalyst 2950 switch, the upstream switch does not detect loss of link and line protocol stays up/up.
There is no workaround to the issue itself. However aggressive mode UDLD can be used when suitable.
Open CMS Caveats
These are the open severity 3 CMS configuration caveats:
•
When there are Catalyst 2950 and 2955 devices in a cluster, if you launch the QoS Queue Window to configure the devices and then try to view the settings for other devices by using the device selection menu, CMS halts after 20 to 30 selections.
The workaround is to close and then restart CMS.
•
When you change the Spanning Tree Protocol (STP) mode from Rapid PVST+ to PVST+, a Java OutOfBoundsException error sometimes appears.
There is no workaround. The new STP mode is still configured even if the error message appears.
•
When a Catalyst 3750 stack member leaves or joins the switch stack, the entire stack disappears from the Topology View. Only the stack member that has left the stack should disappear from the Topology view.
There is no workaround.
•
When you select a remote device from the VLAN menu, the displayed table sometimes does not show all the connected links between the device selected in the Host Name and the Remote Device lists. This can also occur when you add a new device to a cluster and then open VLAN menu.
This is the workaround:
1.
2.
•
The Device Manager Launch button does not work for Catalyst 1900 and 2820 switches.
The workaround is to launch Device Manager for these devices outside of CMS by opening a new browser and manually entering the URL for the switch.
•
When you click Refresh in the Stack Settings dialog, the latest information switch cluster does not appear.
The workaround is to close and then to reopen the Stack Settings dialog.
Resolved Caveats
These are the caveats that were resolved in this release:
•
•
•
•
Note
Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1
This Cisco IOS caveat was resolved in this release:
•
The link no longer fails to activate when 10/100-Mbps ports are interconnected through media converters and 100BASE-FX media.
•
Certain release trains of Cisco Internetwork Operating System (IOS), when configured to use the Cisco IOS Secure Shell (SSH) server in combination with Terminal Access Controller Access Control System Plus (TACACS+) as a means to perform remote management tasks on Cisco IOS devices, may contain two vulnerabilities that can potentially cause Cisco IOS devices to exhaust resources and reload. Repeated exploitation of these vulnerabilities can result in a Denial of Service (DoS) condition. Use of SSH with Remote Authentication Dial In User Service (RADIUS) is not affected by these vulnerabilities.
Cisco has made free software available to address these vulnerabilities for all affected customers. There are workarounds available to mitigate the effects of the vulnerability (see the "Workarounds" section of the full advisory for details.)
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20050406-ssh.shtml
•
Certain release trains of Cisco Internetwork Operating System (IOS), when configured to use the Cisco IOS Secure Shell (SSH) server in combination with Terminal Access Controller Access Control System Plus (TACACS+) as a means to perform remote management tasks on Cisco IOS devices, may contain two vulnerabilities that can potentially cause Cisco IOS devices to exhaust resources and reload. Repeated exploitation of these vulnerabilities can result in a Denial of Service (DoS) condition. Use of SSH with Remote Authentication Dial In UserService (RADIUS) is not affected by these vulnerabilities.
Cisco has made free software available to address these vulnerabilities for all affected customers. There are workarounds available to mitigate the effects of the vulnerability (see the "Workarounds" section of the full advisory for details.)
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20050406-ssh.shtml
•
If you shut down the default management VLAN and configure another VLAN as the management VLAN, the output from the show ip aliases privileged EXEC command shows the correct IP address information.
•
If you use the deny MAC access list configuration command to manually configure a MAC ACL, the MAC address list remains intact.
•
When the 10/100 interfaces on a 2940 Catalyst switch are oversubscribed, packets are no longer dropped. Performance is improved on UDP-based applications that are running on TCP/IP.
•
When outbound traffic exceeds interface speed, egress queuing is not supported on the Catalyst 2940 switch.
There is no workaround.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA2
These Cisco IOS caveats were resolved in release:
•
When you upgrade a Catalyst 2940 switch running Cisco IOS Release 12.1(13)AY, or downgrade a Catalyst 2940 switch to Cisco IOS Release 12.1(13)AY, the archive download-sw privileged EXEC command now works.
•
You can now obtain VLAN statistics information from clustered switches.
•
On a Catalyst 2950 or 2940 switch, these MIB entries no longer contain invalid characters:
entPhysicalHardwareReventPhysicalSerialNumThe switch can now be added to the CiscoWorks Resource Manager Essentials (RME) database.
•
On a Catalyst 2950 switch, initiating a ping by using the CISCO-PING-MIB interface no longer returns an error message.
•
When you create an RSPAN source session and the reflector port is configured on a port number higher than 24, the RSPAN session now works.
•
The output from the show interfaces interface-id privileged EXEC command now shows the correct media types for the SFP modules.
•
The switch now accepts duplicate remark statements in named ACLs.
•
When port security is enabled on an interface and the interface receives IGMP packets, the switch now learns the secure MAC address of the connected device. If the interface receives other types of packets, such as ICMP packets, the switch also learns the secure MAC address of the connected device.
CMS Caveats Resolved in Cisco IOS Release 12.1(22)EA1
These severity 3 CMS caveats were resolved in this release:
•
When you open the Port Settings dialog for a Power-over-Ethernet (PoE) switch that is a member of a switch stack and the stack master is not a PoE switch, a Java exception error no longer occurs.
•
When a switch cluster has only one member switch and that member switch is down, CMS now displays the Remove From Cluster option.
CMS Caveats Resolved in Cisco IOS Release 12.1(20)EA2
These severity 3 CMS caveats were resolved in this release:
•
In the IP Multicast Wizard, multicast-enabled member devices are now correctly listed in the Enabled Multicast list box instead of in the Current Candidate list box.
•
The Front Panel View now correctly displays the port LEDs.
Documentation Updates
This section provides updates to the product documentation. These changes will be included in the next documentation revisions.
•
•
•
•
•
•
•
•
Additions to the System Messages Guides for All Switches
These system messages are new for this release:
•
•
Addition to the Dynamic Trunking Protocol (DTP) Messages
Error Message DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch.Explanation The two ports involved in trunk negotiation belong to different VTP domains. Trunking is possible only when the ports involved belong to the same VTP domain. [chars] is the name of the interface.
Recommended Action Ensure that the two ports that are involved in trunk negotiation belong to the same VTP domain.
Addition to the SW_VLAN Messages
Error Message SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars].Explanation This message means that the VTP database is currently locked by another task and is not available. Retry the operation later. [chars] is the name of the function that has locked the VTP database.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section in Chapter 1 of the Catalyst 2940 Switch System Message Guide or the Catalyst 2950 and Catalyst 2955 Switch System Message Guide.
Corrections for the Software Configuration Guides and Command References for All Switches
This section provides updates to the product documentation for the Catalyst 2940 and Catalyst 2950 series switches. These changes will be included in the next revision of the documentation.
This information was omitted from the "Enabling Storm Control" section of the "Configuring Port-Based Traffic Control" chapter in the software configuration guides and from the "Usage Guidelines" section of the storm-control interface configuration command in the command references:
If you configure the action to be taken when a packet storm is detected as shutdown (the port is error-disabled during a storm), you must use the no shutdown interface configuration command to bring the interface out of this state. If you do not specify the shutdown action, specify the action as trap (the switch generates a trap when a storm is detected).
Correction to the Software Configuration Guides for All Switches
In the printed copies of the software configuration guides, the URL listed in the "Privilege Levels" section of the "Getting Started with CMS" chapter in the software configuration guides is incorrect. The section lists this URL:
http://ip_address/level/13
This is the correct URL (the closing "/" is required):
Revisions to the Catalyst 2950 and Catalyst 2955 Command Reference
These commands were added or revised to the Catalyst 2950 and Catalyst 2955 switch command reference:
duplex
Use the duplex interface configuration command to specify the duplex mode of operation for switch ports. Use the no form of this command to return to the default setting.
duplex {auto | full | half}
no duplex
Syntax Description
auto
Port automatically detects whether it should run in full- or half-duplex mode.
full
Port is in full-duplex mode.
half
Port is in half-duplex mode.
Defaults
For Fast Ethernet and 10/100/1000 ports, the default is auto.
For the default duplex mode of the Gigabit Interface Converter (GBIC)-module ports, refer to the documentation that came with your GBIC module.
For small, form-factor pluggable (SFP) Gigabit Ethernet ports on Catalyst 2950 LRE switches, the default is auto.
Command Modes
Interface configuration
Command History
Usage Guidelines
Certain ports, such as GBIC module ports, can be configured to be either full duplex or half duplex. The applicability of this command depends on the device to which the switch is attached.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.
Beginning with Cisco IOS Release 12.1(22)EA1, you can configure the duplex setting when the speed is set to auto.
If both the speed and duplex are set to specific values, autonegotiation is disabled.
For Fast Ethernet ports, setting the port to auto has the same effect as specifying half if the attached device does not autonegotiate the duplex parameter.
The 100BASE-FX ports on Catalyst 2950C-24 switches do not support the duplex interface configuration command. These ports only operate in full duplex and at 100 Mbps.
You can configure the 10/100/1000 ports on the Catalyst 2950T-24 and Catalyst 2950T-48-SI switches to autonegotiate the duplex mode by using the duplex auto interface configuration command. You can manually set the duplex mode to full by using the duplex full command. The 10/100/1000 ports support the half keyword only when the interface speed is 10 or 100 Mbps.
On Catalyst 2950 Long-Reach Ethernet (LRE) switches, use the duplex command to configure both the MAC and LRE chipsets.
A 10/100/1000 LRE switch port autonegotiates with the device at the other end of the link for the duplex setting and then forces the duplex setting to the negotiated value. A fiber-optic connection (SFP) also autonegotiates with the device at the other end of the link but only accepts a connection at full duplex.
The duplex setting for an SFP module Gigabit Ethernet port has a close relationship to the setting for speed. Fiber-optic connections are always forced to 1000 Mbps and full-duplex mode. Copper connections can run at either full- or half-duplex mode for 10 or 100 Mbps but are can only run in full-duplex mode at 1000 Mbps. When you manually set the speed and duplex settings, autonegotiation is disabled, and speed and duplex settings can cause a mismatch.
Note
Examples
This example shows how to set a port to half duplex:
Switch(config)# interface fastethernet0/1Switch(config-if)# duplex halfThis example shows how to set a port to full duplex:
Switch(config)# interface fastethernet0/1Switch(config-if)# duplex fullYou can verify your settings by entering the show interfaces transceiver properties or show running-config privileged EXEC command.
Related Commands
show controllers utilization
Use the show controllers utilization user EXEC command to display bandwidth utilization on the switch or specific ports.
show controllers [interface-id ] utilization [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
User EXEC
Command History
Usage Guidelines
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 controllers utilization command. Table 9 describes the fields in the output.
Switch> show controllers utilizationPort Receive Utilization Transmit UtilizationFa0/1 0 0Fa0/2 0 0<output truncated>Total Ports : 9Switch Receive Bandwidth Percentage Utilization : 0Switch Transmit Bandwidth Percentage Utilization : 0Switch Fabric Percentage Utilization : 0This is an example of output from the show controllers utilization command on a specific port:
Switch> show controllers Fa0/8 utilizationReceive Bandwidth Percentage Utilization : 0Transmit Bandwidth Percentage Utilization : 0
Related Commands
show interfaces
Use the show interfaces privileged EXEC command to display the administrative and operational status of all interfaces or a specified interface.
show interfaces [interface-id | vlan vlan-id] [accounting | capabilities [module {module-number]} | cpe [port port-id] | description | etherchannel | flowcontrol | media [interface-id] | pruning | stats | status [err-disabled] | switchport | trunk] | [ transceiver properties ] [ | {begin | exclude | include} expression]
Syntax Description
Note
Command Modes
Privileged EXEC
Command History
Usage Guidelines
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 interfaces accounting command:
Switch# show interfaces accountingVlan1Protocol Pkts In Chars In Pkts Out Chars OutIP 17950 2351279 3205 411175ARP 8626 552064 62 3720Interface Vlan5 is disabledFastEthernet0/1Protocol Pkts In Chars In Pkts Out Chars OutSpanning Tree 2956958 179218508 34383 2131700CDP 14301 5777240 14307 5722418VTP 0 0 1408 145908DTP 28592 1572560 0 0<output truncated>This is an example of output from the show interfaces capabilities command:
Switch# show interfaces fastethernet0/1 capabilitiesFastEthernet0/1Model: WS-C2950G-48-EIType: 10/100BaseTXSpeed: 10,100,autoDuplex: half,full,autoUDLD: yesTrunk encap. type: 802.1QTrunk mode: on,off,desirable,nonegotiateChannel: yesBroadcast suppression: percentage(0-100)Flowcontrol: rx-(none),tx-(none)Fast Start: yesCoS rewrite: yesToS rewrite: yesInline power: noSPAN: source/destinationPortSecure: YesDot1x: YesThis is an example of output from the show interfaces command for a specified interface:
Switch# show interfaces fastethernet0/1FastEthernet0/1 is up, line protocol is downHardware is Fast Ethernet, address is 0005.7428.09c1 (bia 0005.7428.09c1)MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Auto-duplex, Auto-speedinput flow-control is off, output flow-control is offLast input never, output 4d21h, output hang neverLast clearing of "show interface" counters neverInput queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec1 packets input, 64 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 0 multicast, 0 pause input0 input packets with dribble condition detected1 packets output, 64 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier, 0 PAUSE output0 output buffer failures, 0 output buffers swapped outThis is an example of output from the show interfaces description command for an interface when the interface has been described as Connects to Marketing by using the description interface configuration command.
Switch# show interfaces gigabitethernet0/1 descriptionInterface Status Protocol DescriptionGi0/1 up down Connects to MarketingThis is an example of output from the show interfaces pruning command for an interface when pruning is enabled in the VTP domain:
Switch# show interfaces fastethernet0/1 pruningPort Vlans pruned for lack of request by neighborFa0/1 4,196Port Vlan traffic requested of neighborFa0/1 1,4This is an example of output from the show interfaces stats command:
Switch# show interfaces statsVlan1Switching path Pkts In Chars In Pkts Out Chars OutProcessor 3224706 223689126 3277307 280637322Route cache 0 0 0 0Total 3224706 223689126 3277307 280637322Interface Vlan5 is disabledFastEthernet0/1Switching path Pkts In Chars In Pkts Out Chars OutProcessor 3286423 231672787 179501 17431060Route cache 0 0 0 0Total 3286423 231672787 179501 17431060This is an example of output from the show interfaces status command. It displays the status of all interfaces.
Switch# show interfaces statusPort Name Status Vlan Duplex Speed TypeFa0/1 notconnect 1 auto auto 10/100BaseTXFa0/2 notconnect 1 auto auto 10/100BaseTXFa0/3 disabled 100 auto auto 10/100BaseTXFa0/4 connected trunk a-full a-100 10/100BaseTXFa0/5 notconnect 1 auto auto 10/100BaseTXFa0/6 connected trunk a-full a-100 10/100BaseTX<output truncated>This is an example of output from the show interfaces status err-disabled command. It displays the status of interfaces in error-disabled state.
switch# show interfaces fastethernet0/1 status err-disabledPort Name Status ReasonFa0/1 err-disabled psecure-violationThis is an example of output from the show interfaces etherchannel command when port channels are configured on the switch:
Switch# show interfaces etherchannel----FastEthernet0/1:Port state = Up Mstr In-BndlChannel group = 1 Mode = On/FEC Gcchange = 0Port-channel = Po1 GC = 0x00010001 Pseudo port-channel = Po1Port index = 0 Load = 0x00Age of the port in the current state:00d:00h:06m:54s----Port-channel1:Age of the Port-channel = 09d:22h:45m:14sLogical slot/port = 1/0 Number of ports = 1GC = 0x00010001 HotStandBy port = nullPort state = Port-channel Ag-InusePorts in the Port-channel:Index Load Port EC state------+------+------+------------0 00 Fa0/1 onTime since last port bundled: 00d:00h:06m:54s Fa0/1This is an example of output from the show interfaces flowcontrol command. Table 10 lists the fields in this display.
Switch# show interfaces flowcontrolPort Send FlowControl Receive FlowControl RxPause TxPauseadmin oper admin oper----- -------- -------- -------- -------- ------- -------Fa0/1 Unsupp. Unsupp. off off 0 0Fa0/2 Unsupp. Unsupp. off off 0 0<output truncated>Gi0/1 desired off off off 0 0
This is an example of output from the show interfaces switchport command for a single interface. Table 11 describes the fields in the output.
Switch# show interfaces gigabitethernet0/1 switchportName: Gi0/1Switchport:EnabledAdministrative Mode:dynamic desirableOperational Mode:static accessAdministrative Trunking Encapsulation:negotiateNegotiation of Trunking:OnAccess Mode VLAN:1 (default)Trunking Native Mode VLAN:1 (default)Voice VLAN:noneAdministrative private-vlan host-association:noneAdministrative private-vlan mapping:noneOperational private-vlan:noneTrunking VLANs Enabled:ALLPruning VLANs Enabled:2-1001Capture Mode: DisabledCapture VLANs Allowed:ALLProtected:trueUnknown unicast blocked:disabledUnknown multicast blocked:disabledVoice VLAN:none (Inactive)Appliance trust:none
This is an example of output from the show interfaces trunk command:
Switch# show interfaces trunkPort Mode Encapsulation Status Native vlanFa0/4 on 802.1q trunking 1Fa0/6 on 802.1q trunking 1Port Vlans allowed on trunkFa0/4 1-4094Fa0/6 1-4094Port Vlans allowed and active in management domainFa0/4 1-2,51-52Fa0/6 1-2,51-52Port Vlans in spanning tree forwarding state and not prunedFa0/4 1Fa0/6 1-2,51-52This is an example of output from the show interfaces trunk command for an interface. It displays trunking information for the interface.
Switch# show interfaces fastethernet0/1 trunkPort Mode Encapsulation Status Native vlanFa0/1 desirable 802.1q trunking 1Port Vlans allowed on trunkFa0/1 1-4094Port Vlans allowed and active in management domainFa0/1 1,4,196,306Port Vlans in spanning tree forwarding state and not prunedFa0/1 1,306This is an example of output from the show interfaces transceiver properties command. If you do not specify an interface, the output of the command shows the status on all switch ports:
Switch# show interfaces transceiver propertiesName : Fa0/1Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 100Operational Duplex: fullOperational Auto-MDIX: N/AName : Fa0/2Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 10Operational Duplex: fullOperational Auto-MDIX: N/AName : Fa0/3Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 100Operational Duplex: fullOperational Auto-MDIX: N/A<output truncated>This is an example of output from the show interfaces module number transceiver properties command for a specific interface:
Switch# show interfaces fastethernet0/1 transceiver propertiesName : Fa0/1Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 100Operational Duplex: fullOperational Auto-MDIX: N/AThis is an example of output from the show interfaces command for an LRE port:
Switch# show interfaces longreachethernet0/5LongReachEthernet0/5 is up, line protocol is upHardware is Ethernet over LRE, address is 0006.2871.5902 (bia 0006.2871.5902)MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive not setHalf-duplex, Auto Speed (10), 100BaseTX/FXARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:21, output 00:00:00, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec8272 packets input, 852898 bytes, 0 no bufferReceived 1182 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 1182 multicast0 input packets with dribble condition detected61899 packets output, 17981033 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outThis is an example of output from the show interfaces command for all interfaces on a CPE device:
Switch# show interfaces longreachethernet0/2 cpePort Status Speed Duplex---- ------------ ----- ------1 notconnected auto NA2 notconnected auto NA3 notconnected auto NA4 notconnected auto NA5 connected 100 halfSwitch#This is an example of output from the show interfaces command for a port on a CPE device:
Switch# show interfaces longreachethernet0/2 cpe port 5Port Status Speed Duplex---- ------------ ----- ------5 connected 100 halfSwitch#This is an example of output from the show interfaces media command on an interface:
Switch# show interfaces gigabitethernet0/1 mediaPort Media-configured Active AttachedGi0/1 auto-select rj45 1000BaseSX-10/100/1000BaseTXSwitch#This is an example of output from the show interfaces media command:
Switch# show interfaces mediaPort Media-configured Active AttachedGi0/1 auto-select rj45 1000BaseSX-10/100/1000BaseTXGi0/2 prefer-sfp sfp 1000BaseSX-10/100/1000BaseTXRelated Commands
speed
Use the speed interface configuration command to specify the speed of a port. Use the no form of this command to return to the default setting.
speed {10 | 100 | 1000 | auto [ 10 | 100 | 1000 ] | nonegotiate}
no speed
Note
Syntax Description
Defaults
For Fast Ethernet and 10/100/1000 ports, the default is auto.
For 100BASE-FX ports, the default is 100 Mbps.
For GBIC-module ports, the default is 1000 Mbps.
For small form-factor pluggable (SFP)-module ports, the default is auto.
Command Modes
Interface configuration
Command History
12.0(5.2)WC(1)
This command was introduced.
12.1(11)EA1
The nonegotiate keyword was added.
12.1(22)EA1
Support for the 10, 10, and 1000 keywords with the auto keyword was added.
Usage Guidelines
The applicability of this command depends on the switch on which you enter this command.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch. If both the speed and duplex are set to specific values, autonegotiation is disabled.
If the speed is set to auto and the 10, 100, or 1000 keywords are also used, the port only autonegotiates at the specified speeds.
On non-Long-Reach Ethernet (LRE) switches, Fast Ethernet ports, except for 100BASE-FX ports, can be configured at 10 or 100 Mbps. The 10/100/1000 Ethernet interfaces on the Catalyst 2950T-24, Catalyst 2950T-48-SI, and Catalyst 2955T-24 switches operate at 10 or 100 Mbps in either half- or full-duplex mode or at 1000 Mbps only in full-duplex mode.
You cannot configure the speed on GBIC interfaces, but you can configure the speed to not negotiate (nonegotiate) for the 1000BASE-SX, -LX, or -ZX GBICs if they are connected to devices that do not support autonegotiation. GBIC-module ports support only 1000 Mbps. The speed values of 10 Mbps and 100 Mbps are not supported.
Note
On LRE switches, LRE Gigabit Ethernet ports are set to auto by default. A copper connection (10/100/1000) autonegotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. A fiber-optic SFP connection also autonegotiates with the device at the other end of the link but only accepts a connection at 1000 Mbps.
SFP modules only operate at 1000 Mbps, and those with a 1000 BASE-T module installed can only be configured for full-duplex mode.
On LRE switches, the speed setting for a Gigabit Ethernet port has a close relationship to the setting for duplex mode. Fiber-optic SFP-module ports are always forced to 1000 Mbps and to full-duplex mode. Copper ports can run in either full- or half-duplex module at 10 or 100 Mbps but are forced to run in full-duplex mode at 1000Mbps. When you configure the speed and duplex settings, autonegotiation is disabled, and speed and duplex settings can cause a mismatch.
The speed command is not supported on LRE interfaces. Use the cpe speed interface configuration command to set the speed of individual customer premises equipment (CPE) ports.
Note
Examples
This example shows how to set a port to 100 Mbps:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed 100This example shows how to set a port to autonegotiate the speed:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed autoThis example shows how to set a port to autonegotiate at only 10 Mbps:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed auto 10This example shows how to set a port to autonegotiate at only 10 or 100 Mbps:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed auto 10 100You can verify your settings by entering the show interfaces transceiver properties or the show running-config privileged EXEC command.
Related Commands
Revisions to the Catalyst 2940 Switch Software Configuration Guide
The updates in this section should be added to Chapter 14, Configuring VLANs, before the "Displaying VLANs" section on page 14-10:
•
•
•
•
•
Configuring Extended-Range VLANs
When the switch is in VTP transparent mode (VTP disabled), you can create extended-range VLANs (in the range 1006 to 4094 for any switch port commands that allow VLAN IDs). Enter the vlan vlan-id global configuration command to access config-vlan mode and to configure extended-range VLANs. The VLAN database configuration mode (that you access by entering the vlan database privileged EXEC command) does not support the extended range.
Extended-range VLAN configurations are not stored in the VLAN database. Because VTP mode is transparent, they are stored in the switch running configuration file. You can save the configuration in the startup configuration file by using the copy running-config startup-config privileged EXEC command.
Default VLAN Configuration
Refer to Table 14-2 on page 14-7 of the Catalyst 2940 Software Configuration Guide for IOS Release 12.1(20)EA2 for the default configuration for Ethernet VLANs. You can change only the MTU size on extended-range VLANs; all other characteristics must remain at the default state.
Extended-Range VLAN Configuration Guidelines
Follow these guidelines when creating extended-range VLANs:
•
•
•
•
•
•
•
Creating an Extended-Range VLAN
You create an extended-range VLAN in global configuration mode by entering the vlan global configuration command with a VLAN ID from 1006 to 4094. This command accesses the config-vlan mode. The extended-range VLAN has the default Ethernet VLAN characteristics and the MTU size is the only parameter you can change. Refer to the description of the vlan global configuration command in the command reference for defaults of all parameters. If you enter an extended-range VLAN ID when the switch is not in VTP transparent mode, an error message is generated when you exit from config-vlan mode, and the extended-range VLAN is not created.
Extended-range VLANs are not saved in the VLAN database; they are saved in the switch running configuration file. You can save the extended-range VLAN configuration in the switch startup configuration file by using the copy running-config startup-config privileged EXEC command.
Beginning in privileged EXEC mode, follow these steps to create an extended-range VLAN:
To delete an extended-range VLAN, use the no vlan vlan-id global configuration command.
The procedure for assigning static-access ports to an extended-range VLAN is the same as for normal-range VLANs.
This example shows how to create a new extended-range VLAN with all default characteristics, enter config-vlan mode, and save the new VLAN in the switch startup configuration file:
Switch(config)# vtp mode transparentSwitch(config)# vlan 2000Switch(config-vlan)# endSwitch# copy running-config startup configFull-Range of VLAN IDs Supported
The software configuration guide has been updated throughout to reflect support for the full range of 1 to 4094 VLAN IDs that are allowed by the IEEE 802.1Q standard and support for 12 spanning-tree instances and 12 active VLANs.
Chapter 8, Configuring 802.1x Port-Based Authentication
The "Using 802.1x with Guest VLAN" section and the "Configuring a Guest VLAN" section in the software configuration guide has been updated to support 802.1x with guest VLAN:
•
•
Using 802.1x with Guest VLAN
You can configure a guest VLAN for each 802.1x port on the switch to provide limited services to clients (for example, downloading the 802.1x client). These clients might be upgrading their system for 802.1x authentication, and some hosts, such as Windows 98 systems, might not be 802.1x-capable.
If an 802.1x port is configured, the switch assigns clients to a guest VLAN for the 802.1x port when one of these situations occurs:
•
•
•
Any number of hosts have access after the switch port is moved to the guest VLAN. If an 802.1x-capable host joins the same port on which the guest VLAN is configured, the port is put into the unauthorized state in the user-configured access VLAN, and authentication is restarted.
Guest VLANs are supported on 802.1x ports in single-host and multiple-hosts modes.
You can configure any VLAN, except RSPAN VLANs or voice VLAN IDs (VVIDs), as an 802.1x guest VLAN. The guest VLAN feature is not supported on trunk ports; it is supported only on access ports.
For configuration steps, see the "Configuring a Guest VLAN" section.
Configuring a Guest VLAN
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 EAPOL request/identity frame. Clients that are 802.1x-capable but fail authentication are not granted access to the network. The switch supports guest VLANs in single-host or multiple-hosts mode.
Beginning in privileged EXEC mode, follow these steps to configure a guest VLAN. This procedure is optional.
To disable and remove the guest VLAN, use the no dot1x guest-vlan interface configuration command. The port returns to the unauthorized state.
This example shows how to enable VLAN 9 as an 802.1x guest VLAN on a port:
Switch(config)# interface fastethernet0/1Switch(config-if)# dot1x guest-vlan 9This example shows how to set 3 as the quiet time on the switch, to set 15 as the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request, and to enable VLAN 2 as an 802.1x guest VLAN when an 802.1x port is connected to a DHCP client:
Switch(config-if)# dot1x timeout quiet-period 3Switch(config-if)# dot1x timeout tx-period 15Switch(config-if)# dot1x guest-vlan 2Revisions to the Catalyst 2940 Command Reference
This guide has been updated throughout to reflect support for the full range of 1 to 4094 VLAN IDs that are allowed by the IEEE 802.1Q standard and support for 12 spanning-tree instances and 12 active VLANs.
For most commands with a vlan vlan-id keyword, the valid VLAN ID range is now from 1 to 4094.
If VTP mode is transparent, you can use the vlan global configuration command to create extended VLANs (with VLAN IDs of 1006 to 4094) and enter config-vlan mode.
Note
The following commands were added or revised to the Catalyst 2940 switch command reference:
•
duplex
Use the duplex interface configuration command to specify the duplex mode of operation for switch ports. Use the no form of this command to return to the default setting.
duplex {auto | full | half}
no duplex
Syntax Description
auto
Port automatically detects whether it should run in full- or half-duplex mode.
full
Port is in full-duplex mode.
half
Port is in half-duplex mode.
Defaults
For Fast Ethernet and 10/100/1000 ports, the default is auto.
For 100BASE-FX and small form-factor pluggable (SFP) modules, the default is full.
Command Modes
Interface configuration
Command History
Usage Guidelines
Certain ports, such as Fast Ethernet or 10/100/1000 ports, can be configured as either full duplex or half duplex. How you apply this command depends on the device to which the switch is attached.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.
Beginning with Cisco IOS Release 12.1(22)EA1, you can configure the duplex setting when the speed is set to auto.
If both the speed and duplex are set to specific values, autonegotiation is disabled.
For Fast Ethernet ports, setting the port to auto has the same effect as specifying half if the attached device does not autonegotiate the duplex parameter.
The 100BASE-FX ports do not support the duplex interface configuration command. These ports only operate in full-duplex mode and at 100 Mbps.
Note
Examples
This example shows how to set a port to half duplex:
Switch(config)# interface fastethernet0/1Switch(config-if)# duplex halfThis example shows how to set a port to full duplex:
Switch(config)# interface fastethernet0/1Switch(config-if)# duplex fullYou can verify your settings by entering the show interfaces transceiver properties or show running-config privileged EXEC command.
Related Commands
show controllers utilization
Use the show controllers utilization user EXEC command to display bandwidth utilization on the switch or specific ports.
show controllers [interface-id ] utilization [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
User EXEC
Command History
Usage Guidelines
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 controllers utilization command. Table 12 describes the fields in the output.
Switch> show controllers utilizationPort Receive Utilization Transmit UtilizationFa0/1 0 0Fa0/2 0 0<output truncated>Total Ports : 9Switch Receive Bandwidth Percentage Utilization : 0Switch Transmit Bandwidth Percentage Utilization : 0Switch Fabric Percentage Utilization : 0This is an example of output from the show controllers utilization command on a specific port:
Switch> show controllers Fa0/8 utilizationReceive Bandwidth Percentage Utilization : 0Transmit Bandwidth Percentage Utilization : 0
Related Commands
show interfaces
Use the show interfaces privileged EXEC command to display the administrative and operational status of all interfaces or a specified interface.
show interfaces [interface-id | vlan vlan-id] [accounting | capabilities [module {module-number]} | description | etherchannel | flowcontrol | pruning | stats | status [err-disabled] | switchport | trunk] | [ transceiver properties ] [ | {begin | exclude | include} expression]
Syntax Description
Note
Command Modes
Privileged EXEC
Command History
12.1(13)AY
This command was introduced.
12.1(22)EA1
The transceiver and properties keywords were added.
Usage Guidelines
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 interfaces accounting command:
Switch# show interfaces accountingVlan1Protocol Pkts In Chars In Pkts Out Chars OutIP 17950 2351279 3205 411175ARP 8626 552064 62 3720Interface Vlan5 is disabledFastEthernet0/1Protocol Pkts In Chars In Pkts Out Chars OutSpanning Tree 2956958 179218508 34383 2131700CDP 14301 5777240 14307 5722418VTP 0 0 1408 145908DTP 28592 1572560 0 0<output truncated>This is an example of output from the show interfaces capabilities command:
Switch# show interfaces fastethernet0/1 capabilitiesFastEthernet0/1Model: WS-C2940-8TF-SType: 10/100BaseTXSpeed: 10,100,autoDuplex: half,full,autoUDLD: yesTrunk encap. type: 802.1QTrunk mode: on,off,desirable,nonegotiateChannel: yesBroadcast suppression: percentage(0-100)Flowcontrol: rx-(none),tx-(none)Fast Start: yesCoS rewrite: yesToS rewrite: yesInline power: noSPAN: source/destinationPortSecure: YesDot1x: YesThis is an example of output from the show interfaces command for a specified interface:
Switch# show interfaces fastethernet0/1FastEthernet0/1 is up, line protocol is downHardware is Fast Ethernet, address is 0005.7428.09c1 (bia 0005.7428.09c1)MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Auto-duplex, Auto-speedinput flow-control is off, output flow-control is offLast input never, output 4d21h, output hang neverLast clearing of "show interface" counters neverInput queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec1 packets input, 64 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 0 multicast, 0 pause input0 input packets with dribble condition detected1 packets output, 64 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier, 0 PAUSE output0 output buffer failures, 0 output buffers swapped outThis is an example of output from the show interfaces description command for an interface when the interface has been described as Connects to Marketing by using the description interface configuration command.
Switch# show interfaces gigabitethernet0/1 descriptionInterface Status Protocol DescriptionGi0/1 up down Connects to MarketingThis is an example of output from the show interfaces pruning command for an interface when pruning is enabled in the VTP domain:
Switch# show interfaces fastethernet0/1 pruningPort Vlans pruned for lack of request by neighborFa0/1 4,196Port Vlan traffic requested of neighborFa0/1 1,4This is an example of output from the show interfaces stats command:
Switch# show interfaces statsVlan1Switching path Pkts In Chars In Pkts Out Chars OutProcessor 3224706 223689126 3277307 280637322Route cache 0 0 0 0Total 3224706 223689126 3277307 280637322Interface Vlan5 is disabledFastEthernet0/1Switching path Pkts In Chars In Pkts Out Chars OutProcessor 3286423 231672787 179501 17431060Route cache 0 0 0 0Total 3286423 231672787 179501 17431060This is an example of output from the show interfaces status command. It displays the status of all interfaces.
Switch# show interfaces statusPort Name Status Vlan Duplex Speed TypeFa0/1 notconnect 1 auto auto 10/100BaseTXFa0/2 notconnect 1 auto auto 10/100BaseTXFa0/3 disabled 100 auto auto 10/100BaseTXFa0/4 connected trunk a-full a-100 10/100BaseTXFa0/5 notconnect 1 auto auto 10/100BaseTXFa0/6 connected trunk a-full a-100 10/100BaseTX<output truncated>This is an example of output from the show interfaces status err-disabled command. It displays the status of interfaces in error-disabled state.
switch# show interfaces fastethernet0/1 status err-disabledPort Name Status ReasonFa0/1 err-disabled psecure-violationThis is an example of output from the show interfaces etherchannel command when port channels are configured on the switch:
Switch# show interfaces etherchannel----FastEthernet0/1:Port state = Up Mstr In-BndlChannel group = 1 Mode = On/FEC Gcchange = 0Port-channel = Po1 GC = 0x00010001 Pseudo port-channel = Po1Port index = 0 Load = 0x00Age of the port in the current state:00d:00h:06m:54s----Port-channel1:Age of the Port-channel = 09d:22h:45m:14sLogical slot/port = 1/0 Number of ports = 1GC = 0x00010001 HotStandBy port = nullPort state = Port-channel Ag-InusePorts in the Port-channel:Index Load Port EC state------+------+------+------------0 00 Fa0/1 onTime since last port bundled: 00d:00h:06m:54s Fa0/1This is an example of output from the show interfaces flowcontrol command. Table 13 lists the fields in this display.
Switch# show interfaces flowcontrolPort Send FlowControl Receive FlowControl RxPause TxPauseadmin oper admin oper----- -------- -------- -------- -------- ------- -------Fa0/1 Unsupp. Unsupp. off off 0 0Fa0/2 Unsupp. Unsupp. off off 0 0<output truncated>Gi0/1 desired off off off 0 0
This is an example of output from the show interfaces switchport command for a single interface. Table 14 describes the fields in the output.
Switch# show interfaces gigabitethernet0/1 switchportName: Gi0/1Switchport:EnabledAdministrative Mode:dynamic desirableOperational Mode:static accessAdministrative Trunking Encapsulation:negotiateNegotiation of Trunking:OnAccess Mode VLAN:1 (default)Trunking Native Mode VLAN:1 (default)Voice VLAN:noneAdministrative private-vlan host-association:noneAdministrative private-vlan mapping:noneOperational private-vlan:noneTrunking VLANs Enabled:ALLPruning VLANs Enabled:2-1001Capture Mode: DisabledCapture VLANs Allowed:ALLProtected:trueUnknown unicast blocked:disabledUnknown multicast blocked:disabledVoice VLAN:none (Inactive)Appliance trust:none
This is an example of output from the show interfaces trunk command:
Switch# show interfaces trunkPort Mode Encapsulation Status Native vlanFa0/4 on 802.1q trunking 1Fa0/6 on 802.1q trunking 1Port Vlans allowed on trunkFa0/4 1-4094Fa0/6 1-4094Port Vlans allowed and active in management domainFa0/4 1-2,51-52Fa0/6 1-2,51-52Port Vlans in spanning tree forwarding state and not prunedFa0/4 1Fa0/6 1-2,51-52This is an example of output from the show interfaces trunk command for an interface. It displays trunking information for the interface.
Switch# show interfaces fastethernet0/1 trunkPort Mode Encapsulation Status Native vlanFa0/1 desirable 802.1q trunking 1Port Vlans allowed on trunkFa0/1 1-4094Port Vlans allowed and active in management domainFa0/1 1,4,196,306Port Vlans in spanning tree forwarding state and not prunedFa0/1 1,306This is an example of output from the show interfaces transceiver properties command. If you do not specify an interface, the output of the command shows the status on all switch ports:
Switch# show interfaces transceiver propertiesName : Fa0/1Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 100Operational Duplex: fullOperational Auto-MDIX: N/AName : Fa0/2Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 10Operational Duplex: fullOperational Auto-MDIX: N/AName : Fa0/3Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 100Operational Duplex: fullOperational Auto-MDIX: N/A<output truncated>This is an example of output from the show interfaces module number transceiver properties command for a specific interface:
Switch# show interfaces fastethernet0/1 transceiver propertiesName : Fa0/1Administrative Speed: autoAdministrative Duplex: autoAdministrative Auto-MDIX: N/AAdministrative Power Inline: N/AOperational Speed: 100Operational Duplex: fullOperational Auto-MDIX: N/ARelated Commands
speed
Use the speed interface configuration command to specify the speed of a port. Use the no form of this command to return to the default setting.
speed {10 | 100 | 1000 | auto [ 10 | 100 | 1000 ] }
no speed
Syntax Description
Defaults
For Fast Ethernet and 10/100/1000 ports, the default is auto.
For 100BASE-FX ports, the default is 100 Mbps.
For small form-factor pluggable (SFP) modules, the default is 1000 Mbps.
Command Modes
Interface configuration
Command History
12.1(13)AY
This command was introduced.
12.1(22)EA1
Support for the 10, 10, and 1000 keywords with the auto keyword was added.
Usage Guidelines
The applicability of this command depends on the switch on which you enter this command.
Fast Ethernet ports, except for 100BASE-FX ports, can be configured at 10 or 100 Mbps in half- or full-duplex mode. The 10/100/1000 ports operate in half- or full-duplex mode at 10 or 100 Mbps and in full-duplex mode only at 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 the speed and duplex are set to specific values, autonegotiation is disabled.
If the speed is set to auto and the 10, 100, or 1000 keywords are also used, the port only autonegotiates at the specified speeds.
Note
Note
Examples
This example shows how to set a port to 100 Mbps:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed 100This example shows how to set a port to autonegotiate the speed:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed autoThis example shows how to set a port to autonegotiate at only 10 Mbps:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed auto 10This example shows how to set a port to autonegotiate at only 10 or 100 Mbps:
Switch(config)# interface fastethernet0/1Switch(config-if)# speed auto 10 100You can verify your settings by entering the show interfaces transceiver properties or the show running-config privileged EXEC command.
Related Commands
Corrections and Additions to the Catalyst 2950 Hardware Installation Guide
These chapters have changed or have new information:
•
•
Quick Setup Chapter
This is a correction to the "Quick Setup" section:
The chapter states that the Express Setup program is supported on Catalyst 2950 LRE switches running Cisco IOS Release 12.1(14)EA1 or later. Express Setup is only supported on Catalyst 2950 LRE switches running Cisco IOS Release 12.1(19)EA1 or later.
This is a new step in the "Configuring the Switch Settings" section:
Step 2
Enter a VLAN ID in the Management Interface (VLAN ID) field. This is the management interface through which you manage the switch and to which you assign IP information. The Management Interface field displays 1 by default. The VLAN ID range for this field is 1 to 1001.
Installation Chapter
This an addition to the "Installation Guidelines" section:
For sites requiring compliance to Telcordia GR-1089-CORE Intra-building Lightning requirements, all 10/100 and 10/100/1000 ports must be connected with shielded cable grounded at both ends.
This is a new section in the "Installation" chapter:
Installing the Optional AC Ground Kit for Catalyst 2950 Switches
For switches that require a two-hole lug for grounding, you can order a kit containing the ground lug and hardware (Cisco part number NEBS-LUG-3550=).
Note
To install the ground lug, you need these tools and equipment:
•
•
•
•
To ground the switch to earth ground, follow these steps. Make sure to follow any grounding requirements at your site.
Step 1
Figure 1 Attaching the RPS Connector Cover
Step 2
Figure 2 Stripping the Ground Wire
Step 3
Step 4
Figure 3 Crimping the Ground Lug
Step 5
Step 6
Figure 4 Torquing Ground-Lug Screws
Corrections and Additions to the Catalyst 2940 Hardware Installation Guide
These chapters have changed or have new information:
•
•
Quick Setup Chapter
This is a new step in the "Configuring the Switch Settings" section:
Step 2
Enter a VLAN ID in the Management Interface (VLAN ID) field. This is the management interface through which you manage the switch and to which you assign IP information. The Management Interface field displays 1 by default. The VLAN ID range for this field is 1 to 1001.
Overview Chapter
This is an addition to the "Features" section:
The Catalyst 2940-8TF-S switch now supports CWDM SFP modules.
Managing the Switch by Using the Cluster Management Suite Chapter
This is a correction to the "CMS Requirements" section:
The CMS requirements described are no longer correct. Refer to the "Getting Started with CMS" chapter of the software configuration guide for the latest CMS requirements.
Related Documentation
These documents provide complete information about the Catalyst 2955, 2950, and 2940 switches and are available at Cisco.com:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2940/index.htm
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the "Obtaining Documentation" section.
These publications provide more information about the Catalyst 2955 and Catalyst 2950 switches:
•
•
•
•
•
These publications provide more information about the Catalyst 2940 switches:
•
•
•
•
•
For other information about related products, refer to these documents:
•
•
•
•
•
•
•
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain 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 at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
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:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
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-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
•
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documentation listed in the "Related Documentation" section.
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, EtherFast, EtherSwitch, Fast Step, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, 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 United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0406R)
Copyright ©2005 Cisco Systems Inc. All rights reserved
