Fixes: - The master DWS-4026 fails to push AP configuration to the peer switch and the DWL-8600AP s managed by peer switch. - DWL-8600AP s that are managed by a DWS-4026 become hung suddenly. - DWL-8600AP s managed by a DWS-4026 may be incorrectly reported as rogue APs in the AP RF scan status and by the WLAN Visualization tool. - After several days of normal operation, some DWL-8600AP s managed by a DWS-4000 switch begin to be inaccessible and can't be managed by the DWS-4026. - No SNMP support is available to control client failure traps - When placing an object on the WLAN Visualization graph, the object is not placed in the desired location. - DWS-4026 might report its total number of associated clients incorrectly as on the WLAN Global Status and Associated Client Status page - Client fails to associate with a DWL-8600 AP managed by a DWS-4026 with 802.1X or WPA-EAP authentication. - The result is showed as error after compile with net-snmp. - The DWS-4026 will not allow for the DHCP Server on the VLAN 1 to be specified in the Helper IP address. It will show an error message: “Error! adding the Helper IP Address”. - The switch PoE feature reports an incorrect power budget, and the PoE usage threshold and per-port power limit do not work. - Editing and changing the graph image multiple times through the “Edit > Edit Graph menu” in “WLAN Visualization Tool” function might cause the switch to automatically reboot. - The WLAN > Monitoring > Client > Associated Clients page reports an incorrect value for the Encryption field of authentication clients. - The RADIUS authentication keeps dropping out. After rebooting the switch, it all works for a while before failing again. - After enabling the Captive Portal feature, the access to the network or management access to the switch through the Captive Portal might become unresponsive after a period of several hours or days. - Sometimes AP stops passing DHCP packets to the clients. AP will work fine again after rebooting, but it will stop passing DHCP packets again later. - When using Microsoft Windows 2008 server as DHCP and RADIUS Server, if accounting function on the RADIUS server is disabled but RADIUS Accounting related configuration on DWS-4026 is enabled, the clients can connect normally at the beginning, but can not authenticate successfully after several hours (< 1 day). The issue is due to out of RADIUS buffers on the switch that handles RADIUS accounting.
Скачать