Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 15.0(2)SE and Later
Available Languages
Table of Contents
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 15.0(2)SE and Later
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
Caveats Resolved in Cisco IOS Release 15.0(2)SE12
Caveats Resolved in Cisco IOS Release 15.0(2)SE11
Caveats Resolved in Cisco IOS Release 15.0(2)SE10a
Caveats Resolved in Cisco IOS Release 15.0(2)SE10
Caveats Resolved in Cisco IOS Release 15.0(2)SE9
Caveats Resolved in Cisco IOS Release 15.0(2)SE8
Caveats Resolved in Cisco IOS Release 15.0(2)SE7
Caveats Resolved in Cisco IOS Release 15.0(2)SE6
Caveats Resolved in Cisco IOS Release 15.0(2)SE5
Caveats Resolved in Cisco IOS Release 15.0(2)SE4
Caveats Resolved in Cisco IOS Release 15.0(2)SE3
Caveats Resolved in Cisco IOS Release 15.0(2)SE1
Caveats Resolved in Cisco IOS Release 15.0(2)SE
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 15.0(2)SE and Later
These release notes include important information about Cisco IOS Release 15.0(2)SE 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 switch packaging.
- If your switch is on, use the show version privileged EXEC command. See the “Finding the Software Version and Feature Set” section.
- If you are upgrading to a new release, see the software upgrade filename for the software version. See the “Deciding Which Files to Use” section.
For the complete list of Cisco Catalyst Blade Switch 3020 for HP documentation, see the “Related Documentation” section.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm
Contents
- “System Requirements” section
- “Upgrading the Switch Software” section
- “Installation Notes” section
- “New Software Features” section
- “Limitations and Restrictions” section
- “Important Notes” section
- “Cisco Bug Search Tool” section
- “Open Caveats” section
- “Resolved Caveats” section
- “Related Documentation” section
- “Obtaining Documentation, Obtaining Support, and Security Guidelines” section
System Requirements
Upgrading the Switch Software
- “Finding the Software Version and Feature Set” section
- “Deciding Which Files to Use” section
- “Archiving Software Images” section
- “Upgrading a Switch by Using the Device Manager” section
- “Upgrading a Switch by Using the CLI” section
- “Recovering from a Software Failure” section
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
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 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(50)SE or later (the IP base image), you must first upgrade to Cisco IOS Release 12.2(40)SE2.
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/prod/collateral/iosswrel/ps8802/ps6969/ps1835/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/fundamentals/command/reference/cf_t1.html
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.
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 to identify the file that you want to download.
Step 2 Download the software image file:
a. If you are a registered customer, go to this URL and log in.
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm
b. Navigate to Switches > Blade Switches.
c. Navigate to your switch model.
d. Click IOS Software , then select the latest IOS release.
Download the image you identified in Step 1.
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:
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:
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:
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.
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 Features
- Support for OSPFv3 authentication with IPsec. You can now use the IPsec secure socket API to authenticate OSPF for IPv6 (OSPFv3) packets to ensure that the packets are not altered and resent to the switch. For more information, see the IPv6 Unicast Routing chapter of the software configuration guide on Cisco.com..
- Support for port security on Etherchannels. For more information, see the Configuring Port-Based Traffic Control chapter in the software configuration guide.
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.
Bootloader
- The bootloader label is incorrect and displays “CISCO DEVELOPMENT TEST VERSION.” However, the actual bootloader software is the correct version with the correct functionality.
There is no workaround. It does not impact functionality. (CSCta72141)
Configuration
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 Mp/s full duplex or 100 Mp/s 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 Mp/s 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)
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
- 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. (CSCsk65142)
- An internal switch port is down when one of these HP Flex 10-Gigabit Ethernet network interface cards (NICs) is up:
The workaround is to use the speed nonegotiate interface configuration command on the internal port. (CSCth94904)
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 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)
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
Multicasting
- 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)
– 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.
– 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)
Quality of Service (QoS)
- 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)
- A QoS service policy with a policy map containing more than 62 policers cannot be added to an interface by using the service-policy interface configuration command.
The workaround is to use policy maps with 62 or fewer policers. (CSCsc59418)
- If you configure a large number of input interface VLANs in a class map, a traceback message similar to this might appear:
SPAN and RSPAN
- 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)
- 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
- 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.
VLAN
- 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)
- When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is within the configured rate limit, the port might go into an error-disabled state.
The workaround is to configure the burst interval to more than 1 second. (CSCse06827)
- When many VLANs are configured on the switch, high CPU utilization occurs when many links are flapping at the same time.
The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are flapping. (CSCtl04815)
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)
Important Notes
Note Beginning with Cisco IOS Release 12.2(58)SE, the software configuration guide no longer includes a MIB appendix. To locate and download MIBs for a specific Cisco product and release, use the Cisco MIB Locator:
‘http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Cisco IOS Notes
- The behavior of the no logging on global configuration command changed in Cisco IOS Release 12.2(18)SE and later. You can only use the logging on and then the no logging console global configuration commands to disable logging to the console. (CSCec71490)
- In Cisco IOS Release 12.2(25)SEC, the implementation for multiple spanning tree (MST) changed from the previous release. Multiple STP (MSTP) complies with the IEEE 802.1s standard. Previous MSTP implementations were based on a draft of the IEEE 802.1s standard.
- 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:
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:
If 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
- We recommend this browser setting to more quickly 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 .
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.
- 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:
- 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.
Cisco Bug Search Tool
The Bug Search Tool (BST), which is the online successor to Bug Toolkit, is designed to improve the effectiveness in network risk management and device troubleshooting. The BST allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The tool has a provision to filter bugs based on credentials to provide external and internal bug views for the search input.
To view the details of a caveat listed in this document:
1. Access the BST (use your Cisco user ID and password) at https://tools.cisco.com/bugsearch/ .
Open Caveats
When you make port security changes on an interface, such as configuring aging time, violations, or aging type, error messages and tracebacks might appear.
When a switch or switch stack running Multiple Spanning Tree (MST) is connected to a switch running Rapid Spanning Tree Protocol (RSTP), the MST switch acts as the root bridge and runs per-VLAN spanning tree (PVST) simulation mode on boundary ports connected to the RST switch. If the allowed VLAN on all trunk ports connecting these switches is changed to a VLAN other than VLAN 1 and the root port of the RSTP switch is shut down and then enabled, the boundary ports connected to the root port move immediately to the forward state without going through the PVST+ slow transition.
Resolved Caveats
- Caveats Resolved in Cisco IOS Release 15.0(2)SE12
- Caveats Resolved in Cisco IOS Release 15.0(2)SE11
- Caveats Resolved in Cisco IOS Release 15.0(2)SE10a
- Caveats Resolved in Cisco IOS Release 15.0(2)SE10
- Caveats Resolved in Cisco IOS Release 15.0(2)SE9
- Caveats Resolved in Cisco IOS Release 15.0(2)SE8
- Caveats Resolved in Cisco IOS Release 15.0(2)SE7
- Caveats Resolved in Cisco IOS Release 15.0(2)SE6
- Caveats Resolved in Cisco IOS Release 15.0(2)SE5
- Caveats Resolved in Cisco IOS Release 15.0(2)SE4
- Caveats Resolved in Cisco IOS Release 15.0(2)SE3
- Caveats Resolved in Cisco IOS Release 15.0(2)SE1
- Caveats Resolved in Cisco IOS Release 15.0(2)SE
Caveats Resolved in Cisco IOS Release 15.0(2)SE12
Use the Bug Search Toolkit to view the details of a caveat listed in this section. For more information about the BST, go to https://tools.cisco.com/bugsearch/ .
Caveats Resolved in Cisco IOS Release 15.0(2)SE11
Use the Bug Search Toolkit to view the details of a caveat listed in this section. For more information about the BST, go to https://tools.cisco.com/bugsearch/ .
Caveats Resolved in Cisco IOS Release 15.0(2)SE10a
Use the Bug Search Toolkit to view the details of a caveat listed in this section. For more information about the BST, go to https://tools.cisco.com/bugsearch/ .
Caveats Resolved in Cisco IOS Release 15.0(2)SE10
Use the Bug Search Toolkit to view the details of a caveat listed in this section. For more information about the BST, go to https://tools.cisco.com/bugsearch/ .
Caveats Resolved in Cisco IOS Release 15.0(2)SE9
Use the Bug Search Toolkit to view the details of a caveat listed in this section. For more information about the BST, go to https://tools.cisco.com/bugsearch/
Caveats Resolved in Cisco IOS Release 15.0(2)SE8
Use the Bug Search Toolkit to view the details of a caveat listed in this section. For more information about the BST, go to https://tools.cisco.com/bugsearch/ .
Caveats Resolved in Cisco IOS Release 15.0(2)SE7
Designated port on the Root Bridge experiences a block forward for 30 seconds. This issue occurs because the message-time (the period of time a packet is alive in the network) is almost equal to max-age (the period of time a packet is allowed to stay in the network). When message-time >= max-age, the switch receives an agedMsg on the forwarding port which moves the port to a blocking state.
Link State Tracking (LST) fails after upgrade to Cisco IOS Release 15.0(2)SE6. The LST downstream interfaces flap continually while the upstream interfaces remain stable.
The workaround is to disable Link State Tracking on the switch. Alternatively, downgrade to Cisco IOS Release 15.0(2) SE5.
Due to a timing issue, the port channel member port on the slave switch of the stack loops during boot up. The issue occurs only on the member port that is configured as the first port in a cross-stack EtherChannel configuration and when Nexus devices are connected to Cisco devices. Due to Link Aggregation Control Protocol (LACP) graceful convergence, when both the devices are up and in sync (S) state, Cisco devices start transmitting even before the devices get onto collecting (C) state. This causes the port to be pulled down by the Nexus devices. When this happens during boot up, the EtherChannel hardware programming for the port is cleared even when the port is bundled in the port-channel.
The workaround is to enter the shutdown/no shutdown command on the port-channel interface or disable lacp graceful-convergence on the port-channel on peer devices.
An interface configured with no logging event link-status command, fails to change its state from disabled to enabled when you run the logging event link-status command along with the switchport command.
Caveats Resolved in Cisco IOS Release 15.0(2)SE6
When you upgrade a device to a Cisco IOS or Cisco IOS XE release that supports Type 4 passwords, enable secret passwords are stored using a Type 4 hash which can be more easily compromised than a Type 5 password.
The workaround is to configure the enable secret command on an IOS device without Type 4 support, copy the resulting Type 5 password, and paste it into the appropriate command on the upgraded IOS device.
The workaround is to use chassisTempAlarm object from CISCO-STACK-MIB to get the following values:
– off — when the temperature of the device is in normal range
– on — when the temperature of the device is too high
– critical — when the temperature of the device is critical due to which a system shut down is imminent.
When VTp mode is set to transparent and vlan.dat file present in flash is deleted, after reload, access vlan is not configured in the switch even though vlan configuration is present in running config or startup config.
The workaround is to set the vtp mode to server or client.
The internal port links between 3020 switches and blade servers do not work when you start the switch and the server with a specific power on and off sequence.
The workaround is to restart the switch.
In a network that consists of two DHCP clients with same client id and different mac addresses, the DHCP server reloads when one of the clients releases its DHCP address.
A switch configured with login quiet-mode resets when you enter the login block-for or no login block-for commands.
There is no workaround. To avoid a reset, do not enter the login block or no login block-for command.
Caveats Resolved in Cisco IOS Release 15.0(2)SE5
A memory leak is observed when configuring VLANs using tclsh mode.
The workaround is to make the tclsh mode interactive to avoid any memory leak.
When the privilege exec level 5 show mac address-table interface gigabitethernet privileged EXEC command is entered, all interfaces in the switch have the command applied to the running configuration.
CPU usage goes above 90% when Internet Group Management Protocol (IGMP) version 3 report packets are sent to the switch which has IGMP version 2 configured on the switch virtual interface.
The workaround is to either disable multicast fast convergence or configure IGMP version 3 on switch virtual interface.
Topology Change Notification (TCN) occurs over the network when a new stack member is added to the switch stack.
TACACS+ single connect authentication request from a switch stack takes around 10 to 12 minutes to failover to secondary server after the primary TACACS server is unreachable.
The workaround is to disable TACACS+ single connect configuration on the switch.
After rebooting a Cisco Catalyst Blade Switch 3012 (CBS3012), incorrect data is found in the vital product data (VPD) of the switch, which causes the switch to become unmanageable.
Switch runs out of memory within few seconds of configuring the command privilege exec level <n> show spanning-tree active/detail .
Caveats Resolved in Cisco IOS Release 15.0(2)SE4
Internal VLANs are displayed when the show snmp mib ifmib ifindex command is entered or the SNMP is queried for the ipMIB object.
The workaround is to check if the displayed VLANs are internal and then to hide them.
When the switch is started using TACACS+ configurations, the CPU utilization increases to 100% and the VTY device does not work.
The workaround is to remove the TACACS+ configurations and restart the switch.
The ipAddrEntry value in the IP Address Table shows an interface index that is not exposed by the ifEntry Object ID.
Caveats Resolved in Cisco IOS Release 15.0(2)SE3
CPU usage is high when an SNMP Walk of the Address Resolution Protocol (ARP) table is performed.
The workaround is to implement SNMP view using the following commands:
snmp-server view cutdown iso included
snmp-server view cutdown at excluded
snmp-server view cutdown ip.22 excluded
snmp-server community public view cutdown ro
snmp-server community private view cutdown rw
If an ACL is configured on a router VTY line for ingress traffic, the ACL is applied for egress traffic also. As a result, egress traffic to another router on an SSH connection is blocked.
The workaround is to permit egress traffic to the specific destination router using the permit tcp host <destination router IP address> eq 0 any interface configuration command.
Memory leak is seen in the switch when it sends CDP, LLDP or DHCP traffic and when the link flaps.
The workaround is to apply protocol filters to the device sensor output by entering the following global configuration commands:
device-sensor filter-spec dhcp exclude all
device-sensor filter-spec lldp exclude all
device-sensor filter-spec cdp exclude all
If the memory leak continues in the "DHCPD Receive" process, disable the built-in DHCP server by entering the no service dhcp global configuration command.
STP loop occurs on Flexstack connected by parallel links when a link state is changed on Flexlink port.
The workaround is to change the switch to root bridge.
When native VLAN is configured on the trunk or when switchport trunk native vlan 99 is configured on the interface, spanning-tree instance is not created for native VLAN.
The workaround is to keep VLAN1 as a native on the trunk. In Cisco IOS Release15.0(2) SE, dot1.x is enabled by default and causes authentication fail in the native VLAN. This results in pm_vp_statemachine not triggering any event to spanning tree. To disable dot1x internally, run the no macro auto monitor command. The stp instance is created for native vlan 99 after running the show and no show command on the interface.
When the secret password is configured, the password is not saved. The default password is used as the secret password.
The workaround is to use the default password to login and then change the password.
Caveats Resolved in Cisco IOS Release 15.0(2)SE1
When using SNMP v3, the switch unexpectedly reloads when it encounters the snmp_free_variable_element.
When two traps are generated by two separate processes, the switch fails if one process is suspended while the other process updates variables used by the first process.
The workaround is to disable all SNMP traps.
If a redundant power supply (RSP) switchover occurs during a bulk configuration synchronization, some of the line configurations might disappear.
The workaround is to reapply the line configurations.
The show ip dhcp pool command displays a large number of leased addresses.
The workaround is to turn off ip dhcp remember and reload the switch.
The following warning messages might be displayed during the boot process even when a RADIUS or a TACACS server have been defined:
The secure copy feature (copy: source-filename scp: destination-filename command) does not work.
Local web authorization and HTTP services on the switch do not respond because of a web authorization resource limitation in the system. The resource limitation is normally caused by incorrectly terminated HTTP or TCP sessions.
These are possible workarounds and are not guaranteed to solve the problem:
– Enter the ip admission max-login-attempts privileged EXEC command to increase the number of maximum login attempts allowed per user.
– If the web authorization module is intercepting HTTP sessions from web clients in an attempt to authorize them, try using a different browser.
– Eliminate background processes that use HTTP transport.
Heavy traffic load conditions may cause the loop guard protection function to be automatically activated and almost immediately deactivated. These conditions can be caused by entering the shutdown and no shutdown interface configuration commands or by interface link flaps on more than forty ports. These log messages appear:
%SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port GigabitEthernet1/0/1 on MST0.
%SPANTREE-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port GigabitEthernet1/0/1 on MST0.When a peer switch sends inferior Bridge Protocol Data Units (BPDUs) on the blocking port of the Cisco switch (with the proposal bit ON), the Cisco switch waits for three such BPDUs before responding with a better BPDU. This leads to a convergence time of more than 5 seconds. The problem appears under these conditions:
– The Cisco switch is not configured as the root switch.
– The Cisco switch uses Multiple Spanning-Tree Protocol (MSTP) and the peer switch uses Rapid Spanning Tree Protocol (RSTP) or rapid per-VLAN spanning-tree plus (rapid PVST+).
With switches running Cisco IOS Release 15.0(2)SE, there was a problem when port-based address allocation was configured. The DHCP client did not receive IP addresses from the server if the client ID was configured as an ASCII string or if the subscriber ID was used as the client ID.
This problem has been fixed now. No action is required.
When you configure and save the monitor session source interface, the configuration is not saved after reboot.
If an interface is configured with the switchport port-security maximum 1 vlan command, the following error message is displayed:
%PORT_SECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address XXXX.XXXX.XXXX on port <interface>The flash memory is corrupted when you format the flash manually.
The workaround is to reload the switch. (Note that this will erase the flash memory, and you will need to reload the software image using TFTP, a USB drive, or a serial cable.
If the Performance Monitor cache is displayed (using the show performance monitor cache command) and you attempt to stop the command output display by entering the q keyword, there is an unusually long delay before the output is stopped.
The workaround is to enter the term len 0 privileged EXEC command so that all command outputs are displayed without any breaks.
Caveats Resolved in Cisco IOS Release 15.0(2)SE
The archive download feature does not work if the flash contains an “update” directory. This situation is likely to occur if a previous download failed or was interrupted and the “update”" directory is still left in the flash.
The workaround is to delete the “update” directory in the flash before starting the archive download.
OSPFv3 neighbors might flap because of the way the switch handles IPv6 traffic destined for well-known IPv6 multicast addresses.
Users connecting to the network through a device configured for web proxy authentication may experience a web authentication failure.
There is no workaround. Use the clear tcp tcb command to release the HTTP Proxy Server process.
Using the dot1x default command on a port disables access control on the port and resets the values of the authentication host-mode and authentication timer reauthenticate commands to the default values.
The workaround is to avoid using the dot1x default command and set various dot1x parameters individually. You can also reconfigure the parameters that were changed after you entered the dot1x default command.
When using the switchport port-security maximum 1 vlan access command, if an IP-phone with a personal computer connected to it is connected to an access port with port security, a security violation will occur on the interface. This type of message is displayed on the console:
%PORT_SECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address XXXX.XXXX.XXXX on port FastEthernet0/1.Here is a sample configuration:
The workaround is to remove the line switchport port-security maximum 1 vlan access.
The switch does not correctly detect a loopback when the switch port on an authenticated IP phone is looped to a port configured and authenticated with dot1x security, even when bpduguard is configured on the interface. This situation can result in 100 percent CPU utilization and degraded switch performance.
The workaround is to configure the interface with the authentication open command or to configure authentication mac-move permit on the switch.
Related Documentation
User documentation in HTML format includes the latest documentation updates and might be more current than the complete book PDF available on Cisco.com.
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:
- Cisco Catalyst Blade Switch 3020 for HP Getting Started Guide
- Regulatory Compliance and Safety Information for the Cisco Catalyst Blade Switch 3020 for HP
- Cisco Catalyst Blade Switch 3020 for HP Software Configuration Guide
- Cisco Catalyst Blade Switch 3020 for HP Command Reference
- Cisco Catalyst Blade Switch 3020 for HP System Message Guide
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
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned 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. (1721R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)