Table Of Contents
Device Manager System Requirements
Upgrading the Switch Module Software
Finding the Software Version and Feature Set
Upgrading a Switch Module by Using the Device Manager or Network Assistant
Upgrading a Switch Module by Using the CLI
Recovering from a Software Failure
Minimum Cisco IOS Release for Major Features
IBM BladeCenter Advanced Management Module Limitations
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
Update to the Device Manager Online Help
Updates to the Switch Getting Started Guide
Update to the Switch Hardware Installation Guide
Updates to the System Message Guide
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Catalyst Switch Module 3110G, 3110X, and 3012 for IBM BladeCenter, Cisco IOS Release 12.2(55)SE and Later
Revised March 28, 2012
Cisco IOS Release 12.2(55)SE runs only on Catalyst Switch Module 3110G, 3110X, and 3012.
These release notes include important information about Cisco IOS Release 12.2(55)SE and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch module:
•
If you are installing a new switch module, see the Cisco IOS release label on the rear panel of your switch module.
•
•
You can download the switch module software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/software/navigator.html
For the complete list of Catalyst Switch Module 3110G, 3110X, and 3012 for IBM BladeCenter documentation, see the "Related Documentation" section.
Contents
•
•
•
•
•
•
•
•
System Requirements
•
Hardware Supported
Table 1 Catalyst Switch Module Supported Hardware
Cisco IOS ReleaseCatalyst Switch Module 3110G
4 external 10/100/1000BASE-T Ethernet ports, 14 internal 1000BASE-X Ethernet downlink ports, 1 internal 100BASE-T Ethernet management port, 2 StackWise Plus ports
Cisco IOS Release 12.2(40)EX2
Catalyst Switch Module 3110X
1 external 10-Gigabit Ethernet module slot, 14 internal 1000BASE-X Ethernet downlink ports, 1 internal 100BASE-T Ethernet management port, 2 StackWise Plus ports
Note
Cisco IOS Release 12.2(40)EX2
Catalyst Switch Module 3012
4 external 10/100/1000BASE-T Ethernet ports, 14 internal 1000BASE-X Ethernet downlink ports, 1 internal 100BASE-T Ethernet management port
Cisco IOS Release 12.2(40)EX2
Cisco X2 transceiver modules
X2-10GB-SR
X2-10GB-LX4
X2-10GB-CX4X2-10GB-LR
X2-10GB-LRMNote
12.2(40)EX1
12.2(46)SE
SFP modules1
GLC-T
GLC-SX-MM
GLC-LH-SMNote
12.2(52)SE
Supports OneX (CVR-X2-SFP10G) and these SFP+ modules
(For the Catalyst Switch Modules 3110G and 3110X)
SFP-10G-SR
Only version 02 or later CX12 cables are supported:
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5M12.2(55)SE1
1 SFP = small form-factor pluggable
2 The CX1 cables are used with the OneX converters.
Table 2 lists the IBM BladeCenter supported blade enclosures. The switch module is for use only in listed IBM BladeCenter products.
Table 2 IBM BladeCenter Supported Switch Modules
BladeCenter E (BC-E)
Yes
Yes
Yes
BladeCenter T (BC-T)
Yes
Yes
Yes
BladeCenter H (BC-H)
Yes
Yes
Yes
BladeCenter HT (BCH-T)1
Yes
Yes
Yes
BladeCenter S (BC-S)
No
No
Yes
BladeCenter Multi-switch Interconnect Module (MSIM)
Yes2
Yes2
Yes
1 The Cisco Catalyst Switch modules are not supported in the MSIM-T module.
2 The advanced Management Module (aMM) firmware must use Version 1.42i or higher.
Device Manager System Requirements
•
•
Hardware Requirements
Table 3 Minimum Hardware Requirements
Intel Pentium II1
64 MB2
256
1024 x 768
Small
1 We recommend Intel Pentium 4.
2 We recommend 256-MB 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.
Note
CNA Compatibility
Cisco IOS Release 12.2(40)EX2 and later is only compatible with Cisco Network Assistant 5.0 and later. You can download Network Assistant from this URL:
http://www.cisco.com/go/cna_doc
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Module Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch module. The second line of the display shows the version.
Note
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 module through the device manager. To upgrade the switch module through the command-line interface (CLI), use the tar file and the archive download-sw or archive download privileged EXEC command.
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 IBM document on Cisco.com:
http://www.cisco.com/en/US/products/ps8741/products_installation_and_configuration_guides_list.html
Archiving Software Images
Before upgrading your switch module 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 network devices to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly.
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 module as a TFTP server to copy files from one switch module 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 Module by Using the Device Manager or Network Assistant
You can upgrade switch module software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
Upgrading a Switch Module by Using the CLI
This procedure is for copying the combined tar file to the switch module. You copy the file to the switch module 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/software/navigator.html
b.
c.
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 module, 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 module:
Switch# archive download-sw /overwrite tftp://198.30.20.19/cbs31x0-universal-tar.image-name.tarYou can also download the image file from the TFTP server to the switch module 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 module by using the IBM advanced Management Module software and the switch module device manager Express Setup program, as described in the switch module getting started guide.
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.
Minimum Cisco IOS Release for Major Features
Table 5 lists the minimum software release (after the first release) required to support the major features of the Catalyst Switch Module 3110G, 3110X, and 3012. Features not listed are supported in all releases.
Limitations and Restrictions
You should review this section before you begin working with the switch module. 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 module hardware or software.
•
•
•
Cisco IOS Limitations
Unless otherwise noted, these limitations apply to the Catalyst Switch Module 3110G, 3110X, and 3012:
•
•
•
•
•
Access Control List
•
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 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
•
•
Configuration
•
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 module generates this notification when snooping the next ARP packet. (CSCse47548)
•
The workaround is to not configure VLANs with protected ports as part of a fallback bridge group. (CSCsg40322)
•
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)
•
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 879A58There is no workaround. (CSCsh12472)
•
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port.(CSCsi26392)
•
show mls qos interfaceshow mls qos interface buffersshow mls qos interface policersshow mls qos interface queueingshow mls qos interface statisticsshow mac access-groupshow controllers ethernet-controllershow interfaces Gin/0/19 [all options]show idb allThere is no workaround. (CSCsk51772)
•
There is no workaround. (CSCso35380)
•
There is no workaround. (CSCso75068)
•
The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090)
HSRP
•
There is no workaround.(CSCth00938)
IEEE 802.1x Authentication
•
•
Use one of these workarounds (CSCsd90495):
–
–
•
–
–
Use one of these workarounds (CSCse04534):
–
–
Multicasting
•
–
–
–
The workaround is to not generate multicast packets with a TTL value of 0 or 1 or to disable multicast routing in the VLAN. (CSCeh21660)
•
–
–
–
There is no workaround. (CSCei08359)
•
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)
•
There is no workaround. (CSCsd45753)
•
Quality of Service (QoS)
•
There is no workaround. (CSCeh18677)
•
There is no workaround. (CSCsc63334)
•
The workaround is to use a different name for the interface-level policy map. (CSCsd84001)
•
There is no workaround. (CSCsd72001)
•
There is no workaround. (CSCsg79627)
•
Use one of these workarounds:
–
–
•
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)
RADIUS
•
There is no workaround. (CSCta05071)
Routing
•
The workaround is to not send traffic to unknown destinations. (CSCse97660)
SPAN and RSPAN
•
There is no workaround. This is a hardware limitation. (CSCei10129)
Stacking
•
There is no workaround. This is not a supported configuration. (CSCsj44478)
Device Manager Limitations
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
IBM BladeCenter Advanced Management Module Limitations
•
See the IBM Retain database for more information.
SoL and cKVM
Serial over LAN (SoL) can be used to manage remote servers through the command-line interface (CLI) over a Telnet or Secure Shell (SSH) connection. A systems management controller is on each server, and the server serial ports are connected through an IP network. SoL is available even with no operating system on the server.
With concurrent Keyboard, Video, and Mouse (cKVM) support, an enhancement of standard KVM, you can access all servers at the same time. cKVM also uses systems management controller to send traffic.
IBM BladeCenter SoL and cKVM traffic is encapsulated and sent on one of the chassis switch modules via VLAN 4095 to the IBM management module. This traffic is sent separately from the server traffic. The IBM BladeCenter servers support VLAN 4095, SoL, and cKVM.
These limitations apply to all server facing ports on the Cisco Catalyst Switch Module CBS3110X, CBS3110G, and CBS3012:
•
There is no workaround
•
There is no workaround.
•
There is no workaround.
•
There is no workaround.
•
The workaround is to configure the proper load-balancing method that always forwards the SoL traffic to the active NIC.
•
•
On the Catalyst Switch Module 3110X only, port 14 is the collector port receiving SoL and cKVM traffic. In addition to the previous limitations, these also apply to this port:
•
•
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
If the switch module 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:
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 module and the ACS. You should also make sure that the switch module has been properly configured as an AAA client on the ACS.
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 module 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 module.
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.
Open Caveats
•
On the Catalyst Switch Module 3012, the license boot level global configuration command shows ipbase and ipservices as available keywords. The ipservices keyword is not supported. The switch supports only the IP base image.
There is no workaround.
•
You cannot ping the Ethernet management port interface (Fa0) on the switch after you configure an IP address on the VLAN 1 interface.
There is no workaround.
•
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.
•
If you enter the shutdown interface configuration command on the the Fast Ethernet 0 router interface and VLAN 1 client switch interface, and then restart the master switch, the shutdown status of these two interfaces are not shown correctly. If you check their status with the show running-config privileged EXEC command, these interfaces are shown as up..
There is no workaround.
•
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.
•
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
•
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.
•
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.
•
A memory leak occurs when a Switch Virtual Interface (SVI) is configured and an external management port is disabled on the Advanced Management Module (AMM).
There is no workaround.
•
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.
•
The device manager does not work properly if a BladeCenter T chassis is used for the switch.
There is no workaround.
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.
•
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
•
A CPUHOG system message is displayed.
The workaround is to create an snmp-server view that blocks the particular portion of the MIB tree (interface configuration command snmp-server view cutdown).
•
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:
–
–
–
–
•
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.
•
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.
•
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
•
Cisco X2-10GB-CX4 transceiver modules with a version identification number lower than V03 might be difficult to install because of a size discrepancy.
The workaround is to use modules with a version identification number of V03 or later.
•
When the logging event-spanning-tree interface configuration command is configured and logging to the console is enabled, a topology change might generate a large number of logging messages, causing high CPU usage. CPU usage can increase with the number of spanning-tree instances and the number of interfaces configured with the logging event-spanning-tree interface configuration command. This condition adversely affects how the switch module operates and could cause problems such as STP convergence delay.
High CPU usage can also occur with other conditions, such as when debug messages are logged at a high rate to the console.
Use one of these workarounds:
–
–
–
•
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 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.
•
Attempts to restore factory default settings from the advanced Management Module (aMM) web interface fail. After the switch restarts, the configurations are not erased and restored to their factory default settings. Switches that run Cisco IOS Release 12.2(50)SE or Release 12.2(52)SE are affected.
Workaround: Enter the write erase privileged EXEC command from the switch console, do not save the configuration from the switch console, and then restart the switch.
•
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–
–
•
When PAgP or LACP EtherChannels are configured on a switch and the stack reloads, entering a show interface or show etherchannel summary privileged EXEC command when the stack comes up can cause the console to lock up.
There is no workaround.
•
After a 10-Gigabit Ethernet interface in an X2-10GB-SR module is down and the switch is restarted, the show inventory command output shows the module as not present.
The workaround is to reinstall the X2-10GB-SR module or to restart the switch.
•
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 an external uplink port is in the spanning-tree blocking state, the port LED is off instead of green.
There is no workaround. This is a cosmetic error and does not affect the switch port functionality.
•
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
•
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.
•
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.
•
You can see this error message on the switch message logs:
%PLATFORM_ENV-1-TEMP: Abnormal temperature detected
However, when you enter the show env all privileged EXEC command, the temperature value shows it to be well within the limits.
There is no workaround.
•
If you try to access the Web-based device manager from the IBM AMM, the switch incorrectly reports to the IBM blade center chassis that it supports only https and does not support http.
When you access device manager from the AMM, the URL link is always https://. The workaround is to manually change it to http:// in the browser.
•
A PC in 802.1x or 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.
•
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 reinitalized and moved out of the critical VLAN.
There is no workaround.
•
Replacing the power module can cause the advanced management module (AMM) to fail to connect with the switches.
The workaround is to restart the AMM.
•
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.
•
The switch internally uses the mac-address-table static mac-address deprecated global configuration command to configure the MAC address on the Ethernet management port (Fa0).
The workaround is to use the correct version of the command: mac address-table static mac-address.
•
When VTP pruning is enabled in a VTP domain, the switch in VTP server mode sends advertisements to neighboring switches. If the VTP and VLAN configuration for neighboring ports is not updated, VLANs on those ports can be pruned, causing a network traffic outage.
The workaround is to disable VTP pruning.
•
This message appears after inserting the CVR-X2-SFP converter module and the X2-10GB-SR transceiver modules in the10-Gigabit slots of the Catalyst 3750-E and 3560-E switches:
%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Te1/0/1 has bad crcThere is no workaround.
•
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:
Update to the Device Manager Online Help
For Catalyst Switch Module 3110G and 3012, the physical LED behavior is different from the LED behavior on the device manager.
Updates to the Switch Getting Started Guide
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.
Update to the Switch Hardware Installation Guide
Catalyst Switch Module 3110X running Cisco IOS Release 12.2(52)SE or later ships with the Cisco TwinGig Converter Module (model CVR-X2-SFP) installed.
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 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 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 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.
Related Documentation
For more information about the switch module, see these documents on Cisco.com:
http://www.cisco.com/en/US/products/ps8741/tsd_products_support_series_home.html•
•
•
•
•
•
•
For more information about the IBM BladeCenter enclosure, see the IBM documentation:
http://www-03.ibm.com/systems/bladecenter/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•
For other information about related products, see these documents:
•
•
•
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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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. (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.
© 2010 Cisco Systems, Inc. All rights reserved.
