Table Of Contents
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE
Updates to the Software Configuration Guide
Updates to the System Message Guide
Updates to the Getting Started Guide
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(44)SE and Later
Revised March 25, 2009
Cisco IOS Release 12.2(44)SE and later runs on the Cisco Catalyst Blade Switch 3020 for HP, referred to as the switch. Unless otherwise noted, the term switch refers to a standalone switch.
http://www.cisco.com/en/US/products/ps8743/prod_release_notes_list.html
Note
If you wish to use Device Manager to upgrade the switch from Cisco IOS Release 12.2(35)SE through Cisco IOS Release 12.2(40)SE1 (the LAN Base image) to Cisco IOS Release 12.2(44)SE or later (the IP base image), you must first upgrade to Cisco IOS Release 12.2(40)SE2.
These release notes include important information about Cisco IOS Release 12.2(44)SE and any limitations, restrictions, and caveats that apply to them. Verify that these release notes are correct for your switch:
•
•
•
For the complete list of Cisco Catalyst Blade Switch 3020 for HP documentation, see the "Updates to the Getting Started Guide" 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/MDFTree.x?butype=switches
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
The system requirements are described in these sections:
•
Hardware Supported
Table 1 lists the hardware supported on this release.
Table 1 Supported Hardware
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
•
•
Hardware Requirements
Table 2 lists the minimum hardware requirements for running the device manager.
Table 2 Minimum Hardware Requirements
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, 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
Table 3 Supported Operating Systems and Browsers
Windows 2000
None
5.5 or 6.0
7.1
Windows XP
None
5.5 or 6.0
7.1
1 Service Pack 1 or higher is required for Internet Explorer 5.5.
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
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.
Note
Table 4 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
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
You can upgrade switch software by using the device manager. For detailed instructions, click Help.
Note
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
Step 2
http://www.cisco.com/public/sw-center/sw-lan.shtml
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/c3750-ipservices-tar.122-44.SE.tarYou 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:
•
•
•
•
New Software Features
These are the new software features for this release:
•
•
•
•
•
•
•
•
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
These limitations apply to the switch:
•
Configuration
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
The workaround is to configure the port for 10 Mp/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
Ethernet
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 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)
IP
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
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
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•
–
–
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:
–
–
QoS
•
•
•
The workaround is to use policy maps with 62 or fewer policers. (CSCsc59418)
SPAN and RSPAN
•
•
•
Trunking
•
•
•
VLAN
•
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
Device Manager Limitations
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
•
There is no workaround (CSCsd98457).
Important Notes
These sections describe the important notes related to this software release:
•
Cisco IOS Notes
These notes apply to Cisco IOS software:
•
•
•
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)SE (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 appliedpolicy map AutoQoS-Police-CiscoPhone not configuredIf this happens, enter the no auto qos voip cisco-phone interface command on all interface 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:
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
Open Caveats
•
The switch might display tracebacks similar to these examples when a large number of IEEE 802.1x supplicants try to repeatedly log in and log out.
Examples:
Jan 3 17:54:32 L3A3 307: Jan 3 18:04:13.459: %SM-4-BADEVENT: Event 'eapReq' is invalid for the current state 'auth_bend_idle': dot1x_auth_bend Fa9
Jan 3 17:54:32 L3A3 308: -Traceback= B37A84 18DAB0 2FF6C0 2FF260 8F2B64 8E912C Jan 3 19:06:13 L3A3 309: Jan 3 19:15:54.720: %SM-4-BADEVENT: Event 'eapReq_no_reAuthMax' is invalid for the current ate 'auth_restart': dot1x_auth Fa4
Jan 3 19:06:13 L3A3 310: -Traceback= B37A84 18DAB0 3046F4 302C80 303228 8F2B64 8E912C Jan 3 20:41:44 L3A3 315: .Jan 3 20:51:26.249: %SM-4-BADEVENT: Event 'eapSuccess' is invalid for the current state 'auth_restart': dot1x_auth Fa9
Jan 3 20:41:44 L3A3 316: -Traceback= B37A84 18DAB0 304648 302C80 303228 8F2B64 8E912C
There is no workaround.
•
When IEEE 802.1x is globally disabled on the switch by using the no dot1x system-auth-control global configuration command, some interface level configuration commands, including the dot1x timeout and dot1x mac-auth-bypass commands, become unavailable.
The workaround is to enable the dot1x system-auth-control global configuration command before attempting to configure interface level IEEE 802.1x parameters.
•
The switch does not correctly update the entPhysicalChildIndex objects from the ENTITY-MIB, and some of the entPhysicalChildIndex entries are missing from the table. This adversely affects network management applications such as CiscoWorks CiscoView because they cannot manage the switch.
There is no workaround.
•
When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.
The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command.
Resolved Caveats
This section describes the caveats that have been resolved in these releases:
•
•
•
•
•
•
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6
•
Symptoms: Several features within Cisco IOS software are affected by a crafted UDP packet vulnerability. If any of the affected features are enabled, a successful attack will result in a blocked input queue on the inbound interface. Only crafted UDP packets destined for the device could result in the interface being blocked, transit traffic will not block the interface.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available in the workarounds section of the advisory. This advisory is posted at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20090325-udp.shtml.
•
A vulnerability in the handling of IP sockets can cause devices to be vulnerable to a denial of service attack when any of several features of Cisco IOS software are enabled. A sequence of specially crafted TCP/IP packets could cause any of the following results:
–
–
–
–
Workarounds that mitigate this vulnerability are available in the "workarounds" section of the advisory. The advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-ip.shtml
•
When MAC authentication bypass (MAB) authentication fails, a memory leak no longer occurs.
•
When a VLAN is assigned for IEEE 802.1x authentication and no VLAN is assigned for other types of authentication (such as user authentication or reauthentication), the 802.1x VLAN assignment no longer persists across subsequent authentication attempts.
•
Cisco IOS software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.
Cisco has released free software updates that address this vulnerability.
Several mitigation strategies are outlined in the workarounds section of this advisory.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml
•
When the switch uses HTTP (web-based) authentication, a memory leak no longer occurs after authorization and policy download.
•
The server side of the Secure Copy (SCP) implementation in Cisco IOS software contains a vulnerability that could allow authenticated users with an attached command-line interface (CLI) view to transfer files to and from a Cisco IOS device that is configured to be an SCP server, regardless of what users are authorized to do, per the CLI view configuration. This vulnerability could allow valid users to retrieve or write to any file on the device's file system, including the device's saved configuration and Cisco IOS image files, even if the CLI view attached to the user does not allow it. This configuration file may include passwords or other sensitive information.
The Cisco IOS SCP server is an optional service that is disabled by default. CLI views are a fundamental component of the Cisco IOS Role-Based CLI Access feature, which is also disabled by default. Devices that are not specifically configured to enable the Cisco IOS SCP server, or that are configured to use it but do not use role-based CLI access, are not affected by this vulnerability.
This vulnerability does not apply to the Cisco IOS SCP client feature.
Cisco has released free software updates that address this vulnerability.
There are no workarounds available for this vulnerability apart from disabling either the SCP server or the CLI view feature if these services are not required by administrators.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090325-scp.shtml.
•
A switch no longer displays processor memory-allocation failure messages under these conditions:
–
–
–
Note
This is resolved in Cisco IOS 12.2(44)SE6 and later.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5
•
Excessive IPRT-3-PATHIDX error messages no longer appear in the log file.
•
When configuring an IP SSH version 2 connection, you can no longer create an RSA key that is less than 768 bits.
•
RIP routes now correctly update when the maximum-paths 16 option is used.
•
The DHCP server can be configured to send DHCP Not Acknowledge(DHCPNAK) messages to unknown clients.
•
The dot1x timeout reauth-period server interface configuration command now works correctly. In previous releases, the switch would reauthenticate correctly after the command was entered, but the switch would then reauthenticate every 10 minutes.
•
The cdpCacheAddress value now appears in a GLOBAL_UNICAST address.
•
The switch now correctly processes ingress traffic when a port is configured with a short 802.1x tx-period timer value (such as dot1x timeout tx-period 3).
•
The username is now properly logged when the remote command privileged EXEC command is used to configure a cluster member.
•
Avaya IP phones now correctly authenticate on an 802.1x-enabled switch port.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3
•
An SNMP access-control list (ACL) now works correctly on virtual routing and forwarding (VRF) interfaces.
•
Intermittently switch reloads no longer occur when IP helper addresses are configured on a VLAN.
•
When multiple voice-over-IP phones are connected to a switch or switch stack with MAC authentication bypass enabled, setting the IEEE 802.1x timeout period too low no longer causes a switch in single-host mode to authenticate the phones using MAC authentication bypass, except when other data packets are received before CDP packets.
•
An end host no longer remains in the guest VLAN after an IEEE 802.1X authentication.
•
A switch no longer drops Cisco Group Management Protocol (CGMP) packets.
•
The switch no longer reloads with an address error if the TACACS+ server sends an authentication error when the access control system is configured and a timeout request occurs.
•
When IEEE 802.1x port-based authentication is enabled on the switch, Extensible Authentication Protocol (EAP) notification packets from the supplicant are no longer discarded.
•
In environments using Layer 2 IP Network Admission Control (NAC), long downloadable ACLs (dACLs) with source or destination Layer 4 ports no longer cause unpredictable events in which all traffic is dropped and URL redirects are not enforced.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2
•
When the logging event-spanning-tree interface configuration command is configured and logging to the console is enabled, a topology change no longer generates a large number of logging messages.
•
The switch no longer unexpectedly reloads while configured with IEEE 802.1x authentication and the MAC authentication bypass feature.
•
When you enable detection of Cisco IP phones by entering the switchport voice detect cisco-phone interface configuration command, the interface is no longer disabled if you connect a third-party IP phone is connected to the interface.
Note
•
When you configure a port channel as trusted by entering the ip dhcp snooping trust interface configuration command, the configuration is no longer lost when the link goes from down to up.
•
This traceback error no longer appears when you enter the show aaa subscriber profile privileged EXEC command:
*Mar 2 01:50:41.127: %PARSER-3-BADSUBCMD: Unrecognized subcommand 10 in exec command'show aaa subscriber profile WORD'-Traceback= D003B4 D00AC8 C908A0 C2F040 C8CA18 CB8984 93B670 932338
Note
•
Enhanced IGRP (EIGRP) now works correctly when you enter the ip authentication key-chain eigrp interface configuration command.
•
A switch no longer unexpectedly reloads when you configure two or more authentication, authorization, and accounting (AAA) broadcast groups.
•
The switch no longer experiences a memory leak during an HTTP core process.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1
•
A router that is configured for HTTP and voice-based services no longer unexpectedly reloads due to memory corruption.
•
When AAA is enabled and you use the aaa group server radius group-name global configuration command to put the switch in server group configuration mode, entering the server-private command no longer causes the switch to reload.
•
The switch no longer reloads when you use the aaa authentication eou default group radius enable global configuration command to configure an EAP over UDP (EOU) method list.
•
A Cisco IOS device may crash while processing an SSL packet. This can happen during the termination of an SSL-based session. The offending packet is not malformed and is normally received as part of the packet exchange.
Cisco has released free software updates that address this vulnerability.
Aside from disabling affected services, there are no available workarounds to mitigate an exploit of this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-ssl.shtml.
•
High CPU usage (greater than 90 percent) no longer occurs on the switch when you first connect a new device.
•
A switch no longer unexpectedly reloads when you configure the switch ports as dynamic ports by using the VLAN Membership Policy Server (VMPS).
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE
•
The switch no longer returns an incorrect value for the ciscoFlashPartitionFileCount MIB.
•
Syslog messages are no longer generated when two or more IEEE 802.1x-capable hosts are connected through a hub and the port is in single-host mode.
•
When traffic passes through a VMPS port and you enter the shut interface configuration command, a dynamic VLAN is now assigned.
•
This error message no longer appears during authentication when a method list is used and one of the methods in the method list is removed:
AAA-3-BADMETHODERROR:Cannot process authentication method 218959117•
The switch no longer reloads when you use a Kron command scheduler routine to automatically copy configuration data using the Secure Copy Protocol (SCP). (Kron is a Cisco IOS utility for scheduling non-prompting CLI commands to execute at a later time.)
•
When IGMP snooping is enabled and an EtherChannel member interface fails, the switch no longer stops forwarding multicast traffic on the EtherChannel. In previous releases, this occurred when multicast routing was enabled and the EtherChannel interface was a member of a multicast group not directly connected (that is, the multicast group that did not have the C flag set in the show ip mroute privileged EXEC command output).
•
When a switch is connected to a third-party router through an EtherChannel and the EtherChannel is running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel no longer fail after you enter the switchport trunk native vlan vlan-id interface configuration command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.
•
When dynamic ARP inspection is enabled and IP validation is disabled, the switch no longer drops ARP requests that have a source address of 0.0.0.0. When you are enabling IP validation, use the allow zeros keyword to allow the 0.0.0.0 source address.
•
When MAC addresses are learned on an EtherChannel port, the addresses are now correctly deleted from the MAC address table.
•
When you configure an IP address on a switch virtual interface (SVI) with DCHP and enable DHCP snooping on the SVI VLAN, the switch SVI can now obtain an IP address.
•
When a VLAN includes multiple MAC addresses, the number of MAC addresses shown in SNMP now matches the output of the show mac-address count vlan vlan-id privileged EXEC command.
•
MAC flap-notification no longer occurs when a switch is running VLAN bridge spanning-tree protocol (STP) and fallback bridging is configured on the VLANs running STP.
•
Multiple Spanning-Tree Protocol (MSTP) convergence time has been improved for Cisco IOS Release 12.2.
•
Changing the spanning tree mode from MSTP to other spanning modes no longer causes tracebacks.
•
The TxBufferFullDropCount counter no longer increments when the switch is a standalone switch.
•
The Total- output-drops field in the show interfaces privileged EXEC command output now displays accurate ASIC drops.
•
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 now saved in the switch configuration.
•
A switch configured for Link Layer Discovery Protocol (LLDP) now correctly reports the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes.
Documentation Updates
This section contains these documentation updates:
•
•
Updates to the Software Configuration Guide
These are the updates to the software configuration guide:
•
When you globally enable BPDU guard on ports that are Port Fast-enabled (the ports are in a Port Fast-operational state), spanning tree shuts down Port Fast-enabled ports that receive BPDUs.
This is the correct information:
When you globally enable BPDU guard on ports that are Port Fast-enabled (the ports are in a Port Fast-operational state), spanning tree continues to run on the ports. They remain up unless they receive a BPDU.
•
After you have entered the eigrp stub router configuration command, only the eigrp stub connected summary command takes effect. Although the CLI help might show the receive-only and static keywords and you can enter these keywords, the switch always behaves as if the connected and summary keywords were configured.
Updates to the System Message Guide
These are the updates to the system message guide:
Error Message VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit.Explanation The system has shut down the specified interface because too many hosts have requested access to that interface. [chars] is the interface name.
Recommended Action To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command.
Error Message VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response.Explanation The VLAN membership policy server (VMPS) has specified a VLAN name that is unknown to the switch. [chars] is the VLAN name.
Recommended Action Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.
Error Message WCCP-5-CACHEFOUND: Web Cache [IP_address] acquired.Explanation The switch has acquired the specified web cache. [IP_address] is the web cache IP address.
Recommended Action No action is required.
Error Message WCCP-1-CACHELOST: Web Cache [IP_address] lost.Explanation The switch has lost contact with the specified web cache. [IP_address] is the web cache IP address.
Recommended Action Verify the operation of the web cache by entering the show ip wccp web-cache privileged EXEC command.
Updates to the Getting Started Guide
This illustration in the Cisco Catalyst Blade Switch 3040 for HP Getting Started Guide has been updated:
Figure 1 The Catalyst Blade Switch 3040 for HP
Switch module
Health LED
Release latch
SFP module port LEDs for ports 17 to 20
System status LEDs
SFP module ports 17 to 20
Mode button
Gigabit Ethernet ports LEDs for ports 17x to 24x
Console port
Gigabit Ethernet ports 17x to 24x
UID1 LED
1 UID: unit identifier.
Related Documentation
These documents provide complete information about the Cisco Catalyst Blade Switch 3020 for HP and are available at Cisco.com:
http://www.cisco.com/en/US/products/ps8743/tsd_products_support_series_home.html
These documents provide complete information about the Cisco Catalyst Blade Switch 3020 for HP:
•
•
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, 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, 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. (0903R)
Copyright © 2008-2009 Cisco Systems, Inc. All rights reserved.
