Release Notes for the Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 15.0(2)SE and Later

16
Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 15.0(2)SE and Later
OL-27316-02
Limitations and Restrictions
The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)
• When the PBR is enabled and QoS is enabled with DSCP settings, the CPU utilization might be high
if traffic is sent to unknown destinations.
The workaround is to not send traffic to unknown destinations. (CSCse97660)
SPAN and RSPAN
• When egress SPAN is running on a 10-Gigabit Ethernet port, only about 12 percent of the egress
traffic is monitored.
There is no workaround. This is a hardware limitation. (CSCei10129)
• The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.
The workaround is to configure aggressive UDLD. (CSCsh70244).
Stacking
• When using the logging console global configuration command, low-level messages appear on both
the stack master and the stack member consoles.
The workaround is to use the logging monitor global configuration command to set the severity
level to block the low-level messages on the stack member consoles. (CSCsd79037)
• If a new member switch joins a switch stack within 30 seconds of a command to copy the switch
configuration to the running configuration of the stack master, the new member might not get the
latest running configuration and might not operate properly.
The workaround is to reboot the new member switch. Use the remote command all show run
privileged EXEC command to compare the running configurations of the stack members.
(CSCsf31301)
• When the flash memory of a stack member is almost full, it might take longer to start up than other
member switches. This might cause that switch to miss the stack-master election window. As a
result, the switch might fail to become the stack master even though it has the highest priority.
The workaround is to delete files in the flash memory to create more free space. (CSCsg30073)
• The error message %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND might appear for a switch stack under
these conditions:
– IEEE 802.1 is enabled.
– A supplicant is authenticated on at least one port.
– A new member joins a switch stack.
You can use one of these workarounds:
– Enter the shutdown and the no shutdown interface configuration commands to reset the port.
– Remove and reconfigure the VLAN. (CSCsi26444)
• When you use the switch renumber global configuration command to renumber a member switch
in a switch stack and then reload the switch, the internal server-facing ports do not have the required
default of spanning-tree portfast enabled.
The workaround is to apply the switch provision configuration before you reboot the switch.
Enter
both the switch current-stack-member-number renumber new-stack-member-number and the
switch stack-member-number provision type global configuration commands, and reload the
switch. (CSCsl63862)