Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(52)SE

24
Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(52)SE
OL-19714-01
Resolved Caveats
CSCsy90265
If you repeatedly enter the show tech-support privileged EXEC command, the switch might leak
memory and, in some cases, shut down.
The workaround is to reload the switch to clear the memory after repeated use of the show
tech-support command.
CSCsz66428
When flow control is enabled on a port-channel interface and you enter the flowcontrol receive on
interface configuration command, the bundle is not enabled after the switch restarts. The command
appears in the port-channel interface running configuration but does not appear in the switch running
configuration. A message such as this appears:
%EC-5-CANNOT_BUNDLE2: Gi0/27 is not compatible with Po1 and will be suspended (flow
control receive of Gi0/27 is on, Po1 is off)
%EC-5-CANNOT_BUNDLE2: Gi0/28 is not compatible with Po1 and will be suspended (flow
control receive of Gi0/28 is on, Po1 is off)
Use one of these workarounds:
To manually configure the port-channel interface, enter the flowcontrol receive on interface
configuration command.
To add the flow-control configuration to the interface after the switch restarts, use an EEM
script similar to this:
event manager applet Add_flowcontrol_on_restart
event syslog pattern SYS-5-RESTART
action 1 cli command "en"
action 2 cli command "conf t"
action 3 cli command "inter port 1"
action 4 cli command "flowcontrol receive on"
For action 3, specify the port-channel interface.
CSCsz72234
In a VPN routing/forwarding (VRF) instance, a port channel is configured, and the default route is
in the global routing table. If a link shuts down while the other links remain up, the port channel
might not forward traffic.
Use one of these workarounds:
Enter the shutdown interface configuration command, and then enter the no shutdown
interface command.
In the VRF instance, configure the links in the port channel as Layer 2 access links, and
configure a switch virtual interface (SVI).
CSCsz88857
When an interface on the stack master is a member of an EtherChannel and the channel group
number is removed before a master switch changeover, you can not use the same group number when
you recreate the EtherChannel after the changeover.
These are possible workarounds:
Reload the switches in the EtherChannel into the channel group that you were not able to create.
Use a new channel group number to bundle the physical interfaces in an EtherChannel.
Reconfigure the EtherChannel before the master switch changeover.