Installation guide

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 10 of 21
F0615-O
Firmware Release 5.0.11.4:
Resolved an issue when rebooting the RBT switch via the CLI command ―reset system‖ does not generate a
'warm start' SNMP. Instead, a 'cold start' trap is sent.
Resolved an issue when clients who authenticated to a switch with a low bias DAP moved to the high bias
switch when the switch became available.
Resolved an issue where using the same port for SSH and Telnet access caused the RBT switch to reboot.
Resolved an issue where setting ports as a port group, then changing one port to wired-auth type, caused the
RBT switch to become unresponsive.
When downgrading from 5.0 to 4.1 (and earlier releases), changes may be required in the 4.1 configuration if
the 5.0 configuration had a service profile with last-resort or web-portal access. Specifically, an authentication
access rule must be added for last-resort users and the correct VLAN (and other attributes) may need to be set
for the last-resort-<ssid>, web-portal-<ssid> special users. Earlier 4.2 versions contain a script that sets the
special user attributes and the last-resort access rule on downgrade from 5.0. It is highly recommended in any
case to back up the 4.x configuration before upgrading to 5.0.
Resolved an issue where using the ―monitor port counter receive-errors‖ command displays statistics in wrong
order.
Firmware Release 5.0.10.3:
Resolved an issue with the RBT-4102 not coming back online if connected to a non-PoE switch and power or
reset cycle was initiated to on host RBT-8xxx controller switch.
Based upon the previous resolution, the thin DAP boot-loader number has been incremented, so the new
bootloader code will be automatically downloaded to the DAP.
Resolved an issue where the Client MAC address was not flushed from the FDB after a DAP disconnect.
Resolved an issue where corrupted TAPA packets from configured DAPs were causing the RBT switch to core
crash.
Resolved an issue where a DAP is broadcasting a DHCP request to every IP address renewal. If two DHCP
servers are on the same segment this could cause a different DHCP server to send a DHCP response. When
this happens it will reboot the DAP even if it already received a DHCP acknowledgement from the correct DHCP
server (which was used previously).
Resolved an issue where the RBT switch generated excessive ROGUE_AP_ALERT:rfslave_handle_packet
messages, possibly affecting the DAPs to run countermeasures.
Resolved an issue with multiple core crashes on RBT switches with ―ASSERT‖ errors and DAP loss due to
increased traffic spikes in the network.
Firmware Release 5.0.9.3:
Resolved an issue for a performance problem with one of the encryption methods used in the supported access
points. Due to a change to the Atheros radio driver code, the WPA/TKIP protocol was executed in software
instead of in hardware. This led to a reduction in throughput of approximately 33% for that encryption type. This
problem also brought with it a chance of CPU over utilization that could lead to the access point rebooting while
under heavy WPA/TKIP traffic load.
Resolved an issue where connection loss occurred between the Intel 3945 Internal Wireless NIC and the non-
broadcasting SSID from the RoamAbout Switch system.
Resolved an issue where the RBT switch reported a ―DAP: Recv Seq Cntr Failure‖ error message from clients
using WPA-TKIP authentication, causing some clients to lose wireless connections to the network.
Firmware Release 5.0.9.2:
Added support for the RBT-8210. This RBT switch, along with the current RBT-8200, will be known as the RBT-
82x0 family.
Resolved an issue where DAPs would reset with an ASSERT error, due to traffic spikes in the network.
Resolved an issue where the RBT-1002-EU would crash with an ASSERT error after an image download.
Resolved an issue where a custom web page was not displayed after the client successfully authenticated
against the Access Point.
Resolved an issue where blank DNS and IP Router Fields in WebView resulted in a WebView IP Services error.
Resolved an issue where VLAN ports could not be selected in WebView.