Cisco 3020 - Cisco Catalyst Blade Switch Instruction Manual

Corporate Headquarters:
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Release Notes for the Cisco Catalyst
Blade Switch 3020 for HP,
Cisco IOS Release 12.2(35)SE and Later
Revised May 22, 2007
Cisco IOS Release 12.2(35)SE and later runs on the Cisco Catalyst Blade Switch 3020 for HP, also
referred to as the switch.
These release notes include important information about Cisco IOS Release 12.2(35)SE and later and
any limitations, restrictions, and caveats that apply to them. Verify that these release notes are correct
for your switch:
•If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•If your switch is on, use the show version privileged EXEC command. See the “Finding the
Software Version and Feature Set” section on page 3.
•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 on page 3.
For the complete list of Cisco Catalyst Blade Switch 3020 for HP documentation, see the “Related
Documentation” section on page 33.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
This software release is part of a special release of Cisco IOS software that is not released on the same
8-week maintenance cycle that is used for other platforms. As maintenance releases and future software
releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Contents
This information is in the release notes:
•“System Requirements” section on page 2
•“Upgrading the Switch Software” section on page 3
•“Installation Notes” section on page 6

2
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
System Requirements
•“Limitations and Restrictions” section on page 6
•“Important Notes” section on page 11
•“Open Caveats” section on page 13
•“Resolved Caveats” section on page 16
•“Documentation Updates” section on page 19
•“Related Documentation” section on page 33
•“Obtaining Documentation” section on page 34
•“Documentation Feedback” section on page 34
•“Product Alerts and Field Notices” section on page 36
•“Obtaining Technical Assistance” section on page 36
•“Obtaining Additional Publications and Information” section on page 38
System Requirements
The system requirements are described in these sections:
•“Hardware Supported” section on page 2
•“Device Manager System Requirements” section on page 2
Hardware Supported
The hardware supported on this release is the Cisco Catalyst Blade Switch 3020 for HP.
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
•“Hardware Requirements” section on page 2
•“Software Requirements” section on page 3
Hardware Requirements
Table 1 lists the minimum hardware requirements for running the device manager.
Table 1 Minimum Hardware Requirements
Processor Speed DRAM Number of Colors Resolution Font Size
Intel Pentium II1
1. We recommend Intel Pentium 4.
64 MB2
2. We recommend 256-MB DRAM.
256 1024 x 768 Small

3
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Upgrading the Switch Software
Software Requirements
Table 2 lists the supported operating systems and browsers for using the device manager, which does not
require a plug-in. The device manager verifies the browser version when starting a session to ensure that
the browser is supported.
Note Windows NT and Windows 98 are no longer supported.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for
important information:
•“Finding the Software Version and Feature Set” section on page 3
•“Deciding Which Files to Use” section on page 3
•“Upgrading a Switch by Using the Device Manager” section on page 4
•“Upgrading a Switch by Using the CLI” section on page 5
•“Recovering from a Software Failure” section on page 5
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.
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 2 Supported Operating Systems and Browsers
Operating System Minimum Service Pack or Patch
Microsoft Internet
Explorer1
1. Service Pack 1 or higher is required for Internet Explorer 5.5.
Netscape
Navigator
Windows 2000 None 5.5 or 6.0 7.1
Windows XP None 5.5 or 6.0 7.1

4
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Upgrading the Switch Software
Table 3 lists the filenames for this software release.
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 to which you are upgrading. You should keep these archived
images until you have upgraded all devices in the network to the new Cisco IOS image and until you
have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more
information:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a
host by using the copy flash: tftp: privileged EXEC command.
Note Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy
all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and
archive it on an internal host in your network.
You can also configure the switch as a TFTP server to copy files from one switch to another without
using an external TFTP server by using the tftp-server global configuration command. For more
information about the tftp-server command, see the “Basic File Transfer Services Commands” section
of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_r/ffrprt2/frf011.htm#
wp1018426
Upgrading a Switch by Using the Device Manager
You can upgrade switch software by using the device manager. For detailed instructions, click Help.
Note When using the device manager to upgrade your switch, do not use or close your browser session after
the upgrade process begins. Wait until after the upgrade process completes.
Table 3 Cisco IOS Software Image Files
Filename Description
cbs30x0-lanbase-tar.122-35.SE.tar Cisco Catalyst Blade Switch 3020 for HP image file and
device manager files.
This image has Layer 2+ features.
cbs30x0-lanbasek9-tar.122-35.SE.tar Cisco Catalyst Blade Switch 3020 for HP cryptographic
image file and device manager files.
This image has the Kerberos and SSH features.

5
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Upgrading the Switch Software
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 3 on page 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://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
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/cbs30x0lanbase-mz
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.

6
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Installation Notes
Installation Notes
You can assign IP information to your switch by using these methods:
•The Express Setup program or the HP Onboard Administrator program described in the getting
started guide.
•The CLI-based setup program, as described in the hardware installation guide.
•The DHCP-based autoconfiguration, as described in the software configuration guide.
•Manually assigning an IP address, as described in the software configuration guide.
New Software Feature
This release supports Web authentication to authenticate a supplicant (client) that does not support
IEEE 802.1x functionality. For more information, see the “Documentation Updates” section on
page 19.
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations
that will not be fixed, and there is not always a workaround. Some features might not work as
documented, and some features could be affected by recent changes to the switch hardware or software.
This section contains these limitations:
•“Cisco IOS Limitations” section on page 6
•“Device Manager Limitations” section on page 10
Cisco IOS Limitations
These limitations apply to switch:
•“Configuration” section on page 7
•“Ethernet” section on page 7
•“IP” section on page 8
•“IP Telephony” section on page 8
•“MAC Addressing Multicasting” section on page 8
•“MAC Addressing Multicasting” section on page 8
•“QoS” section on page 9
•“SPAN and RSPAN” section on page 9
•“Trunking” section on page 10
•“VLAN” section on page 10

7
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Limitations and Restrictions
Configuration
These are the configuration limitations:
•A static IP address might be removed when the previously acquired DHCP IP address lease expires.
This problem occurs under these conditions:
– When the switch is booted without a configuration (no config.text file in flash memory).
– When the switch is connected to a DHCP server that is configured to give an address to it (the
dynamic IP address is assigned to VLAN 1).
– When an IP address is configured on VLAN 1 before the dynamic address lease assigned to
VLAN 1 expires.
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•When connected to some third-party devices that send early preambles, a switch port operating at
100 Mbps full duplex or 100 Mbps half duplex might bounce the line protocol up and down. The
problem is observed only when the switch is receiving frames.
The workaround is to configure the port for 10 Mbps and half duplex or to connect a hub or a
nonaffected device to the switch. (CSCed39091)
•When port security is enabled on an interface in restricted mode and the switchport block unicast
interface command has been entered on that interface, MAC addresses are incorrectly forwarded
when they should be blocked
The workaround is to enter the no switchport block unicast interface configuration command on
that specific interface. (CSCee93822)
•A traceback error occurs if a crypto key is generated after an SSL client session.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch.
(CSCef59331)
Ethernet
This is the Ethernet limitation:
•Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports
are distributed to member ports on load balance configuration and traffic characteristics like MAC
or IP address. More than one traffic stream might map to same member ports, based on hashing
results calculated by the ASIC.
If this happens, traffic distribution is uneven on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel
can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
– for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip
– for incrementing source-ip traffic, configure load balance method as src-ip
– for incrementing dest-ip traffic, configure load balance method as dst-ip
– Configure the number of ports in the EtherChannel so that the number is equal to a power of 2
(for example, 2, 4, or 8)
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP
addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is
optimal. (CSCeh81991)

8
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Limitations and Restrictions
IP
This is the IP limitation:
When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response
time might be slow when you are using the console. The workaround is to use rate limiting on DHCP
traffic to prevent a denial of service attack from occurring. (CSCeb59166)
IP Telephony
These are the IP telephony limitations:
•Some access point devices are incorrectly discovered as IEEE 802.3af Class 1 devices. These access
points should be discovered as Cisco pre-standard devices. The show power inline user EXEC
command shows the access point as an IEEE Class 1 device. The workaround is to power the access
point by using an AC wall adaptor. (CSCin69533)
•After you change the access VLAN on a port that has IEEE 802.1x enabled, the IP phone address is
removed. Because learning is restricted on IEEE 802.1x-capable ports, it takes approximately 30
seconds before the address is relearned. No workaround is necessary. (CSCea85312)
MAC Addressing Multicasting
These are the multicasting limitations:
•If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more
than the maximum number specified by the show sdm prefer global configuration command, the
traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp
snooping multicast-table privileged EXEC command output shows otherwise. The workaround is
to reduce the number of multicast routes and IGMP snooping groups to less than the maximum
supported value. (CSCdy09008)
•IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets
that are forwarded through software. Hence, with multicast routing enabled, the first few packets are
sent from a port even when IGMP filtering is set to deny those groups on that port. There is no
workaround. (CSCdy82818)
•If an IGMP report packet has two multicast group records, the switch removes or adds interfaces
depending on the order of the records in the packet:
– If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the
switch removes the port from the group.
– If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the
switch adds the port to the group.
There is no workaround. (CSCec20128)
•When IGMP snooping is disabled and you enter the switchport block multicast interface
configuration command, IP multicast traffic is not blocked.
The switchport block multicast interface configuration command is only applicable to non-IP
multicast traffic.
There is no workaround. (CSCee16865)

9
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Limitations and Restrictions
•Incomplete multicast traffic can be seen under either of these conditions:
– You disable IP multicast routing or re-enable it globally on an interface.
– A switch mroute table temporarily runs out of resources and recovers later.
The workaround is to enter the clear ip mroute privileged EXEC command on the interface.
(CSCef42436)
After you configure a switch to join a multicast group by entering the ip igmp join-group
group-address interface configuration command, the switch does not receive join packets from the
client, and the switch port connected to the client is removed from the IGMP snooping forwarding
table.
Use one of these workarounds:
– Cancel membership in the multicast group by using the no ip igmp join-group group-address
interface configuration command on an SVI.
– Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id
global configuration command. (CSCeh90425)
QoS
These are the quality of service (QoS) limitations:
•Some switch queues are disabled if the buffer size or threshold level is set too low with the mls qos
queue-set output global configuration command. The ratio of buffer size to threshold level should
be greater than 10 to avoid disabling the queue. The workaround is to choose compatible buffer sizes
and threshold levels. (CSCea76893)
•When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses
shaped round robin (SRR) as the queuing mechanism. The auto-QoS feature is designed on each
platform based on the feature set and hardware limitations, and the queuing mechanism supported
on each platform might be different. There is no workaround. (CSCee22591)
SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•Egress SPAN routed packets (both unicast and multicast) show the incorrect source MAC address.
For remote SPAN packets, the source MAC address should be the MAC address of the egress VLAN,
but instead the packet shows the MAC address of the RSPAN VLAN. For local SPAN packets with
native encapsulation on the destination port, the packet shows the MAC address of VLAN 1. This
problem does not appear with local SPAN when the encapsulation replicate option is used. This
limitation does not apply to bridged packets. The workaround is to use the encapsulate replicate
keywords in the monitor session global configuration command. Otherwise, there is no
workaround. This is a hardware limitation. (CSCdy81521)
•During periods of very high traffic when two RSPAN source sessions are configured, the VLAN ID
of packets in one RSPAN session might overwrite the VLAN ID of the other RSPAN session. If this
occurs, packets intended for one RSPAN VLAN are incorrectly sent to the other RSPAN VLAN.
This problem does not affect RSPAN destination sessions. The workaround is to configure only one
RSPAN source session. This is a hardware limitation. (CSCea72326)

10
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(35)SE and Later
OL-8918-03
Limitations and Restrictions
•Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol
(PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local
SPAN session. The workaround is to use the monitor session session_number destination
{interface interface-id encapsulation replicate}global configuration command for local SPAN.
(CSCed24036)
Trunking
These are the trunking limitations:
•The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link
[ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber.
This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the
frame to an IEEE 802.1Q trunk interface. There is no workaround. (CSCdz33708)
•IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a
member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the
output interface for the multicast route entry assigned to the multicast group and an interface in
VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN
interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is
forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no
workaround. (CSCdz42909).
•For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might
appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q
frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the
frames are not counted on the interface statistics. There is no workaround. (CSCec35100).
VLAN
This is the VLAN limitation:
•If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000,
the switch can fail.
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
Device Manager Limitations
These are the Device Manager limitations for this release:
•When you are prompted to accept the security certificate and you click No, you only see a blank
screen, and the device manager does not launch.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
•When the physical UID LED of the switch is on, it is blue. However, when the image of this LED
on the device manager Front Panel view is on, it is green.
There is no workaround (CSCsd98457).