Software Fixes

Release F.02.12Fixed in release F.02.12

Monitoring Port — When a config file containing a Monitoring Port configuration is loaded onto the switch via TFTP or XModem, the Monitoring Port feature does not work properly.

Release F.02.13Fixed in release F.02.13

Monitoring Port — Monitoring Port configuration changes made within a particular switch interface (e.g., Web-browser interface), are not correctly displayed within the other switch interfaces (e.g., CLI and Menu).

Release F.04.01 (Beta Release Only)Fixed in release F.04.01

CLI — The response to an incomplete trunk configuration command did not produce the proper message "Incomplete input: Trunk."

CLI — The crash history is lost after the "reload" command is performed from the CLI.

Crash — A transceiver hot-swap may cause the switch to crash with a message similar to:

-> Software exception at woodyDma_rev.c154 -- in 'eDrv'.

Crash — A transceiver hot-swap may cause the switch to crash with a message similar to:

-> Software exception in ISR at buffers.c:1627.

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

-> Software exception at woodyDma_recv.c:154 -- in 'eDrv'.

This crash may occur if both the following conditions exist:

a.The "reload" CLI command is issued; andb.A 100/1000-T transceiver is installed

Flow Control — Changing Flow Control setting on a port is not reflected in Auto- negotiation's advertised capability.

IGMP — Interoperability issues with some Cisco devices cause IGMP groups to be aged out of the switch's IGMP tables prematurely.

Menu/Web-Browser Interface — Display of mirror port configuration is inconsistent between menu and WEB interface.

236