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
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE5
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE3
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE
Update to the Software Documentation
Update to the Command Reference
Update to the Device Manager Online Help
Updates to the Switch Getting Started 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(50)SE and Later
Revised October 21, 2010
Cisco IOS Release 12.2(50)SE and later runs only on Catalyst Switch Module 3110G, 3110X, and 3012.
These release notes include important information about Cisco IOS Release 12.2(50)SE and later 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 these sites (registered Cisco.com users with a login password):
http://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches
http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?brandind=5000020&taskind=2
This software release is part of a special release of Cisco IOS software that is not released on the same maintenance cycle that is used for other platforms. As maintenance releases and future software releases become available, they will be posted to Cisco.com in the Cisco IOS software area, and on the IBM support page.
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 lists the hardware supported on this release.
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 (BC-HT)
Yes
Yes
Yes
BladeCenter S (BC-S)
No
No
Yes
BladeCenter Multi-switch Interconnect Module (MSIM)
Yes1
Yes1
Yes
1 The advanced Management Module (aMM) firmware must use Version 1.42i or higher.
Device Manager System Requirements
These sections describe the hardware and software requirements for using the device manager:
•
•
Hardware Requirements
Table 3 lists the minimum hardware requirements for running the device manager.
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.
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/networkassistant
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.
Table 4 lists the filenames for this software release.
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.
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/12_2/configfun/command/reference/ffun_r.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
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the universal software image files for a switch module, click Cisco Catalyst Blade Switch 3000 Series for IBM.
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.122-40.EX.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 Features
These sections describe the new supported hardware and the new and updated software features provided in this release:
•
•
New Hardware Features
For a list of all supported hardware, see the "Hardware Supported" section.
New Software Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The advanced IP services software license is now end-of-sale (EOS) and end-of-life (EOL). For more information, see http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps7077/eol_c51_519629.html
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.
This section contains these limitations:
•
•
•
Cisco IOS Limitations
Unless otherwise noted, these limitations apply to the Catalyst Switch Module 3110G, 3110X, and 3012:
•
•
•
•
Access Control List
This is the access control list (ACL) limitation:
When a MAC access list is used to block packets from a specific source MAC address, that MAC address is entered in the switch module MAC-address table.
The workaround is to block traffic from the specific MAC address by using the mac address-table static mac-addr vlan vlan-id drop global configuration command. (CSCse73823)
Address Resolution Protocol
This is an Address Resolution Protocol limitation:
The switch module might place a port in an error-disabled state due to an Address Resolution Protocol (ARP) rate limit exception even when the ARP traffic on the port is not exceeding the configured limit. This could happen when the burst interval setting is 1 second, the default.
The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem.(CSCse06827))
Cisco X2 Transceiver Modules
These are the Cisco X2 transceiver module limitations:
•
•
•
Configuration
These are the configuration limitations:
•
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 A268D8
No 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 879A58
There is no workaround. (CSCsh12472)
•
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port.(CSCsi26392)
•
There is no workaround. (CSCso35380)
•
The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090)
IEEE 802.1x Authentication
These are the IEEE 802.1x authentication limitations:
•
Use one of these workarounds (CSCsd90495):
–
–
•
–
–
Use one of these workarounds (CSCse04534):
–
–
Multicasting
These are the multicasting limitations:
•
–
–
–
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)
•
QoS
These are the quality of service (QoS) limitations:
•
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:
–
–
Routing
This is the routing limitation:
•
The workaround is to not send traffic to unknown destinations. (CSCse97660)
SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•
There is no workaround. This is a hardware limitation. (CSCei10129)
•
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 (CSCsg91027):
–
–
–
Device Manager Limitations
This is the device manager limitation:
When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not start.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
IBM BladeCenter Advanced Management Module Limitations
This is the advanced Management Module (aMM) limitation:
When a switch module is installed in a BC-HT chassis with the ISL Interposer, the switch module incorrectly reports that it is installed in a BC-T chassis and that it provides 8 server ports and no ISL ports. When it is installed with the non-ISL Interposers, the switch module incorrectly reports that it is installed in a BC-H chassis and that it provides 14 server ports.
See the IBM Retain database for more information.
Important Notes
These sections describe the important notes related to this software release for the Catalyst Switch Module 3110G, 3110X, and 3012:
•
Cisco IOS Notes
This note applies to Cisco IOS software:
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
These notes apply to the device manager:
•
•
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch 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
This section describes the open caveats in this software release. Unless otherwise noted, these Cisco IOS configuration caveats apply to the Catalyst Switch Module 3110G, 3110X, and 3012:
•
Creating a mixed switch stack with a Catalyst Switch Module 3110, a Catalyst Switch Module 3120, or a Catalyst Switch Module 3130 produces unpredictable behavior and could cause a system failure. Because the switch module software does not detect this type of configuration, it allows a stack of this type.
There is no workaround. This is not a supported configuration.
•
(Only Catalyst Switch Module 3110G and 3012) These privileged EXEC commands incorrectly display the internal, nonconfigurable Gigabit Ethernet interfaces n/0/19 and n/0/20.
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.
•
When you remove a switch module from a switch stack, the switch module Fa0 management interface remains administratively down and cannot be enabled by using the CLI.
The workaround is to reload the switch module.
•
(Only Catalyst Switch Module 3110X) When you move a blade server installed in slot 14 to another blade enclosure slot and install a new server in slot 14, unicast traffic from the original server to the new server might not be forwarded.
No workaround is needed. The problem corrects itself when the dynamic MAC address learning period times out. The default timeout is 5 minutes and is configurable in the CLI.
•
(Only Catalyst Switch Module 3110X) If you configure port security on Gigabit Ethernet interface n/0/14, the switch module software incorrectly allows the configuration. Port security is not supported on Gigabit Ethernet interface n/0/14.
There is no workaround.
•
When you use the ipv6 address dhcp interface configuration command on an interface that is configured in router mode, other addresses on the prefix associated with the new address might not be accessible.
The workaround is to use the ipv6 address dhcp interface configuration command on an interface that is configured in host mode, or configure a static route to the prefix through the interface.
•
On switches running Cisco IOS Release 12.2(44)SE or 12.2(46)SE, when you enter the show mvr interface interface-id members privileged EXEC command to see status of an MVR port, an MVR member port that is not connected always shows as ACTIVE.
The workaround is to use the show mvr interface interface-id or the show mvr members privileged EXEC command. These command outputs show the correct status of an MVR port.
•
When you enter the mvr vlan vlan-id global configuration command to create an MVR VLAN and enable MVR on the switch by entering the mvr global configuration command, if you enter the show mvr interface interface-id members privileged EXEC command, the output shows the MVR groups on the interface. However, if you enable MVR first and then create the MVR VLAN, the MVR groups are not displayed correctly.
•
A switch running Cisco IOS Release 12.2(46)SE might lose packets for up to 30 seconds when a link fails. This occurs in some multiple spanning-tree (MST) topologies.
There is no workaround.
•
The management port (Fa0) is shut down when a Telnet session is opened on the port from the chassis GUI. This occurs when the switch is in a stack and the stack members are powered down by using the chassis GUI.
The workaround is to reload the switch.
•
When an interface on the stack master is a member of an EtherChannel and the channel group number is removed before a master switch changeover, you can not use the same group number when you recreate the EtherChannel after the changeover.
These are possible workarounds:
–
–
–
•
The switch unexpectedly reloads when copying a configuration file from a remote server or from flash memory containing logging file flash:
The workaround is to enter the logging file flash:filename global configuration command to configure logging to flash instead of copying to flash.
•
When periodic port-based reauthentication is enabled and a new stack master is elected, the stack does not reauthenticate a connected client.
The workaround is to enter the dot1x re-authenticate interface interface-id privileged EXEC command to reauthenticate the client.
•
When a redirect URL is configured for a client on the authentication server and a large number of clients are authenticated, high CPU usage could occur on the switch.
There is no workaround.
Resolved Caveats
•
•
•
•
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE5
•
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
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE3
•
Memory allocation errors no longer occur when the Cisco Express Forwarding (CEF) consistency checkers have been enabled. The CEF consistency checkers have been enabled by default. They can also be enabled by using these global configuration commands:
cef table consistency-check ipv4
cef table consistency-check ipv6
•
A switch no longer fails when you enter the configure replace privileged EXEC command, and a banner is already present in the switch configuration.
•
You can now query the bgpPeerTable MIB for VPN/VRF interfaces.
•
Cisco IOS Software contains a vulnerability that could allow an attacker to cause a Cisco IOS device to reload by remotely sending a crafted encryption packet. Cisco has released free software updates that address this vulnerability. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml.
•
The output of the show ip ssh privileged EXEC command no longer displays SSH Enabled - version 2.99. Instead, a correct SSH version (1.5, 1.99 or 2.0) now appears.
•
Cisco IOS Software configured with Authentication Proxy for HTTP(S), Web Authentication or the consent feature, contains a vulnerability that may allow an unauthenticated session to bypass the authentication proxy server or bypass the consent webpage.
There are no workarounds that mitigate this vulnerability.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml
•
Cisco IOS devices that are configured for Internet Key Exchange (IKE) protocol and certificate based authentication are vulnerable to a resource exhaustion attack. Successful exploitation of this vulnerability may result in the allocation of all available Phase 1 security associations (SA) and prevent the establishment of new IPsec sessions.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml
•
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.
•
A switch no longer fails when a host moves from a dynamically assigned VLAN to a configured VLAN.
•
A switch configured with 802.1x and port security on the same ports no longer might inappropriately put the ports into an error-disabled state.
•
Moving a PC between two IP Phones without disconnecting either phone from the switch no longer triggers a port-security violation.
•
A port security violation error no longer occurs when MAC address sticky learning is enabled on a port and a CDP is enabled on a connected IP Phone.
•
A Telnet, Secure Shell (SSH), or console session on the switch no longer fails when you use the show file systems EXEC command or when you access the remote file system, flashn: (where n is the switch number).
•
Third-party IP phones now automatically power up when reconnected to enabled PoE ports on the switch.
•
If a large number of clients in a switch stack use MAC authentication bypass to authenticate at the same time, the clients are no longer in the unauthorized state when
–
–
–
–
•
The switch now changes the time in an EnergyWise recurrence event when the local time changes to daylight saving time.
•
A trunk port no longer goes into the error-disabled state when the trunk port's native VLAN is in a suspended state or is not configured on the switch itself.
•
The switch no longer fails when you use the vacant-message line configuration command.
•
When IEEE 802.1x multiple authentication mode is configured on a port, two PCs have been authenticated, and the first PC is disconnected, the second PC now receives and forwards traffic on the port.
•
The switch no longer reloads when the default port cost of service (CoS) value is updated on a port that has a policy map configured and CoS override enabled with the mls qos cos override privileged EXEC command.
•
If a link failure occurs on a secondary edge port, preemption now occurs after the link comes up.
•
Communication with the blade server is no longer lost after a blade switch is upgraded.
•
A stack member no longer fails when the hostname is longer than 36 characters.
•
When open1x authentication and MAC authentication bypass are enabled on a port, an IP phone is connected to the port, and DHCP snooping is enabled on the switch, DHCP traffic is now forwarded on the voice VLAN before open 1x authentication times out and the switch uses MAC authentication bypass to authorize the port.
•
The switch no longer reloads when you enter several key strokes while in interface-range configuration mode.
•
If MAC authenication bypass is enabled and the RADIUS server is not available, the switch now tries to re-authenticate a port after a server becomes available.
•
If you are configuring Flexible Authentication Ordering with web authentication on a switch port and the switch uses 802.1x to authenticate the the host, Address Resolution Protocol (ARP) now works properly.
•
When VPN routing and forwarding (VRF) is configured on the stack master, communication no longer fails after the stack master has shut down.
•
A memory leak no longer occurs when Cisco Network Assistant is polling the switch and the ip http server or ip http-secure-server global configuration command is enabled.
•
If you enable automatic server testing through the radius-server host ip-address [test username name] global configuration command, the switch no longer sends requests to the RADIUS server if the server is not available.
•
SNMP queries to the Bridge-MIB now operate on switch stacks with five or more stack members and a large number of active ports.
•
Re-authentication now occurs on a port under these conditions:
–
–
–
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE1
•
If the connection to a primary AAA server fails, the backup server is now queried for login access.
•
When a TCP packet with all flags set to zero (at the TCP level) is sent to a remote router, the remote (destination) router no longer returns an ACK/RST packet back to the source of the TCP segment.
•
The switch now accepts an encrypted secret password.
•
The switch no longer runs out of memory when an smnpwalk, snmpget, or snmpbulkwalk is run on the CISCO-ENERGYWISE-MIB.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE
•
Symptoms: Several features within Cisco IOS software are affected by a crafted UDP packet vulnerability. If any of the affected features are enabled, a successful attack will result in a blocked input queue on the inbound interface. Only crafted UDP packets destined for the device could result in the interface being blocked, transit traffic will not block the interface.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available in the workarounds section of the advisory. This advisory is posted at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20090325-udp.shtml.
•
A vulnerability in the handling of IP sockets can cause devices to be vulnerable to a denial of service attack when any of several features of Cisco IOS software are enabled. A sequence of specially crafted TCP/IP packets could cause any of the following results:
–
–
–
–
Workarounds that mitigate this vulnerability are available in the "workarounds" section of the advisory. The advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-ip.shtml
•
When STP is disabled on the stack, the Hot Standby Router Protocol (HSRP) hello packets now pass through the switch stack when the stack is connected to two routers through cross-stack EtherChannels.
•
The server no longer attempts re-authentication every ten minutes when a switch is configured with the dot1x timeout reauth-period server interface configuration command.
•
Traffic is now forwarded to the interfaces that are configured with static multicast MAC addresses after the switch is reloaded.
Note
•
If the switch uses 802.1x authentication with VLAN assignment, it no longer uses the VLAN assignment with different authorization attempts, such as user authentication or re-authentication.
•
Cisco IOS software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.
Cisco has released free software updates that address this vulnerability.
Several mitigation strategies are outlined in the workarounds section of this advisory.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml
•
When keepalive is disabled on an interface, the interface is no longer put in an error-disabled state when it receives keepalive packets.
•
The Switched Port Analyzer (SPAN) destination port no longer detects IPv6 multicast packets from a VLAN that is not being monitored by SPAN.
•
This message no longer appears in the log during the system bootup on a switch that is running
Cisco IOS 12.2(50)SE:%COMMON_FIB-3-FIBIDBINCONS2•
When SFP ports are configured as status multicast router ports, IPv6 Multicast Listener Discovery (MLD) snooping now works after the switch reloads.
•
The Set TxPortFifo SRR Failed message no longer appears when you enter both the srr-queue bandwidth shape 200 0 2 200 and the priority-queue out interface configuration commands on the same interface.
•
The switch no longer reloads when the Forwarding Information Base (FIB) adjacency table is added.
•
Multiple Cisco products are affected by denial of service (DoS) vulnerabilities that manipulate the state of Transmission Control Protocol (TCP) connections. By manipulating the state of a TCP connection, an attacker could force the TCP connection to remain in a long-lived state, possibly indefinitely. If enough TCP connections are forced into a long-lived or indefinite state, resources on a system under attack may be consumed, preventing new TCP connections from being accepted. In some cases, a system reboot may be necessary to recover normal system operation. To exploit these vulnerabilities, an attacker must be able to complete a TCP three-way handshake with a vulnerable system.
In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.
Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090908-tcp24.shtml.
•
A Cisco IP Phone connected to a Catalyst switch no longer becomes unauthorized when it transitions from the data authorization domain to the voice authorization domain.
•
The server side of the Secure Copy (SCP) implementation in Cisco IOS software contains a vulnerability that could allow authenticated users with an attached command-line interface (CLI) view to transfer files to and from a Cisco IOS device that is configured to be an SCP server, regardless of what users are authorized to do, per the CLI view configuration. This vulnerability could allow valid users to retrieve or write to any file on the device's file system, including the device's saved configuration and Cisco IOS image files, even if the CLI view attached to the user does not allow it. This configuration file may include passwords or other sensitive information.
The Cisco IOS SCP server is an optional service that is disabled by default. CLI views are a fundamental component of the Cisco IOS Role-Based CLI Access feature, which is also disabled by default. Devices that are not specifically configured to enable the Cisco IOS SCP server, or that are configured to use it but do not use role-based CLI access, are not affected by this vulnerability.
This vulnerability does not apply to the Cisco IOS SCP client feature.
Cisco has released free software updates that address this vulnerability.
There are no workarounds available for this vulnerability apart from disabling either the SCP server or the CLI view feature if these services are not required by administrators.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090325-scp.shtml.
•
A switch port configured for IGMP snooping no longer lose its group membership when the port receives a query comes from an upstream device that is not configured for IGMP snooping.
•
A switch configured with class-based policies that are applied and active on at least one interface no longer might reload or display CPU hog messages during SNMP polling for the ciscoCBQosMIB.
•
When you have entered the vlan dot1q tag native global configuration command to configure a switch to tag native VLAN frames on 802.1Q trunk ports, and you configure a new voice VLAN on an access port, the MAC address of a connected PC is now correctly relearned.
•
When a switch virtual interface (SVI) is configured as unnumbered and is pointing to a loopback interface, the switch no longer fails when the SVI receives a packet.
•
When LLDP is enabled and a voice VLAN is configured, the L2 Priority and DSCP Value fields in the LLDP type, length, and value descriptions (TLVs) are now correctly marked to give the voice traffic the correct DSCP and Layer 2 priority.
•
Switch ports no longer attempt authentication at the interval configured for the port security timer instead of the configured IEEE 802.1x timer.
Documentation Updates
•
•
•
•
•
Update to the Software Documentation
The switch does not support ISL trunking.
The switch does not support Cisco EnergyWise.
Update to the Command Reference
debug authentication
Use the debug authentication privileged EXEC command to enable debugging of the authentication settings on an interface. Use the no form of this command to disable debugging.
debug authentication {all | errors | events | sync | feature [all] [acct] [auth_fail_vlan] [auth_policy] [autocfg] [critical] [dhcp] [guest_vlan] [mab_pm] [mda] [multi_auth] [switch_pm] [switch_sync] [vlan_assign] [voice] [webauth] [all | errors | events]}
no debug authentication {all | errors | events | sync | feature [all] [acct] [auth_fail_vlan] [auth_policy] [autocfg] [critical] [dhcp] [guest_vlan] [mab_pm] [mda] [multi_auth] [switch_pm] [switch_sync] [vlan_assign] [voice] [webauth] [all | errors | events]}
Syntax Description
Defaults
Authentication debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug authentication command is the same as the no debug authentication command.
On stacking switches, when you enable debugging, it is enabled only on the stack master.
To enable debugging on a stack member, you can start a session from the stack master by using the session switch-number privileged EXEC command and then entering the debug authentication command at the command-line prompt of the stack member. You also can use the remote command stack-member-number line privileged EXEC command on the stack master switch to enable debugging on a stack member.
Related Commands
Update to the Device Manager Online Help
This is the update to switch module 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.
Updates to the System Message Guide
These messages were added:
Error Message ACLMGR-2-NOVMR: Cannot generate hardware representation of access list [chars]Explanation There are insufficient resources available to create a hardware representation of the ACL. A lack of available logical operation units or specialized hardware resources can cause this problem. Logical operation units are needed for a TCP flag match or a test other than eq (ne, gt, lt, or range) on TCP, UDP, or SCTP port numbers.
Recommended Action Modify the ACL configuration to use fewer resources, or rename the ACL with a name or number that alphanumerically precedes the other ACL names or numbers.
Error Message %DOT1X-5-FAIL: Authentication failed for client ([chars]) on Interface [chars]Explanation Authentication was unsuccessful. The first [chars] is the hostname, and the second [chars] is the interface.
Recommended Action No action is required.
Error Message %DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars]Explanation Authentication was successful. The first [chars] is the host name, and the second [chars] is the interface.
Recommended Action No action is required.
Error Message %DOT1X_SWITCH-4-PROC_START_ERR: Unable to start dot1x switch process.Explanation The software could not start the 802.1x authentication process.
Recommended Action Use the reload privileged EXEC command to reload the switch.
Error Message %EC-5-MINLINKS_MET: Port-channel [chars] is up as its bundled ports ([dec]) meets min-linksRecommended Action The administrative configuration of minimum links is equal to or less than the number of EtherChannel ports. The port channel is up. [chars] is the EtherChannel, and [dec] is the EtherChannel group number.
Recommended Action No action is required.
Error Message %EC-5-MINLINKS_NOTMET: Port-channel [chars] is down bundled ports ([dec]) doesn't meet min-linksExplanation The administrative configuration of minimum links is greater than the number of bundled ports. The port channel is down. [chars] is the EtherChannel, and [dec] is the EtherChannel group number.
Recommended Action Reduce the value of the minimum-links configuration parameter for an EtherChannel , or add more ports to the EtherChannel to create a bundle.
Error Message %IP_DEVICE_TRACKING_HA-3-FAIL_SEND_MSG_TO_ACTIVE: Failed to send [chars] message to active for [chars], [chars]
Note
Explanation The Inter-Process Communication (IPC) synchronization message was could not sent to the stack member in the run-time module because of a software error. For more information, see the message on the console or in the system log. The system state between the stack members and provisioned switches might not be synchronized. The first [chars] is the synchronization message, the second [chars] is the stack master number, and the third [chars] is the run-time module.
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. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. 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. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section on page 2-7.
Error Message %IP_DEVICE_TRACKING_HA-3-NO_RESOURCES: [chars]
Note
Recommended Action The software could not get the required resources to complete a task. This was probably caused by a software error or a lack of available memory. For more information, see the message on the console or in the system log. The system state between the active and standby units might not be synchronized. [chars] is message.
Recommended Action If a lack of available memory caused the problem, reduce other system activity, or allocate more memory for this task. If the problem recurs, 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. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. 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. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section on page 2-7.
Error Message %PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED: Unable to create [chars]Explanation The switch cannot create the specified managed object. [chars] is the object name.
Recommended Action No action is required.
Error Message %PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER: PAgP running on [chars] informing virtual switches of dual-active: new active id [enet], old id [enet]Explanation Port Aggregation Protocol (PAgP) received a new active ID on the specified interface, which means that all virtual switches are in a dual-active scenario. The interface is informing virtual switches of this, which causes one switch to go into recovery mode. [chars] is the interface. The first [enet] is the new active ID. The second [enet] is the ID that it replaces.
Recommended Action No action is required.
Error Message %PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registryExplanation The switch could not add a function to the registry. [chars] is the registry name.
Recommended Action No action is required.
Error Message %PHY-4-SFP_PLUS_NOT_SUPPORTED: The SFP PLUS in [chars] is not supportedExplanation The Cisco X2 transceiver module is not supported on the switch. [chars] is the port in which the SFP module is inserted.
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. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. 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. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section on page 2-7.
Error Message %PM-6-EXT_VLAN_ADDITION: Extended VLAN is not allowed to be configured in VTP CLIENT mode.Explanation The switch did not add a VLAN in VTP client mode.
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. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section in the system message guides.
Error Message %SPANTREE_VLAN_SHIM-3-ADD_REGISTRY_FAILED: Subsystem [chars] fails to add callback function [chars]Explanation A subsystem has added its callback functions. Use this message only for debugging. The first [chars] is the subsystem name, and the second [chars] is the function name.
Recommended Action No action is required.
Error Message %SPANTREE_VLAN_SHIM-2-MAX_INSTANCE: Platform limit of [dec] STP instances exceeded. No instance created for [chars] (port [chars]).Explanation The number of VLAN spanning-tree instances has reached the allowable maximum. No more VLAN instances are created until instances are less than the maximum. [dec] is the maximum, the first [chars] is the VLAN for which an STP instance is not created, and the second [chars] is the port number.
For example, when you are configuring spanning tree and the allowable maximum is 128 instances
–
–
STP instances are also not created for the remainder of the VLANs in the range
Recommended Action Reduce the number of active spanning-tree instances by either disabling some or deleting the VLANs associated with them. To create STP instances, manually create them. If you do not, the switch automatically creates an STP instances when a VLAN is created.
For example, if the switch has already created 128 instances and you want to create an STP instance for VLAN 200, remove a spanning-tree instance with one of these commands:
–
–
Then enter the spanning-tree 200 global configuration command to create an instance for VLAN 200.
These messages have been deleted:
Error Message ACLMGR-2-NOVMR: Cannot create VMR data structures for access list [chars].Error Message DOT1X-5-INVALID_INPUT: Dot1x Interface parameter is Invalid on interface [chars].Error Message DOT1X-5-SECURITY_VIOLATION: Security violation on interface [chars], New MAC address [enet] is seen.Error Message DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or shutdown VLAN [dec] to 802.1x port [chars]Error Message DOT1X_SWITCH-5-ERR_VLAN_ROUTED_PORT: Attempt to assign VLAN [dec] to routed 802.1x port [chars]Error Message UDLD-3-UDLD_IDB_ERROR: UDLD error handling [chars] interface [chars].Error Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error [chars].Error Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface [chars] [chars].Error Message UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface [chars], [chars] detected.Error Message UDLD-6-UDLD_PORT_RESET: UDLD reset interface [chars].Error Message UFAST_MCAST_SW-3-PROC_START_ERROR: No process available for transmitting UplinkFast packets.Error Message UFAST_MCAST_SW-4-MEM_NOT_AVAILABLE: No memory is available for transmitting UplinkFast packets on Vlan [dec].Error Message VQPCLIENT-2-CHUNKFAIL: Could not allocate memory for VQP.Error Message VQPCLIENT-2-DENY: Host [enet] denied on interface [chars].Error Message %VQPCLIENT-2-INITFAIL: Platform-specific VQP initialization failed. QuittingError Message %VQPCLIENT-2-IPSOCK: Could not obtain IP socketError Message %VQPCLIENT-7-NEXTSERV: Trying next VMPS [IP_address]Error Message %VQPCLIENT-7-PROBE: Probing primary server [IP_address]Error Message %VQPCLIENT-2-PROCFAIL: Could not create process for VQP. QuittingError Message %VQPCLIENT-7-RECONF: Reconfirming VMPS responsesError Message %VQPCLIENT-2-SHUTDOWN: Interface [chars] shutdown by VMPSError Message %VQPCLIENT-3-THROTTLE: Throttling VLAN change on [chars]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 at:
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, at:
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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
