Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(50)SE and Later

ManualsBrandsHP ManualsComputer AccessoriesCisco Catalyst 1GbE 3120G Blade Switch

OL-18270-03

Limitations and Restrictions

EtherChannel

These are the EtherChannel limitations:

• 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.

The EtherChannel ports are put in the error-disabled state because the switches in the partitioned

stacks send STP BPDUs. The switch or stack at the other end of the EtherChannel receiving the

multiple BPDUs with different source MAC addresses detects an EtherChannel misconfiguration.

After the partitioned stacks merge, ports in the suspended state should automatically recover.

(CSCse33842)

• When a switch stack is configured with a cross-stack EtherChannel, it might transmit duplicate

packets across the EtherChannel when a physical port in the EtherChannel has a link-up or

link-down event. This can occur for a few milliseconds while the switch stack adjusts the

EtherChannel for the new set of active physical ports and can happen when the cross-stack

EtherChannel is configured with either mode ON or LACP. This problem might not occur with all

link-up or link-down events.

No workaround is necessary. The problem corrects itself after the link-up or link-down event.

(CSCse75508)

• 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. (CSCsh12472)

IEEE 802.1x Authentication

These are the IEEE 802.1x authentication limitations:

• If a supplicant using a Marvel Yukon network interface card (NIC) is connected to an

IEEE 802.1x-authorized port in multihost mode, the extra MAC address of 0c00.0000.0000 appears

in the MAC address table.

Use one of these workarounds (CSCsd90495):

–

Configure the port for single-host mode to prevent the extra MAC address from appearing in the

MAC address table.

–

Replace the NIC with a new card.