Installation guide

13
Release Notes for the Cisco ME 3400 Ethernet Access Switch, Cisco IOS Release 12.2(44)SE
OL-14632-01
Open Caveats
VLAN
These are the VLAN limitations:
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 not configure more than the recommended number of VLANs and trunks.
(CSCeb31087)
A CPUHOG message sometimes appears when you configure a private VLAN. Enable port security
on one or more of the ports affected by the private VLAN configuration.
There is no workaround. (CSCed71422)
Open Caveats
This section describes the open caveats in this software release.
CSCse11323
When 256 policy maps are configured globally on the system, the creation of the 257th policy map
is rejected. The platform supports a maximum of 256 policy maps. If you then delete some existing
policy maps and again configure the rejected policy map, when you try to attach that policy map to
an interface, it might be rejected without any descriptive error message explaining the reason for the
rejection or with an unexpected and incorrect error message.
The workaround is to delete the problematic policy map and to reconfigure it with a different name.
The new policy map should be accepted as expected.
CSCsi01526
Traceback messages appear if you enter the no switchport interface configuration command to
change a Layer 2 interface that belongs to a port channel to a routed port.
There is no workaround.
CSCsi06399
When a RIP network and IP address are configured on an interface, a traceback error occurs after
you enter the shutdown, no shutdown, switchport and no switchport interface configuration
commands.
The workaround is to configure the RIP network and the IP address after you configure the interface.
CSCsi06578
When you clear counters on an interface and then disable storm control on that interface, an
incorrect value (an unusually large number) for McastSuppDiscards appears when you enter the
show interface counters privileged EXEC command. This can occur when the interface had storm
control enabled and experienced traffic with a data rate higher than the storm-control threshold so
that storm control is dropping packets.
There is no workaround.