Release Notes for the Catalyst 3750, 3560, 2970, and 2960 Switches, Cisco IOS Release 12.2(25)SEE
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)
Updates for the Regulatory Compliance and Safety Information
Statement 361—VoIP and Emergency Calling Services do not Function if Power Fails
Updates for the Software Configuration Guides
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
The Cisco IOS Release 12.2(25)SEE runs on all Catalyst 3750, 3560, 2970, and 2960 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, 2970, and 2960 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)SEE and any limitations, restrictions, and caveats that apply to them. Verify that these release notes are correct for your switch:
For the complete list of Catalyst 3750, 3560, 2970, and 2960 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/kobayashi/sw-center/sw-lan.shtml
Note For IPv6 capability on the Catalyst 3750 or 3560 switches or on Cisco EtherSwitch service modules, you must order the advanced IP services image upgrade from Cisco.
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)SEE is 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)SEE, unless they are listed in the Cisco IOS Release 12.2(25)SEE resolved caveats list. The list of open caveats in Cisco IOS Release 12.2(25)S is available at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122relnt/122srn.htm#wp2367913
This information is in the release notes:
The system requirements are described in these sections:
Table 1 lists the hardware supported on Cisco IOS Release 12.2SE.
24 100BASE-FX ports and 2 SFP1 module slots |
||
24 10/100 PoE2 ports and 2 SFP module slots |
||
16 10/100/1000 Ethernet ports and 1 XENPAK 10-Gigabit Ethernet module slot |
||
24 10/100BASE-T Ethernet ports and 2 dual-purpose uplinks1 (two 10/100/1000BASE-T copper ports and two SFP module slots) |
||
48 10/100BASE-T Ethernet ports and 2 dual-purpose uplinks3 (two 10/100/1000BASE-T copper ports and two SFP4 module slots) |
||
24 10/100BASE-T Ethernet ports and 2 10/100/1000BASE-T Ethernet ports |
||
48 10/100BASE-T Ethernet ports 2 10/100/1000BASE-T Ethernet ports |
||
24 10/100/1000BASE-T Ethernet ports and 4 of these are dual-purpose uplinks1 (four 10/100/1000BASE-T copper ports and four SFP module slots) |
||
44 10/100/1000 Ethernet ports and 4 dual purpose uplinks four 10/100/1000BASE-T copper ports and four SFP uplinks |
||
NME-16ES-1G 5 |
16 10/100 ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide |
|
NME-16ES-1G-P5 |
16 10/100 PoE ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide |
|
NME-X-23ES-1G 5 |
23 10/100 ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide |
|
NME-X-23ES-1G-P 5 |
23 10/100 PoE ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide |
|
NME-XD-24ES-1S-P 5 |
24 10/100 PoE ports, 1 SFP module port, 2 StackWise connector ports, extended double-wide |
|
NME-XD-48ES-2S-P 5 |
48 10/100 PoE ports, 2 SFP module ports, no StackWise connector ports, extended double-wide |
|
1000BASE-CWDM6, -LX, SX, -T, -ZX 100BASE-FX MMF7 |
||
XENPAK modules8 |
XENPAK-10-GB-ER, XENPAK-10-GB-LR, XENPAK-10-GB-LX4, XENPAK-10-GB-SR, and XENPAK-10-GB-CX4 |
|
Cisco RPS 675 Redundant Power System Cisco RPS 300 Redundant Power System (supported only on the Catalyst 2960 switch) |
These sections describes the hardware and software requirements for using the device manager:
Table 2 lists the minimum hardware requirements for running the device manager.
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 The device manager does not require a plug-in.
Microsoft Internet Explorer
11
|
|||
---|---|---|---|
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.
Cisco IOS 12.2(25)SEE and later are only compatible with Cisco Network Assistant (CNA) 3.1 and later. You can download CNA 3.1 from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
These are the procedures for downloading software. Before downloading software, read this section for important information:
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 For Catalyst 3750 and 3560 switches and the Cisco EtherSwitch service modules, although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration (IP base image [formerly known as the SMI] or IP services image [formerly known as the EMI]) and does not change if you upgrade the software image.
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.
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 5 lists the filenames for this software release.
Note For IPv6 capability on the Catalyst 3750 or 3560 switch or on the Cisco EtherSwitch service modules, you must order the advanced IP services image upgrade from Cisco.
Catalyst 3750 IP base image and device manager files. |
|
Catalyst 3750 IP services image and device manager files. |
|
Catalyst 3750 IP base cryptographic image and device manager files. |
|
Catalyst 3750 IP services cryptographic image and device manager files. |
|
Catalyst 3750 advanced IP services image, cryptographic file, and device manager files. |
|
Catalyst 3560 IP base image file and device manager files. |
|
Catalyst 3560 IP services image and device manager files. |
|
Catalyst 3560 IP base cryptographic image and device manager files. |
|
Catalyst 3560 IP services cryptographic image and device manager files. This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features. |
|
Catalyst 3560 advanced IP services image, cryptographic file, and device manager files. |
|
Catalyst 2970 image file and device manager files. |
|
Catalyst 2970 cryptographic image file and device manager files. |
|
Catalyst 2960 image file and device manager files. |
|
Catalyst 2960 cryptographic image file and device manager files. This image has the Kerberos and SSH features. |
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/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 Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.
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:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_r/ffrprt2/frf011.htm#wp1018426
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.
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 Use Table 5 to identify the file that you want to download.
Step 2 Download the software image file. If you have a SmartNet support contract, go to this URL, and log in to download the appropriate files:
http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
To download the image for a Catalyst 2960 switch, click Catalyst 2960 software. To obtain authorization and to download the cryptographic software files, click Catalyst 2960 3DES Cryptographic Software.
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.
Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.
For more information, see Appendix B in the software configuration guide for this release.
Step 4 Log into the switch through the console port or a Telnet session.
Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command:
For more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6 Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by entering this privileged EXEC command:
The /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:
You 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.
You can assign IP information to your switch by using these methods:
Note If you are upgrading a Catalyst 3750 or a 2950 switch running Cisco IOS Release 12.1(11)AX, which uses the IEEE 802.1x feature, you must re-enable IEEE 802.1x after upgrading the software. For more information, see the “Cisco IOS Notes” section.
Note When upgrading or downgrading from Cisco IOS Release 12.2(18)SE, you might need to reconfigure the switch with the same password that you were using when running Cisco IOS Release 12.2(18)SE. This problem only occurs when changing from Cisco IOS Release 12.2(18)SE to any other release. (CSCed88768)
These sections describe the new supported hardware and the new software features provided in this release:
This release supports the Catalyst 2960G-48TC-L switch. For more information, see the “Hardware Supported” section.
This release contains these new switch features or enhancements (available in all software images unless otherwise noted):
Note Inaccessible authentication bypass is also referred to as critical authentication.
Table 6 lists the minimum software release required to support the major features of the Catalyst 3750, 3560, and 2970, and 2960 switches and the Cisco EtherSwitch service modules.
Multiple spanning-tree (MST) based on the IEEE 802.1s standard |
||
VRF Lite (multi-VRF-CE). This feature is not supported in the IP base image. Although configuration is allowed in this release, we strongly recommend that you do not configure it. Beginning with Cisco IOS Release 12.2(35)SE, you will receive an error message if you configure the feature on the IP base image. |
||
Support for configuring private-VLAN ports on interfaces that are configured for dynamic ARP inspection (IP base image [formerly known as the SMI] only) |
||
Support for IP source guard on private VLANs (IP base image [formerly known as the SMI] only) |
||
Support for VLAN-based QoS15 and hierarchical policy maps on SVIs16 |
||
Layer 2 point-to-point tunneling and Layer 2 point-to-point tunneling bypass |
||
Support for SSL version 3.0 for secure HTTP communication (cryptographic images only) |
||
Support for configuring private-VLAN ports on interfaces that are configured for dynamic ARP inspection (IP services image [formerly known as the EMI] only) |
||
Support for IP source guard on private VLANs (IP services image [formerly known as the EMI] only) |
||
Cisco intelligent power management to limit the power allowed on a port, or pre-allocate (reserve) power for a port. |
||
IEEE 802.1x accounting and MIBs (IEEE 8021-PAE-MIB and CISCO-PAE-MIB) |
||
Dynamic ARP inspection (IP services image [formerly known as the EMI] only) |
||
IP source guard (IP services image [formerly known as the EMI] only) |
||
Private VLAN (IP services image [formerly known as the EMI] only) |
||
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:
Unless otherwise noted, these limitations apply to the Catalyst 3750, 3560, and 2970, and 2960 switches and the Cisco EtherSwitch service modules:
These are the configuration limitations:
This problem occurs under these conditions:
– When the switch is booted without a configuration (no config.text file in flash memory).
– When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).
– When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
1. Disable auto-QoS on the interface.
2. Change the routed port to a nonrouted port or the reverse.
3. Re-enable auto-QoS on the interface. (CSCec44169)
– (Catalyst 3750 switch and Cisco EtherSwitch service modules) When the Network Time Protocol (NTP) is configured, but the NTP clock is not synchronized. You can check the clock status by entering the show NTP status privileged EXEC command and verifying that the network connection to the NTP server and the peer work correctly.
– (Catalyst 3750, 3560, or 2970 switches and Cisco EtherSwitch service modules) The DHCP snooping database file is manually removed from the file system. After enabling the DHCP snooping database by configuring a database URL, a database file is created. If the file is manually removed from the file system, the DHCP snooping database does not create another database file. You need to disable the DHCP snooping database and enable it again to create the database file.
– (Catalyst 3750, 3560, or 2970 switches and Cisco EtherSwitch service modules) The URL for the configured DHCP snooping database was replaced because the original URL was not accessible. The new URL might not take effect after the timeout of the old URL.
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)
The workaround is to use switch ports other than those specified for redundancy and for applications that immediately detect active links. (CSCeh70503)
These are the Ethernet limitations:
– Ports 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, and 24 of the Catalyst 3750G-24T and 3750G-24TS switches
– Ports 3, 4, 7, 8, 11, 12, 15, 16, 19, and 20 of the Catalyst 2970G-24T and 2970G-24TS switches
– Gigabit Ethernet ports on the Cisco EtherSwitch service modules
– Contact the NIC vendor, and get the latest driver for the card.
– Configure the interface for 1000 Mbps instead of for 10/100 Mbps.
– Connect the NIC to an interface that is not listed here. (CSCea77032)
For more information, enter CSCea77032 in the Bug Toolkit at this URL:
http://www.cisco.com/cgi-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 random source-ip and dest-ip traffic, configure load balance method as src-dst-ip
– for incrementing source-ip traffic, configure load balance method as src-ip
– for incrementing dest-ip traffic, configure load balance method as dst-ip
– Configure the number of ports in the EtherChannel so that the number is equal to a power of 2 (i.e. 2, 4, or 8)
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)
These are the fallback bridging limitations:
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)
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)
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)
These are the multicasting limitations:
Multicast is not supported on tunnel interfaces
error message. IP PIM is not supported on tunnel interfaces. There is no workaround. (CSCeb75366)– If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.
– If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.
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)
– You disable IP multicast routing or re-enable it globally on an interface.
– A switch mroute table temporarily runs out of resources and recovers later.
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
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.
– Cancel membership in the multicast group by using the no ip igmp join-group group-address interface configuration command on an SVI.
– Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id global configuration command. (CSCeh90425)
The workaround is to enable IP routing or to disable multicast routing on the switch. You can also use the ip igmp snooping querier global configuration command if IP multicast routing is enabled for queries on a multicast router port. (CSCsc02995)
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)
This 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)
These are the quality of service (QoS) limitations:
These are the routing limitations:
This 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)
– Port security is enabled with the violation mode set to protected.
– The maximum number of secure addresses is less than the number of switches connected to the port.
– There is a physical loop in the network through a switch whose MAC address has not been secured, and its BPDUs cause a secure violation.
The workaround is to change any one of the listed conditions. (CSCed53633)
These are the SPAN and Remote SPAN (RSPAN) limitations.
This is a hardware limitation and only applies to these switches (CSCdy72835):
– Cisco EtherSwitch service modules
This is a hardware limitation and only applies to these switches (CSCdy81521):
– Cisco EtherSwitch service modules
This is a hardware limitation and only applies to these switches (CSCea72326):
– Cisco EtherSwitch service modules
Decreased egress SPAN rate
. In all cases, normal traffic is not affected; the degradation limits only how much of the original source stream can be egress spanned. If fallback bridging and multicast routing are disabled, egress SPAN is not degraded. There is no workaround. If possible, disable fallback bridging and multicast routing. If possible, use ingress SPAN to observe the same traffic. (CSCeb01216)These are the Catalyst 3750 and Cisco EtherSwitch service module switch stack limitations:
There is no workaround. (CSCed54150)
IP-3-STCKYARPOVR
appears on the consoles of other default IP gateways. Because sticky ARP is not disabled, the MAC address update caused by the stack master re-election cannot complete.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):
– If the stack master is running the IP services image (formerly known as the EMI), all stack members have private VLAN enabled.
– If the stack master is running the IP base image (formerly known as the SMI), all stack members have private VLAN disabled.
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:
– Reload the stack after an IP services image (formerly known as the EMI) to IP base image (formerly known as the SMI) master switch change (or the reverse).
– Before an IP services image (formerly known as the EMI)-to-IP base image (formerly known as the SMI) master switch change, delete the private-VLAN configuration from the existing stack master. (CSCee06802)
This is the expected behavior of the offline configuration (provisioning) feature. There is no workaround. (CSCee12431)
The workaround is to copy the bootable image to the parent directory or first directory. (CSCei69329)
These are the trunking limitations:
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)
These sections describe the important notes related to this software release for the Catalyst 3750, 3560, and 2970, and 2960 switches and for the Cisco EtherSwitch service modules:
These notes apply to switch stacks:
These notes apply to Cisco IOS software:
– the no logging on and then the no logging console global configuration commands
– the logging on and then the no logging console global configuration commands
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)
If this message appears, check that there is network connectivity between the switch and the ACS. You should also check that the switch has been properly configured as an AAA client on the ACS.
These notes apply to the device manager:
From Microsoft Internet Explorer:
1. Choose Tools > Internet Options.
2. Click Settings in the “Temporary Internet files” area.
3. From the Settings window, choose Automatically.
5. Click OK to exit the Internet Options window.
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:
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, and 2960 switches and to Cisco EtherSwitch service modules:
When a Cisco IP Phone is connected to the switch, its MAC address is learned on both the port VLAN identification (PVID) and the voice VLAN identification (VVID). However, when the dynamic MAC addresses are either manually or automatically removed due to a topology change or enabling or disabling the port security or IEEE 802.1x feature, the Cisco IP Phone's MAC address will only be re-learned on the VVID. This occurs when the Cisco IP Phone is connected to a Cisco Catalyst 2970, 3560, or 3750 and the Cisco IP Phone is using software without the fix for CSCed84163.
When configured for a Voice VLAN, the phone sends untagged Cisco Discovery Protocol (CDP) packets and tagged voice packets. All frames from any devices connected to the Cisco IP Phone are sent tagged with the access VLAN ID. Catalyst 2970, 3560, and 3750 switches do not populate the secure address-table with the source MAC address from CDP packets.
The workaround is that when using Cisco IP Phones with the fix for CSCed84163 and port-security configured on the switchport, configure switches with one secure address for the phone, plus additional MAC addresses for any devices connected to the Cisco IP Phone.
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.
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.
– Connect to the router through the console port, and open a session to the service module.
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.
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.
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:
The 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.
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:
where x is the stack member number.
There is no workaround. This problem does not affect the switch functionality.
When an IEEE 802.1x restricted VLAN is configured on a port and a hub with multiple devices is connected to that port, no syslog messages are generated.
This is not a supported configuration. Only one host should be connected to an IEEE 802.1x restricted VLAN port.
When a switch running Cisco IOS image 12.2(25)SEA or later joins a stack running Cisco IOS 12.2(20)SE1 or earlier, the boot auto-copy-sw global configuration command might not work as expected. The new member switch might not be automatically upgraded or downgraded to the Cisco IOS image version that is running on the stack. If that happens, the new member switch is detected in a version mismatch state and is not operational.
The workaround is to follow the procedures displayed when the boot auto-copy-sw global configuration command fails. If another failure occurs, enter the archive download-sw privileged EXEC command on all switches in the stack.
When configuring a hierarchical policy map, changes to the match criteria of the VLAN level class-map do not take effect until the policy map is detached and reapplied.
The workaround is to detach the policy map from the interface, make the VLAN-level changes, and reapply the policy map.
Static IGMP snooping group members are inconsistent across different members in a Catalyst 3750 switch stack after a stack reload or an individual member switch reload.
There is an extra index in the port table of the ciscoStpExtensions MIB that does not exist in the portCrossIndex MIB. For example, extra indexes like 1000-16/40
are seen in stpxRootGuardConfigEnabled displays that do not exist in portCrossIndex, and they appear during an SNMP walk operation.
When a stack of Catalyst 3750 switches running Release 12.2(25)SED are configured with a Layer 3 LACP EtherChannel, tracebacks are generated when a master switchover occurs.
The workaround is to enable the persistent stack-mac feature on the switch by entering the stack-mac persistent timer switch configuration command.
When a Catalyst 3750 stack master fails or leaves the stack, a cross-stack EtherChannel in trunk mode running Link Aggregation Control Protocol (LACP) protocol might stop forwarding traffic on some VLANs.
The workaround is to enable the stack-mac persistent feature by using the stack-mac persistent timer global configuration command. You can also use the shutdown interface configuration command and then the no shutdown command on the EtherChannel interface.
When a Cisco device configured for Network Admission Control and the EAP over UDP port number is changed from its default value and then changed back with the eou default switch configuration command, the port change does not take effect, and EAP over UDP sessions can remain in a hold state.
The workaround is to reset the EAP over UDP port number to its default value (0x5566) by using the eou port 21862 switch configuration command.
When you configure a Cisco IP Phone to use Network Admission Control, the CDP packet is delayed, and the phone is identified as an agentless host without an identity profile.
The workaround is to enter the eou initialize ip address switch configuration command to revalidate the host that CDP has learned.
During IEEE 802.1x authentication, a RADIUS server might download a per-user IP address access control list (ACL) or a MAC address ACL that is applied to the interface as part of the Access-Accept message. If the ACL is too large, the switch might not be able to apply it, and authentication fails and starts over.
The workaround is to reduce the size of the per-user ACL access control entries (ACEs) to less than 20 if ACLs are downloaded as part of IEEE 802.1x authorization.
A nonstackable EtherSwitch Service Module boots with this provisioned switch error message:
This message is only informational.
MAC address notification traps do not work when port security is enabled on the interface.
The workaround is to disable port security on the interface.
The switch does not forward an IEEE802.1x request that has null credentials.
When a source port for a SPAN session has IEEE 802.1x enabled, Extensible Authentication Protocol over LAN (EAPOL) packets are not visible to the packet sniffing tool.
The workaround is to enable a voice VLAN on the SPAN source port.
When the master switch reloads one of the member switches, the interface of the member switch remains up, but the line protocol goes down. The MIB object returns this message: incorrect status.
When you filter a MAC address by entering mac-address-table static vlan drop global configuration command, IEEE 802.1X still authenticates that address
The switch might fail or display illegal memory access messages during the SNMP Timer process, while copying a configuration to the running configuration file using the CiscoConfigCopyMIB.
This might happen when rmon alarm global configuration commands are present in the running configuration before downloading the copy.
The workaround is to disable all rmon alarm global configuration commands by using the no rmon alarm global configuration command before copying the configuration.
Removing the bridge topology change trap with the no snmp-server enable traps bridge topologychange configuration command also disables the stpx root-inconsistency trap.
The workaround is to re-enable the stpx root-inconsistency trap by using the snmp-server enable traps stpx configuration command.
This error message appears during authentication when a method list is used and one of the methods in the method list is removed:
There is no workaround. However, this is only an informational message and does not affect switch functionality.
When reloading a Cisco EtherSwitch service module that is a member of a switch stack with port security enabled, the following traceback might appear:
PSECURE: Assert failure: 0:../switch/psecure/psecure_events.c: 2034: psecure_vp_list_fwdchange
There is no workaround. This message can be ignored.
When the switch displays a STORM_CONTROL-3-SHUTDOWN
message, and a port status changes to disabled, the cpscEvent (cpscStatus) Trap incorrectly shows that the CPortStormControlStatusType is 2, which means forwarding. (The correct status is 5, which means shutdown.)
When the radius-server source-ports 1645-1646 global configuration command is removed, the switch sends the RADIUS server requests with incorrect source ports. This causes failed authentication attempts.
The workaround is to reload the switch, which restores the reload radius-server source-ports 1645-1645 global configuration command to the configuration and re-establishes communication with the RADIUS server.
A switch might display a traceback during a stack master change under these conditions:
– The switch is a member of a stack.
– The switch stack includes at least six members.
– The switch stack contains both Catalyst 3750 and Catalyst 3750G switches.
There is no workaround. This is a warning that has no operational effect.
The entPhysicalIndex in the entPhysicalTable (ENTITY-MIB) for SFPs becomes incorrect when master and slaves are reloaded at the same time, and the invalid SFP entry in the entPhysicalTable might overwrite the chassis entry.
The workaround is to first boot the master and then the slaves.
The switch fails when the VPN Routing and Forwarding (VRF) configuration is removed under these conditions:
– VRF is removed by using the no ip vrf global configuration command.
– Interfaces are configured in two or more VRFs.
– One VRF has static address resolution protocols (ARPs) configured.
– The VRF with static ARPs is removed first.
The failure occurs when the second VRF is removed.
The workaround is to remove the static ARP entries configured on a VRF prior to deleting it.
The switch might display tracebacks similar to these examples when a large number of IEEE 802.1x supplicants try to repeatedly log in and log out.
Jan 3 17:54:32 L3A3 307: Jan 3 18:04:13.459: %SM-4-BADEVENT: Event 'eapReq' is invalid for the current state 'auth_bend_idle': dot1x_auth_bend Fa9
Jan 3 17:54:32 L3A3 308: -Traceback= B37A84 18DAB0 2FF6C0 2FF260 8F2B64 8E912C Jan 3 19:06:13 L3A3 309: Jan 3 19:15:54.720: %SM-4-BADEVENT: Event 'eapReq_no_reAuthMax' is invalid for the current ate 'auth_restart': dot1x_auth Fa4
Jan 3 19:06:13 L3A3 310: -Traceback= B37A84 18DAB0 3046F4 302C80 303228 8F2B64 8E912C Jan 3 20:41:44 L3A3 315:.Jan 3 20:51:26.249: %SM-4-BADEVENT: Event 'eapSuccess' is invalid for the current state 'auth_restart': dot1x_auth Fa9
Jan 3 20:41:44 L3A3 316: -Traceback= B37A84 18DAB0 304648 302C80 303228 8F2B64 8E912C
When IEEE 802.1x is globally disabled on the switch by using the no dot1x system-auth-control global configuration command, some interface level configuration commands, including the dot1x timeout and dot1x mac-auth-bypass commands, become unavailable.
The workaround is to enable the dot1x system-auth-control global configuration command before attempting to configure interface level IEEE 802.1x parameters.
on command to the configuration and re-establishes communication with the RADIUS server.
When you remove a voice VLAN from a secure port, this message appears:
PORT_SECURITY-6-VLAN_REMOVED: VLAN xxx is no longer allowed on port ppp. Its port security configuration has been removed.
There is no workaround.This is only a notification; no action is required.
After a master changeover, error messages about invalid port security configuration might appear under these circumstances:
– Port security and 802.1x are enabled on a port.
– A supplicant is authenticated.
– An IEEE 802.1x VLAN assignment, such as guest VLAN, restricted VLAN, or RADIUS assigned VLAN, has occurred.
There is no workaround. The error message is informational only and does not affect switch functionality.
If you globally disable IEEE 802.1x authentication by using the no dot1x system-auth-control global configuration command and if the dot1x port-control auto or the dot1x port-control force-unauthorized interface configuration command was previously entered, the dot1x port-control auto or the dot1x port-control force-unauthorized interface configuration command takes effect, and the host cannot access the port.
The workaround is to enter the no dot1x port-control interface configuration command to return to the default setting of force-authorized.
After a switch stack is reloaded, SFP-module info such as the serial number or type might not appear in the entPhysicalTable (ENTITY-MIB).
These are the workarounds (you must do one of these):
– Reboot the master switch and then reboot the slave switches.
This section describes the caveats have been resolved in this release. Unless otherwise noted, these resolved caveats apply to the Catalyst 3750, 3560,and 2970, and 2960 switches and the Cisco EtherSwitch service modules:
Open Shortest Path First (OSPF) routes now appear in the routing table after a topology change when Incremental SPF (iSPF) is enabled.
When a non powered Cisco IP Phone is connected to a switch that does not provide inline power, the interface no longer comes up when the down-when-looped interface configuration command is configured.
Symptoms: A router may crash if it receives a packet with a specific crafted IP option as detailed in Cisco Security Advisory: Crafted IP Option Vulnerability:
http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml
Conditions: This DDTS resolves a symptom of CSCec71950. Cisco IOS with this specific DDTS are not at risk of crash if CSCec71950 has been resolved in the software.
Workaround: Cisco IOS versions with the fix for CSCec71950 are not at risk for this issue and no workaround is required. If CSCec71950 is not resolved, see the following Cisco Security Advisory: Crafted IP Option Vulnerability for workaround information:
http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml
The Cisco IOS Transmission Control Protocol (TCP) listener in certain versions of Cisco IOS software is vulnerable to a remotely-exploitable memory leak that may lead to a denial of service condition.
This vulnerability only applies to traffic destined to the Cisco IOS device. Traffic transiting the Cisco IOS device will not trigger this vulnerability.
Cisco has made free software available to address this vulnerability for affected customers.
This issue is documented as Cisco bug ID CSCek37177.
There are workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml
Policy-based routing (PBR) for IP Version 4 (IPv4) traffic is available when you run IPv4 and IPv6 traffic on the switch, because the Dual IPv4-IPv6 Switch Database Management (SDM) templates now have resource provisions for PBR.
If you use the no snmp-server enable traps stpx mode command, BRIDGE-MIB traps are no longer disabled.
When a switch must authenticate a large number of IEEE 802.1x-enabled ports, and hosts are logging in and out every few seconds, the switch no longer displays HRPC dot1x request handler error messages.
The Cross Stack UplinkFast feature is no longer delayed by 30 seconds when all the interfaces on the root switch are configured with the no shutdown interface configuration command.
A non-responsive host (NRH) policy is no longer applied to a Cisco IP phone when a LAN port IP (LPIP) exception policy should be applied to it. (In previous releases, when a Cisco IP phone was attached to a port it was sometimes not detected by LAN port IP [LPIP] and was configured as a clientless or an NRH.)
Configuring static IP routes with new distance values no longer causes routes to disappear from the routing table.
Commit errors no longer occur when SNMP is used to disable the 802.1X guest-vlan feature (by setting the cpaeGuestVlanNumber object to a value of 0).
When using Simple Network Management Protocol to disable the IEEE 802.1x guest VLAN feature, the SNMP client no longer receives an error message.
If two VLANs are configured on the same switch (for example, VLAN 1 and VLAN 2) with an SVI configured in VLAN 1 and an external bridging device connected to the switch, traffic sent from VLAN 2 to the SVI in VLAN 1 is no longer dropped.
The output of the show controller utilization user EXEC command no longer incorrectly shows a Gigabit interface at 100 percent utilization.
The switch now downloads the reauthentication timer and reauthentication action from the RADIUS server only when the port is configured with the dot1x timeout reauth server interface configuration command.
When the master switch in a stack of Catalyst 3750 switches is reloaded, all remarks that were part of individual access control entries (ACEs) now appear with their associated ACE entries.
The hierarchical per-VLAN policy-map police action now works correctly when a child policy-map is not configured in the first class-map.
A switch no longer fails when the VPN Routing and Forwarding (VRF) configuration is removed under these conditions:
– VRF is removed by using the no ip vrf global configuration command.
– Interfaces are configured in two or more VRFs.
– One VRF has static address resolution protocols (ARPs) configured.
– The VRF with static ARPs is removed first.
In previous releases, a failure occured when the second VRF was removed.
When both IEEE 802.1x and standard per-user ACL are configured on a member switch in a switch stack, the switch no longer fails when a supplicant tries to authenticate.
When the cable connected to a Gigabit Ethernet port on a Catalyst 2970 switch is unplugged, under these conditions, the switch no longer recalculates its port state and role on other ports:
– The port is in the alternate state before the cable is unplugged.
– The configured port speed is 100 Mbps.
– The port is configured for full-duplex operation.
– This port would have been chosen the root port if a speed of 100 Mbps had not been configured on the port.
When a member switch is reset and then reset again in less than 10 seconds, multicast users connected to the switch now receive multicast traffic from other VLANs or interfaces in the switch stack.
The switch now sends the NAS-Identifier, attribute 32, to the RADIUS server when you configure the attribute in the running configuration by using these Cisco IOS global configuration commands:
radius-server attribute 32 include-in-access-req [format %h]
radius-server attribute 32 include-in-accounting-req [format &h]
IEEE 802.1s authorization no longer fails on a port under these circumstances:
– A switch is configured for IEEE 802.1x authentication and VLAN assignment by a RADIUS server.
– The port receives the VLAN ID from the RADIUS that is identical to the VLAN ID for which the port is configured.
A switch doing IEEE 802.1x authorization with an AAA server no longer fails when connectivity is lost to the AAA server and AAA authorization is configured to default to a group of none.
Processing a specially crafted IPv6 Type 0 Routing header can crash a device running Cisco IOS software. This vulnerability does not affect IPv6 Type 2 Routing header which is used in mobile IPv6. IPv6 is not enabled by default in Cisco IOS.
Cisco has made free software available to address this vulnerability for affected customers.
There are workarounds available to mitigate the effects of the vulnerability. The workaround depends on if Mobile IPv6 is used and what version on Cisco IOS is being currently used.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml
This section provides these updates to the product documentation for the Catalyst 3750, 3560, 2970, and 2960 switches:
This information was added to the R egulatory Compliance and Safety Information for the Catalyst 3750, 3560, 2970, and 2960 switches:
This is the documentation update for the software configuration guides for this release:
In the “Configuring Network Security with ACLs” chapter, the note in Step 3 of the “Configuring VLAN Maps” section is inaccurate. The correct text is:
Note If the VLAN map is configured with a match clause for a type of packet (IP or MAC) and the map action is drop, all packets that match the type are dropped. If the VLAN map has no match clause, and the configured action is drop, then all IP and Layer 2 packets are dropped.
These documents provide complete information about the Catalyst 3750, 3560, and 2970, and 2960 switches and the Cisco EtherSwitch service modules and are available at Cisco.com:
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 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:
These documents provide complete information about the Catalyst 2960 switches:
For other information about related products, see these documents:
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.
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:
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML 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= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:
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/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
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 submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
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 will find information about how to:
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
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 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 We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.
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.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
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.
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 Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
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-2447
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing 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 operations 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 the network is impaired, while 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.
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