Wireless Edge Services zl Module Release Notes WT.01.03

21
Known Software Issues and Limitations
Release WT.01.03
■ Applet (39807) — There should be an option to generate a Tech-Support file in the web
management application, and there is not.
Workaround: Generate this file using the CLI command. To do this using TFTP transfer, use the
following command syntax.
Host_zl_Switch# wireless-services <slot id >
Host_zl_Switch(wireless-services-slot)# support copy tech-support tftp://<ip address of tftp server>/
<filename.tar.gz>
■ Applet (41536) — In the web management interface L3 mobility page, changes made to
the settings take affect without the user hitting the Apply button.
Workaround: Use caution - do not click an option that you do not intend to configure on this
screen.
■ Applet (40012) — In the web management interface Special Features -> Station Intrusion
Detection, clicking in any of the threshold value fields enables the Apply button, even when
no changes were made. If the user has a concern that they inadvertently made a change, the
Revert button may be used.
■ Applet (41721) — The web management interface produces a Java console error message
when a DDNS TTL value of 1 is configured for a DHCP pool. Additionally, the value does not
get saved to the running configuration.
Workaround: Though a DDNS TTL value of 1 would be an unusual setting, if the user desires this
setting, reconfiguring it a second time will allow the value to be saved.
■ Applet (1000460321) — The web management interface Security -> MAC Filters ->
Authentication column has a "#" in place of MAC-Auth.
■ Applet (1000460349) — The web management interface Help section for the Security ->
NAT -> Configuration page states that the "list is empty".
■ Chassis (40367) — The switch does not consistently report the correct module status after
execution of the halt command. Typing show wireless-services <slot-id> at the switch CLI after
the halt has been executed may show a status of "not responding" even though the module
has been successfully shut down. It is safe to remove the module in that circumstance.
■ Chassis (41075) — The chassis self test LED should not be extinguished until the module
is fully booted and ready. It currently shuts off early.
■ CLI (40764) — It is possible to configure a duplicate SSID (an invalid condition) using the
CLI.
Workaround: Configure SSIDs via the web management interface or validate your configuration
by examination after CLI use.
■ CLI (41227) — The CLI allows the user to enter the command to remove an access-group
that does not exist without producing an error message.