Table Of Contents
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Caveats Resolved in Cisco IOS Release 12.2(55)SE5
Caveats Resolved in Cisco IOS Release 12.2(55)SE4
Caveats Resolved in Cisco IOS Release 12.2(55)SE3
Caveats Resolved in Cisco IOS Release 12.2(55)SE2 and Earlier
Updates to the Software Configuration Guide
Updates to the System Message Guide
Updates to the Getting Started Guide
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(55)SE and Later
Revised March 28, 2012
Cisco IOS Release 12.2(55)SE runs on the Cisco Catalyst Blade Switch 3020 for HP, referred to as the switch. 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.
These release notes include important information about Cisco IOS Release 12.2(55)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.
•
•
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/web/download/index.html
Contents
•
•
•
•
•
•
•
System Requirements
•
Hardware Supported
Table 1 Supported Hardware
Device Manager System Requirements
•
•
Hardware Requirements
Table 2 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1 GB DRAM.
Software Requirements
These are the supported operating systems and browsers for the device manager:
•
•
The device manager verifies the browser version when starting a session, and it does not require a plug-in.
Upgrading the Switch Software
•
•
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Note
Table 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:
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 at this URL:
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
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
To download software, follow these steps:
Step 1
Step 2
a.
http://www.cisco.com/cisco/web/download/index.html
b.
c.
d.
Download the image you identified in Step 1.
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/image-name.tarYou can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
Recovering from a Software Failure
For additional recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
New Software Features
•
•
•
•
•
•
•
•
•
•
•
•
MAC replace can be configured so that when a host disconnects from a port without ending its session, the session can be ended and the authentication sequence reset when a new MAC address connects to the port.
•
•
•
Use the dot1x supplicant controlled transient global configuration command to control access to the supplicant port during authentication. Use the no form of this command to provide access to the supplicant port during the authentication period
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.
•
•
Cisco IOS Limitations
•
Configuration
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
The workaround is to configure the port for 10 Mp/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•
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)
Ethernet
•
If this happens, traffic distribution is uneven on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
–
–
–
–
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal. (CSCeh81991)
IP
•
IP Telephony
•
Multicasting
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•
–
–
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
•
Use one of these workarounds:
–
–
Quality of Service (QoS)
•
•
•
The workaround is to use policy maps with 62 or fewer policers. (CSCsc59418)
•
01:01:32: %BIT-4-OUTOFRANGE: bit 1321 is not in the expected range of 0 to 1024There is no impact to switch functionality.
There is no workaround. (CSCtg32101)
SPAN and RSPAN
•
•
•
Trunking
•
•
•
VLAN
•
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•
Device Manager Limitations
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
•
There is no workaround (CSCsd98457).
Caveats
The following limitations are reported as caveats:
•
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.
Important Notes
•
Cisco IOS Notes
•
•
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.
•
If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)SE (or later), when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message:
AutoQoS Error: ciscophone input service policy was not properly appliedpolicy map AutoQoS-Police-CiscoPhone not configuredIf this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.
Device Manager Notes
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
•
Open Caveats
Device Manager
•
The chassis ID for the CBS3020 does not appear in the Device Manager window.
There is no workaround.
Cisco IOS
•
When you use the device manager, the dashboard does not display the switch chassis ID.
There is no workaround.
•
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.
•
If the Dynamic Trunking Protocol (DTP) is set to speed nonegotiate for two switches that interface each other, and the speed/duplex is configured as full/1000, the speed/duplex configuration of one of the switches changes to auto/auto when the switch is restarted. The port channel becomes incompatible and the second switch's operation is suspended. This problem applies only to the 1000BASE-LX interface.
The workaround is to enter the shutdown interface configuration command followed by the no shutdown command.
•
A port that is programatically configured with auth-default ACL does not allow any traffic on the switch except DHCP traffic. If the configurations on the interface are cleared and the interface is restarted, the auth-default ACL configuration remains and the problem persists.
There is no workaround.
Resolved Caveats
•
•
•
•
Caveats Resolved in Cisco IOS Release 12.2(55)SE5
•
During a Telnet session, the router crashes when the TACACS+ server is configured or unconfigured (tacacs-server host command) using the single-connection keyword.
The workaround is to not use the single-connection keyword.
•
When you enter the show running-config interface configuration command, IP Service Level Agreement notifications are shown as enabled even when you have not enabled this configuration using the ip sla enable reaction-alerts interface configuration command.
There is no workaround.
•
If local proxy Address Resolution Protocol (ARP) is configured on the VLAN interface, the ARP entry for the Hot Standby Router Protocol (HSRP) enters into an incomplete state.
The workaround is to remove the proxy ARP feature on the VLAN interface (by using the no ip local-proxy-arp interface configuration command) and restart the interface.
•
When AAA authorization is used with TACACS+, an error is displayed if the banner message (banner exec global configuration command) starts with a blank character.
The workaround is to not start the banner message with a blank character.
•
If the no vtp VLAN configuration command is used on a port that receives VTP updates, the switch does not process Layer 2 control traffic (STP and CDP) after some time.
The workaround is to configure VTP on the port or to not use the no vtp command.
•
The switch fails when LLDP data units with Type Length Value (TLV) of more than 10 management addresses (MA) are received.
The workaround is to disable the sending of LLDP MA TLVs on peer hosts.
•
When you enter the default interface, switchport, or no switchport interface configuration command on the switch, this message appears:
EMAC phy access error, port 0, retrying......There is no workaround.
•
CPU usage is high when a device connected to the switch is accessed using the https://IP_address command on the router.
The workaround is to reload the device.
•
The switch crashes when DCHP snooping is enabled with value 125 and an offer packet is received.
There is no workaround.
•
If a Tcl policy is copied to the router, the router fails when an event manager policy is configured.
There is no workaround.
•
If a CLI configuration text file is copied from a Windows system to the switch, a space is appended to the end of the macro description command when the file is read from the flash of the switch. This leads to errors resulting in high CPU utilization on the switch. Another possible issue is that the macro is not removed when the link goes down or the connected device is removed from the switch.
The workaround is to copy the configuration file from a non-Windows system (like UNIX or Linux) or convert the file to an appropriate UNIX format before copying.
•
A vulnerability in the Multicast Source Discovery Protocol (MSDP) implementation of Cisco IOS Software and Cisco IOS XE Software could allow a remote, unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition.
Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available. This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-msdp
•
A vulnerability exists in the Cisco IOS Software that may allow a remote application or device to exceed its authorization level when authentication, authorization, and accounting (AAA) authorization is used. This vulnerability requires that the HTTP or HTTPS server is enabled on the Cisco IOS device.
Products that are not running Cisco IOS Software are not vulnerable.
Cisco has released free software updates that address these vulnerabilities.
The HTTP server may be disabled as a workaround for the vulnerability described in this advisory.
This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-pai
•
The switch crashes due to the "HACL Acl Manager" memory fragmentation when a large access control list (ACL) is modified.
The workaround is add or remove ACE entries in sequential order when the ACL is modified.
•
Routing Information Protocol (RIP) Version 2 packets egressing an 801.1Q tunnel interface are triplicated.
There is no workaround.
•
Cisco IOS Software contains a vulnerability in the Smart Install feature that could allow an unauthenticated, remote attacker to cause a reload of an affected device if the Smart Install feature is enabled. The vulnerability is triggered when an affected device processes a malformed Smart Install message on TCP port 4786.
Cisco has released free software updates that address this vulnerability. There are no workarounds to mitigate this vulnerability.
This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/
cisco-sa-20120328-smartinstall•
If a client switch is authorized using MAC Authentication Bypass (MAB), and then by using the 802.1x standard and dynamic VLAN assignment, the MAC address of the switch is not updated in the MAC address table of slave switches.
The workaround is to not use both the 802.1x and dynamic VLAN assignment configurations for the client switch.
•
The switch crashes when an IP phone that uses LLDP and authenticates itself using MAC Authentication Bypass (MAB) or 802.1x is physically disconnected and reconnected to the switch port.
The workaround is to remove the aaa authorization network default group SG-PBA global configuration command.
Caveats Resolved in Cisco IOS Release 12.2(55)SE4
•
The Dynamic Host Configuration Protocol (DHCP) CLI does not accept white spaces in raw ASCII option in the DHCP pool configuration submode. This issue is seen in Cisco IOS Release 12.4(24)T1 and later.
There is no workaround.
•
In a VPN Routing and Forwarding (VRF) aware setup, messages are not sent to the syslog server. This issue applies to Cisco IOS Release 12.2(53)SE and 12.2(53)SE1. This situation does not occur if system logging is configured in the global table.
This problem has been corrected.
•
When two traps are generated by two separate processes, the switch fails if one process is suspended while the other process updates some variables used by the first process.
The workaround is to disable all SNMP traps.
•
A memory leak occurs in the SSH process, and user authentication is required.
The workaround is to allow SSH connections only from trusted hosts.
•
If a tunnel interface is configured with Cisco Discovery Protocol (CDP), the switch fails when it receives a CDP packet.
The workaround is to disable CDP on the interface by using the no cdp enable interface configuration command.
•
The switch fails when the Differentiated Services Code Point (DSCP) mutation name is longer than 25 characters.
The workaround is to configure DSCP mutation names with fewer than 25 characters.
•
On a switch running Protocol-Independent Multicast (PIM) and Source Specific Multicast (SSM), multicast traffic might not be sent to the correct port after the switch reloads.
The workaround is to enter the clear ip route privileged EXEC command or reconfigure PIM and SSM after a reload.
•
If Auto Smartports macros are configured, access points with the AIR-CAP prefix are not detected.
The workaround is to manually configure the access point port.
•
Neighbor discovery fails for IPv6 hosts connected to the switch when the IPv6 MLD snooping feature is enabled globally on the switch.
The workaround is to disable IPv6 MLD snooping on the switch.
•
The switch sometimes reloads after a CPU overload, regardless of the process that is overloading the CPU.
This problem has been corrected.
•
If a switch stack is configured with the stack-mac persistent timer value interface configuration command, the switch virtual interface (SVI) should remain in shutdown mode during a switchover. In this case, the SVI is in up mode.
The workaround is to specify the timer value to be long enough so that the stack's MAC address is not changed.
•
If a member switch does not have an access control list (ACL) and is running an Enforcement Policy Module (EPM) session, the client on that interface is re-authorized each time that the switch reloads.
The workaround is to configure an ACL on the interface.
•
The switch fails when DHCP snooping is configured and packet data traffic is excessive. The traffic exhausts the I/O memory and triggers the switch to crash.
There is no workaround.
Caveats Resolved in Cisco IOS Release 12.2(55)SE3
•
When ports in an EtherChannel are linking up, the message
EC-5-CANNOT_BUNDLE2might appear. This condition is often self-correcting, indicated by the appearance ofEC-5-COMPATIBLEmessage following the first message. On occasion, the issue does not self-correct, and the ports may remain unbundled.The workaround is to reload the switch or to restore the EtherChannel bundle by shutting down and then enabling the member ports and the EtherChannel in this order:
–
–
–
–
There is no workaround.
•
The switch stack log displays an error message about the redundant power supply (RPS). No RPS is actually present and the switch is instead powered by the blade chassis.
There is no workaround.
•
The switch LEDs freeze or behave erratically. The problem occurs with bootloader version 12.2(44)SE5.
There is no workaround.
•
For changes in temperature, the command line interface shows the updated temperature but the Simple Network Management Protocol (SNMP) always shows the temperature as "1 degree Celsius".
There is no workaround.
•
When the show spanning-tree vlan VLAN interface fastethernet 0 command is entered, the switch restarts.
The FastEthernet 0 interface is a management interface that does not run Spanning Tree Protocol (STP). Do not run show spanning-tree commands for management interfaces.
•
The switch sends out temperature traps when the temperature is between 58 and 60 degrees Celsius.
There is no workaround.
•
The show env stack command displays RPS status as "RPS NOT PRESENT". This could confuse the customer because Blade switches do not support RPS.
The workaround is to use the remote command all show env all command to display environment information.
•
When a member switch port security is used with port-based dot1x authentication and the switch MAC address is sticky, a connected device authenticates itself. Its MAC address is added as sticky in the switch configuration and in the port security tables of the stack switches. When the switch is shut down, the device MAC address is removed from the master switch, but it is retained in the member switch security tables. When the interface is re-enabled, the device MAC address is restored to the master switch configuration.
The workaround is to use port security without dot1x authentication.
Caveats Resolved in Cisco IOS Release 12.2(55)SE2 and Earlier
•
The buffer space of a switch running TCP applications is full while the TCP sessions are in the TIME_WAIT state. Buffer space becomes available after the TCP session the closed.
There is no workaround.
•
On switches running Cisco IOS Release 12.2(35)SE or later, connectivity issues might occur with these messages:
%SUPQ-4-CPUHB_RECV_STARVE: Still seeing receive queue stuck after throttlingThere is no workaround.
•
On a switch running Cisco IOS Release 12.2(46)SE, the output of the show interfaces privileged EXEC command shows 0 packets for port channel input and output rates.
The workaround is to reload the switch by entering the reload privileged EXEC command.
•
When a switch is low on memory (less than 256 MB), it can reload and display a SYS-2-WATCHDOG error.
There is no workaround. Enter the show memory debug leak privileged EXEC command to check for signs of a memory leak and address these symptoms.
•
On switches running Cisco IOS Release 12.2(50)SE3 running MAC authentication bypass with multidomain authentication (MDA), IP phones connected to a port might not be able to regain network connectivity in the VOICE domain if the session times out and all RADIUS servers are unreachable.
There is no workaround.
•
Switches running Cisco IOS Release 12.2(52)SE might reload after you enter the no mac address-table static mac-address vlan vlan-id interface interface-id global configuration command if the interface is up and the MAC address was dynamically learned before it was changed to static.
Use one of these workarounds:
–
Switch(config)# no mac address-table learning vlan vlan_idSwitch(config)# clear mac-address-table dynamic address mac_addressSwitch(config)# mac address-table static mac_address vlan vlan_id interface interface_idSwitch(config)# mac address-table learning vlan vlan_id–
–
•
A switch that has at least one trunk port configured might fail when you configure more than 950 VLANS by using the vlan vlan-id global configuration command.
There is no workaround.
•
When a port that is configured for Switched Port Analyzer (SPAN) goes up and down, a memory leak occurs in the `hpm main' process.
There is no workaround.
•
A vulnerability in the Internet Group Management Protocol (IGMP) version 3 implementation of Cisco IOS Software and Cisco IOS XE Software allows a remote unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition. Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100922-igmp.shtml.
Note: The September 22, 2010, Cisco IOS Software Security Advisory bundled publication includes six Cisco Security Advisories. Five of the advisories address vulnerabilities in Cisco IOS Software, and one advisory addresses vulnerabilities in Cisco Unified Communications Manager. Each advisory lists the releases that correct the vulnerability or vulnerabilities detailed in the advisory. The table at the following URL lists releases that correct all Cisco IOS Software vulnerabilities that have been published on September 22, 2010, or earlier:
http://www.cisco.com/warp/public/707/cisco-sa-20100922-bundle.shtml
Individual publication links are in "Cisco Event Response: Semiannual Cisco IOS Software Security Advisory Bundled Publication" at the following link:
http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_sep10.html
•
After a software upgrade from Cisco IOS Release 12.2(52)SE to Cisco IOS Release 12.2(53)SE, EIGRP hello packets are flooded on access ports belonging to another subnet. The same result occurs when you initiate ping requests to the broadcast address of other subnets. This results in Not on common subnet errors on the other side of the link.
The workaround is to downgrade to 12.2(52)SE
•
When two blade switches in a blade server are running Cisco IOS release 12.2(53)SE, with no stack cable connection between them, if you enter the no shutdown interface command on gigabitethernet ports 1/0/17 and 1/0/18, the output of the show running-config or show interface privileged EXEC command shows the ports to be down.
The workaround is to downgrade the software to Cisco IOS Release 12.2(52)SE.
•
After you apply an ACL, these messages appear:
%IPACCESS-4-INVALIDACL: Invalid ACL field: Acl number is 0%IPACCESS-4-INVALIDACL: Invalid ACL field: Acl type is 145There is no workaround.
•
A switch can report abnormal temperatures even though the output of the show environment all user EXEC or privileged EXEC command shows that the temperatures are within acceptable limits.
This is an example of the system messages:
Dec 25 19:03:57.463 AEST: %PLATFORM_ENV-1-TEMP: Abnormal temperature detected
Jan 2 04:04:46.600 AEST: %PLATFORM_ENV-1-TEMP: Abnormal temperature detected
Jan 7 06:33:36.067 AEST: %PLATFORM_ENV-1-TEMP: Abnormal temperature detectedThis is an example of the output of the show environment all command:
switch#show environment all
TEMPERATURE is OK
Temperature Value: 39 Degree Celsius
Temperature State: GREEN
Yellow Threshold : 80 Degree Celsius
Red Threshold : 90 Degree CelsiusThere is no workaround.
•
If the RADIUS authentication server is unavailable and inaccessible authentication bypass is enabled, the switch grants the client access to the network by putting the connected port in the critical-authentication state in the RADIUS-configured or the user-specified access VLAN. After the server is available, the client is not reinitialized and moved out of the critical VLAN.
There is no workaround.
•
A PC in 802.1x or multidomain authentication (MDA) mode is connected to an IP phone and connected to a MDA-enabled switch port. After the PC and phone are authenticated on the port, the PC is down. The port does not automatically reauthenticate the PC.
There is no workaround.
•
A switch running Cisco IOS Release 12.2(53)SE1 stops when IEEE 802.1x authentication is enabled.
The workaround is to apply a VLAN that the RADIUS server assigned to the switch.
•
Multidomain authentication (MDA) with guest VLAN or MAC authentication bypass (MAB) as a fallback method is enabled on a switch running Cisco IOS Release 12.2(53)SE. When a non-802.1x client is connected to a IP phone and the phone connected to a switch port shuts down and then restarts, the client MAC address status is drop in the MAC address table. It takes 5 minutes for the client to access the network.
The workaround is to use another software release, such as Cisco IOS Release 12.2(44)SE2.
•
This error message is displayed after copying a configuration file to the running configuration file fails:
%Error opening system:/running-config (No such file or directory)The output of the dir system:/ EXEC command also does not show a running configuration file.
The workaround is to reload the switch.
•
After you upgrade the switch software to Cisco IOS Release 12.2(55)SE, enhanced auto-QoS commands are generated when
–
and
–
If the mls qos command was already enabled on the switch, enhanced auto-QoS commands are generated only when you configure one of these commands:
–
–
–
Cisco IOS Release 12.2(55)SE supports implicit and explicit migration to enhanced auto-QoS configurations.
Implicit migration to enhanced auto-QoS occurs on a switch running legacy auto-QoS when you configure the auto qos video, auto qos trust, or auto qos classify command on an interface. Global and interface configurations on the switch migrate to the enhanced video or trust auto-QoS configurations.
Explicit migration to enhanced auto-QoS occurs on a switch when you enable the auto qos srnd4 global configuration command. You can configure the [no] form of this commandafter you remove auto-QoS functionality from all switch interfaces.
•
When you disconnect the spanning tree protocol (STP) peer link, the STP port path cost configuration changes.
There is no workaround.
•
If a static MAC address entry is configured for an IP address in the global routing table, ping requests are sent through the global context, and replies are sent through Virtual Routing and Forwarding (VRF). This is a VRF leak.
The workaround is to remove the static MAC address entry.
Documentation Updates
•
•
•
Updates to the Software Configuration Guide
In the "Configuring RIP for IPv6" section in the "Configuring IPv6 Unicast Routing" chapter, the task table is incorrect. This is the correct table:
Updates to the System Message Guide
New System Messages
Error Message AUTHMGR-5-SECURITY_VIOLATION: Security violation on the interface [chars], new MAC address ([enet) is seen. AuditSessionID [chars]Explanation A host on the interface attempted to gain access to the network or attempted an authentication. The interface mode does not support the number of hosts that are attached to the interface. This is a security violation, and the interface has been error-disabled. The first [chars] is the interface, [enet] is the Ethernet address of the host, and the second [chars] is the session ID.
Recommended Action Make sure that the interface is configured to support the number of hosts that are attached to it. Enter the shutdown interface configuration command followed by no shutdown interface configuration command to restart the interface.
Error Message AUTHMGR-5-VLANASSIGN: VLAN [dec] assigned to Interface [chars] AuditSessionID [chars]Explanation A VLAN was assigned. [dec] is the VLAN ID, the first [chars] is the interface, and the second [chars] is the session ID.
Recommended Action No action is required.
Error Message AUTHMGR-7-FAILOVER: Failing over from [chars] for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation The authorization manager is failing over from the current authentication method to another method. The first [chars] is the current authentication method, the second [chars] is the client ID, the third [chars] is the interface, and the fourth [chars] is the session ID.
Recommended Action No action is required.
Error Message AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation All available authentication methods have been tried for the client, but authentication has failed. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required. If local authorization has been configured, the port will be authorized based on the local authorization method. Otherwise, authentication will restart according to the configured reauthentication period.
Error Message AUTHMGR-7-RESULT: Authentication result [chars] from [chars] for client [chars] on Interface [chars] AuditSessionID [chars]Explanation The results of the authentication. The first [chars] is the status of the authentication, the second [chars] is the authentication method, the third [chars] is the client ID, the fourth [chars] is the interface, and the fifth [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action. AuditSessionID [chars]Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication. [chars] is the session ID.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-5-FAIL: Authentication failed for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation The authentication was unsuccessful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation Authentication was successful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars] AuditSessionID [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. This message might appear if IEEE 802.1x is enabled. [enet] is the client MAC address, the first [chars] is the interface, and the second [chars] is the session ID.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.
Error Message EPM-6-AUTH_ACL: POLICY [chars]| EVENT [chars]Explanation The switch has sent or received a download request for a downloadable ACL (dACL). The first [chars] is the dACL policy? The second [chars] is the event.
Recommended Action No action is required.
Error Message HARDWARE-3-ASICNUM_ERROR: [traceback] Port-ASIC number [dec] is invalidExplanation The port ASIC number is invalid. [dec] is the port ASIC number.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message HARDWARE-3-PORTNUM_ERROR: [traceback] port number [dec] is invalidExplanation The port number is out of range. [dec] is the port number.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message HULC_LICENSE-1-LICENSE_REGISTER_FAILED: [chars] - rc = [dec]Explanation The licensing initialization failed. [chars] explains what part of the license registration failed, and [dec] is the type of license initialization error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT: [chars] seems to be corrupted. Trying to read [dec] sizeExplanation The ifIndex table is corrupted. [chars] is the path to the IfIndex file, and [dec] is the number of bytes that was being read from the ifIndex table when the corruption was detected.
Recommended Action Delete the ifindex table.
Error Message IFMGR-3-INVALID_PERSISTENT_DATA: Invalid persistent dataExplanation The interface manager attempts to write invalid persistent data.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.Explanation A license authentication failure occurred for the switch.
Recommended Action Contact your Cisco sales representative for assistance.
Error Message ILET-1-DEVICE_AUTHENTICATION_FAIL: The [chars] inserted in this switch may not have been manufactured by Cisco or with Cisco's authorization. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.Explanation A license authentication failure occurred for a component that was inserted in the switch. [chars] is the component.
Recommended Action Contact your Cisco sales representative for assistance.
Error Message SCHED-3-UNEXPECTEDEVENT: [traceback] [process information] Process received unknown event (maj [hex], min [hex])Explanation A process did not handle an event. The first [hex] is the major event number, and the second [hex] is the minor event number, both of which allow you to identify the event that occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Modified System Messages
Error Message DOT1X-5-RESULT_OVERRIDE: Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation The authentication result was overridden. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a primary VLAN to an 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Use a different VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid secondary VLAN [dec] to PVLAN host 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a nonsecondary VLAN to a private VLAN host 802.1x port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the port mode so that it is no longer a PVLAN host port, or use a valid secondary VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND: Attempt to assign VLAN [dec], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shut down. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Make sure that the primary VLAN exists and is not shut down. Verify that the private VLAN is associated with a primary VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN [dec] to non-PVLAN host 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a secondary VLAN to a port that is not a private VLAN host port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the port mode so that it is configured as a private VLAN host port, or use a different VLAN that is not configured as a secondary VLAN.
Error Message DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN [dec] to 802.1x port [chars], which is configured as a SPAN destination AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to an 802.1x port that is configured as a Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the SPAN configuration so that the port is no longer a SPAN destination port, or change the configuration so that no VLAN is assigned.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port AuditSessionID [chars]Explanation Multi-Domain Authentication (MDA) host mode cannot start when the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port session ID.
Recommended Action Change either the voice VLAN or the access VLAN on the interface so that they are not the same. MDA then starts.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot be equivalent to the Voice VLAN AuditSessionID [chars]Explanation An attempt was made to assign a data VLAN to an 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change either the voice VLAN or the 802.1x-assigned VLAN on the interface so that they are not the same.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Assign a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is out of range. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Update the configuration to use a valid VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Make sure the VLAN exists and is not shut down, or use another VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Attempt to assign VLAN [dec] to routed 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to a supplicant on a routed port, which is not allowed. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Either disable the VLAN assignment, or change the port type to a nonrouted port.
Error Message DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Attempt to assign VLAN [dec] to promiscuous 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to a promiscuous IEEE 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the port mode so that it is no longer a promiscuous port, or change the configuration so that no VLAN is assigned.
Error Message DOT1X_SWITCH-5-ERR_VLAN_RESERVED: Attempt to assign reserved VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the seconds [chars] is the session ID.
Recommended Action Assign a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_RSPAN: Attempt to assign RSPAN VLAN [dec] to 802.1x port [chars]. 802.1x is incompatible with RSPAN AuditSessionID [chars]Explanation Remote SPAN should not be enabled on a VLAN with IEEE 802.1x-enabled. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Either disable remote SPAN configuration on the VLAN, or disable IEEE 802.1x on all the ports in this VLAN.
Error Message SPANTREE-2-BLOCK_BPDUGUARD_VP: Received BPDU on port [chars], vlan [dec] with BPDU Guard enabled. Disabling vlan.Explanation A BPDU was received on the interface and the VLAN specified in the error message. The spanning tree BPDU guard feature was enabled and configured to shut down the VLAN. As a result, the VLAN was placed in the error-disabled state. [chars] is the interface, and [dec] is the VLAN.
Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature. The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have Port Fast enabled. Re-enable the interface and vlan by entering the clear errdisable privileged EXEC command.
Deleted System Messages
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action.Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars]Explanation Authentication was successful. [chars] is the interface.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. This message might appear if IEEE 802.1x is enabled. [enet] is the client MAC address, and [chars] is the interface.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.
Error Message SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: [chars].Explanation This message means that the VTP code encountered an unusual diagnostic situation. [chars] is a description of the situation.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Updates to the Getting Started Guide
This illustration in the Cisco Catalyst Blade Switch 3020 for HP Getting Started Guide has been updated:
Figure 1 The Catalyst Blade Switch 3020 for HP
Switch module
Health LED
Release latch
SFP module port LEDs for ports 17 to 20
System status LEDs
SFP module ports 17 to 20
Mode button
Gigabit Ethernet ports LEDs for ports 17x to 24x
Console port
Gigabit Ethernet ports 17x to 24x
UID1 LED
1 UID: unit identifier.
This information in the Cisco Catalyst Blade Switch 3020 for HP Getting Started Guide has been updated:
When you launch Express Setup, you are prompted for the switch password. Enter the default password, cisco. The switch ignores text in the username field. Before you complete and exit Express Setup, you must change the password from the default password, cisco.
Related Documentation
These documents provide complete information about the Cisco Catalyst Blade Switch 3020 for HP and are available at Cisco.com:
http://www.cisco.com/en/US/products/ps8743/tsd_products_support_series_home.html
These documents provide complete information about the Cisco Catalyst Blade Switch 3020 for HP:
•
•
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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. (1110R)
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.
Copyright © 2010 Cisco Systems, Inc. All rights reserved.
