Device Manager System Requirements
Finding the Software Version and Feature Set
Catalyst 3750G Integrated Wireless LAN Controller Switch Software Compatibility
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)
Caveats Resolved in Cisco IOS Release 12.2(35)SE5
Resolved Caveats in Cisco IOS Release 12.2(35)SE2
Resolved Caveats in Cisco IOS Release 12.2(35)SE1
Resolved Caveats in Cisco IOS Release 12.2(35)SE
Updates for the System Message Guide
Update to the Catalyst 2960 Software Configuration Guide
Configuring Web Authentication
Update to the Catalyst 2960 Command Reference
Updates to the Catalyst 3750 Getting Started Guide
Updates for the Regulatory Compliance and Safety Information
Statement 361—VoIP and Emergency Calling Services do not Function if Power Fails
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco IOS Release 12.2(35)SE and SE1 run on all Catalyst 3750, 3560, 2970, and 2960 switches and on Cisco EtherSwitch service modules. Cisco IOS Release 12.2(35)SE5 runs on Catalyst 3750 switches and 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(35)SE and later and any limitations, restrictions, and caveats that apply to the releases. 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
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.
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 this release.
24 10/100/1000 PoE1 ports, 2 SFP2 module slots, and an integrated wireless LAN controller supporting up to 25 access points. |
Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE |
|
24 10/100/1000 PoE ports, 2 SFP module slots, and an integrated wireless LAN controller supporting up to 50 access points |
Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE |
|
16 10/100/1000 Ethernet ports and 1 XENPAK 10-Gigabit Ethernet module slot |
||
8 10/100 PoE ports and 1 dual-purpose port3 (one 10/100/1000BASE-T copper port and one SFP module slot) |
||
8 10/100 Ethernet ports and 1 dual-purpose port ==(one 10/100/1000BASE-T copper port and one SFP module slot) |
||
7 10/100/1000 Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot) |
||
24 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP module slots) |
||
48 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP 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, including 4 dual-purpose ports (four 10/100/1000BASE-T copper ports and four SFP module slots) |
||
NME-16ES-1G4 |
16 10/100 ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide |
|
16 10/100 PoE ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide |
||
23 10/100 ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide |
||
23 10/100 PoE ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide |
||
24 10/100 PoE ports, 1 SFP module port, 2 StackWise connector ports, extended double-wide |
||
48 10/100 PoE ports, 2 SFP module ports, no StackWise connector ports, extended double-wide |
||
1000BASE-CWDM5, -LX, SX, -T, -ZX 100BASE-FX MMF6 |
||
XENPAK modules7 |
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 SystemCisco 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
10
|
|||
---|---|---|---|
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(35)SE and later is only compatible with Cisco Network Assistant (CNA) 5.0 and later. You can download Cisco Network Assistant 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. |
The Catalyst 3750 Integrated Wireless LAN Controller Switch is an integrated Catalyst 3750 switch and Cisco 4400 series wireless LAN controller that supports up to 25 or 50 lightweight access points. The switch and the internal controller run separate software versions, which must be upgraded separately. If the image versions are not compatible, the wireless LAN controller switch could stop functioning. Table 6 is the compatibility matrix for Catalyst 3750 and wireless controller.
For information about this controller software release, see the Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Point, Release 4.0.x.0. For controller software upgrade procedure, see the Cisco Wireless LAN Controller Configuration Guide Release 4.0.
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 and updated software features provided in this release:
There are no new hardware features for this release. For a list of all supported hardware, see the “Hardware Supported” section.
These are the new software features for this release:
Note NSF is not supported on interfaces running Hot Standby Routing Protocol (HSRP).
Starting with Cisco IOS Release 12.2(25)SEE1, the device manager GUI, online help, and the Catalyst 2960 Switch Getting Started Guide are now available in Chinese (simplified), English, French, German, Italian, Japanese, and Spanish.
To display a translated version of the GUI and online help, select your language from the Language field located at the top of the device manager window.
The translated getting started guides are available at this URL:
http://www.cisco.com/en/US/products/ps6406/tsd_products_support_series_home.html
Table 7 lists the minimum software release required to support the major features of the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules.
Generic online diagnostics to test the hardware functionality of the supervisor engine. |
||
Stack MAC persistent timer and archive download enhancements |
||
OSPF and EIGRP Nonstop forwarding capability (IP services image only) |
||
IPv6 router ACLs for inbound Layer 3 management traffic in the IP base and IP services image |
||
Generic online diagnostics to test the hardware functionality of the supervisor engine. |
||
Multiple spanning-tree (MST) based on the IEEE 802.1s standard |
||
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 QoS14 and hierarchical policy maps on SVIs15 |
||
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, 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)
The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. (CSCsf32300)
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)
The workaround is to assign a lower path cost to the forwarding port. (CSCsd95246)
This can but does not always occur during link flaps and does not last for more than a few milliseconds. This problem can happen for cross-stack EtherChannels with the mode set to ON or LACP.
There is no workaround. No manual intervention is needed. The problem corrects itself within a short interval after the link flap as all the switches in the stack synchronize with the new load-balance configuration. (CSCse75508)
The workaround is to reboot the new member switch. Use the remote command all show run privileged EXEC command to compare the running configurations of the stack members. (CSCsf31301)
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 are the device manager limitations:
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
These sections describe the important notes related to this software release for the Catalyst 3750, 3560, 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, 2970, and 2960 switches and to Cisco EtherSwitch service modules:
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.
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 traffic is passing through VMPS ports and you perform a shut operation, a dynamic VLAN is not assigned and a VLAN with a null ID appears.
The workaround is to clear the MAC address table. This forces the VMPS server to correctly reassign the VLAN.
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.
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
Entering the reload privileged EXEC command might not reload the switch after these events occur in the order listed:
a. An SNMP configuration file that contains crypto key generate rsa
is copied to the switch running configuration.
b. An snmp set command is performed.
c. The reload command is entered.
The workaround is to not copy an SNMP configuration with a configuration file that contains crypto key generate rsa
. If the switch has existing keys, the Cisco IOS operating system expects either a Yes or No response that you want to replace the existing keys. If the switch does not have existing keys, the system expects the key size. The system never receives the Yes or No response nor the key size because the copy operation is performed from SNMP.
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.
The error message %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND might appear in a switch stack under these conditions:
– A supplicant is authenticated on at least one port.
– A new member joins a switch stack.
When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is within the configured rate limit, the port might go into an error-disabled state.
The workaround is to configure the burst interval to more than 1 second.
When the dynamic ARP inspection trust setting is removed from a large number of ports across multiple members of a stack, a %PLATFORM_RPC-3-MSG_THROTTLED message might appear.
The workaround is to remove the trust settings on a small number of ports one switch at a time. If the problem still occurs, continue to reduce the number of ports.
When cross-stack UplinkFast (CSUF) is configured on a switch and one of the member ports is flapping, packets transmitted from an EtherChannel port might be duplicated.
The error message %HPSECURE-6-ADDR_REMOVED might appear in a switch stack under these conditions:
– Port security is enabled on at least one port.
– Some secure addresses exist in the switch state.
– A new member joins a switch stack.
When there are more than five switches in a stack or when four or more switches join a stack, there might be a long delay between the time the Ready prompt appears and a switch that is starting up begins carrying traffic. This delay can last several minutes.
There is no workaround. However, this condition only causes a delay during switch startup, and no data is lost.
When dynamic ARP inspection is enabled and IP validation is disabled, the switch drops ARP requests that have a source address of 0.0.0.0.
The workaround is to configure an ARP access control list (ACL) that permits IP packets with a source IP address of 0.0.0.0 (and any MAC) address) and apply the ARP ACL to the desired DAI VLANs.
When MAC addresses are learned on an Etherchannel port, the addresses are incorrectly deleted from the MAC address table even when the MAC address table aging timeout value is configured to be longer than the ARP timeout value. This causes intermittent unicast packet flooding in the network.
The MAC address is automatically relearned after the ARP refresh. The workaround is to enter the ping ip address privileged EXEC command from the switch to the next hop router to avoid the intermittent flooding.
When you configure an IP address on a switch virtual interface (SVI) with DCHP and enable DHCP snooping on the SVI VLAN, the switch SVI cannot obtain an IP address.
The workaround is to not enable DCHP snooping on the SVI VLAN or to use a static IP address for the SVI.
Clearing secure addresses by entering the clear port-security global configuration command in a stack member might cause traffic to be dropped from the switch. Some secure addresses learned on the stack master might not be learned on a stack member. Packets with a secure source address might also be dropped.
These are the workarounds. You only need to do one of these:
– Enter the clear port-security global configuration command to stop the traffic.
– Enter the shut and no shut interface configuration commands on the port where the traffic is being dropped.
CSCsg70039 (Catalyst 3750 and 3560 switches)
When both an authorized data domain and an authorized voice domain is present on a port, and you change the VLAN configuration on the port to equal the assigned VLAN, a traceback error appears. This problem only occurs on the ports of a member switch.
The workaround is to change the voice VLAN to a value that does not match the assigned VLAN or VLAN feature (such as a guest VLAN).
During repeated reauthentication of supplicants on an IEEE 802.1x-enabled switch, if the RADIUS server is repeatedly going out of service and then coming back up, the available switch memory might deplete over time, eventually causing the switch to shut down.
There is no work-around, except to ensure that the RADIUS server is stable.
When a device is attached to a multidomain authentication (MDA)- enabled port that has IEEE 802.1x guest VLAN configured but not MAC authentication bypass (MAB), if the switch gets its MAC address from that port, the device is authenticated in the guest VLAN but appears as an IEEE 802.1x-authenticated device.
The workaround is to enable MAB by entering the dot1x mac-auth-bypass interface configuration command, or enter the dot1x timeout tx-period 1 to set the IEEE 802.1x timeout period to 1 second.
If IEEE 802.1x critical authentication is not enabled and the RADIUS authentication server is temporarily unavailable during a reauthentication, when the RADIUS server comes back up, MAC authentication bypass (MAB) does not authenticate a previously authenticated client.
The workaround is to enter the shutdown interface configuration command followed by the no shutdown command on the port connected to the client. An alternative, to prevent the problem from occurring, is to enable critical authentication by entering the dot1x critical {eapol | recovery delay milliseconds} global configuration command.
An IEEE 802.1x port configured for Multi-Domain Authentication does not allow access to the guest VLAN if an IEEE 802.1x supplicant has previously authenticated and then logged off.
On a Catalyst 3750 or Catalyst 3560 switch running Cisco IOS Release 12.2(35)SE or later, when an 802.1x port is configured for Multi-Domain Authentication and Guest VLAN, the guest VLAN feature is disabled once an 802.1X-enabled client has attached on the port. The feature remains disabled until the link goes down on the port. The result is that if an IEEE802.1x-enabled host is attached to the switch through an IP phone and is later replaced by a non-IEEE802.1x enabled host, the new host is not able to access the network via the guest VLAN. Instead, the port keeps trying to authenticate the new host (via IEEE802.1x or MAC Authentication Bypass indefinitely.
The workaround is to enter the dot1x guest-vlan supplicant global configuration command to allow access to the guest VLAN even after EAPoL packets have been seen on a port.
This sections describes the caveats that have been resolved in this release:
Unless otherwise noted, these resolved caveats apply to the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules.
The output of the show ip route privileged EXEC command now correctly displays the default gateway.
The stack master switch no longer resets with an error message when you enter the show storm-control user EXEC command and specify a stack member interface that is not configured for storm control.
The switch no longer reloads when the write core privileged EXEC command is entered when testing a core dump configuration and FTP is selected as the file transfer protocol.
A switch no longer displays this error message when reading from or writing to the configuration file:
When DHCP snooping is enabled on a VLAN, the broadcast DHCP request is now correctly sent over the trusted port and the connected hosts correctly receive their IP addresses.
These caveats were resolved in Cisco IOS Release 12.2(35)SE2:
A vulnerability has been discovered in a third party cryptographic library which is used by a number of Cisco products. This vulnerability may be triggered when a malformed Abstract Syntax Notation One (ASN.1) object is parsed. Due to the nature of the vulnerability it may be possible, in some cases, to trigger this vulnerability without a valid certificate or valid application-layer credentials (such as a valid username or password).
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
The vulnerable cryptographic library is used in the following Cisco products:
– Cisco IOS, documented as Cisco bug ID CSCsd85587
– Cisco IOS XR, documented as Cisco bug ID CSCsg41084
– Cisco PIX and ASA Security Appliances, documented as Cisco bug ID CSCse91999
– Cisco Unified CallManager, documented as Cisco bug ID CSCsg44348
– Cisco Firewall Service Module (FWSM)
This vulnerability is also being tracked by CERT/CC as VU#754281.
Cisco has made free software available to address this vulnerability for affected customers. There are no workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
Note Another related advisory is posted together with this Advisory. It also describes vulnerabilities related to cryptography that affect Cisco IOS. A combined software table for Cisco IOS only is available at http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml and can be used to choose a software release which fixes all security vulnerabilities published as of May 22, 2007. The related advisory is published at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
A Gigabit Ethernet port on a Catalyst 3750 switch running Cisco IOS Release 12.2(35)SE1 shows linkup but no data goes through the port, including pinging the host through the port. This problem is fixed in Cisco IOS Release 12.2(35)SE2.
On a Catalyst 3750 switch, changing the MAC address or VLAN ID associated with an IPv4 or IPv6 address present in the ARP table or neighbor table no longer might impact traffic forwarding.
These caveats were resolved in Cisco IOS Release 12.2(35)SE1:
DHCP snooping now works when the switch is in VTP server mode and VLANs with IDs greater than 255 (256 and above) are created.
When multiple hosts are authenticated on an IEEE 802.1X-enabled port that is configured with multidomain authentication (MDA), a START/STOP RADIUS Attribute-Value (AV) pair is now sent for each host.
Access control lists that are applied to routed ports on a member switch are now programmed into the switch hardware.
The MAC access bypass (MAB) inactivity timer is no longer applied to an IP phone (Cisco or non-Cisco) connected to an IEEE 802.1x-enabled port that is configured with multidomain authentication (MDA).
A query of the SNMP MIB object chassisFanStatus.0 no longer returns a value of 4 (which indicates that the fan is faulty) when the fan is operating properly.
These caveats were resolved in Cisco IOS Release 12.2(35)SE:
If two or more switches in a stack of PoE switches restarted at the same time and you entered the no switch stack-member-number provision global configuration command, this message no longer appears on the console:
%Command not applied to switch x, remote error
When an IEEE 802.1x restricted VLAN is configured on a port and a hub with multiple devices are connected to that port, syslog messages are now generated.
This is not a supported configuration. Only one host should be connected to an IEEE 802.1x restricted VLAN port.
When a switch joins a stack running Cisco IOS 12.2(20)SE1 or earlier, the boot auto-copy-sw now works correctly.
If two Cisco EtherSwitch service modules were directly connected through Fast Ethernet interfaces configured as both 100 Mbps and full duplex and as automatic speed and duplex settings, one interface might have detected the other as a Cisco-powered device.
Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
– Processing ClientHello messages, documented as Cisco bug ID CSCsb12598
– Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304
– Processing Finished messages, documented as Cisco bug ID CSCsd92405
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
– Processing ClientHello messages, documented as Cisco bug ID CSCsb12598
– Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304
– Processing Finished messages, documented as Cisco bug ID CSCsd92405
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
An extra index no longer appears in the port table of the ciscoStpExtensions MIB.
When a stack of Catalyst 3750 switches are configured with a Layer 3 LACP EtherChannel, tracebacks are no longer generated when a stack master failover occurred.
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 no longer stops forwarding traffic on some VLANs.
When a Cisco device is configured for Network Admission Control and the EAP over UDP port number changes from its default value and then changes back with the eou default switch configuration command, the port change now takes effect.
When you configure a Cisco IP Phone to use Network Admission Control, the CDP packet is no longer delayed, and the phone is no longer identified as an agentless host without an identity profile.
A nonstackable EtherSwitch Service Module no longer boots with this provisioned switch error message:
Secure server will use temporary self-signed certificate.
When you configure a MAC address filter by entering the mac-address-table static vlan drop global configuration command, IEEE 802.1X no longer authenticates supplicants using that address. If a supplicant with that address is authenticated, its authorization is revoked.
When you remove the bridge topology change trap with the no snmp-server enable traps bridge topologychange configuration command, the stpx root-inconsistency trap is now active.
When reloading a Cisco EtherSwitch service module that is a member of a switch stack and port security is enabled on the stack, a PSECURE traceback error no longer appears.
When you reload the stack master and a stack member at the same time, the entPhysicalIndex in the entPhysicalTable (ENTITY-MIB) for the SFP modules is now correct.
A switch no longer fails when the VPN Routing and Forwarding (VRF) configuration is removed under these conditions (in this order):
– Interfaces are configured in two or more VRFs.
– One VRF has static address resolution protocols (ARPs) configured.
– The VRF configuration with static ARPs is removed.
– The second VRF configuration is removed.
VRF is removed by using the no ip vrf global configuration command.
When the switch is running Ethernet over multiprotocol label switching (EoMPLS) in Cisco IOS Release 12.2(25)SED, the switch virtual interface (SVI) service policy now polices data traffic according to its defined policy.
When you reload a switch stack, the SFP module information now appears in the entPhysicalTable (ENTITY-MIB).
If you insert a defective SFP module into the switch SFP module slot, HSRP links flap and CPUHOG error messages are no longer sent.
When you clear the ARP by entering the clear arp user [interface <name>] EXEC command or when the ARP entry times out, the switch now sends packets with the correct destination MAC address.
When IGMP snooping is enabled and an EtherChannel member interface goes down, the switch now forwards multicast traffic on the rest of the EtherChannel member interfaces.
When IEEE 802.1x authentication was configured on a voice VLAN port, the switch did not forward traffic if the attached PC was configured for both machine authentication and user authentication.
An authenticated 802.1X port might not have forwarded traffic in these conditions:
– The port is assigned to a voice VLAN.
– The PC is configured for both machine authentication and user authentication.
– The machine-initiated and user-initiated authentications result in different VLANs being assigned to the port.
Sometimes the switch dropped a fragmented multicast packet when it did not have the (S,G) entry, and more than 600 packets per second (pps) of other multicast traffic were sent to the switch CPU.
When you apply the mls qos trust dscp global configuration command to a port, this error message no longer appears:
command failed on GigabitEthernetx/x
When you remove and reconfigure a loopback interface, it no longer appears in the ifTable.
When you configure the ip cef load-sharing algorithm universal <id> global configuration command on the master switch, the command now appears in the stack member's running configuration. If the command is not configured on the master, it does not appear on the stack member switches.
The output from the show interface global configuration command now shows private VLANs for notconnect ports.
Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
– Processing ClientHello messages, documented as Cisco bug ID CSCsb12598
– Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304
– Processing Finished messages, documented as Cisco bug ID CSCsd92405
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
EtherChannels with very long allowed VLAN lists no longer experience a link flap when a master failover occurs.
A routing protocol flap no longer occurs when a stack member joins the stack.
When you remove a voice VLAN that has no per-VLAN configuration from a secure port, a PORT_SECURITY-6-VLAN_REMOVED message no longer appears.
Note: If an address was learned on a VLAN, the error message still appears when that VLAN is aged out or removed. However, this does not affect switch functionality.
If a switch is connected to a third-party router through an EtherChannel and the EtherChannel is running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel no longer fail after you enter the switchport trunk native vlan vlan-id interface configuration command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.
If a Putty client is used to change the configuration to a device with SSH, the switch no longer stops responding to incoming traffic, such as SSH, Telnet, or ping packets.
If fallback bridging is enabled on a routed port connected to an IEEE 802.1Q trunk port that is an EtherChannel member, the EtherChannel is no longer disabled after receiving the DTP frames.
Multiple Cisco products contain either of two authentication vulnerabilities in the Simple Network Management Protocol version 3 (SNMPv3) feature. These vulnerabilities can be exploited when processing a malformed SNMPv3 message. These vulnerabilities could allow the disclosure of network information or may enable an attacker to perform configuration changes to vulnerable devices. The SNMP server is an optional service that is disabled by default. Only SNMPv3 is impacted by these vulnerabilities. Workarounds are available for mitigating the impact of the vulnerabilities described in this document.
The United States Computer Emergency Response Team (US-CERT) has assigned Vulnerability Note VU#878044 to these vulnerabilities.
Common Vulnerabilities and Exposures (CVE) identifier CVE-2008-0960 has been assigned to these vulnerabilities.
This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20080610-snmpv3.shtml
This section provides these updates to the product documentation for the Catalyst 3750, 3560, 2970, and 2960 switches:
When you configure one end of an EtherChannel in either PAgP or LACP mode, the system negotiates with the other end of the channel to determine which ports should become active. In previous releases, the incompatible ports were suspended. Beginning with Cisco IOS Release 12.2(35)SE, instead of a suspended state, the local port is put into an independent state and continues to carry data traffic as would any other single link. The port configuration does not change, but the port does not participate in the EtherChannel.
For new messages in this release, see the Catalyst 3750, 3560, 3550, 2970, and 2960 Switch System Message Guide, 12.2(35)SE at this URL: http://www.cisco.com/en/US/products/hw/switches/ps5023/products_system_message_guides_list.html
These sections were added to the “Configuring IEEE 802.1x” chapter:
You can use a web browser to authenticate a client that does not support IEEE 802.1x functionality.
You can configure a port to use only web authentication. You can also configure the port to first try and use IEEE 802.1x authentication and then to use web authorization if the client does not support IEEE 802.1x authentication.
Web authentication requires two Cisco Attribute-Value (AV) pair attributes:
Note The proxyacl entry determines the type of allowed network access.
For more information, see the “Configuring Web Authentication” section.
Beginning in privileged EXEC mode, follow these steps to configure authentication, authorization, accounting (AAA) and RADIUS on a switch before configuring web authentication. The steps enable AAA by using RADIUS authentication and enable device tracking.
This example shows how to enable AAA, use RADIUS authentication and enable device tracking:
Beginning in privileged EXEC mode, follow these steps to configure a port to use web authentication:
This example shows how to configure only web authentication on a switch port:
Beginning in privileged EXEC mode, follow these steps to configure a switch port for IEEE 802.1x authentication with web authentication as a fallback method:
This example shows how to configure IEEE 802.1x authentication with web authentication as a fallback method.
For more information about the ip admission name and dot1x fallback commands, see the command reference for this release.
Use the dot1xfallback interface configuration command on the switch stack or on a standalone switch to configure a port to use web authentication as a fallback method for clients that do not support IEEE 802.1x authentication. To return to the default setting, use the no form of this command.
You must enter the dot1x port-control auto interface configuration command on a switch port before entering this command.
This example shows how to specify a fallback profile to a switch port that has been configured for IEEE 802.1x authentication:
You can verify your settings by entering the show dot1x [ interface interface-id ] privileged EXEC command.
Use the fallback profile global configuration command on the switch stack or on a standalone switch to create a fallback profile for web authentication. To return to the default setting, use the no form of this command.
The fallback profile is used to define the IEEE 802.1x fallback behavior for IEEE 802.1x ports that do not have supplicants. The only supported behavior is to fall back to web authentication.
After entering the fallback profile command, you enter profile configuration mode, and these configuration commands are available:
This example shows how to create a fallback profile to be used with web authentication:
You can verify your settings by entering the show running-configuration [ interface interface-id ] privileged EXEC command.
This example shows how to apply a web authentication rule to a switchport:
This example shows how to apply a web authentication rule to a fallback profile for use on an IEEE 802.1x enabled switch port.
The ip admission name proxy http command globally enables web authentication on a switch.
After you enable web authentication on a switch, use the ip access-group in and ip admission web-rule interface configuration commands to enable web authentication on a specific interface.
This example shows how to configure only web authentication on a switchport:
This example shows how to configure IEEE 802.1x authentication with web authentication as a fallback mechanism on a switchport.
Use the show fallback profile privileged EXEC command to display the fallback profiles that are configured on a switch.
show fallback profile [ append | begin | exclude | include | {[redirect | tee] url } expression ]
Use the show fallback profile privileged EXEC command to display profiles that are configured on the switch.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain Output are displayed.
The Express Setup configuration windows were updated in the getting started guide. This is the complete procedure:
When you first set up the switch, you should use Express Setup to enter the initial IP information. This enables the switch to connect to local routers and the Internet. You can then access the switch through the IP address for further configuration.
This information was added to the Regulatory Compliance and Safety Information for the Catalyst 3750, 3560, 2970, and 2960 switches.
These documents provide complete information about the Catalyst 3750, 3560, 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 listed in the “Obtaining Documentation, Obtaining Support, and Security Guidelines” 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 3750G Integrated Wireless LAN Controller Switch and the integrated wireless LAN controller and are available at cisco.com:
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:
Note The above getting started guide, orderable in print, provides information in all supported languages. Listed below are online-only getting started guides in the individual languages.
For other information about related products, see these documents:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
– Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix (not orderable but available on Cisco.com)
– Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix (not orderable but available on Cisco.com)
– Cisco Small Form-Factor Pluggable Modules Compatibility Matrix (not orderable but available on Cisco.com)
– Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules (not orderable but available on Cisco.com)
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html