Release Notes

Release Notes for the Catalyst 2960-C and 2960-Plus Switches, Cisco IOS Release 15.2(3)E and Later

OL-32525-01

Limitations and Restrictions

• VLAN, page 15

Configuration

• When connected to some third-party devices that send early preambles, a switch port operating at

100 Mb/s full duplex or 100 Mb/s 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 Mb/s and half duplex or to connect a hub or a

nonaffected device to the switch. (CSCed39091)

• When port security is enabled on an interface in restricted mode and the switchport block unicast

interface command has been entered on 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 on

that specific interface. (CSCee93822)

• 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)

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

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

• A ciscoFlashMIBTrap message appears during switch startup. This does not affect switch

functionality. (CSCsj46992)

• 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)

• When authorization and accounting are enabled on the switch and you use the interface range

command to change the configuration on a range of interfaces, the change might cause high CPU

utilization and authentication failures.

The workaround is to disable authorization and accounting or to enter the configuration change for

one interface at a time. (CSCsg80238, CSCti76748)

• When a logging discriminator is configured and applied to a device, memory leak is seen under

heavy syslog or debug output. The rate of the leak is dependent on the quantity of logs produced. In

extreme cases, the device may crash. As a workaround, disable the logging discriminator on the

device. (CSCur45606, CSCur28336)

Ethernet

• Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports

are distributed to member ports on load balance configuration and traffic characteristics like MAC

or IP address. More than one traffic stream may map to same member ports based on hashing results

calculated by the ASIC.

If this happens, uneven traffic distribution will happen on EtherChannel ports.

Changing the load balance distribution method or changing the number of ports in the EtherChannel

can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing: