Release Notes for Cisco Catalyst Blade Switch 3120 for HP Cisco IOS Release 12.2(40)EX
18
Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(40)EX1
OL-12250-01
Open Caveats
If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the
address (for example, www.cisco.com:84), you must enter http:// as the URL prefix. Otherwise, you
cannot launch the device manager.
Open Caveats
This section describes the open caveats with possible unexpected activity in this software release.
• CSCsg58889
If IEEE 802.1Q tunneling and Layer 2 protocol tunneling are configured first on physical ports, and
the ports are then added to an unconfigured port channel, the port channel might stop forwarding
traffic if one or more physical ports in the EtherChannel are shut down.
These are the workarounds:
–
Remove and reapply the Layer 2 protocol tunneling configuration on the port channel.
–
Configure the port channel first, next configure the physical ports, and then add them to the port
channel.
• CSCsg67684
When a cross-stack LACP EtherChannel has a maximum configuration, such as eight active and
eight hot-standby ports, and there are multiple rapid sequential master failovers and stack rejoins
that cause extreme stress, the port channel might not function as expected. Some ports might not join
the EtherChannel, and traffic might be lost. You can detect the condition by using the remote
command all show etherchannel summary privileged EXEC command.
There is no workaround. The out-of-sync switches must be reloaded.
• CSCsg77818
When a switch interface is configured with trust boundary and Cisco Discovery Protocol (CDP) or
the CDP table is repeatedly disabled, enabled, or cleared, the switch might reload.
The workaround is to avoid repeatedly disabling or clearing the CDP table, or avoid enabling CDP
when the trust boundary is configured on an interface. Or, first disable the trust boundary before you
disable or clear the CDP table or enable CDP.
• CSCsh12472
The switch might display tracebacks similar to this example when an EtherChannel interface
port-channel type changes from Layer 2 to Layer 3 or the reverse:
15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1
(ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C
4CEB50 859DF4 A7BF28 A98260 882658 879A58
There is no workaround.
• CSCsh70377
When a secondary VLAN is disassociated from the primary VLAN, duplicate MAC addresses on
the primary VLAN remain in the MAC address table.
The workaround is to disassociate the secondary VLAN from the primary VLAN by entering these
commands (in this order):
clear port-security {all | interface interface-id) privileged EXEC command
primary-vlan association remove vlan-id VLAN configuration mode command.










