Release Notes for the Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 15.0(2)SE and Later
Available Languages
Table of Contents
Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 15.0(2)SE and Later
Device Manager System Requirements
Cisco Network Assistant Compatibility
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
New in Cisco IOS Release 15.0(2)SE1
New in Cisco IOS Release 15.0(2)SE
Minimum Cisco IOS Release for Major Features
Cisco X2 Transceiver Modules and SFP Modules
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 and Submitting a Service Request
Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 15.0(2)SE and Later
Cisco IOS Release 15.0(2)SE and later runs on the Cisco Catalyst Blade Switch 3120 for HP switches. These switches support stacking through Cisco StackWise Plus technology. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
These release notes include important information about Cisco IOS Release 15.0(2)SE and later and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:
- If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
- If your switch is on, use the show version privileged EXEC command. See the “Finding the Software Version and Feature Set” section.
- If you are upgrading to a new release, see the software upgrade filename for the software version. See the “Deciding Which Files to Use” section.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm
For the complete list of the Cisco Catalyst Blade Switch 3120 for HP documentation, see the “Related Documentation” section.
Note References in this document to the CBS3120G-S and CBS3120X-S switches also apply to the CBS3125G-S and CBS3125X-S switches, respectively.
Contents
- System Requirements
- Upgrading the Switch Software
- Installation Notes
- New Software Features
- Minimum Cisco IOS Release for Major Features
- Limitations and Restrictions
- Important Notes
- Cisco Bug Search Tool
- Open Caveats
- Resolved Caveats
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
System Requirements
Hardware Supported
Table 1 Cisco Catalyst Blade Switch 3120 for HP Supported Hardware
- 18 internal Gigabit Ethernet 1000BASE-X downlink ports that connect to the blade enclosure.
- 4 Gigabit Ethernet (RJ-45) uplink ports
- 4 RJ-45 SFP module slots1/ 2 10-Gigabit Ethernet X2 module slots
- 1 Ethernet management port (Fa0) used only for switch module management traffic
SFP modules2
SFP-10G-SR
Only version 02 or later CX13 cables are supported:
Caution The Cisco Catalyst Blade Switch 3120 for HP switch modules do not support switch stacks with other types of blades switches as members. Combining the Cisco Catalyst Blade Switch 3120 for HP with other types of blade switches in a switch stack might cause the switch to work improperly or to fail.
Software Requirements
- Windows 2000, XP, Vista, and Windows Server 2003.
- Internet Explorer 6.0, 7.0, Firefox 1.5, 2.0 or later with JavaScript enabled.
The device manager verifies the browser version when starting a session and does not require a plug-in.
Cisco Network Assistant Compatibility
Cisco IOS Release 12.2(40)EX1 and later is only compatible with Cisco Network Assistant 5.3 and later. You can download Network Assistant from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
- Finding the Software Version and Feature Set
- Deciding Which Files to Use
- Upgrading a Switch by Using the Device Manager or Network Assistant
- Upgrading a Switch by Using the CLI
- Recovering from a Software Failure
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
Note Although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration (IP base feature set or IP services feature set) and does not change if you upgrade the software license.
You can also use the dir filesystem : privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Note To use the IPv6 routing and IPv6 ACL features on the Cisco Catalyst Blade Switch 3120 for HP, you must purchase the IP services software license from Cisco.
The universal software images support multiple feature sets. Use the software activation feature to deploy a software license and to enable a specific feature set. For information about software activation, see the Cisco Software Activation for HP document on Cisco.com:
http://www.cisco.com/en/US/products/ps6748/products_installation_and_configuration_guides_list.html
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release from which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/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 or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help .
Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
To download software, follow these steps:
Step 1 Use Table 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 , as described in the switch getting started guide.
- The CLI-based setup program, as described in the switch hardware installation guide.
- The DHCP-based autoconfiguration, as described in the switch software configuration guide.
- Manually assigning an IP address, as described in the switch software configuration guide.
New Software Features
New in Cisco IOS Release 15.0(2)SE
- 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. (Switches running the IP Base image)
- Support for IPv6 multicast. For more information, see the Implementing IPv6 Multicast chapter of the software configuration guide on Cisco.com.
Minimum Cisco IOS Release for Major Features
Table 4 lists the minimum software release (after the first release) required to support the major features of the Catalyst Blade Switch 3120 for HP. Features not listed are supported in all releases.
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
Access Control List
- The Cisco Catalyst 3120 for HP Blade Switch has 964 TCAM entries available for ACLs in the default and routing SDM templates instead of the 1024 entries that are available on the Catalyst 3560 and Catalyst 3750 switches.
There is no workaround. (CSCse33114)
- When a MAC access list is used to block packets from a specific source MAC address, that MAC address is entered in the switch MAC-address table.
The workaround is to block traffic from the specific MAC address by using the mac address-table static mac-addr vlan vlan-id drop global configuration command. (CSCse73823)
Address Resolution Protocol
- The switch might place a port in an error-disabled state due to an Address Resolution Protocol (ARP) rate limit exception even when the ARP traffic on the port is not exceeding the configured limit. This could happen when the burst interval setting is 1 second, the default.
The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem. (CSCse06827))
Cisco X2 Transceiver Modules and SFP Modules
- Cisco X2-10GB-LR transceiver modules with a version identification number lower than V03 might show intermittent frame check sequence (FCS) errors or be ejected from the switch during periods of operational shock greater than 50 g.
There is no workaround. (CSCse14048)
- Switches with the Cisco X2-10GB-LX4 transceiver modules with a version identification number before V03 might intermittently fail.
The workaround is to use Cisco X2-10GB-LX4 transceiver modules with a version identification number of V03 or later. (CSCsh60076)
- When switches are installed closely together and the uplink ports of adjacent switches are in use, you might have problems accessing the SFP module bale-clasp latch to remove the SFP module or the SFP cable (Ethernet or fiber).
– Allow space between the switches when installing them.
– In a switch stack, plan the SFP module and cable installation so that uplinks in adjacent stack members are not all in use.
– Use a long, small screwdriver to access the latch, and then remove the SFP module and cable. (CSCsd57938)
Configuration
- If a half-duplex port running at 10 Mb/s receives frames with Inter-Packet Gap (IPG) that do not conform to Ethernet specifications, the switch might stop sending packets.
There is no workaround. (CSCec74610)
- When an excessive number (more than 100 packets per second) of Address Resolution Protocol (ARP) packets are sent to a Network Admission Control (NAC) Layer 2 IP-configured member port, a switch might display a message similar to this:
PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 0, class 51, max_msg 128, total throttled 984323
-Traceback= 6625EC 5DB4C0 5DAA98 55CA80 A2F2E0 A268D8No workaround is necessary. Under normal conditions, the switch generates this notification when snooping the next ARP packet. (CSCse47548)
- When there is a VLAN with protected ports configured in fallback bridge group, packets might not be forwarded between the protected ports.
The workaround is to not configure VLANs with protected ports as part of a fallback bridge group. (CSCsg40322)
- When a switch port configuration is set at 10 Mb/s half duplex, sometimes the port does not send in one direction until the port traffic is stopped and then restarted. You can detect the condition by using the show controller ethernet-controller or the show interfaces privileged EXEC commands.
The workaround is to stop the traffic in the direction in which it is not being forwarded, and then restart it after 2 seconds. You can also use the shutdown interface configuration command followed by the no shutdown command on the interface. (CSCsh04301)
- When line rate traffic is passing through a dynamic port, and you enter the switchport access vlan dynamic interface configuration command for a range of ports, the VLANs might not be assigned correctly. One or more VLANs with a null ID appears in the MAC address table instead.
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port.(CSCsi26392)
- 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)
- 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)
EtherChannel
- In an EtherChannel running Link Aggregation Control Protocol (LACP), the ports might be put in the suspended or error-disabled state after a stack partitions or a member switch reloads. This occurs when
– The EtherChannel is a cross-stack EtherChannel with a switch stack at one or both ends.
– The switch stack partitions because a member reloads. The EtherChannel is divided between the two partitioned stacks, each with a stack master.
The EtherChannel ports are put in the suspended state because each partitioned stack sends LACP packets with different LACP Link Aggregation IDs (the system IDs are different). The ports that receive the packets detect the incompatibility and shut down some of the ports. Use one of these workarounds for ports in this error-disabled state:
– Enable the switch to recover from the error-disabled state.
– Enter the shutdown and the no shutdown interface configuration commands to enable the port.
The EtherChannel ports are put in the error-disabled state because the switches in the partitioned stacks send STP BPDUs. The switch or stack at the other end of the EtherChannel receiving the multiple BPDUs with different source MAC addresses detects an EtherChannel misconfiguration.
After the partitioned stacks merge, ports in the suspended state should automatically recover. (CSCse33842)
- When a switch stack is configured with a cross-stack EtherChannel, it might transmit duplicate packets across the EtherChannel when a physical port in the EtherChannel has a link-up or link-down event. This can occur for a few milliseconds while the switch stack adjusts the EtherChannel for the new set of active physical ports and can happen when the cross-stack EtherChannel is configured with either mode ON or LACP. This problem might not occur with all link-up or link-down events.
No workaround is necessary. The problem corrects itself after the link-up or link-down event. (CSCse75508)
- The switch might display tracebacks similar to this example when an EtherChannel interface port-channel type changes from Layer 2 to Layer 3 or the reverse:
15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1 (ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C 4CEB50 859DF4 A7BF28 A98260 882658 879A58HSRP
IEEE 802.1x Authentication
- If a supplicant using a Marvel Yukon network interface card (NIC) is connected to an IEEE 802.1x-authorized port in multihost mode, the extra MAC address of 0c00.0000.0000 appears in the MAC address table.
Use one of these workarounds (CSCsd90495):
– Configure the port for single-host mode to prevent the extra MAC address from appearing in the MAC address table.
– Replace the NIC with a new card.
- When MAC authentication bypass is configured to use Extensible Authentication Protocol (EAP) for authorization and critical authentication is configured to assign a critical port to an access VLAN:
– If the connected device is supposed to be unauthorized, the connected device might be authorized on the VLAN that is assigned to the critical port instead of to a guest VLAN.
– If the device is supposed to be authorized, it is authorized on the VLAN that is assigned to the critical port.
Use one of these workarounds (CSCse04534):
– Configure MAC authentication bypass to not use EAP.
– Define your network access profiles to not use MAC authentication bypass. For more information, see the Cisco Access Control Server (ACS) documentation.
- When IEEE 802.1x authentication with VLAN assignment is enabled, a CPUHOG message might appear if the switch is authenticating supplicants in a switch stack.
The workaround is not use the VLAN assignment option. (CSCse22791)
Multicasting
- Multicast packets with a time-to-live (TTL) value of 0 or 1 are flooded in the incoming VLAN when all of these conditions are met:
– Multicast routing is enabled in the VLAN.
– The source IP address of the packet belongs to the directly connected network.
– The TTL value is either 0 or 1.
The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)
- Multicast packets denied by the multicast boundary access list are flooded in the incoming VLAN when all of these conditions are met:
– Multicast routing is enabled in the VLAN.
– The source IP address of the multicast packet belongs to a directly connected network.
– The packet is denied by the IP multicast boundary access-list configured on the VLAN.
There is no workaround. (CSCei08359)
- Reverse path forwarding (RPF) failed multicast traffic might cause a flood of Protocol Independent Multicast (PIM) messages in the VLAN when a packet source IP address is not reachable.
The workaround is to not send RPF-failed multicast traffic, or make sure that the source IP address of the RPF-failed packet is reachable. (CSCsd28944)
- If the clear ip mroute privileged EXEC command is used when multicast packets are present, it might cause temporary flooding of incoming multicast traffic in the VLAN.
There is no workaround. (CSCsd45753)
- When you configure the ip igmp max-groups number and ip igmp max-groups action replace interface configuration commands and the number of reports exceed the configured max-groups value, the number of groups might temporarily exceed the configured max-groups value.
No workaround is necessary because the problem corrects itself when the rate or number of IGMP reports are reduced. (CSCse27757)
- When you configure the IGMP snooping throttle limit by using the ip igmp max-groups number interface configuration on a port-channel interface, the groups learned on the port-channel might exceed the configured throttle limit number when all of these conditions are true:
– The port-channel is configured with member ports across different switches in the stack.
– One of the member switches reloads.
– The member switch that is reloading has a high rate of IP IGMP joins arriving on the port-channel member port.
The workaround is to disable the IGMP snooping throttle limit by using the no ip igmp max-groups number interface configuration command and then to reconfigure the same limit again. (CSCse39909)
Quality of Service (QoS)
- When QoS is enabled and the egress port receives pause frames at the line rate, the port cannot send packets.
There is no workaround. (CSCeh18677)
There is no workaround. (CSCsc63334)
- In a hierarchical policy map, if the VLAN-level policy map is attached to a VLAN interface and the name of the interface-level policy map is the same as that for another VLAN-level policy map, the switch rejects the configuration, and the VLAN-level policy map is removed from the interface.
The workaround is to use a different name for the interface-level policy map. (CSCsd84001)
- If the ingress queue has low buffer settings and the switch sends multiple data streams of system jumbo MTU frames at the same time at the line rate, the frames are dropped at the ingress.
There is no workaround. (CSCsd72001)
- When you use the srr-queue bandwidth limit interface configuration command to limit port bandwidth, packets that are less than 256 bytes can cause inaccurate port bandwidth readings. The accuracy is improved when the packet size is greater than 512 bytes. There is no workaround. (CSCsg79627)
- If QoS is enabled on a switch and the switch has a high volume of incoming packets with a maximum transmission unit (MTU) size greater than 1512 bytes, the switch might reload.
– Use the default buffer size.
– Use the mls qos queue-set output qset-id buffers allocation1 ... allocation4 global configuration command to allocate the buffer size. The buffer space for each queue must be at least 10 percent. (CSCsx69718)
- If you configure a large number of input interface VLANs in a class map, a traceback message similar to this might appear:
RADIUS
RADIUS change of authorization (COA) reauthorization is not supported on the critical auth VLAN.
Routing
- The switch stack might reload if the switch runs with this configuration for several hours, depleting the switch memory and causing the switch to fail:
– The switch has 400 Open Shortest Path First (OSPF) neighbors.
– The switch has thousands of OSPF routes.
The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)
- When the PBR is enabled and QoS is enabled with DSCP settings, the CPU utilization might be high if traffic is sent to unknown destinations.
The workaround is to not send traffic to unknown destinations. (CSCse97660)
SPAN and RSPAN
- When egress SPAN is running on a 10-Gigabit Ethernet port, only about 12 percent of the egress traffic is monitored.
There is no workaround. This is a hardware limitation. (CSCei10129)
The workaround is to configure aggressive UDLD. (CSCsh70244).
Stacking
- When using the logging console global configuration command, low-level messages appear on both the stack master and the stack member consoles.
The workaround is to use the logging monitor global configuration command to set the severity level to block the low-level messages on the stack member consoles. (CSCsd79037)
- If a new member switch joins a switch stack within 30 seconds of a command to copy the switch configuration to the running configuration of the stack master, the new member might not get the latest running configuration and might not operate properly.
The workaround is to reboot the new member switch. Use the remote command all show run privileged EXEC command to compare the running configurations of the stack members. (CSCsf31301)
- When the flash memory of a stack member is almost full, it might take longer to start up than other member switches. This might cause that switch to miss the stack-master election window. As a result, the switch might fail to become the stack master even though it has the highest priority.
The workaround is to delete files in the flash memory to create more free space. (CSCsg30073)
- The error message %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND might appear for a switch stack under these conditions:
– A supplicant is authenticated on at least one port.
– A new member joins a switch stack.
You can use one of these workarounds:
– Enter the shutdown and the no shutdown interface configuration commands to reset the port.
– Remove and reconfigure the VLAN. (CSCsi26444)
- When you use the switch renumber global configuration command to renumber a member switch in a switch stack and then reload the switch, the internal server-facing ports do not have the required default of spanning-tree portfast enabled.
The workaround is to apply the switch provision configuration before you reboot the switch. Enter both the switch current-stack-member-number renumber new-stack-member-number and the switch stack-member-number provision type global configuration commands, and reload the switch. (CSCsl63862)
- If you enter the show tech-support privileged EXEC command after you enter the remote command { all | stack-member-number } privileged EXEC command, the complete output does not appear.
The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090)
VLANs
- When the domain is authorized in the guest VLAN on a member switch port without link loss and an Extensible Authentication Protocol over LAN (EAPOL) is sent to an IEEE 802.1x supplicant to authenticate, the authentication fails. This problem happens intermittently with certain stacking configurations and only occurs on the member switches.
The workaround is to enter the shut and no shut interface configuration commands on the port to reset the authentication status. (CSCsf98557)
- 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)
- If you launch the device manager from a Firefox web browser, an invalid certificate alert appears. If you launch the device manager from an Internet Explorer 7.0 browser, a certificate error appears.
The workaround when using Firefox is to either temporarily or permanently accept the certificate. If you temporarily accept the certificate, close and then reopen the Firefox browser window. If you permanently accept the certificate, delete the certificate, and then close and restart Firefox:
– If you are using Firefox version 1.5, choose Tools > Options > Advanced > Security > View Certificates > Web Sites , select the certificate, and click Delete .
– If you are using Firefox version 2.0, choose Tools > Options > Advanced > Encryption > View Certificates > Web Sites , select the certificate, and click Delete .
The workaround when using Internet Explorer is to click Click here for Options in the warning message, and click Display Blocked Content . Close the browser window, and launch a new session. (CSCsk80229)
Important Notes
Cisco IOS Notes
- 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)EX1 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 interfaces with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.
Device Manager Notes
- You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the CLI or Cisco Network Assistant.
- We recommend this browser setting to reduce the time needed to display the device manager from Microsoft Internet Explorer.
From Microsoft Internet Explorer:
1. Choose Tools > Internet Options .
2. Click Settings in the “Temporary Internet files” area.
3. From the Settings window, choose Automatically .
5. Click OK to exit the Internet Options window.
- The HTTP server interface must be enabled to display the device manager. By default, the HTTP server is enabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
- The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the address (for example, www . cisco.com:84 ), you must enter http:// as the URL prefix. Otherwise, you cannot launch the device manager.
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
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
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.
LSG Downlink port flaps when SFP+ is used as an uplink port. This issue also appears if SFP+ is configured in a flexlink configuration.
There is no workaround. The configuration recovers automatically.
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.
The show switch chassis management command incorrectly displays all slot numbers as 0.
When the master switch (Switch A) is reloaded or loses power and rejoins the stack as a member switch, any traffic stream that exits Switch A is dropped because the newly joined member is not able to establish an Address Resolution Protocol (ARP) entry for the next hop router or switch. Debugs confirm that Switch A does not send a GARP or ARP for the next hop, though traffic continues to be sent to the switch.
The workaround is to add a static ARP. Ping the destination from Switch A to force the ARP to respond.
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
After upgrading to Cisco IOS Release 12.2(58)SE1, the Fa0 port on the switch does not respond to the ping command.
The workaround is to use Cisco IOS Release 12.2(55)SE.
When an interface is configured with the mls qos command, traffic is not matched by port-based QoS ACLs that use the range option.
The workaround is to is to configure the switch using the single port eq keyword. Alternatively, you can configure the trust under class-default setting for the same policy-map that uses the acl-range option.
In a switch stack, you cannot establish a console session with a member switch when an ACL is applied to the VTY lines.
The workaround is to use the following procedure when you apply an ACL to line vty 0 4 and line vty 5 15:
1. Create the vty ACL and permit the 127 network.
2. Append the vrf-also keyword to the configured access-class inbound.
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.
When a device is moved from one port to another in a switch stack, the SNMP data generated for the move event is incorrect.
The workaround is to ensure that the uplink to the core network is configured on the master switch (for example, a 1/0/x port).
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.
If a new port is added to an etherchannel on a switch using DAI or IPDT, ARP packets that ingress the port are lost.
The workaround is to save the configuration and reload the switch. Alternatively, configure the switch by entering the no macro auto monitor command followed by the macro auto monitor command after the port is bundled for the first time.
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 3120 for HP Blade Switch and are available from this Cisco.com site:
http://www.cisco.com/en/US/products/ps6748/tsd_products_support_series_home.html
- Cisco Catalyst Blade Switch 3000 Series for HP Getting Started Guide
- Regulatory Compliance and Safety Information for the Cisco Catalyst Blade Switch 3000 Series for HP
- Release Notes for the Cisco Catalyst Blade Switch 3120 for HP
Note Before you install, configure, or upgrade the switch module, see the release notes on Cisco.com for the latest information.
- Cisco Catalyst Blade Switch 3120 for HP Software Configuration Guide
- Cisco Catalyst Blade Switch 3120 for HP Command Reference
- Cisco Catalyst Blade Switch 3120 for HP System Message Guide
- Cisco Software Activation Document for HP
- These compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
– Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix
– Cisco Small Form-Factor Pluggable Modules Compatibility Matrix
– Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules
For other information about related products, see these documents on Cisco.com:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
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)
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)