 Feedback
|
Table Of Contents
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Minimum Cisco IOS Release for Major Features
Stacking (Catalyst 3750 or Cisco EtherSwitch service module switch stack only)
Resolved IOS Caveats in Cisco IOS Release 12.2(25)SEC2
Resolved IOS Caveats in Cisco IOS Release 12.2(25)SEC1
Resolved IOS Caveats in Cisco IOS Release 12.2(25)SEC
Documentation Updates in Cisco IOS Release 12.2(25)SEC
Updates for the Software Configuration Guides
Allocating Power to Devices Connected to a PoE Port
Updates for the Command Reference
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Catalyst 3750, 3560, and 2970 Switches, Cisco IOS Release 12.2(25)SEC and Later
Revised November 2, 2005
The Cisco IOS Release 12.2(25)SEC and later runs on all Catalyst 3750, 3560, and 2970 switches and on Cisco EtherSwitch service modules.
The Catalyst 3750 switches and the Cisco EtherSwitch service modules support stacking through Cisco StackWise technology. The Catalyst 3560 and 2970 switches do not support switch stacking. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
These release notes include important information about Cisco IOS Release 12.2(25)SEC, Cisco IOS Release 12.2(25)SEC1, and Cisco IOS Release 12.2(25)SEC2, and any limitations, restrictions, and caveats that apply to them. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
For the complete list of Catalyst 3750, 3560, and 2970 switch documentation and of Cisco EtherSwitch service module documentation, see the "Related Documentation" section.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/public/sw-center/sw-lan.shtml
Note
This software 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 software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Cisco IOS Release 12.2(25)SEC and later are based on Cisco IOS Release 12.2(25)S. Open caveats in Cisco IOS Release 12.2(25)S also affect Cisco IOS Release 12.2(25)SEC and later, unless they are listed in the Cisco IOS Release 12.2(25)SEC resolved caveats list. The list of open caveats in Cisco IOS Release 12.2(25)S is available at this URL:
/en/US/docs/ios/12_2s/release/notes/122Srn.html#wp2367913
Contents
This information is in the release notes:
•
•
•
•
•
•
•
•
•
•
System Requirements
The system requirements are described in these sections:
•
•
Hardware Supported
Table 1 lists the hardware supported on Cisco IOS Release 12.2SE.
Table 1 Catalyst 3750, 3560, and 2970 and Cisco EtherSwitch Service Modules Supported Hardware
Catalyst 3750-24FS
24 100BASE-FX ports and 2 SFP1 module slots
Cisco IOS Release 12.2(25)SEB
Catalyst 3750-24PS
24 10/100 PoE2 ports and 2 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3750-24TS
24 10/100 Ethernet ports and 2 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3750-48PS
48 10/100 PoE ports and 4 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3750-48TS
48 10/100 Ethernet ports and 4 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3750G-12S
12 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3750G-16TD
16 10/100/1000 Ethernet ports and 1 XENPAK 10-Gigabit Ethernet module slot
Cisco IOS Release 12.2(18)SE
Catalyst 3750G-24PS
24 10/100/1000 PoE ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3750G-24T
24 10/100/1000 Ethernet ports
Cisco IOS Release 12.2(18)SE
Catalyst 3750G-24TS
24 10/100/1000 Ethernet ports and 4 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3750G-24TS-1U
24 10/100/1000 Ethernet ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3750G-48PS
48 10/100/1000 PoE ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3750G-48TS
48 10/100/1000 Ethernet ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3560-24PS
24 10/100 PoE ports and 2 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3560-24TS
24 10/100 ports and 2 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3560-48PS
48 10/100 PoE ports and 4 SFP module slots
Cisco IOS Release 12.2(18)SE
Catalyst 3560-48TS
48 10/100 ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3560G-24PS
24 10/100 PoE ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3560G-24TS
24 10/100/1000 Ethernet ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3560G-48PS
48 10/100/1000 PoE ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 3560G-48TS
48 10/100/1000 Ethernet ports and 4 SFP module slots
Cisco IOS Release 12.2(20)SE3
Catalyst 2970G-24T
24 10/100/1000 Ethernet ports
Cisco IOS Release 12.2(18)SE
Catalyst 2970G-24TS
24 10/100/1000 Ethernet ports and 4 SFP module slots
Cisco IOS Release 12.2(18)SE
NME-16ES-1G3
16 10/100 ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide
Cisco IOS Release 12.2(25)SEC
NME-16ES-1G-P3
16 10/100 PoE ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide
Cisco IOS Release 12.2(25)EZ
NME-X-23ES-1G3
23 10/100 ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide
Cisco IOS Release 12.2(25)SEC
NME-X-23ES-1G-P3
23 10/100 PoE ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide
Cisco IOS Release 12.2(25)EZ
NME-XD-24ES-1S-P3
24 10/100 PoE ports, 1 SFP module port, 2 StackWise connector ports, extended double-wide
Cisco IOS Release 12.2(25)EZ
NME-XD-48ES-2S-P3
48 10/100 PoE ports, 2 SFP module ports, no StackWise connector ports, extended double-wide
Cisco IOS Release 12.2(25)EZ
SFP modules
1000BASE-T, 1000BASE-SX
1000BASE-LX, 1000BASE-ZX, and CWDM4
100BASE-FX MMF5
Cisco IOS Release 12.2(18)SE
Cisco IOS Release 12.2(20)SE
XENPAK modules6
XENPAK-10-GB-ER, XENPAK-10-GB-LR, XENPAK-10-GB-LX4, XENPAK-10-GB-SR, and XENPAK-10-GB-CX4
Cisco IOS Release 12.2(18)SE
Redundant power systems
Cisco RPS 675 Redundant Power System
Supported on all software releases
1 SFP = small form-factor pluggable
2 PoE = Power over Ethernet
3 Cisco EtherSwitch service module
4 CWDM = coarse wavelength-division multiplexer
5 MMF = multimode fiber
6 XENPAK modules are only supported on the Catalyst 3750G-16TD switches.
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
•
•
Hardware Requirements
Table 2 lists the minimum hardware requirements for running the device manager.
Table 2 Minimum Hardware Requirements
Intel Pentium II1
64 MB2
256
1024 x 768
Small
1 We recommend Intel Pentium 4.
2 We recommend 256-MB DRAM.
Software Requirements
Table 3 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.
Note
Table 3 Supported Operating Systems and Browsers
Windows 98
None
5.5 or 6.0
7.1
Windows NT 4.0
Service Pack 6 or later
5.5 or 6.0
7.1
Windows 2000
None
5.5 or 6.0
7.1
Windows XP
None
5.5 or 6.0
7.1
1 Service Pack 1 or higher is required for Internet Explorer 5.5.
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, the command reference, and the Cisco EtherSwitch service module feature guide.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS 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 privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
Note
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 the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
For the Catalyst 3750 and 3560 switches, Cisco IOS Release 12.2(25)SEA and earlier referred to the image that provides Layer 2+ features and basic Layer 3 routing as the standard multilayer image (SMI). The image that provides full Layer 3 routing and advanced services was referred to as the enhanced multilayer image (EMI).
Cisco IOS Release 12.2(25)SEB and later refers to the SMI as the IP base image and the EMI as the IP services image.
Cisco IOS Release 12.2(25)SEB and later refers to the Catalyst 2970 image as the LAN base image.
Table 4 lists the different file-naming conventions before and after Cisco IOS Release 12.2(25)SEB.
Table 4 Cisco IOS Image File Naming Convention
c3750-i9-mz (SMI1 )
c3750-ipbase-mz
c3750-i9k91-mz (SMI)
c3750-ipbasek9-mz
c3750-i5-mz (EMI2 )
c3750-ipservices-mz
c3750-i5k91-mz (EMI)
c3750-ipservicesk9-mz
c3560-i9-mz (SMI)
c3560-ipbase-mz
c3560-i9k91-mz (SMI)
c3560-ipbasek9-mz
c3560-i5-mz (EMI)
c3560-ipservices-mz
c3560-i5k91-mz (EMI)
c3560-ipservicesk9-mz
c2970-i6l2-mz
c2970-lanbase-mz
c2970-i6k91l2-mz
c2970-lanbasek9-mz
1 SMI = standard multilayer image
2 EMI = enhanced multilayer image
Table 5 lists the filenames for this software release.
Note
Table 5 Cisco IOS Software Image Files
Filename
c3750-ipbase-tar.122-25.SEC2.tar
Catalyst 3750 IP base image and device manager files.
This image has Layer 2+ and basic Layer 3 routing features.
This image also runs on the Cisco EtherSwitch service modules.c3750-ipservices-tar.122-25.SEC2.tar
Catalyst 3750 IP services image and device manager files.
This image has both Layer 2+ and full Layer 3 routing features.
This image also runs on the Cisco EtherSwitch service modules.c3750-ipbasek9-tar.122-25.SEC2.tar
Catalyst 3750 IP base cryptographic image and device manager files.
This image has the Kerberos, SSH1 , Layer 2+, and basic Layer 3 routing features.
This image also runs on the Cisco EtherSwitch service modules.c3750-ipservicesk9-tar.122-25.SEC2.tar
Catalyst 3750 IP services cryptographic image and device manager files.
This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features.
This image also runs on the Cisco EtherSwitch service modules.c3750-advipservicesk9-tar.122-25.SEC2.tar
Catalyst 3750 advanced IP services image, cryptographic file, and device manager files.
This image has all the IP services image (formerly known as the EMI) features and the capability for unicast routing of IPv6 packets.
This image also runs on the Cisco EtherSwitch service modules.c3560-ipbase-tar.122-25.SEC2.tar
Catalyst 3560 IP base image file and device manager files.
This image has Layer 2+ and basic Layer 3 routing features.c3560-ipservices-tar.122-25.SEC2.tar
Catalyst 3560 IP services image and device manager files.
This image has both Layer 2+ and full Layer 3 routing features.c3560-ipbasek9-tar.122-25.SEC2.tar
Catalyst 3560 IP base cryptographic image and device manager files.
This image has the Kerberos, SSH, and Layer 2+, and basic Layer 3 routing features.c3560-ipservicesk9-tar.122-25.SEC2.tar
Catalyst 3560 IP services cryptographic image and device manager files. This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features.
c3560-advipservicesk9-tar.122-25.SEC2.tar
Catalyst 3560 advanced IP services image, cryptographic file, and device manager files.
This image has all the IP services image (formerly known as the EMI) features and the capability for unicast routing of IPv6 packets.c2970-lanbase.122-25.SEC2.tar
Catalyst 2970 image file and device manager files.
This image has Layer 2+ features.c2970-lanbasek9-tar.122-25.SEC2.tar
Catalyst 2970 cryptographic image file and device manager files.
This image has the Kerberos and SSH features.
1 SSH = Secure Shell
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 at this URL:
/en/US/docs/ios/12_2/configfun/command/reference/frf011.html#wp1018426
Upgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the 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.
To download software, follow these steps:
Step 1
Step 2
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the image for a Catalyst 2970 switch, click Catalyst 2970 software. To obtain authorization and to download the cryptographic software files, click Catalyst 2970 3DES Cryptographic Software.
To download the IP services image (formerly known as the EMI) or IP base image (formerly known as the SMI) files for a Catalyst 3560 switch, click Catalyst 3560 software. To obtain authorization and to download the cryptographic software files, click Catalyst 3560 3DES Cryptographic Software.
To download the IP services image (formerly known as the EMI) or IP base image (formerly known as the SMI) files for a Catalyst 3750 switch, click Catalyst 3750 software. To obtain authorization and to download the cryptographic software files, click Catalyst 3750 3DES Cryptographic Software.
Caution
to 1 minute to upgrade the first time that the new software is loaded. Do not power cycle the switch during the bootloader upgrade.
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
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/c3750-ipservices-tar.122-25.SEB.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.
Recovering from a Software Failure
For additional recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
Note
Note
New Features
These sections describe the new supported hardware and the new software features provided in this release:
•
•
New Hardware Features
There are no new hardware features for this release. For a list of all supported hardware, see the "Hardware Supported" section.
New Software Features
This release contains these new switch features or enhancements (available in all software images):
•
•
•
•
•
•
•
•
•
•
Minimum Cisco IOS Release for Major Features
Table 6 lists the minimum software release required to support the major features of the Catalyst 3750, 3560, and 2970 switches and the Cisco EtherSwitch service modules.
Table 6 Catalyst 3750, 3560, and 2970 Switch and Cisco EtherSwitch Service Module Features and the Minimum Cisco IOS Release Required
IEEE 802.1x with wake-on-LAN
12.2(25)SEC
3750, 3560, 2970
Cisco EtherSwitch service modules
Nonstop forwarding awareness
12.2(25)SEC
3750, 3560, 2970
Cisco EtherSwitch service modules
Configuration logging
12.2(25)SEC
3750, 3560, 2970
Cisco EtherSwitch service modules
Secure Copy Protocol
12.2(25)SEC
3750, 3560, 2970
Cisco EtherSwitch service modules
Cross-stack EtherChannel
12.2(25)SEC
3750
Cisco EtherSwitch service modules
Support for configuring private-VLAN ports on interfaces that are configured for dynamic ARP inspection (IP base image [formerly known as the SMI] only)
12.2(25)SEB
3750, 3560, 2970
Support for IP source guard on private VLANs (IP base image [formerly known as the SMI] only)
12.2(25)SEB
3750 and 3560
IGMP leave timer
12.2(25)SEB
3750, 3560, 2970
IGMP snooping querier
12.2(25)SEA
3750, 3560, 2970
Advanced IP services
12.2(25)SEA
3750, 3560
Support for DSCP transparency
12.2(25)SE
3750, 3560, 2970
Support for VLAN-based QoS1 and hierarchical policy maps on SVIs2
12.2(25)SE
3750, 3560, 2970
Device manager
12.2(25)SE
3750, 3560, 2970
IEEE 802.1Q tunneling and Layer 2 protocol tunneling
12.2(25)SE
3750, 3560
Layer 2 point-to-point tunneling and Layer 2 point-to-point tunneling bypass
12.2(25)SE
3750, 3560
Support for SSL version 3.0 for secure HTTP communication (cryptographic images only)
12.2(25)SE
3750, 3560, 2970
Support for configuring private-VLAN ports on interfaces that are configured for dynamic ARP inspection (IP services image [formerly known as the EMI] only)
12.2(25)SE
3750 and 3560
Support for IP source guard on private VLANs (IP services image [formerly known as the EMI] only)
12.2(25)SE
3750 and 3560
Cisco intelligent power management to limit the power allowed on a port, or pre-allocate (reserve) power for a port.
12.2(25)SE
3750 and 3560
IEEE 802.1x accounting and MIBs (IEEE 8021-PAE-MIB and CISCO-PAE-MIB)
12.2(20)SE
3750, 3560, 2970
Dynamic ARP inspection (IP services image [formerly known as the EMI] only)
12.2(20)SE
3750, 3560
Flex Links
12.2(20)SE
3750, 3560, 2970
Software upgrade (device manager or Network Assistant only)
12.2(20)SE
3750, 3560, 2970
IP source guard (IP services image [formerly known as the EMI] only)
12.2(20)SE
3750, 3560
Private VLAN (IP services image [formerly known as the EMI] only)
12.2(20)SE
3750, 3560
SFP module diagnostic management interface
12.2(20)SE
3750, 3560, 2970
Switch stack offline configuration
12.2(20)SE
3750
Stack-ring activity statistics
12.2(20)SE
3750
Smartports macros
12.2(18)SE
3750, 3560, 2970
1 QoS = quality of service
2 SVIs = switched virtual interfaces
Limitations and Restrictions
You should review this section before you begin working with the switch. 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.
This section contains these limitations:
•
•
Cisco IOS Limitations
Unless otherwise noted, these limitations apply to the Catalyst 3750, 3560, and 2970 switches and the Cisco EtherSwitch service modules:
•
Configuration
These are the configuration limitations:
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
•
1.
2.
3.
•
–
–
–
No workaround is necessary; these are the designed behaviors. (CSCed50819)
•
However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)
•
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)
•
When you enter the show ip arp inspection log privileged EXEC command, the log entries from all switches in the stack are moved to the switch on which you entered the command.
There is no workaround. (CSCed95822)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•
To change the baud rate, reload the Cisco EtherSwitch service module with the bootloader prompt. You can then change the baud rate and change the speed on the TTY line of the router connected to the Cisco EtherSwitch Service module console.
There is no workaround. (CSCeh50152)
•
After password recovery completes, the workaround is to enter the set_bs bs: rw command at the Cisco EtherSwitch service module prompt before you change any variables. This command sets the service module in read-write mode. Then enter the set_param command to write the changes before resetting the Cisco EtherSwitch service module. (CSCeh45594)
•
The workaround is to use switch ports other than those specified for redundancy and for applications that immediately detect active links. (CSCeh70503)
Ethernet
These are the Ethernet limitations:
•
–
–
–
These are the workarounds:
–
–
–
For more information, enter CSCea77032 in the Bug Toolkit at this URL:
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl
•
If the Cisco EtherSwitch service module is in access mode, the workaround is to enter the spanning-tree portfast interface configuration command on the internal Gigabit Ethernet interface. If the service module is in trunk mode, there is no workaround.
•
If this happens, uneven traffic distribution will happen on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
–
–
–
–
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal.(CSCeh81991)
Fallback Bridging
These are the fallback bridging limitations:
•
•
HSRP
This is the Hot Standby Routing Protocol (HSRP) limitation:
When the active switch fails in a switch cluster that uses HSRP redundancy, the new active switch might not contain a full cluster member list. The workaround is to ensure that the ports on the standby cluster members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking state, see the "Configuring STP" chapter in the software configuration guide. (CSCec76893)
IP
These are the IP limitations:
•
•
IP Telephony
These are the IP telephony limitations:
•
•
•
•
The workaround for networks with pre-standard powered devices is to leave the maximum wattage set at the default value (15.4 W). You can also configure the maximum wattage for the port for no less than the value the powered device reports as the power consumption through CDP messages. For networks with IEEE Class 0, 3, or 4 devices, do not configure the maximum wattage for the port at less than the default 15.4 W (15,400 milliwatts). (CSCee80668)
Management
CiscoWorks is not supported on the Catalyst 3750-24FS switch.
MAC Addressing
This is the MAC addressing limitation:
(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) When a MAC address is configured for filtering on the internal VLAN of a routed port, incoming packets from the MAC address to the routed port are not dropped. (CSCeb67937)
Multicasting
These are the multicasting limitations:
•
•
•
•
•
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•
–
–
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
Power
These are the powers limitation for the Cisco EtherSwitch service modules:
•
There is no workaround. You should use the power inline never interface configuration command on Cisco EtherSwitch service module ports that are not connected to PoE devices. (CSCee71979)
•
Router# show power inlinePowerSupply SlotNum. Maximum Allocated Status----------- -------- ------- --------- ------INT-PS 0 360.000 121.000 PS1 GOOD PS2 ABSENTInterface Config Device Powered PowerAllocated--------- ------ ------ ------- --------------Gi4/0 auto Unknown On 121.000 WattsThis is not a problem because the display correctly shows the total used power and the remaining power available on the system. (CSCeg74337)
•
The workaround is to enter the shutdown and the no shutdown interface configuration commands on the Fast Ethernet interface of a new IP phone that is attached to the service module port after the internal link is brought up. (CSCeh45465)
QoS
These are the quality of service (QoS) limitations:
•
•
Routing
These are the routing limitations:
•
•
•
%SYS-2-MALLOCFAIL: Memory allocation of 4252 bytes failed from 0x179C80, alignment 0Pool: I/O Free: 77124 Cause: Memory fragmentationAlternate Pool: None Free: 0 Cause: No Alternate poolThis error message means there is a temporary memory shortage that normally recovers by itself. You can verify that the switch stack has recovered by entering the show cef line user EXEC command and verifying that the line card states are up and sync. No workaround is required because the problem is self-correcting. (CSCea71611)
•
–
–
–
The workaround is to change any one of the listed conditions. (CSCed53633)
SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•
This is a hardware limitation and only applies to these switches (CSCdy72835):
–
–
–
–
–
–
–
–
–
–
–
•
This is a hardware limitation and only applies to these switches (CSCdy81521):
–
–
–
–
–
–
–
–
–
–
–
–
–
•
This is a hardware limitation and only applies to these switches (CSCea72326):
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
Stacking (Catalyst 3750 or Cisco EtherSwitch service module switch stack only)
These are the Catalyst 3750 and Cisco EtherSwitch service module switch stack limitations:
•
•
•
•
•
There is no workaround. (CSCed54150)
•
The workaround is to complete the MAC address update by entering the clear arp privileged EXEC command. (CSCed62409)
•
•
Private VLAN is enabled or disabled on a switch stack, depending on whether or not the stack master is running the IP services image (formerly known as the EMI) or the IP base image (formerly known as the SMI):
–
–
This occurs after a stack master re-election when the previous stack master was running the IP services image (formerly known as the EMI) and the new stack master is running the IP base image (formerly known as the SMI). The stack members are configured with private VLAN, but any new switch that joins the stack will have private VLAN disabled.
These are the workarounds. Only one of these is necessary:
–
–
•
This is the expected behavior of the offline configuration (provisioning) feature. There is no workaround. (CSCee12431)
Trunking
These are the trunking limitations:
•
•
•
•
VLAN
These are the VLAN limitations:
•
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•
There is no workaround. (CSCed71422)
•
The workaround is to define another policy-map name for the second-level policy-map with the same configuration to be used for another policy-map. (CSCef47377)
Device Manager Limitations
When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not launch.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Important Notes
These sections describe the important notes related to this software release for the Catalyst 3750, 3560, and 2970 switches and for the Cisco EtherSwitch service modules:
•
Switch Stack Notes
These notes apply to switch stacks:
•
•
•
Cisco IOS Notes
These notes apply to Cisco IOS software:
•
•
–
–
In Cisco IOS Release 12.2(18)SE and later, you can only use the logging on and then the no logging console global configuration commands to disable logging to the console. (CSCec71490)
•
Device Manager Notes
These notes apply to the device manager:
•
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
Open Caveats
This section describes the open caveats with possible unexpected activity in this software release. Unless otherwise noted, these severity 3 Cisco IOS configuration caveats apply to the Catalyst 3750, 3560, and 2970 switches and to Cisco EtherSwitch service modules:
•
You cannot ping a Layer 3 interface that has a Network Address Translation (NAT) configuration.
There is no workaround.
•
Phone detection events that are generated by many IEEE phones connected to the switch ports can consume a significant amount of CPU time if the switch ports cannot power the phones because the internal link is down.
The workaround is to enter the power inline never interface configuration command on all the Fast Ethernet ports that are not powered by but are connected to IP phones if the problem persists.
•
Disabling OSPFv3 causes a memory leak.
There is no workaround.
•
When the switch boots up, ports 2, 6, and 10 can become active before the Cisco IOS software loading process is complete. Packets arriving at these ports before the switch software is completely loaded are lost.
The workaround is to use switch ports other than those specified for redundancy and for applications that immediately detect active links.
•
SNMP polling for CiscoEnvMonSupplyStatusDescr, which gives power supply status, does not supply accurate information.
The workaround is to use the show env stack user EXEC command to verify that switch hardware is working properly.
•
When connected to the router through an auxiliary port in a session to a Cisco EtherSwitch service module, the service module session fails when you enter the shutdown and the no shutdown interface configuration commands on the service module router interface.
These are the workarounds:
–
–
•
Probing a switch to see which server is current and reachable produces different results when another server on the switch sends an unsolicited response. If the secondary server responds while the primary server is current, this causes the switch to treat the secondary server as current. When this happens the switch does not probe for the primary server, and does not switch back to the primary server. Having two different servers respond as primary causes the switch to change its primary server value in VMPS.
The workaround is to reboot the switch.
•
A duplex mismatch occurs when two Fast Ethernet interfaces that are directly connected on two EtherSwitch service modules are configured as both 100 Mbps and full duplex and as automatic speed and duplex settings. This is expected behavior for the PHY on the Cisco EtherSwitch service modules.
There is no workaround.
•
If two Cisco EtherSwitch service modules are directly connected through Fast Ethernet interfaces configured as both 100 Mbps and full duplex and as automatic speed and duplex settings, one interface might detect the other as a Cisco powered device.
There is no workaround.
•
The storm-control feature does not work properly when the multicast MAC destination address and the multicast IP destination address are not mapped correctly. The switch blocks all other multicast traffic except multicast storm traffic.
There is no workaround.
•
A stack of switches running IEEE 802.1D STP with UplinkFast enabled may send dummy multicast packets on the new root port for some MAC addresses learned on the old root port after the UplinkFast transition occurs. This problem requires that an existing root port go down and that the new root port exists on a different switch member in the stack. When these conditions are true, traffic to such MAC addresses will be lost for a short time until they are flushed from the MAC address table of the neighbor on the new root port.
The workaround is to configure all alternate ports on the same stack member as the root port.
•
When the router is rebooted after it is powered on (approximately once in 10 to 15 reboots), the Router Blade Communication Protocol (RBCP) between the router and the EtherSwitch service module might not be reestablished, and this message appears:
[date]: %Y88E8K-3-ILP_MSG_TIMEOUT_ERROR: GigabitEthernet1/0: EtherSwitch Service Module RBCP ILP messages timeoutThe workaround is to reload the EtherSwitch service module software without rebooting the router. You can reload the switching software by using the reload user EXEC command at the EtherSwitch service module prompt or by using the service-module g slot_numer /0 reset privileged EXEC command at the router prompt.
•
When you try to access the snmpwalk MIBs with double indexing, the switch does not respond.
The workaround is to configure the community string without an at (@) character.
•
Interfaces that have port security enabled and violation mode protect stop forwarding packets when their secure address maximum has been reached. An attempt to clear the secure port addresses on the switch does not allow packets to resume forwarding. The switch does not recognize that ports have been cleared and allow packets to resume forwarding until the switch has been rebooted or until the port interface is shut down and brought back. This bug occurs when an interface has port security enabled and violation mode protect configured.
The workaround is to use the violation mode restrict interface configuration command instead of the violation mode protect interface configuration command
•
If the switch writes extended information to the console at the time of a failure, messages such as this might appear:
00:00:201985112528: %SYS-2-INTSCHED: 'may_suspend' at level 6 -Process= "Init", ipl= 6, pid= 3 -Traceback= 8A322C 752718 C122A8 422210 424E40 428B20 428FF4 42F110 935E94 45C2F8 45C3EC 45C5C8 3FBD60 7584B0 758788 4A2FE0There is no workaround.
•
After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.
Use one of these workarounds:
–
–
•
When you configure EtherChannels, ports with different settings for speed, duplex, and trunking mode are allowed in the same EtherChannel. This configuration can cause issues with load balancing if too much traffic is sent to a slower port.
The workaround is to configure ports with mismatched parameters in different EtherChannels.
•
If two or more switches in a stack of PoE switches restart at the same time and you enter the no switch stack-member-number provision global configuration command, this message appears on the console:
%Command not applied to switch x, remote errorwhere x is the stack member number.
There is no workaround. This problem does not affect the switch functionality.
•
When a switch is configured with both IEEE 802.1Q and Layer 2 Protocol tunneling, it can receive traffic from unauthorized VLANs through the Layer 2 Protocol tunnel. If the unauthorized traffic causes STP inconsistencies, the switch blocks the uplink port.
Use one of these workarounds:
–
–
•
If you use the no snmp-server enable traps stpx command, BRIDGE-MIB traps are disabled because BRIDGE-MIB traps are enabled when using the stpxNotification Enable object in the CISCO-STP-EXTENSIONS-MIB.
The workaround is to re-enable the BRIDGE-MIB traps by using the snmp-server enable traps stpx command.
•
You cannot use the no snmp-server host [ip] [ver] [2c] [word] udp-port <port number> (add mode) command to delete the snmp-server host [ip] [ver] [2c] [word] udp-port <port number> configuration.
The workaround is to enter the no snmp-server (add mode) command, the exit (add mode) command, and the save configuration (add mode) command, and then restart the switch with an SNMP configuration that does not include udp-port.
Resolved Caveats
These sections describe the caveats have been resolved in this release. Unless otherwise noted, these resolved caveats apply to the Catalyst 3750, 3560, and 2970 switches and the Cisco EtherSwitch service modules:
•
•
•
Resolved IOS Caveats in Cisco IOS Release 12.2(25)SEC2
These caveats were resolved:
•
Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability. Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution.
Cisco has made free software available that includes the additional integrity checks for affected customers.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20051102-timers.shtml.
•
Through normal software maintenance processes, Cisco is removing deprecated functionality. These changes have no impact on system operation or feature availability.
Resolved IOS Caveats in Cisco IOS Release 12.2(25)SEC1
This caveat was resolved:
•
Cisco Internetwork Operating System (IOS) software is vulnerable to a Denial of Service (DoS) and potentially an arbitrary code execution attack from a specifically crafted IPv6 packet. The packet must be sent from a local network segment. Only devices that have been explicitly configured to process IPv6 traffic are affected. Upon successful exploitation, the device may reload or be open to further exploitation.
Cisco has made free software available to address this vulnerability for all affected customers.
More details can be found in the security advisory that is posted at http://www.cisco.com/warp/public/707/cisco-sa-20050729-ipv6.shtml.
Resolved IOS Caveats in Cisco IOS Release 12.2(25)SEC
These caveats were resolved:
•
These switches can now forward SNAP encapsulated IP packets, but only when you enter the ip snap forwarding command:
–
–
Other switches affected by CSCdz89142 continue to drop SNAP encapsulated IP packets.
•
If a switch without a vlan.dat file is reloaded, the switch now configures itself by using the start-up configuration file.
•
The cns config retrieve global configuration command no longer stalls or fails when attempting to download a configuration if the CNS Event Agent is also configured.
•
You can modify the second level (port-level) policy-map when the per-VLAN QoS per-port policer policy-map is already attached to a VLAN switched virtual interface (SVI).
•
Static power allocation on an EtherSwitch service module port is now supported in Cisco IOS Release 12.2(25)SEC.
•
EtherSwitch service modules now provide power to all ports during a power cycle.
•
When you enable IEEE 802.1x on one or more ports of a member switch and you enter the show dot1x all privileged EXEC command, the command output now displays IEEE 802.1x information about ports on the member switches.
•
In a switch stack with switches running Cisco IOS Release 12.2(20)SE4 or Cisco IOS Release 12.2(25)SEA, if the main power supply of a member switch or a redundant power system (RPS) connected to a member switch fails, the switch stack now generates the appropriate trap.
•
The port that you configure as the designated MST port now synchronizes.
•
If an IEEE 802.1x client configured for both machine and user authentication is connected to a Catalyst 3750, 3560, 3550, or 2970 switch running Cisco IOS Release 12.2(25)SE or to a Cisco EtherSwitch service module and if RADIUS VLAN assignment is used only for the machine authentication, the user authentication no longer takes 2 to 5 minutes.
•
The SFP-100FX modules now work on the 48-port Cisco EtherSwitch service modules.
•
After you have created an EtherChannel, the switch can now set the MIB object by using SNMP and no longer returns an incorrect value when the switch executes a cmnMacAddrLearntEnable query. The value now changes when you enter the snmp trap mac-notification command on the interface.
•
RSA encryption keys are now properly synchronized among stack members, so that SSH connectivity is no longer lost after a stack master reloads.
•
When a switch has a multicast receiver that joins a multicast group and the multicast receiver sends the IGMP Leave and Report message immediately one after the other, the switch processes the leave message but not the report message, which causes the outgoing interface list (OIL) to be null. This null value delays the multicast receiver from receiving multicast traffic up to a minute.
•
When the switch becomes a root bridge and sends a trap, the newRoot trap does not have a valid spanning-tree ID.
•
A cluster command switch may report the following error when the configuration is saved:
%CMP-4-MEM_CMPIP_ADDR_CONFLICT: Conflict with CMP IP address <ip address>
Reissuing a new CMP IP address to member <member number>
•
High CPU utilization no longer occurs on the switch after you upgrade the software to Cisco IOS Release 12.2(25)SEA or later.
•
You can configure an ingress port of the switch either to specify that the Cisco IP Phone is a trusted device, or to apply a policy map to the port, but not both. The setting that is configured last takes effect.
•
Sending any SNMP trap to a VRF destination no longer results in a memory leak. Memory held by the trap process does not cause switch memory failure, which then requires the switch be reloaded.
•
A switch running Cisco IOS Release 12.2(25)SEB now listens to RP announce and discovery messages.
•
If a switch port is in the access mode and is assigned to a voice VLAN, when you enter the vlan dot1q tag native (add mode) command after the switch restarts, traffic from the port is correctly tagged.
•
Switches running Cisco IOS Release 12.2(25)SE do not properly run the Service Assurance Agent (SAA) HTTP process. When you configure an HTTP process on the switch by using the Internet Performance Monitor (IPM) application, IPM might not work properly with the HTTP process.
There is no workaround.
•
A switch port might fail to enter the blocking state under these conditions:
–
–
These messages appear:
%SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id%SPANTREE-2-BLOCK_PVID_PEER: Blocking on <port>. Inconsistent peer vlanAlthough the messages show that the port is in a blocking state, the port can be in the forwarding state, creating a spanning-tree loop.
The workaround is to reset the link at one end of the trunk.
Documentation Updates in Cisco IOS Release 12.2(25)SEC
This section provides updates to the product documentation.
•
•
Updates for the Software Configuration Guides
These are the documentation updates for the software configuration guides for this release:
•
With Cisco IOS Release 12.2(25)SE and later, the switch maintains the EAPOL packet history. If an EAPOL packet is detected on the interface during the lifetime of the link, the switch determines that the device connected is interface to be an 802.1x-capable supplicant, and the interface does not transition to the guest VLAN state. EAPOL history is cleared if the interface link status goes down. If no EAPOL packet is detected on the interface, it is transitioned to the guest VLAN state.
Note
•
The section should be called "Configuring IEEE 802.3x Flow Control" and references to IEEE 802.3z flow control should be IEEE 802.3x flow control.
•
Allocating Power to Devices Connected to a PoE Port
Note
When powered devices are connected to PoE ports, the switch keeps track of the amount of power allocated (the power budget) to the devices. When the switch detects a powered device on a PoE port, the switch allocates (budgets) a specific amount of power to the device.
Powered devices have a default amount of power that can be allocated to them based on the IEEE classification for the device. The switch uses the wattage values of the powered devices to track the switch PoE budget.
Follow these guidelines when allocating power to powered devices:
•
•
%CAUTION: Interface Gi1/0/1: Misconfiguring the 'power inline consumption/allocation' command may cause damage to the switch and void your warranty. Take precaution not to oversubscribe the power supply.Refer to documentation.•
PLATFORM_RPC-3-RESP_FAIL: Unexpected response or failure, class [dec], req [dec], switch [dec], error [dec], [chars].
Note
Beginning in privileged EXEC mode, follow these steps to configure the amount of power allocated to a powered device connected to each PoE port on a switch:
To return to the default setting, use the no power inline consumption default global configuration command.
Beginning in privileged EXEC mode, follow these steps to configure amount of power allocated to a powered device connected to a specific PoE port:
To return to the default setting, use the no power inline consumption default interface configuration command.
•
Using the crashinfo Files
The crashinfo files save information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail (crash). The switch writes the crash information to the console at the time of the failure. The switch creates two types of crashinfo files:
•
•
Basic crashinfo Files
The information in the basic file includes the Cisco IOS image name and version that failed, a list of the processor registers, and a stack trace. You can provide this information to the Cisco technical support representative by using the show tech-support privileged EXEC command.
Basic crashinfo files are kept in this directory on the flash file system:
flash:/crashinfo/.
The filenames are crashinfo_n where n is a sequence number.
Each new crashinfo file that is created uses a sequence number that is larger than any previously existing sequence number, so the file with the largest sequence number describes the most recent failure. Version numbers are used instead of a timestamp because the switches do not include a real-time clock. You cannot change the name of the file that the system will use when it creates the file. However, after the file is created, you can use the rename privileged EXEC command to rename it, but the contents of the renamed file will not be displayed by the show stacks or the show tech-support privileged EXEC command. You can delete crashinfo files by using the delete privileged EXEC command.
You can display the most recent basic crashinfo file (that is, the file with the highest sequence number at the end of its filename) by entering the show stacks or the show tech-support privileged EXEC command. You also can access the file by using any command that can copy or display files, such as the more or the copy privileged EXEC command.
Extended crashinfo Files
In Cisco IOS Release 12.2(25)SEC or later, the switch creates the extended crashinfo file when the system is failing. The information in the extended file includes additional information that can help determine the cause of the switch failure. You provide this information to the Cisco technical support representative by manually accessing the file and using the more or the copy privileged EXEC command.
Extended crashinfo files are kept in this directory on the flash file system:
flash:/crashinfo_ext/.
The filenames are crashinfo_ext_n where n is a sequence number.
You can configure the switch to not create the extended crashinfo file by using the no exception crashinfo global configuration command.
Updates for the Command Reference
These are updates to the command references for this release:
•
•
•
exception crashinfo
Use the exception crashinfo global configuration command on the switch stack or on a standalone switch to configure the switch to create the extended crashinfo file when the Cisco IOS image fails. Use the no form of this command to disable this feature.
exception crashinfo
no exception crashinfo
Syntax Description
This command has no arguments or keywords.
Defaults
The switch creates the extended crashinfo file.
Command Modes
Global configuration
Command History
Usage Guidelines
The basic crashinfo file includes the Cisco IOS image name and version that failed, a list of the processor registers, and a stack trace. The extended crashinfo file includes additional information that can help determine the cause of the switch failure.
If you enter the exception crashinfo global configuration command on a stack master, it configures all the stack members to create the extended crashinfo file if the Cisco IOS image on the stack members fail.
Use the no exception crashinfo global configuration command to configure the switch to not create the extended crashinfo file.
Examples
This example shows how to configure the switch to not create the extended crashinfo file:
Switch(config)# no exception crashinfoYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
•
power inline consumption
Use the power inline consumption global or interface configuration command on the switch stack or on a standalone switch to override the amount of power specified by the IEEE classification for the device and to allocate (budget) the amount of power specified by the wattage setting. Use the no form of this command to return to the default power setting.
power inline consumption default wattage
no power inline consumption default
Note
Syntax Description
wattage
Specify the power allocated on the port. The range for each connected device is 4000 to 15400 milliwatts.
Defaults
The default power allocated on each Power over Ethernet (PoE) port is 15400 milliwatts.
Command Modes
Global configuration
Interface configuration
Command History
Usage Guidelines
Powered devices have a default amount of power that can be allocated to them based on the IEEE classification for the device. The switch uses the wattage values of the powered devices to track the switch PoE budget.
These are examples of how to track the switch PoE budget:
•
•
When you enter the power inline consumption default wattage or the no power inline consumption default command, this message appears:
%CAUTION: Interface interface-id: Misconfiguring the 'power inline consumption/allocation' command may cause damage to the switch and void your warranty. Take precaution not to oversubscribe the power supply. Refer to documentation.This command is supported only on PoE-capable ports. If you enter this command on a switch or port that does not support PoE, an error message appears:
Switch(config)# power inline consumption default 12000^% Invalid input detected at '^' marker.or
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# power inline consumption default 12000^% Invalid input detected at '^' marker.In a switch stack, this command is supported on all switches or ports in the stack that support PoE.
Examples
This example shows how to configure the switch to allocate only 10000 milliwatts to each the PoE port:
Switch(config)# power inline consumption default 10000%CAUTION: Interface Gi1/0/1: Misconfiguring the 'power inline consumption/allocation' command may cause damage to the switch and void your warranty. Take precaution not to oversubscribe the power supply. Refer to documentation.This example shows how to configure the switch to allocate only 12000 milliwatts to the powered device connected to the specific PoE port:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline consumption default 12000%CAUTION: Interface Gi1/0/2: Misconfiguring the 'power inline consumption/allocation' command may cause damage to the switch and void your warranty. Take precaution not to oversubscribe the power supply. Refer to documentation.You can verify your settings by entering the show power inline consumption default privileged EXEC command.
Related Commands
power inline
Configure the power management mode on PoE ports.
show power inline
Displays the PoE status for the specified PoE port or for all PoE ports.
•
show inventory
Use the show inventory user EXEC command to display product identification (PID) information for the hardware.
show inventory [entity-name | raw] [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
User EXEC
Command History
Usage Guidelines
The command is case sensitive. With no arguments, the show inventory command produces a compact dump of all identifiable entities that have a product identifier. The compact dump displays the entity location (slot identity), entity description, and the unique device identifier (UDI) (PID, VID, and SN) of that entity.
Note
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain Output are displayed.
Examples
This is example output from the show inventory command:
Switch> show inventoryNAME: "5", DESCR: "WS-C3750G-12S"PID: WS-C3750G-12S-S , VID: E0 , SN: CAT0749R204•
show inventory
Use the show inventory user EXEC command to display product identification (PID) information for the hardware.
show inventory [entity-name | raw] [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
User EXEC
Command History
Usage Guidelines
The command is case sensitive. With no arguments, the show inventory command produces a compact dump of all identifiable entities that have a product identifier. The compact dump displays the entity location (slot identity), entity description, and the unique device identifier (UDI) (PID, VID, and SN) of that entity.
Note
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain Output are displayed.
Examples
This is example output from the show inventory command:
Switch> show inventoryNAME: "1", DESCR: "WS-C3560G-48PS"PID: WS-C3560G-48PS-S , VID: 01 , SN: FOC0916U0BTSwitch> show inventoryNAME: "1", DESCR: "WS-C2970G-24T-E"PID: WS-C2970G-24T-E , VID: A0 , SN: CAT0719R0TT•
show power inline
Use the show power inline user EXEC command to display the Power over Ethernet (PoE) status for the specified PoE port or for all PoE ports.
show power inline [interface-id | module switch-number | consumption default] [ | {begin | exclude | include} expression]
Note
Syntax Description
Command Modes
User EXEC
Command History
12.1(19)EA1
This command was introduced.
12.2(25)SEC
The consumption default 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 power inline command. In the display, port 2 is configured as static; power has been pre-allocated to this port, but no powered device is connected. Port 6 is a static port in the power-deny state because its maximum wattage is configured for 10 W. The connected powered device has a reported class maximum wattage for a Class 0 or Class 3 device.
Switch> show power inlineModule Available Used Remaining(Watts) (Watts) (Watts)------ --------- -------- ---------1 370.0 114.9 255.12 370.0 34.3 335.Interface Admin Oper Power Device Class Max(Watts)--------- ------ ---------- ------- ------------------- ----- ----Fa1/0/1 auto on 6.3 IP Phone 7910 n/a 15.4Fa1/0/2 static off 15.4 n/a n/a 15.4Fa1/0/3 auto on 6.3 IP Phone 7910 n/a 15.4Fa1/0/4 auto on 6.3 IP Phone 7960 2 15.4Fa1/0/5 static on 15.4 IP Phone 7960 2 15.4Fa1/0/6 static power-deny 10.0 n/a n/a 10.0Fa1/0/7 auto on 6.3 IP Phone 7910 n/a 15.4<output truncated>This is an example of output from the show power inline command on a port:
Switch> show power inline fastethernet2/0/1Interface Admin Oper Power Device Class Max(Watts)--------- ------ ---------- ------- ------------------- ----- ----Fa2/0/1 auto on 6.3 IP Phone 7910 n/a 15.4This is an example of output from the show power inline module switch-number command on stack member 1:
Switch> show power inline module 1Module Available Used Remaining(Watts) (Watts) (Watts)------ --------- -------- ---------1 370.0 166.2 203.9Interface Admin Oper Power Device Class Max(Watts)--------- ------ ---------- ------- ------------------- ----- ----Fa1/0/1 auto on 6.3 IP Phone 7910 n/a 15.4Fa1/0/2 auto on 6.3 IP Phone 7910 n/a 15.4Fa1/0/3 auto on 6.3 IP Phone 7910 n/a 15.4Fa1/0/4 auto on 6.3 IP Phone 7910 n/a 15.4Fa1/0/5 auto on 6.3 IP Phone 7910 n/a 15.4Fa1/0/6 auto on 6.3 IP Phone 7910 n/a 15.4<output truncated>
This is an example of output from the show power inline consumption default command on each PoE port of a switch:
Switch> show power inline consumption defaultDefault PD consumption : 15400 mWRelated Commands
Related Documentation
These documents provide complete information about the Catalyst 3750, 3560, and 2970 switches and the Cisco EtherSwitch service modules and are available at Cisco.com:
•
•
•
•
products_feature_guide09186a0080415bae.htmlYou 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 documents provide complete information about the Catalyst 3750 switches and the Cisco EtherSwitch service modules:
•
•
•
•
•
•
•
•
These documents provide complete information about the Catalyst 3560 switches:
•
•
•
•
•
•
•
These documents provide complete information about the Catalyst 2970 switches:
•
•
•
•
•
•
•
For other information about related products, see 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/techsupport
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
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Cisco will continue to support documentation orders using the Ordering tool:
•
http://www.cisco.com/en/US/partner/ordering/
•
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco 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.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation 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, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation 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
Note
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 provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco 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 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 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
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://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, 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 Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, 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, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0502R)
© 2005 Cisco Systems, Inc. All rights reserved.
