HP ProCurve 2500 GVRP —, IGMP —, LACP —, Crash —, Crash —, Crash —, Crash —, Crash —, Crash —, Crash —, Event Log —, LACP/802.1X —

Software Fixes

■Crash — If dynamic trunks are configured and the switch is rebooted, the switch may crash with a message similar to:

->Software exception at rstp_dyn_reconfit.c:243 in -- 'Lpmgr'

■Crash — The "show config" CLI command may cause the switch to crash with a message similar to:

->Software exception "xlate.c:1358 in 'mSess1'

■Crash — When hot-swapping transceivers multiple times, the switch may crash with a message similar to:

-> Software exception at port_sm.c:378 in -- 'mPmSlvCtrl'

■

■

■

■

■

■

■

■

■

Crash — The switch may crash with a message similar to:

-> Software exception at alloc_free.c:545 -- in 'eDrvPoll'

Crash — The switch may crash with a message similar to:

->Asserts in rv.cc line 632

Crash — When adding ports to a manual LACP trunk configuration, the switch may crash with a message similar to:

-> Assert line 10070 cli_config_action.c

Crash — The switch may crash with a message similar to:

-> Bus Error: HW Addr=0x0000000 IP=0x002fe640 Task='eTelnetd'

This crash has been associated with security/vulnerability test applications such as Nessus.

Event Log — Log messages for trunks and trunk members enhanced to be easier to read.

GVRP — Upstream GVRP neighbor does not pass VLAN information to downstream neighbor after a topology change.

IGMP — Interoperability issues with some Cisco devices (such as some Cisco Catalyst 5000

&6000 series switches) cause IGMP groups to be aged out of the switch's IGMP tables prematurely.

LACP/802.1X — 802.1X and LACP trunks can co-exist on the same port. (Fix is to make these trunks mutually exclusive.)

LACP — LACP maintains a dynamic trunk with only 1 port configured for the trunk group.

240