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

12
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
• When there is a VLAN with protected ports configured in fallback bridge group, packets might not
be forwarded between the protected ports.
The workaround is to not configure VLANs with protected ports as part of a fallback bridge group.
(CSCsg40322)
• When a switch port configuration is set at 10 Mb/s half duplex, sometimes the port does not send in
one direction until the port traffic is stopped and then restarted. You can detect the condition by
using the show controller ethernet-controller or the show interfaces privileged EXEC commands.
The workaround is to stop the traffic in the direction in which it is not being forwarded, and then
restart it after 2 seconds. You can also use the shutdown interface configuration command followed
by the no shutdown command on the interface. (CSCsh04301)
• 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)
• The bootloader label is incorrect and displays “CISCO DEVELOPMENT TEST VERSION.”
However, the actual bootloader software is the correct version with the correct functionality.
There is no workaround. It does not impact functionality. (CSCta72141)
• An internal switch port is down when one of these HP Flex 10-Gigabit Ethernet network interface
cards (NICs) is up:
– Flex 522m Mezz
– Flex 542m Mezz
– Flex 552m Mezz
The workaround is to use the speed nonegotiate interface configuration command on the internal
port. (CSCth94904)
EtherChannel
• In an EtherChannel running Link Aggregation Control Protocol (LACP), the ports might be put in
the suspended or error-disabled state after a stack partitions or a member switch reloads. This occurs
when
– The EtherChannel is a cross-stack EtherChannel with a switch stack at one or both ends.
– The switch stack partitions because a member reloads. The EtherChannel is divided between the
two partitioned stacks, each with a stack master.
The EtherChannel ports are put in the suspended state because each partitioned stack sends LACP
packets with different LACP Link Aggregation IDs (the system IDs are different). The ports that
receive the packets detect the incompatibility and shut down some of the ports. Use one of these
workarounds for ports in this error-disabled state:
– Enable the switch to recover from the error-disabled state.
– Enter the shutdown and the no shutdown interface configuration commands to enable the port.