Wireless Edge Services zl Module Release Notes WT.01.28

33
Known Software Issues and Limitations
Release WT.01.03
■ 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.
■ CLI (40893) — The sFlow timeout values that can be configured via the CLI differ from
those considered valid by the web management interface. This does not have any significant
consequence; values configured in either management context will be honored.
■ CLI (38053) — There is no support for tethereal on the module.
Workaround: Use the local or remote mirroring features of the switch to perform packet captures.
■ Infrastructure (41648) — The web management interface does not display the
management interface IP address for layer 3 mobility when the no layer3-mobility local address
command is executed through the CLI. Although the CLI output to the show layer3-mobility
global command correctly displays the management VLAN interface as the "local address",
the web management interface continues to display the local interface IP address.
Workaround: View the configuration using the CLI if there is some question about the active
configuration.
■ Infrastructure (39772) — When the primary RADIUS server is unavailable, a valid
secondary RADIUS server configuration will successfully authenticate the wireless client,
though the error messages generated may mislead the network administrator into thinking
authentication did not occur. Syslog messages may be similar to the following (date, time
and IP stamps were removed for clarity).
%USER-3-ERR: WIOS_SNMP[981]:auth failed:user manager role 0 src 0
%IMI-5-AUTHNOTIFY: Radius server secret not configured or server not
reachable. Hence trying next auth method
%PM-4-PROCNORESP: Process "fileMgmt" is not responding (2/20)
%PM-4-PROCNORESP: Process "securitymgr" is not responding (1/20)
%PM-4-PROCNORESP: Process "radconfd" is not responding (2/20)
%PM-4-PROCNORESP: Process "leaseparsed" is not responding (1/20)
%PM-4-PROCNORESP: Process "imi" is not responding (2/20)
%PM-4-PROCNORESP: Process "ccstatsd" is not responding (2/20)