Software Fixes

■LACP — Resolves several issues with LACP, including: conversation on a trunk may momentarily fail if a trunk member port goes down, difficulty accessing the MIB, configura- tion issues, port priority issues, problems with dynamic negotiation, and switch crashes with messages similar to:

-> Software Exception at woody_dev.c: 450 in AdMgrCtrl-> ppmgr_setDefaultPriority: invalid port number

and

-> Software exception at woody_pktDriver.c:317 -- in 'eDrvPoll' -> ERROR: ASIC buffer return failure

■Link — The switch exhibits intermittent link behavior when connected to some 3C905B 3Com NICs.

■Monitor Port — If a user attempts to monitor the monitoring port the switch displays a meaningless error message.

■Ping — The switch replies to pings with a source address of 127.1.1.1, which is a loopback address.

■Port Security — Static addresses are saved to startup-config without the user executing a write memory command. [Fix is: static addresses will only be saved to startup-config by executing the write memory command.]

■SNMP — For ports with no transceiver present, any SNMP sets to the hpSwitchPortTable fail and an SNMP get of hpSwitchPortType, hpSwitchStpPortType, or hpSwitchIgmpPortType2 returns an illegal value of zero (0).

■Stack Management — Resolves several issues with ProCurve Stack Management via the Web-browser interface, including problems with stacking configuration screen, Stack Member port counters, and not being able to add a candidate to a stack.

■STP — Resolves several issues with STP, including problems with an SNMP set and get of the dot1dStpPortEnable MIB variable, setting STP parameters via SNMP disables Spanning Tree, and a switch crash with a message similar to:

-> Software exception at stp_ctrl.c:154 -- in 'mStpCtrl'

■TFTP/XMODEM — The switch's event log is not properly formatted when captured via TFTP or XMODEM using the copy command.

■VLAN — After creating several VLANs, the default value for all ports in one VLAN is forbid and this value cannot be changed.

Release F.02.03Fixed in release F.02.03:■Stack Management — Cannot access member switches via SNMPv2c.

231