Cisco IOS Release 12.2(40)EX1 and later runs on the Cisco Catalyst Blade Switch 3120 for HP switches. For the WS-CBS3125G-S and WS-CBS3125X-S switch models, you need to install Cisco IOS Release 12.2(40)EX3 or later.

Note on WS-CBS3125G-S and WS-CBS3125X-S switch models:

•The WS-CBS3125G-S is the same product as the WS-CBS3120G-S.

•The WS-CBS3125X-S is the same product as the WS-CBS3120X-S.

The functionality and the performance of WS-CBS3125 switches are same as those of WS-CBS3120 switches. All Cisco Catalyst Blade Switch 3120/3125 for HP models are HP BladeSystem c-Class compatible.

All switch models support stacking through Cisco StackWise Plus technology. 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(40)EX1 and later and any limitations, restrictions, and caveats that apply to it. 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.

This software release is part of a special release of Cisco IOS software that is not released on the same 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.

Caution The Cisco Catalyst Blade Switch 3120 for HP switches do not support switch stacks with other types of blades switches as members. Combining the Cisco Catalyst Blade Switch 3120 for HP with other types of blade switches in a switch stack might cause the switch to work improperly or to fail.

Device Manager System Requirements

These sections describe the hardware and software requirements for using the device manager:

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.

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 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 feature set or IP services feature set) and does not change if you upgrade the software license.

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.

Note To use the IPv6 routing and IPv6 ACL features on the Cisco Catalyst Blade Switch 3120 for HP, you must purchase the advanced IP services software license from Cisco.

Table 4 Cisco IOS Software Image Files

Filename

Description

cbs31x0-universal-tar.122-40.EX3.tar

Cisco Catalyst Blade Switch 3120 for HP universal image and device manager files. This image has the supported features that are enabled by the installed software license.

cbs31x0-universalk9-tar.122-40.EX3.tar

Cisco Catalyst Blade Switch 3120 for HP universal cryptographic image and device manager files. This image has the Kerberos, SSH, SSL, and SNMPv3 in addition to the features supported in the universal image.

The universal software images support multiple feature sets. Use the software activation feature to deploy a software license and to enable a specific feature set. For information about software activation, see the Cisco Software Activation for HP document on Cisco.com:

Archiving Software Images

Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release from 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:

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:

Upgrading a Switch by Using the Device Manager or Network Assistant

You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.

Note 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.

Step 3 Copy the image to the appropriate TFTP directory on your PC, 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 thisprivileged EXEC command:

Switch# pingtftp-server-address

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:

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.

Access Control List

These are the access control list (ACL) limitations:

•The Cisco Catalyst 3120 for HP Blade Switch has 964 TCAM entries available for ACLs in the default and routing SDM templates instead of the 1024 entries that are available on the Catalyst 3560 and Catalyst 3750 switches.

There is no workaround. (CSCse33114)

•When a MAC access list is used to block packets from a specific source MAC address, that MAC address is entered in the switch MAC-address table.

The workaround is to block traffic from the specific MAC address by using the mac address-table staticmac-addrvlanvlan-iddrop global configuration command. (CSCse73823)

Address Resolution Protocol

This is an Address Resolution Protocol limitation:

•The switch might place a port in an error-disabled state due to an Address Resolution Protocol (ARP) rate limit exception even when the ARP traffic on the port is not exceeding the configured limit. This could happen when the burst interval setting is 1 second, the default.

The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem. (CSCse06827))

Cisco X2 Transceiver Modules and SFP Modules

These are the Cisco X2 transceiver module and SFP module limitations:

•Cisco X2-10GB-LR transceiver modules with a version identification number lower than V03 might show intermittent frame check sequence (FCS) errors or be ejected from the switch during periods of operational shock greater than 50 g. There is no workaround. (CSCse14048)

•Cisco X2-10GB-CX4 transceiver modules with a version identification number lower than V03 might be difficult to insert because of a dimensional tolerance discrepancy. The workaround is to use modules with a version identification number of V03 or later. (CSCsg28558)

•Switches with the Cisco X2-10GB-LX4 transceiver modules with a version identification number before V03 might intermittently fail. The workaround is to use Cisco X2-10GB-LX4 transceiver modules with a version identification number of V03 or later. (CSCsh60076)

•Cisco GLC-GE-100FX SFP modules with a serial number between OPC0926xxxx and OPC0945xxxx might show intermittent module not valid, data, status, link-flapping, and FCS errors. The workaround is to use modules with serial numbers that are not in the specified range. (CSCsh59585)

•When switches are installed closely together and the uplink ports of adjacent switches are in use, you might have problems accessing the SFP module bale-clasp latch to remove the SFP module or the SFP cable (Ethernet or fiber). Use one of these workarounds:

–Allow space between the switches when installing them.

–In a switch stack, plan the SFP module and cable installation so that uplinks in adjacent stack members are not all in use.

–Use a long, small screwdriver to access the latch, and then remove the SFP module and cable. (CSCsd57938)

•When a Cisco X2-10GB-CX4 transceiver module is in the X2 transceiver module port and you enter the show controllers ethernet-controller tengigabitethernet privileged EXEC command, the command displays some fields as unspecified. This is the expected behavior based on IEEE 802.3ae. (CSCsd47344)

•The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module. The workaround is to configure aggressive UDLD. (CSCsh70244).

Configuration

These are the configuration limitations:

•When an excessive number (more than 100 packets per second) of Address Resolution Protocol (ARP) packets are sent to a Network Admission Control (NAC) Layer 2 IP-configured member port, a switch might display a message similar to this:

No workaround is necessary. Under normal conditions, the switch generates this notification when snooping the next ARP packet. (CSCse47548)

•When there is a VLAN with protected ports configured in fallback bridge group, packets might not be forwarded between the protected ports.

The workaround is to not configure VLANs with protected ports as part of a fallback bridge group. (CSCsg40322)

When a switch port configuration is set at 10 Mb/s half duplex, sometimes the port does not send in one direction until the port traffic is stopped and then restarted. You can detect the condition by using the show controller ethernet-controller or the show interfaces privileged EXEC commands.

The workaround is to stop the traffic in the direction in which it is not being forwarded, and then restart it after 2 seconds. You can also use the shutdown interface configuration command followed by the no shutdown command on the interface. (CSCsh04301)

•When line rate traffic is passing through a dynamic port, and you enter the switchport access vlan dynamic interface configuration command for a range of ports, the VLANs might not be assigned correctly. One or more VLANs with a null ID appears in the MAC address table instead.

The workaround is to enter the switchport access vlan dynamic interface configurationcommand separately on each port.(CSCsi26392)

EtherChannel

These are the EtherChannel limitations:

•In an EtherChannel running Link Aggregation Control Protocol (LACP), the ports might be put in the suspended or error-disabled state after a stack partitions or a member switch reloads. This occurs when

–The EtherChannel is a cross-stack EtherChannel with a switch stack at one or both ends.

–The switch stack partitions because a member reloads. The EtherChannel is divided between the two partitioned stacks, each with a stack master.

The EtherChannel ports are put in the suspended state because each partitioned stack sends LACP packets with different LACP Link Aggregation IDs (the system IDs are different). The ports that receive the packets detect the incompatibility and shut down some of the ports. Use one of these workarounds for ports in this error-disabled state:

–Enable the switch to recover from the error-disabled state.

–Enter the shutdown and the noshutdown interface configuration commands to enable the port.

The EtherChannel ports are put in the error-disabled state because the switches in the partitioned stacks send STP BPDUs. The switch or stack at the other end of the EtherChannel receiving the multiple BPDUs with different source MAC addresses detects an EtherChannel misconfiguration.

After the partitioned stacks merge, ports in the suspended state should automatically recover. (CSCse33842)

•When a switch stack is configured with a cross-stack EtherChannel, it might transmit duplicate packets across the EtherChannel when a physical port in the EtherChannel has a link-up or link-down event. This can occur for a few milliseconds while the switch stack adjusts the EtherChannel for the new set of active physical ports and can happen when the cross-stack EtherChannel is configured with either mode ON or LACP. This problem might not occur with all link-up or link-down events.

No workaround is necessary. The problem corrects itself after the link-up or link-down event. (CSCse75508)

IEEE 802.1x Authentication

These are the IEEE 802.1x authentication limitations:

•If a supplicant using a Marvel Yukon network interface card (NIC) is connected to an IEEE 802.1x-authorized port in multihost mode, the extra MAC address of 0c00.0000.0000 appears in the MAC address table.

Use one of these workarounds (CSCsd90495):

–Configure the port for single-host mode to prevent the extra MAC address from appearing in the MAC address table.

–Replace the NIC with a new card.

•When MAC authentication bypass is configured to use Extensible Authentication Protocol (EAP) for authorization and critical authentication is configured to assign a critical port to an access VLAN:

–If the connected device is supposed to be unauthorized, the connected device might be authorized on the VLAN that is assigned to the critical port instead of to a guest VLAN.

–If the device is supposed to be authorized, it is authorized on the VLAN that is assigned to the critical port.

Use one of these workarounds (CSCse04534):

–Configure MAC authentication bypass to not use EAP.

–Define your network access profiles to not use MAC authentication bypass. For more information, see the Cisco Access Control Server (ACS) documentation.

•When IEEE 802.1x authentication with VLAN assignment is enabled, a CPUHOG message might appear if the switch is authenticating supplicants in a switch stack.

The workaround is not use the VLAN assignment option. (CSCse22791)

Multicasting

These are the multicasting limitations:

•Multicast packets with a time-to-live (TTL) value of 0 or 1 are flooded in the incoming VLAN when all of these conditions are met:

–Multicast routing is enabled in the VLAN.

–The source IP address of the packet belongs to the directly connected network.

–The TTL value is either 0 or 1.

The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)

•Multicast packets denied by the multicast boundary access list are flooded in the incoming VLAN when all of these conditions are met:

The workaround is to not send RPF-failed multicast traffic, or make sure that the source IP address of the RPF-failed packet is reachable. (CSCsd28944)

•If the clear ip mroute privileged EXEC command is used when multicast packets are present, it might cause temporary flooding of incoming multicast traffic in the VLAN.

There is no workaround. (CSCsd45753)

•When you configure the ip igmp max-groupsnumber and ip igmp max-groups action replace interface configuration commands and the number of reports exceed the configured max-groups value, the number of groups might temporarily exceed the configured max-groups value. No workaround is necessary because the problem corrects itself when the rate or number of IGMP reports are reduced. (CSCse27757)

•When you configure the IGMP snooping throttle limit by using the ip igmp max-groups number interface configuration on a port-channel interface, the groups learned on the port-channel might exceed the configured throttle limit number when all of these conditions are true:

–The port-channel is configured with member ports across different switches in the stack.

–One of the member switches reloads.

–The member switch that is reloading has a high rate of IP IGMP joins arriving on the port-channel member port.

The workaround is to disable the IGMP snooping throttle limit by using the no ip igmp max-groups number interface configuration command and then to reconfigure the same limit again. (CSCse39909)

QoS

These are the quality of service (QoS) limitations:

•When QoS is enabled and the egress port receives pause frames at the line rate, the port cannot send packets.

There is no workaround. (CSCeh18677)

•Egress shaped round robin (SRR) sharing weights do not work properly with system jumbo MTU frames.

There is no workaround. (CSCsc63334)

•In a hierarchical policy map, if the VLAN-level policy map is attached to a VLAN interface and the name of the interface-level policy map is the same as that for another VLAN-level policy map, the switch rejects the configuration, and the VLAN-level policy map is removed from the interface.

The workaround is to use a different name for the interface-level policy map. (CSCsd84001)

•If the ingress queue has low buffer settings and the switch sends multiple data streams of system jumbo MTU frames at the same time at the line rate, the frames are dropped at the ingress.

There is no workaround. (CSCsd72001)

•When you use the srr-queue bandwidth limit interface configuration command to limit port bandwidth, packets that are less than 256 bytes can cause inaccurate port bandwidth readings. The accuracy is improved when the packet size is greater than 512 bytes. There is no workaround. (CSCsg79627)

Routing

These are the routing limitations:

•The switch stack might reload if the switch runs with this configuration for several hours, depleting the switch memory and causing the switch to fail:

–The switch has 400 Open Shortest Path First (OSPF) neighbors.

–The switch has thousands of OSPF routes.

The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)

•When the PBR is enabled and QoS is enabled with DSCP settings, the CPU utilization might be high if traffic is sent to unknown destinations.

The workaround is to not send traffic to unknown destinations. (CSCse97660)

SPAN and RSPAN

These are the SPAN and Remote SPAN (RSPAN) limitations.

•When egress SPAN is running on a 10-Gigabit Ethernet port, only about 12 percent of the egress traffic is monitored.

There is no workaround. This is a hardware limitation. (CSCei10129)

•When the logging event-spanning-tree interface configuration command is configured and logging to the console is enabled, a topology change might generate a large number of logging messages, causing high CPU utilization. CPU utilization can increase with the number of spanning-tree instances and the number of interfaces configured with the logging event-spanning-tree interface configuration command. This condition adversely affects how the switch operates and could cause problems such as STP convergence delay.

High CPU utilization can also occur with other conditions, such as when debug messages are logged at a high rate to the console.

•The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.

The workaround is to configure aggressive UDLD. (CSCsh70244).

VLANs

This is a VLAN limitation:

When the domain is authorized in the guest VLAN on a member switch port without link loss and an Extensible Authentication Protocol over LAN (EAPOL) is sent to an IEEE 802.1x supplicant to authenticate, the authentication fails. This problem happens intermittently with certain stacking configurations and only occurs on the member switches.

The workaround is to enter the shut and no shut interface configuration commands on the port to reset the authentication status. (CSCsf98557)

Stacking

These are the switch stack limitations:

•When using the logging console global configuration command, low-level messages appear on both the stack master and the stack member consoles.

The workaround is to use the logging monitor global configuration command to set the severity level to block the low-level messages on the stack member consoles. (CSCsd79037)

•If a new member switch joins a switch stack within 30 seconds of a command to copy the switch configuration to the running configuration of the stack master, the new member might not get the latest running configuration and might not operate properly.

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)

•When the flash memory of a stack member is almost full, it might take longer to start up than other member switches. This might cause that switch to miss the stack-master election window. As a result, the switch might fail to become the stack master even though it has the highest priority.

The workaround is to delete files in the flash memory to create more free space. (CSCsg30073)

Device Manager Limitations

These are the 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 start.

The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)

•If you launch the device manager from a Firefox web browser, an invalid certificate alert appears. If you launch the device manager from an Internet Explorer 7.0 browser, a certificate error appears.

The workaround when using Firefox is to either temporarily or permanently accept the certificate. If you temporarily accept the certificate, close and then reopen the Firefox browser window. If you permanently accept the certificate, delete the certificate, and then close and restart Firefox:

The workaround when using Internet Explorer is to click Click here for Options in the warning message, and click Display Blocked Content. Close the browser window, and launch a new session. (CSCsk80229)

Important Notes

These sections describe the important notes related to this software release:

If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.

•If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)EX1 or later, when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message:

AutoQoS Error: ciscophone input service policy was not properly applied

policy map AutoQoS-Police-CiscoPhone not configured

If this happens, enter the no auto qos voip cisco-phone interface command on all interfaces with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.

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.

•We recommend this browser setting to reduce 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 HTTP 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.

Configure the HTTP server interface for the type of authentication that you want to use.

•aaa—Enable the authentication, authorization, and accounting feature. You must enter the aaa new-model interface configuration command for the aaa keyword to appear.

•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.

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.

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.

•CSCsg67684

When a cross-stack LACP EtherChannel has a maximum configuration, such as eight active and eight hot-standby ports, and there are multiple rapid sequential master failovers and stack rejoins that cause extreme stress, the port channel might not function as expected. Some ports might not join the EtherChannel, and traffic might be lost. You can detect the condition by using the remote command all show etherchannel summary privileged EXEC command.

There is no workaround. The out-of-sync switches must be reloaded.

•CSCsg77818

When a switch interface is configured with trust boundary and Cisco Discovery Protocol (CDP) or the CDP table is repeatedly disabled, enabled, or cleared, the switch might reload.

The workaround is to avoid repeatedly disabling or clearing the CDP table, or avoid enabling CDP when the trust boundary is configured on an interface. Or, first disable the trust boundary before you disable or clear the CDP table or enable CDP.

•CSCsh12472

The switch might display tracebacks similar to this example when an EtherChannel interface port-channel type changes from Layer 2 to Layer 3 or the reverse:

There is no workaround. This message is only information; switch functionality is not affected.

•CSCsi16162

When you enter an all 0s route with an all 1s mask in the routing table and the next hop is entered as an interface, a traceback message appears.

The workaround is to use an IP address as the next hop instead of an interface.

•CSCsi26444

The error message %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND might appear for a switch stack under these conditions:

–IEEE 802.1 is enabled.

–A supplicant is authenticated on at least one port.

–A new member joins a switch stack.

You can use one of these workarounds:

–Enter the shutdown and the no shutdown interface configuration commands to reset the port.

–Remove and reconfigure the VLAN.

•CSCsi52914

When you are configuring a SPAN session, this message might erroneously appear even when two source sessions are not configured:

% Platform can support a maximum of 2 source sessions

The workaround is to reboot the switch stack.

•CSCsi65551

In certain situations during master switch failover, a VLAN that has been error disabled on a port might be re-enabled after the master switch failover, even though the port has not been configured for automatic recovery.

There is no workaround.

•CSCsi70454

The configuration file used for the configuration replacement feature requires the character string end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the configuration rollback does not work.

These are the workarounds. (You only need to do one of these.)

–Do not use a configuration file that is stored by or edited with Windows Notepad.

–Manually add the character string end\n to the end of the file.

The workaround is to configure routed IPv4 multicast and IPv6 unicast traffic in different switch ports.

•CSCsi84165

If you are running the Cisco IOS cryptographic image (such as cbs31x0-universalk9-mz), you cannot create a secure HTTP session to the switch from the device manager when using a Firefox web browser.

The workaround is to use the Internet Explorer web browser.

•CSCsj10198

When a per-port per-VLAN policy map (a hierarchical VLAN-based policy map) is attached to a VLAN interface, and you remove the child-policy policer from the policy map and then add it back, the policy map fails to re-attach to the same SVI.

The workaround is to delete the child policy, which removes it from the parent policy. Then recreate the child policy (with the same or a different name), and reference it in the parent policy. The parent policy then successfully attaches to the SVI.

•CSCsj77933

If you enter a space before a comma in the define interface-range or the interface range global configuration command, the space before the comma is not saved in the switch configuration.

There is no workaround.

•CSCsl49153

You might receive a traceback message when you use the no interface port-channel global configuration command to delete interfaces from an EtherChannel that has port channels on multiple stack members.

The workaround is to save the configuration and to reload the stack.

•CSCsl63862

When you use the switch renumber global configuration command to renumber a member switch in a switch stack and then reload the switch, the internal server-facing ports do not have the required default of spanning-tree portfast enabled.

The workaround is to apply the switch provision configuration before you reboot the switch. Enter both the switchcurrent-stack-member-numberrenumbernew-stack-member-number and the switchstack-member-numberprovisiontype global configuration commands, and reload the switch.

•CSCso15367

The CLI output for the StackWise Plus port 2 shows the output for the StackWise Plus port 1 and vice versa.

There is no workaround.

•CSCsm77199

If you configured the HTTP secure server on the switch, this error message appears: %DATACORRUPTION-1-DATAINCONSISTENCY: copy error.

The workaround is to not configure the HTTP secure server.

•CSCsq17094

If a new stack master is elected, and some link-state group members are interfaces on this stack master, some or all downstream interfaces of the link-state group no longer operate.

The workaround is to reload the entire stack.

•CSCsr37307

If your switch is installed in an HP c-Class blade enclosure that is running OA version 2.20, and you perform these actions, the port status might remain in shutdown mode:

–First you enter the shutdown interface configuration command on any switch downlink port 1 to 16.

–Next you insert the switch in slot 1 of the blade enclosure.

–The corresponding blade enclosure slot changes from empty state to not empty.

–You enter the no shutdown interface configuration command for the switch downlink port.

This issue occurs only if you are running Cisco IOS version 12.2(44)SE to 12.2(44)SE2 (only available as IPBase).

The workaround is to reload the switch.

Resolved Caveats

These are the caveats resolved in the Cisco IOS Release 12.2(40)EX3:

•CSCsg58889

If IEEE 802.1Q tunneling and Layer 2 protocol tunneling were configured first on physical ports, and the ports were then added to an unconfigured port channel, the port channel stopped forwarding traffic if one or more physical ports in the EtherChannel was shut down. In this situation, the port channel now forwards traffic.

•CSCsh70377

When a secondary VLAN was disassociated from the primary VLAN, duplicate MAC addresses on the primary VLAN remained in the MAC address table. The primary VLAN no longer remains in the MAC address table in this situation.

•CSCsi01526

Traceback messages appeared if you entered the no switchport interface configuration command to change a Layer 2 interface that belonged to a port channel to a routed port. The traceback messages no longer appear in these circumstances.

•CSCsi67680

When unicast routing was disabled and then re-enabled, virtual routing and forwarding (VRF) routing was disabled on the switch interfaces. This effect no longer occurs.

•CSCsi73653

After a stack-master failover, switch ports in the stack would not detect new devices. Switch ports now detect new devices after a stack-master failover.

•CSCsj22678

A delay occurred when you removed an access control list (ACL) from a switch stack under certain conditions. The delay no longer occurs in those conditions.

•CSCsk19926

Traffic was not received on a member port in a switch stack under certain conditions. The member port now receives traffic.

Documentation Updates

The online version of the Cisco Catalyst Blade Switch 3000 Series for HP Getting Started Guide has been updated with this information:

Note on WS-CBS3125G-S and WS-CBS3125X-S switches:

•The WS-CBS3125G-S is the same product as the WS-CBS3120G-S.

•The WS-CBS3125X-S is the same product as the WS-CBS3120X-S.

The functionality and the performance of WS-CBS3125 switches are same as those of WS-CBS3120 switches. All Cisco Catalyst Blade Switch for HP models are HP BladeSystem c-Class compatible.

Related Documentation

These documents provide complete information about the Cisco Catalyst 3120 for HP Blade Switch and are available from this Cisco.com site:

For other information about related products, see these documents on Cisco.com:

•Getting Started with Cisco Network Assistant

•Release Notes for Cisco Network Assistant

•Network Admission Control Software Configuration Guide

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0807R)