Table Of Contents
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 X2 Transceiver Modules and SFP Modules
Stacking (only Catalyst 3750-E Switch Stack)
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE4 (Catalyst 3750-E Switches Only)
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE
Updates to the Software Configuration Guide
Understanding Embedded Event Manager
Embedded Event Manager Actions
Embedded Event Manager Policies
Embedded Event Manager Environment Variables
Configuring Embedded Event Manager
Registering and Defining an Embedded Event Manager Applet
Registering and Defining an Embedded Event Manager TCL Script
Displaying Embedded Event Manager Information
Updates to the Command Reference
Updates to the System Message Guide
Updates to the Getting Started Guides
Updates to the Hardware Installation Guide
Updates to the Regulatory Compliance and Safety Information
Regulatory Standards Compliance
Cautions and Regulatory Compliance Statements for NEBS
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Catalyst 3750-E
and Catalyst 3560-E Switches, Cisco IOS Release 12.2(44)SE and Later
Revised September 9, 2009
Cisco IOS Release 12.2(44)SE and later runs on all Catalyst 3750-E and Catalyst 3560-E switches.
Note
Cisco IOS Release 12.2(44)SE4 only runs on the Catalyst 3750-E switches.
The Catalyst 3750-E switches support stacking through Cisco StackWise Plus technology. The Catalyst 3560-E switches do not support switch 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(44)SE 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://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches
This software release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
For the complete list of Catalyst 3750-E and Catalyst 3560-E switch documentation, see the "Related Documentation" section.
Contents
This information is in the release notes:
•
•
•
•
•
•
•
System Requirements
The system requirements are described in these sections:
•
•
•
Hardware Supported
Table 1 lists the hardware supported on this release.
Table 1 Catalyst 3750-E and Catalyst 3560-E Switches Supported Hardware
Cisco Catalyst 3750E-24TD
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-48TD
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-24PD
24 10/100/1000 PoE1 ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-48PD
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-48PD
Full Power48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-24TD
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-48TD
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-24PD
24 10/100/1000 PoE ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-48PD
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-48PD
Full Power48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-12D
12 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(40)EX
Cisco Catalyst 3560E-12SD
12 SFP2 module slots, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(44)SE
Cisco X2 transceiver modules
X2-10GB-SR V02 or later
X2-10GB-LR V03 or later
X2-10GB-ER V02 or later
X2-10GB-CX4 V03 or later
X2-10GB-LX4 V03 or later
X2-10GB-LRMCisco IOS Release 12.2(35)SE2
Cisco IOS Release 12.2(40)SECisco TwinGig Converter Module
Dual SFP X2 converter module to allow the switch to support SFP Gigabit Ethernet modules
Cisco IOS Release 12.2(35)SE2
SFP modules
1000BASE-LX/LH
1000BASE-SX
1000BASE-ZX
1000BASE-BX10-D
1000BASE-BX10-U
1000BASE-T
100BASE-FX
CWDM3Cisco IOS Release 12.2(35)SE2
SFP module patch cable4
CAB-SFP-50CM
Cisco IOS Release 12.2(35)SE2
C3K-PWR-1150WAC
1150-W AC power supply module for PoE-capable switches
Supported on all software releases
C3K-PWR-750WAC
750-W AC power supply module for PoE-capable switches
Supported on all software releases
C3K-PWR-265WAC
265-W AC power supply module for nonPoE-capable switches
Supported on all software releases
C3K-PWR-265WDC
265-W DC power supply module for nonPoE-capable switches
Supported on all software releases
C3K-BLWR-60CFM
Fan module
Supported on all software releases
Redundant power system (RPS)
Cisco RPS 2300 RPS
Supported on all software releases
1 PoE = Power over Ethernet.
2 SFP = small form-factor pluggable
3 CWDM = coarse wavelength-division multiplexer
4 Only Catalyst 3560-E switches. The SFP module patch cable is a 0.5-meter, copper, passive cable with SFP module connectors at each end. The patch cable can connect two Catalyst 3560-E switches in a cascaded configuration.
Device Manager System Requirements
These sections describe the hardware and software requirements for using the device manager:
•
•
Hardware Requirements
Table 2 lists the minimum hardware requirements for running the device manager.
Table 2 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1 GB DRAM.
Software Requirements
Table 3 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.
Note
Table 3 Supported Operating Systems and Browsers
Windows 2000
None
5.5 or 6.0
7.1
Windows XP
None
5.5 or 6.0
7.1
1 Service Pack 1 or higher is required for Internet Explorer 5.5.
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.
CNA Compatibility
Cisco IOS 12.2(35)SE2 and later is only compatible with Cisco Network Assistant 5.0 and later. You can download Network Assistant from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
Note
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Table 4 lists the filenames for this software release.
Note
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 software activation, see the Cisco Software Activation and Compatibility Document on Cisco.com:
http://www.cisco.com/en/US/products/ps7077/tsd_products_support_series_home.html
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release from which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/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
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, at this URL:
Upgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
To download software, follow these steps:
Step 1
Step 2
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the universal software image files for a Catalyst 3750-E switch, click Catalyst 3750-E software. To obtain authorization and to download the cryptographic software files, click Catalyst 3750-E 3DES Cryptographic Software.
To download the universal software image files for a Catalyst 3560-E switch, click Catalyst 3560-E software. To obtain authorization and to download the cryptographic software files, click Catalyst 3560-E 3DES Cryptographic Software.
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/c3750e-universal-tar.122-44.SE.tarYou 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.
Recovering from a Software Failure
For additional recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
New Features
These sections describe the new supported hardware and the new and updated software features provided in this release:
•
•
New Hardware Features
For a list of all supported hardware, see the "Hardware Supported" section.
New Software Features
These are the new software features for this release:
•
•
•
•
•
•
•
•
•
•
•
•
Minimum Cisco IOS Release for Major Features
Table 5 lists the minimum software release (after the first release) required to support the major features of the Catalyst 3750-E and Catalyst 3560-E switches. Features not listed are supported in all releases.
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
This section contains these limitations:
•
•
Cisco IOS Limitations
Unless otherwise noted, these limitations apply to the Catalyst 3750-E and 3560-E switches:
•
•
•
•
•
•
Access Control List
These are the access control list (ACL) limitations:
•
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)
Address Resolution Protocol
This is an Address Resolution Protocol limitation:
•
The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem.(CSCse06827))
Cisco Redundant Power System 2300
This is the Cisco Redundant Power System (RPS) 2300 limitation:
•
PLATFORM_ENV-1-RPS_ACCESS: RPS is not responding
No workaround is required because the problem corrects itself. (CSCsf15170)
Cisco X2 Transceiver Modules and SFP Modules
These are the Cisco X2 transceiver module and SFP module limitations:
•
•
•
•
–
–
–
•
•
Configuration
These are the configuration limitations:
•
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)
EtherChannel
These are the EtherChannel limitations:
•
–
–
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:
–
–
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
There is no workaround. (CSCsh12472)
IEEE 802.1x Authentication
These are the IEEE 802.1x authentication limitations:
•
Use one of these workarounds (CSCsd90495):
–
–
•
–
–
Use one of these workarounds (CSCse04534):
–
–
•
The workaround is not use the VLAN assignment option. (CSCse22791)
Multicasting
These are the multicasting limitations:
•
–
–
–
The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)
•
–
–
–
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 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)
PoE
These are the power-over-Ethernet (PoE) limitations:
•
•
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)
QoS
These are the quality of service (QoS) limitations:
•
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)
•
Routing
These are the routing limitations:
•
–
–
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 IP address as the next hop instead of an interface. (CSCsi16162)
SPAN and RSPAN
This is the SPAN and Remote SPAN (RSPAN) limitation.
•
There is no workaround. This is a hardware limitation. (CSCei10129)
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
VLANs
These are the VLAN limitations:
•
The workaround is to enter the shut and no shut interface configuration commands on the port to reset the authentication status. (CSCsf98557)
•
–
–
–
You can use one of these workarounds:
–
–
Stacking (only Catalyst 3750-E Switch Stack)
These are the Catalyst 3750-E switch stack limitations:
•
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)
Device Manager Limitations
This is the device manager limitation:
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Important Notes
These sections describe the important notes related to this software release for the Catalyst 3750-E and 3560-E switches:
•
Switch Stack Notes
These notes apply to switch stacks:
•
•
•
Cisco IOS Notes
These notes apply to Cisco IOS software:
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.
•
AutoQoS Error: ciscophone input service policy was not properly appliedpolicy map AutoQoS-Police-CiscoPhone not configuredIf this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.
Device Manager Notes
These notes apply to the device manager:
•
•
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the address (for example, www.cisco.com:84), you must enter http:// as the URL prefix. Otherwise, you cannot launch the device manager.
Open Caveats
This section describes the open caveats with possible unexpected activity in this software release. Unless otherwise noted, these severity 3 Cisco IOS configuration caveats apply to the Catalyst 3750-E and 3560-E switches:
•
When a RIP network and IP address are configured on an interface, a traceback error occurs after you enter the shutdown, no shutdown, switchport and no switchport interface configuration commands.
The workaround is to configure the RIP network and the IP address after you configure the interface.
•
The configuration file used for the configuration replacement feature requires the character string end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the configuration rollback does not work.
These are the workarounds. (You only need to do one of these.)
–
–
The workaround is to configure routed IPv4 multicast and IPv6 unicast traffic in different switch ports.
•
If you upgrade the software image from Cisco IOS Release 12.2(25)SEE2 to Cisco IOS Release 12.2(35)SE1, the IPv6 static routes are in the switch configuration but might not be in the routing table.
The workaround is to specify the egress interface on the IPv6 static route
•
When a per-port per-VLAN policy map (a hierarchical VLAN-based policy map) is attached to a VLAN interface, and you remove the child-policy policer from the policy map and then add it back, the policy map fails to re-attach to the same SVI
The workaround is to delete the child policy, which removes it from the parent policy. Then recreate the child policy (with the same or a different name) and reference it in the parent policy. The parent policy then successfully attaches to the SVI.
•
When a switch stack boots up, one or more traceback messages may appear on the switch console when the switch stack has these conditions:
–
–
–
The workaround is to execute clear ip mds linecard [<num>| *] to re-trigger the multicast information download from Route Processor to Line Card. This should be executed after the VLAN database is in sync across the stack.
•
When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.
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.
•
A stack member switch might fail to bundle Layer 2 protocol tunnel ports into a port channel when you have followed these steps:
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:
Switch(config)# interface fastethernet1/0/11Switch(config-if)# l2protocol-tunnel cdpSwitch(config-if)# channel-group 1 mode on•
When the configuration file is removed from the switch and the switch is rebooted, port status for VLAN 1 and the management port (Fast Ethernet 0) is sometimes reported as 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?
–
–
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.
•
After a stack bootup, the spanning tree state of a port that has IEEE 802.1x enabled might be blocked, even when the port is in the authenticated state. This can occur on a voice port where the Port Fast feature is enabled.
The workaround is to enter a shutdown interface configuration command followed by a no shutdown command on the port in the blocked state.
•
When SNMP is enabled on a Catalyst 3560E-12D or 3560E-12SD switch, an SNMP trap is not generated when a power-supply module is removed or inserted.
There is no workaround.
Resolved Caveats
•
•
•
•
•
•
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6
•
When MAC authentication bypass (MAB) authentication fails, a memory leak no longer occurs.
•
When a VLAN is assigned for IEEE 802.1x authentication and no VLAN is assigned for other types of authentication (such as user authentication or reauthentication), the 802.1x VLAN assignment no longer persists across subsequent authentication attempts.
•
When the switch uses HTTP (web-based) authentication, a memory leak no longer occurs after authorization and policy download.
•
A switch no longer displays processor memory-allocation failure messages under these conditions:
–
–
–
Note
This is resolved in Cisco IOS 12.2(44)SE6 and later.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5
•
A vulnerability in the handling of IP sockets can cause devices to be vulnerable to a denial of service attack when any of several features of Cisco IOS software are enabled. A sequence of specially crafted TCP/IP packets could cause any of the following results:
–
–
–
–
Workarounds that mitigate this vulnerability are available in the "workarounds" section of the advisory. The advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-ip.shtml
•
The server side of the Secure Copy (SCP) implementation in Cisco IOS software contains a vulnerability that could allow authenticated users with an attached command-line interface (CLI) view to transfer files to and from a Cisco IOS device that is configured to be an SCP server, regardless of what users are authorized to do, per the CLI view configuration. This vulnerability could allow valid users to retrieve or write to any file on the device's file system, including the device's saved configuration and Cisco IOS image files, even if the CLI view attached to the user does not allow it. This configuration file may include passwords or other sensitive information.
The Cisco IOS SCP server is an optional service that is disabled by default. CLI views are a fundamental component of the Cisco IOS Role-Based CLI Access feature, which is also disabled by default. Devices that are not specifically configured to enable the Cisco IOS SCP server, or that are configured to use it but do not use role-based CLI access, are not affected by this vulnerability.
This vulnerability does not apply to the Cisco IOS SCP client feature.
Cisco has released free software updates that address this vulnerability.
There are no workarounds available for this vulnerability apart from disabling either the SCP server or the CLI view feature if these services are not required by administrators.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090325-scp.shtml.
•
Cisco IOS software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.
Cisco has released free software updates that address this vulnerability.
Several mitigation strategies are outlined in the workarounds section of this advisory.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml
•
Symptoms: Several features within Cisco IOS software are affected by a crafted UDP packet vulnerability. If any of the affected features are enabled, a successful attack will result in a blocked input queue on the inbound interface. Only crafted UDP packets destined for the device could result in the interface being blocked, transit traffic will not block the interface.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available in the workarounds section of the advisory. This advisory is posted at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20090325-udp.shtml.
•
Excessive IPRT-3-PATHIDX error messages no longer appear in the log file.
•
When configuring an IP SSH version 2 connection, you can no longer create an RSA key that is less than 768 bits.
•
Debug messages no longer appear when you remove a Twingig converter SFP from the switch.
•
When you remove a Twingig converter SFP from the switch, the link state of the unconnected port belonging to a same port ASIC no longer remains in an up state.
•
TACACS+ authorization no longer fails on a device when an unknown TACACS+ attribute is received from the TACACS+ server.
•
An EAP-Success message is now sent to a supplicant after it is authenticated on a port.
•
The dot1x timeout reauth-period server interface configuration command now works correctly. In previous releases, the switch would reauthenticate correctly after the command was entered, but the switch would then reauthenticate every 10 minutes.
•
IPv6 MLD snooping now continues to work correctly after a switch in the stack reloads.
•
The cdpCacheAddress value now appears in a GLOBAL_UNICAST address.
•
The switch now correctly processes ingress traffic when a port is configured with a short 802.1x tx-period timer value (such as dot1x timeout tx-period 3).
•
The username is now properly logged when the remote command privileged EXEC command is used to configure a cluster member.
•
Multiple Cisco products are affected by denial of service (DoS) vulnerabilities that manipulate the state of Transmission Control Protocol (TCP) connections. By manipulating the state of a TCP connection, an attacker could force the TCP connection to remain in a long-lived state, possibly indefinitely. If enough TCP connections are forced into a long-lived or indefinite state, resources on a system under attack may be consumed, preventing new TCP connections from being accepted. In some cases, a system reboot may be necessary to recover normal system operation. To exploit these vulnerabilities, an attacker must be able to complete a TCP three-way handshake with a vulnerable system.
In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.
Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090908-tcp24.shtml.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE4 (Catalyst 3750-E Switches Only)
•
Debug messages no longer appear when you remove a Twingig converter SFP from the switch.
•
TACACS+ authorization no longer fails on a device when an unknown TACACS+ attribute is received from the TACACS+ server.
•
An EAP-Success message is now sent to a supplicant after it is authenticated on a port.
•
The dot1x timeout reauth-period server interface configuration command now works correctly. In previous releases, the switch would reauthenticate correctly after the command was entered, but the switch would then reauthenticate every 10 minutes.
•
IPv6 MLD snooping now continues to work correctly after a switch in the stack reloads.
•
The cdpCacheAddress value now appears in a GLOBAL_UNICAST address.
•
The switch now correctly processes ingress traffic when a port is configured with a short 802.1x tx-period timer value (such as dot1x timeout tx-period 3).
•
The username is now properly logged when the remote command privileged EXEC command is used to configure a cluster member.
•
Avaya IP phones now correctly authenticate on an 802.1x-enabled switch port.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3
•
An SNMP access-control list (ACL) now works correctly on virtual routing and forwarding (VRF) interfaces.
•
Intermittently switch reloads no longer occur when IP helper addresses are configured on a VLAN.
•
When multiple voice-over-IP phones are connected to a switch or switch stack with MAC authentication bypass enabled, setting the IEEE 802.1x timeout period too low no longer causes a switch in single-host mode to authenticate the phones using MAC authentication bypass, except when other data packets are received before CDP packets.
•
An end host no longer remains in the guest VLAN after an IEEE 802.1X authentication.
•
The show interfaces command output for a switch stack now shows the correct values for the output drops.
•
A switch no longer drops Cisco Group Management Protocol (CGMP) packets.
•
A switch stack can now send a VTP join message for a VLAN without access associated ports, but for which a Layer 3 VLAN interface exists without causing the VLAN to be pruned.
•
The switch no longer reloads with an address error if the TACACS+ server sends an authentication error when the access control system is configured and a timeout request occurs.
•
Layer 4 operations now work correctly for all port ranges in QoS policy maps.
•
A network loop or incorrect spanning-tree status no longer occurs when you enable cross-stack EtherChannel and connect customer edge devices across a Layer 2 protocol tunnel. The STP bridge protocol data units (BPDUs) now reach the remote end when they are received on an EtherChannel port that is not on the stack master.
•
When IEEE 802.1x port-based authentication is enabled on the switch, Extensible Authentication Protocol (EAP) notification packets from the supplicant are no longer discarded.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2
•
When the logging event-spanning-tree interface configuration command is configured and logging to the console is enabled, a topology change no longer generates a large number of logging messages.
•
When a secondary VLAN is disassociated from the primary VLAN, duplicate MAC addresses on the primary VLAN no longer remain in the MAC address table.
•
If you enter the no ip vrf vrf-name global configuration command to delete a VPN routing/forwarding instance on the switch when routing is not enabled on the switch, the VRF instance is no longer held in the delete queue.
•
Traceback messages no longer appear if you enter the no switchport interface configuration command to change a Layer 2 interface that belongs to a port channel to a routed port.
•
When unicast routing is disabled and then re-enabled, virtual routing and forwarding (VRF) routing is no longer disabled on the switch interfaces.
•
Switch ports in the stack now detect new devices after a stack-master failover.
•
The switch no longer unexpectedly reloads while configured with IEEE 802.1x authentication and the MAC authentication bypass feature.
•
When you configure a port channel as trusted by entering the ip dhcp snooping trust interface configuration command, the configuration is no longer lost when the link goes from down to up.
•
When you configure fallback bridging with redundant links on a switch stack, VLAN bridge STP now correctly blocks the SVIs and routed ports that lead to the redundant path. This works even if the physical ports configured on the bridge domain VLANs belong to the member switches in the stack.
•
When you enable detection of Cisco IP phones by entering the switchport voice detect cisco-phone interface configuration command, the interface is no longer disabled if you connect a third-party IP phone is connected to the interface.
Note
•
This traceback error no longer appears when you enter the show aaa subscriber profile privileged EXEC command:
*Mar 2 01:50:41.127: %PARSER-3-BADSUBCMD: Unrecognized subcommand 10 in exec command'show aaa subscriber profile WORD'-Traceback= D003B4 D00AC8 C908A0 C2F040 C8CA18 CB8984 93B670 932338
Note
•
An IP address can be assigned to a routed port that is up and also assigned to a routed port that is administratively down. If you remove the IP address from the down port, the switch no longer loses the hardware forwarding information.
•
A switch no longer unexpectedly reloads when you configure two or more authentication, authorization, and accounting (AAA) broadcast groups.
•
The switch no longer experiences a memory leak during an HTTP core process.
•
On a switch stack with multiple members, a switch now provides a timely response to an SNMP request on the BridgeMIB's object dot1dBaseNumPorts.
•
Enhanced IGRP (EIGRP) now works correctly when you enter the ip authentication key-chain eigrp interface configuration command.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1
•
A router that is configured for HTTP and voice-based services no longer unexpectedly reloads due to memory corruption.
•
When AAA is enabled and you use the aaa group server radius group-name global configuration command to put the switch in server group configuration mode, entering the server-private command no longer causes the switch to reload.
•
The switch no longer reloads when you use the aaa authentication eou default group radius enable global configuration command to configure an EAP over UDP (EOU) method list.
•
Note
If more than 24 switch ports are configured with the same policy map, CPU_HOG traceback errors no longer occur when the switch is reloaded.
•
High CPU usage (greater than 90 percent) no longer occurs on the switch when you first connect a new device.
•
You can now use the interface range interface configuration command to configure IP source guard on member switches.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE
•
The switch no longer reloads when you use a Kron command scheduler routine to automatically copy configuration data using the Secure Copy Protocol (SCP). (Kron is a Cisco IOS utility for scheduling non-prompting CLI commands to execute at a later time.)
•
When a switch is connected to a third-party router through an EtherChannel and the EtherChannel is running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel no longer fail after you enter the switchport trunk native vlan vlan-id interface configuration command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.
•
If IEEE 802.1Q tunneling and Layer 2 protocol tunneling are configured first on physical ports, and the ports are then added to an unconfigured port channel, the port channel no longer stops forwarding traffic if one or more physical ports in the EtherChannel are shut down.
•
A switch with the Dynamic ARP Inspection feature enabled no longer experiences the issue that triggered the display of buffer sharecount messages under certain patterns of ARP packet traffic.
•
When a switch interface is configured with trust boundary and Cisco Discovery Protocol (CDP) or the CDP table is repeatedly enabled or cleared, the switch might reload.
•
When a stack master changeover event occurs, the backup interface no longer loses traffic. In previous releases, traffic loss occurred for up to 4 seconds under these conditions:
–
–
–
–
•
When a VLAN includes multiple MAC addresses, the number of MAC addresses shown in SNMP now matches the output of the show mac-address count vlan vlan-id privileged EXEC command.
•
When changing a switch port access VLAN from static to dynamic or the reverse, this message no longer appears:
01:43:55: PSECURE: Assert failure: is_etherchnl(hwidb_or_null swidb)): ../switch/psecure/psecure_ifc.c: 412: psecure_get_vlanid (l2a1-5) 01:43:55Traceback= 804484 809604 802258 806904 70FC 8D70 5C97BC 6901DC 6903CC 9EF8D8 9E6CC4 (l2a1-5)•
This message no longer appears when you set an interface back to its default configuration by using the default interface configuration command, this message no longer appears:
%SM-4-STOPPED: Event 'mabAbort' ignored because the state machine is stopped: dot1x_auth_mab-Traceback= 1D2368 3C1BA8 3C1D40 3C16A8 9EF8D8 9E6CC4•
When you configure two local source SPAN sessions and then delete these SPAN sessions, the switch allows the creation of new sessions and no longer displays this error message:
% Platform can support a maximum of 2 source sessions•
Changing the spanning tree mode from MSTP to other spanning modes no longer causes tracebacks.
•
During master switch failover, a VLAN that has been error disabled on a port is no longer re-enabled after the master switch changeover.
•
When the switch has VRF interfaces configured and you disable unicast routing by entering the no ip routing global configuration command and then re-enable unicast routing, VRF routing now functions correctly over the VRF interface.
•
Broadcast storm control now works correctly on IEEE 802.1Q trunk ports.
•
The cpmCPURisingThreshold traps on the switch are no longer missing the cpmProcExtUtil5SecRev and cpmProcessTimeCreated trap components. Note that although the components were missing from the traps, the PROCESS MIB was still populating the objects.
•
OSPF hello packets now have the correct CoS value of 7.
•
A Cisco IP Phone now works correctly when it is connected to a port that is configured with CDP bypass and multidomain authentication (MDA).
•
The interface between two 3560-E switches that are running the 12.2(35)SE2 software release with the TwinGig converter module installed and connected through the CAB-SFP-50CM cable no longer stays down when you disconnect and then reconnect one end of the cable, if you manually shut down the switch, or if one of the switches reloads.
•
When you enter the show interface status privileged EXEC command on the switch, a port no longer might show notconnect for an inline power port when the show power inline privileged EXEC command shows that the port is still delivering power.
•
A significant delay no longer occurs when you remove an access control list (ACL) from a switch stack under these conditions:
–
–
–
•
ACLs are now configured correctly when they contain ICMP codes 251 to 255.
•
If you upgrade from Cisco IOS Release 12.2(35)SE1 to Release 12.2(37)SE, a security violation no longer occurs when:
–
–
•
The TxBufferFullDropCount no longer continuously increments on a switch or switch stack.
•
The Total- output-drops field in the show interfaces privileged EXEC command output now displays accurate ASIC drops.
•
When IGMP snooping is enabled, CGMP interoperability mode now works as it should when the upstream multicast router is set up correctly with PIM and IP CGMP.
•
If you enter a space before a comma in the define interface-range or the interface range global configuration command, the space before the comma is now saved in the switch configuration.
•
A switch configured for Link Layer Discovery Protocol (LLDP) now correctly reports the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes.
•
When VTP pruning is enabled, the switch no longer might experience high CPU usage (greater than 90 percent) for up to 20 minutes after the link comes up simultaneously on multiple trunk ports.
•
On a switch that supports fallback bridging, when a bridge-group is configured on some VLANs, non-IP traffic in the VLANs destined to a known MAC address are no longer flooded in the bridge-group.
•
When you are using AAA for Telnet and console authentication and login failure and success debugging is enabled, the username now shows correctly in the log.
•
Traffic is now received on a member port in a switch stack under these conditions:
–
–
–
•
When the switch has VTP pruning and an RSPAN session configured, the RSPAN VLAN traffic is now correctly pruned as set up by the VTP pruning configuration.
•
On a switch with routed ports, when you configure MAC address-table aging time by entering the mac address-table aging-time time global configuration command and then enter the show running-config privileged EXEC command, the output no longer displays the aging time values for internal VLANs.
•
When UDLD is enabled on a Layer 2 interface, and the native VLAN for the port is not configured as a VLAN on the switch, UDLD no longer puts the port into an error-disabled state.
•
A switch no longer fails when you enter the show interfaces vlan vlan-id switchport privileged EXEC command.
•
If you enter the hostname global configuration command followed by a hostname that contains illegal characters, for example, one that appears to be an IP address, the switch now displays a warning message, but the specified hostname is configured.
•
A switch no longer fails under these conditions:
–
–
–
•
When port security is configured on a switch, a device MAC address is now correctly learned on that port. (In previous releases, a new device MAC address was not learned on a port-security enabled port, and the device MAC address was not added to the list of secure addresses.)
•
The output of these show user EXEC commands now display the correct status of ports in a cross-stack EtherChannel bundle:
–
–
•
Web authentication no longer stops working when IEEE 802.1X re-authentication is enabled and the re-authentication timer expires.
Documentation Updates
•
•
•
•
•
•
Updates to the Software Configuration Guide
These are the updates to the Software Configuration Guide for the Catalyst 3750-E and Catalyst 3560-E switches:
•
You can also enable the login enhancements feature, which logs both failed and unsuccessful login attempts. Login enhancements can also be configured to block future login attempts after a set number of unsuccessful attempts are made. For more information, see the Cisco IOS Login Enhancements documentation at this URL:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gt_login.html
•
After you have entered the eigrp stub router configuration command, only the eigrp stub connected summary command takes effect. Although the CLI help might show the receive-only and static keywords and you can enter these keywords, the switch running the IP base image always behaves as if the connected and summary keywords were configured.
•
You can configure 104 policies whether or not VRFs are configured on the switch or the switch stack.
This is the correct guideline:
You can configure up to 105 policies whether or not VRFs are configured on the switch or the switch stack.
•
Per-user ACLs are supported only in single-host mode.
•
In Cisco IOS Release 12.2(40)SE and earlier, each 10/100/1000 PoE port provides up to 15.4 W of power to the device. Cisco IOS Release 12.2(44)SE and later supports enhanced PoE. An enhanced PoE port can support any additional powered device that requires up to 20 watts.
•
Beginning in privileged EXEC mode, follow these steps to configure amount of power budgeted to a powered device connected to a specific PoE port:
To return to the default setting, use the no power inline consumption default interface configuration command.
For information about the output of the show power inline consumption default privileged EXEC command, see the command reference for this release.
•
Note
This chapter consists of these sections:
–
–
–
Understanding Embedded Event Manager
The embedded event manager (EEM) monitors key system events and then acts on them though a set policy. This policy is a programmed script that you can use to customize a script to invoke an action based on a given set of events occurring. The script generates actions such as generating custom syslog or Simple Network Management Protocol (SNMP) traps, invoking CLI commands, forcing a failover, and so forth. The event management capabilities of EEM are useful because not all event management can be managed from the switch and because some problems compromise communication between the switch and the external network management device. Network availability is improved.if automatic recovery actions are performed without rebooting the switch,
Figure 1 shows the relationship between the EEM server, the core event publishers (event detectors), and the event subscribers (policies). The event publishers screen events and when there is a match on an event specification that is provided by the event subscriber. Event detectors notify the EEM server when an event occurs. The EEM policies then implement recovery based on the current state of the system and the actions specified in the policy for the given event.
Figure 1 Embedded Event Manager Core Event Detectors
These sections contain this conceptual information:
–
–
–
Event Detectors
EEM software programs known as event detectors determine when an EEM event occurs. Event detectors are separate systems that provide an interface between the agent being monitored, for example SNMP, and the EEM polices where an action can be implemented. Event detectors are generated only by the master switch. CLI and routing processes also run only from the master switch.
Note
EEM allows these event detectors:
–
–
–
–
–
–
–
–
–
–
–
Publishes events for these timers:
–
–
–
–
Watchdog event detector (IOSWDSysMon). This detector applies only to the master switch.
Publishes an event when one of these events occurs:
–
–
Two events can be monitored at the same time, and the event publishing criteria requires that one or both events cross their specified thresholds.
Embedded Event Manager Actions
EEM provides actions that occur in response to an event. EEM supports these actions:
–
–
–
–
–
–
–
Embedded Event Manager Policies
EEM can monitor events and provide information, or take corrective action when the monitored events occur or a threshold is reached. An EEM policy is an entity that defines an event and the actions to be taken when that event occurs.
There are two types of EEM policies: an applet or a script. An applet is a simple policy that is defined within the CLI configuration. It is a concise method for defining event screening criteria and the actions to be taken when that event occurs. Scripts are defined on the networking device by using an ASCII editor. The script is then copied to the networking device and registered with EEM.
You use EEM to write and implement your own policies using the EEM policy tool command language (TCL) script. When you configure a TCL script on the master switch and the file is automatically sent to the member switches. The user-defined TCL scripts must be available in the member switches so that if the master switch changes, the TCL scripts policies continue to work.
Cisco enhancements to TCL in the form of keyword extensions facilitate the development of EEM policies. These keywords identify the detected event, the subsequent action, utility information, counter values, and system information.
For complete information on configuring EEM policies and scripts, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.
Embedded Event Manager Environment Variables
EEM uses environment variables in EEM policies. These variables are defined in a EEM policy tool command language (TCL) script by running a CLI command and the event manager environment command. These environment variables can be defined in EEM:
–
Defined by the user for a user-defined policy.
–
Defined by Cisco for a specific sample policy.
–
Defined by Cisco and can be read-only or read-write. The read-only variables are set by the system before an applet starts to execute. The single read-write variable, _exit_status, allows you to set the exit status for policies triggered from synchronous events.
Cisco-defined environment variables and Cisco system-defined environment variables might apply to one specific event detector or to all event detectors. Environment variables that are user-defined or defined by Cisco in a sample policy are set by using the event manager environment global configuration command. You must defined the variables in the EEM policy before you register the policy.
For information about the environmental variables that EEM supports, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.
Configuring Embedded Event Manager
These sections contain this configuration information:
–
–
For complete information about configuring embedded event manager, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.
Registering and Defining an Embedded Event Manager Applet
Beginning in privileged EXEC mode, perform this task to register an applet with EEM and to define the EEM applet using the event applet and action applet configuration commands.
Note
This example shows the output for EEM when one of the fields specified by an SNMP object ID crosses a defined threshold:
Switch(config-applet)# event snmp oid 1.3.6.1.4.1.9.9.48.1.1.1.6.1 get-type exact entry-op lt entry-val 5120000 poll-interval 10These examples show actions that are taken in response to an EEM event:
Switch(config-applet)# action 1.0 syslog priority critical msg "Memory exhausted; current available memory is $_snmp_oid_val bytes"Switch (config-applet)# action 2.0 force-switchoverRegistering and Defining an Embedded Event Manager TCL Script
Beginning in privileged EXEC mode, perform this task to register a TCL script with EEM and to define the TCL script and policy commands.
This example shows the sample output for the show event manager environment command:
Switch# show event manager environment allNo. Name Value1 _cron_entry 0-59/2 0-23/1 * * 0-62 _show_cmd show ver3 _syslog_pattern .*UPDOWN.*Ethernet1/0.*4 _config_cmd1 interface Ethernet1/05 _config_cmd2 no shutThis example shows a CRON timer environment variable, which is assigned by the software, to be set to every second minute, every hour of every day:
Switch (config)# event manager environment_cron_entry 0-59/2 0-23/1 * * 0-6This example shows the sample EEM policy named tm_cli_cmd.tcl registered as a system policy. The system policies are part of the Cisco IOS image. User-defined TCL scripts must first be copied to flash memory:
Switch (config)# event manager policy tm_cli_cmd.tcl type systemDisplaying Embedded Event Manager Information
To display information about EEM, including EEM registered policies and EEM history data, see the Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3T.
•
Privileged EXEC
event manager scheduler clear
event manager update user policy
show event manager detector
show event manager version
Global Configuration
event manager detector rpc
event manager directory user repository
Applet Configuration (config-applet)
event rpc
event snmp-notification
trigger (EEM)
Trigger Applet Configuration (config-applet-trigger)
attribute (EEM)
correlate
Event Trigger Configuration (config-event-trigger)
event owner
Updates to the Command Reference
These are updates to the command reference:
•
Pair status
The status of the pair of wires on which TDR is running:
•
•
•
power inline
Use the power inline interface configuration command on the switch stack or on a standalone switch to configure the power management mode on the Power over Ethernet (PoE) ports. Use the no form of this command to return to the default settings.
power inline {auto [max max-wattage] | never | police [action log] | port maximum | static [max max-wattage]}
no power inline {auto | never | police | port | static}
Syntax Description
Defaults
The default is auto (enabled).
The maximum wattage is 15400 mW.
Command Default
Interface configuration
Command History
12.2(35)SE2
This command was introduced.
12.2(44)SE
The port maximum keywords were added.
Usage Guidelines
This command is supported only on PoE-capable ports. If you enter this command on a port that does not support PoE, this error message appears:
Switch(config)# interface gigabitethernet1/0/1Switch(config-if)# power inline auto^% Invalid input detected at '^' marker.In a switch stack, this command is supported on all ports in the stack that support PoE.
Use the max max-wattage option to disallow higher-power powered devices. With this configuration, when the powered device sends Cisco Discovery Protocol (CDP) messages requesting more power than the maximum wattage, the switch removes power from the port. If the powered-device IEEE class maximum is greater than the maximum wattage, the switch does not power the device. The power is reclaimed into the global power budget.
Note
If the switch denies power to a powered device (the powered device requests more power through CDP messages or if the IEEE class maximum is greater than the maximum wattage), the PoE port is in a power-deny state. The switch generates a system message, and the Oper column in the show power inline privileged EXEC command output shows power-deny.
Use the power inline static max max-wattage command to give a port high priority. The switch allocates PoE to a port configured in static mode before allocating power to a port configured in auto mode. The switch reserves power for the static port when it is configured rather than upon device discovery. The switch reserves the power on a static port even when there is no connected device and whether or not the port is in a shutdown or in a no shutdown state. The switch allocates the configured maximum wattage to the port, and the amount is never adjusted through the IEEE class or by CDP messages from the powered device. Because power is pre-allocated, any powered device that uses less than or equal to the maximum wattage is guaranteed power when it is connected to a static port. However, if the powered device IEEE class is greater than the maximum wattage, the switch does not supply power to it. If the switch learns through CDP messages that the powered device needs more than the maximum wattage, the powered device is shut down.
Note
If the switch cannot pre-allocate power when a port is in static mode (for example, because the entire power budget is already allocated to other auto or static ports), this message appears: Command rejected: power inline static: pwr not available. The port configuration remains unchanged.
When you configure a port by using the power inline auto or the power inline static interface configuration command, the port autonegotiates by using the configured speed and duplex settings. This is necessary to determine the power requirements of the connected device (whether or not it is a powered device). After the power requirements have been determined, the switch hardcodes the interface by using the configured speed and duplex settings without resetting the interface.
When you configure a port by using the power inline never command, the port reverts to the configured speed and duplex settings.
If a port has a Cisco powered device connected to it, you should not use the power inline never command to configure the port. A false link-up can occur, placing the port in an error-disabled state.
Examples
This example shows how to enable detection of a powered device and to automatically power a PoE port on a Catalyst 3750-E switch:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline autoThis example shows how to configure a PoE port on a Catalyst 3560-E switch to allow a class 1 or a class 2 powered device:
Switch(config)# interface gigabitethernet0/2Switch(config-if)# power inline auto max 7000This example shows how to disable powered-device detection and to not power a PoE port on a Catalyst 3750-E switch:
Switch(config)# interface gigabitethernet1/0/2Switch(config-if)# power inline neverThis example shows how to configure a port to supply 20w to an attached device:
Switch(config-if)# power inline port maximum 20000Switch(config-if)# power inline auto max ?<15400-20000> milli-wattsYou can verify your settings by entering the show power inline user EXEC command.
Related Commands
Updates to the System Message Guide
These are the updates to System Message Guide for the Catalyst 3750-E and Catalyst 3560-E switches:
Error Message ACLMGR-4-UNLOADINGFSPAN Unloading[chars]session[dec][chars]featureExplanation The access control list (ACL) manager is unable to store the flow-based SPAN (FSPAN) configuration, and this feature has been temporarily disabled for the specified session. The first [chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is the type of traffic being filtered: MAC, IPv4, or IPv6.
Recommended Action Specify an SDM template that allocates more system resources for ACLs, simplify the ACL, or use the same ACLs on multiple interfaces.
Error Message ACLMGR-4-RELOADEDFSPAN Reloading [chars] session [dec] [chars] featureExplanation The access control list (ACL) manager can store the flow-based SPAN configuration for the specified session. One or more ACLs had previously been unloaded because of lack of hardware memory. The first [chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is the type of traffic being filtered: MAC, IPv4, or IPv6.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. [enet] is the supplicant MAC address, and [chars] is the interface. This message might appear if the IEEE 802.1x feature is enabled.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, manually remove it from that port.
Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will remain stand-alone.Explanation The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel. The second [chars] is the port number.
Recommended Action Ensure that the other ports in the bundle have the same configuration]
Error Message ILPOWER-3-CONTROLLER_PORT_ERR:Controller port error, Interface Fa0/7:Power given, but link is not up.Explanation The inline-power-controller reported an error on an interface.
Recommended Action Enter the shutdown and no shutdown interface configuration commands on the affected interfaces. Upgrade to Cisco IOS Release12.1(14)EA1 or later, which provides an electrostatic discharge (ESD) recovery mechanism.
Error Message PLATFORM_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefixExplanation A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ip unicast failed route privileged EXEC command lists the failed prefixes.
Recommended Action No action is required.
Error Message PLATFORM_HCEF-3-ADJ: [chars]Explanation This message appears when an unsupported feature is configured on a switch running Cisco IOS Release 12.2(25)SE. [chars] is the error message.
Recommended Action Determine if a generic routing encapsulation (GRE) tunnel or the ip cef accounting global configuration command are configured. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnels are supported. If the GRE tunnel is configured, remove the tunnel, or upgrade the switch software to a Cisco IOS release when the GRE feature is needed. If the ip cef accounting command is configured, remove it by using the no ip cef accounting global configuration command.
Note
Error Message PLATFORM_IPv6_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefixExplanation A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ipv6 unicast retry route privileged EXEC command lists the failed prefixes.
Recommended Action No action is required.
Error Message PLATFORM_SPAN-3-FEATUREMISMATCH:[chars] cannot be supported with the image running on switch [dec].Explanation A switch stack member software image does not support a specific flow-based SPAN (FSPAN) access control list (ACL) filter. [chars] is the FSPAN ACL filter that is not supported, and [dec] is the stack member number.
Recommended Action Upgrade to an image that supports the FSPAN ACL filter.
Error Message SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all VlansExplanation The interface has been added to all VLANs. [chars] is the added interface.
Recommended Action No action is required.
Error Message SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all VlansExplanation The interface has been deleted from all VLANs. [chars] is the deleted interface.
Recommended Action No action is required.
Error Message SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].Explanation The VLAN Trunking Protocol (VTP) domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.
Recommended Action No action is required.
Error Message VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit.Explanation The system has shut down the specified interface because too many hosts have requested access to that interface. [chars] is the interface name.
Recommended Action To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command.
Error Message VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response.Explanation The VLAN membership policy server (VMPS) has specified a VLAN name that is unknown to the switch. [chars] is the VLAN name.
Recommended Action Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.
Error Message WCCP-5-CACHEFOUND: Web Cache [IP_address] acquired.Explanation The switch has acquired the specified web cache. [IP_address] is the web cache IP address.
Recommended Action No action is required.
Error Message WCCP-1-CACHELOST: Web Cache [IP_address] lost.Explanation The switch has lost contact with the specified web cache. [IP_address] is the web cache IP address.
Recommended Action Verify the operation of the web cache by entering the show ip wccp web-cache privileged EXEC command.
Updates to the Getting Started Guides
These are the updates to the Getting Started Guides for the Catalyst 3750-E and Catalyst 3560-E switches:
•
–
–
•
–
Updates to the Hardware Installation Guide
These are the updates for the Hardware Installation Guide for the Catalyst 3750-E and Catalyst 3560-E switches:
•
•
Caution
Updates to the Regulatory Compliance and Safety Information
These are the updates to the Regulatory Compliance and Safety information for the Catalyst 3750-E and Catalyst 3560-E switches:
This Network Equipment-Building System (NEBS) compliance statement information was added to the Regulatory Standards Compliance section:
Regulatory Standards Compliance
This section includes all regulatory, safety, and EMC standards. The Catalyst 3750-E and Catalyst 3560-E switches are in compliance with national and international standards as described in Table 6.
For specific details about the years, revisions, and relevant amendments, refer to the applicable declaration of conformity available at:
http://tools.cisco.com/cse/prdapp/jsp/externalsearch.do?action=externalsearch&page=EXTERNAL_SEARCH&module=EXTERNAL_SEARCH.
Cautions and Regulatory Compliance Statements for NEBS
This section includes the cautions and regulatory compliance statements for the Network Equipment-Building System (NEBS) certification from the Telcordia Electromagnetic Compatibility and Electrical Safety - Generic Criteria for Network Telecommunications Equipment (A Module of LSSGR, FR-64; TSGR, FR-440; and NEBSFR, FR-2063) Telcordia Technologies Generic Requirements, GR-1089-CORE, Issue 4, June 2006 (see Table 7).
Related Documentation
These documents provide complete information about the Catalyst 3750-E and Catalyst 3560-E switches and are available on Cisco.com:
http://www.cisco.com/en/US/products/ps7077/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps7078/tsd_products_support_series_home.html
These documents provide complete information about the switches:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
These compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
•
•
•
•
For other information about related products, see these documents:
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0908R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008-2009 Cisco Systems, Inc. All rights reserved.
Guest
