Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(35)SE
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 IOS Release Number
Updates to Software Configuration Guide
Update to the "Configuring IEEE 802.1x chapter
Updates to the Command Reference
Updates to the System Message Guide
Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(35)SE
Revised: May 22, 2007
These release notes include important information about this Cisco IOS release 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.
Note
The documentation for the CGESM switch refers to IOS Release 12.2(25)SE. For a complete list of these documents, see the "Documentation Notes" section.
This document provides updates to Cisco IOS Release 12.2(35)SE
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
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
Table 2 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.
Note
Table 2 Supported Operating Systems and Browsers
Windows 2000
None
5.5 or 6.0
7.1
Windows XP
None
5.5 or 6.0
7.1
1 Service Pack 1 or higher is required for Internet Explorer 5.5.
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.
New Software Feature
This release supports Web authentication to authenticate a supplicant (client) that does not support IEEE 802.1x functionality. For more information, see the "Documentation Updates" section.
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
Major Features
This release supports web authentication for authenticating a supplicant (client) that does not support IEEE 802.1x functionality. For more information, see the "Documentation Updates" section.
Minimum Cisco IOS Release for Major Features
Table 3 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:
•
•
are ignored. The workaround is to wait until you see the IP address appear when it is provided by the DCHP server.•
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 Mbps 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)
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
These are the IP telephony limitations:
•
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
If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, the switch can fail. The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
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
These are the hardware limitations and restrictions:
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)
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 IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
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 IOS Release Number
These documents refer to Release 12.2(25)SE. The correct release is Release 12.2(25)SE1.
•
•
•
Open Caveats
These sections describe the open caveats with possible unexpected activity in this software release:
•
Open IOS Caveats
These severity 3 Cisco IOS configuration caveats apply to the CGESM switch:
•
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 not removed from the port.
There is no workaround.
•
When you power on or restart a switch that does not have a config.text file in flash memory, the switch tries to get configuration files from a TFTP server. If the configuration files are not found, the switch automatically configures the service config global configuration command, which causes the switch to continue searching (in the background) for the expected configuration files.
If the service config command does not find the configuration files, these error messages appear:
%Error opening tftp://255.255.255.255/network-confg (Timed out)%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)%Error opening tftp://255.255.255.255/router-confg (Timed out)%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)These system messages also appear:
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/network-confg) failed00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/cisconet.cfg) failed00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/switch-confg) failed00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/ciscortr.cfg) failedThese messages are for information only. There is no problem with the switch operation.
Because the switch automatically configures the service config global configuration command, it is in the switch startup-config file when you save the running-config file. This command runs every time the switch is restarted, even if a config.text configuration file is in the switch flash memory.
The workaround is to prevent these messages from being generated. To do this, enter the switch configuration mode, and issue the no service config command. Save the configuration to flash by using the copy running-config to startup-config command. The preceding error and system messages no longer appear and do not appear when the switch is restarted.
•
When using SNMP, the CGESM switch returns an incorrect value of 65534 for the ciscoFlashPartitionFileCount MIB; the switch actually contains 1367 files.
There is no workaround.
•
If traffic is passing through VMPS ports and you perform a shut operation, a dynamic VLAN is not assigned and a VLAN with a null ID appears.
The workaround is to clear the MAC address table. This forces the VMPS server to correctly reassign the VLAN.
•
Sometimes interfaces Gi0/23 & Gi0/24 will not link up with another switch when the interface speed is set to an explicit value instead of autonegotiated. This does not happen when a copper SFP is used with interfaces Gi0/17 - Gi0/20.
The workaround is to autonegotiate the speed with the other device, or to use a different cable type. Use a straight through cable for switch to switch connection, or a cross-over cable for switch to any non switch device connection. If the other device is capable of auto MDIX even with speed not set to auto, then use that. When an improper cable is used only one side of the connection needs to use auto MDIX to achieve a link.
•
When IGMP snooping is enabled and an EtherChannel member interface goes down, the switch might stop forwarding multicast traffic on the EtherChannel. This problem occurs when the EtherChannel interface is a member of a multicast group that is not directly connected (that is, the multicast group that does not have the C flag set in the show ip mroute privileged EXEC command output).
The workaround is to either disable IGMP snooping, or to use the clear ip mroute user EXEC command to refresh all the routes.
•
When you apply the mls qos trust dscp global configuration command to a port, this error message might appear.
Master sets trust failed, sets to untrust modetrust type update
failed on ifc GigabitEthernetx/x
Switch(config-if)#Tcam write failed trust dscp
%QOSMGR-4-COMMAND_FAILURE: Execution of slave:HQM_IDBTRUST_CMD
command failed on GigabitEthernetx/x
The workaround is to apply the sdm prefer qos global configuration command before you enter the mls qos trust dscp global configuration command.
•
When you remove and reconfigure a loopback interface, it does not appear in the ifTable.
The workaround is to reload the switch.
•
If the switch is in VTP server mode and VLANs with IDs greater than 255 (256 and above) are created, DHCP snooping does not work properly on these VLANs.
The workaround is to put the switch in VTP transparent mode before creating the VLANs.
•
When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is within the configured rate limit, the port might go into an error-disabled state.
The workaround is to configure the burst interval to more than 1 second.
•
If a switch is connected to a third-party router through an EtherChannel and the EtherChannel is running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel might go down after you enter the switchport trunk native vlan vlan-id interface configuration command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.
These are the workarounds. You only need to do one of these:
–
–
•
When dynamic ARP inspection is enabled and IP validation is disabled, the switch drops ARP requests that have a source address of 0.0.0.0.
The workaround is to configure an ARP access control list (ACL) that permits IP packets with a source IP address of 0.0.0.0 (and any MAC) address) and apply the ARP ACL to the desired DAI VLANs.
•
When MAC addresses are learned on an Etherchannel port, the addresses are incorrectly deleted from the MAC address table even when the MAC address table aging timeout value is configured to be longer than the ARP timeout value. This causes intermittent unicast packet flooding in the network.
The MAC address is automatically relearned after the ARP refresh. The workaround is to enter the ping ip address privileged EXEC command from the switch to the next hop router to avoid the intermittent flooding.
•
When you configure an IP address on a switch virtual interface (SVI) with DCHP and enable DHCP snooping on the SVI VLAN, the switch SVI cannot obtain an IP address.
The workaround is to not enable DCHP snooping on the SVI VLAN or to use a static IP address for the SVI.
•
During repeated reauthentication of supplicants on an IEEE 802.1x-enabled switch, if the RADIUS server is repeatedly going out of service and then coming back up, the available switch memory might deplete over time, eventually causing the switch to shut down.
There is no work-around, except to ensure that the RADIUS server is stable.
•
If IEEE 802.1x critical authentication is not enabled and the RADIUS authentication server is temporarily unavailable during a reauthentication, when the RADIUS server comes back up, MAC authentication bypass (MAB) does not authenticate a previously authenticated client.
The workaround is to enter the shutdown interface configuration command followed by the no shutdown command on the port connected to the client. An alternative, to prevent the problem from occurring, is to enable critical authentication by entering the dot1x critical {eapol | recovery delay milliseconds} global configuration command.
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.
Open Device Manager Caveats
This is the severity 3 device manager caveat for this release:
•
If you enter the letter i by itself in the port description, the VLAN status column displays i; this only occurs when you are using Device Manager through Netscape 7.1.
The workaround is to run Device Manager through Internet Explorer if you must enter a port description with only the value "i."
Resolved Caveats
These sections describe the resolved caveats for the CGESM switch:
•
When an SNMP version 3 user is configured with the encrypted option and password, the switch no longer reloads when the MIB object usmUserAuthKeyChange is set.
•
If you entered the letter i by itself in the port description, the VLAN status column no longer displays only i ; this only occurred when you were using Device Manager through Netscape 7.1.
•
no longer appear:
%Error opening tftp://255.255.255.255/network-confg (Timed out)%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)%Error opening tftp://255.255.255.255/router-confg (Timed out)%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)These system messages also appeared:
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from(tftp://255.255.255.255/network-confg) failed00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from(tftp://255.255.255.255/cisconet.cfg) failed00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from(tftp://255.255.255.255/switch-confg) failed00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from(tftp://255.255.255.255/ciscortr.cfg) failed•
When using SNMP, the switch no longer returns an incorrect value of 65534 for the ciscoFlashPartitionFileCount MIB.
•
When an IEEE 802.1x restricted VLAN is configured on a port and a hub with multiple devices are connected to that port, syslog messages are now generated.
This is not a supported configuration. Only one host should be connected to an IEEE 802.1x restricted VLAN port.
•
Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
–
–
–
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
•
Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
–
–
–
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
•
An extra index no longer appears in the port table of the ciscoStpExtensions MIB.
•
When you configure a Cisco IP Phone to use Network Admission Control, the CDP packet is no longer delayed, and the phone is no longer identified as an agentless host without an identity profile.
•
When a Cisco device is configured for Network Admission Control and the EAP over UDP port number changes from its default value and then changes back with the eou default switch configuration command, the port change now takes effect.
•
When you configure a MAC address filter by entering the mac-address-table static vlan drop global configuration command, IEEE 802.1X no longer authenticates supplicants using that address. If a supplicant with that address is authenticated, its authorization is revoked.
•
The interfaces GigabitEthernet0/23 and 0/24 now link to another switch or host when the interface speed is set to an explicit value or auto-MDIX is disabled.
•
When you remove the bridge topology change trap with the no snmp-server enable traps bridge topologychange configuration command, the stpx root-inconsistency trap is now active.
•
When IGMP snooping is enabled and an EtherChannel member interface goes down, the switch now forwards multicast traffic on the rest of the EhternetChannel member interfaces.
•
When you enter the show interfaces transceiver properties privileged EXEC command for a Gigabit Ethernet dual-media interface and the interface is set to media-type rj45, the output now shows the correct attached SFP module. This only applies to GigabitEthernet0/17 to 0/20.
•
A vulnerability has been discovered in a third party cryptographic library which is used by a number of Cisco products. This vulnerability may be triggered when a malformed Abstract Syntax Notation One (ASN.1) object is parsed. Due to the nature of the vulnerability it may be possible, in some cases, to trigger this vulnerability without a valid certificate or valid application-layer credentials (such as a valid username or password).
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
The vulnerable cryptographic library is used in the following Cisco products:
–
–
–
–
–
This vulnerability is also being tracked by CERT/CC as VU#754281.
Cisco has made free software available to address this vulnerability for affected customers. There are no workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
Note
•
When you apply the mls qos trust dscp global configuration command to a port, this error message no longer appears:
Master sets trust failed, sets to untrust modetrust type updatefailed on ifc GigabitEthernetx/xSwitch(config-if)#Tcam write failed trust dscp%QOSMGR-4-COMMAND_FAILURE: Execution of slave:HQM_IDBTRUST_CMDcommand failed on GigabitEthernetx/x
•
When you remove and reconfigure a loopback interface, it no longer appears in the ifTable.
•
Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
–
–
–
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
•
If a switch is connected to a third-party router through an EtherChannel and the EtherChannel is running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel no longer fail after you enter the switchport trunk native vlan vlan-id interface configuration command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.
Documentation Updates
This section provides these updates:
•
•
•
Updates to Software Configuration Guide
This section was added to the "Configuring EtherChannels" chapter:
When you configure one end of an EtherChannel in either PAgP or LACP mode, the system negotiates with the other end of the channel to determine which ports should become active. In previous releases, the incompatible ports were suspended. Beginning with Cisco IOS Release 12.2(35)SE, instead of a suspended state, the local port is put into an independent state and continues to carry data traffic as would any other single link. The port configuration does not change, but the port does not participate in the EtherChannel.
Update to the "Configuring IEEE 802.1x chapter
These sections were added to the "Configuring IEEE 802.1x" chapter:
Using Web Authentication
You can use a web browser to authenticate a client that does not support IEEE 802.1x functionality.
You can configure a port to use only web authentication. You can also configure the port to first try and use IEEE 802.1x authentication and then to use web authorization if the client does not support IEEE 802.1x authentication.
Web authentication requires two Cisco Attribute-Value (AV) pair attributes:
•
•
For example:
proxyacl# 10=permit ip any 10.0.0.0 255.0.0.0proxyacl# 20=permit ip any 11.1.0.0 255.255.0.0proxyacl# 30=permit udp any any eq syslogproxyacl# 40=permit udp any any eq tftp
Note
For more information, see the "Configuring Web Authentication" section.
Configuring Web Authentication
Beginning in privileged EXEC mode, follow these steps to configure authentication, authorization, accounting (AAA) and RADIUS on a switch before configuring web authentication. The steps enable AAA by using RADIUS authentication and enable device tracking.
This example shows how to enable AAA, use RADIUS authentication and enable device tracking:
Switch(config) configure terminalSwitch(config)# aaa new-modelSwitch(config)# aaa authentication login default group radiusSwitch(config)# aaa authorization auth-proxy default group radiusSwitch(config)# radius-server host key key1Switch(config)# radius-server attribute 8 include-in-access-reqSwitch(config)# radius-server vsa send authenticationSwitch(config)# ip device trackingSwitch(config) endBeginning in privileged EXEC mode, follow these steps to configure a port to use web authentication:
This example shows how to configure only web authentication on a switch port:
Switch# configure terminalSwitch(config)# ip admission name rule1 proxy httpSwitch(config)# interface gigabit1/0/1Switch(config-if)# switchport mode accessSwitch(config-if)# ip access-group policy1 inSwitch(config-if)# ip admission rule1Switch(config-if)# endBeginning in privileged EXEC mode, follow these steps to configure a switch port for IEEE 802.1x authentication with web authentication as a fallback method:
This example shows how to configure IEEE 802.1x authentication with web authentication as a fallback method.
Switch(config) configure terminalSwitch(config)# ip admission name rule1 proxy httpSwitch(config)# fallback profile fallback1Switch(config-fallback-profile)# ip access-group default-policy in Switch(config-fallback-profile)# ip admission rule1Switch(config-fallback-profile)# exitSwitch(config)# interface gigabit1/0/1Switch(config-if)# switchport mode accessSwitch(config-if)# dot1x port-control autoSwitch(config-if)# dot1x fallback fallback1Switch(config-if)# endFor more information about the ip admission name and dot1x fallback commands, see the command reference for this release.
Updates to the Command Reference
These commands were added:
dot1x fallback
Use the dot1xfallback interface configuration command on the switch stack or on a standalone switch to configure a port to use web authentication as a fallback method for clients that do not support IEEE 802.1x authentication. To return to the default setting, use the no form of this command.
dot1x fallback profile
no dot1x fallback
Syntax Description
Defaults
No fallback is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must enter the dot1x port-control auto interface configuration command on a switch port before entering this command.
Examples
This example shows how to specify a fallback profile to a switch port that has been configured for IEEE 802.1x authentication:
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitethernet1/0/3Switch(config-if)# dot1x fallback profile1Switch(config-fallback-profile)# exitSwitch(config)# endYou can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
fallback profile
Use the fallback profile global configuration command on the switch stack or on a standalone switch to create a fallback profile for web authentication. To return to the default setting, use the no form of this command.
fallback profile profile
no fallback profile
Syntax Description
Defaults
No fallback profile is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
The fallback profile is used to define the IEEE 802.1x fallback behavior for IEEE 802.1x ports that do not have supplicants. The only supported behavior is to fall back to web authentication.
After entering the fallback profile command, you enter profile configuration mode, and these configuration commands are available:
•
•
•
Examples
This example shows how to create a fallback profile to be used with web authentication:
Switch# configure terminalSwitch(config)# ip admission name rule1 proxy httpSwitch(config)# fallback profile profile1Switch(config-fallback-profile)# ip access-group default-policy in Switch(config-fallback-profile)# ip admission rule1Switch(config-fallback-profile)# exitSwitch(config)# interface gigabitethernet 1/0/1Switch(config-if)# dot1x fallback profile1 Switch(config-if)# endYou can verify your settings by entering the show running-configuration [interface interface-id] privileged EXEC command.
Related Commands
ip admission
Use the ip admission interface configuration command to enable web authentication. You can also use this command in fallback-profile mode. Use the no form of this command to disable web authentication.
ip admission rule
no ip admission
Syntax Description
Command Modes
Global configuration
Command History
Usage Guidelines
The ip admission command applies a web authentication rule to a switch port.
Examples
This example shows how to apply a web authentication rule to a switchport:
Switch# configure terminalSwitch(config)# interface gigabitethernet1/0/1Switch(config-if)# ip admission rule1This example shows how to apply a web authentication rule to a fallback profile for use on an IEEE 802.1x enabled switch port.
Switch# configure terminalSwitch(config)# fallback profile profile1Switch(config)# ip admission name rule1Switch(config)# endRelated Commands
ip admission name proxy http
Use the ip admission name proxy http global configuration command to enable web authentication. Use the no form of this command to disable web authentication.
ip admission name proxy http
no ip admission name proxy http
Syntax Description
This command has no arguments or keywords.
Defaults
Web authentication is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The ip admission name proxy http command globally enables web authentication on a switch.
After you enable web authentication on a switch, use the ip access-group in and ip admission web-rule interface configuration commands to enable web authentication on a specific interface.
Examples
This example shows how to configure only web authentication on a switchport:
Switch# configure terminalSwitch(config) ip admission name http-rule proxy httpSwitch(config)# interface gigabitethernet1/0/1Switch(config-if)# ip access-group 101 inSwitch(config-if)# ip admission ruleSwitch(config-if)# endThis example shows how to configure IEEE 802.1x authentication with web authentication as a fallback mechanism on a switchport.
Switch# configure terminalSwitch(config)# ip admission name rule2 proxy httpSwitch(config)# fallback profile profile1Switch(config)# ip access group 101 inSwitch(config)# ip admission name rule2Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# dot1x port-control autoSwitch(config-if)# dot1x fallback profile1Switch(config-if)# endRelated Commands
show fallback profile
Use the show fallback profile privileged EXEC command to display the fallback profiles that are configured on a switch.
show fallback profile [ append | begin | exclude | include | { [redirect | tee ] url } expression ]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show fallback profile privileged EXEC command to display profiles that are configured on the switch.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain Output are displayed.
Examples
This is an example of output from the show fallback profile command:
switch# show fall profileProfile Name: dot1x-www------------------------------------Description : NONEIP Admission Rule : webauth-fallbackIP Access-Group IN: default-policyProfile Name: dot1x-www-lpip------------------------------------Description : NONEIP Admission Rule : web-lpipIP Access-Group IN: default-policyProfile Name: profile1------------------------------------Description : NONEIP Admission Rule : NONEIP Access-Group IN: NONERelated Commands
Updates to the System Message Guide
These system messages were added to the system message guide:
Error Message DOT1X-5-SECURITY_VIOLATION: Security violation on the interface [chars], new MAC address [enet] is seen.Explanation A host on the specified interface is trying to access the network or to authenticate in a host mode that does not support the number of hosts attached to the interface. This is a security violation, and the port is put in the error-disabled state.
Recommended Action Ensure that the interface is configured to support the number of attached hosts. Enter the shutdown interface configuration command and then the no shutdown interface configuration command to restart the port.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot be equivalent to the Voice VLAN.Explanation The IEEE 802.1x-assigned VLAN on a port cannot be the same as the voice VLAN. [dec] is the data VLAN ID, and [chars] is the port.
Recommended Action Configure either a different voice VLAN or a different IEEE 802.1x-assigned access VLAN on the interface. The authentication then proceeds normally on the next retry.
Error Message FRNTEND_CTRLR-1-MGR_TXQ_FULL: The front end controller Tx queue reached watermark levelExplanation There are too many messages in the queue between the front-end controller and the switch software.
Recommended Action Try reloading the switch. If this does not resolve the issue, this might be a hardware problem. Contact the Cisco technical support representative.
Error Message GBIC_SECURITY_CRYPT-4-ID_MISMATCH: Identification check failed for GBIC in port [chars]Explanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP module, but the system could not verify its identity. [chars] is the port.
Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software. Otherwise, verify that the SFP module was obtained from Cisco or from a supported vendor.
Error Message GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR: GBIC in port [chars] manufactured by an unrecognized vendorExplanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP module, but the switch could not match its manufacturer with one on the known list of Cisco SFP module vendors. [chars] is the port.
Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software.
Error Message GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port [chars] has bad crcExplanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP module, but it does not have a valid cyclic redundancy check (CRC) in the EEPROM data. [chars] is the port.
Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software. Even if the switch does not recognize the SFP module, it might still operate properly but have limited functionality.
Error Message PHY-4-UNSUPPORTED_SFP_CARRIER: Unsupported SFP carrier module found in [chars]Explanation The switch has identified the small form-factor pluggable (SFP) module as an unsupported non-Cisco SFP module. [chars] is the interface.
Recommended Action Remove the unsupported SFP module, and use a supported module.
Error Message PORT_SECURITY-6-ADDR_REMOVED: Address [dec]:[enet] exists on port [chars]. It has been removed from port [chars].Explanation A routed port is reconfigured as a switch port. The address in the previous switch configuration conflicts with the running configuration and has been deleted. [dec]:[enet] is the MAC address of the port. [chars] is the reconfigured port.
Recommended Action No action is required.
Error Message WCCP-5-SERVICEFOUND: Service [chars] acquired on WCCP Client [IP_address]Explanation Web Cache Communication Protocol (WCCP) has found a service on the specified WCCP client. [chars] is the name of the service, and [IP_address] is the client IP address.
Recommended Action No action is required.
Error Message WCCP-1-SERVICELOST: Service [chars] lost on WCCP Client [IP_address]Explanation WCCP has lost the service associated with the specified WCCP client. [chars] is the name of the service, and [IP_address] is the client IP address.
Recommended Action Verify the operational state of the WCCP client.
These system messages were updated in the system message guide:
Error Message EC-5-CANNOT_BUNDLE_LACP: [chars] is not compatible with aggregators in channel [dec] and cannot attach to them ([chars]).Explanation The port has different port attributes than the port channel or ports within the port channel. [chars] is the incompatible port. [chars] is the short interface name, such as Gi1/0/1 on a Catalyst 3750 switch, [dec] is the channel group number, and the last [chars] is the reason.
Recommended Action For the port to join the bundle, change the port attributes so that they match the port.
Error Message EC-5-DONTBNDL: [chars] suspended: incompatible remote port with [chars]Recommended Action The configuration of the remote port differs from the configuration of other remote ports in the bundle. A port can only join the bundle when its global configuration and the configuration of the remote port are the same as other ports in the bundle. The first [chars] is the suspended local interface, and the second [chars] is the local interface that is already bundled.
Error Message PORT_SECURITY-6-VLAN_REMOVED: VLAN [int] is no longer allowed on port [chars]. Its port security configuration has been removed.Explanation A configured VLAN has been excluded either due to a port-mode change or an allowed VLAN list change and is removed from the configuration. [int] is the VLAN ID, and [chars] is the switch port assigned to the VLAN.
Recommended Action No action is required.
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