 Feedback
|
Table Of Contents
Release Notes for Catalyst 2350 Switch, Cisco IOS Release 12.2(55)SE and Later
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Cisco X2 Transceiver Modules and SFP Modules
Caveats Resolved in Cisco IOS Release 12.2(55)SE8
Caveats Resolved in Cisco IOS Release 12.2(55)SE7
Caveats Resolved in Cisco IOS Release 12.2(55)SE6
Caveats Resolved in Cisco IOS Release 12.2(55)SE5
Caveats Resolved in Cisco IOS Release 12.2(55)SE4
Caveats Resolved in Cisco IOS Release 12.2(55)SE3
Caveats Resolved in Cisco IOS Release 12.2(55)SE1
Caveats Resolved in Cisco IOS Release 12.2(55)SE
Updates to the Software Configuration Guide VTP Chapter
Configuring a VTP Version 3 Password
Configuring a VTP Version 3 Primary Server
Configuring VTP on a Per-Port Basis
Other Updates to the Software Configuration Guide
Updates to the Command Reference
Updates for the System Message Guide
Update for the Getting Started Guide
Obtaining Documentation and Submitting a Service Request
Release Notes for Catalyst 2350 Switch, Cisco IOS Release 12.2(55)SE and Later
Revised June 28, 2013
Cisco IOS Release 12.2(55)SE runs on all Catalyst 2350 switches.
These release notes include important information about Cisco IOS Release 12.2(55)SE and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/web/download/index.htmlContents
•
•
•
•
•
•
•
•
System Requirements
•
•
Supported Hardware
Table 1 Supported Hardware
Catalyst 2350-48TD-S
48 10/100/1000 Ethernet ports,
2 10-Gigabit Ethernet X2 module slots, AC powerCisco IOS Release 12.2(46)EY
Catalyst 2350-48TD-SD
48 10/100/1000 Ethernet ports,
2 10-Gigabit Ethernet X2 module slots, DC powerCisco IOS Release 12.2(46)EY
Cisco X2 transceiver modules
X2-10GB-SR V02 or later
X2-10GB-CX4 V03 or later
X2-10GB-LRMCisco IOS Release 12.2(46)EY
Cisco TwinGig Converter Module
Dual SFP X2 converter module to allow the switch to support SFP1 Gigabit Ethernet modules
Cisco IOS Release 12.2(46)EY
SFP modules
1000BASE-SX
1000BASE-TCisco IOS Release 12.2(46)EY
DOM2 support for these SFP modules
X2-10GB-SR
X2-10GB-LRMCisco IOS Release 12.2(46)EY
SFP module patch cable3
CAB-SFP-50CM
Cisco IOS Release 12.2(46)EY
C3K-PWR-265WAC
265-W AC-power-supply module
Cisco IOS Release 12.2(46)EY
C3K-PWR-265WDC
265-W DC-power-supply module
Cisco IOS Release 12.2(46)EY
C3K-BLWR-60CFM
Fan module
Cisco IOS Release 12.2(46)EY
1 SFP = small form-factor pluggable.
2 DOM = digital optical monitoring.
3 The SFP module patch cable is a 0.5-meter, copper, passive cable with SFP module connectors at each end. The patch cable can connect two
Catalyst 2350 switches in a cascaded configuration.
Device Manager System Requirements
Hardware
Table 2 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1 GB DRAM.
Software
•
•
The device manager verifies the browser version when starting a session does not require a plug-in.
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. Use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.
CNA Support
Cisco Network Assistant 5.4 and earlier does not provide specific device support for the Catalyst 2350 switch. For more information about Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
•
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Table 3 Cisco IOS Software Image Files
c2350-lanlitek9-tar.122-55.SE.tar
Catalyst 2350 cryptographic image file and device manager files. This image has SSH features.
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current
Cisco IOS release and the Cisco IOS release from which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps6969/ps1835/prod_bulletin0900aecd80281c0e.htmlYou can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2:
|http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_t1.htmlUpgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an new image file and replace or keep the current image.
Step 1
Step 2
a.
http://www.cisco.com/cisco/web/download/index.html
b.
c.
d.
e.
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 a default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/c2350-lanlite-tar.122-46.EY.tarThis example shows how to download an image from a TFTP server and keep the current image by replacing the /overwrite option with the /leave-old-sw option:
Switch# archive download-sw /leave-old-sw tftp://198.30.20.19/c2350-lanlite-tar.122-46.EY.tar
Recovering from a Software Failure
For recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
New Software Features
•
Configuration Notes
Use these methods to assign IP information to your 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.
Cisco IOS Limitations
•
•
Address Resolution Protocol
•
The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem.(CSCse06827)
Cisco X2 Transceiver Modules and SFP Modules
•
–
–
•
Configuration
•
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)
•
The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command. (CSCsk65142)
•
upand sometimes asdown, resulting in conflicts. This status depends on when you respond to the reboot query:
Would you like to enter the initial configuration dialog?–
down. This is the correct state.–
up) occurs if you respond to the query before VLAN 1 line status appears on the console.The workaround is to wait for approximately 1 minute after rebooting and until the VLAN 1 interface line status appears on the console before you respond to the query. (CSCsl02680)
Multicasting
•
•
–
–
–
The workaround is to disable the IGMP snooping throttle limit by using the no ip igmp max-groups number interface configuration command and then to reconfigure the same limit again. (CSCse39909)
QoS
•
There is no workaround. (CSCeh18677)
•
There is no workaround. (CSCsc63334)
•
The workaround is to use a different name for the interface-level policy map. (CSCsd84001)
•
There is no workaround. (CSCsd72001)
•
•
01:01:32: %BIT-4-OUTOFRANGE: bit 1321 is not in the expected range of 0 to 1024There is no impact to switch functionality.
There is no workaround. (CSCtg32101)
SPAN and RSPAN
•
There is no workaround. This is a hardware limitation. (CSCei10129)
Device Manager Limitations
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Important Notes
•
Cisco IOS Notes
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.
Device Manager Notes
•
•
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:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
•
Open Caveats
•
When you disable an interface and configure voice and data on the same VLAN and enable the interface:
–
–
When you configure voice and data on the same VLAN on an enabled interface, it causes a security violation and an error message is displayed.
In both cases the workaround is to configure voice and data on separate VLANs.
The workaround is to use port security without dot1x authentication.
•
If the switch is in multidomain authorization (MDA) mode and it receives three or more MAC addresses simultaneously or if the switch is in single-host mode and it receives two or more MAC addresses simultaneously, a security violation trap occurs in the shutdown and protect violation modes.
The workaround is to connect one device at a time.
•
If you have configured web authentication on a switch stack as the fallback method and the stack elects a new stack master, the default access control entry (ACE) in the access control list (ACL) changes from implicit deny (auth-default-ACL) to implicit permit (auth-default-ACL-open) even if the port is in closed authentication mode.
The workaround is to enter the shutdown interface configuration command followed by the no shutdown interface configuration command to re-enable the interface.
•
If you configure multidomain authentication (MDA) with Open1x authentication and the restrict violation mode, a security violation occurs if the MAC address on the voice LAN is the last MAC address that the switch receives. However, the MAC address is added to the table as a dynamic MAC address and the connected data VLANs continue to access the interface.
The workaround is to connect the voice device first.
•
In the multidomain authentication (MDA) mode, if you configure the network-policy profile global configuration command and you remove a voice VLAN at the interface level after authentication, tracebacks and error messages are generated.
There is no workaround.
•
If the switch sends untagged and non-CDP traffic in the single-host or multiple-hosts mode after the phone configuration is removed and the Cisco Discovery Protcol (CDP) cache on the switch is cleared, the CDP bypass feature does not work.
The work around is to enter the shutdown interface configuration command followed by the no shutdown interface configuration command to restart the interface.
•
A port that is programatically configured with auth-default ACL does not allow any traffic on the switch except DHCP traffic. If the configurations on the interface are cleared and the interface is restarted, the auth-default ACL configuration remains and the problem persists.
There is no workaround.
Resolved Caveats
•
•
•
•
•
•
•
•
Caveats Resolved in Cisco IOS Release 12.2(55)SE8
•
When a Terminal Access Controller Access Control System (TACACS) server is configured with a single connection, the CPU usage is high.
The workaround is to remove the single connection option.
•
Cisco IOS IP SLAs probes fail because the control message is blocked. The firewalls block the control message when a response packet is not returned to the originating port.
The workaround is to disable IP SLAs control messages for this probe instance.
•
The snmp-server group command does not associate both IPv6 and IPv4 ACLs simultaneously with an SNMP group.
The workaround is to use the snmp-server user command, which associates both IPv4 and IPv6 ACLs with an SNMP user.
•
When a switch is configured with Cisco IOS IP SLAs FTP GET operation and if the target file is unavailable, the switch experiences a memory leak and may become unresponsive if it runs out of memory.
The workaround is to configure the Cisco IOS IP SLAs FTP GET operation only after verifying the availability of the remote target file and setting the permissions for the file, as appropriate. This allows the switch to retrieve the file and not experience a memory leak.
•
When manually running on-demand diagnostic tests on a stack member using the diagnostic start switch number test all interface configuration command, the test TestPortAsicRingLoopback fails arbitrarily.
The workaround is to run only the TestPortAsicRingLoopback test (diagnostic start switch number test 4 interface configuration command) on the stack member. Isolate the stack member and then run the diagnostic start switch number test all interface configuration command on the rest of the stack.
Caveats Resolved in Cisco IOS Release 12.2(55)SE7
•
The Hot Standby Router Protocol (HSRP) on dot1q sub-interfaces remains in INIT state after a physical link flap on the trunk port.
The workaround is to enter the shutdown and no shutdown command on the interface.
•
IPv6 packets travel randomly between two isolated ports that are in the same VLAN.
There is no workaround.
•
If the switch is configured with Multicast Distributed Switching (MDS), memory leaks if the multicast-routing distributed command is toggled repeatedly.
There is no workaround.
•
Memory leaks (due to SNMP traps) cause the switch to respond slowly to commands; eventually the switch fails. This is observed when more than one SNMP server host is configured, one of the host broadcasts SNMP traps, or the snmp-server enable traps snmp authentication coldstart warmstart command is configured.
The workaround is to disable the snmp-server enable traps snmp authentication coldstart warmstart command and reload the switch.
Caveats Resolved in Cisco IOS Release 12.2(55)SE6
•
The switch processes data packets that are sent to the network address of an interface if the layer-2 frame encapsulating that packet is specifically crafted to target layer-2 address of the interface or a broadcast layer-2 address.
The workaround is to use Cisco Express Forwarding (CEF).
•
High memory usage is seen with the 'Virtual Exec" process.
There is no workaround.
•
Cisco IOS Software and Cisco IOS XE Software contain a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. An attacker could exploit this vulnerability by sending a crafted request to an affected device that has the DHCP version 6 (DHCPv6) server feature enabled, causing a reload.
Cisco has released free software updates that address this vulnerability. This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120926-dhcpv6
•
The sh udld neighbor command does not work.
The workaround is to enable the udld port aggressive command on the interface level once.
•
The switch stops working when you enter the show epm session summary privileged EXEC command.
There is no workaround.
•
In a single connection-enabled Terminal Access Controller Access Control System (TACACS) server, when the primary TACACS server goes down , the authentication fallback to the secondary server fails.
The workaround is to disable the single connection.
•
The switch stops working even after a successful 802.1x authentication of the client.
There is no workaround.
•
A port configured and authenticated with 802.1x security may not correctly detect a loop even if the Bridge Protocol Data Unit (BPDU) guard is configured on the interface. This may result in 100 percent CPU utilization because of the Spanning Tree Protocol (STP) process of the switch.
The workaround is to configure the switch with the authentication open or authentication mac-move permit command.
•
The switch reloads unexpectedly due to segV exception while making PBR configuration changes.
There is no workaround.
•
Traffic that should be dropped or denied by an Access Control List (ACL) is permitted by the switch.
The workaround is to remove and reapply the ACL.
•
When a switch is configured for SNMP and receives SNMP packets from an authenticated user, a successful exploitation causes the affected device to reload. This vulnerability could be exploited repeatedly to cause an extended Denial of Service (DoS) condition.
There is no workaround.
•
Advanced Access Control List (dACL) does not get applied to a switch interface configured for Multi-Domain Authentication (MDA).
The workaround is to modify the dACL name and configuration.
•
ARP is blocked with open authentication-enabled switchports.
The workaround is to run the command clear authentication session.
Caveats Resolved in Cisco IOS Release 12.2(55)SE5
•
During a Telnet session, the router crashes when the TACACS+ server is configured or unconfigured (tacacs-server host command) using the single-connection keyword.
The workaround is to not use the single-connection keyword.
•
When you enter the show running-config interface configuration command, IP Service Level Agreement notifications are shown as enabled even when you have not enabled this configuration using the ip sla enable reaction-alerts interface configuration command.
There is no workaround.
•
If local proxy Address Resolution Protocol (ARP) is configured on the VLAN interface, the ARP entry for the Hot Standby Router Protocol (HSRP) enters into an incomplete state.
The workaround is to remove the proxy ARP feature on the VLAN interface (by using the no ip local-proxy-arp interface configuration command) and restart the interface.
•
When AAA authorization is used with TACACS+, an error is displayed if the banner message (banner exec global configuration command) starts with a blank character.
The workaround is to not start the banner message with a blank character.
•
If the no vtp VLAN configuration command is used on a port that receives VTP updates, the switch does not process Layer 2 control traffic (STP and CDP) after some time.
The workaround is to configure VTP on the port or to not use the no vtp command.
•
CPU usage is high when a device connected to the switch is accessed using the https://IP_address command on the router.
The workaround is to reload the device.
•
The switch crashes when DCHP snooping is enabled with value 125 and an offer packet is received.
There is no workaround.
•
If a Tcl policy is copied to the router, the router fails when an event manager policy is configured.
There is no workaround.
•
If a CLI configuration text file is copied from a Windows system to the switch, a space is appended to the end of the macro description command when the file is read from the flash of the switch. This leads to errors resulting in high CPU utilization on the switch. Another possible issue is that the macro is not removed when the link goes down or the connected device is removed from the switch.
The workaround is to copy the configuration file from a non-Windows system (like UNIX or Linux) or convert the file to an appropriate UNIX format before copying.
•
A vulnerability in the Multicast Source Discovery Protocol (MSDP) implementation of Cisco IOS Software and Cisco IOS XE Software could allow a remote, unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition.
Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available. This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-msdp
•
A vulnerability exists in the Cisco IOS Software that may allow a remote application or device to exceed its authorization level when authentication, authorization, and accounting (AAA) authorization is used. This vulnerability requires that the HTTP or HTTPS server is enabled on the Cisco IOS device.
Products that are not running Cisco IOS Software are not vulnerable.
Cisco has released free software updates that address these vulnerabilities.
The HTTP server may be disabled as a workaround for the vulnerability described in this advisory.
This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-pai
•
The switch crashes due to the "HACL Acl Manager" memory fragmentation when a large access control list (ACL) is modified.
The workaround is add or remove ACE entries in sequential order when the ACL is modified.
•
Routing Information Protocol (RIP) Version 2 packets egressing an 801.1Q tunnel interface are triplicated.
There is no workaround.
•
Cisco IOS Software contains a vulnerability in the Smart Install feature that could allow an unauthenticated, remote attacker to cause a reload of an affected device if the Smart Install feature is enabled. The vulnerability is triggered when an affected device processes a malformed Smart Install message on TCP port 4786.
Cisco has released free software updates that address this vulnerability. There are no workarounds to mitigate this vulnerability.
This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/
cisco-sa-20120328-smartinstall•
If a client switch is authorized using MAC Authentication Bypass (MAB), and then by using the 802.1x standard and dynamic VLAN assignment, the MAC address of the switch is not updated in the MAC address table of slave switches.
The workaround is to not use both the 802.1x and dynamic VLAN assignment configurations for the client switch.
•
The switch crashes when an IP phone that uses LLDP and authenticates itself using MAC Authentication Bypass (MAB) or 802.1x is physically disconnected and reconnected to the switch port.
The workaround is to remove the aaa authorization network default group SG-PBA global configuration command.
Caveats Resolved in Cisco IOS Release 12.2(55)SE4
•
The Dynamic Host Configuration Protocol (DHCP) CLI does not accept white spaces in raw ASCII option in the DHCP pool configuration submode. This issue is seen in Cisco IOS Release 12.4(24)T1 and later.
There is no workaround.
•
In a VPN Routing and Forwarding (VRF) aware setup, messages are not sent to the syslog server. This issue applies to Cisco IOS Release 12.2(53)SE and 12.2(53)SE1. This situation does not occur if system logging is configured in the global table.
•
A memory leak occurs in the SSH process, and user authentication is required.
The workaround is to allow SSH connections only from trusted hosts.
•
If a tunnel interface is configured with Cisco Discovery Protocol (CDP), the switch fails when it receives a CDP packet.
The workaround is to disable CDP on the interface by using the no cdp enable interface configuration command.
•
The switch fails when the Differentiated Services Code Point (DSCP) mutation name is longer than 25 characters.
The workaround is to configure DSCP mutation names with fewer than 25 characters.
•
If Auto Smartports macros are configured, access points with the AIR-CAP prefix are not detected.
The workaround is to manually configure the access point port.
•
Neighbor discovery fails for IPv6 hosts connected to the switch when the IPv6 MLD snooping feature is enabled globally on the switch.
The workaround is to disable IPv6 MLD snooping on the switch.
•
The switch sometimes reloads after a CPU overload, regardless of the process that is overloading the CPU.
This problem has been corrected.
•
If a member switch does not have an access control list (ACL) and is running an Enforcement Policy Module (EPM) session, the client on that interface is re-authorized each time that the switch reloads.
The workaround is to configure an ACL on the interface.
•
The switch fails when DHCP snooping is configured and packet data traffic is excessive. The traffic exhausts the I/O memory and triggers the switch to crash.
There is no workaround.
Caveats Resolved in Cisco IOS Release 12.2(55)SE3
•
A vulnerability exists in the Smart Install feature of Cisco Catalyst Switches running Cisco IOS Software that could allow an unauthenticated, remote attacker to perform remote code execution on the affected device.
Cisco has released free software updates that address this vulnerability.
There are no workarounds available to mitigate this vulnerability other than disabling the Smart Install feature.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-smart-install.shtml.
•
If you configure multidomain authentication (MDA) with Open1x authentication and the restrict violation mode, only two MAC addresses are allowed to access the interface. A security violation occurs when a third MAC address on a voice VLAN tries to access the interface. The voice VLAN is not authenticated, and a syslog message is generated. However, the MAC address is not removed from the voice VLAN because Open1x authentication is configured. If you have authorized the voice VLAN with a policy, such as a dynamic VLAN, the policy is not applied.
The workaround is to not configure a voice VLAN on the phone.
•
When a member switch port security is used with port-based dot1x authentication and the switch MAC address is sticky, a connected device authenticates itself. Its MAC address is added as sticky in the switch configuration and in the port security tables of the stack switches. When the switch is shut down, the device MAC address is removed from the master switch, but it is retained in the member switch security tables. When the interface is re-enabled, the device MAC address is restored to the master switch configuration.
Caveats Resolved in Cisco IOS Release 12.2(55)SE1
•
When you disconnect the spanning tree protocol (STP) peer link, the STP port path cost configuration changes.
There is no workaround.
•
If a static MAC address entry is configured for an IP address in the global routing table, ping requests are sent through the global context, and replies are sent through Virtual Routing and Forwarding (VRF). This is a VRF leak.
The workaround is to remove the static MAC address entry.
Caveats Resolved in Cisco IOS Release 12.2(55)SE
•
Cisco X2-10GB-CX4 transceiver modules with a version identification number lower than V03 might be difficult to insert because of a dimensional tolerance discrepancy.
The workaround is to use modules with a version identification number of V03 or later.
•
The buffer space of a switch running TCP applications is full while the TCP sessions are in the TIME_WAIT state. Buffer space becomes available after the TCP session the closed.
There is no workaround.
•
On a switch running Cisco IOS release 12.2(46)SE, the output of the show interfaces privileged EXEC command shows 0 packets for port channel input and output rates.
The workaround is to reload the switch by entering the reload privileged EXEC command.
•
On switches running Cisco IOS release 12.2(50)SE3 running MAC authentication bypass with multidomain authentication (MDA, IP phones connected to a port might not be able to regain network connectivity in the VOICE domain if the session times out and all RADIUS servers are unreachable.
There is no workaround.
•
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
•
If the RADIUS authentication server is unavailable and inaccessible authentication bypass is enabled, the switch grants the client access to the network by putting the connected port in the critical-authentication state in the RADIUS-configured or the user-specified access VLAN. After the server is available, the client is not reinitalized and moved out of the critical VLAN.
There is no workaround.
•
A PC in 802.1x or multidomain authentication (MDA) mode is connected to an IP phone and connected to a MDA-enabled switch port. After the PC and phone are authenticated on the port, the PC is down. The port does not automatically reauthenticate the PC.
There is no workaround.
•
A switch running Cisco IOS Release 12.2(53)SE1 stops when IEEE 802.1x authentication is enabled.
The workaround is to apply a VLAN that the RADIUS server assigned to the switch.
•
Multidomain authentication (MDA) with guest VLAN or MAC authentication bypass (MAB) as a fallback method is enabled on a switch running Cisco IOS Release 12.2(53)SE. When a non-802.1x client is connected to a IP phone and the phone connected to a switch port shuts down and then restarts, the client MAC address status is drop in the MAC address table. It takes 5 minutes for the client to access the network.
The workaround is to use another software release, such as Cisco IOS Release 12.2(44)SE2.
•
This error message is displayed after copying a configuration file to the running configuration file fails:
%Error opening system:/running-config (No such file or directory)The output of the dir system:/ EXEC command also does not show a running configuration file.
The workaround is to reload the switch.
Documentation Updates
•
•
•
•
•
Updates to the Software Configuration Guide VTP Chapter
Cisco IOS Release 12.2(55)SE adds support for VTP version 3, which introduces these changes:
•
•
Note
•
•
VTP version 3 supports these features that are not supported in versions 1 or 2:
•
•
•
•
By default, all devices come up as secondary servers. You can enter the vtp primary privileged EXEC command to specify a primary server. Primary server status is only needed for database updates when the administrator issues a takeover message in the domain. You can have a working VTP domain without any primary servers. Primary server status is lost if the device reloads or domain parameters change, even when a password is configured on the switch.
•
Globally setting VTP mode to off applies to all the trunking ports in the system. However, you can specify on or off per-VTP instance. For example, you can configure the switch as a VTP server for the VLAN database but with VTP off for the MST database.
VTP v3 Defaults
•
•
•
Configuring the VTP Version
Follow these guidelines when deciding which VTP version to implement:
•
•
Caution
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Caution
Beginning in privileged EXEC mode, follow these steps to configure the VTP version:
To return to the default VTP version 1, use the no vtp version global configuration command.
Configuring the VTP Mode
Beginning in privileged EXEC mode, follow these steps to configure the VTP mode:
Step 1
configure terminal
Enter global configuration mode.
Step 2
vtp domain domain-name
Configure the VTP administrative-domain name. The name can be 1 to 32 characters. All switches operating in VTP server or client mode under the same administrative responsibility must be configured with the same domain name.
This command is optional for modes other than server mode. VTP server mode requires a domain name. If the switch has a trunk connection to a VTP domain, the switch learns the domain name from the VTP server in the domain.
You should configure the VTP domain before configuring other VTP parameters.
Step 3
vtp mode {client | server | transparent | off} {vlan | mst | unknown}
Configure the switch for VTP mode (client, server, transparent, or off).
(Optional) Configure the database:
•
•
•
Step 4
vtp password password
(Optional) Set the password for the VTP domain. The password can be 8 to 64 characters. If you configure a VTP password, the VTP domain does not function properly if you do not assign the same password to each switch in the domain.
See the "Configuring a VTP Version 3 Password" section for options available with VTP version 3.
Step 5
end
Return to privileged EXEC mode.
Step 6
show vtp status
Verify your entries in the VTP Operating Mode and the VTP Domain Name fields of the display.
Step 7
copy running-config startup-config
(Optional) Save the configuration in the startup configuration file.
Note
To return a switch in another mode to VTP server mode, use the no vtp mode global configuration command. To return the switch to a no-password state, use the no vtp password global configuration command.
This example shows how to configure the switch as a VTP server with the domain name eng_group and the password mypassword:
Switch(config)# vtp domain eng_groupSetting VTP domain name to eng_group.Switch(config)# vtp mode serverSetting device to VTP Server mode for VLANS.Switch(config)# vtp password mypasswordSetting device VLAN database password to mypassword.Switch(config)# endConfiguring a VTP Version 3 Password
Beginning in privileged EXEC mode, follow these steps to configure the password when using VTP version 3:
To clear the password, enter the no vtp password global configuration command.
This example shows how to configure a hidden password and how it appears.
Switch(config)# vtp password mypassword hiddenGenerating the secret associated to the password.Switch(config)# endSwitch# show vtp passwordVTP password: 89914640C8D90868B6A0D8103847A733Configuring a VTP Version 3 Primary Server
Beginning in privileged EXEC mode, follow these steps on a VTP server to configure it as a VTP primary server (version 3 only), which starts a takeover operation:
This example shows how to configure a switch as the primary server for the VLAN database (the default) when a hidden or secret password was configured:
Switch# vtp primary vlanEnter VTP password: mypasswordThis switch is becoming Primary server for vlan feature in the VTP domainVTP Database Conf Switch ID Primary Server Revision System Name------------ ---- -------------- -------------- -------- --------------------VLANDB Yes 00d0.00b8.1400=00d0.00b8.1400 1 stp7Do you want to continue (y/n) [n]? yConfiguring VTP on a Per-Port Basis
With VTP version 3, you can enable or disable VTP on a per-port basis. You can enable VTP only on ports that are in trunk mode. Incoming and outgoing VTP traffic is blocked, not forwarded.
Beginning in privileged EXEC mode, follow these steps to enable VTP on a port:
To disable VTP on the interface, use the no vtp interface configuration command.
Switch(config)# interface gigabitethernet 0/1Switch(config-if)# vtpSwitch(config-if)# endOther Updates to the Software Configuration Guide
In the "Configuring RIP for IPv6" section in the "Configuring IPv6 Unicast Routing" chapter, the task table is incorrect. This is the correct table:
Updates to the Command Reference
These commands are new or changed:
•
vtp (global configuration)
To set or modify the VLAN Trunking Protocol (VTP) configuration characteristics, use the vtp global configuration command. To remove the settings or to return to the default settings, use the no form of this command.
vtp {domain domain-name | file filename | interface name [only] | mode {client | off | server | transparent} [mst | unknown | vlan] | password password [hidden | secret] | pruning | version number}
no vtp {file | interface | mode [client | off | server | transparent] [mst | unknown | vlan] | password | pruning | version}
Syntax Description
Defaults
The default filename is flash:vlan.dat.
The default mode is server mode, and the default database is VLAN.
In VTP version 3, the default mode for the MST database is transparent.
No domain name or password is defined.
No password is configured.
Pruning is disabled.
The default version is Version 1.
Command Modes
Global configuration
Command History
Usage Guidelines
When you save VTP mode, domain name, and VLAN configurations in the switch startup configuration file and reboot the switch, the VTP and VLAN configurations are selected by these conditions:
•
•
The vtp file filename cannot be used to load a new database, It renames only the file in which the existing database is stored.
Follow these guidelines when configuring a VTP domain name:
•
•
•
Follow these guidelines when setting a VTP mode:
•
•
•
•
•
•
•
•
•
•
Follow these guidelines when setting a VTP password:
•
•
•
Follow these guidelines when setting VTP pruning:
•
•
•
•
Follow these guidelines when setting the VTP version:
•
•
•
•
•
•
•
•
You cannot save password, pruning, and version configurations in the switch configuration file.
Examples
This example shows how to rename the filename for VTP configuration storage to vtpfilename:
Switch(config)# vtp file vtpfilenameThis example shows how to clear the device storage filename:
Switch(config)#no vtp file vtpconfigClearing device storage filename.This example shows how to specify the name of the interface providing the VTP updated ID for this device:
Switch(config)#vtp interface gigabitethernet 0/1This example shows how to set the administrative domain for the switch:
Switch(config)# vtp domain OurDomainNameThis example shows how to place the switch in VTP transparent mode:
Switch(config)# vtp mode transparentThis example shows how to configure the VTP domain password:
Switch(config)# vtp password ThisIsOurDomain'sPasswordThis example shows how to enable pruning in the VLAN database:
Switch(config)# vtp pruningPruning switched ONThis example shows how to enable Version 2 mode in the VLAN database:
Switch(config)# vtp version 2You can verify your settings by entering the show vtp status privileged EXEC command.
Related Commands
vtp (interface configuration)
To enable the VLAN Trunking Protocol (VTP) on a per-port basis, use the vtp interface configuration command. To disable VTP on the interface, use the no form of this command.
vtp
no vtp
Note
Syntax Description
This command has no keywords or arguments.
Command Default
This command has no default settings.
Command Modes
Interface configuration.
Command History
Usage Guidelines
Enter this command only on interfaces that are in switchport trunk mode.
This command is supported only on switches configured for VTP version 3.
Examples
This example shows how to enable VTP on an interface:
Switch(config-if)# vtpThis example shows how to disable VTP on an interface:
Switch(config-if)# no vtp
Related Commands
vtp (global configuration)
Globally configures VTP domain-name, password, pruning, version, and mode.
vtp primary
To configure a switch as the VLAN Trunking Protocol (VTP) primary server, use the vtp primary privileged EXEC command.
vtp primary [mst | vlan] [force]
There is no no form of the command.
Note
Note
Syntax Description
Defaults
The switch is a VTP secondary server.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is supported only on switches configured for VTP version 3.
A VTP primary server updates the database information and sends updates that are honored by all devices in the system. A VTP secondary server can only back up to NVRAM the updated VTP configurations received from the primary server.
By default, all devices come up as secondary servers. Primary server status is needed only for database updates when the administrator issues a takeover message in the domain. You can have a working VTP domain without any primary servers.
Primary server status is lost if the device reloads or domain parameters change.
Examples
This example shows how to configure the switch as the primary VTP server for VLANs:
Switch# vtp primary vlanThis sytems is becoming primary server for feature vlan.You can verify your settings by entering the show vtp status privileged EXEC command.
Related Commands
Updates for the System Message Guide
New System Messages
Error Message AUTHMGR-5-SECURITY_VIOLATION: Security violation on the interface [chars], new MAC address ([enet) is seen. AuditSessionID [chars]Explanation A host on the interface attempted to gain access to the network or attempted an authentication. The interface mode does not support the number of hosts that are attached to the interface. This is a security violation, and the interface has been error-disabled. The first [chars] is the interface, [enet] is the Ethernet address of the host, and the second [chars] is the session ID.
Recommended Action Make sure that the interface is configured to support the number of hosts that are attached to it. Enter the shutdown interface configuration command followed by no shutdown interface configuration command to restart the interface.
Error Message AUTHMGR-5-VLANASSIGN: VLAN [dec] assigned to Interface [chars] AuditSessionID [chars]Explanation A VLAN was assigned. [dec] is the VLAN ID, the first [chars] is the interface, and the second [chars] is the session ID.
Recommended Action No action is required.
Error Message AUTHMGR-7-FAILOVER: Failing over from [chars] for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation The authorization manager is failing over from the current authentication method to another method. The first [chars] is the current authentication method, the second [chars] is the client ID, the third [chars] is the interface, and the fourth [chars] is the session ID.
Recommended Action No action is required.
Error Message AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation All available authentication methods have been tried for the client, but authentication has failed. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required. If local authorization has been configured, the port will be authorized based on the local authorization method. Otherwise, authentication will restart according to the configured reauthentication period.
Error Message AUTHMGR-7-RESULT: Authentication result [chars] from [chars] for client [chars] on Interface [chars] AuditSessionID [chars]Explanation The results of the authentication. The first [chars] is the status of the authentication, the second [chars] is the authentication method, the third [chars] is the client ID, the fourth [chars] is the interface, and the fifth [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X-5-FAIL: Authentication failed for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation The authentication was unsuccessful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action. AuditSessionID [chars]Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication. [chars] is the session ID.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation Authentication was successful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars] AuditSessionID [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. This message might appear if IEEE 802.1x is enabled. [enet] is the client MAC address, the first [chars] is the interface, and the second [chars] is the session ID.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.
Error Message EPM-6-AUTH_ACL: POLICY [chars]| EVENT [chars]Explanation The switch has sent or received a download request for a downloadable ACL (dACL). The first [chars] is the dACL policy? The second [chars] is the event.
Recommended Action No action is required.
Error Message HARDWARE-3-ASICNUM_ERROR: [traceback] Port-ASIC number [dec] is invalidExplanation The port ASIC number is invalid. [dec] is the port ASIC number.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message HARDWARE-3-PORTNUM_ERROR: [traceback] port number [dec] is invalidExplanation The port number is out of range. [dec] is the port number.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT: [chars] seems to be corrupted. Trying to read [dec] sizeExplanation The ifIndex table is corrupted. [chars] is the path to the IfIndex file, and [dec] is the number of bytes that was being read from the ifIndex table when the corruption was detected.
Recommended Action Delete the ifindex table.
Error Message IFMGR-3-INVALID_PERSISTENT_DATA: Invalid persistent dataExplanation The interface manager attempts to write invalid persistent data.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message ILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.Explanation A license authentication failure occurred for the switch.
Recommended Action Contact your Cisco sales representative for assistance.
Error Message ILET-1-DEVICE_AUTHENTICATION_FAIL: The [chars] inserted in this switch may not have been manufactured by Cisco or with Cisco's authorization. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.Explanation A license authentication failure occurred for a component that was inserted in the switch. [chars] is the component.
Recommended Action Contact your Cisco sales representative for assistance.
Error Message SCHED-3-UNEXPECTEDEVENT: [traceback] [process information] Process received unknown event (maj [hex], min [hex])Explanation A process did not handle an event. The first [hex] is the major event number, and the second [hex] is the minor event number, both of which allow you to identify the event that occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.
Modified System Messages
Error Message DOT1X-5-RESULT_OVERRIDE: Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation The authentication result was overridden. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN [dec] to 802.1x port [chars], which is configured as a SPAN destination AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to an 802.1x port that is configured as a Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the SPAN configuration so that the port is no longer a SPAN destination port, or change the configuration so that no VLAN is assigned.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port AuditSessionID [chars]Explanation Multi-Domain Authentication (MDA) host mode cannot start when the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port session ID.
Recommended Action Change either the voice VLAN or the access VLAN on the interface so that they are not the same. MDA then starts.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot be equivalent to the Voice VLAN AuditSessionID [chars]Explanation An attempt was made to assign a data VLAN to an 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change either the voice VLAN or the 802.1x-assigned VLAN on the interface so that they are not the same.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Assign a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is out of range. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Update the configuration to use a valid VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Make sure the VLAN exists and is not shut down, or use another VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Attempt to assign VLAN [dec] to routed 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to a supplicant on a routed port, which is not allowed. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Either disable the VLAN assignment, or change the port type to a nonrouted port.
Error Message DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Attempt to assign VLAN [dec] to promiscuous 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to a promiscuous IEEE 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the port mode so that it is no longer a promiscuous port, or change the configuration so that no VLAN is assigned.
Error Message DOT1X_SWITCH-5-ERR_VLAN_RESERVED: Attempt to assign reserved VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the seconds [chars] is the session ID.
Recommended Action Assign a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_RSPAN: Attempt to assign RSPAN VLAN [dec] to 802.1x port [chars]. 802.1x is incompatible with RSPAN AuditSessionID [chars]Explanation Remote SPAN should not be enabled on a VLAN with IEEE 802.1x-enabled. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Either disable remote SPAN configuration on the VLAN, or disable IEEE 802.1x on all the ports in this VLAN.
Error Message SPANTREE-2-BLOCK_BPDUGUARD_VP: Received BPDU on port [chars], vlan [dec] with BPDU Guard enabled. Disabling vlan.Explanation A BPDU was received on the interface and the VLAN specified in the error message. The spanning tree BPDU guard feature was enabled and configured to shut down the VLAN. As a result, the VLAN was placed in the error-disabled state. [chars] is the interface, and [dec] is the VLAN.
Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature. The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have Port Fast enabled. Re-enable the interface and vlan by entering the clear errdisable privileged EXEC command.
Removed System Messages
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action.Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars]Explanation Authentication was successful. [chars] is the interface.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. This message might appear if IEEE 802.1x is enabled. [enet] is the client MAC address, and [chars] is the interface.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.
Update for the Getting Started Guide
In the "Running Express Setup" section of the Catalyst 2350 Switch Getting Started Guide, Step 12 incorrectly states that the VLAN ID range is 1 to 1001. The correct range is 1 to 4094.
Related Documentation
These documents provide complete information about the Catalyst 2350 switch and are available on Cisco.com:
http://www.cisco.com/en/US/products/ps10116/tsd_products_support_series_home.html•
•
•
•
•
•
•
•
•
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 and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlSubscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2013 Cisco Systems, Inc. All rights reserved.
