2910al Firmware Bugs?

[CraigS1]

I've been running version W.15.14.0007, 0009, 0011, and 0012 firmware on my 2910al switches, but I've found some bugs.  (One of which is pretty serious.)  I've tried to create a support ticket, but HP's web site crashes during the process.  (I've tried over the course of several weeks, on several different browsers, and several different computers.)  Here are the problems I've noted.  Hopefully, someone can pass this on to whoever is supposed to test these things:

1.  When using the menu system from a telnet session, you cannot save changes to the trunking Group and Type for each port. The error message, Unable to save field. appears when selecting Save. These settings CAN be changed using the Web interface or the CLI. I also verified that this works in W.15.13.0014 and W.15.12.0015. (It appears to have been broken in the W.15.14.xxxx series.)

2.  Module information is NOT displayed when using the menu system from a telnet session.

3.  Most seriously, modules do NOT work when hot-plugged!  (The MDL Status light is red on the module and the MDL light on the switch itself is red.)  Modules DO work when the switch is powered off and back on.  (I did not check a switch reboot.)

Is a newer version of the W.15.14.xxxx firmware available?

Thank you.

[Vince-Whirlwind]

1. They do seem to be deprecating the menu system as they release newer firmware. I've noticed not everything works via menu. Then again, there isn't much I use the menu for anymore.

2. With the modules - if you take out a CX4 module and replace it with a SFP+ module, you definitely need a reboot, even though the modules are hot-swappable, the switch needs a reboot if you've changed the interface type. Adding a module to a slot that hasn't ever had a module before used to work fine without a reboot, from memory.

[CraigS1]

In the case of a module swap, I was placing a module in an empty slot.  I haven't tested that with older firmware, but I did test on two different switches with several modules, so it certainly appears to be a firmware issue.