Device Manager System Requirements
Finding the Software Version and Feature Set
Catalyst 3750G Integrated Wireless LAN Controller Switch Software Compatibility
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Minimum Cisco IOS Release for Major Features
Stacking (Catalyst 3750 or Cisco EtherSwitch service module switch stack only)
Caveats Resolved in Cisco IOS Release 12.2(55)SE4
Caveats Resolved in Cisco IOS Release 12.2(58)SE2
Caveats Resolved in Cisco IOS Release 12.2(58)SE1
Update to the Catalyst 3750 Software Configuration Guide
Update to the Catalyst 2960 and 2960-S Software Configuration Guide
Updates to the System Message Guides
Update to the Catalyst 3560 and Catalyst 2960 Hardware Installation Guides
Updates to the Catalyst 2960 Hardware Installation Guide
Update to the Getting Started Guide
Update to the Catalyst 2960-S Switch Getting Started Guide
Obtaining Documentation and Submitting a Service Request
Note Cisco IOS Release 12.2(58)SE images for all platforms were removed from Cisco.com because of a severe defect, CSCto62631. The solution for the defect is in Cisco IOS Release 12.2(58)SE1.
Cisco IOS Release 12.2(58)SE1 runs on Catalyst 3750, 3560, 2960-S, and 2960 switches and on Cisco EtherSwitch service modules. Not all Catalyst 3750 and 3560 switches can run this release. The models listed below are not supported in Cisco IOS Release 12.2(58)SE1 and later. For ongoing maintenance rebuilds for these models, use Cisco IOS Release 12.2(55)SE and later (SE1, SE2, and so on).
The Catalyst 3750 switches and the Cisco EtherSwitch service modules support stacking through Cisco StackWise technology. The Catalyst 3560 and 2960 switches do not support switch stacking. Catalyst 2960-S does support stacking. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
These release notes include important information about Cisco IOS Release 12.2(58)SE1 and any limitations, restrictions, and caveats that apply to the releases. Verify that these release notes are correct for your switch:
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/software/navigator.html?a=ahttp://www.cisco.com/cisco/web/download/index.htmli=rpm
24 10/100/1000 PoE1 ports, 2 SFP2 module slots, and an integrated wireless LAN controller supporting up to 25 access points. |
Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE |
|
24 10/100/1000 PoE ports, 2 SFP module slots, and an integrated wireless LAN controller supporting up to 50 access points |
Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE |
|
NME-16ES-1G3 |
16 10/100 ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide |
|
16 10/100 PoE ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide |
||
23 10/100 ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide |
||
23 10/100 PoE ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide |
||
24 10/100 PoE ports, 1 SFP module port, 2 StackWise connector ports, extended double-wide |
||
48 10/100 PoE ports, 2 SFP module ports, no StackWise connector ports, extended double-wide |
8 10/100 PoE ports and 1 dual-purpose port4 (one 10/100/1000BASE-T copper port and one SFP module slot) |
||
12 Ethernet 10/100 ports with PoE and 1 dual-purpose 10/100/1000 or SFP uplink |
||
48 10/100 PoE ports, 2 10/100/1000 ports, and 2 SFP module slots |
||
24 10/100 PoE ports and 2 dual-purpose ports |
||
24 10/100 ports (8 of which are PoE) and 2 dual-purpose ports |
||
8 10/100 ports and 1 dual-purpose port3 (1 10/100/1000BASE-T copper port and1 SFP module slot) |
||
48 10/100 PoE ports, 1 10/100/1000 ports and 2 SFP module slots |
||
24 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP module slots) |
||
48 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP module slots) |
||
8 10/100 Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot) |
||
7 10/100/1000 Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot) |
||
24 10/100 ports, 8 of which are PoE, and 2 10/100/1000 ports |
||
24 10/100 Power over Ethernet (PoE) ports and 2 dual-purpose ports (2 10/100/1000BASE-T copper ports and 2 small form-factor pluggable [SFP] module slots) |
||
24 10/100BASE-T Ethernet ports and 2 10/100/1000BASE-T Ethernet ports |
||
48 10/100BASE-T Ethernet ports 2 10/100/1000BASE-T Ethernet ports |
||
24 10/100/1000BASE-T Ethernet ports, including 4 dual-purpose ports (four 10/100/1000BASE-T copper ports and four SFP module slots) |
||
48 10/100/1000BASE-T Ethernet ports, including 4 dual-purpose ports (four 10/100/1000BASE-T copper ports and four SFP module slots) |
||
Catalyst 2960S-48FPD-L5 |
48 10/100/1000 Power over Ethernet Plus (PoE+) ports (PoE budget of 740 W) and 2 SFP+6 module slots |
|
Catalyst 2960S-48LPD-L 1 |
48 10/100/1000 PoE+ ports (PoE budget of 370 W) and 2 SFP+ module slots |
|
Catalyst 2960S-24PD-L 1 |
24 10/100/1000 PoE+ ports (PoE budget of 370 W) and 2 SFP+ module slots |
|
Catalyst 2960S-48TD-L 1 |
||
Catalyst 2960S-24TD-L 1 |
||
Catalyst 2960S-48FPS-L 1 |
48 10/100/1000 PoE+ ports (PoE budget of 740 W) and 4 SFP module slots |
|
Catalyst 2960S-48LPS-L 1 |
48 10/100/1000 PoE+ ports (PoE budget of 370 W) and 4 SFP module slots |
|
Catalyst 2960S-24PS-L 1 |
24 10/100/1000 PoE+ ports (PoE budget of 370 W) and 4 SFP module slots |
|
Catalyst 2960S-48TS-L 1 |
||
Catalyst 2960S-24TS-L 1 |
1000BASE-CWDM7, -LX, SX, -T, -ZX 100BASE-FX MMF8 Support for eight additional DWDM SFP optical modules. For a complete list of supported SFPs and part numbers, see the data sheet: |
||
XENPAK modules9 |
||
Cisco RPS 675 Redundant Power System Cisco RPS 300 Redundant Power System (supported only on the Catalyst 2960 switch) |
Supported on all software releases |
The device manager verifies the browser version when starting a session and does not require a plug-in.
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, 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, the command reference, and the Cisco EtherSwitch service module feature guide.
Cisco IOS 12.2(50)SE and later is only compatible with Cisco Network Assistant (CNA) 5.0 and later. You can download Cisco Network Assistant from this URL:
http://www.cisco.com/cisco/software/navigator.html?mdfid=279230132http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistanti=rp
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
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.
Note For Catalyst 3750 and 3560 switches and the Cisco EtherSwitch service modules, although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration (IP base image or IP services image) and does not change if you upgrade the software image.
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.
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.
Catalyst 3750 IP base cryptographic image and device manager files. This image has the Kerberos, SSH12, Layer 2+, and basic Layer 3 routing features. This image also runs on the Cisco EtherSwitch service modules. |
|
Catalyst 3750 IP services cryptographic image and device manager files. This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features. This image also runs on the Cisco EtherSwitch service modules. |
|
Catalyst 3560 IP base cryptographic image and device manager files. This image has the Kerberos, SSH, and Layer 2+, and basic Layer 3 routing features. |
|
Catalyst 3560 IP services cryptographic image and device manager files. This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features. |
|
Catalyst 2960 cryptographic image file and device manager files. This image has the Kerberos and SSH features. |
|
Catalyst 2960 LAN lite cryptographic image file and device manager files. |
|
The Catalyst 3750 Integrated Wireless LAN Controller Switch is an integrated Catalyst 3750 switch and Cisco 4400 series wireless LAN controller that supports up to 25 or 50 lightweight access points. The switch and the internal controller run separate software versions, which must be upgraded separately.
To use the controller in the Catalyst 3750G Wireless LAN Controller Switch, the switch must be running one of these Cisco IOS software releases:
Note These Cisco IOS Releases and any versions of them are not supported: Cisco IOS Release 12.2(25)SEC, 12.2(25)SED, 12.2(25)SEE, 12.2(25)SEF, and 12.2(25)SEG. All Catalyst 3750 images (IP Base, IP Services, and Advanced IP Services) are supported for use with the controller.
If the switch image version is not compatible, the wireless LAN controller switch could stop functioning.
For information about the controller software, see the release notes on this page for Cisco Software Release 4.0.x.0 or later:
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html
For controller software upgrade procedure, see the Cisco Wireless LAN Controller Configuration Guide on this page:
.http://www.cisco.com/en/US/products/ps6366/products_installation_and_configuration_guides_list.
html
Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to 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.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.
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.html
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.
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 image file and replace or keep the current image.
To download software, follow these steps:
Step 1 Use Table 6 to identify the file that you want to download.
Step 2 Download the software image file:
a. If you are a registered customer, go to this URL and log in.
http://www.cisco.com/cisco/software/navigator.html?a=ahttp://www.cisco.com/cisco/web/download/index.htmli=rpm
b. Navigate to Switches > LAN Switches - Access.
c. Navigate to your switch model.
d. Click IOS Software, then select the latest IOS release.
Download the image you identified in Step 1.
Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.
For more information, see Appendix B in the software configuration guide for this release.
Step 4 Log into the switch through the console port or a Telnet session.
Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command:
For more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6 Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by entering this privileged EXEC command:
The /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.
The / allow-feature-upgrade option allows installation of an image with a different feature set (for example, upgrade from the IP base image to the IP services image).
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:
You can also 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.
Use these methods to assign IP information to your switch:
Note If you are upgrading a Catalyst 3750 or a 2950 switch running Cisco IOS Release 12.1(11)AX, which uses the IEEE 802.1x feature, you must re-enable IEEE 802.1x after upgrading the software. For more information, see the “Cisco IOS Notes” section.
Note When upgrading or downgrading from Cisco IOS Release 12.2(18)SE, you might need to reconfigure the switch with the same password that you were using when running Cisco IOS Release 12.2(18)SE. This problem only occurs when changing from Cisco IOS Release 12.2(18)SE to any other release. (CSCed88768)
– for network assessment before deploying applications with stringent network performance requirements.
– with Cisco Mediatrace for post-deployment troubleshooting of network-related performance issues.
The traffic simulator includes a sophisticated scheduler that allows you to run several tests simultaneously or periodically, and over extended time periods. (Catalyst 3750 and 3560)
Table 7 lists the minimum software release required to support the major features of the Catalyst 3750, 3560, 2960-S, and 2960 switches and the Cisco EtherSwitch service modules.
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.
Unless otherwise noted, these limitations apply to the Catalyst 3750, and 3560, and 2960 switches and the Cisco EtherSwitch service modules:
This problem occurs under these conditions:
– When the switch is booted up without a configuration (no config.text file in flash memory).
– When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).
– When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
The workaround is to upgrade to Cisco IOS Release 12.1(20)EA1. (CSCec35100)
1. Disable auto-QoS on the interface.
2. Change the routed port to a nonrouted port or the reverse.
3. Re-enable auto-QoS on the interface. (CSCec44169)
The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
– (Catalyst 3750 switch and Cisco EtherSwitch service modules) When the Network Time Protocol (NTP) is configured, but the NTP clock is not synchronized. You can check the clock status by entering the show NTP status privileged EXEC command and verifying that the network connection to the NTP server and the peer work correctly.
– (Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The DHCP snooping database file is manually removed from the file system. After enabling the DHCP snooping database by configuring a database URL, a database file is created. If the file is manually removed from the file system, the DHCP snooping database does not create another database file. You need to disable the DHCP snooping database and enable it again to create the database file.
– (Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The URL for the configured DHCP snooping database was replaced because the original URL was not accessible. The new URL might not take effect after the timeout of the old URL.
No workaround is necessary; these are the designed behaviors. (CSCed50819)
However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)
When you enter the show ip arp inspection log privileged EXEC command, the log entries from all switches in the stack are moved to the switch on which you entered the command.
There is no workaround. (CSCed95822)
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)
To change the baud rate, reload the Cisco EtherSwitch service module with the bootloader prompt. You can then change the baud rate and change the speed on the TTY line of the router connected to the Cisco EtherSwitch Service module console.
There is no workaround. (CSCeh50152)
The workaround is to use switch ports other than those specified for redundancy and for applications that immediately detect active links. (CSCeh70503)
15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1 (ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C 4CEB50 859DF4 A7BF28 A98260 882658 879A58
(CSCsh12472 [Catalyst 3750 and 3560 switches])
The workaround is to configure aggressive UDLD. (CSCsh70244).
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)
up
and sometimes as down
, resulting in conflicts. This status depends on when you respond to the reboot query: Would you like to enter the initial configuration dialog?
– After a reboot if you wait until the Line Protocol status of VLAN 1 appears on the console before responding, VLAN 1 line status is always shown as down
. This is the correct state.
– The problem (VLAN 1 reporting 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) (Catalyst 3750 and 3560 switches)
– Two-link ports on the same switch are connected with a crossover cable.
– The switch is running Cisco IOS 12.2(50)SE3 or later.
The workaround is to connect the two ports with a straight-through cable. (CSCsr41271) (Catalyst 3750V2 and Catalyst 3560V2 PoE switches and Cisco Etherswitch service modules only)
The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090)
The workaround is to disable authorization and accounting or to enter the configuration change for one interface at a time. (CSCsg80238, CSCti76748)
– Ports 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, and 24 of the Catalyst 3750G-24T and 3750G-24TS switches
– Gigabit Ethernet ports on the Cisco EtherSwitch service modules
– Contact the NIC vendor, and get the latest driver for the card.
– Configure the interface for 1000 Mb/s instead of for 10/100 Mb/s.
– Connect the NIC to an interface that is not listed here. (CSCea77032)
For more information, enter CSCea77032 in the Bug Toolkit at this URL:
http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
If the Cisco EtherSwitch service module is in access mode, the workaround is to enter the spanning-tree portfast interface configuration command on the internal Gigabit Ethernet interface. If the service module is in trunk mode, there is no workaround.
If this happens, uneven traffic distribution will happen on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
– for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip
– for incrementing source-ip traffic, configure load balance method as src-ip
– for incrementing dest-ip traffic, configure load balance method as dst-ip
– Configure the number of ports in the EtherChannel so that the number is equal to a power of 2 (i.e. 2, 4, or 8)
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal.(CSCeh81991)
The workaround is to remove the VLAN from the bridge group or to remove the static MAC address from the VLAN. (CSCdw81955)
The workaround is to disable fallback bridging or to disable port security on all ports in all VLANs participating in fallback bridging. To remove an interface from a bridge group and to remove the bridge group, use the no bridge-group bridge-group interface configuration command. To disable port security on all ports in all VLANs participating in fallback bridging, use the no switchport port-security interface configuration command. (CSCdz80499)
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)
The workaround is to not set an ARP timeout value lower than 120 seconds. (CSCea21674)
The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)
No workaround is necessary. (CSCea85312)
The workaround for networks with pre-standard powered devices is to leave the maximum wattage set at the default value (15.4 W). You can also configure the maximum wattage for the port for no less than the value the powered device reports as the power consumption through CDP messages. For networks with IEEE Class 0, 3, or 4 devices, do not configure the maximum wattage for the port at less than the default 15.4 W (15,400 milliwatts). (CSCee80668)
The workaround is to enter the power inline never interface configuration command on all the Fast Ethernet ports that are not powered by but are connected to IP phones if the problem persists. (CSCef84975, Cisco EtherSwitch service modules only)
The workaround is to power the access point by using an AC wall adaptor. (CSCin69533)
The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. (CSCsf32300)
There is no workaround for this problem because non-RPF traffic is continuous in certain topologies. As long as the trunk port is a member of the group in at least one VLAN, this problem occurs for the non-RPF traffic. (CSCdu25219)
The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)
There is no workaround. (CSCdy82818)
The workaround is to not apply a router ACL set to deny access to a VLAN interface. Apply the security through other means; for example, apply VLAN maps to the VLAN instead of using a router ACL for the group. (CSCdz86110)
There is no workaround. (CSCea71255)
Multicast is not supported on tunnel interfaces
error message. IP PIM is not supported on tunnel interfaces. There is no workaround. (CSCeb75366)
– If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.
– If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.
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)
– You disable IP multicast routing or re-enable it globally on an interface.
– A switch mroute table temporarily runs out of resources and recovers later.
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.
– Cancel membership in the multicast group by using the no ip igmp join-group group-address interface configuration command on an SVI.
– Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id global configuration command. (CSCeh90425)
The workaround is to enable IP routing or to disable multicast routing on the switch. You can also use the ip igmp snooping querier global configuration command if IP multicast routing is enabled for queries on a multicast router port. (CSCsc02995)
There is no workaround. You should use the power inline never interface configuration command on Cisco EtherSwitch service module ports that are not connected to PoE devices. (CSCee71979)
To display the total power used by a specific EtherSwitch service module, enter the show power inline command on the router. This output appears:
This is not a problem because the display correctly shows the total used power and the remaining power available on the system. (CSCeg74337)
The workaround is to enter the shutdown and the no shutdown interface configuration commands on the Fast Ethernet interface of a new IP phone that is attached to the service module port after the internal link is brought up. (CSCeh45465)
The workaround is to choose compatible buffer sizes and threshold levels. (CSCea76893)
There is no workaround. (CSCea52915)
This error message means there is a temporary memory shortage that normally recovers by itself. You can verify that the switch stack has recovered by entering the show cef line user EXEC command and verifying that the line card states are up
and sync
.
No workaround is required because the problem is self-correcting. (CSCea71611)
– Port security is enabled with the violation mode set to protected.
– The maximum number of secure addresses is less than the number of switches connected to the port.
– There is a physical loop in the network through a switch whose MAC address has not been secured, and its BPDUs cause a secure violation.
The workaround is to change any one of the listed conditions. (CSCed53633)
The workaround is to use an on-demand upgrade to upgrade switches in a stack by entering the vstack download config and vstack download image commands. (CSCta64962)
When you upgrade the director to Cisco IOS Release 12.2(55)SE, the workaround is to also modify the configuration to include all built-in, custom, and default groups. You should also configure the tar image name instead of the image-list file name in the stored images. (CSCte07949)
The workaround is to use the TFTP utility of another server instead of a Windows server or to manually delete the existing backup file before backing up again. (CSCte53737)
– If client needs to upgrade using an image and configuration file configured in the DHCP server options, you should remove the client from the Smart Install network during the upgrade.
– In a network using Smart Install, you should not configure options for image and configuration in the DHCP server. For clients to upgrade using Smart Install, you should configure product-id specific image and configuration files in the director. (CSCte99366)
The workaround, if you need to configure a switch in a stack with the backup configuration, is to use the vstack download config privileged EXEC command so that the director performs an on-demand upgrade on the client.
– When the backup configuration is stored in a remote repository, enter the location of the repository.
– When the backup file is stored in the director flash memory, you must manually set the permissions for the file before you enter the vstack download config command. (CSCtf18775)
There is no workaround. (CSCtg98656)
– When you select the NONE option in the director CLI, the upgrade should be allowed and is successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.
– When you enter any password in the director CLI, the upgrade should not be allowed, but it is successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.
This is a hardware limitation and only applies to these switches (CSCdy72835):
– Cisco EtherSwitch service modules
This is a hardware limitation and only applies to these switches (CSCdy81521):
– Cisco EtherSwitch service modules
This is a hardware limitation and only applies to these switches (CSCea72326):
– Cisco EtherSwitch service modules
Decreased egress SPAN rate
. In all cases, normal traffic is not affected; the degradation limits only how much of the original source stream can be egress spanned. If fallback bridging and multicast routing are disabled, egress SPAN is not degraded. There is no workaround. If possible, disable fallback bridging and multicast routing. If possible, use ingress SPAN to observe the same traffic. (CSCeb01216)
There is no workaround. (CSCeb23352)
There is no workaround. (CSCec36644)
There is no workaround. (CSCed00328)
The workaround is to save the stack configuration before removing or replacing any switch in the stack. (CSCed15939)
There is no workaround. (CSCed54150)
IP-3-STCKYARPOVR
appears on the consoles of other default IP gateways. Because sticky ARP is not disabled, the MAC address update caused by the stack master re-election cannot complete.The workaround is to complete the MAC address update by entering the clear arp privileged EXEC command. (CSCed62409)
There is no workaround. (CSCed70894)
Private VLAN is enabled or disabled on a switch stack, depending on whether or not the stack master is running the IP services image or the IP base image:
– If the stack master is running the IP services image, all stack members have private VLAN enabled.
– If the stack master is running the IP base image, all stack members have private VLAN disabled.
This occurs after a stack master re-election when the previous stack master was running the IP services image and the new stack master is running the IP base image. The stack members are configured with private VLAN, but any new switch that joins the stack will have private VLAN disabled.
These are the workarounds. Only one of these is necessary:
– Reload the stack after an IP services image to IP base image master switch change (or the reverse).
– Before an IP services image-to-IP base image master switch change, delete the private-VLAN configuration from the existing stack master. (CSCee06802)
This is the expected behavior of the offline configuration (provisioning) feature. There is no workaround. (CSCee12431)
– Connect to the router through the console port, and open a session to the service module. (CSCeh01250) (Cisco EtherSwitch service modules)
The workaround is to copy the bootable image to the parent directory or first directory. (CSCei69329)
The workaround is to assign a lower path cost to the forwarding port. (CSCsd95246)
This can but does not always occur during link flaps and does not last for more than a few milliseconds. This problem can happen for cross-stack EtherChannels with the mode set to ON or LACP.
There is no workaround. No manual intervention is needed. The problem corrects itself within a short interval after the link flap as all the switches in the stack synchronize with the new load-balance configuration. (CSCse75508)
The workaround is to reboot the new member switch. Use the remote command all show run privileged EXEC command to compare the running configurations of the stack members. (CSCsf31301)
– A supplicant is authenticated on at least one port.
– A new member joins a switch stack.
You can use one of these workarounds:
– Enter the shutdown and the no shutdown interface configuration commands to reset the port.
– Remove and reconfigure the VLAN. (CSCsi26444)
The workaround is to check the flash. If it contains many files, remove the unnecessary ones. Check the lost and found directory in flash and if there are many files, delete them. To check the number of files use the fsck flash: command. (CSCsi69447)
1. You configure a Layer 2 protocol tunnel port on the master switch.
2. You configure a Layer 2 protocol tunnel port on the member switch.
3. You add the port channel to the Layer 2 protocol tunnel port on the master switch.
4. You add the port channel to the Layer 2 protocol tunnel port on the member switch.
After this sequence of steps, the member port might stay suspended.
The workaround is to configure the port on the member switch as a Layer 2 protocol tunnel and at the same time also as a port channel. For example:
The workaround is to enter a shutdown interface configuration command followed by a no shutdown command on the port in the blocked state. (CSCsl64124)
The workaround it to enter a shutdown and then a no shutdown interface configuration command on the interface. (CSCsx70643) (Catalyst 3750 switch)
There is no workaround.(CSCth00938) (Catalyst 3750 and 2960-S switches)
There is no workaround. (CSCdz33708)
There is no workaround. (CSCdz42909).
There is no workaround. (CSCea40988)
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
There is no workaround. (CSCed71422)
The workaround is to define another policy-map name for the second-level policy-map with the same configuration to be used for another policy-map. (CSCef47377)
The workaround is to configure the burst interval to more than 1 second. (CSCse06827, Catalyst 3750 switches only)
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port. (CSCsi26392)
The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are flapping. (CSCtl04815)
– the no logging on and then the no logging console global configuration commands
– the logging on and then the no logging console global configuration commands
In Cisco IOS Release 12.2(18)SE and later, you can only use the logging on and then the no logging console global configuration commands to disable logging to the console. (CSCec71490)
If this message appears, check that there is network connectivity between the switch and the ACS. You should also check that the switch has been properly configured as an AAA client on the ACS
If this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.
From Microsoft Internet Explorer:
1. Choose Tools > Internet Options.
2. Click Settings in the “Temporary Internet files” area.
3. From the Settings window, choose Automatically.
5. Click OK to exit the Internet Options window.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
Unless otherwise noted, these caveats apply to the Catalyst 3750, 3560, 2960-S, and 2960 switches and to Cisco EtherSwitch service modules:
Cisco Network Assistant displays the LED ports with a light blue color for all switches in a stack that have the Catalyst 3750G-48PS switch as part of the stack.
When you make port security changes on an interface, such as configuring aging time, violations, or aging type, error messages and tracebacks might appear.
The output from the show sdm prefer lanbase-routing privileged EXEC command shows some incorrect values. The corrected values are:
Mediatrace does not report statistics on the initiator under these conditions:
– The responder is a mixed switch stack with a Catalyst 3750 as the master switch
– The ingress interface on the responder from the initiator is on a member switch.
The workaround is to ensure that the mediatrace ingress and egress connections are on the stack master or to configure a Catalyst 3750-E or 3750-X as the stack master and then reload the switch stack.
Unicast EIGRP packets destined for the switch are sent to the host queue instead of to the higher priority routing protocol queue.
Note This does not occur when packets are routed through the switch to another destination.
When a switch or switch stack running Multiple Spanning Tree (MST) is connected to a switch running Rapid Spanning Tree Protocol (RSTP), the MST switch acts as the root bridge and runs per-VLAN spanning tree (PVST) simulation mode on boundary ports connected to the RST switch. If the allowed VLAN on all trunk ports connecting these switches is changed to a VLAN other than VLAN 1 and the root port of the RSTP switch is shut down and then enabled, the boundary ports connected to the root port move immediately to the forward state without going through the PVST+ slow transition.
When a switch is using a DHCP server to assign IP addresses and an interface on the switch has RIP enabled, if the switch reloads, the interface loses some RIP configuration (specifically RIP authentication mode and RIP authentication key-chain). This does not happen when the IP address is statically configured on the interface. The problem occurs only when you configure RIP before an IP address is assigned by the DHCP server.
There is no workaround, but you can use an embedded event manager (EEM) script to add the interface configuration commands on the interface:
When you configure OSPFv3 graceful restart on a stack of switches with more than one OSPF area and you use the router-id ip-address router configuration command to configure a fixed router ID, if there is a switchover of the stack master switch, OSPFv3 graceful restart might be terminated.
The workaround, if possible, is to not use the router-id command to configure a fixed router ID with OSPFv3 graceful restart.
A Catalyst 2960 with 64Mb of DRAM might display low memory on the console after you upgrade the switch to 12.2(58)SE or later.
The workaround is to limit the memory that is used by different features on the switch if this release is required. You can reduce memory usage by minimizing the number of trunk ports and VLANs in use on the switch.
On a switch running Protocol-Independent Multicast (PIM) and Source Specific Multicast (SSM), multicast traffic might not be sent to the correct port after the switch reloads.
The workaround is to enter the clear ip route privileged EXEC command or reconfigure PIM and SSM after a reload.
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.
Cisco IOS Software is affected by two vulnerabilities that cause a Cisco IOS device to reload when processing IP version 6 (IPv6) packets over a Multiprotocol Label Switching (MPLS) domain. These vulnerabilities are:
– Crafted IPv6 Packet May Cause MPLS-Configured Device to Reload
– ICMPv6 Packet May Cause MPLS-Configured Device to Reload
Cisco has released free software updates that address these vulnerabilities.
Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-ipv6mpls.shtml.
When you configure a port to be in a dynamic VLAN by entering the switchport access vlan dynamic interface configuration command on it, the switch might reload when it processes ARP requests on the port.
The workaround is to configure static VLANs for these ports.
Fallback web authentication does not work.
The workaround is to downgrade to Cisco IOS Release 12.2(55)SE2.
The switch fails when a port channel is created with a WS-6708-GE-TX line card on the other end of the port channel.
The workaround is to downgrade to a release earlier than Cisco IOS Release 12.2(55)SE.
Use the vlan dot1q tag native global configuration command to configure the edge switch so that all packets going out an IEEE 802.1Q trunk, including the native VLAN, are tagged. If the switch is configured to tag native VLAN packets on all IEEE 802.1Q trunks, the switch accepts untagged packets, but sends only tagged packets.
When you globally enable UDLD by entering the udld { aggressive | enable | message time message-timer-interval } global configuration command, UDLD is now enabled only on fiber optic ports and on dual-purpose ports operating as fiber optic interfaces. It is not enabled on copper ports or dual-purpose ports operating as copper interfaces. For the udld global configuration command to enable UDLD on dual-purpose ports that have a small form-factor pluggable (SFP) module connected, you must explicitly configure the interface media type as SFP by entering the media-type sfp interface configuration command.
When you reload a stack master, the ip vrf forwarding command does not appear in the running configuration, which causes AAA authentication to fail. This issue does not occur with standalone switches.
The workaround is to reenter the ip vrf forwarding command.
A switch stack configured as a multicast router has a hardware programming error. Some multicast streams are not forwarded to a receiver while other streams from the same source are forwarded correctly. The unforwarded streams are Layer 2 forwarded by the stack on the same VLAN on which they were received to the multicast designated router for the VLAN.
The workaround is to use the clear ip mroute privileged EXEC command to resolve the hardware programming error.
A Link Aggregation Control Protocol (LACP) bundle takes up to 70 seconds to form when NetFlow sampling is enabled.
The workaround is to disable NetFlow sampling.
When you configure a switch to send messages to a syslog server in a VPN Routing and Forwarding (VRF) instance, the messages are not sent to the server.
The workaround is to remove the VRF configuration.
When ports in an EtherChannel are linking up, the message EC-5-CANNOT_BUNDLE2
might appear. This condition is often self-correcting, indicated by the appearance of EC-5-COMPATIBLE
message following the first message. On occasion, the issue does not self-correct, and the ports may remain unbundled.
The workaround is to reload the switch or to restore the EtherChannel bundle by shutting down and then enabling the member ports and the EtherChannel in this order:
– Enter the shutdown interface configuration command on each member port.
– Enter the shutdown command on the port-channel interface.
– Enter the no shutdown command on each member port.
– Enter the no shutdown command on the port-channel interface.
The CPU utilization on the switch remains high (50 to 60 percent) when the switch is not being accessed by a telnet or a console session. When you telnet or console into the switch, the CPU utilization goes down.
When you connect a switch as a VLAN Trunk Protocol (VTP) client to a Catalyst 4000 switch configured as a VTP client or server and the VTP database contains more than 512 VLANs, the database is not correctly updated.
The workaround is to connect the VTP client directly to a Catalyst 6500 VTP server.
A host switch connected to a stack member switch can download a downloadable access control list (dACL) with more than 13 access control entries, but the dACL is not applied to an interface.
On a stack member, the show interface command output incorrectly displays a media-type setting.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch.
Enabling the Cisco Discovery Protocol (CDP) on a tunnel interface causes the switch to fail when a a CDP packet is received on the interface.
Note Tunnels are not supported on these platforms.
The workaround is to use the no cdp enable interface configuration command to disable CDP on the interface.
When a FlexLinks backup interface is configured on a member switch in a switch stack, the backup interface incorrectly shows that all VLANs are in the forwarding state.
The workaround is to use the show interface trunk interface configuration command to display the status of the backup link.
A Catalyst 29560-S switch downlink port cannot connect to the uplink port of a Catalyst compact switch.
The workaround is to configure the speed to 100 Mb/s on both ports.
When a new member switch with a different SDM template than that of the master switch is added to a stack, it does not reload with the SDM template of the stack master switch and does not display an SDM mismatch condition.
The config.text.backup file is present after the switch is restored to the factory defaults.
When you enter the ipv6 traffic-filter interface configuration command, it might not filter traffic as expected, and it might allow traffic to pass through.
QoS ACL commands might appear differently in the running configuration after the master switch is reloaded or removed from the stack. The functionality of the commands remains the same.
When you disconnect the spanning tree protocol (STP) peer link, the STP port path cost configuration changes.
Two stacks that have members with fiber SFP modules are connected in a cross-stack EtherChannel with this configuration:
If a member in one stack is reloaded, this error message appears on a member switch port in the other stack and the port is error disabled.
%PLATFORM_PM-3-INTVLANINUSE: internal vlan-id 1012 allocated for interface Gi2/0/2 is still in use (3750-b-2)-Traceback= 173E7F0 198F40C 176DA04 1774E70 173FBDC 1744574 16C9C28 17C65C4 17C67D8 1BB7308 1BADD78 (3750-b-2)
The workaround is to configure Layer 2 EtherChannels with SVIs and to use the EtherChannel Active mode.
A switch stack reloads when you enter the ip routing global configuration command.
The workaround is to use the no ip routing global configuration command to disable IP routing.
When the destination IP address matches the default route, the switch does not forward traffic.
The workaround is to use a specific static route such as
When a spanning-tree bridge protocol data unit (BPDU) is received on an 802.1Q trunk port and has a VLAN ID is greater than or equal to 4095, the spanning-tree lookup process fails.
When the Ethernet management port speed is 10 Mb/s and the link between the switch and its peer is up, IP ping fails.
The workaround is to set the speed to 100 Mb/s.
When a GLC-FE-100FX SFP module port is in full-duplex mode, it changes to half-duplex mode after you enter the shutdown and the no shutdown interface configuration commands or after the link between the switch and another device fails and then comes up.
The workaround is to enter the no duplex and the duplex full interface configuration commands.
When a stack is running per-VLAN spanning-tree plus (PVST+) and you create a VLAN, the STP topology change resets the aging time for all members and ages out all the MAC addresses for the new VLAN. If a cookie for the new VLAN on the member is not created when the master sends the member an HRPC message to update the aging timer, the member changes the aging time for VLAN 1 to that set during the topology change.
After the topology change, the aging time for the new VLAN is reset to that before the STP topology changed. However, the aging time for VLAN 1 does not change. The MAC addresses learned on VLAN 1 and on the member switch ports age out before aging time for the new VLAN.
The workaround is to disable STP before creating a new VLAN in the stack.
When you enter the default interface, switchport, or no switchport interface configuration command on the switch, this message appears: EMAC phy access error, port 0, retrying......
When you use a network scanner to check network devices for security issues, the CPU usage increases.
On a switch running Cisco IOS Release 12.2(55)SE with the parser config cache interface global configuration command in the configuration, when you use the CISCO-MAC-NOTIFICATION-MIB to enable the SNMP MAC address notification trap, the trap is enabled, but the trap setting does not appear in the switch configuration.
The workaround is to remove the parser config cache interface command from the configuration.
The CPU usage on a standalone switch varies as the switch updates the running configuration.
When the switch stack elects a new stack master, by default the MAC address of the new master becomes the stack MAC address. Configuring a persistent MAC address sets a delay after stack master change before the stack master MAC address change. A timer value of 0 means that the MAC address of the current master is used indefinitely.
When you enter the stack-mac persistent timer 0 global configuration command on a stack and the master switch is not the original owner of the stack MAC address, ports on member switches do not go through Rapid Spanning Tree Protocol (STP) transitions directly into the forwarding state.
The workaround is to not use the stack-mac persistent timer 0 command on the switch stack.
On Catalyst 2960-S, 3560-X, and 3750-X switches, some SFP+ module ports do not work correctly with 1 Gigabit SFP modules when the speed for the port and for the connected device is set to nonegotiate. This occurs only on some ports and some SKUs.
The workaround is to set the speed on the SFP interface to autonegotiate by entering the speed auto interface configuration command.
When a Catalyst 2960-S FlexStack with four switches is connected to a Catalyst 3750 switch, and devices in the same VLAN are connected to the Catalyst 2960-S switches but a device in another VLAN is connected to the Catalyst 3750, if you recycle power on one of the Catalyst 2960-S switches, connected devices can lose packets.
When quality of service (QoS) is disabled on a switch, packet fragments might be dropped when more traffic is exiting a port than the bandwidth allows. The port can become oversubscribed because fragments are sent to an incorrect egress queue that has fewer buffers.
The workaround is to enable QoS by entering the mls qos global configuration command.
The SNMP Get action does not work correctly on Cisco IOS Releases 12.2(46)SE and 12.2(53)SE with the pethMainPseOperStatus operation.
The workaround is to use the SNMP Walk utility instead of SNMP Get.
When 802.1x MAC authentication bypass with multidomain authentication and critical VLAN are enabled on an interface on a switch running Cisco IOS Release 12.2(53)SE or later, if the switch loses connectivity with the AAA server, the switch might experience high CPU usage and show these messages:
If the startup configuration file is empty on the master switch and Multiple Spanning Tree Protocol (MSTP) is configured on the switch stack, the stack fails and reloads when you enter the config replace nvram:startup-config user EXEC command.
The workaround is to ensure that a valid startup configuration file exists on the master switch.
The port manager callback might cause more than 90% CPU usage for up to 20 minutes under these conditions:
– Link comes up simultaneously on multiple dot1q trunk ports.
– VLAN Trunking Protocol (VTP) pruning is enabled.
The workaround is to disable VTP pruning.
A switch running Cisco IOS Release 12.2(58)SE might reload if:
– SSH version 2 is configured on the switch, and
– a customized login banner was configured by using the banner login message global configuration command
– Disable the login banner by entering the no login banner command.
– Downgrade to a software version prior to Cisco IOS Release 12.2(58)SE.
Note The “Supported MIBs” appendix is no longer in the software configuration guide. To locate and download MIBs for a specific Cisco product and release, use the Cisco MIB Locator:
http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Catalyst 2960-S switches internally support up to 16 different control plane queues. Each queue is dedicated to handling specific protocol packets and is assigned a priority level. For example, STP, routed, and logged packets are sent to three different control plane queues, which are prioritized in corresponding order, with STP having the highest priority. Each queue is allocated a certain amount of processing time based on its priority. The processing-time ratio between low-level functions and high-level functions is allocated as 1-to-2. Therefore, the control plane logic dynamically adjusts the CPU utilization to handle high-level management functions as well as punted traffic (up to the maximum CPU processing capacity). Basic control plane functions, such as the CLI, are not overwhelmed by functions such logging or forwarding of packets.
In the “Managing Switch Stacks” chapter, this information is added.
In a mixed stack that has Catalyst 3750-X, Catalyst 3750-E, and Catalyst 3750 switches, we recommend that a Catalyst 3750-X switch be the stack’s active switch and that all stack members run Cisco IOS Release 12.2(53)SE2 or later. The Catalyst 3750 image is on the Catalyst 3750-X and 3750-E switches to simplify switch management.
To upgrade the stack, use the archive download-sw privileged EXEC command to download images to the active switch. For example, use the archive download-sw /directory tftp://10.1.1.10/ c3750-ipservicesk9-tar.122-55.SE1.tar c3750e-universalk9-tar.122-55.SE1.tar command to specify a directory, following the command with the list of tar files to download for the members.
In the “Configuring SDM Templates” chapter, the LAN base routing template has incorrect values. The corrected values are:
Explanation The subblock data structure was not initialized. [chars] is the structure identifier.
Recommended Action No action is required.
Error Message VLMAPLOG-6-ARP: vlan [dec] (port [chars]) denied arp ip [inet] -> [inet], [dec] packet[chars]Explanation A packet from the virtual LAN (VLAN) that matches the VLAN access-map (VLMAP) log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] denotes the number of packets, and the second [chars] represents the letter “s” to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-L4: vlan [dec] (port [chars]) denied [chars] [inet]([dec]) -> [inet]([dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [chars] is the protocol, the first [inet] is the source IP address, the second [dec] is the source port, the second [inet] is the destination IP address, the third [dec] is the destination port, the fourth [dec] denotes the number of packets, and the third [chars] represents the letter “s” to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-IGMP: vlan [dec] (port [chars]) denied igmp [inet] -> [inet] ([dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Group Management Protocol (IGMP) message type, the third [dec] denotes the number of packets, and the second [chars] represents the letter “s” to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-ICMP: vlan [dec] (port [chars]) denied icmp [inet] -> [inet] ([dec]/[dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Control Message Protocol (ICMP) message type, the third [dec] is the ICMP message code, the fourth [dec] denotes the number of packets, and the second [chars] represents the letter “s” to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-IP: vlan [dec] (port [chars]) denied ip protocol=[dec] [inet] -> [inet], [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [dec] is the protocol number, the first [inet] is the source IP address, the second [inet] is the destination IP address, the third [dec] denotes the number of packets, and the second [chars] represents the letter “s” to indicate more than one packet.
Recommended Action No action is required.
Error Message HARDWARE-2-PSU_THERMAL_WARNING: PSU [chars] temperature has reached warning thresholdExplanation The switch power supply unit (PSU) temperature sensor value has reached the warning level. The external temperature is high. [chars] is the power supply.
Recommended Action Reduce the temperature in the room. (The switch functions normally until the temperature reaches the critical level.)
Error Message HARDWARE-1-PSU_THERMAL_CRITICAL: PSU [chars] temperature has reached critical thresholdExplanation The switch PSU temperature sensor value has reached the critical level, and the switch cannot function normally. The external temperature is very high. [chars] is the power supply.
Recommended Action Immediately reduce the room temperature.
Error Message HARDWARE-5-PSU_THERMAL_NORMAL: PSU [chars] Temperature is within the acceptable limitExplanation The switch PSU temperature sensor value is within normal limits. [chars] is the power supply.
Recommended Action No action is required.
Error Message HARDWARE-2-THERMAL_WARNING: Temperature has reached warning thresholdExplanation The switch temperature sensor value has reached the warning level. The external temperature is high.
Recommended Action Reduce the room temperature. (The switch functions normally until the temperature reaches the critical level.)
Error Message AUTHMGR-7-STOPPING: Stopping ’[chars]’ for client [enet] on Interface [chars] AuditSessionID [chars]Explanation The authentication process has been stopped. The first [chars] is the authentication method, [enet] is the Ethernet address of the host, the second [chars] is the interface for the host, and the third [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. The first [chars] is the client identifier, the second [chars]s is the interface for the client, and the third [chars] is the session ID.
Explanation The client moved to a new interface but did not log off from the first interface. [enet] is the MAC address of the client, the first [chars] is the earlier interface, and the second [chars] is the newer interface.
Recommended Action No action is required.
Error Message AUTHMGR-5-MACREPLACE: MAC address ([enet]) on Interface [chars] is replaced by MAC ([enet])Explanation A new client has triggered a violation that caused an existing client to be replaced. The first [enet] is the first client, [chars] is the interface, the second [enet] is the new client.
Recommended Action No action is required.
Error Message EOU-6-IDENTITY_MATCH: IP=[inet]| PROFILE=EAPoUDP| POLICYNAME=[chars]| AUDITSESSID=[chars]Explanation The router has found the specifed host under the Extensible Authentication Protocol over User Datagram Protocol (EAPoUDP) identity profile. [inet] is the host IP address, the first [chars] is the enforced policy, and the second [chars] is the session ID.
Recommended Action If you do not want the host to be exempt from authentication, remove its entry from the EAPoUDP identity profile.
Error Message EOU-5-RESPONSE_FAILS: Received an EAP failure response from AAA for host=[inet]| AUDITSESSID=[chars]Explanation The router received an EAP failure response from authentication, authorization, and accounting (AAA). The host credentials were not validated. [inet] is the host, and [chars] is the session ID.
Recommended Action Check for causes of unsuccessful AAA validation of host credentials.
Error Message EOU-6-SESSION: IP=[inet]| HOST=[chars]| Interface=[chars]| AUDITSESSID=[chars]Explanation An entry for the host was created or deleted on the specified interface. [inet] is the host IP address, the first [chars] is the host identifier, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message EOU-4-VERSION_MISMATCH: HOST=[inet]| Version=[dec]| AUDITSESSID=[chars]Explanation A mismatch in the EAPoUDP versions was detected from the host. [inet] is the host identifier, [dec] is the EAPoUDP version, and [chars] is the session ID.
Recommended Action Check EAPoUDP versions on peers.
Error Message EOU-6-POSTURE: IP=[inet]| HOST=[chars]| Interface=[chars]|AUDITSESSID=[chars]Explanation The posture validation status for the host. [inet] is the host IP address, the first [chars] is the host identfier, the second [chars] is the host interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message EOU-6-AUTHTYPE: IP=[inet]| AuthType=[chars]| AUDITSESSID=[chars]Explanation The authentication type for the host. [inet] is the host IP address, the first [chars] is the authentication type, and the second [chars] is the session ID.
Recommended Action No action is required.
Error Message EOU-4-UNKN_EVENT_ERR: UNKNOWN Event for HOST=[inet]| Event=[dec]| AUDITSESSID=[chars]Explanation Unknown message for the EAPoUDP process. [inet] is the host identifier, [dec] is the event identifier, and [chars] is the session ID.
Recommended Action File a DDTS with Cisco.
Error Message EOU-5-AAA_DOWN: AAA unreachable. METHODLIST=[chars]| HOST=[inet]| POLICY=[chars].| AUDITSESSID=[chars]Explanation The AAA servers defined by the method list cannot be reached by the host and the applied policy. The first [chars] is the method list identifer, [inet] is the host identifier, the second [chars] is the policy, and the third [chars] is the session ID.
Recommended Action Check the possible causes for unreachable AAA servers.
Error Message MAB-5-FAIL: Authentication failed for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation Authentication was unsuccessful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message MAB-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation Authentication was successful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.
Explanation Multiple stations are configured with the same IP address in a private VLAN. (This could be a case of IP address theft.) [inet] is the IP address that is configured, the first [enet] is the original MAC address associated with the IP address, and the second [enet] is the MAC address that triggered this message.
Recommended Action Change the IP address of one of the two systems.
In the “Switch Installation (24- and 48-Port Switches)” chapter, the note in the “Connecting to a Dual-Purpose Port” section is incorrect. The correct information is:
Note By default, the switch automatically selects the interface type the first time a port links up. For subsequent links, you must use the media-type interface configuration command to manually configure either the RJ-45 connector or the SFP module connector. For more information, see the command reference.
Cisco Ethernet Switches are equipped with cooling mechanisms, such as fans and blowers. However, these fans and blowers can draw dust and other particles, causing contaminant buildup inside the chassis, which can result in a system malfunction.
You must install this equipment in an environment as free as possible from dust and foreign conductive material (such as metal flakes from construction activities).
This applies to all Cisco Ethernet switches except for these compact models:
– Catalyst 2960-8TC switch—8 10/100BASE-T Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)
– Catalyst 2960G-8TC switch—7 10/100/100BASE-T Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)
When you launch Express Setup, you are prompted for the switch password. Enter the default password, cisco. The switch ignores text in the username field. Before you complete and exit Express Setup, you must change the password from the default password, cisco.
This correction applies to the French, Italian, German, Spanish, Japanese, and simplified Chinese versions of the getting started guide:
In the “Unpacking the Switch” section, four number-8 Phillips flat-head screws (48-0655-01) are included with the switch.
User documentation in HTML format includes the latest documentation updates and might be more current than the complete book PDF available on Cisco.com.
These documents provide complete information about the Catalyst 3750, 3560, 2975, 2960-S and 2960 switches and the Cisco EtherSwitch service modules and are available at Cisco.com:
http://www.cisco.com/en/US/products/hw/switches/ps5023/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/hw/switches/ps5528/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps10081/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps6406/tsd_products_support_series_home.html
These documents provide complete information about the Catalyst 3750 switches and the Cisco EtherSwitch service modules:
These documents provide complete information about the Catalyst 3750G Integrated Wireless LAN Controller Switch and the integrated wireless LAN controller and are available at cisco.com:
These documents provide complete information about the Catalyst 3560 switches:
These documents provide complete information about the Catalyst 2960 and 2960-S switches and are available on Cisco.com:
For other information about related products, see these documents:
SFP 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 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.html
Subscribe 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.