Cisco Cisco IOS Software Release 15.2(3)E

12

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

If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, 
the switch can fail. 

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

When line rate traffic is passing through a dynamic port, and you enter the switchport access vlan 
dynamic interface configuration command for a range of ports, the VLANs might not be assigned 
correctly. One or more VLANs with a null ID appears in the MAC address table instead.

The workaround is to enter the switchport access vlan dynamic interface configuration command 
separately on each port. (CSCsi26392)

When many VLANs are configured on the switch, high CPU utilization occurs when many links are 
flapping at the same time.

The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are 
flapping. (CSCtl04815)

Cisco IE 2000 supports IPv4 static routing in the LAN Base image. To access static routing commands, 
you need to change the SDM template from the default template to lanbase-routing, followed by a switch 
reload sequence.

The following note is an update to the Regulatory Compliance and Safety Information (RCSI) guide. 
This note applies to the 61000-4-3 standard listed in the “EMC Interface Immunity” section of Table 1 
of the guide.