Guest

Cisco IOS Software Releases 12.2 SE

Release Notes for the Catalyst 3750 Metro Switch, Cisco IOS Release 12.2(55)SE and Later

  • Viewing Options

  • PDF (503.3 KB)
  • Feedback
Release Notes for the Catalyst 3750 Metro Switch, Cisco IOS Release 12.2(55)SE and Later

Table Of Contents

Release Notes for the Catalyst 3750 Metro Switch, Cisco IOS Release 12.2(55)SE and Later

Contents

Hardware Supported

Upgrading the Switch Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Archiving Software Images

Upgrading a Switch by Using the CLI

Recovering from a Software Failure

Installation Notes

New Software Features

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Bidirectional Forwarding Detection

Configuration

Connectivity Fault Management (CFM)

EtherChannel

Fallback Bridging

Hot Standby Routing Protocol (HSRP)

IP

IP Service Level Agreements (SLAs)

IP Telephony

logging event-spanning-tree Command

MAC Addressing

Multiprotocol Label Switching (MPLS) and Ethernet over MPLS (EoMPLS)

Multicasting

Quality of Service (QoS)

Resilient Ethernet Protocol (REP)

Routing

SPAN and Remote SPAN (RSPAN)

Trunking

Tunneling

VLAN

Important Notes

Open Caveats

Resolved Caveats

Caveats Resolved in Cisco IOS Release 12.2(55)SE8

Caveats Resolved in Cisco IOS Release 12.2(55)SE7

Caveats Resolved in Cisco IOS Release 12.2(55)SE6

Caveats Resolved in Cisco IOS Release 12.2(55)SE5

Caveats Resolved in Cisco IOS Release 12.2(55)SE4

Caveats Resolved in Cisco IOS Release 12.2(55)SE3

Caveats Resolved in Cisco IOS Release 12.2(55)SE1

Caveats Resolved in Cisco IOS Release 12.2(55)SE

Documentation Updates

Updates to the Software Configuration Guide and Command Reference

Updates to the System Message Guide

Added System Messages

Modified System Messages

Deleted System Messages

Update to the Hardware Installation Guide

Installation Update

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for the Catalyst 3750 Metro Switch, Cisco IOS Release 12.2(55)SE and Later


Revised June 28, 2013

Cisco IOS Release 12.2(55)SE and higher runs on the Catalyst 3750 Metro switch.

These release notes include important information about Cisco IOS Release 12.2(55)SE and any limitations, restrictions, and caveats that apply to the releases.

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.

If your switch is on, use the show version privileged EXEC command. See the "Finding the Software Version and Feature Set" section.

If you are upgrading to a new release, see the software upgrade filename for the software version. See the "Deciding Which Files to Use" section.

For the complete list of switch documentation, see the "Related Documentation" section.

You can download the switch software from this site:
http://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches

Contents

Hardware Supported

Upgrading the Switch Software

Installation Notes

New Software Features

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Important Notes

Open Caveats

Resolved Caveats

Documentation Updates

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Hardware Supported

Table 1 Supported Hardware 

Switch
Description
Supported by Minimum Cisco IOS Release

Catalyst 3750 Metro 24-AC switch

24 10/100 Ethernet ports, 2 1000X standard SFP1 module slots, 2 1000X ES2 SFP slots, and field-replaceable AC power supply

Cisco IOS Release 12.1(14)AX

Catalyst 3750 Metro 24-DC switch

24 10/100 Ethernet ports, 2 1000X standard SFP module slots, 2 1000X ES SFP slots, and field-replaceable DC power supply

Cisco IOS Release 12.1(14)AX

SFP modules

1000BASE-T, 1000BASE-SX, and 1000BASE-LX

Cisco IOS Release 12.1(14)AX

1000BASE-ZX and CWDM3

Cisco IOS Release 12.1(14)AX1

100BASE-FX MMF4

Cisco IOS Release 12.2(25)EY

1000BASE-BX

Cisco IOS Release 12.2(25)EY2

DOM5 support for GLC-BX, CWDM, and DWDM SFPs

Cisco IOS Release 12.2(44)SE

1000BASE-LX/LH MMF and SMF

1000BASE-SX MMF

DOM support for GLC-ZX-SM SFP, 1000BASE-LX/LH, and 1000BASE-SX

1000 FX GLC-EX-SMG SFP

Cisco IOS Release 12.2(46)SE

Additional DWDM SFP qualifications

Cisco IOS Release 12.2(50)SE

For a complete list of supported SFPs and part numbers, see the Catalyst 3750 Metro data sheet:
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps5532/product_data_sheet0900aecd806e27b9.html

1 SFP = small form-factor pluggable

2 ES = enhanced services

3 CWDM = coarse wavelength-division multiplexer

4 MMF = multimode fiber

5 DOM = digital optical monitoring


Upgrading the Switch Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Archiving Software Images

Upgrading a Switch by Using the CLI

Recovering from a Software Failure


Note 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. 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.

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. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.

Table 2 lists the software filename for this software release.

Table 2 Cisco IOS Software Image Files for Catalyst 3750 Metro Switches 

Filename

Description

c3750me-i5k91-tar.122-55.SE.tar

Cisco IOS cryptographic image tar file.
This image has the Kerberos, SSH1 , SSL2 , Layer 2+, and Layer 3 features.

1 SSH = Secure Shell

2 SSL = Secure Socket Layer


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 to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.

Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps6969/ps1835/prod_bulletin0900aecd80281c0e.html

You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.


Note Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.


You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2:
http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_t1.html

Upgrading a Switch by Using the CLI

This procedure is for copying the 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.

Download the software from Cisco.com to your management station by following these steps:


Step 1 Use Table 2 to identify the file that you want to download.

Step 2 Download the software image file:

a. If you are a registered customer, go to this URL and log in.

http://www.cisco.com/cisco/web/download/index.html

b. Navigate to Switches > Service Provider Switches - Ethernet Access.

c. Navigate to your switch model.

d. Click IOS Software, then select the latest IOS release.

Download the image you identified in Step 1.

Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.

For more information, see Appendix B in the software configuration guide for this release.

Step 4 Log in to the switch through the console port or a Telnet session.

Step 5 Check your VLAN 1 configuration by using the show interfaces vlan 1 privileged EXEC command, and verify that VLAN 1 is part of the same network as the TFTP server. (Check the Internet address is line near the top of the display.)

Step 6 Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by using this privileged EXEC command:

archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tar
 
   

The /overwrite option overwrites the software image in flash memory with the downloaded one.

The /reload option reloads the system after downloading the image unless the configuration has been changed and not been 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/image-name.tar
 
   

You can also download the image file from the TFTP server to the switch and keep the current image by using the /leave-old-sw option instead of the /overwrite option.

Recovering from a Software Failure

Switch software can be corrupted during an upgrade, by downloading the wrong file to the switch, and by deleting the image file. In all of these cases, the switch does not pass the power-on self-test (POST), and there is no connectivity. You can use the Xmodem protocol to recover from these failures.

For detailed 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:

Using the Express Setup program as described in the Catalyst 3750 Metro Switch Getting Started Guide.

Using the CLI-based setup program as described in the Catalyst 3750 Metro Switch Hardware Installation Guide.

Using the DHCP-based autoconfiguration as described in the Catalyst 3750 Metro Switch Software Configuration Guide.

Manually assigning an IP addresses described in the Catalyst 3750 Metro Switch Software Configuration Guide.

New Software Features

Support for the BFD Protocol on SVIs.

Support for configuration of an alternate MTU value to allow specific interfaces a different MTU than the global system MTU or jumbo MTU.

Support for CDP and LLDP enhancements for exchanging location information with video end points for dynamic location-based content distribution from servers.

AAA guarantee-first support for enabling or disabling system accounting as the first record.

An option to suppress verbose 802.1x, authentication manager, and MAC authentication bypass syslog messages.

Support for QoS class-default policy placement.

Support for increasing the NVRAM buffer size for saving large configuration files.

ARP tracking probe enhancement to specify a source IP address for a VLAN.l

Network Edge Access Topology (NEAT) controls the supplicant port during the supplicant authentication period. When you connect a supplicant switch to the authenticator switch, the authenticator port could be error-disabled when receiving Spanning Tree Protocol (STP) bridge protocol data unit (BPDU) packets and the supplicant switch is not authenticated. The NEAT feature is now enhanced to block the supplicant port during authentication, to ensure authentication completes.

Use the dot1x supplicant controlled transient global configuration command to control access to the supplicant port during authentication. Use the no form of this command to provide access to the supplicant port during the authentication period

Minimum Cisco IOS Release for Major Features


Note Features not included in the table are available in all releases. You can see a list of features from the first release:
http://www.cisco.com/en/US/products/hw/switches/ps5532/products_configuration_guide_chapter09186a00801ee872.html


Table 3 Catalyst 3750 Metro Switch Features and the Minimum Cisco IOS Release Required 

Feature
Minimum Cisco IOS Release Required

Configuration of an alternate MTU value for specific interfaces

12.2(55)SE

BFD Protocol on SVIs

12.2(55)SE

Support for the IEEE 802.1ad standard.

12.2(54)SE

CFM support on customer VLANs (C-VLANs).

12.2(54)SE

IEEE CFM MIB support.

12.2(54)SE

Support for Layer 2 transport over MPLS interworking for Ethernet and VLAN interworking.

12.2(52)SE

IPv6 QoS trust capability.

12.2(52)SE

EEM 3.2 support.

12.2(52)SE

IP source guard on static hosts.

12.2(52)SE

802.1x User Distribution for deployments with multiple VLANs.

12.2(52)SE

Network Edge Access Topology (NEAT) for changing the port host mode.

12.2(52)SE

SNMPv3 for 168-bit Triple Data Encryption Standard (3DES) and the 128-bit, 192-bit, and 256-bit Advanced Encryption Standard (AES) encryption algorithms.

12.2(52)SE

Support for including a hostname in the option 12 field of DHCPDISCOVER packets.

12.2(52)SE

DHCP Snooping enhancement to support the circuit-id sub-option.

12.2(52)SE

Connectivity fault management (CFM) Draft 8.1 compliance.

12.2(52)SE

TWAMP standard for measuring round-trip network performance between any two devices that support the protocol.

12.2(52)SE

IPv6 eBGP, IPv6 SNMP, Syslog, and HTTP as well as IPv6 MLD snooping.

12.2(52)SE

QoS marking of CPU-generated traffic and queue CPU-generated traffic on the egress network ports.

12.2(52)SE

IPv6 unicast routing, neighbor discovery, default router preference, DHCP server and relay, IPv6 eBGP, IPv6 SNMP, Syslog, and HTTP as well as IPv6 MLD snooping. and IPv6 QoS trust.

12.2(52)SE

Multicast VLAN registration (MVR) enhancements.

12.2(52)SE

Shorter REP hello.

12.2(52)SE

BFD

12.2(50)SE

REP support on ports connected to nonREP ports

12.2(50)SE

NEAT with 802.1X switch supplicant, host authorization with CISP, and auto enablement

12.2(50)SE

CPU utilization threshold trap

12.2(50)SE

EEM 2.4

12.2(50)SE

RADIUS server load balancing

12.2(50)SE

REP timer and counter enhancements

12.2(46)SE

MPLS traffic engineering and fast reroute

12.2(46)SE

HSRPv2

12.2(46)SE

EOT and IP SLAs EOT static route

12.2(46)SE

DHCP server port-based address allocation

12.2(46)SE

DHCP-based autoconfiguration and image update

12.2(44)SE

Configurable small-frame arrival threshold

12.2(44)SE

Source Specific Multicast (SSM) mapping for multicast applications

12.2(44)SE

Support for the *, ip-address, interface interface-id, and vlan vlan-id keywords with the clear ip dhcp snooping command

12.2(44)SE

Flex Link Multicast Fast Convergence

12.2(44)SE

IEEE 802.1x readiness check

12.2(44)SE

Configurable control-plane queue assignment

12.2(44)SE

Prioritization of management traffic

12.2(44)SE

/31 bit mask support for multicast traffic

12.2(44)SE

Configuration replacement and rollback

12.2(40)SE

Embedded event manager (EEM)

12.2(40)SE

Internet Group Management Protocol (IGMP) Helper

12.2(40)SE

IP Service Level Agreements (IP SLAs) support

12.2(40)SE

IP SLAs EOT

12.2(40)SE

IP SLAs for Metro Ethernet using IEEE 802.1ag Ethernet operation, administration, and maintenance (OAM)

12.2(40)SE

Multiprotocol label-switching (MPLS) OAM

12.2(40)SE

Multicast virtual routing and forwarding (VRF) lite

12.2(40)SE

Support for the SSM PIM protocol

12.2(40)SE

Support for the Link Layer Discovery Protocol Media Extensions (LLDP-MED)

12.2(40)SE

Support for Resilient Ethernet Protocol (REP)

12.2(40)SE

Ethernet OAM MPLS

12.2(37)SE

ELMI-CE

12.2(37)SE

LLDP and LLDP-MED

12.2(37)SE

Port security on a PVLAN host

12.2(37)SE

VLAN Flex Links load balancing

12.2(37)SE

MVR over trunk port (MVRoT) support

12.2(35)SE1

Hierarchical QoS on ES EtherChannels

12.2(35)SE1

Enhanced object tracking for HSRP

12.2(35)SE1

Ethernet OAM IEEE 802.3ah protocol

12.2(35)SE1

Ethernet OAM CFM (IEEE 802.1ag) and E-LMI

12.2(25)SEG

NSF awareness

12.2(25)SEG

MST based on the IEEE 802.1s standard

12.2(25)SEG

SCP

12.2(25)SEG

Per VLAN MAC learning disable

12.2(25)SEG

DHCP Option-82 configurable remote Id and circuit ID

12.2(25)SEE

H-VPLS

12.2(25)SED

IEEE 802.1x restricted VLANs

12.2(25)SED

IEEE 802.1x accounting and MIBs (IEEE8021-PAE-MIB and CISCO-PAE-MIB)

12.2(25)EY

DHCP snooping with the option-82 information option

12.2(25)EY

DHCP snooping binding database configuration

12.2(25)EY

Dynamic ARP inspection

12.2(25)EY

EtherChannel guard

12.2(25)EY

Flex Links

12.2(25)EY

IGMPv3 snooping

12.2(25)EY

IGMP throttling

12.2(25)EY

IP source guard

12.2(25)EY

MultipleVPN Routing/Forwarding (Multi-VRF) CE

12.2(25)EY

Private VLAN

12.2(25)EY

SFP diagnostic management interface

12.2(25)EY

SSHv2 server application (cryptographic images only)

12.2(25)EY

SSL Version 3.0 for secure HTTP communication (cryptographic images only)

12.2(25)EY

Smartports macros

12.2(25)EY

Auto-QoS

12.2(25)EY

VLAN-based QoS and dual-level hierarchical policy maps on SVIs

12.2(25)EY

Matching the CoS of the inner tag for IEEE 802.1Q tunneling traffic.

12.2(25)EY

Applying hierarchical service policies in the inbound direction on an ES port.

12.2(25)EY

Storm control enhancements

12.2(25)EY

SFP diagnostic management interface

12.2(25)EY

Unicast MAC address filtering

12.2(25)EY

QoS egress priority queue

12.1(14)AX2

QoS DSCP transparency

12.1(14)AX2

Point-to-point Layer 2 protocol tunneling

12.1(14)AX1

Flex Link Preemptive Switchover

12.2(25)SEE

OSPF nonbroadcast and point-to-multipoint networks

12.2(25)SEE


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.

Bidirectional Forwarding Detection

Configuration

Connectivity Fault Management (CFM)

EtherChannel

Fallback Bridging

Hot Standby Routing Protocol (HSRP)

IP

IP Service Level Agreements (SLAs)

IP Telephony

MAC Addressing

Multiprotocol Label Switching (MPLS) and Ethernet over MPLS (EoMPLS)

Multicasting

logging event-spanning-tree Command

Quality of Service (QoS)

Resilient Ethernet Protocol (REP)

Routing

SPAN and Remote SPAN (RSPAN)

Trunking

Tunneling

VLAN

Bidirectional Forwarding Detection

If you create a BFD session between two switches and then create an ACL that includes the permit ip any any log-input access-list configuration command, when you attach the ACL to one of the connecting interfaces, the BFD session goes down. If you remove the ACL from the interface, BFD comes back up.

The workaround is to not use a permit ACL entry with the log option on interfaces participating in BFD. (CSCtf31731)

Configuration

A static IP address might be removed when the previously acquired DHCP IP address lease expires.

This problem occurs under these conditions:

When the switch is booted without a configuration (no config.text file in flash memory).

When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).

When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.

The workaround is to reconfigure the static IP address. (CSCea71176)

On a switch running Cisco IOS Release 12.1(14)AX, when the show interface privileged EXEC is entered on a port that is running IEEE 802.1Q, inconsistent statistics from ports running IEEE 802.1Q might be reported.

The workaround is to upgrade to Cisco IOS Release 12.2(25)EY or later. (CSCec35100)

When you change a port from a nonrouted port to a routed port or the reverse, the applied auto-QoS setting is not changed or updated when you verify it by using the show running interface or show mls qos interface user EXEC commands.

These are the workarounds:

1. Disable auto-QoS on the interface.

2. Change the routed port to a nonrouted port or the reverse.

3. Re-enable auto-QoS on the interface. (CSCec44169)

The DHCP snooping binding database is not written to flash or a remote file in any of these situations:

When the Network Time Protocol (NTP) is configured, but the NTP clock is not synchronized. You can check the clock status by entering the show NTP status privileged EXEC command and verifying that the network connection to the NTP server and peer work correctly.

The DHCP snooping database file is manually removed from the file system. After enabling the DHCP snooping database by configuring a database URL, a database file is created. If the file is removed manually from the file system, the DHCP snooping database does not create another database file. You need to disable the DHCP snooping database and enable it again to create the database file.

The URL for the configured DHCP snooping database was replaced because the original URL is not accessible. The new URL might not take effect after the timeout of the old URL.

No workaround is necessary; these are the designed behaviors. (CSCed50819)

When dynamic ARP inspection is enabled on a switch or switch stack, ARP and RARP packets greater than 2016 bytes are dropped by the switch. This is a hardware limitation.

However, when dynamic ARP inspection is not enabled and jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)

When connected to some third-party devices that send early preambles, a switch port operating at 100 Mbps full duplex or 100 Mbps half duplex might bounce the line protocol up and down. The problem is observed only when the switch is receiving frames.

The workaround is to configure the port for 10 Mbps and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)

Dynamic ARP inspection log entries might be lost after a switch failure. Any log entries that are still in the log buffer (have not been output as a system message) on a switch that fails will be lost.

When you enter the show ip arp inspection log privileged EXEC command, the log entries from all switches in the stack are moved to the switch on which the command was entered.

There is no workaround. (CSCed95822)

When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered for that interface, MAC addresses are incorrectly forwarded when they should be blocked.

The workaround is to enter the no switchport block unicast interface configuration command for that specific interface. (CSCee93822)

The Catalyst 3750 Metro switch does not learn its own MAC address on Layer 2 interfaces. For example: Ports 1/0/1 and 1/0/2 belong to VLAN x, port 1/0/3 is a Layer 3 port with an IP address that belongs to the subnet of VLAN x, and ports 1/0/2 and 1/0/3 are connected. In this case, a host connected to port 1/0/1 cannot ping port 1/0/3. The switch does not update the CAM table and does not use the MAC address of port 1/0/3 in the CAM table for port 1/0/2.

The workaround is to statically configure the MAC address of port 1/0/3 in the CAM table of the switch bound to port 1/0/2 by using the mac address-table static mac-addr vlan vlan-id interface fastethernet1/0/2 global configuration command. (CSCee87864)

A traceback error occurs if a crypto key is generated after an SSL client session.

There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)

When enhanced services (ES) interfaces in an EtherChannel are carrying Multiprotocol Label Switching (MPLS) traffic and more routes are configured than are supported in the SDM template, messages similar to the following might appear when the interface is shut down and brought back up:

2d20h: %PLATFORM_UCAST-3-LB: PI<->PD handles out of sync for Adj 222.1.1.1 LB -Traceback= 252620 A919CC A847E0 A85BE0 A927FC AA2D28 A965E0 A89C08 A78744 B08F48 ADF504 ADDC4C AE3460 AD25CC B94AA0 B94F20

There is no workaround. (CSCeh13477)

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. (CSCsk65142)

Connectivity Fault Management (CFM)

On a switch running CFM, continuity check messages (CCMs) received on a MEP port that are a lower level than the configured MEP level should be discarded and an error message generated, regardless of whether or not the CCM has a valid CFM multicast destination address. On the Catalyst 3750 Metro switch, CFM C-VLAN CCMs with non-CFM multicast addresses are forwarded without CFM processing and no error messages are sent.

There is no workaround. (CSCte39713)

When the CFM start delay timer is configured to a small value, the Crosscheck-Up field in the output of the show ethernet cfm domain privileged EXEC command and the Mep-Up field in the output of the show ethernet cfm maintenance-points remote crosscheck privileged EXEC command might appear as No even if the CCM is learned in the remote database.

This is expected behavior. The workaround is to use the ethernet cfm mep crosscheck start-delay command to set the delay-start timer value larger than the continuity-check interval. (CSCtf30542)`

EtherChannel

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.(CSCsh12472)

When an EtherChannel is configured for 802.1ad and a channel member that is up is removed from the EtherChannel, the 802.1ad configuration is removed. However, if the port channel is shut down and then removed from the EtherChannel, the 802.1ad configuration is not removed.

The workaround is to enter the no shutdown interface configuration command on the port channel before removing it from the EtherChannel. (CSCtf77937)

Fallback Bridging

If a bridge group contains a VLAN that has a static MAC address configured, all non-IP traffic in the bridge group with this MAC address destination is sent to all ports in the bridge group.

The workaround is to remove the VLAN from the bridge group or to remove the static MAC address from the VLAN. (CSCdw81955)

Known unicast (secured addresses) are flooded within a bridge group under this condition: If secure addresses are learned or configured on a port and the VLAN on this port is part of a bridge group, non-IP traffic destined to the secure addresses is flooded within the bridge group.

The workaround is to disable fallback bridging. To remove an interface from a bridge group and to remove the bridge group, use the no bridge-group bridge-group interface configuration command. Another workaround is to disable port security on all ports in all VLANs participating in fallback bridging by using the no switchport port-security interface configuration command. (CSCdz80499)

Hot Standby Routing Protocol (HSRP)

When the active switch fails in a switch cluster that uses HSRP redundancy, the new active switch might not contain a full cluster member list.

The workaround is to ensure that the ports on the standby cluster members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking state, see the "Configuring STP" chapter in the software configuration guide. (CSCec76893)

HSRP does not function on multiprotocol label switching (MPLS) interfaces.

There is no workaround. Do not configure HSRP on MPLS interfaces. (CSCeg76540)

IP

The switch does not create an adjacency table entry when the Address Resolution Protocol (ARP) timeout value is 15 seconds and the ARP request times out.

The workaround is to set an ARP timeout value higher than 120 seconds. (CSCea21674)

When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console.

The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)

IP Service Level Agreements (SLAs)

When the IP SLAs configured reaction type (configured by entering the ip sla reaction-configuration global configuration command) is round-trip time (RTT), an RTT event causes duplicate SNMP traps.

There is no workaround.

IP Telephony

Some access point (AP)-350 devices are incorrectly discovered as IEEE 802.3af Class 1 devices. These APs should be discovered as Cisco pre-standard devices. The show power inline user EXEC command shows the AP-350 as an IEEE Class 1 device.

The workaround is to power the AP by using an AC wall adaptor. (CSCin69533)

After changing the access VLAN on a port that has IEEE 802.1x enabled, the IP phone address is removed. Because learning is restricted on IEEE 802.1x capable ports, it takes approximately 30 seconds before the address is relearned.

There is no workaround. (CSCea85312)

logging event-spanning-tree Command

When the logging event-spanning-tree interface configuration command is configured and logging to the console is enabled, a topology change might generate a large number of logging messages, causing high CPU utilization. CPU utilization can increase with the number of spanning-tree instances and the number of interfaces configured with the logging event-spanning-tree interface configuration command. This condition adversely affects how the switch operates and could cause problems such as STP convergence delay.

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:

Disable logging to the console.

Rate-limit logging messages to the console. (CSCsg91027)

Remove the logging event spanning-tree interface configuration command from the interfaces.

The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.

The workaround is to configure aggressive UDLD. (CSCsh70244).

MAC Addressing

When a MAC address is configured for filtering on the internal VLAN of a routed port, incoming packets from the MAC address to the routed port are not dropped. (CSCeb67937)

Multiprotocol Label Switching (MPLS) and Ethernet over MPLS (EoMPLS)

Port-based Ethernet over Multiprotocol Label Switching (EoMPLS) sessions do not function if the incoming port is configured as an Inter-Switch Link (ISL) trunk.

The workaround is to configure the incoming ports as an IEEE 802.1Q trunk or as an access port. (CSCeb44014)

The display for the show mpls ldp neighbor ipaddr-of-neighbor detail user EXEC command always shows the targeted hello holdtime value as infinite.

The workaround is to use the show mpls ldp parameter user EXEC command to see the configured value. (CSCeb76775)

When MPLS is enabled, traceroute is not supported.

There is no workaround. (CSCec13655)

When you mark SNMP packets to an IP DSCP value setting, and you then mark the control plane protocol packets to a different CPU traffic quality of service (QoS) value setting, the CPU traffic setting overrides the SNMP IP DSCP setting.

This only occurs on the enhanced services ports with Multiprotocol Label Switching (MPLS) configured. The FastEthernet and Gigabit Ethernet customer edge ports are not affected.

There is no workaround. You can specify the marking as either SNMP IP DSCP or as CPU traffic QoS, not both. (CSCsl65914)

For pseudowire redundancy, the switch does not support LDP MAC address withdrawal.

There is no workaround. (CSCsq24540)

Multicasting

The switch does not support tunnel interfaces for unicast routed traffic. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing.

Nonreverse-path forwarded (RPF) IP multicast traffic to a group that is bridged in a VLAN is leaked onto a trunk port in the VLAN even if the port is not a member of the VLAN group, but it is a member in some other VLAN group. Unnecessary traffic is sent on the trunk port and needlessly reduces the bandwidth of the port.

There is no workaround because non-RPF traffic is continuous in certain topologies. As long as the trunk port is a member on a trunk port in at least one VLAN, this problem for the non-RPF traffic occurs. (CSCdu25219)

If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more than the maximum number in the Switch Database Management (SDM) template shown with the show sdm prefer global configuration command, the traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp snooping multicast-table privileged EXEC command output shows otherwise.

The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)

IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port.

There is no workaround. (CSCdy82818)

When you use the ip access-group interface configuration command with a router access control list (ACL) to deny access to a group in a VLAN, multicast data to the group that is received in the VLAN is always flooded in the VLAN regardless of IGMP group membership in the VLAN. This provides access to directly connected clients, if any, in the VLAN.

The workaround is to not apply a router ACL configured to deny access to a VLAN interface. Apply the security through other means; for example, apply VLAN maps to the VLAN instead of using a router ACL for the group. (CSCdz86110)

(Catalyst 3750 switches) When IP Protocol-Independent Multicast (PIM) is enabled on a tunnel interface, the switch incorrectly displays the Multicast is not supported on tunnel interfaces error message. IP PIM is not supported on tunnel interfaces.

There is no workaround. (CSCeb75366)

If an IGMP report packet has two multicast group records, the switch removes or adds interfaces depending on the order of the records in the packet:

If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.

If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.

There is no workaround. (CSCec20128)

When IGMP snooping is disabled and you enter the switchport block multicast interface configuration command, IP multicast traffic is not blocked.

The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.

There is no workaround. (CSCee16865)

Incomplete multicast traffic can be seen under either of these conditions:

You disable and then re-enable IP multicast routing on an interface.

A switch mroute table temporarily runs out of resources and recovers later.

The workaround is to enter clear ip mroute privileged EXEC command on the interface. (CSCef42436)

When more multicast groups are configured than are supported by the selected Switch Database Management (SDM) template, Layer 2 multicast traffic is flooded on one or more multicast groups.

There is no workaround. (CSCef67261)

Quality of Service (QoS)

For MPLS VPN, you cannot use the enhanced-services (ES) port QoS to perform per-VRF QoS because the network processor cannot identify VRFs. You can use standard QoS on a non-ES port to perform upstream traffic rate limiting by using hierarchical QoS policers applied at the SVI. You cannot use this method for downstream traffic rate limiting because the switch does not support applying egress policers to an SVI.

Some switch queues are disabled if the buffer size or threshold level is set too low with the mls qos queue-set output global configuration command. The ratio of buffer size to threshold level should be greater than ten to avoid disabling the queue.

The workaround is to choose compatible buffer sizes and threshold levels. (CSCea76893)

When traffic with different class of service (CoS) values is sent into a IEEE 802.1Q tunnel, only the CoS 0 statistics increment in the show mls qos interface user EXEC command display.

There is no workaround. (CSCeb75230)

The bandwidth interface configuration command is not supported at the interface level, but it appears in the CLI.

There is no workaround. (CSCeb80223)

The random-detect interface configuration command is not supported at the interface level, but it appears in the CLI.

There is no workaround. (CSCeb80300)

The display for the show policy-map interface user EXEC command shows zeros for the counters associated with class-map match criteria.

There is no workaround. (CSCec08205)

The priority policy-map class configuration command cannot be configured for the default traffic class in a policy map.

The workaround is to configure explicit matches for traffic that requires priority treatment. (CSCec38901)

Modifying a QoS class within a very large service policy that is attached to an enhanced-services (ES) port can cause high CPU utilization and an unresponsive CLI for an excessive period of time.

The workaround is to detach the service policy from the port while making the modifications and then to re-attach the service policy. (CSCec75945)

When packets are queued for egress on an enhanced-services (ES) port due to the application of a QoS service policy, they consume packet buffer memory on the switch. If many queues are simultaneously congested and are unable to drain, packet loss can occur in either direction (ingress or egress) due to the lack of buffer memory.

If this becomes a problem, you can change switch behavior by using the queue-limit policy-map class configuration command at the class level to set shorter queue depths. Each shaper has an associated buffer queue with a default depth of 128 packets.

For example:

Switch(config)# policy-map cos2-policy
Switch(config-pmap)# class cos2
Switch(config-pmap-c)# bandwidth 50000
Switch(config-pmap-c)# queue-limit 32
 
   

The point at which buffer memory is exhausted depends on the number of queues, the sizes of the queued packets, and whether or not the traffic pattern being sent to the switch allows the queues to drain at all.

Upgrading your switch to Cisco IOS Release 12.2(25)EY or later greatly reduces the possibility of this situation happening, although it can still occur with some configurations and traffic patterns. (CSCed83886)

When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses shaped round robin (SRR) as the queuing mechanism. The auto-QoS feature is designed on each platform based on the feature set and hardware limitations, and the queuing mechanism supported on each platform might be different.

There is no workaround. (CSCee22591)

You cannot enable MPLS fast reroute (FRR) link protection notifications by using SNMP (via the cmplsFrrNotifsEnabled object in the CISCO-MPLS-FRR-MIB).

The workaround is to use the CLI to enable the trap by entering the snmp-server enable traps mpls fast-reroute [protected] global configuration command. (CSCsq07065)

If you configure a large number of input interface VLANs in a class map, a traceback message similar to this might appear:

01:01:32: %BIT-4-OUTOFRANGE: bit 1321 is not in the expected range of 0 to 1024
 
   

There is no impact to switch functionality.

There is no workaround. (CSCtg32101)

Resilient Ethernet Protocol (REP)

The Resilient Ethernet Protocol (REP) convergence times on a ring might be longer when a cable is pulled from an enhanced services port that has a large number of VLANs.

There is no workaround. (CSCsk00716)

Although you can configure a REP segment without configuring REP edge ports, we recommend that you configure REP edge ports whenever possible because edge ports enable these functions:

selecting the preferred alternate port

configuring VLAN load balancing

configuring topology change notifications (TCNs) toward STP, other REP segments, or an interface

initiating the topology collection process

preemption mechanisms

You cannot enable these functions on REP segments without edge ports.

On a switch running both Resilient Ethernet Protocol (REP) and Bidirectional Forwarding Detection (BFD), when the REP link status layer (LSL) age-out value is less than 1 second, the REP link flaps if the BFD interface is shut down and then brought back up.

The workaround is to use the rep lsl-age-out timer interface configuration command to configure the REP LSL age timer for more than 1000 milliseconds (1 second). (CSCsz40613)

If you configure two or more connected REP segments to send segment topology change notices (STCNs) by entering the rep stcn segment segment-id interface configuration command on REP interfaces, when segments inject messages simultaneously, an STCN loop occurs, and CPU usage can increase to 99 percent for 1 to 2 minutes before recovering.

The workaround is to avoid configuring multiple STCNs in connected segments. This is a misconfiguration. (CSCth18662)

Routing

The switch does not support tunnel interfaces for unicast routed traffic. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing.

A route map that contains an ACL with a DSCP clause cannot be applied to a Layer 3 interface. The switch rejects this configuration and issues an error message that shows that the route map is unsupported.

There is no workaround. (CSCea52915)

A spanning-tree loop might occur if all of these conditions are true:

Port security is enabled with the violation mode set to protected.

The maximum number of secure addresses is less than the number of switches connected to the port.

There is a physical loop in the network through a switch whose MAC address has not been secured, and its BPDUs cause a secure violation.

The workaround is to change any one of the listed conditions. (CSCed53633)

The MAC addresses of routed interfaces on a platform might change following a reload.

There is no workaround. (CSCsj41522)

SPAN and Remote SPAN (RSPAN)

An egress SPAN copy of routed unicast traffic might show an incorrect destination MAC address on both local and remote SPAN sessions. This limitation does not apply to bridged packets. The workaround for local SPAN is to use the replicate option.

There is no workaround for a remote SPAN session. This is a hardware limitation. (CSCdy72835)

Egress SPAN routed packets (both unicast and multicast) show the incorrect source MAC address. For remote SPAN packets, the source MAC address should be the MAC address of the egress VLAN, but instead the packet shows the MAC address of the remote SPAN (RSPAN) VLAN. For local SPAN packets with native encapsulation on the destination port, the packet shows the MAC address of VLAN 1. This problem does not appear with local SPAN when the encapsulation replicate option is used and does not apply to bridged packets.

The workaround is to use the encapsulate replicate keywords in the monitor session global configuration command. This is a hardware limitation. (CSCdy81521)

During periods of very high traffic and when two RSPAN source sessions are configured, the VLAN ID of packets in one RSPAN session might overwrite the VLAN ID of the other RSPAN session. Packets intended for one RSPAN VLAN are incorrectly sent to the other RSPAN VLAN. This problem does not affect RSPAN destination sessions.

The workaround is to configure only one RSPAN source session. (CSCea72326)

The egress-SPAN data rate might degrade when fallback bridging or multicast routing is enabled. The amount of degradation depends on the processor loading. Typically, the switch can process egress-SPAN at up to 40,000 packets per second (64-byte packets). When the total traffic being monitored is below this limit, there is no degradation. However, if the traffic exceeds the limit, only a portion of the source stream is monitored. When this occurs, this console message appears: Decreased egress SPAN rate.

In all cases, normal traffic is not affected; the degradation limits only how much of the original source stream can be monitored. If fallback bridging and multicast routing are disabled, egress-SPAN monitoring is not degraded.

There is no workaround. If possible, disable fallback bridging and multicast routing. If possible, use ingress-SPAN to observe the same traffic. (CSCeb01216)

Some IGMP report and query packets with IP options might not be ingress-span monitored. Packets that are susceptible to this problem are IGMP packets with 4 bytes of IP options (IP header length of 24). Examples of such packets are IGMP reports and queries having the router alert IP option. Ingress-span monitoring of such packets is not accurate and can vary with traffic rate. Typically, very few or none of these packets are monitored.

There is no workaround. (CSCeb23352)

Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local SPAN session.

The workaround is to use the monitor session session_number destination {interface interface-id encapsulation replicate} global configuration command for a local SPAN session. (CSCed24036)

When system jumbo MTU size is configured on a switch and the egress ports can support jumbo frames, the egress SPAN jumbo frames are not forwarded to the SPAN destination ports. In a mixed hardware stack of Catalyst 3750-E and 3750 switches, this problems occurs if the egress port is a switch port on a Catalyst 3750 switch.

There is no workaround. (CSCsj21718)

Trunking

The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link [ISL]) as frames with FCS errors, increments the error counters, and causes the port LED to blink amber. This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame to an IEEE 802.1Q trunk interface.

There is no workaround. (CSCdz33708)

IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y. This is because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y.

There is no workaround. (CSCdz42909)

For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics.

There is no workaround. (CSCec35100).

When a trunk interface is converted to an IEEE 802.1Q tunnel, a traceback error message similar to the following might appear:

3d20h: %PLATFORM_UCAST-3-LB: PI<->PD handles out of sync for Adj 222.1.1.1 LB -Traceback= 252620 A9204C A84E60 A86260 A92E7C AA36A0 AA3520 A96C60 A8A288 A78DC4 B095C8

There is no workaround. This does not affect switch functionality. (CSCeh20081)

Tunneling

VLAN mappings can be configured on a per-interface basis. A different set of mappings can be configured on each enhanced-services (ES) interface. The per-interface VLAN mappings remain in effect when the ES ports are bundled in an EtherChannel. For example, if you map Gigabit Ethernet 1/1/1 to VLAN 20 through VLAN 50 and Gigabit Ethernet 1/1/2 to VLAN 20 through VLAN 70, traffic on VLAN 20 leaving the switch through the ES port bundle should be load-balanced across the individual ES interfaces. However, some of that traffic is incorrectly translated to VLAN 50, and some is incorrectly translated to VLAN 70.

The workaround is to configure identical VLAN mappings on both ES ports if they will be bundled into an EtherChannel. (CSCec49520)

Although you can enter the switchport vlan mapping interface configuration command on any ES port to configure VLAN mapping, VLAN mapping is only valid on trunk ports. The configuration is allowed on an access port, but does not take effect.

The workaround is to configure the ES port as a trunk or yo use the switchport access vlan vlan_id interface configuration command to define the access VLAN for the access port. (Ctb67562)

VLAN

If the number of VLANs times the number of trunk ports exceeds 13,000, the switch can stop.

The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)

A CPUHOG message sometimes appears when you configure a private VLAN. Enable port security on one or more of the ports affected by the private VLAN configuration.

There is no workaround. (CSCed71422)

When you apply a per-VLAN QoS per-port policer policy-map to a VLAN SVI, the second-level (child) policy-map in use cannot be re-used by another policy-map.

The workaround is to define another policy-map name for the second-level policy-map with the same configuration to be used for another policy-map. (CSCef47377)

Important Notes

Cisco IOS Release 12.2(50)SE introduced the virtual circuit (VC) auto-sense signaling feature for hierarchical virtual private LAN service (H-VPLS), the xconnect of the SVI, to interoperate with the ASR 9000 Series routers. The default signaling for H-VPLS is now VC type 5. The local Catalyst 3750 Metro PE switch boots up signaling for VC type 5. If the remote provider-edge switch also supports type 5, H-VPLS comes up with type 5. If the remote switch supports only VC type 4, the local PE switch resets and renegotiates for VC type 4, and the H-VPLS comes up with type 4. H-VPLS comes up whether the remote PE supports VC type 4 or VC type 5. Before Cisco IOS Release 12.2(50)SE, H-VPLS would not come up unless the remote provider edge device also supported VC type 4.

By definition, the local PE H-VPLS VLAN should not be relevant for the VPLS network. Because the local PE SVI with the xconnect and the remote PE SVI with the xconnect do not need to be on the same VLAN, it does not matter if the VLAN is carried across the transport network or not. However, problems could occur if a service provider deployed the Catalyst 3750M switch using the H-VPLS VLAN as the customer VLAN when H-VPLS came up with VC type 5 because the customer VLAN tag would not be consistent across the transport. The new behavior is now consistent with the Cisco default.

Cisco IOS Release 12.2(40)SE and later:

If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)SE (or later), when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message:

AutoQoS Error: ciscophone input service policy was not properly applied
policy map AutoQoS-Police-CiscoPhone not configured
 
   

If this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.

The behavior of the no logging on global configuration command changed in Cisco IOS Release 12.2(25)EY and later. In software releases earlier than Cisco IOS Release 12.2(25)EY, both of these command pairs disabled logging to the console:

the no logging on and then the no logging console global configuration commands

the logging on and then the no logging console global configuration commands

In Cisco IOS Release 12.2(18)SE and later, you can only use the logging on and then the no logging console global configuration commands to disable logging to the console. (CSCec71490)

Beginning with Cisco IOS Release 12.2(25)EY, ISL encapsulation is supported only on standard ports and not on an enhanced-services (ES) ports. The ES ports support only IEEE 802.1Q encapsulation and the switchport trunk encapsulation interface configuration command is no longer available on these ports. When you are upgrading a switch from Cisco IOS Release12.1(14)AX to Cisco IOS Release 12.2(25)EY or later, during the initial configuration process, the switchport trunk encapsulation option is rejected on ES ports, and an error message appears. You can ignore this error message. If you save the new configuration by using the copy running-config startup-config privileged EXEC command and later re-install the Cisco IOS Release 12.1(14)AX image, the trunk encapsulation method originally configured on ES ports is lost, and the ES ports use the default encapsulation method, which is to negotiate.

In Cisco IOS Release 12.1(14)AX and earlier, port-based EoMPLS sessions could only be configured on switch ports. In Cisco IOS Release 12.2(25)EY and later, port-based EoMPLS sessions can only be configured on routed ports.


Note This change is handled automatically during an upgrade to Cisco IOS 12.2(25)EY or later, but if a configuration is written to NVRAM and the switch is then reloaded with Cisco IOS 12.1(14)AX, the new-style configuration is lost.


Beginning with Cisco IOS Release 12.2(25)EY, you must specify the encapsulation type when using the xconnect interface configuration command.


Note This change is handled automatically during an upgrade to Cisco IOS 12.2(25)EY or later, but if a configuration is written to NVRAM and the switch is then reloaded with Cisco IOS 12.1(14)AX, the new-style configuration is lost.


Open Caveats

CSCth97324

When you are configuring 802.1ad on an EtherChannel interface, the ethernet dot1ad isolate interface configuration command is visible and available. However, the isolate keyword is not supported on the Catalyst 3750 Metro switch. If you enter the ethernet dot1ad isolate command on an EtherChannel, the EtherChannel becomes inactive, and strange spanning tree behavior can occur.

Do not enter the isolate keyword on a Catalyst 3750 Metro EtherChannel. The workaround, if you do enter the isolate keyword, is to restart the switch.

CSCti26743

When you configure an interface that is connected to a customer edge device as an 802.1ad S-UNI port, by default Layer 2 PDUs should be tunneled through the 802.1ad service provider cloud on the S-UNI port configured on the provider edge device. On a Catalyst 3750 Metro switch, LLDP, STP, and other Layer 2 control protocol traffic is correctly tunneled, but end-to-end tunneling is not working for CDP.

On an 802.1ad S-UNI port connected to a customer port, CDP is automatically disabled to prevent service-provider CDP packets from being propagated to the customer domain. The workaround is to use the command line interface to explicitly enable CDP on the 802.1ad S-UNI port to allow end-to-end tunneling to work correctly. The problem with the workaround is that the customer edge device recognizes the remote customer device as a neighbor, but will also recognize the directly connected provider edge device as a neighbor, which is not desirable when end-to-end tunneling is configured.

CSCtx34771

Cisco ME 3750 ES ports stop forwarding traffic.

Workaround:

None.

CSCty84680

Internal VLAN allocation ignores configured VLANs on reload.

On a Cisco ME 3750 series switch, VLANs are allocated for internal use starting at 1006. To use these VLANs for other purposes, first allocate them prior to configuring the services which require internal vlans (for example, VRF's, layer-3 routed ports, and so forth). After a reload of the switch, the internal VLANs are allocated first before reading the VLANs configured in the running-configuration, causing a loss of connectivity to those layer 2 VLANs.

Workaround:

1. Do not use VLANs starting at 1006 until 1020 (or higher depending on how many services you have configured).

2. Erase the configuration, recreate the layer 2 VLANs, and re-configure the layer 3 services. This functions until the switch is reloaded.

CSCty87384

Cisco ME C3750 with 12.2(55)SE3 IOS does not forward frames received from an ES port configured for xconnect.

Topology:

CE1---PE1---PE2---CE2

CE1 is not able to successfully ping CE2.

The issue is seen only with 12.2(55)SE5 images. The 12.2(44)SE2 image does not have this issue. The CLI show mpls l2 vc detail shows the send and receive counters are not incrementing but with the 12.2(44)SE2 image the CLI show mpls l2 vc detail shows the send and receive counters incrementing.

Workaround:

None.

Further Problem Description:

Issue is specific to the Cisco ME 3750 platform.

CSCua32557

Cisco ME 3750 crash on platform side with MPLS.

This crash is observed when MPLS neighbor flaps.

Workaround:

None.

Resolved Caveats

Caveats Resolved in Cisco IOS Release 12.2(55)SE8

Caveats Resolved in Cisco IOS Release 12.2(55)SE7

Caveats Resolved in Cisco IOS Release 12.2(55)SE6

Caveats Resolved in Cisco IOS Release 12.2(55)SE5

Caveats Resolved in Cisco IOS Release 12.2(55)SE4

Caveats Resolved in Cisco IOS Release 12.2(55)SE3

Caveats Resolved in Cisco IOS Release 12.2(55)SE1

Caveats Resolved in Cisco IOS Release 12.2(55)SE

Caveats Resolved in Cisco IOS Release 12.2(55)SE8

CSCtf23298

When a Terminal Access Controller Access Control System (TACACS) server is configured with a single connection, the CPU usage is high.

The workaround is to remove the single connection option.

CSCtt19737

Cisco IOS IP SLAs probes fail because the control message is blocked. The firewalls block the control message when a response packet is not returned to the originating port.

The workaround is to disable IP SLAs control messages for this probe instance.

CSCty66157

The snmp-server group command does not associate both IPv6 and IPv4 ACLs simultaneously with an SNMP group.

The workaround is to use the snmp-server user command, which associates both IPv4 and IPv6 ACLs with an SNMP user.

CSCud79753

When a switch is configured with Cisco IOS IP SLAs FTP GET operation and if the target file is unavailable, the switch experiences a memory leak and may become unresponsive if it runs out of memory.

The workaround is to configure the Cisco IOS IP SLAs FTP GET operation only after verifying the availability of the remote target file and setting the permissions for the file, as appropriate. This allows the switch to retrieve the file and not experience a memory leak.

CSCue07405

When manually running on-demand diagnostic tests on a stack member using the diagnostic start switch number test all interface configuration command, the test TestPortAsicRingLoopback fails arbitrarily.

The workaround is to run only the TestPortAsicRingLoopback test (diagnostic start switch number test 4 interface configuration command) on the stack member. Isolate the stack member and then run the diagnostic start switch number test all interface configuration command on the rest of the stack.

Caveats Resolved in Cisco IOS Release 12.2(55)SE7

CSCtg52885

The Hot Standby Router Protocol (HSRP) on dot1q sub-interfaces remains in INIT state after a physical link flap on the trunk port.

The workaround is to enter the shutdown and no shutdown command on the interface.

CSCtz96168

IPv6 packets travel randomly between two isolated ports that are in the same VLAN.

There is no workaround.

CSCub92642

If the switch is configured with Multicast Distributed Switching (MDS), memory leaks if the multicast-routing distributed command is toggled repeatedly.

There is no workaround.

CSCud17778

Memory leaks (due to SNMP traps) cause the switch to respond slowly to commands; eventually the switch fails. This is observed when more than one SNMP server host is configured, one of the host broadcasts SNMP traps, or the snmp-server enable traps snmp authentication coldstart warmstart command is configCaveats Resolved in Cisco IOS Release 12.2(55)SE7the snmp-server enable traps snmp authentication coldstart warmstart command and reload the switch.

Caveats Resolved in Cisco IOS Release 12.2(55)SE6

CSCef01541

Router processes packets destined to a network address it does not have.

CSCsd67567

show ip mroute count displays twice of routes entries under SSM setup.

CSCtc42278

%DATACORRUPTION-1-DATAINCONSISTENCY: Copy error is seen for incoming ISDN call.

CSCtd74235

Adding aggregate policers to the child policy-map crashes the switch.

CSCtg71149

When ports in an EtherChannel are linking up, the message EC-5-CANNOT_BUNDLE2 might appear. This condition is often self-correcting, indicated by the appearance of EC-5-COMPATIBLE message following the first message. On occasion, the issue does not self-correct, and the ports may remain unbundled.

CSCth09799

Performing a traceroute MPLS across an IPSec protected GRE tunnel carrying MPLS traffic may cause a traceback message at an intermediate-hop router along the path.

CSCth77918

When the EtherChannel group mode is on and you configure 802.1ad split horizon on the EtherChannel interface by entering the ethernet dot1ad uni s-port isolate interface configuration command, after a switch reload, a PAgP flap error occurs, and the EtherChannel goes down.

CSCtj48387

Crash on ASR occurs due to corrupt values passed from DHCP component to doprnt.

CSCtj60261

Traceroute on an MPLS TE tunnel over GRE causes traceback on a next hop router.

CSCtj83964

On a switch running Protocol-Independent Multicast (PIM) and Source Specific Multicast (SSM), multicast traffic might not be sent to the correct port after the switch reloads.

CSCtj88307

When you enter the default interface, switchport, or no switchport interface configuration command on the switch, this message appears: EMAC phy access error, port 0, retrying......

CSCtk18810

High memory usage is seen with Virtual Exec process.

CSCtn84698

When you configure VLAN-based Ethernet over Multiprotocol Label Switching (EoMPLS) on switches running Cisco IOS Release 12.2(52)SE or later, the bridge protocol data unit (BPDU) filter on the Layer 2 trunk interface does not filter BPDUs.

CSCtn94127

An RP crash is observed at dhcpv6_server_pd_assign_pool during security tests.

CSCto57605

If the Dynamic Trunking Protocol (DTP) is set to speed nonegotiate for two switches that interface each other, and the speed/duplex is configured as full/1000, the speed/duplex configuration of one of the switches changes to auto/auto when the switch is restarted. The port channel becomes incompatible and the second switch's operation is suspended. This problem applies only to the 1000BASE-LX interface.

CSCto57723

Cisco IOS Software and Cisco IOS XE Software contain a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. An attacker could exploit this vulnerability by sending a crafted request to an affected device that has the DHCP version 6 (DHCPv6) server feature enabled, causing a reload.

Cisco has released free software updates that address this vulnerability. This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120926-dhcpv6

CSCts03820

Auto Image Install: DHCP Option 125 / Sub Option 5 does not work.

CSCtt02313

PfR: Uncontrolled TC occurs due to Exit Mismatch.

CSCtt39990

%PM-4-LIMITS appear although the VPI does not go over the maximum limit.

CSCtw56617

C3750G: Unexpected ACL sequence delete.

CSCtw58495

show epm session summary crashes the switch.

CSCtw93790

snmp-server trap timeout is not working as expected.

CSCtx20903

TACACS authentication fallback is not working.

CSCtx61557

The switch crashes after logging "success" from "dot1x" for client (Unknown MAC).

CSCtx91976

SNMP PoE bug is seen on Cat 2960S.

CSCtx99483

Switch crashes when removing PBR from interface.

CSCty93544

ACL is not fully applied when TCAM space is exhausted.

CSCty28713

Packet loss occurs on a master switch uplink while a member switch reloads.

CSCtz27507

MF: 4500 crash occurs while polling ENTITY-MIB.

CSCtz54899

GLC-T in 12.2(55)SE5/ WS-C3750X-24S does not link up.

CSCtz92782

dACL is not applied on the switch interface in multi-domain mode.

Caveats Resolved in Cisco IOS Release 12.2(55)SE5

CSCsy43147

During a Telnet session, the router crashes when the TACACS+ server is configured or unconfigured (tacacs-server host command) using the single-connection keyword.

The workaround is to not use the single-connection keyword.

CSCtb35715

When you enter the show running-config interface configuration command, IP Service Level Agreement notifications are shown as enabled even when you have not enabled this configuration using the ip sla enable reaction-alerts interface configuration command.

There is no workaround.

CSCtc18841

If local proxy Address Resolution Protocol (ARP) is configured on the VLAN interface, the ARP entry for the Hot Standby Router Protocol (HSRP) enters into an incomplete state.

The workaround is to remove the proxy ARP feature on the VLAN interface (by using the no ip local-proxy-arp interface configuration command) and restart the interface.

CSCtg38468

When AAA authorization is used with TACACS+, an error is displayed if the banner message (banner exec global configuration command) starts with a blank character.

The workaround is to not start the banner message with a blank character.

CSCth00398

If the no vtp VLAN configuration command is used on a port that receives VTP updates, the switch does not process Layer 2 control traffic (STP and CDP) after some time.

The workaround is to configure VTP on the port or to not use the no vtp command.

CSCtj22354

The switch fails when LLDP data units with Type Length Value (TLV) of more than 10 management addresses (MA) are received.

The workaround is to disable the sending of LLDP MA TLVs on peer hosts.

CSCtj89743

CPU usage is high when a device connected to the switch is accessed using the https://IP_address command on the router.

The workaround is to reload the device.

CSCtn10697

The switch crashes when DCHP snooping is enabled with value 125 and an offer packet is received.

There is no workaround.

CSCto72927

If a Tcl policy is copied to the router, the router fails when an event manager policy is configured.

There is no workaround.

CSCtq09233

If a CLI configuration text file is copied from a Windows system to the switch, a space is appended to the end of the macro description command when the file is read from the flash of the switch. This leads to errors resulting in high CPU utilization on the switch. Another possible issue is that the macro is not removed when the link goes down or the connected device is removed from the switch.

The workaround is to copy the configuration file from a non-Windows system (like UNIX or Linux) or convert the file to an appropriate UNIX format before copying.

CSCtr28857

A vulnerability in the Multicast Source Discovery Protocol (MSDP) implementation of Cisco IOS Software and Cisco IOS XE Software could allow a remote, unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition.

Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available. This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-msdp

CSCtr91106

A vulnerability exists in the Cisco IOS Software that may allow a remote application or device to exceed its authorization level when authentication, authorization, and accounting (AAA) authorization is used. This vulnerability requires that the HTTP or HTTPS server is enabled on the Cisco IOS device.

Products that are not running Cisco IOS Software are not vulnerable.

Cisco has released free software updates that address these vulnerabilities.

The HTTP server may be disabled as a workaround for the vulnerability described in this advisory.

This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-pai

CSCts34688

The switch crashes due to the "HACL Acl Manager" memory fragmentation when a large access control list (ACL) is modified.

The workaround is add or remove ACE entries in sequential order when the ACL is modified.

CSCts75641

Routing Information Protocol (RIP) Version 2 packets egressing an 801.1Q tunnel interface are triplicated.

There is no workaround.

CSCtt16051

Cisco IOS Software contains a vulnerability in the Smart Install feature that could allow an unauthenticated, remote attacker to cause a reload of an affected device if the Smart Install feature is enabled. The vulnerability is triggered when an affected device processes a malformed Smart Install message on TCP port 4786.

Cisco has released free software updates that address this vulnerability. There are no workarounds to mitigate this vulnerability.

This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/
cisco-sa-20120328-smartinstall

CSCtt37202

If a client switch is authorized using MAC Authentication Bypass (MAB), and then by using the 802.1x standard and dynamic VLAN assignment, the MAC address of the switch is not updated in the MAC address table of slave switches.

The workaround is to not use both the 802.1x and dynamic VLAN assignment configurations for the client switch.

CSCtu14007

If a link fails and then recovers, the Resilient Ethernet Protocol (REP) continues to show the link status as failed. Consequently, no redundancy on the ring, and an outage occurs if another link fails.

The workaround is to enter the shutdown interface configuration command followed by the no shutdown command to reload the interface.

CSCtu17483

The switch crashes when an IP phone that uses LLDP and authenticates itself using MAC Authentication Bypass (MAB) or 802.1x is physically disconnected and reconnected to the switch port.

The workaround is to remove the aaa authorization network default group SG-PBA global configuration command.

Caveats Resolved in Cisco IOS Release 12.2(55)SE4

CSCta85026

The Dynamic Host Configuration Protocol (DHCP) CLI does not accept white spaces in raw ASCII option in the DHCP pool configuration submode. This issue is seen in Cisco IOS Release 12.4(24)T1 and later.

There is no workaround.

CSCtg11547

In a VPN Routing and Forwarding (VRF) aware setup, messages are not sent to the syslog server. This issue applies to Cisco IOS Release 12.2(53)SE and 12.2(53)SE1. This situation does not occur if system logging is configured in the global table.

This problem has been corrected.

CSCth87458

A memory leak occurs in the SSH process, and user authentication is required.

The workaround is to allow SSH connections only from trusted hosts.

CSCti37197

If a tunnel interface is configured with Cisco Discovery Protocol (CDP), the switch fails when it receives a CDP packet.

The workaround is to disable CDP on the interface by using the no cdp enable interface configuration command.

CSCtj56719

The switch fails when the Differentiated Services Code Point (DSCP) mutation name is longer than 25 characters.

The workaround is to configure DSCP mutation names with fewer than 25 characters.

CSCtk00846

If Auto Smartports macros are configured, access points with the AIR-CAP prefix are not detected.

The workaround is to manually configure the access point port.

CSCtl51859

Neighbor discovery fails for IPv6 hosts connected to the switch when the IPv6 MLD snooping feature is enabled globally on the switch.

The workaround is to disable IPv6 MLD snooping on the switch.

CSCtl60151

The switch sometimes reloads after a CPU overload, regardless of the process that is overloading the CPU.

This problem has been corrected.

CSCto67688

If a member switch does not have an access control list (ACL) and is running an Enforcement Policy Module (EPM) session, the client on that interface is re-authorized each time that the switch reloads.

The workaround is to configure an ACL on the interface.

CSCtr79386

The switch fails when DHCP snooping is configured and packet data traffic is excessive. The traffic exhausts the I/O memory and triggers the switch to crash.

There is no workaround.

Caveats Resolved in Cisco IOS Release 12.2(55)SE3

CSCto55124

When a member switch port security is used with port-based dot1x authentication and the switch MAC address is sticky, a connected device authenticates itself. Its MAC address is added as sticky in the switch configuration and in the port security tables of the stack switches. When the switch is shut down, the device MAC address is removed from the master switch, but it is retained in the member switch security tables. When the interface is re-enabled, the device MAC address is restored to the master switch configuration.

The workaround is to use port security without dot1x authentication.

Caveats Resolved in Cisco IOS Release 12.2(55)SE1

CSCtj03875

When you disconnect the spanning tree protocol (STP) peer link, the STP port path cost configuration changes.

There is no workaround.

CSCtj86299

If a static MAC address entry is configured for an IP address in the global routing table, ping requests are sent through the global context, and replies are sent through Virtual Routing and Forwarding (VRF). This is a VRF leak.

The workaround is to remove the static MAC address entry.

Caveats Resolved in Cisco IOS Release 12.2(55)SE

CSCsu31853

The buffer space of a switch running TCP applications is full while the TCP sessions are in the TIME_WAIT state. Buffer space becomes available after the TCP session the closed.

There is no workaround.

CSCtb12209

When port security is configured to restrict data on a port when a violation occurs, it can interfere with Spanning Tree Protocol (STP) and Link Layer Discovery Protocol (LLDP) control packets, and drop these packets, causing network instability.

The workaround is to configure port security to shut down the port when a violation occurs.

CSCte14603

A vulnerability in the Internet Group Management Protocol (IGMP) version 3 implementation of Cisco IOS Software and Cisco IOS XE Software allows a remote unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition. Cisco has released free software updates that address this vulnerability.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100922-igmp.shtml.

Note: The September 22, 2010, Cisco IOS Software Security Advisory bundled publication includes six Cisco Security Advisories. Five of the advisories address vulnerabilities in Cisco IOS Software, and one advisory addresses vulnerabilities in Cisco Unified Communications Manager. Each advisory lists the releases that correct the vulnerability or vulnerabilities detailed in the advisory. The table at the following URL lists releases that correct all Cisco IOS Software vulnerabilities that have been published on September 22, 2010, or earlier:

http://www.cisco.com/warp/public/707/cisco-sa-20100922-bundle.shtml

Individual publication links are in "Cisco Event Response: Semiannual Cisco IOS Software Security Advisory Bundled Publication" at the following link:

http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_sep10.html

CSCtf19991

If the RADIUS authentication server is unavailable and inaccessible authentication bypass is enabled, the switch grants the client access to the network by putting the connected port in the critical-authentication state in the RADIUS-configured or the user-specified access VLAN. After the server is available, the client is not reinitialized and moved out of the critical VLAN.

There is no workaround.

CSCtf27594

When Bidirectional Forwarding Detection (BFD) is enabled on an interface of a switch that is running Cisco IOS Release12.2(50)SE or later, Release 12.2(52)SE or later, or Release 12.2(54)SE, CPU spikes can occur once or twice per hour.

There is no workaround.

CSCtf33948

A PC in 802.1x or multidomain authentication (MDA) mode is connected to an IP phone and connected to a MDA-enabled switch port. After the PC and phone are authenticated on the port, the PC is down. The port does not automatically reauthenticate the PC.

There is no workaround.

CSCtg26822

When you configure a port for 802.1ad UNI by entering the ethernet dot1ad uni s-port interface configuration command and enter the l2protocol peer stp lldp command on a UNI-S port, STP and LLDP protocols are not peered between both switches.

The workaround, when you want to peer STP and LLDP between customer and provider edge switches and to tunnel other Layer 2 protocols, is to use the ethernet dot1ad uni c-port interface command to configure the service provider customer-facing port as a UNI-C port and not a UNI-S port. By default on UNI-C ports, all Layer 2 protocols, including STP and LLDP are peered. For protocols to be tunneled through the 802.1ad provider network, enter the l2protocol forward command on the UNI-C port.

CSCtg30232

When an alternate MTU size is applied to ES ports, packets are treated as expected (forwarded or dropped), but large packets are not tagged as giant frames.

There is no workaround. Accounting is not supported on ES ports.

CSCtg47738

This error message is displayed after copying a configuration file to the running configuration file fails:

%Error opening system:/running-config (No such file or directory)

The output of the dir system:/ EXEC command also does not show a running configuration file.

The workaround is to reload the switch.

CSCth03022

Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS Software and Cisco IOS XE Software that could allow an unauthenticated, remote attacker to cause a reload of an affected device or trigger memory leaks that may result in system instabilities. Affected devices would need to be configured to process SIP messages for these vulnerabilities to be exploitable.

Cisco has released free software updates that address these vulnerabilities. There are no workarounds for devices that must run SIP; however, mitigations are available to limit exposure to the vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-sip.shtml.

CSCti48504

Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS Software and Cisco IOS XE Software that could allow an unauthenticated, remote attacker to cause a reload of an affected device or trigger memory leaks that may result in system instabilities. Affected devices would need to be configured to process SIP messages for these vulnerabilities to be exploitable.

Cisco has released free software updates that address these vulnerabilities. There are no workarounds for devices that must run SIP; however, mitigations are available to limit exposure to the vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-sip.shtml.

CSCto88686

Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS Software and Cisco IOS XE Software that could allow an unauthenticated, remote attacker to cause a reload of an affected device or trigger memory leaks that may result in system instabilities. Affected devices would need to be configured to process SIP messages for these vulnerabilities to be exploitable.

Cisco has released free software updates that address these vulnerabilities. There are no workarounds for devices that must run SIP; however, mitigations are available to limit exposure to the vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-sip.shtml.

CSCtj41194

Cisco IOS Software contains a vulnerability in the IP version 6 (IPv6) protocol stack implementation that could allow an unauthenticated, remote attacker to cause a reload of an affected device that has IPv6 enabled. The vulnerability may be triggered when the device processes a malformed IPv6 packet.

Cisco has released free software updates that address this vulnerability. There are no workarounds to mitigate this vulnerability.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-ipv6.shtml.

CSCth69364

Cisco IOS Software contains a memory leak vulnerability in the Data-Link Switching (DLSw) feature that could result in a device reload when processing crafted IP Protocol 91 packets.

Cisco has released free software updates that address this vulnerability.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-dlsw.shtml.

CSCtd10712

The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:

NetMeeting Directory (Lightweight Directory Access Protocol, LDAP)

Session Initiation Protocol (Multiple vulnerabilities)

H.323 protocol

All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.

Cisco has released free software updates that address these vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.

CSCso02147

The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:

NetMeeting Directory (Lightweight Directory Access Protocol, LDAP)

Session Initiation Protocol (Multiple vulnerabilities)

H.323 protocol

All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.

Cisco has released free software updates that address these vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.

CSCti98219

The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:

NetMeeting Directory (Lightweight Directory Access Protocol, LDAP)

Session Initiation Protocol (Multiple vulnerabilities)

H.323 protocol

All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.

Cisco has released free software updates that address these vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.

CSCti48483

The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:

NetMeeting Directory (Lightweight Directory Access Protocol, LDAP)

Session Initiation Protocol (Multiple vulnerabilities)

H.323 protocol

All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.

Cisco has released free software updates that address these vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.

CSCtj04672

The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:

NetMeeting Directory (Lightweight Directory Access Protocol, LDAP)

Session Initiation Protocol (Multiple vulnerabilities)

H.323 protocol

All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.

Cisco has released free software updates that address these vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.

CSCth11006

The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:

NetMeeting Directory (Lightweight Directory Access Protocol, LDAP)

Session Initiation Protocol (Multiple vulnerabilities)

H.323 protocol

All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.

Cisco has released free software updates that address these vulnerabilities.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.

CSCto07919

Cisco IOS Software is affected by two vulnerabilities that cause a Cisco IOS device to reload when processing IP version 6 (IPv6) packets over a Multiprotocol Label Switching (MPLS) domain. These vulnerabilities are:

Crafted IPv6 Packet May Cause MPLS-Configured Device to Reload

ICMPv6 Packet May Cause MPLS-Configured Device to Reload

Cisco has released free software updates that address these vulnerabilities.

Workarounds that mitigate these vulnerabilities are available.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-ipv6mpls.shtml.

CSCtj30155

Cisco IOS Software is affected by two vulnerabilities that cause a Cisco IOS device to reload when processing IP version 6 (IPv6) packets over a Multiprotocol Label Switching (MPLS) domain. These vulnerabilities are:

Crafted IPv6 Packet May Cause MPLS-Configured Device to Reload

ICMPv6 Packet May Cause MPLS-Configured Device to Reload

Cisco has released free software updates that address these vulnerabilities.

Workarounds that mitigate these vulnerabilities are available.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-ipv6mpls.shtml.

CSCti79848

The Cisco IOS Software contains two vulnerabilities related to Cisco IOS Intrusion Prevention System (IPS) and Cisco IOS Zone-Based Firewall features. These vulnerabilities are:

Memory leak in Cisco IOS Software

Cisco IOS Software Denial of Service when processing specially crafted HTTP packets

Cisco has released free software updates that address these vulnerabilities.

Workarounds that mitigate these vulnerabilities are not available.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-zbfw.shtml.

CSCto68554

The Cisco IOS Software contains two vulnerabilities related to Cisco IOS Intrusion Prevention System (IPS) and Cisco IOS Zone-Based Firewall features.

These vulnerabilities are:

Memory leak in Cisco IOS Software

Cisco IOS Software Denial of Service when processing specially crafted HTTP packets

Cisco has released free software updates that address these vulnerabilities.

Workarounds that mitigate these vulnerabilities are not available.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-zbfw.shtml.

CSCtk67073

The Cisco IOS IP Service Level Agreement (IP SLA) feature contains a denial of service (DoS) vulnerability. The vulnerability is triggered when malformed UDP packets are sent to a vulnerable device. The vulnerable UDP port numbers depend on the device configuration. Default ports are not used for the vulnerable UDP IP SLA operation or for the UDP responder ports.

Cisco has released free software updates that address this vulnerability.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-ipsla.shtml.

CSCtk62453

The Cisco 10000 Series Router is affected by a denial of service (DoS) vulnerability where an attacker could cause a device reload by sending a series of ICMP packets.

Cisco has released free software updates that address this vulnerability.

Workarounds that mitigate this vulnerability are also available.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-c10k.shtml.

CSCto10165

A vulnerability exists in the Smart Install feature of Cisco Catalyst Switches running Cisco IOS Software that could allow an unauthenticated, remote attacker to perform remote code execution on the affected device.

Cisco has released free software updates that address this vulnerability.

There are no workarounds available to mitigate this vulnerability other than disabling the Smart Install feature.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-smart-install.shtml.

CSCtq28732

Symptoms: Memory leak is observed when device is configured parameter-map type inspectglobal.

Conditions: Device is configured with parameter-map type inspect global.

See also Cisco Security Advisory: Cisco IOS Software IPS and Zone Based Firewall Vulnerabilities, at the following link:

http://www.cisco.com/warp/public/707/cisco-sa-20110928-zbfw.shtml

Workaround: There is no workaround.

Documentation Updates

Updates to the Software Configuration Guide and Command Reference

Updates to the System Message Guide

Update to the Hardware Installation Guide

Updates to the Software Configuration Guide and Command Reference

The clustering chapter has been removed from the software configuration guide and the commands removed from the command reference. The Catalyst 3750 Metro switch does not support clustering.

References to switch stacks in the software configuration guide and command reference are incorrect and will be removed. The Catalyst 3750 Metro switch does not support switch stacks.

In the "Configuring RIP for IPv6" section in the "Configuring IPv6 Unicast Routing" chapter, the task table is incorrect. This is the correct table:

Updates to the System Message Guide

Added System Messages

Error Message    AUTHMGR-5-SECURITY_VIOLATION: Security violation on the interface 
[chars], new MAC address ([enet) is seen. AuditSessionID [chars]

Explanation    A host on the interface attempted to gain access to the network or attempted an authentication. The interface mode does not support the number of hosts that are attached to the interface. This is a security violation, and the interface has been error-disabled. The first [chars] is the interface, [enet] is the Ethernet address of the host, and the second [chars] is the session ID.

Recommended Action    Make sure that the interface is configured to support the number of hosts that are attached to it. Enter the shutdown interface configuration command followed by no shutdown interface configuration command to restart the interface.

Error Message    AUTHMGR-5-VLANASSIGN: VLAN [dec] assigned to Interface [chars] 
AuditSessionID [chars]

Explanation    A VLAN was assigned. [dec] is the VLAN ID, the first [chars] is the interface, and the second [chars] is the session ID.

Recommended Action    No action is required.

Error Message    AUTHMGR-7-FAILOVER: Failing over from [chars] for client ([chars]) on 
Interface [chars] AuditSessionID [chars]

Explanation    The authorization manager is failing over from the current authentication method to another method. The first [chars] is the current authentication method, the second [chars] is the client ID, the third [chars] is the interface, and the fourth [chars] is the session ID.

Recommended Action    No action is required.

Error Message    AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for 
client ([chars]) on Interface [chars] AuditSessionID [chars]

Explanation    All available authentication methods have been tried for the client, but authentication has failed. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action    No action is required. If local authorization has been configured, the port will be authorized based on the local authorization method. Otherwise, authentication will restart according to the configured reauthentication period.

Error Message    AUTHMGR-7-RESULT: Authentication result [chars] from [chars] for 
client [chars] on Interface [chars] AuditSessionID [chars]

Explanation    The results of the authentication. The first [chars] is the status of the authentication, the second [chars] is the authentication method, the third [chars] is the client ID, the fourth [chars] is the interface, and the fifth [chars] is the session ID.

Recommended Action    No action is required.

Error Message    DOT1X-5-FAIL: Authentication failed for client ([chars]) on Interface 
[chars] AuditSessionID [chars] 

Explanation    The authentication was unsuccessful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action    No action is required.

Error Message    DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X 
action. AuditSessionID [chars] 

Explanation    The system memory is not sufficient to perform the IEEE 802.1x authentication. [chars] is the session ID.

Recommended Action    Reduce other system activity to reduce memory demands.

Error Message    DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on 
Interface [chars] AuditSessionID [chars] 

Explanation    Authentication was successful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action    No action is required.

Error Message    DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on 
[chars] AuditSessionID [chars] 

Explanation    The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. This message might appear if IEEE 802.1x is enabled. [enet] is the client MAC address, the first [chars] is the interface, and the second [chars] is the session ID.

Recommended Action    If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.

Error Message    EPM-6-AUTH_ACL: POLICY [chars]| EVENT [chars]

Explanation    The switch has sent or received a download request for a downloadable ACL (dACL). The first [chars] is the dACL policy? The second [chars] is the event.

Recommended Action    No action is required.

Error Message    HARDWARE-3-ASICNUM_ERROR: [traceback] Port-ASIC number [dec] is 
invalid

Explanation    The port ASIC number is invalid. [dec] is the port ASIC number.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message    HARDWARE-3-PORTNUM_ERROR: [traceback] port number [dec] is invalid

Explanation    The port number is out of range. [dec] is the port number.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message    IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT: [chars] seems to be corrupted. 
Trying to read [dec] size

Explanation    The ifIndex table is corrupted. [chars] is the path to the IfIndex file, and [dec] is the number of bytes that was being read from the ifIndex table when the corruption was detected.

Recommended Action    Delete the ifindex table.

Error Message    IFMGR-3-INVALID_PERSISTENT_DATA: Invalid persistent data

Explanation    The interface manager attempts to write invalid persistent data.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message    ILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured 
by Cisco or with Cisco's authorization. This product may contain software that was 
copied in violation of Cisco's license terms. If your use of this product is the 
cause of a support issue, Cisco may deny operation of the product, support under 
your warranty or under a Cisco technical support program such as Smartnet. Please 
contact Cisco's Technical Assistance Center for more information.

Explanation    A license authentication failure occurred for the switch.

Recommended Action    Contact your Cisco sales representative for assistance.

Error Message    ILET-1-DEVICE_AUTHENTICATION_FAIL: The [chars] inserted in this switch 
may not have been manufactured by Cisco or with Cisco's authorization. If your use 
of this product is the cause of a support issue, Cisco may deny operation of the 
product, support under your warranty or under a Cisco technical support program 
such as Smartnet. Please contact Cisco's Technical Assistance Center for more 
information.

Explanation    A license authentication failure occurred for a component that was inserted in the switch. [chars] is the component.

Recommended Action    Contact your Cisco sales representative for assistance.

Error Message    REP-3-INVALIDPKT: received invalid pkt: [chars]

Explanation    The switch has received an invalid Resilient Ethernet Protocol (REP) packet. [chars] is information about the invalid packet.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message    REP-3-NOPPPROC: [traceback] Failed to create REP LSL Fast Hello Process

Explanation    The switch cannot exchange hello packets with its Resilient Ethernet Protocol (REP) neighbors because the Link Status Layer (LSL) age timer is set to more than 3 seconds.

Recommended Action    Reload the switch.

Error Message    SCHED-3-UNEXPECTEDEVENT: [traceback] [process information] Process 
received unknown event (maj [hex], min [hex])

Explanation    A process did not handle an event. The first [hex] is the major event number, and the second [hex] is the minor event number, both of which allow you to identify the event that occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.

Modified System Messages

Error Message    DOT1X-5-RESULT_OVERRIDE: Authentication result overridden for client 
([chars]) on Interface [chars] AuditSessionID [chars]

Explanation    The authentication result was overridden. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action    No action is required.

Error Message    DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary 
VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]

Explanation    An attempt was made to assign a primary VLAN to an 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Use a different VLAN.

Error Message    DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid 
secondary VLAN [dec] to PVLAN host 802.1x port [chars] AuditSessionID [chars] 

Explanation    An attempt was made to assign a non secondary VLAN to a private VLAN host 802.1x port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Change the port mode so that it is no longer a PVLAN host port, or use a valid secondary VLAN.

Error Message    DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND: Attempt to assign VLAN 
[dec], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars] 
AuditSessionID [chars] 

Explanation    An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shut down. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Make sure that the primary VLAN exists and is not shut down. Verify that the private VLAN is associated with a primary VLAN.

Error Message    DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN 
[dec] to non-PVLAN host 802.1x port [chars] AuditSessionID [chars] 

Explanation    An attempt was made to assign a secondary VLAN to a port that is not a private VLAN host port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Change the port mode so that it is configured as a private VLAN host port, or use a different VLAN that is not configured as a secondary VLAN.

Error Message    DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN [dec] to 
802.1x port [chars], which is configured as a SPAN destination AuditSessionID 
[chars] 

Explanation    An attempt was made to assign a VLAN to an 802.1x port that is configured as a Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Change the SPAN configuration so that the port is no longer a SPAN destination port, or change the configuration so that no VLAN is assigned.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication 
cannot activate because Data and Voice VLANs are the same on port AuditSessionID 
[chars] 

Explanation    Multi-Domain Authentication (MDA) host mode cannot start when the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port session ID.

Recommended Action    Change either the voice VLAN or the access VLAN on the interface so that they are not the same. MDA then starts.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] 
cannot be equivalent to the Voice VLAN AuditSessionID [chars]

Explanation    An attempt was made to assign a data VLAN to an 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Change either the voice VLAN or the 802.1x-assigned VLAN on the interface so that they are not the same.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN 
[dec] to 802.1x port [chars] AuditSessionID [chars] 

Explanation    An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Assign a different VLAN.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] 
to 802.1x port [chars] AuditSessionID [chars] 

Explanation    An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is out of range. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Update the configuration to use a valid VLAN.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or 
shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]

Explanation    An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Make sure the VLAN exists and is not shut down, or use another VLAN.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Attempt to assign VLAN [dec] 
to routed 802.1x port [chars] AuditSessionID [chars]

Explanation    An attempt was made to assign a VLAN to a supplicant on a routed port, which is not allowed. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Either disable the VLAN assignment, or change the port type to a nonrouted port.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Attempt to assign VLAN [dec] to 
promiscuous 802.1x port [chars] AuditSessionID [chars]

Explanation    An attempt was made to assign a VLAN to a promiscuous IEEE 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Change the port mode so that it is no longer a promiscuous port, or change the configuration so that no VLAN is assigned.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_RESERVED: Attempt to assign reserved VLAN 
[dec] to 802.1x port [chars] AuditSessionID [chars]

Explanation    An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the seconds [chars] is the session ID.

Recommended Action    Assign a different VLAN.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_RSPAN: Attempt to assign RSPAN VLAN [dec] to 
802.1x port [chars]. 802.1x is incompatible with RSPAN AuditSessionID [chars]

Explanation    Remote SPAN should not be enabled on a VLAN with IEEE 802.1x-enabled. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action    Either disable remote SPAN configuration on the VLAN, or disable IEEE 802.1x on all the ports in this VLAN.

Error Message    ESF_API-3-MTU_SET_FAILED: MTU size of [dec] failed on port [dec]

Explanation    An internal error prevents the switch from configuring the jumbo maximum transmission unit (MTU) setting on the enhanced-services ports. The first [dec] is the MTU size, and the second [dec] is the port number.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message    SPANTREE-2-BLOCK_BPDUGUARD_VP: Received BPDU on port [chars], vlan 
[dec] with BPDU Guard enabled. Disabling vlan. 

Explanation    A BPDU was received on the interface and the VLAN specified in the error message. The spanning tree BPDU guard feature was enabled and configured to shut down the VLAN. As a result, the VLAN was placed in the error-disabled state. [chars] is the interface, and [dec] is the VLAN.

Recommended Action    Either remove the device sending BPDUs, or disable the BPDU guard feature. The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have Port Fast enabled. Re-enable the interface and vlan by entering the clear errdisable privileged EXEC command.

Deleted System Messages

Error Message    DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X 
action.
Error Message    DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on 
Interface [chars]
Error Message    DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on 
[chars]
Error Message    SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: 
[chars]. 

Update to the Hardware Installation Guide

Installation Update

Cisco Ethernet Switches are equipped with cooling mechanisms, such as fans and blowers. However, these fans and blowers can draw dust and other particles, causing contaminant buildup inside the chassis, which can result in a system malfunction.

You must install this equipment in an environment as free as possible from dust and foreign conductive material (such as metal flakes from construction activities).

These standard provide guidelines for acceptable working environments and acceptable levels of suspended particulate matter:

Network Equipment Building Systems (NEBS) GR-63-CORE

National Electrical Manufacturers Association (NEMA) Type 1

International Electrotechnical Commission (IEC) IP-20

Related Documentation

These documents provide information about the switch and are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/switches/ps5532/tsd_products_support_series_home.html

Catalyst 3750 Metro Switch Getting Started Guide

Regulatory Compliance and Safety Information for the Catalyst 3750 Metro Switch

Catalyst 3750 Metro Switch Software Configuration Guide

Catalyst 3750 Metro Switch Command Reference

Catalyst 3750 Metro Switch System Message Guide

Catalyst 3750 Metro Switch Hardware Installation Guide

For more information about the Network Admission Control (NAC) features, see the Network Admission Control Software Configuration Guide.

Information about Cisco SFP, SFP+, and GBIC modules is available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.html

SFP compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html

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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html