Table Of Contents
Release Notes for the Cisco EtherSwitch Service Modules, Cisco IOS Release 12.2(25)EZ and Later
Contents
System Requirements
Hardware Supported
Device Manager System Requirements
Hardware Requirements
Software Requirements
Cluster Compatibility
Upgrading the Switch Software
Finding the Software Version and Feature Set
Deciding Which Files to Use
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Installation Notes
New Features
New Hardware Features
Limitations and Restrictions
Cisco IOS Limitations
Configuration
Ethernet
Fallback Bridging
HSRP
IP
IP Telephony
MAC Addressing
Multicasting
Power
QoS
Routing
SPAN and RSPAN
Stacking (Cisco EtherSwitch service module switch stack and Catalyst 3750 switch stack)
Trunking
VLAN
Device Manager Limitations
Important Notes
Switch Stack Notes
Device Manager Notes
Open Caveats
Resolved Caveats
Documentation Updates in Cisco IOS Release 12.2(25)EZ
Updates to the Software Configuration Guides
Supported MIBs
Port Security Updates
IGMP Updates
QoS Updates
Updates to the Command Reference
clear port-security
ip igmp snooping last-member-query interval
show ip igmp snooping
show version
switchport port-security
Related Documentation
Obtaining Documentation
Cisco.com
Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Cisco EtherSwitch Service Modules, Cisco IOS Release 12.2(25)EZ and Later
Revised August 1, 2005
The Cisco IOS Release 12.2(25)EZ and later runs on all Cisco EtherSwitch Service Modules.
The Cisco EtherSwitch service modules and Catalyst 3750 switches support stacking through Cisco StackWise technology.
These release notes include important information about Cisco IOS Release 12.2(25)EZ and Cisco IOS Release 12.2(25)EZ1, and any limitations, restrictions, and caveats that apply to them. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•If your switch is on, use the show version privileged EXEC command. See the "Finding the Software Version and Feature Set" section.
•If you are upgrading to a new release, see the software upgrade filename for the software version. See the "Deciding Which Files to Use" section.
For the complete list of Cisco EtherSwitch service module or Catalyst 3750 switch 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 Cisco EtherSwitch service modules and Catalyst 3750 switches, you must order the advanced IP services image upgrade from Cisco.
This software release is part of a special release of Cisco IOS software. 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)EZ and later is based on Cisco IOS Release 12.2(25)SEB. Open caveats in Cisco IOS Release 12.2(25)SEB also affect Cisco IOS Release 12.2(25)EZ and later.
Contents
This information is in the release notes:
•"System Requirements" section
•"Upgrading the Switch Software" section
•"Installation Notes" section
•"New Features" section
•"Limitations and Restrictions" section
•"Important Notes" section
•"Resolved Caveats" section
•"Open Caveats" section
•"Documentation Updates in Cisco IOS Release 12.2(25)EZ" section
•"Related Documentation" section
•"Related Documentation" section
•"Obtaining Documentation" section
•"Documentation Feedback" section
•"Obtaining Technical Assistance" section
•"Obtaining Additional Publications and Information" section
System Requirements
The system requirements are described in these sections:
•"Hardware Supported" section
•"Device Manager System Requirements" section
•"Cluster Compatibility" section
Hardware Supported
Table 1 lists the hardware supported on Cisco IOS Release 12.2(25)EZ.
Table 1 Cisco EtherSwitch Service Modules Supported Hardware
Cisco EtherSwitch Service Module
|
Description
|
Supported by Minimum Cisco IOS Release
|
NME-16ES-1G-P
|
16 10/100 PoE1 ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide
|
Cisco IOS Release 12.2(25)EZ
|
NME-X-23ES-1G-P
|
23 10/100 PoE ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide
|
Cisco IOS Release 12.2(25)EZ
|
NME-XD-24ES-1S-P
|
24 10/100 PoE ports, 1 SFP2 port, 2 StackWise connector ports, extended double-wide
|
Cisco IOS Release 12.2(25)EZ
|
NME-XD-48ES-2S-P
|
48 10/100 PoE ports, 2 SFP ports, no StackWise connector ports, extended double-wide
|
Cisco IOS Release 12.2(25)EZ
|
SFP modules
|
1000BASE-T, 1000BASE-SX
1000BASE-LX, 1000BASE-ZX, CWDM3 , and 100BASE-FX MMF4
|
Cisco IOS Release 12.2(25)EZ
|
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
•"Hardware Requirements" section
•"Software Requirements" section
Hardware Requirements
Table 2 lists the minimum hardware requirements for running the device manager.
Table 2 Minimum Hardware Requirements
Processor Speed
|
DRAM
|
Number of Colors
|
Resolution
|
Font Size
|
Intel Pentium II1
|
64 MB2
|
256
|
1024 x 768
|
Small
|
Software Requirements
Table 3 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.
Note The device manager does not require a plug-in.
Table 3 Supported Operating Systems and Browsers
Operating System
|
Minimum Service Pack or Patch
|
Microsoft Internet Explorer 1
|
Netscape Navigator
|
Windows 98
|
None
|
5.5 or 6.0
|
7.1
|
Windows NT 4.0
|
Service Pack 6 or later
|
5.5 or 6.0
|
7.1
|
Windows 2000
|
None
|
5.5 or 6.0
|
7.1
|
Windows XP
|
None
|
5.5 or 6.0
|
7.1
|
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•When you create a switch cluster, we recommend configuring the highest-end switch in your cluster as the command switch.
•The standby command switch must be the same type as the command switch. For example, if the command switch is a Cisco EtherSwitch StackWise Service Module or Catalyst 3750 switch, all standby command switches must be Cisco EtherSwitch StackWise Service Modules or Catalyst 3750 switches.
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 Cisco EtherSwitch service module feature guide, and the Catalyst 3750 software configuration guide and command reference.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•"Finding the Software Version and Feature Set" section
•"Deciding Which Files to Use" section
•"Upgrading a Switch by Using the Device Manager or Network Assistant" section
•"Upgrading a Switch by Using the CLI" section
•"Recovering from a Software Failure" section
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
Note For 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.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Cisco IOS Release 12.2(25)EZ refers to the SMI as the IP base image and the EMI as the IP services image.
Table 4 lists the different file-naming conventions for the Cisco IOS Release 12.2(25)EZ and later.
Table 4 Cisco IOS Image File Naming Convention
Cisco IOS 12.2(25)EZ and later
|
c3750-ipbase-mz
|
c3750-ipbasek9-mz
|
c3750-ipservices-mz
|
c3750-ipservicesk9-mz
|
c3750-advipservicesk9-mz
|
Table 5 lists the filenames for this software release.
Note For IPv6 capability on the Cisco EtherSwitch service module and Catalyst 3750 switches, you must order the advanced IP services image upgrade from Cisco.
Table 5 Cisco IOS Software Image Files
Filename
|
Description
|
c3750-ipbase-tar.122-25.EZ.tar
|
Catalyst 3750 IP base image and device manager files.
This image has Layer 2+ and basic Layer 3 routing features.
|
c3750-ipservices-tar.122-25.EZ.tar
|
Catalyst 3750 IP services image and device manager files.
This image has both Layer 2+ and full Layer 3 routing features.
|
c3750-ipbasek9-tar.122-25.EZ.tar
|
Catalyst 3750 IP base cryptographic image and device manager files.
This image has the Kerberos, SSH1 , Layer 2+, and basic Layer 3 routing features.
|
c3750-ipservicesk9-tar.122-25.EZ.tar
|
Catalyst 3750 IP services cryptographic image and device manager files.
This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features.
|
c3750-advipservicesk9-tar.122-25.EZ1.tar
|
Catalyst 3750 advanced IP services image, cryptographic file, and device manager files.
This image has all the IP services image (formerly known as the EMI) features and the capability for unicast routing of IPv6 packets.
|
Upgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager. 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.
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
To download software, follow these steps:
Step 1 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 2970 switch, click Catalyst 2970 software. To obtain authorization and to download the cryptographic software files, click Catalyst 2970 3DES Cryptographic Software.
To download the IP services image (formerly known as the EMI) or IP base image (formerly known as the SMI) files for a Catalyst 3560 switch, click Catalyst 3560 software. To obtain authorization and to download the cryptographic software files, click Catalyst 3560 3DES Cryptographic Software.
To download the IP services image (formerly known as the EMI) or IP base image (formerly known as the SMI) files for a Catalyst 3750 switch, click Catalyst 3750 software. To obtain authorization and to download the cryptographic software files, click Catalyst 3750 3DES Cryptographic Software.
Caution If you are upgrading a Catalyst 3750 or a Catalyst 2970 switch that is running a release earlier than Cisco IOS Release 12.1(19)EA1c, this release includes a bootloader upgrade. The bootloader can take up
to 1 minute to upgrade the first time that the new software is loaded. Do not power cycle the switch during the bootloader upgrade.
Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.
For more information, refer to 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:
Switch# ping tftp-server-address
For more information about assigning an IP address and default gateway to the switch, refer to 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:
Switch# archive download-sw /overwrite /reload
tftp:[[//location]/directory]/image-name.tar
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:
Switch# archive download-sw /overwrite
tftp://198.30.20.19/c3750-ipservices-tar.122-25.SEB.tar
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.
Recovering from a Software Failure
For recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•The Express Setup program, as described in the switch getting started guide.
•The CLI-based setup program, as described in the switch hardware installation guide.
•The DHCP-based autoconfiguration, as described in the switch software configuration guide.
•Manually assigning an IP address, as described in the switch software configuration guide.
New Features
These sections describe the new supported hardware and the new software features provided in this release:
•"New Hardware Features" section
New Hardware Features
For a list of all supported hardware, see the "Hardware Supported" section.
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
This section contains these limitations:
•"Cisco IOS Limitations" section
•"Device Manager Limitations" section
Cisco IOS Limitations
These limitations apply to the Cisco EtherSwitch service modules or Catalyst 3750 switches:
•"Configuration" section
•"Ethernet" section
•"Fallback Bridging" section
•"HSRP" section
•"IP" section
•"IP Telephony" section
•"MAC Addressing" section
•"Multicasting" section
•"QoS" section
•"Routing" section
•"SPAN and RSPAN" section
•"Stacking (Cisco EtherSwitch service module switch stack and Catalyst 3750 switch stack)" section
•"Trunking" section
•"VLAN" section
Configuration
These are the configuration limitations:
•A static IP address might be removed when the previously acquired DHCP IP address lease expires.
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)
•When you change a port from a nonrouted port to a routed port or the reverse, the applied auto-QoS setting is not changed or updated when you verify it by using the show running interface or show mls qos interface user EXEC commands. These are the workarounds:
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)
•The DHCP snooping binding database is not written to flash memory or a remote file in any of these situations:
–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.
–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.
–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)
•When dynamic ARP inspection is enabled on a switch or switch stack, ARP and RARP packets greater than 2016 bytes are dropped by the switch or switch stack. This is a hardware limitation.
However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)
•When connected to some third-party devices that send early preambles, a switch port operating at 100 Mbps full duplex or 100 Mbps half duplex might bounce the line protocol up and down. The problem is observed only when the switch is receiving frames.
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)
•Dynamic ARP inspection log entries might be lost after a switch failure. Any log entries that are still in the log buffer (have not been output as a system message) on a switch that fails are lost.
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)
•When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered on that interface, MAC addresses are incorrectly forwarded when they should be blocked
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•A traceback error occurs if a crypto key is generated after an SSL client session.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•(Cisco EtherSwitch service modules) Console baud rate changes in switch IOS are not allowed. The console on the Cisco Etherswitch Service module only supports three baud rates (9600 bps, 19200 bps and 38400 bps) and must be set at the bootloader prompt. Changing baud rates in the switch IOS is not allowed and the command will be rejected.
To change the baud rate, reload the Cisco Etherswitch Service module to the bootloader prompt. Then, change the baud rate and change the speed on the TTY line of the router connecting to the Cisco Etherswitch Service module console.
There is no workaround. (CSCeh50152)
•(Cisco EtherSwitch service modules) The bootloader defaults to read-only mode after the password recovery is performed. When password recovery procedure is completed, the bootloader changes into read only mode. After this, anything configured at the bootloader prompt will be lost when the switch is reset.
The workaround is after password recovery is completed, at the Cisco Etherswitch Service module, prompt, configure it to read-write mode with set_bs bs: rw before setting any variable and then enter set_param to write the changes before resetting the Cisco Etherswitch Service module. (CSCeh45594)
Ethernet
These are the Ethernet limitations:
•Subnetwork Access Protocol (SNAP) encapsulated IP packets are dropped without an error message being reported at the interface. The switch does not support SNAP-encapsulated IP packets. There is no workaround. (CSCdz89142)
•Link connectivity might be lost between some older models of the Intel Pro1000 NIC and the 10/100/1000 switch port interfaces. The loss of connectivity occurs between the NIC and Cisco EtherSwitch service module Gigabit Ethernet ports.
These are the workarounds:
–Contact the NIC vendor, and obtain 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
•(Cisco EtherSwitch service modules) When the Cisco EtherSwitch service module is reloaded or the internal link is reset, depending on the configuration, there can be up to a 45-second delay in providing power to PoE devices. If the internal Gigabit Ethernet interface on the Cisco EtherSwitch service module connected to the router is configured as a switchport (access or trunk mode), the internal link will not be operational until it reaches the STP forwarding state. Therefore, the PoE that has to come from the host router will also not be available until the internal Gigabit Ethernet link reaches the STP forwarding state. This is due to due to STP convergence time. This problem does not occur on routed ports.
The workaround is when the Cisco EtherSwitch service module is in access mode, configure spanning-tree portfast on the internal Gigabit Ethernet interface. If it is in trunk mode, there is no workaround.
Fallback Bridging
These are the fallback bridging limitations:
•If a bridge group contains a VLAN to which a static MAC address is configured, all non-IP traffic in the bridge group with this MAC address destination is sent to all ports in the bridge group. The workaround is to remove the VLAN from the bridge group or to remove the static MAC address from the VLAN. (CSCdw81955)
•Known unicast (secured) addresses are flooded within a bridge group if secure addresses are learned or configured on a port and the VLAN on this port is part of a bridge group. Non-IP traffic destined to the secure addresses is flooded within the bridge group. The workaround is to disable fallback bridging or to disable port security on all ports in all VLANs participating in fallback bridging. To remove an interface from a bridge group and to remove the bridge group, use the no bridge-group bridge-group interface configuration command. To disable port security on all ports in all VLANs participating in fallback bridging, use the no switchport port-security interface configuration command. (CSCdz80499)
HSRP
This is the Hot Standby Routing Protocol (HSRP) limitation:
When the active switch fails in a switch cluster that uses HSRP redundancy, the new active switch might not contain a full cluster member list. The workaround is to ensure that the ports on the standby cluster members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking state, see the "Configuring STP" chapter in the software configuration guide. (CSCec76893)
IP
These are the IP limitations:
•The switch does not create an adjacent table entry when the ARP timeout value is 15 seconds and the ARP request times out. The workaround is to not set an ARP timeout value lower than 120 seconds. (CSCea21674)
•When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console. The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)
IP Telephony
These are the IP telephony limitations:
•Some access point (AP)-350 devices are incorrectly discovered as IEEE 802.3af Class 1 devices. These APs should be discovered as Cisco pre-standard devices. The show power inline user EXEC command shows the AP-350 as an IEEE Class 1 device. The workaround is to power the AP by using an AC wall adaptor. (CSCin69533)
•When a Cisco IP Phone is connected to the switch, the port VLAN ID (PVID) and the voice VLAN ID (VVID) both learn its MAC address. However, after dynamic MAC addresses are deleted, only the VVID relearns the phone MAC address. MAC addresses are manually or automatically deleted when a topology change occurs or when port security or an IEEE 802.1x feature is enabled or disabled. There is no workaround. (CSCea80105)
•After you change the access VLAN on a port that has IEEE 802.1x enabled, the IP Phone address is removed. Because learning is restricted on IEEE 802.1x capable ports, it takes approximately 30 seconds before the address is relearned. No workaround is necessary. (CSCea85312)
•The switch uses the IEEE classification to learn the maximum power consumption of a powered device before powering it. The switch grants power only when the maximum wattage configured on the port is less than or equal to the IEEE class maximum. This ensures that the switch power budget is not oversubscribed. There is no such mechanism in Cisco prestandard powered devices.
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)
MAC Addressing
This is the MAC addressing limitation:
When a MAC address is configured for filtering on the internal VLAN of a routed port, incoming packets from the MAC address to the routed port are not dropped. (CSCeb67937)
Multicasting
These are the multicasting limitations:
•The switch does not support tunnel interfaces for unicast routed traffic. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing.
•Nonreverse-path forwarded (RPF) IP multicast traffic to a group that is bridged in a VLAN is leaked onto a trunk port in the VLAN even if the port is not a member of the group in the VLAN, but it is a member of the group in another VLAN. Because unnecessary traffic is sent on the trunk port, it reduces the bandwidth of the port. There is no workaround for this problem because non-RPF traffic is continuous in certain topologies. As long as the trunk port is a member of the group in at least one VLAN, this problem occurs for the non-RPF traffic. (CSCdu25219)
•If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more than the maximum number specified by the show sdm prefer global configuration command, the traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp snooping multicast-table privileged EXEC command output shows otherwise. The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)
•IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port. There is no workaround. (CSCdy82818)
•When you use the ip access-group interface configuration command with a router access control list (ACL) to deny access to a group in a VLAN, multicast data to the group that is received in the VLAN is always flooded in the VLAN, regardless of IGMP group membership in the VLAN. This provides reachability to directly connected clients, if any, in the VLAN. The workaround is to not apply a router ACL set to deny access to a VLAN interface. Apply the security through other means; for example, apply VLAN maps to the VLAN instead of using a router ACL for the group. (CSCdz86110)
•If the stack master is power cycled immediately after you enter the ip mroute global configuration command, there is a slight chance that this configuration change might be lost after the stack master changes. This occurs because the stack master did not have time to propagate the running configuration to all the stack members before it was powered down. This problem might also affect other configuration commands. There is no workaround. (CSCea71255)
•When you enable IP Protocol-Independent Multicast (PIM) on a tunnel interface, the switch incorrectly displays the Multicast is not supported on tunnel interfaces error message. IP PIM is not supported on tunnel interfaces. There is no workaround. (CSCeb75366)
•If an IG MP report packet has two multicast group records, the switch removes or adds interfaces depending on the order of the records in the packet:
–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)
•When IGMP snooping is disabled and you enter the switchport block multicast interface configuration command, IP multicast traffic is not blocked.
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•Incomplete multicast traffic can be seen under either of these conditions:
–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)
Power
•When used power is displayed on the Cisco EtherSwitch service module by issuing the show power inline command, total used power is displayed by all Cisco EtherSwitch service modules in the router. Any remaining power shown is the remaining power available for allocation to switching ports on all Cisco EtherSwitch service modules in the router. When the total power just used, by particular EtherSwitch service module, is displayed on an EtherSwitch Service module interface by entering the show power inline command on the router, the following is displayed:
PowerSupply SlotNum. Maximum Allocated Status
----------- -------- ------- --------- ------
INT-PS 0 360.000 121.000 PS1 GOOD PS2 ABSENT
Interface Config Device Powered PowerAllocated
--------- ------ ------ ------- --------------
Gi4/0 auto Unknown On 121.000 Watts
This is not a problem. It is the correct method used to show the total used power and the remaining power available on the system. (CSCeg74337)
QoS
These are the quality of service (QoS) limitations:
•Some switch queues are disabled if the buffer size or threshold level is set too low with the mls qos queue-set output global configuration command. The ratio of buffer size to threshold level should be greater than 10 to avoid disabling the queue. The workaround is to choose compatible buffer sizes and threshold levels. (CSCea76893)
•When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses shaped round robin (SRR) as the queuing mechanism. The auto-QoS feature is designed on each platform based on the feature set and hardware limitations, and the queuing mechanism supported on each platform might be different. There is no workaround. (CSCee22591)
Routing
These are the routing limitations:
•The switch does not support tunnel interfaces for unicast routed traffic. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing.
•A route map that has an ACL with a Differentiated Services Code Point (DSCP) clause cannot be applied to a Layer 3 interface. The switch rejects this configuration and displays a message that the route map is unsupported. There is no workaround. (CSCea52915)
•On a Cisco EtherSwitch service module switch stack or Catalyst 3750 switch stack with a large number of switched virtual interfaces (SVIs), routes, or both on a fully populated nine-member switch stack, this message might appear when you reload the switch stack or add a switch to the stack:
%SYS-2-MALLOCFAIL: Memory allocation of 4252 bytes failed from 0x179C80, alignment 0
Pool: I/O Free: 77124 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
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)
•A spanning-tree loop might occur if all of these conditions are true:
–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)
SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•An egress SPAN copy of routed unicast traffic might show an incorrect destination MAC address on both local and remote SPAN sessions. This limitation does not apply to bridged packets. The workaround for local SPAN is to use the replicate option. For a remote SPAN session, there is no workaround (CSCdy72835).
•Egress SPAN routed packets (both unicast and multicast) show the incorrect source MAC address. For remote SPAN packets, the source MAC address should be the MAC address of the egress VLAN, but instead the packet shows the MAC address of the RSPAN VLAN. For local SPAN packets with native encapsulation on the destination port, the packet shows the MAC address of VLAN 1. This problem does not appear with local SPAN when the encapsulation replicate option is used. This limitation does not apply to bridged packets. The workaround is to use the encapsulate replicate keywords in the monitor session global configuration command. Otherwise, there is no workaround (CSCdy81521).
•During periods of very high traffic, when two RSPAN source sessions are configured, the VLAN ID of packets in one RSPAN session might overwrite the VLAN ID of the other RSPAN session. If this occurs, packets intended for one RSPAN VLAN are incorrectly sent to the other RSPAN VLAN. This problem does not affect RSPAN destination sessions. The workaround is to configure only one RSPAN source session (CSCea72326).
•(Cisco EtherSwitch service modules or Catalyst 3750 switches) The egress SPAN data rate might degrade when fallback bridging or multicast routing is enabled. The amount of degradation depends on the processor loading. Typically, the switch can egress SPAN at up to 40,000 packets per second (64-byte packets). As long as the total traffic being monitored is below this limit, there is no degradation. However, if the traffic being monitored exceeds the limit, only a portion of the source stream is spanned. When this occurs, the following console message appears: 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)
•On Cisco EtherSwitch service modules or Catalyst 3750 switches, some IGMP report and query packets with IP options might not be ingress-spanned. Packets that are susceptible to this problem are IGMP packets containing 4 bytes of IP options (IP header length of 24). An example of such packets would be IGMP reports and queries having the router alert IP option. Ingress-spanning of such packets is not accurate and can vary with the traffic rate. Typically, very few or none of these packets are spanned. There is no workaround. (CSCeb23352)
•Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local SPAN session. The workaround is to use the monitor session session_number destination {interface interface-id encapsulation replicate} global configuration command for local SPAN. (CSCed24036)
Stacking (Cisco EtherSwitch service module switch stack and Catalyst 3750 switch stack)
These are the Cisco EtherSwitch service module switch stack or Catalyst 3750 switch stack limitations:
•If the stack master is immediately reloaded after adding multiple VLANs, the new stack master might fail. The workaround is to wait a few minutes after adding VLANs before reloading the stack master. (CSCea26207)
•If the console speed is changed on a stack, the configuration file is updated, but the baud rate is not. When the switch is reloaded, meaningless characters might appear on the console during bootup before the configuration file is parsed and the console speed is set to the correct value. If manual boot is enabled or the startup configuration is deleted after you change the console speed, you cannot access the console after the switch reboots. There is no workaround. (CSCec36644)
•If a switch is forwarding traffic from a Gigabit ingress interface to a 100 Mbps egress interface, the ingress interface might drop more packets due to oversubscription if the egress interface is on a Fast Ethernet switch. There is no workaround. (CSCed00328)
•If a stack member is removed from a stack and either the configuration is not saved or another switch is added to the stack at the same time, the configuration of the first member switch might be lost. The workaround is to save the stack configuration before removing or replacing any switch in the stack. (CSCed15939)
•When the switchport and no switchport interface configuration commands are entered more than 20,000 times on a port of a Cisco EtherSwitch service module or Catalyst 3750 switch, all available memory is used, and the switch halts.
There is no workaround. (CSCed54150)
•In a private-VLAN domain, only the default private-VLAN IP gateways have sticky ARP enabled. The intermediate Layer 2 switches that have private VLAN enabled disable sticky ARP. When a stack master switch-over occurs on one of the Cisco EtherSwitch service modules or Catalyst 3750 default IP gateways, the message 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 switch-over cannot complete.
The workaround is to complete the MAC address update by entering the clear arp privileged EXEC command. (CSCed62409)
•When a Cisco EtherSwitch service module or Catalyst 3750 switch is being reloaded in a switch stack, packet loss might occur for up to 1 minute while the Cisco Express Forwarding (CEF) table is downloaded to the switch. This only impacts traffic that will be routed through the switch that is being reloaded. There is no workaround. (CSCed70894)
•Inconsistent private-VLAN configuration can occur on a switch stack if a new stack master is running the IP base image and the old stack master was running the IP services image.
Private VLAN is enabled or disabled on a switch stack, depending on whether or not the stack master is running the IP services image or the IP base image:
–If the stack master is running the IP services image, all stack members have private VLAN enabled.
–If the stack master is running the IP base image, 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 and the new stack master is running the IP base image. 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 to IP base image master switch change (or the reverse).
–Before an IP services image-to-IP base image master switch change, delete the private-VLAN configuration from the existing stack master. (CSCee06802)
•Port configuration information is lost when changing from switchport to no switchport modes on Catalyst 3750 switches.
This is the expected behavior of the offline configuration (provisioning) feature. There is no workaround. (CSCee12431)
Trunking
These are the trunking limitations:
•The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link [ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber. This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame to an IEEE 802.1Q trunk interface. There is no workaround. (CSCdz33708)
•IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no workaround. (CSCdz42909).
•If a Catalyst 3750 switch stack is connected to a designated bridge and the root port of the switch stack is on a different switch than the alternate root port, changing the port priority of the designated ports on the designated bridge has no effect on the root port selection for the Catalyst 3750 switch stack. There is no workaround. (CSCea40988)
•For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics. There is no workaround. (CSCec35100).
VLAN
These are the VLAN limitations:
•If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, the switch can fail.
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•A CPUHOG message sometimes appears when you configure a private VLAN. Enable port security on one or more of the ports affected by the private VLAN configuration.
There is no workaround. (CSCed71422)
•When you apply a per-VLAN quality of service (QoS), per-port policer policy-map to a VLAN Switched Virtual Interface (SVI), the second-level (child) policy-map in use cannot be re-used by another policy-map.
The workaround is to define another policy-map name for the second-level policy-map with the same configuration to be used for another policy-map. (CSCef47377)
Device Manager Limitations
When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not launch.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Important Notes
These sections describe the important notes related to this software release for the Cisco EtherSwitch service modules or Catalyst 3750 switches:
•"Switch Stack Notes" section
•"Device Manager Notes" section
Switch Stack Notes
These notes apply to switch stacks:
•Always power off a switch before adding or removing it from a switch stack.
•Catalyst 3750 switches running Cisco IOS Release 12.2(25)SEB are compatible with Cisco EtherSwitch service modules running Cisco IOS Release 12.2(25)EZ. Catalyst 3750 switches and Cisco EtherSwitch service modules can be in the same switch stack. In this switch stack, the Catalyst 3750 switch or the Cisco EtherSwitch service module can be the stack master.
Device Manager Notes
These notes apply to the device manager:
•You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the CLI or Cisco Network Assistant.
•The Legend on the device manager incorrectly includes the 1000BASE-BX SFP module.
•We recommend this browser setting to speed up the time needed to display the device manager from Microsoft Internet Explorer.
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.
4. Click OK.
5. Click OK to exit the Internet Options window.
•The HT TP server interface must be enabled to display the device manager. By default, the HTTP server is enabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
| |
Command
|
Purpose
|
Step 1
|
configure terminal
|
Enter global configuration mode.
|
Step 2
|
ip http authentication {enable | local | tacacs}
|
Configure the HTTP server interface for the type of authentication that you want to use.
•enable—Enable password, which is the default method of HTTP server user authentication, is used.
•local—Local user database, as defined on the Cisco router or access server, is used.
•tacacs—TACACS server is used.
|
Step 3
|
end
|
Return to privileged EXEC mode.
|
Step 4
|
show running-config
|
Verify your entries.
|
•The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.
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:
| |
Command
|
Purpose
|
Step 1
|
configure terminal
|
Enter global configuration mode.
|
Step 2
|
ip http authentication {enable | local | tacacs}
|
Configure the HTTP server interface for the type of authentication that you want to use.
•enable—Enable password, which is the default method of HTTP server user authentication, is used.
•local—Local user database, as defined on the Cisco router or access server, is used.
•tacacs—TACACS server is used.
|
Step 3
|
end
|
Return to privileged EXEC mode.
|
Step 4
|
show running-config
|
Verify your entries.
|
•If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the address (for example, www.cisco.com:84), you must enter http:// as the URL prefix. Otherwise, you cannot launch the device manager.
Open Caveats
This section describes the open caveats with possible unexpected activity in this software release. Unless otherwise noted, these severity 3 Cisco IOS configuration caveats apply to the Cisco EtherSwitch service modules or Catalyst 3750 switches:
•CSCee71979 (Cisco EtherSwitch service modules)
Non-PoE devices attached to a network are erroneously detected as IEEE PD occasionally and powered by the Cisco Etherswitch service module.
There is no workaround, It is recommended to configure power inline never on the Cisco Etherswitch service module ports that do not have PoE device connected.
•CSCee96492 (Cisco EtherSwitch service modules)
When booting up, some non-harmful messages related to stacking may display although the Cisco Etherswitch service module is not capable of stacking.
There is no workaround.
•CSCef37624
You cannot ping a Layer 3 interface that has a Network Address Translation (NAT) configuration.
There is no workaround.
Problem:
•CSCef84975 (Cisco EtherSwitch service modules)
Phone detect events, generated by many IEEE phones connected to switch ports, can consume a significant amount of CPU time. However, the switch ports cannot power the phones because the internal link is down.
The workaround is, if the problem persists, to enter the power inline never command on all the FE ports that are not powered but connected to IP phones,
•CSCef94884
Disabling OSPFv3 causes a memory leak.
There is no workaround.
•CSCeg27382
If the per-VLAN QoS per-port policer policy-map is already attached to a VLAN switched virtual interface (SVI), do not modify the second level (port-level) policy-map. If you modify the policy-map by removing the policer while it is still attached, an error message appears, and the policy-map is detached by the switch. The policer cannot be re-applied back to that policy-map.
The workaround is to redefine the second-level (port level) policy map if the policy map has already been detached by the system.
•CSCeg53353 (Cisco EtherSwitch service modules)
Static power allocation on an Etherswitch Service module port is not supported in this release.
There is no workaround.
•CSCeg56931 (Cisco EtherSwitch service modules)
The Etherswitch service module randomly does not power some ports during a power cycle. This issue will be resolved in IOS software release 12.3(14)T1 and later versions.
•CSCeh01250 (Cisco EtherSwitch service modules)
When connected to the router through an auxiliary port in a session to the Cisco EtherSwitch service module, by entering the shut/no shut command on the service module router interface, the service module session will fail.
The workaround is to reload the router or connect to router through the console and open a session to the service module.
•CSCeh15112
When IEEE 802.1x is enabled on one or more ports of a member switch and you enter the show dot1x all privileged EXEC command, the command output does not have IEEE 802.1x information about ports on the member switches.
The workaround is to use the show dot1x interface privileged EXEC command to display the information for a specific interface.
•CSCeh16869
In an multiple spanning-tree (MST) region in which Switch 1 is connected to Switch 2 and
Switch 2 is connected to Switch 3, if Switch 2 has a root port and a designated port in MST
instance 2, the root port flaps. The designated port is not synchronized with the other switches in the MST region, and the convergence of the port from the blocking state to the learning state is slow.
The workaround is to modify the switch priority to a lower value so that the Switch 2 becomes the root switch for the MST instances 0 and 2.
•CSCeh19672
If an IEEE 802.1x client configured for both machine and user authentication is connected to a Cisco EtherSwitch service module or Catalyst 3750 switch running Cisco IOS Release 12.2(25)SE and RADIUS VLAN assignment is used only for the machine authentication, the user might take 2 to 5 minutes to authenticate.
Use one of these workarounds:
–Use the same VLAN for machine and user authentication.
–If the same VLAN cannot be used, reduce the quiet period by using the dot1x timeout quiet-period seconds interface configuration command.
•CSCeh35595 (Cisco EtherSwitch service module)
A duplex mismatch occurs when two FE interfaces, connected back to back on two EtherSwitch service modules, are configured as 100/full and auto/auto. This is expected behavior for the PHY on the Cisco Etherswitch service module.
There is no workaround.
•CSCeh35693 (Cisco EtherSwitch service modules)
If two Cisco EtherSwitch service modules are connected back to back via FE interfaces configured as 100/full and auto/auto, one FE may detect the FE other as Cisco PD.
There is no workaround.
•CSCeh45465 (Cisco EtherSwitch service modules)
Entering the shut/no shut command on the internal link can disrupt the PoE operation. If a new IP phone is added while the internal link is in shutdown state, the IP phone will not get inline power if the internal link is brought up within 5 minutes.
The workaround is to issue the shut/no shut command on the FE interface of a new IP phone is attached to after the internal link is brought up once again.
•CSCeh46718 (Cisco EtherSwitch service modules)
SFP-100FX modules do not work on a 48-port Cisco EtherSwitch service module.
There is no workaround.
•CSCeh52964 (Cisco EtherSwitch service modules)
Sometimes when the router is rebooted after power on (approximately once in 10 to 15 reboots), the Router Blade Communication Protocol (RBCP) between the router and the EtherSwitch service module may not be reestablished. In this situation, the following error message is displayed:
[date]: %Y88E8K-3-ILP_MSG_TIMEOUT_ERROR: GigabitEthernet1/0: EtherSwitch Service
Module RBCP ILP messages timeout
The workaround is to reload the EtherSwitch service module software without rebooting the router. The switching software may be reloaded by using the reload command at the EtherSwitch service module prompt or running the service-module g <slot#>/0 reset command at the router prompt.
