Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(52)SE

ManualsBrandsHP ManualsComputer AccessoriesCisco Catalyst 1/10GbE 3120X Blade Switch

OL-19714-01

Resolved Caveats

• CSCsi65551

In certain situations during master switch failover, a VLAN that has been error disabled on a port

might be re-enabled after the master switch failover, even though the port has not been configured

for automatic recovery.

There is no workaround.

• CSCsi73653

After a stack-master failover, switch ports in the stack cannot detect new devices. This only affects

new devices connected to the switch ports. Devices that were connected to active ports before the

failover remain in a trusted state.

There is no workaround.

• CSCsj22678

A delay can occur when you remove an access control list (ACL) from a switch stack under these

conditions:

–

A QoS, per-port policy map is attached to a large number of SVIs in the stack.

–

A per-VLAN QoS, per-port policer policy map is attached to a large number of switched virtual

interfaces (SVIs) in the stack.

–

The ACL to be removed is being used by the policy map.

–

There are three or more switches in the stack.

The delay can increase, up to 30 minutes, depending on the number of SVIs that are attached to the

policy map. The delay does not affect the operation of the policy-map. However, either of these

workarounds will reduce the length of the delay:

–

Remove the access control entries (ACEs) from the destination ACL, leaving the ACL empty.

(The effect is the same as removing the ACL itself.)

–

Detach the affected policy-maps from all the attached VLANs and SVIs, remove the ACL from

the policy-maps, and then reattach the policy-maps back to the original SVIs.

• CSCsk19926

Traffic is not received on a member port in a switch stack under these conditions:

–

The port is in a cross-stack EtherChannel.

–

One or more of the master switch Cisco TwinGig Converter Module ports are in the cross-stack

EtherChannel.

–

This member switch has been reloaded.

The workaround is to enter the shutdown and no shutdown interface configuration commands on

the affected interface or to reload the entire stack instead of a single member switch.

• CSCsl49153

You might receive a traceback message when you use the no interface port-channel global

configuration command to delete interfaces from an EtherChannel that has port channels on multiple

stack members.

The workaround is to save the configuration and to reload the stack.

• CSCso15367

The CLI output for the StackWise Plus port 2 shows the output for the StackWise Plus port 1 and

vice versa.

There is no workaround.