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
Minimum Cisco IOS Release for Major Features
Cisco Redundant Power System 2300
Cisco Transceiver Modules and SFP Modules
Stacking (only Catalyst 3750-X and Catalyst 3750-E Switch Stack)
Stack Power (Catalyst 3750-X 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-X and 3750-E Software Configuration Guides
Correction to the “Unsupported Commands in Cisco IOS Release 12.2(58)SE” Chapter
Update to the “Managing Switch Stacks” Chapter
Updates to the Catalyst 3750-E and 3560-E Cisco Software Activation and Compatibility Document
Updates to the System Message Guide
Update to the Installation Notes for Catalyst 3750-X and 3560-X Switch Power Supply Modules
Installation Guidelines Change
Update to the Catalyst 3750-E and 3560-E Getting Started Guides
Catalyst 3750-E Switch Getting Started Guide
Catalyst 3560-E 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 and later runs on Catalyst 3750-X, Catalyst 3750-E, Catalyst 3650-X, and Catalyst 3560-E switches and on Cisco enhanced EtherSwitch service modules.
The Catalyst 3750-X and 3750-E switches support stacking through Cisco StackWise Plus technology. The Catalyst 3750-X also supports StackPower. The Catalyst 3560-X switches, Catalyst 3650-E switches, and the Cisco enhanced EtherSwitch service modules do not support switch stacking.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack. Cisco enhanced EtherSwitch service modules and Catalyst 3560-E switches support the same features.
For more information, see the Deciding Which Files to Use and the “Related Documentation” section.
These release notes include important information about Cisco IOS Release 12.2(55)SE and later and any limitations, restrictions, and caveats that apply to it. 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
Note Upgrading the software image on a Catalyst 3560-X or 3750-X switch from Cisco IOS Release 12.2(53)SE2 or 12.2(55)SE to Cisco IOS Release 12.2(58)SE1 could take up to 20 minutes.
12 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Base feature set1 |
||
24 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Base feature set 1 |
||
12 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Services feature set |
||
24 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Services feature set |
||
24 10/100/1000 Ethernet ports, StackWise Plus, 1 network module slot, 350 W power supply; LAN Base feature set |
||
48 10/100/1000 Ethernet ports, StackWise Plus, one network module slot, 350 W power supply; LAN Base feature set |
||
24 10/100/1000 PoE+2 ports, StackWise Plus, 1 network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+ 2 ports, StackWise Plus, one network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+ 2 ports, StackWise Plus, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
24 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Base feature set 1 |
||
48 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Base feature set 1 |
||
24 10/100/1000 PoE+ 2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Base feature set 1 |
||
48 10/100/1000 PoE+ 2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Base feature set 1 |
||
48 10/100/1000 PoE+ 2 ports, StackWise Plus, StackPower, 1 network module slot, 1100 W power supply; IP Base feature set 1 |
||
24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; LAN Base feature set |
||
48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; LAN Base feature set |
||
24 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+ 2 ports, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Base feature set 1 |
||
48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Base feature set 1 |
||
24 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; IP Base feature set 1 |
||
48 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; IP Base feature set 1 |
||
48 10/100/1000 PoE+ 2 ports, 1 network module slot, 1100 W power supply; IP Base feature set 1 |
||
Four SFP slots. Two slots support only 1-Gigabit SFP modules, two slots support either 1-Gigabit SFP or 10-Gigabit SFP+ modules. |
||
100FX-SFP 1000BASE-LX/LH Note =For a complete list of supported SFP modules, see the hardware installation guide or the data sheets at: |
||
SFP-10G-SR |
||
Only version 02 (or later) of the CX15 cables are supported: |
||
SFP module patch cable6 |
||
C3KX-PWR-1100WAC Note For power supply module descriptions and configurations supported on switch models, see the hardware installation guide. |
||
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
24 10/100/1000 PoE7 ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
24 10/100/1000 PoE ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
12 SFP8 module slots, 2 10-Gigabit Ethernet X2 module slots |
||
X2-10GB-SR V02 or later |
Cisco IOS Release 12.2(35)SE2 |
|
Dual SFP X2 converter module to allow the switch to support SFP Gigabit Ethernet modules |
||
1000BASE-LX/LH For a complete list of supported SFPs and part numbers, see the data sheet: |
||
DOM10 support for these SFP modules. |
||
SFP module patch cable11 |
||
SFP-10G-SR= Only version 02 or later CX112 cables support these SFP modules: |
||
SM-D-ES2-48 7 |
||
SM-D-ES3-48-P 7 |
||
SM-D-ES3G-48-P 7 |
||
SM-ES2-16-P13 |
||
SM-ES2-24 7 |
||
SM-ES2-24-P 7 |
Layer 2-capable, 23 10/100 ports with PoE, 1 10/100/1000 port with PoE |
|
SM-ES3-16-P 7 |
||
SM-ES3-24-P 7 |
||
SM-ES3G-16-P 7 |
||
SM-ES3G-24-P 7 |
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, Release Notes for Cisco Network Assistant, the Cisco enhanced EtherSwitch service module documentation, the software configuration guide, and the command reference.
Cisco IOS 12.2(55)SE will be supported in a future release of the Cisco Network Assistant. Cisco IOS 12.2(35)SE2 and later is only compatible with Cisco Network Assistant 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 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 and does not change if you upgrade the software license.
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.
If you have a service support contract and order a software license or if you order a switch, you receive the universal software image and a specific software license. If you do not have a service support contract, such as a SMARTnet contract, download the IP base image from Cisco.com. For Catalyst 3750-X and 3560-X switches, this image has the IP base and LAN base feature sets. For Catalyst 3750-E and 3560-E switches, this image has the IP base feature set.
Note A Catalyst 3750-X or 3560-X switch running the LAN base feature set supports only 255 VLANs.
The switches running the universal software images can use permanent and temporary software licenses. See the “Cisco IOS Software Activation Conceptual Overview” chapter in the Cisco IOS Software Activation Configuration Guide :
http://www.cisco.com/en/US/docs/ios/csa/configuration/guide/12.4T/csa_book.html
The universal software images support multiple feature sets. Use the software activation feature to deploy a software license and to enable a specific feature set.
For information about Catalyst 3750-E and 3560-E software activation, see the Cisco Software Activation and Compatibility Document on Cisco.com:
http://www.cisco.com/en/US/products/ps7077/products_installation_and_configuration_guides_list.html
Catalyst 3750-X and 3560-X switches running payload-encryption images can encrypt management and data traffic. Switches running nonpayload-encryption images can encrypt only management traffic, such as a Secure Shell (SSH) management session.
For more information about Catalyst 3750-X and 3560-X software licenses and available images, see the Cisco IOS Software Installation Document on Cisco.com:
http://www.cisco.com/en/US/products/ps10745/products_installation_and_configuration_guides_list.html
Layer 2 and basic Layer 3 features, SSH16, SSL17, and SNMPv318, and Kerberos IP base image, as well as LAN base image with Layer 2 features |
||
Layer 2 and basic Layer 3 features, SSH, SSL, SNMPv3, Kerberos, and MACsec19 IP base image, as well as LAN base image with Layer 2 features |
||
All the supported universal image features, Kerberos, SSH, SSL, and SNMPv3 |
||
All the supported universal image features, Kerberos, SSH, SSL, SNMPv3, and MACsec |
||
Layer 2 and basic Layer 3 features, SSH, SSL, SNMPv3, and Kerberos |
||
All the supported universal image features, Kerberos, SSH, SSL, and SNMPv3 |
||
Layer 2 features, SSH, SNMPv3, and Kerberos For these service modules: SM-D-ES2-48, SM-ES2-16-P, SM-ES2-24, and SM-ES2-24-P6. |
||
All the supported universal image features, Kerberos, SSH, SSL, and SNMPv3 IP base and IP services software licenses For these service modules: SM-D-ES3-48-P, SM-D-ES3G-48-P, SM-ES3-16-P, SM-ES3-24-P, SM-ES3G-16-P, and SM-ES3G-24-P. |
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.
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.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 4 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.
e. 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.
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:
– 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.
Table 5 lists the minimum software release after the first release of required to support the major features on the switches. The first release of the Catalyst 3750-X sand 3560-X switches was Cisco IOS Release 12.2(53)SE2).
Built-in Traffic Simulator using Cisco IOS IP SLAs video operations |
||
Auto Smartports enhancements to enable auto-QoS on a digital media player. |
||
Support for 16 static routes on SVIs on the LAN Base feature set |
||
DHCPv6 bulk-lease query and DHCPv6 relay source configuration |
||
NSF IETF mode for OSPFv2 and OSPFv3 (IP services feature set) |
||
Auto-QoS enhancements that add automatic configuration classification of traffic flow from video devices. |
||
AutoSmartports enhancements—support for global macros, last-resort macros, event trigger control, access points, EtherChannels, auto-QoS with Cisco Medianet, and IP phones. |
||
CDP and LLDP enhancements for exchanging location information with video end points.s. |
||
Smart Install enhancements including client backup files, zero-touch replacement for clients with the same product-ID, and automatic generation of the image_list file. |
||
Dynamic creation or attachment of an auth-default ACL on a port with no configured static ACLs. |
||
Cisco EnergyWise Phase 2 to manage power usage of EnergyWise-enabled Cisco devices and non-Cisco end points running EnergyWise agents20 |
||
AutoSmartports enhancements (macro persistency, LLDP-based triggers, MAC address and OUI-based triggers. |
||
EEM 3.2 Neighbor Discovery, Identity, and MAC-Address-Table. |
||
802.1x User Distribution to allow deployments with multiple VLANs. |
||
Network Edge Access Topology (NEAT) to change the port host mode and to apply a standard port configuration on the authenticator switch port. |
||
MAC move to allow hosts to move across ports within the same switch without any restrictions to enable mobility. |
||
SNMPv3 with Triple Data Encryption Standard (3DES) and 128-bit, 192-bit, and 256-bit Advanced Encryption Standard (AES) encryption algorithms. |
||
Hostname inclusion in the option 12 field of DHCPDISCOVER packets. |
||
DHCP Snooping enhancement to support the circuit-id sub-option of the Option 82 DHCP field. |
||
LLPD-MED enhancements to allow the switch to grant power to the power device (PD), based on the power policy TLV request. |
||
QoS marking of CPU-generated traffic and queue CPU-generated traffic on egress ports. |
||
NEAT with 802.1X switch supplicant, host authorization with CISP, and auto enablement |
||
802.1x authentication with downloadable ACLs and redirect URLs. |
||
Flexible-authentication sequencing to configure the order of authentication methods tried by a port. |
||
Multiple-user authentication to allow more than one host to authenticate on an 802.1x-enabled port |
||
Supports the LLPD-MED MIB and the CISCO-ADMISSION-POLICY MIB. |
||
Smart Install to allow a single point of management (director) in a network. |
||
Cisco Medianet to enable intelligent services in the network infrastructure for a wide variety of video applications. |
||
Support for up to 32 10 Gigabit Ethernet DWDM X2 optical modules. |
||
Intermediate System-to-Intermediate System (IS-IS) routing for Connectionless Network Service (CLNS) networks |
||
Support for the Cisco IOS Configuration Engine (previously the Cisco IOS CNS agent) |
||
Support for these MIBs: SCP attribute in the CONFIG_COPY MIB, CISCO-AUTH-FRAMEWORK, CISCO-MAC-AUTH-BYPASS, LLDP |
||
IPv6 features supported in the IP services and IP base software images: ACLs; DHCPv6 for the DCHP server, client, and relay device; EIGRPv6; HSRPv6; OSPFv3; RIP; Static routes |
||
Generic message authentication support with the SSH Protocol and compliance with RFC 4256 |
||
Voice aware 802.1x and mac authentication bypass (MAB) security violation |
||
The ability to exclude a port in a VLAN from the SVI line-state calculation |
||
PAgP Interaction with Virtual Switches and Dual-Active Detection |
||
Rehosting a software license and using an embedded evaluation software license |
||
DHCP for IPv6 relay, client, server address assignment and prefix delegation (IP services image) |
||
Embedded event manager (EEM) for device and system management |
||
Automatic quality of service (QoS) Voice over IP (VoIP) enhancement |
||
Dynamic voice virtual LAN (VLAN) for multidomain authentication (MDA) |
||
Support for the Link Layer Discovery Protocol Media Extensions (LLDP-MED) location TLV |
||
Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) |
||
Support for auto-rendezvous point (auto-RP) for IP multicast |
||
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.
There is no workaround. (CSCse33114)
The workaround is to block traffic from the specific MAC address by using the mac address-table static mac-addr vlan vlan-id drop global configuration command. (CSCse73823)
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))
PLATFORM_ENV-1-RPS_ACCESS: RPS is not responding
No workaround is required because the problem corrects itself. (CSCsf15170)
The workaround is to use modules with serial numbers that are not in the specified range. (CSCsh59585)
– Allow space between the switches when installing them.
– In a switch stack, plan the SFP module and cable installation so that uplinks in adjacent stack members are not all in use.
– Use long, small screwdriver to access the latch then remove the SFP module and cable. (CSCsd57938)
The workaround is to configure aggressive UDLD. (CSCsh70244).
There is no workaround. (CSCec74610) (Catalyst 3750-X switches)
PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 0, class 51, max_msg 128, total throttled 984323
-Traceback= 6625EC 5DB4C0 5DAA98 55CA80 A2F2E0 A268D8
No workaround is necessary. Under normal conditions, the switch generates this notification when snooping the next ARP packet. (CSCse47548)
The workaround is to not configure VLANs with protected ports as part of a fallback bridge group. (CSCsg40322)
When a switch port configuration is set at 10 Mb/s half duplex, sometimes the port does not send in one direction until the port traffic is stopped and then restarted. You can detect the condition by using the show controller ethernet-controller or the show interfaces privileged EXEC commands.
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 enter the switchport access vlan dynamic interface configuration command separately on each port. (CSCsi26392)
The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090)
The workaround is to delete any unnecessary files in flash memory, delete the temporary files created as part of the failed upgrade, and try the MCU upgrade again. (CSCtd75400)
The workaround to verify the cable length is to enter the commands when a Gigabit link is active on the interface or after disconnecting the far end of the cable. (CSCte43869)
– The EtherChannel is a cross-stack EtherChannel with a switch stack at one or both ends.
– The switch stack partitions because a member reloads. The EtherChannel is divided between the two partitioned stacks, each with a stack master.
The EtherChannel ports are put in the suspended state because each partitioned stack sends LACP packets with different LACP Link Aggregation IDs (the system IDs are different). The ports that receive the packets detect the incompatibility and shut down some of the ports. Use one of these workarounds for ports in this error-disabled state:
– Enable the switch to recover from the error-disabled state.
– Enter the shutdown and the no shutdown interface configuration commands to enable the port.
The EtherChannel ports are put in the error-disabled state because the switches in the partitioned stacks send STP BPDUs. The switch or stack at the other end of the EtherChannel receiving the multiple BPDUs with different source MAC addresses detects an EtherChannel misconfiguration.
After the partitioned stacks merge, ports in the suspended state should automatically recover. (CSCse33842)
No workaround is necessary. The problem corrects itself after the link-up or link-down event. (CSCse75508)
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
Use one of these workarounds (CSCsd90495):
– Configure the port for single-host mode to prevent the extra MAC address from appearing in the MAC address table.
– Replace the NIC card with a new card.
– If the connected device is supposed to be unauthorized, the connected device might be authorized on the VLAN that is assigned to the critical port instead of to a guest VLAN.
– If the device is supposed to be authorized, it is authorized on the VLAN that is assigned to the critical port.
Use one of these workarounds (CSCse04534):
– Configure MAC authentication bypass to not use EAP.
– Define your network access profiles to not use MAC authentication bypass. For more information, see the Cisco Access Control Server (ACS) documentation.
The workaround is not use the VLAN assignment option. (CSCse22791)
– Multicast routing is enabled in the VLAN.
– The source IP address of the packet belongs to the directly connected network.
– The TTL value is either 0 or 1.
The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)
– Multicast routing is enabled in the VLAN.
– The source IP address of the multicast packet belongs to a directly connected network.
– The packet is denied by the IP multicast boundary access-list configured on the VLAN.
There is no workaround. (CSCei08359)
The workaround is to not send RPF-failed multicast traffic, or make sure that the source IP address of the RPF-failed packet is reachable. (CSCsd28944)
There is no workaround. (CSCsd45753)
– The port-channel is configured with member ports across different switches in the stack.
– When one of the member switches reloads.
– The member switch that is reloading has a high rate of IP IGMP joins arriving on the port-channel member port.
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)
There is no workaround. (CSCsd60647)
The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. (CSCsf32300)
There is no workaround. (CSCsg20629)
The workaround is to turn the powered device off and then on again.
There is no workaround. (CSCeh18677)
There is no workaround. (CSCsc63334)
The workaround is to use a different name for the interface-level policy map. (CSCsd84001)
There is no workaround. (CSCsd72001)
There is no workaround. (CSCsg79627)
– Use the default buffer size.
– Use the mls qos queue-set output qset-id buffers allocation1... allocation4 global configuration command to allocate the buffer size. The buffer space for each queue must be at least 10 percent. (CSCsx69718) (Catalyst 3750-X switches)
– The switch has 400 Open Shortest Path First (OSPF) neighbors.
– The switch has thousands of OSPF routes.
The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)
The workaround is to not send traffic to unknown destinations. (CSCse97660)
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)
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.
There is no workaround. This is a hardware limitation. (CSCei10129)
The workaround is to configure aggressive UDLD. (CSCsh70244).
The workaround is to use the show platform monitor session privileged EXEC command to display the correct source ports. (CSCtn67868)
The workaround it to enter a shutdown and then a no shutdown interface configuration command on the interface. (CSCsx70643)
unable to read config
message appears.The workaround is to wait a few seconds and then to reenter the write memory privileged EXEC command. (CSCsd66272)
The workaround is to use the logging monitor global configuration command to set the severity level to block the low-level messages on the stack member consoles. (CSCsd79037)
The workaround is to avoid traffic congestion on the stack ring. (CSCsd87538)
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)
The workaround is to delete files in the flash memory to create more free space. (CSCsg30073)
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)
There is no workaround. (CSCth00938)
The workaround is to reload the switch stack after the VRF configuration is changed. (CSCtn71151)
The workaround when you are forming power stack topologies if the power stack mode is not the default (power sharing), you should also configure the power stack mode on the new power stacks by entering the mode redundant power-stack configuration command. (CSCte33875)
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
The workaround is to enter the shut and no shut interface configuration commands on the port to reset the authentication status. (CSCsf98557)
– 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 always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command. (CSCsk65142)
The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are flapping. (CSCtl04815)
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.
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 Catalyst 3750-X, 3750-E, 3560-X, and 3560-E switches:
In a Smart Install network, when the director is connected between the client and the DHCP server and the server has options configured for image and configuration, then the client does not receive the image and configuration files sent by the DHCP server during an automatic upgrade. Instead the files are overwritten by the director and the client receives the image and configuration that the director sends.
– 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.
If you install 10/100/1000BASE-TX or 100BASE-FX SFPs in the SFP+ module ports (port 2 or port 4), the ports are put in an error disabled state. These SFPs are not supported in the SFP+ ports.
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.
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 enter the show sdm template privileged EXEC command on a switch running the LAN base feature set, incorrect values are displayed for vlan, routed interfaces and indirect IPv4 routes.
– The displayed values are: 8 routed interfaces, 1024 VLANs, 2K indirect IPv4 Routes
– The actual values are: 0 routed interfaces, 255 VLANs, 16 indirect IPv4 routes
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 stack power member switch that does not have a PSU connected in Slot A or Slot B might fail during a Cisco IOS upgrade.
The workaround is to ensure that each stack member has at least one PSU connected. Alternatively, you can download and install the Cisco IOS image using the archive download-sw /force-ucode-reload privileged EXEC command.
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.
On a Cisco Integrated Services Router with an Enhanced EtherSwitch Module (ES3), after upgrading the Cisco IOS release on the EtherSwitch Module to Release12.2(58)SE1, the internal trunk link between the EtherSwitch and the router no longer passes any traffic.
The workaround is to upgrade to Cisco IOS Release 12.2(58)SE2.
When you enter the show inventory command on a switch that has an X2 module, the output incorrectly reports the X2 module version ID (VID) as V01 even though the label has a higher VID.
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.
When a Cisco Catalyst 3560E-12D or 3560E-12SD switch receives packets on an interface of a 10GBASE-SR or X2-10GB-LR module that is directly connected to a server, packets can be intermittently dropped after the server is restarted.
The workaround is to use the shutdown and no shutdown interface configuration commands on the interface.
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.
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.
When a Catalyst 3750-E or 3560-E switch has a 10/100/1000BASE-TX SFP module installed in a TwinGig SFP Converter Module, and you configure the SFP module to send at 100 Mb/s, save the configuration, and reload the switch, the speed setting is not saved to the running configuration.
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.
The switch does not generate SNMP traps when a power supply is disconnected.
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.
When traffic is passing through a port, if you unplug the port cable and then plug it back in, the LED might turn to black or might continue flashing amber.
The workaround is to wait until traffic stops passing through the port. The LED changes to the correct color and continues working normally.
When you configure storm control with a range command on two interfaces that belong to an EtherChannel group, this message appears:
The workaround is to configure storm control on a port channel interface.
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.
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.
When you disconnect the spanning tree protocol (STP) peer link, the STP port path cost configuration changes.
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 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.
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:
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.
If you upgrade the Cisco Catalyst 3750-X switch in Cisco StackPower mode from Release 12.2(58)SE, the switch may repeatedly report under-budgeted power messages. This issue is caused by a change in the minimum power budget values.
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 3750-X, 3750-E, 3560-X and 3560-E 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.
The “Miscellaneous Unsupported Privileged EXEC Commands” section should include the show facility-alarm status privileged EXEC command for the Catalyst 3750-E switch.
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 master 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 master. 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 Cisco IOS Release 12.2(50)SE1 and earlier, the Catalyst 3750-E and 3560-E switches support only the universal software images.
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 PLATFORM_STACKPOWER-6-RPS_CABLE: RPS cable [chars]Explanation The redundant power supply (RPS) cable connected to the switch was connected or disconnected.
Recommended Action No action is required.
Error Message PLATFORM_STACKPOWER-6-RPS_LINK: RPS protocol is upExplanation The RPS can now provide backup power.
Recommended Action No action is required.
Error Message PLATFORM_STACKPOWER-6-RPS_BACKUP: RPS backup is [chars]Explanation The status of the RPS backup for the switch. [chars] identifies the active or inactive status.
Recommended Action If the RPS backup is inactive, replace power supplies that are faulty or removed.
Error Message PLATFORM_STACKPOWER-6-SW_RPS_CABLE: Switch [dec] RPS cable [chars]Explanation The RPS cable connected to the switch was connected or disconnected.
Recommended Action No action is required.
Error Message PLATFORM_STACKPOWER-6-SW_RPS_LINK: Switch [dec] RPS protocol is upExplanation The RPS can now provide backup power.
Recommended Action No action is required
Error Message PLATFORM_STACKPOWER-6-SW_RPS_BACKUP: Switch [dec] RPS backup is [chars]Explanation The status of the RPS backup for the switch. [dec] is the switch identifier, and [chars] identifies the active or inactive status.
Recommended Action If the RPS is inactive, replace power supplies that are faulty or have been removed.
Error Message PLATFORM_STACKPOWER-6-TOO_MANY_ERRORS: Switch [dec]: Too many errors seen on port [chars]Explanation Several errors have occurred on the switch stack power port. [chars] is the port.
Recommended Action Check the power supplies and cables connected to the port. Contact your Cisco sales representative for assistance.
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 switch does not have enough power to supply the Power over Ethernet (PoE) port. [chars] is the PoE port identifier.
Recommended Action No action is required.
Error Message AUTHMGR-5-MACMOVE: MAC address ([enet]) moved from Interface [chars] to Interface [chars]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 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.
The power supply is hot-swappable. In some configurations, such as full POE+ or power sharing mode, removing a power supply causes the switch to shut down powered devices until the power budget matches the input power of a single power supply. To minimize network interruption, hot swap the power supply under these circumstances:
The warranty section in the Catalyst 3750-E Switch Getting Started Guide and the Catalyst 3560-E Switch Getting Started Guide has changed. These are the updated sections.
Catalyst 3750-E switches are covered by the Cisco Limited Lifetime Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English/LH2DEN__.html
Note If you purchased your Catalyst 3750-E switch before May 1, 2009, your switch is covered by the Cisco 90-Day Limited Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English/901DEN__.html
Catalyst 3560-E switches are covered by the Cisco Limited Lifetime Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English/LH2DEN__.html
Note If you purchased your Catalyst 3560-E switch before May 1, 2009, your switch is covered by the Cisco 90-Day Limited Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English/901DEN__.html
User documentation in HTML format includes the latest documentation updates and might be more current than the complete book PDF available on Cisco.com.
with complete information about the switch are available from these Cisco.com sites:
Catalyst 3750-X
http://www.cisco.com/en/US/products/ps10745/tsd_products_support_series_home.html
Catalyst 3560-X
http://www.cisco.com/en/US/products/ps10744/tsd_products_support_series_home.html
Catalyst 3750-E
http://www.cisco.com/en/US/products/ps7077/tsd_products_support_series_home.html
Catalyst 3560-E
http://www.cisco.com/en/US/products/ps7078/tsd_products_support_series_home.html
These documents provide complete information about the switches:
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 other information about related products, see these documents:
These documents have information about the Cisco enhanced EtherSwitch service modules:
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.