Release Notes for the Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class, Cisco IOS Release 12.2(50)SE and Later
Available Languages
Table Of Contents
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Minimum Cisco IOS Release for Major Features
Device Manager Limitations and Restrictions
Hardware Limitations and Restrictions
VLAN Interfaces and MAC Addresses
References to Cisco IOS Release 12.2(25)SE
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE5
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE4
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE3
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE2
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 Configuration Guide
Release Notes for the Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class, Cisco IOS Release 12.2(50)SE and Later
Revised October5, 2010
These release notes include important information about Cisco IOS Release 12.2(50)SE and later for the Cisco Gigabit Ethernet Switch Module (CGESM) for the HP BladeSystem p-Class. This document includes any limitations, restrictions, and caveats that apply to this release.
To verify that these release notes are correct for your switch, use the show version user EXEC command (see the "Finding the Software Version and Feature Set" section).
You can download the switch software from this URL:
Contents
This information is in the release notes:
•
"System Requirements" section
•
•
•
•
•
•
•
•
System Requirements
The system requirements are described in these sections:
•
•
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
•
•
Hardware Requirements
Table 1 lists the minimum hardware requirements for running the device manager.
Table 1 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.
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI).
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
•
Finding the Software Version and Feature Set
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 user EXEC command to display the software version that is running on your switch.
You also can 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 tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Here are the filenames for this software release:
•
•
Upgrading a Switch by Using the Device Manager
You can upgrade switch software by using the device manager. From the feature bar, choose Administration > Software Upgrade. For detailed instructions, click Help.
Note
Upgrading a Switch by Using the CLI
This procedure is for copying the tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image. The archive download-sw privileged EXEC command both downloads and extracts the files.
To download the image for a CGESM switch, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
To download the cryptographic software files, click the software depot link in the Notes section. Once there, search for CGESM or go to the Enhancement releases and patch bundles section.
Step 6
For more information, refer to Appendix B in the software configuration guide for this release.
Step 7
Step 8
ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, refer to the software configuration guide for this release.
Step 9
archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/cgesm-i6l2-tar.122-25.SE1.tarYou also can download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
Recovering from a Software Failure
For recovery procedures, see the "Troubleshooting" chapter in the Cisco Gigabit Ethernet Switch Module for HP-Blade System p-Class Software Configuration Guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
New Software Features
There are no new software features for this release.
Minimum Cisco IOS Release for Major Features
Table 2 lists the minimum software release required to support the major features on this switch.
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
This section contains these limitations:
•
•
•
Cisco IOS Limitations
These limitations apply to CGESM switch:
Configuration
These are the configuration limitations:
•
•
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
1.
2.
3.
•
–
–
No workaround is necessary; these are the designed behaviors. (CSCed50819)
•
The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•
There is no workaround. (CSCsj21718)
Ethernet
Subnetwork Access Protocol (SNAP) encapsulated IP packets are dropped without an error message being reported at the interface. The switch does not support SNAP-encapsulated IP packets. There is no workaround. (CSCdz89142)
HSRP
When the active switch fails in a switch cluster that uses HSRP redundancy, the new active switch might not contain a full cluster member list. The workaround is to ensure that the ports on the standby cluster members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking state, see the "Configuring STP" chapter in the software configuration guide. (CSCec76893)
IP
When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console. The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)
IP Telephony
This is the IP telephony limitation:
After you change the access VLAN on a port that has 802.1x enabled, the IP Phone address is removed. Because learning is restricted on 802.1x capable ports, it takes approximately 30 seconds before the address is relearned. No workaround is necessary. (CSCea85312)
Multicasting
These are the multicasting limitations:
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
QoS
These are the quality of service (QoS) limitations:
•
•
SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•
This is a hardware limitation: (CSCdy72835)
•
This is a hardware limitation: (CSCdy81521)
•
This is a hardware limitation: (CSCed24036)
•
Trunking
These are the trunking limitations:
•
•
•
VLAN
These are the VLAN limitations:
•
•
Device Manager Limitations and Restrictions
These are the device manager limitations and restrictions:
•
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Hardware Limitations and Restrictions
This is the hardware limitation and restriction:
When using CLC-T SFPs in CGESM switches, the SFP module can be installed too far into the switch. This can prevent links from operating properly.
The workaround is to slightly pull the SFP out of the module slot. (CSCsd17765)
Important Notes
These sections describe the important notes related to this software release:
•
Cisco IOS Notes
These notes apply to Cisco IOS software:
•
If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)SE (or later), when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message:
AutoQoS Error: ciscophone input service policy was not properly appliedpolicy map AutoQoS-Police-CiscoPhone not configuredIf this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.
Device Manager Notes
These notes apply to the device manager:
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
•
VLAN Interfaces and MAC Addresses
All VLAN interfaces have assigned MAC addresses that are derived from the base MAC address. The base MAC address is the hardware address that is on the switch label. It also appears when you enter the show version privileged EXEC command.
On the first VLAN interface (VLAN 1), the MAC address is the base MAC address + 0 x 40. On the next VLAN interface that you configure, the MAC address is the base MAC address + 0 x 40 +1, and so on for other VLAN interfaces.
You can enter the show interfaces vlan vlan-id privileged EXEC command to show the MAC and IP addresses. The MAC addresses that appear in the show interfaces vlan vlan-id command output are not the same as the MAC address that is printed on the switch label (the base MAC address).
By default, VLAN 1 is the interface that connects to the management network. When the switch boots up, the DHCP client (switch) requests an IP address from a DHCP server by using the MAC address of VLAN 1.
Documentation Notes
This section describes documentation notes related to this IOS release.
References to Cisco IOS Release 12.2(25)SE
These older documents refer to Release 12.2(25)SE. The correct release is Release 12.2(25)SE1.
•
•
•
Open Caveats
Open Cisco IOS Caveats
These severity 3 Cisco IOS configuration caveats apply to the CGESM switch:
•
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.
•
When you use the show mvr interface interface members privileged EXEC command to view the Multicast VLAN Registration (MVR) interface group status, the switch incorrectly displays the status ACTIVE for port members that are not connected.
The workaround is to use the show mvr interface interface or show mvr members privileged EXEC command to display the port MVR status.
•
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 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.
Open HP Caveats
These are the HP severity 2 open caveats for this release:
•
Disconnecting the cable from the console port does not end a Telnet session. If you are in privileged EXEC mode when you remove the cable, the next session that is started on the console port will also be in privileged EXEC mode.
The workaround is to end the session before you remove the cable.
•
If you power on a switch that does not have a config.txt file (the factory default file) and leave the switch on for few hours, the switch console appears to be stalled during setup.
The workaround is to reload the switch before you continue to configure it.
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)SE4
•
Authentication, authorization, and accounting (AAA) fails, preventing authentication and requiring you to recover your password. For example, when you enter the aaa authentication login default group tacacs line global configuration command, AAA fails.
There is no workaround.
•
When you use an access control server (ACS) to enable command authorization, the ACS does not process a copy command ending with a colon (for example, scp:, ftp:, tftp:, flash:).
This problem affects authentication, authorization, and accounting (AAA) authorization:
–
–
To workaround is to either deny or permit the copy command without entering any arguments on the ACS.
•
If you repeatedly enter the show tech-support privileged EXEC command, the switch might leak memory and, in some cases, shut down.
The workaround is to reload the switch to clear the memory after repeated use of the show tech-support command.
•
When flow control is enabled on a port-channel interface and you enter the flowcontrol receive on interface configuration command, the bundle is not enabled after the switch restarts. The command appears in the port-channel interface running configuration but does not appear in the switch running configuration. A message such as this appears:
%EC-5-CANNOT_BUNDLE2: Gi0/27 is not compatible with Po1 and will be suspended (flow control receive of Gi0/27 is on, Po1 is off)
%EC-5-CANNOT_BUNDLE2: Gi0/28 is not compatible with Po1 and will be suspended (flow control receive of Gi0/28 is on, Po1 is off)Use one of these workarounds:
–
–
event manager applet Add_flowcontrol_on_restart
event syslog pattern SYS-5-RESTART
action 1 cli command "en"
action 2 cli command "conf t"
action 3 cli command "inter port 1"
action 4 cli command "flowcontrol receive on"For action 3, specify the port-channel interface.
•
On a switch that supports Cisco Discovery Protocol (CDP) bypass, when a Cisco IP phone is connected to an 802.1x-enabled switch port that is in single host mode and that has a guest VLAN, a supplicant that does not send an Extensible Authentication Protocol over LAN (EAPOL)-start frame cannot be authorized.
The workaround is to ensure that the supplicant sends an EAPoL-start frame.
•
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 you have configured a login banner by entering the banner login c message c global configuration command and the switch reloads, the output of banner is missing a carriage return, making the format incorrect.
There is no workaround.
•
When you use Auto Smartports macros on an interface that is connected to an Cisco IP phone, the the quality of service (QoS) configuration for that interface is not completed.
The workaround is to enter the no mls qos vlan-based interface configuration command, and then enable QoS for voice over IP (VoIP) by entering the auto qos voip cisco-phone interface configuration command.
•
A switch can fail when an SNMP process attempts to configure dot1x authentication when it is already configured.
There is no workaround.
•
A switch enters a loop in which it continues to fail after it first has failed while starting, and then has failed again while attempting to recover. This failure loop occurs only after you have entered the archive upload-sw privileged EXEC command to write the configuration to a remote server using Secure Copy Protocol (SCP) and when the connection to the remote server is configured for spanning-tree PortFast.
The workaround is to not use SCP to write to the remote server. Use File Transfer Protocol (FTP) or Trivial File Transfer Protocol (TFTP).
•
A memory leak occurs when there is a stuck in active (SIA) state condition for an Enhanced Interior Gateway Routing Protocol (EIGRP) route.
There is no workaround.
•
A switch does not receive SNMP trap and inform messages from the correct interface after you have entered the snmp-server trap-source loopback0 and snmp-server source-interface informs loopback0 global configuration commands.
There is no workaround.
•
When the no mac address-table static mac-addr vlan vlan-id interface interface-id global configuration command is used to remove a dynamically learned MAC address, the switch fails under these conditions:
–
–
There is no workaround.
•
After all member ports are brought up on a switch stack, MAC authentication bypass (MAB) authenticates the stack master ports but not any member switch ports. The symptom occurs after you have entered both the switchport port-security interface configuration command and the dot1x control-direction interface configuration command on the stack interfaces.
The workaround is to enter either the no switchport port-security interface configuration command or the no dot1x control-direction interface configuration command on the stack interfaces.
•
A memory leak occurs on a device that uses Enhanced Interior Gateway Routing Protocol (EIGRP) when the external routes are being exchanged.
The workaround is to stabilize the network to minimize the impact of external route advertisement.
•
When you enter the dot1x pae interface configuration command on a switch access port and then enable an access list in the inbound direction on an ingress switched virtual interface (SVI), the access list does not work, allowing all packets to pass.
The workaround is to enable the access list in the outbound direction on the egress SVI.
•
When you enter the no spanning-tree etherchannel guard misconfig global configuration command, enter the write memory privileged EXEC command, and then restart the switch, the spanning-tree etherchannel guard misconfig global configuration command is saved instead of the no form of this command.
There is no workaround.
•
After you have entered the snmp-server host informs global configuration command to enable SNMP informs on a switch, the switch might fail if you enter the show snmp pending user EXEC command.
There is no workaround. Do not enter the show command when SNMP informs are enabled.
•
A Remote Switched Port Analyzer (RSPAN) does not detect IPv6 multicast packets on an RSPAN destination port.
There is no workaround.
•
A switch fails when you enter the show ip ospf interface user EXEC command and then stop the command output at the this line:
Backup Designated router (ID) xx.x.x.x, Interface address xx.x.x.xThe failure occurs when the Backup Designated Router (BDR) neighbor of the switch is shut down while you press Enter or the spacebar to advance the command output.
When the switch fails, it sends this error message:
Unexpected exception to CPUvector 2000, PC = 261FC60There is no workaround.
•
On a switch that is configured for IP routing and that is running Cisco IOS Release 12.2(50)SE or later, Cisco Express Forwarding (CEF) can use a large amount of memory. The IP RIB Update process uses about 2000 bytes for each prefix that CEF uses.
There is no workaround. You can reduce the memory use by reducing the number of routes the switch processes.
•
After you have entered the logging filter global configuration command on a switch to specify a syslog filter module to be used by the Embedded Syslog Manager (ESM), processes logging many system messages retain increasing amounts of processor memory.
The workaround is to enter the no logging filter global configuration command.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE3
•
A switch no longer fails when you enter the configure replace privileged EXEC command, and a banner is already present in the switch configuration.
•
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.
•
Re-authentication now occurs on a port under these conditions:
–
–
–
•
If a link failure occurs on a secondary edge port, preemption now occurs after the link comes up.
•
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.
•
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.
•
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.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE2
•
A switch running 12.2(50)SE or later no longer might unexpectedly restart when Auto Smart Ports is enabled and the switch is configured for SSH or the HTTP secure server is enabled by entering the ip http secure-server global configuration command.
•
The switch no longer fails when you use the vacant-message line configuration command.
•
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.
•
A switch no longer randomly resets due to memory corruption.
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
This section describes the caveats that have been resolved in this release:
•
If a port-based ACL (PACL) is applied to an 802.1x-enabled port and the client is then disconnected from that port, the PACL is now removed from the port.
•
When you remove and reconfigure a loopback interface, it now appears in the ifTable.
•
DHCP snooping now works when the switch is in VTP server mode and VLANs with IDs greater than 255 (256 and above) are created.
•
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.
•
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 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.
•
A switch port configured for IGMP snooping no longer loses 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
This section provides updates to the product documentation:
•
•
Update to the Software Configuration Guide
This text was updated in the "Using IEEE 802.1x Authentication with Guest VLAN section of the software configuration guide:
If the switch is trying to authorize an IEEE 802.1x-capable voice device and the AAA server is unavailable, the authorization attempt fails, but the detection of the EAPOL packet is saved in the EAPOL history. When the AAA server becomes available, the switch authorizes the voice device. However, the switch no longer allows other devices access to the guest VLAN. To prevent this situation, use one of these command sequences:
•
•
System Messages Guide
These are the documentation updates for the system modesties guide:
•
•
•
New System Messages
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. [enet] is the supplicant MAC address, and [chars] is the interface. This message might appear if the IEEE 802.1x feature is enabled.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, manually remove it from that port.
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 %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-6-PORTADD_ALL_VLANS: [chars] added to all VlansExplanation The interface has been added to all VLANs. [chars] is the added interface.
Recommended Action No action is required.
Error Message SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all VlansExplanation The interface has been deleted from all VLANs. [chars] is the deleted interface.
Recommended Action No action is required.
Error Message SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].Explanation The VLAN Trunking Protocol (VTP) domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.
Recommended Action No action is required.
Error Message VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit.Explanation The system has shut down the specified interface because too many hosts have requested access to that interface. [chars] is the interface name.
Recommended Action To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command.
Error Message VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response.Explanation The VLAN membership policy server (VMPS) has specified a VLAN name that is unknown to the switch. [chars] is the VLAN name.
Recommended Action Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.
Error Message WCCP-5-CACHEFOUND: Web Cache [IP_address] acquired.Explanation The switch has acquired the specified web cache. [IP_address] is the web cache IP address.
Recommended Action No action is required.
Error Message WCCP-1-CACHELOST: Web Cache [IP_address] lost.Explanation The switch has lost contact with the specified web cache. [IP_address] is the web cache IP address.
Recommended Action Verify the operation of the web cache by entering the show ip wccp web-cache privileged EXEC command.
Changed System Messages
This system message has changed (both explanation and action).
Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will remain stand-alone.Explanation The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel. The second [chars] is the port number.
Recommended Action Ensure that the other ports in the bundle have the same configuration.
Deleted System Messages
These system messages have been deleted.
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
These documents provide complete information about the switch and are available from the HP web site:
•
(part number 383623-001)•
•
(part number 380260-001)•
•
(part number 380263-001)•
•
Cisco IOS Release 12.2 documentation is available at
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/index.html
Technical support
Before you contact HP
Be sure to have the following information available before you call HP:
•
•
•
•
•
•
•
HP contact information
For the name of the nearest HP authorized reseller:
•
•
For HP technical support:
•
–
–
•
Feedback