Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(46)SE

Table Of Contents

Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(46)SE

Contents

System Requirements

Hardware Supported

Device Manager System Requirements

Hardware Requirements

Software Requirements

Cisco Network Assistant Compatibility

Upgrading the Switch Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Archiving Software Images

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

New Software Features

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Cisco IOS Limitations

Access Control List

Address Resolution Protocol

Cisco X2 Transceiver Modules and SFP Modules

Configuration

EtherChannel

IEEE 802.1x Authentication

Multicasting

QoS

Routing

SPAN and RSPAN

VLANs

Stacking

Device Manager Limitations

Important Notes

Cisco IOS Notes

Device Manager Notes

Open Caveats

Resolved Caveats

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(46)SE

---

August 28, 2008

Cisco IOS Release 12.2(46)SE runs on the Cisco Catalyst Blade Switch 3120 for HP switches. These switches 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(46)SE 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.

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

You can download the switch software from this site (registered Cisco.com users with a login password):

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=268438038

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.

For the complete list of the Cisco Catalyst Blade Switch 3120 for HP documentation, see the "Related Documentation" section.

---

Note References in this document to the CBS3120G-S and CBS3120X-S switches also apply to the CBS3125G-S and CBS3125X-S switches, respectively.

---

Contents

These sections provide information about this release:

•System Requirements

•Upgrading the Switch Software

•Installation Notes

•New Features

•Minimum Cisco IOS Release for Major Features

•Limitations and Restrictions

•Important Notes

•Open Caveats

•Resolved Caveats

•Documentation Updates

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

System Requirements

The system requirements are described in these sections:

•Hardware Supported

•Device Manager System Requirements

•Cisco Network Assistant Compatibility

Hardware Supported

Table 1 lists the hardware supported on this release.

Table 1 Cisco Catalyst Blade Switch 3120 for HP Supported Hardware 

Switch Hardware	Description	Supported by Minimum Cisco IOS Release
CBS3120G-S and CBS3120X-S	•18 internal Gigabit Ethernet 1000BASE-X downlink ports that connect to the blade enclosure. •4 Gigabit Ethernet (RJ-45) uplink ports •4 RJ-45 SFP module slots1 / 2 10-Gigabit Ethernet X2 module slots •1 Ethernet management port (Fa0) used only for switch module management traffic	Cisco IOS Release 12.2(40)EX1
Cisco X2 transceiver modules (supported only on the CBS3120X-S model)	X2-10GB-SR V02 or later X2-10GB-CX4 V03 or later X2-10GB-LRM V03 or later X2-10GB-LX4 V03 or later	Cisco IOS Release 12.2(40)EX1
Cisco TwinGig Converter Module	Dual SFP2 X2 converter module to allow the switch to support SFP Gigabit Ethernet modules	Cisco IOS Release 12.2(40)EX1
SFP modules	1000BASE-LX/LH 1000BASE-SX 1000BASE-T	Cisco IOS Release 12.2(40)EX1

1 X2 module supported only on the CBS3120X-S model 2 SFP = small form-factor pluggable

---

Caution The Cisco Catalyst Blade Switch 3120 for HP switch modules 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:

•Hardware Requirements

•Software Requirements

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
233 MHz minimum1	512 MB2	256	1024 x 768	Small

1 We recommend 1 GHz. 2 We recommend 1-GB DRAM.

Software Requirements

Table 3 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.

Table 3 Supported Operating Systems and Browsers 

Operating System	Minimum Service Pack or Patch	Microsoft Internet Explorer 1	Mozilla FireFox
Windows 2000	None	6.0 or 7.0	1.5 or 2.0
Windows XP	None	6.0 or 7.0	1.5 or 2.0
Windows 2003	None	6.0 or 7.0	1.5 or 2.0
Vista	None	6.0 or 7.0	1.5 or 2.0

1 Service Pack 1 or higher is required for Internet Explorer 5.5.

Cisco Network Assistant Compatibility

Cisco IOS 12.2(40)EX1 and later is only compatible with Cisco Network Assistant 5.3 and later. You can download 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.

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

•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

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.

Table 4 lists the filenames for this software release.

---

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-46.SE.tar	Cisco Catalyst Blade Switch 3120 for HP universal image and device manager files. This image has all the supported features that are enabled by the software license installed on the switch.
cbs31x0-universalk9-tar.122-46.SE.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:

http://www.cisco.com/en/US/products/ps6748/products_installation_and_configuration_guides_list.html

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:

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/en/US/docs/ios/12_2/configfun/command/reference/ffun_r.html

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.

To download software, follow these steps:

---

Step 1 Use Table 4 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://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=268438038

To download the universal software image files for a Cisco Catalyst Blade Switch 3120 for HP, click Blade Switches > Cisco Catalyst Blade Switch 3000 Series for HP >. To obtain authorization and to download the cryptographic software files, click Cisco Catalyst Blade Switch 3000 Series for HP 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:

Switch# ping tftp-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:

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/cbs31x0-universal-tar.122-40.EX1.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 additional recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.

Installation Notes

You can assign IP information to your switch by using these methods:

•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 and updated software features provided in this release:

•"New Hardware Features" section

•"New Software Features" section

New Hardware Features

For a list of all supported hardware, see the "Hardware Supported" section.

New Software Features

These are the new software features for this release:

•Voice aware IEEE 802.1x and MAC authentication bypass (MAB) security violation to shut down only the data VLAN on a port when a security violation occurs

•Local web authentication banner so that custom banner or image file can be displayed at a web authentication login screen

•Support for the CISCO-NAC-NAD and CISCO-PAE MIBs

•The ability to exclude a port in a VLAN from the SVI line-state up or down calculation

•Support for HSRP Version 2 (HSRPv2)

•Disabling MAC address learning on a VLAN

•PAgP Interaction with Virtual Switches and Dual-Active Detection, also referred to as enhanced PAgP

•Support for rehosting a software license and for using an embedded evaluation software license

•DHCP server port-based address allocation for the preassignment of an IP address to a switch port

•HSRP for IPv6 (with the advanced IP services feature set)

•DHCP for IPv6 relay, client, server address assignment and prefix delegation (with the advanced IP services feature set)

•IPv6 default router preference (DRP) for improving the ability of a host to select an appropriate router

•Generic message authentication support with the SSH Protocol and compliance with RFC 4256

Minimum Cisco IOS Release for Major Features

Table 5 lists the minimum software release (after the first release) required to support the major features of the Catalyst Blade Switch 3120 for HP. Features not listed are supported in all releases.

Table 5 Features Introduced After the First Release and the Minimum Cisco IOS Release Required 

Feature	Minimum Cisco IOS Release Required	Catalyst Blade Switch Support
Voice aware IEEE 802.1x and MAC authentication bypass (MAB) security violation	12.2(46)SE	3120
Local web authentication banner	12.2(46)SE	3120
Support for HSRP Version 2 (HSRPv2)	12.2(46)SE	3120
Disabling MAC address learning on a VLAN	12.2(46)SE	3120
PAgP Interaction with Virtual Switches and Dual-Active Detection, also referred to as enhanced PAgP	12.2(46)SE	3120
Support for rehosting a software license and for using an embedded evaluation software license	12.2(46)SE	3120
DHCP server port-based address allocation for the preassignment of an IP address to a switch port	12.2(46)SE	3120
HSRP for IPv6	12.2(46)SE	3120
DHCP for IPv6 relay, client, server address assignment and prefix delegation	12.2(46)SE	3120
IPv6 default router preference (DRP) for improving the ability of a host to select an appropriate router.	12.2(46)SE	3120
Generic message authentication support with the SSH Protocol and compliance with RFC 4256.	12.2(46)SE	3120

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

•Device Manager Limitations

Cisco IOS Limitations

These limitations apply to the Cisco Catalyst Blade Switch 3120 for HP:

•Access Control List

•Address Resolution Protocol

•Cisco X2 Transceiver Modules and SFP Modules

•Configuration

•EtherChannel

•IEEE 802.1x Authentication

•Multicasting

•QoS

•Routing

•SPAN and RSPAN

•Stacking

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 static mac-addr vlan vlan-id drop 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:

PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 0, class 51, max_msg 128, total throttled 984323

-Traceback= 6625EC 5DB4C0 5DAA98 55CA80 A2F2E0 A268D8

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 configuration command 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 no shutdown 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)

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

15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1 (ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C 4CEB50 859DF4 A7BF28 A98260 882658 879A58

There is no workaround. (CSCsh12472)

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:

–Multicast routing is enabled in the VLAN.

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

–The packet is denied by the IP multicast boundary access-list configured on the VLAN.

There is no workaround. (CSCei08359)

•Reverse path forwarding (RPF) failed multicast traffic might cause a flood of Protocol Independent Multicast (PIM) messages in the VLAN when a packet source IP address is not reachable.

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-groups number 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.

Use one of these workarounds (CSCsg91027):

–Disable logging to the console.

–Rate-limit logging messages to the console.

–Remove the logging event spanning-tree interface configuration command from the interfaces.

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

–If you are using Firefox version 1.5, choose Tools > Options > Advanced > Security > View Certificates > Web Sites, select the certificate, and click Delete.

–If you are using Firefox version 2.0, choose Tools > Options > Advanced > Encryption > View Certificates > Web Sites, select the certificate, and click Delete.

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:

•Cisco IOS Notes

•Device Manager Notes

Cisco IOS Notes

These notes apply to Cisco IOS software:

•If the switch requests information from the Cisco Secure Access Control Server (ACS) and the message exchange times out because the server does not respond, a message similar to this appears:

00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not 
responding.

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.

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 {aaa | enable | local}	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.

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

•CSCsi06399

When a RIP network and IP address are configured on an interface, a traceback error occurs after you enter the shutdown, no shutdown, switchport, and no switchport interface configuration commands.

The workaround is to configure the RIP network and the IP address after you configure the interface.

•CSCsi14303

When booting a switch stack configured for IP source guard with port security and dynamic ARP inspection, a message similar to this might appear:

SYS-2-LINKED: Bad enqueue of 2A3DE74 in queue 22881BC (l3a3-9) -Process= "Port-Security", ipl= 6, pid= 161 (l3a3-9) -Traceback= 119CC50 11D2264 9571E0 119B4E0 95D41C 80DBD8 80E734 80B998 80AAD4 80B55C 9EB158 9E2544 (l3a3-9)

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

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

•CSCsi73653

After a stack-master failover, switch ports in the stack cannot detect new devices. This only affects new devices connected to the switch ports. Devices that were connected to active ports before the failover remain in a trusted state.

There is no workaround.

•CSCsj22678

A delay can occur when you remove an access control list (ACL) from a switch stack under these conditions:

–A QoS, per-port policy map is attached to a large number of SVIs in the stack.

–A per-VLAN QoS, per-port policer policy map is attached to a large number of switched virtual interfaces (SVIs) in the stack.

–The ACL to be removed is being used by the policy map.

–There are three or more switches in the stack.

The delay can increase, up to 30 minutes, depending on the number of SVIs that are attached to the policy map. The delay does not affect the operation of the policy-map. However, either of these workarounds will reduce the length of the delay:

–Remove the access control entries (ACEs) from the destination ACL, leaving the ACL empty. (The effect is the same as removing the ACL itself.)

–Detach the affected policy-maps from all the attached VLANs and SVIs, remove the ACL from the policy-maps, and then reattach the policy-maps back to the original SVIs.

•CSCsk19926

Traffic is not received on a member port in a switch stack under these conditions:

–The port is in a cross-stack EtherChannel.

–One or more of the master switch Cisco TwinGig Converter Module ports are in the cross-stack EtherChannel.

–This member switch has been reloaded.

The workaround is to enter the shutdown and no shutdown interface configuration commands on the affected interface or to reload the entire stack instead of a single member switch.

•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 switch current-stack-member-number renumber new-stack-member-number and the switch stack-member-number provision type 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.

•CSCso96778

When you use the ipv6 address dhcp interface configuration command on an interface that is configured in router mode, other addresses on the prefix associated with the new address might not be accessible.

The workaround is to use the ipv6 address dhcp interface configuration command on an interface that is configured in host mode, or configure a static route to the prefix through the interface.

Resolved Caveats

These are the caveats that have been resolved in Cisco IOS Release 12.2(46)SE:

•CSCin91851, CSCsh42013, and CSCsh42316

The SSH Protocol now supports generic message authentication and is compliant with RFC 4256.

•CSCsa73179

A switch no longer fails under these conditions:

–OSPF is in the switch image.

–You enter the RIP no default-information router configuration command.

•CSCse07265

If you configure IP SLA to generate a syslog message for a reaction trap and an operation with a trigger of timeout or connectionless, a syslog message now appears when triggered.

•CSCsg58889

If IEEE 802.1Q tunneling and Layer 2 protocol tunneling are first configured on physical ports, and the ports are then added to an unconfigured port channel, the port channel no longer stops forwarding traffic. The port channel now inherits the Layer 2 port configuration.

•CSCsg77818

The switch no longer reloads when an interface is configured with both trust boundary and Cisco Discovery Protocol (CDP) or when the CDP table is repeatedly disabled, enabled, or cleared.

•CSCsh70377

When a secondary VLAN is disassociated from the primary VLAN, duplicate MAC addresses on the primary VLAN no longer remain in the MAC address table.

•CSCsi01526

Traceback messages no longer appear if you enter the no switchport interface configuration command to change a Layer 2 interface from a port channel to a routed port.

•CSCsi50367

When changing a switch module port access VLAN from static to dynamic or the reverse, a message similar to this no longer appears:

01:43:55: PSECURE: Assert failure: is_etherchnl(hwidb_or_null swidb)): 
../switch/psecure/psecure_ifc.c: 412: psecure_get_vlanid (l2a1-5) 01:43:55Traceback= 
804484 809604 802258 806904 70FC 8D70 5C97BC 6901DC 6903CC 9EF8D8 9E6CC4 (l2a1-5)

•CSCsi67680

When unicast routing is disabled and then re-enabled, virtual routing and forwarding (VRF) routing is no longer disabled on the switch module interfaces.

•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 restore it, the policy map now correctly re-attaches to the same SVI

•CSCsj77933

A space entered before a comma in the define interface-range or the interface range global configuration command is now correctly saved in the switch configuration.

•CSCsk47893

A switch running the IP base image now supports full EIGRP stub routing.

•CSCsl72968

When multidomain authentication (MDA) is configured on a stack member, a switch port in that stack is no longer intermittently enter disabled when the stack reloads.

•CSCso22855

If you specify the router ID before entering the autonomous-system autonomous-system-number address-family configuration command, the router ID is no longer lost when the switch reloads.

•CSCso22883

Any form of the passive-interface command entered in one instance propagates to all configured address-family instances for the same EIGRP routing process.

•CSCso66528

When an interface configured with port security reloads or you clear an error-disabled condition, the interface no longer returns this traceback message:

%BIT-4-OUTOFRANGE: bit 0 is not in the expected range of 1 to 4095

•CSCso70893

A message similar to this one no longer appears when you log into a switch through an SSH session and upgrade the switch by using the archive download-sw privileged EXEC command

*Mar 11 06:48:22.729 JST: %SCHED-3-THRASHING: Process thrashing on watched message 
event. -Process= "SSH Process", ipl= 6, pid= 147

•CSCso72052

An end host no longer remains in the guest VLAN after IEEE 802.1X authentication.

•CSCso78837

When you use the clear counters privileged EXEC command to clear interface counters on a port-channel interface, the show interfaces etherchannel privileged EXEC command output now shows the correct number for received broadcast packets.

•CSCso81660

The show interfaces command output for a switch stack now shows the correct values for the output drops.

•CSCsq17094

Downstream switch interfaces in a link state group no longer fail under these conditions:

–The switch is part of a stack.

–There is a master switch over.

–Some (or all) of the link state group interfaces are on the switch that becomes the new stack master.

•CSCsr55949

When IEEE 802.1x is enabled on the switch, EAP notification packets are no longer dropped.

Documentation Updates

This information is added to the "Using Route Maps to Redistribute Routing Information" section in the "Configuring IP Unicast Routing" chapter of the software configuration guide:

---

Note A route map with no set route-map configuration commands is sent to the CPU, which causes high CPU utilization.

---

These system messages are not yet in the system message guide:

Error Message    %PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED: Unable to create [chars] 

Explanation    The switch cannot create the specified managed object. [chars] is the object name.

Recommended Action    No action is required.

Error Message    %PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER: PAgP running on [chars] 
informing virtual switches of dual-active: new active id [enet], old id [enet] 

Explanation    Port Aggregation Protocol (PAgP) received a new active ID on the specified interface, which means that all virtual switches are in a dual-active scenario. The interface is informing virtual switches of this, which causes one switch to go into recovery mode. [chars] is the interface. The first [enet] is the new active ID. The second [enet] is the ID that it replaces.

Recommended Action    No action is required.

Error Message    %PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars] 
registry 

Explanation    The switch could not add a function to the registry. [chars] is the registry name.

Recommended Action    No action is required.

Error Message    %PM-6-EXT_VLAN_ADDITION: Extended VLAN is not allowed to be configured 
in VTP CLIENT mode. 

Explanation    The switch did not add a VLAN in VTP client mode.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section in the system message guides.

These messages have been deleted from the system message guide:

Error Message    %VQPCLIENT-2-INITFAIL: Platform-specific VQP initialization failed. 
Quitting 

Error Message    %VQPCLIENT-2-IPSOCK: Could not obtain IP socket 

Error Message    %VQPCLIENT-7-NEXTSERV: Trying next VMPS [IP_address] 

Error Message    %VQPCLIENT-7-PROBE: Probing primary server [IP_address] 

Error Message    %VQPCLIENT-2-PROCFAIL: Could not create process for VQP. Quitting 

Error Message    %VQPCLIENT-7-RECONF: Reconfirming VMPS responses 

Error Message    %VQPCLIENT-2-SHUTDOWN: Interface [chars] shutdown by VMPS 

Error Message    %VQPCLIENT-3-THROTTLE: Throttling VLAN change on [chars] 

Related Documentation

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

http://www.cisco.com/en/US/products/ps6748/tsd_products_support_series_home.html

•Cisco Catalyst Blade Switch 3000 Series for HP Getting Started Guide

•Regulatory Compliance and Safety Information for the Cisco Catalyst Blade Switch 3000 Series for HP

•Release Notes for the Cisco Catalyst Blade Switch 3120 for HP

---

Note Before you install, configure, or upgrade the switch module, see the release notes on Cisco.com for the latest information.

---

•Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide

•Cisco Catalyst Blade Switch 3120 for HP Command Reference

•Cisco Catalyst Blade Switch 3120 for HP System Message Guide

•Cisco Software Activation Document for HP

•These compatibility matrix documents are available from this Cisco.com site:

http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html

–Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix

–Cisco Small Form-Factor Pluggable Modules Compatibility Matrix

–Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.

---

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

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

© 2008 Cisco Systems, Inc. All rights reserved.