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

• If the director in the Smart Install network is located between an access point and the DHCP server,

the access point tries to use the Smart Install feature to upgrade even though access points are not

supported devices. The upgrade fails because the director does not have an image and configuration

file for the access point.

There is no workaround. (CSCtg98656)

• When a Smart Install director is upgrading a client switch that is not Smart Install-capable (that is,

not running Cisco IOS Release 12.2(52)SE or later), the director must enter the password configured

on the client switch. If the client switch does not have a configured password, there are unexpected

results depending on the software release running on the client:

–

When you select the NONE option in the director CLI, the upgrade should be allowed and is

successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but

fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.

–

When you enter any password in the director CLI, the upgrade should not be allowed, but it is

successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but

fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.

There is no workaround. (CSCth35152)

SPAN and RSPAN

• When the RSPAN feature is configured on a switch, Cisco Discovery Protocol (CDP) packets

received from the RSPAN source ports are tagged with the RSPAN VLAN ID and forwarded to trunk

ports carrying the RSPAN VLAN. When this happens a switch that is more than one hop away

incorrectly lists the switch that is connected to the RSPAN source port as a CDP neighbor.

This is a hardware limitation. The workaround is to disable CDP on all interfaces carrying the

RSPAN VLAN on the device connected to the switch. (CSCeb32326)

• 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 local SPAN. (CSCed24036)

Spanning Tree Protocol

• CSCtl60247

When a switch or switch stack running Multiple Spanning Tree (MST) is connected to a switch

running Rapid Spanning Tree Protocol (RSTP), the MST switch acts as the root bridge and runs

per-VLAN spanning tree (PVST) simulation mode on boundary ports connected to the RST switch.

If the allowed VLAN on all trunk ports connecting these switches is changed to a VLAN other than

VLAN 1 and the root port of the RSTP switch is shut down and then enabled, the boundary ports

connected to the root port move immediately to the forward state without going through the PVST+

slow transition.

There is no workaround.

Trunking

• 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