Table Of Contents
Release Notes for Catalyst 3750-E
and Catalyst 3560-E Switches, Cisco IOS Release 12.2(40)SEDevice 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)
Updates to the Getting Started Guides
Updates to the Software Configuration Guide
Configuring Source-Specific Multicast
Configuring Embedded Event Manager (New Chapter)
Unsupported Embedded Event Manager Commands
Updates to the Command References
Updates to the System Message Guides
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(40)SE
Revised January 6, 2009
Cisco IOS Release 12.2(40)SE runs on all Catalyst 3750-E and Catalyst 3560-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(40)SE and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
You can download the switch software from this site (registered Cisco.com users with a login password):
http://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 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 SFP2 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
Intel Pentium II1
64 MB2
256
1024 x 768
Small
1 We recommend Intel Pentium 4.
2 We recommend 256-MB DRAM.
Software Requirements
Table 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-35.SE2.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)
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)
SPAN and RSPAN
This is the SPAN and Remote SPAN (RSPAN) limitation.
•
There is no workaround. This is a hardware limitation. (CSCei10129)
•
High CPU utilization can also occur with other conditions, such as when debug messages are logged at a high rate to the console.
Use one of these workarounds:
–
–
–
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
VLANs
This is a VLAN limitation:
•
The workaround is to enter the shut and no shut interface configuration commands on the port to reset the authentication status. (CSCsf98557)
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:
•
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 might stop forwarding traffic if one or more physical ports in the EtherChannel are shut down.
These are the workarounds:
–
–
•
When a cross-stack LACP EtherChannel has a maximum configuration, such as eight active and eight hot-standby ports, and there are multiple rapid sequential master failovers and stack rejoins that cause extreme stress, it is possible that the port channel will not function as expected. Some ports might not join the EtherChannel, and traffic might be lost. You can detect the condition by using the remote command all show etherchannel summary privileged EXEC command.
There is no workaround. The out-of-sync switches must be reloaded.
•
When a switch interface is configured with trust boundary and Cisco Discovery Protocol (CDP) or the CDP table is repeatedly disabled, enabled, or cleared, the switch might reload.
The workaround is to avoid repeatedly disabling, enabling, or clearing CDP or the CDP table when trust boundary is configured on an interface. Or, disable trust boundary first before repeatedly disabling, enabling, or clearing CDP or the CDP table.
•
The switch might display tracebacks similar to this example when an EtherChannel interface port-channel type changes from Layer 2 to Layer 3 or the reverse:
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.
•
When a secondary VLAN is disassociated from the primary VLAN, duplicate MAC addresses on the primary VLAN remain in the MAC address table.
The workaround is to disassociate the secondary VLAN from the primary VLAN by entering these commands (in this order):
clear port-security {all | interface interface-id) privileged EXEC command
primary-vlan association remove vlan-id VLAN configuration mode command.
•
Traceback messages 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.
There is no workaround.
•
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.
•
When booting a switch stack configured for IP source guard with port security and dynamic ARP inspection, a message similar to this might appear:
SYS-2-LINKED: Bad enqueue of 2A3DE74 in queue 22881BC (l3a3-9) -Process= "Port-Security", ipl= 6, pid= 161 (l3a3-9) -Traceback= 119CC50 11D2264 9571E0 119B4E0 95D41C 80DBD8 80E734 80B998 80AAD4 80B55C 9EB158 9E2544 (l3a3-9)
There is no workaround. This message is only information, switch functionality is not affected.
•
When you enter an all 0s route with an all 1s mask in the routing table and the next hop is entered as an interface, a traceback message appears.
The workaround is to use an IP address as the next hop instead of an interface.
•
The error message %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND might appear for a switch stack under these conditions:
–
–
–
You can use one of these workarounds:
–
–
•
When changing a switch port access VLAN from static to dynamic or the reverse, a message similar to this might appear:
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)
There is no workaround necessary. This message does not affect switch functionality.
•
When you are configuring a SPAN session, this message might erroneously appear even when two source sessions are not configured:
% Platform can support a maximum of 2 source sessions
The workaround is to reboot the switch stack.
•
Changing the spanning tree mode from rapid STP to MSTP can cause tracebacks when the virtual port error-disable feature is enabled when the STP mode is changed.
There is no workaround.
•
In certain situations, during master switch failover, a VLAN that has been error disabled on a port might be re-enabled after the master switchover, even though the port has not been configured for automatic recovery.
There is no workaround.
•
When unicast routing is disabled and then re-enabled, virtual routing and forwarding (VRF) routing is disabled on the switch interfaces.
The workaround is to enter the shut and no shut interface configuration commands on the affected interfaces.
•
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
•
After a stack-master failover, switch ports in the stack cannot detect new devices. This only affects new devices connected to the switch ports. Devices that were connected to active ports before the failover remain in a trusted state.
There is no workaround.
•
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.
•
A delay can occur you remove an access control list (ACL) from a switch stack under these conditions:
–
–
–
–
The delay can increase, up to 30 minutes, depending on the number of SVIs that are attached to the policy map. The delay does not affect the operation of the policy-map. However, either of these workarounds will reduce the length of the delay:
–
–
•
In Cisco IOS Release 12.2(35)SE and Cisco IOS Release 12.2(37)SE, 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 not saved in the switch configuration.
There is no workaround.
•
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.
•
Traffic is not received on a member port in a switch stack under these conditions:
–
–
–
The workaround is to enter the shutdown and no shutdown interface configuration commands on the affected interface, or to reload the entire stack instead of a single member switch.
Resolved Caveats
This section describes the caveats that have been resolved in this release:
•
•
•
When the interface range global configuration command and then the ip arp inspection trust interface configuration command are configured on a large number of ports on multiple stack members, this message no longer appears:
PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 5, class 45, max_msg 32, total throttled 17•
The system message HPSECURE-6-ADDR_REMOVED no longer appears for a switch stack under these conditions:
–
–
–
•
When multiple switches are added to a running switch stack, a long delay can occur between the time that the switches enter the Ready state (as shown by the output of the show switch command) and the time that link detection becomes active and the switch starts carrying traffic.
This delay might last for several minutes. However, the delay is shorter than in Cisco IOS Release 12.2(40)SE and earlier. In those releases, a delay of up to 10 minutes could occur when multiple members were added to an active switch stack.
•
MAC addresses learned on an EtherChannel port are no longer deleted from the MAC address table even when the MAC-address-table aging timeout value is longer than the ARP timeout value.
•
Clearing secure addresses by entering the clear port-security global configuration command in a stack member no longer causes traffic to be dropped from the switch.
•
When both an authorized data domain and an authorized voice domain are present on a port and you change the port VLAN configuration to equal the assigned VLAN, a traceback error no longer appears.
•
The switch correctly shows that the DATA domain is in guest-VLAN when a non-IEEE 802.1x capable PC is connected behind an IP phone on a port that:
–
–
–
•
MAC flap-notification no longer occurs when a switch is running VLAN bridge spanning-tree protocol (STP) and fallback bridging is configured on the VLANs running STP.
•
Multiple Spanning-Tree Protocol (MSTP) convergence time has been improved for Cisco IOS Release 12.2.
•
When unicast Reverse Path Forwarding (uRPF) is configured in strict mode and the return path is statically configured to point to an interface that is not an ingress interface, packets are dropped as expected. The switch now correctly increments the relevant hardware counter and not the software counter.
•
When port security is configured on a PVLAN interface, the dynamic MAC address is removed from the interface as expected.
•
During switch configuration, an error message no longer appears under either of these conditions:
–
–
•
The SNMP bridge object dot1dStpRootPort now shows the stack switch root port number instead of the stack port ID of the member switch.
•
When removing a member switch from the stack and you enter the show tech-support privileged EXEC command or the show interfaces privileged EXEC command, the switch no longer resets.
•
The switch now sends an EAP success packet to the client after a IEEE 802.1x multidomain authentication port t successfully reauthenticates.
Documentation Updates
These sections provide updates to the product documentation:
•
•
•
•
•
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 Software Configuration Guide
These sections contain the updates to the Software Configuration Guide for the Catalyst 3750-E and Catalyst 3560-E switches:
•
•
•
EIGRP Routing Note
If the switch is running the IP base feature set, you can configure complete EIGRP routing. However, the configuration is not implemented because the IP base feature set supports only EIGRP stub routing, as described in the "Configuring IP Unicast Routing" chapter of the software configuration guide.
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.
Configuring Source-Specific Multicast
This section describes how to configure source-specific multicast (SSM). For a complete description of the SSM commands in this section, refer to the "IP Multicast Routing Commands" chapter of the Cisco IOS IP Command Reference, Volume 3 of 3: Multicast. To locate documentation for other commands that appear in this chapter, use the command reference master index, or search online.
The SSM feature is an extension of IP multicast in which datagram traffic is forwarded to receivers from only those multicast sources that the receivers have explicitly joined. For multicast groups configured for SSM, only SSM distribution trees (no shared trees) are created.
SSM Components Overview
SSM is a datagram delivery model that best supports one-to-many applications, also known as broadcast applications. SSM is a core networking technology for the Cisco implementation of IP multicast solutions targeted for audio and video broadcast application environments. The switch supports these components that support the implementation of SSM:
•
PIM-SSM is the routing protocol that supports the implementation of SSM and is derived from PIM sparse mode (PIM-SM).
•
To run SSM with IGMPv3, SSM must be supported in the Cisco IOS router, the host where the application is running, and the application itself.
How SSM Differs from Internet Standard Multicast
The current IP multicast infrastructure in the Internet and many enterprise intranets is based on the PIM-SM protocol and Multicast Source Discovery Protocol (MSDP). These protocols have the limitations of the Internet Standard Multicast (ISM) service model. For example, with ISM, the network must maintain knowledge about which hosts in the network are actively sending multicast traffic.
The ISM service consists of the delivery of IP datagrams from any source to a group of receivers called the multicast host group. The datagram traffic for the multicast host group consists of datagrams with an arbitrary IP unicast source address S and the multicast group address G as the IP destination address. Systems receive this traffic by becoming members of the host group.
Membership in a host group simply requires signalling the host group through IGMP version 1, 2, or 3. In SSM, delivery of datagrams is based on (S, G) channels. In both SSM and ISM, no signalling is required to become a source. However, in SSM, receivers must subscribe or unsubscribe to (S, G) channels to receive or not receive traffic from specific sources. In other words, receivers can receive traffic only from (S, G) channels to which they are subscribed, whereas in ISM, receivers need not know the IP addresses of sources from which they receive their traffic. The proposed standard approach for channel subscription signalling use IGMP include mode membership reports, which are supported only in IGMP version 3.
SSM IP Address Range
SSM can coexist with the ISM service by applying the SSM delivery model to a configured subset of the IP multicast group address range. Cisco IOS software allows SSM configuration for the IP multicast address range of 224.0.0.0 through 239.255.255.255. When an SSM range is defined, existing IP multicast receiver applications do not receive any traffic when they try to use an address in the SSM range (unless the application is modified to use an explicit (S, G) channel subscription).
SSM Operations
An established network, in which IP multicast service is based on PIM-SM, can support SSM services. SSM can also be deployed alone in a network without the full range of protocols that are required for interdomain PIM-SM (for example, MSDP, Auto-RP, or bootstrap router [BSR]) if only SSM service is needed.
If SSM is deployed in a network already configured for PIM-SM, only the last-hop routers support SSM. Routers that are not directly connected to receivers do not require support for SSM. In general, these not-last-hop routers must only run PIM-SM in the SSM range and might need additional access control configuration to suppress MSDP signalling, registering, or PIM-SM shared tree operations from occurring within the SSM range.
Use the ip pim ssm global configuration command to configure the SSM range and to enable SSM. This configuration has the following effects:
•
•
•
IGMPv3 Host Signalling
In IGMPv3, hosts signal membership to last hop routers of multicast groups. Hosts can signal group membership with filtering capabilities with respect to sources. A host can either signal that it wants to receive traffic from all sources sending to a group except for some specific sources (called exclude mode), or that it wants to receive traffic only from some specific sources sending to the group (called include mode).
IGMPv3 can operate with both ISM and SSM. In ISM, both exclude and include mode reports are applicable. In SSM, only include mode reports are accepted by the last-hop router. Exclude mode reports are ignored.
Configuration Guidelines
This section contains the guidelines for configuring SSM.
Legacy Applications Within the SSM Range Restrictions
Existing applications in a network predating SSM do not work within the SSM range unless they are modified to support (S, G) channel subscriptions. Therefore, enabling SSM in a network can cause problems for existing applications if they use addresses within the designated SSM range.
Address Management Restrictions
Address management is still necessary to some degree when SSM is used with Layer 2 switching mechanisms. Cisco Group Management Protocol (CGMP), IGMP snooping, or Router-Port Group Management Protocol (RGMP) support only group-specific filtering, not (S, G) channel-specific filtering. If different receivers in a switched network request different (S, G) channels sharing the same group, they do not benefit from these existing mechanisms. Instead, both receivers receive all (S, G) channel traffic and filter out the unwanted traffic on input. Because SSM can re-use the group addresses in the SSM range for many independent applications, this situation can lead to decreased traffic filtering in a switched network. For this reason, it is important to use random IP addresses from the SSM range for an application to minimize the chance for re-use of a single address within the SSM range between different applications. For example, an application service providing a set of television channels should, even with SSM, use a different group for each television (S, G) channel. This setup guarantees that multiple receivers to different channels within the same application service never experience traffic aliasing in networks that include Layer 2 switches.
IGMP Snooping and CGMP Limitations
IGMPv3 uses new membership report messages that might not be correctly recognized by older IGMP snooping switches. For more information about switching issues related to IGMP (especially with CGMP), refer to the "Configuring IGMP Version 3" section of the "Configuring IP Multicast Routing" chapter.
State Maintenance Limitations
In PIM-SSM, the last hop router continues to periodically send (S, G) join messages if appropriate (S, G) subscriptions are on the interfaces. Therefore, as long as receivers send (S, G) subscriptions, the shortest path tree (SPT) state from the receivers to the source is maintained, even if the source does not send traffic for longer periods of time (or even never).
This case is opposite to PIM-SM, where (S, G) state is maintained only if the source is sending traffic and receivers are joining the group. If a source stops sending traffic for more than 3 minutes in PIM-SM, the (S, G) state is deleted and only re-established after packets from the source arrive again through the RPT. Because no mechanism in PIM-SSM notifies a receiver that a source is active, the network must maintain the (S, G) state in PIM-SSM as long as receivers are requesting receipt of that channel.
Configuring SSM
Beginning in privileged EXEC mode, follow these steps to configure SSM:
Monitoring SSM
Beginning in privileged EXEC mode, follow these steps to monitor SSM.
Configuring Embedded Event Manager (New Chapter)
This chapter describes how to use the embedded event manager (EEM) to monitor and manage the Catalyst 3750-E or 3560-E switch and how to configure it. (For the Catalyst 3750-E switch, the term switch refers to a standalone switch or a switch stack unless otherwise noted.)
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 0-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 0-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:
–
–
–
–
•
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.
Unsupported Embedded Event Manager Commands
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 References
These are the updates to the Command Reference for the Catalyst 3750-E and Catalyst 3560-E switches:
•
These are the correct usage guidelines for the set command:
Environment variables are case sensitive and must be entered as documented.
Environment variables that have values are stored in flash memory outside of the flash file system.
Under normal circumstances, it is not necessary to alter the setting of the environment variables.
The MANUAL_BOOT environment variable can also be set by using the boot manual global configuration command.
The BOOT environment variable can also be set by using the boot system filesystem:/file-url global configuration command.
The ENABLE_BREAK environment variable can also be set by using the boot enable-break global configuration command.
The HELPER environment variable can also be set by using the boot helper filesystem:/file-url global configuration command.
The CONFIG_FILE environment variable can also be set by using the boot config-file flash:/file-url global configuration command.
The HELPER_CONFIG_FILE environment variable can also be set by using the boot helper-config-file filesystem:/file-url global configuration command.
The HELPER_CONFIG_FILE environment variable can also be set by using the boot helper-config-file filesystem:/file-url global configuration command.
The SWITCH_NUMBER environment variable can also be set by using the switch current-stack-member-number renumber new-stack-member-number global configuration command.
The SWITCH_PRIORITY environment variable can also be set by using the switch stack-member-number priority priority-number global configuration command.
The bootloader prompt string (PS1) can be up to 120 printable characters except the equal sign (=).
These are the correct guidelines for the unset command:
Under normal circumstances, it is not necessary to alter the setting of the environment variables.
The MANUAL_BOOT environment variable can also be reset by using the no boot manual global configuration command.
The BOOT environment variable can also be reset by using the no boot system global configuration command.
The ENABLE_BREAK environment variable can also be reset by using the no boot enable-break global configuration command.
The HELPER environment variable can also be reset by using the no boot helper global configuration command.
The CONFIG_FILE environment variable can also be reset by using the no boot config-file global configuration command.
The HELPER_CONFIG_FILE environment variable can also be reset by using the no boot helper-config-file global configuration command.
Updates to the System Message Guides
These are the updates to System Message Guide for the Catalyst 3750-E and Catalyst 3560-E switches:
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 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 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 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.
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
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the URL referenced in the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section.
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.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0705R)
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.
© 2007-2009 Cisco Systems, Inc. All rights reserved.
Guest
