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

ManualsBrandsHP ManualsComputer AccessoriesCisco Catalyst 1/10GbE 3120X Blade Switch

OL-16968-01

Open Caveats

• CSCsi14303

When booting a switch stack configured for IP source guard with port security and dynamic ARP

inspection, a message similar to this might appear:

SYS-2-LINKED: Bad enqueue of 2A3DE74 in queue 22881BC (l3a3-9) -Process=

"Port-Security", ipl= 6, pid= 161 (l3a3-9) -Traceback= 119CC50 11D2264 9571E0 119B4E0

95D41C 80DBD8 80E734 80B998 80AAD4 80B55C 9EB158 9E2544 (l3a3-9)

There is no workaround. This message is only information; switch functionality is not affected.

• CSCsi26444

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.

• CSCsi52914

When you are configuring a SPAN session, this message might erroneously appear even when two

source sessions are not configured:

% Platform can support a maximum of 2 source sessions

The workaround is to reboot the switch stack.

• CSCsi65551

In certain situations during master switch failover, a VLAN that has been error disabled on a port

might be re-enabled after the master switch failover, even though the port has not been configured

for automatic recovery.

There is no workaround.

• CSCsi70454

The configuration file used for the configuration replacement feature requires the character string

end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the

configuration rollback does not work.

These are the workarounds. (You only need to do one of these.)

–

Do not use a configuration file that is stored by or edited with Windows Notepad.

–

Manually add the character string end\n to the end of the file.

The workaround is to configure routed IPv4 multicast and IPv6 unicast traffic in different switch

ports.

• CSCsi73653

After a stack-master failover, switch ports in the stack cannot detect new devices. This only affects

new devices connected to the switch ports. Devices that were connected to active ports before the

failover remain in a trusted state.

There is no workaround.