Cisco Cisco IOS Software Release 15.0(1)SE

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 IP multicast routing or re-enable it globally on an interface.

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

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

After you configure a switch to join a multicast group by entering the ip igmp join-group 
group-address interface configuration command, the switch does not receive join packets from the 
client, and the switch port connected to the client is removed from the IGMP snooping forwarding 
table. 

Use one of these workarounds:

Cancel membership in the multicast group by using the no ip igmp join-group group-address 
interface configuration command on an SVI.

Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id 
global configuration command. (CSCeh90425)

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 10 to avoid disabling the queue. 

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

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)

A QoS service policy with a policy map containing more than 62 policers cannot be added to an 
interface by using the service-policy interface configuration command.

The workaround is to use policy maps with 62 or fewer policers. (CSCsc59418)

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)