Enterasys RoamAbout RBT-4102-EU Instruction Manual

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 1 of 21
F0615-O
50 Minuteman Road
Andover, MA 01810 (USA)
Tel: [phone]
Enterasys RoamAbout®Wireless Switch 8xx0 Release
Firmware Version 6.0.4.4
October 17, 2007
INTRODUCTION:
The RBT-8xx0 family of wireless switches include the following: 1) the RBT-8100 and RBT-8110, which have the
ability to control up to 24 access points; 2) the RBT-8200 and RBT-8210, which have the ability to control
24/48/72 access points; and 3) the RBT-8400, which has the ability to control 40/80/120 access points. The
RoamAbout Switch Manager (RASM) can manage all of these devices.
The 6.0.4.4 Firmware release addresses firmware modifications and customer escalations (refer to the Firmware
and Enhancements section).
Enterasys recommends that you thoroughly review this document prior to installing or upgrading this product.
NOTE: Enabling Direct Path Forwarding (also known as local switching) for a given AP affects the
number of ACEs that can be applied within a single ACL policy to a user connecting to that AP.
When local switching is enabled on an AP in version 6.0.4.4 of RBT switch firmware, up to 16
ACEs in an ACL policy can be applied to a user of that AP. In a future release of the firmware, the
number of available ACEs per ACL policy will increase to approximately 25. For more information,
see the Known Restrictions and Limitations section of these release notes.
NOTE: At the time of this release, there is an open LED issue with the RBT-82x0 switches, where ports 1 and 2
could show an incorrect connection status after a device reboot when there are no cables attached.
This does not affect the performance for ports in any way, and will be resolved in a future release.
NOTE: The 5.0.9.2 RoamAbout Wireless Switch Firmware, and future released firmware, support the RBT-8210,
the new small form factor switch that replaces the larger RBT-8200. The RBT-8210 uses the RBT-8200
firmware and commands. The RBT-8210 prompt is displayed as RBT-8200.
NOTE: If you are using a 4.x firmware image/software, Enterasys recommends that you upgrade the
RoamAbout Switch Manager (RASM) to firmware version 5.0.12.2 BEFORE upgrading your RBT-8xx0
wireless switches to firmware version 5.0.12.2.
NOTE: If you are upgrading a pre-existing RBT-4102 or RBT-4102-EU model Access Point from 4.1.4 or earlier,
please read the instructions listed in the Firmware Release 4.1.5.0 section of the Firmware Changes
and Enhancements section of the RoamAbout Switch Manager (RASM) 6.0.4.4 Release Notes.
NOTE: For the calendar year 2007, please be aware that the United States Daylight savings time period begins
March 11, 2007, and ends November 4, 2007. Refer to the “Configuring and Managing Time
Parameters” chapter, section “Configuring the Summertime Period”, in the Mobility System Software
Configuration Guide for more detailed instructions.
NOTE: For the 6.0.4.2 release and beyond, the „DAP‟ term has been replaced with „AP‟.

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 2 of 21
F0615-O
FIRMWARE SPECIFICATION:
Status
Version No.
Type
Release Date
Current Release
6.0.4.4
Customer
October 2007
Previous Release
6.0.4.2
Customer, added TRPZ-MP-620 support
September 2007
Previous Release
5.0.12.2
Customer, added TRPZ-MP-422 support.
Includes DFS2 Support for North
American Models:
RBT-1002 Rev 6A (AP ID: AP1002C),
RBT-4102 Rev 6A (AP ID: AP4102C),
RBT-1602 Rev 6A (AP ID: AP1602C)
June 2007
Previous Release
5.0.11.4
Customer
April 2007
Previous Release
5.0.10.3
Customer –Patch
March 2007
Previous Release
5.0.9.3
Customer
February 2007
Previous Release
5.0.9.2
Customer, added
RBT-8210 support
January 2007
Previous Release
5.0.6.1
Customer, added
TRPZ-MXR-2 support
December 2006
Previous Release
4.2.5.1
Customer, added
RBT-8110 and
TRPZ-MP-620 support
October 2006
Previous Version
4.1.11.0
Customer
June 2006
Previous Version
4.1.5.0
Customer
April 2006
Previous Version
4.1.4.0
Customer, added RBT-8200 support
February 2006
Previous Version
4.0.21.0
Customer
January 2006
Previous Version
4.0.20.0
Customer
December 2005
Previous Version
4.0.18.0
Customer
November 2005
Previous Version
4.0.16.0
Customer, added RBT-8400 support
September 2005
Previous Version
4.0.7.0
Customer
August 2005
Previous Version
4.0.4.0
Customer, added RBT-8100 support
July 2005
NOTE: For firmware release 5.0.12.2, please read the DFS2 Tech Tip on page 16 for the channel availability
information.
HARDWARE COMPATIBILITY:
Switches:
- RBT-8100, RBT-8110, RBT-8200, RBT-8210, RBT-8400, and TRPZ-MXR-2.
Thin Access Points:
- RBT-1002, RBT-1002-EU, RBT-1602, thin-RBT-4102, thin-RBT-4102-EU, thin-RBT3K-AG, MP-372, the
outdoor TRPZ-MP-620 Access Point, TRPZ-MP-422, and the APxxxxC ID Access Points for DFS2
support: RBT-1002 rev 6A, RBT-4102 rev 6A, and RBT-1602 rev 6A.
Standalone Access Points:
- RBT-4102, RBT-4102-EU, and RBT3K-AG.
NETWORK MANAGEMENT SOFTWARE SUPPORT:
NMS Platform
Version No.
Module No.
RoamAbout Switch Manager 50 Access Point User License
6.0.4.4
RBT-NMS-50
RoamAbout Switch Manager 200 Access Point User License
6.0.4.4
RBT-NMS-200

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 3 of 21
F0615-O
NMS Platform
Version No.
Module No.
RoamAbout Switch Manager unlimited User License
6.0.4.4
RBT-NMS-UNL
RoamAbout RF Planning Tool
6.0.4.4
RBT-RFPLAN
RBT-8400 Platform
Version No.
Module No.
RBT-8400 40 Additional Access Point Upgrade License
6.0.4.4
RBT-8400-40
RBT-8400 80 Additional Access Point Upgrade License
6.0.4.4
RBT-8400-80
RBT-82x0 Platform
Version No.
Module No.
RBT-82x0 24 Additional Access Point Upgrade License
6.0.4.4
RBT-8200-24
RBT-82x0 48 Additional Access Point Upgrade License
6.0.4.4
RBT-8200-48
SUPPORTED FUNCTIONALITY:
Please refer to the RoamAbout Mobility System Software Configuration Guide and the RoamAbout Software
Management Interface Reference for more details on the new enhancements and overall functionality.
New Product Features
RF Load Balancing
Mesh Services
Local Switching –also known as Direct Path
Forwarding
Wireless Bridging
Enforceable Beacon Data Rate Control
Logout for Web Authentication
MX Seed Redundancy
Password Management
NOTES:
Local switching is only available in RBT firmware version 6.0 and higher.
Restricting Layer 2 forwarding for a VLAN is not supported if the VLAN is configured for local
switching.
The DHCP restrict feature is not supported for locally switched clients.
Web Portal is not supported for locally switched clients.
On a directly attached MP, when the set port type command is used to specify a port, cannot be
configured to perform local switching. However, a directly connected MP with an unspecified port can
perform local switching.
IGMP snooping is not supported with local switching.
Locally Switched APs can only support 16 ACL rules, total of inbound and outbound.
For Wireless bridging, here are some best practice guidelines:
oWhen connecting a Mesh Portal to the network, use only ethernet port 1 on the AP.
oBecause all AP CPU cycles are devoted to bridging, make other arrangements for service
coverage in the bridge area as the endpoints cannot provide other wireless services.
oA single radio must be devoted to maintaining the bridge.
Existing Product Features
WebView 2 –updated Web interface
RBT-RBT security (also called RAS-RAS security)
AirDefense software support on APs
AeroScout RFID tag support
Persistent VLAN assignment for roaming clients
Simplified Web-Portal and last-resort configuration
RF Auto-Tuning enhancements
Unscheduled Automatic Powersave Delivery (U-APSD)
support
Local software images on APs
DHCP server enhancements
RADIUS accounting enhancements
Support for special characters in SNMP community
names
Increased life span of new self-signed certificates
Web Interface to RASM services

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 4 of 21
F0615-O
Existing Product Features
Web-Start Client
Static IP configuration for APs
Sygate On-Demand Agent (SODA)
Broadcast settings per Wireless profile
Configurable data rate settings for clients
Session Based Call Admission Control
Static Class of Service
User Session Timers per SSID
Network Planning and Site Survey
Management services
SSID (Wireless Service)
Radio and Service profiling
Load Sharing
802.1Q VLANs
Spanning Tree –PVST
AAA/802.1X
ACLs
IP services
RF detection
Rogue detection
Countermeasures
Client and AP monitoring
Site policies
Reporting
Image repository and deployment
Auto-AP configuration
L2 traffic restriction
Default AAA attributes for each SSID
On-demand countermeasures
Network Domains
Configurable timeout for the RoamAbout Switch CLI
sessions
Configurable CoS to QoS mappings
INSTALLATION AND CONFIGURATION NOTES:
In general, the RoamAbout Wireless Switch RBT-8xx0 has been, or is being, shipped to you with a previous
firmware version. Please refer to the appropriate RBT-8xx0 Quick Start or the RBT-8xx0 Installation Guide for
hardware installation information. Please refer to the next section, Upgrading the RBT-8xx0 Switches,for
upgrading information and procedures.
UPGRADING THE RBT-8XX0 SWITCHES FROM PREVIOUS 4.0.X VERSIONS:
Minimum RBT Switch Requirements for Upgrade
Product
Minimum RBT switch version required
Upgrade Path
RBT-8100
4.0.4.0
4.0.4.0 5.0.12.2 6.0.4.x
RBT-8200
4.1.4.0
4.1.4.0 5.0.12.2 6.0.4.x
RBT-8110, RBT-8210
4.2.5.1
4.2.5.1 5.0.12.2 6.0.4.x
RBT-8400
4.0.16.0
4.0.16.0 5.0.12.2 6.0.4.x
Note: You must upgrade to RBT switch Version 5.0 or later before upgrading to RBT switch Version 6.0.
Preparing the RBT Switch for the Upgrade
Note: The following upgrade procedures refer to all RBT-8xx0 switches.
Caution!
Save the configuration, and then create a backup of your RBT switch files before you upgrade the switch.
Enterasys Networks recommends that you make a backup of the switch, before you install the upgrade. If
an error occurs during the upgrade, you can restore your switch to its previous state. If you later decide to
downgrade the switch, commands with newer syntax in future RBT switch versions might not be
converted correctly.

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 5 of 21
F0615-O
1. Use the following command to save the configuration. Unsaved changes will be lost during the upgrade
procedure.
RBT-8xx0# save config [filename]
2. The following command should be used to back up the switch‘s files:
RBT-8xx0# backup system [tftp://ip-addr/]filename [all | critical]
3. To restore a switch that has been backed up, use the following command:
RBT-8xx0# restore system [tftp://ip-addr/]filename [all | critical] [force]
The ―Upgrade Scenario‖ listed below shows an example use of the backup command. For more information about
these commands, see the ―Backing Up and Restoring the System‖ section in the ―Managing System Files‖
chapter of the RoamAbout Mobility System Software Configuration Guide.
Note: If you have made configuration changes but have not saved the changes, use the save config
command to save the changes, before you back up the switch.
If the RAS is running an earlier version of firmware, use the copy tftp command to copy files from the switch onto
a TFTP server.
Upgrading an Individual Switch Using the CLI:
1. Save the configuration, using the save configuration command.
2. Back up the switch, using the backup system command.
3. Copy the new system image onto a TFTP server.
For example, login to http://www.enterasys.com/download/ using a web browser on your TFTP server and
download the image onto the server.
4. Copy the new system image file from the TFTP server into a boot partition in the switch‘s nonvolatile
storage. You can copy the image file only into the boot partition that was not used for the most recent
restart. For example, if the currently running image was booted from partition 0, you can copy the new
image only into partition 1.
5. Set the boot partition to the one with the upgrade image for the next restart.
a. To verify that the new image file is installed, type show boot.
6. Reboot the software.
a. To restart an RBT switch and reboot the software, type the following command:
RBT-8xx0# reset system [force]
After resetting the RBT switch, the switch boots using the new image. The RBT switch also sends the AP
version of the new boot image to the configured APs and restarts the APs. After an AP restarts, it checks
the version of the new AP boot image to make sure the boot image is newer than the boot image
currently installed on the AP. If the boot image is newer, the AP completes installation of its new boot
image by copying the boot image into the AP‘s flash memory, which takes about 30 seconds, then
restarts again. The upgrade of the AP is complete after the second restart.

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 6 of 21
F0615-O
Upgrade Scenario:
To upgrade an RBT-8xx0 switch from one RBT switch Version to another, type commands such as the
following.
Note: This upgrade scenario uses the firmware image file 6.0.4.4 to show the download features. Please
follow these procedures for any of the 4.0.x, 4.1.x, 4.2.x, and 5.0.x firmware images.
Note: This example copies the image file into boot partition 1. On your switch, copy the image file into
the boot partition not used for the last restart. For example, if the switch booted from boot partition 1, copy
the new image into boot partition 0. To see boot partition information, type the show boot command.
RBT-8200# save config success: configuration saved.
RBT-8200# backup system tftp:/[ip-addr]/sysa_bak success: sent 28263 bytes in 0.324 seconds [ 87231
bytes/sec]
RBT-8200# copy tftp://[ip-addr]/R2060404.REL boot1:R2060404.REL success: received 11159702 bytes
in 18.391 seconds [606802 bytes/sec]
RBT-8200# set boot partition boot1 success: Boot partition set to boot1.
RBT-8200# show boot
Configured boot version: 6.0.4.4.0
Configured boot image: boot1: R2060404.rel
Configured boot configuration: file:configuration
Backup boot configuration: file:backup
Booted version: 5.0.12.2.0
Booted image: boot0:R2050C02.REL
Booted configuration: file:configuration
Product model: RBT-8200
Upgrading an Individual Switch Using the RoamAbout Switch Manager (RASM)
Please refer to the chapter ―Managing and Monitoring Your Network‖, section ―Distributing Image and
Configuration Files‖ in the RoamAbout Switch Manager User’s Guide when upgrading the RBT-8xx0 switch to
the released version.
SYSTEM PARAMETER SUPPORT:
RoamAbout System Parameters:
Parameter:
Supported Value:
RBT switches in a single Network Domain
500
RBT switches in a single Mobility Domain
32
Roaming VLANs per RBT switch
300
Does not include local statically configured VLANs
VLANs per Mobility Domain
400
This number consists of 300 roaming VLANs plus 100 local
statically configured VLANs
DAPs per RBT switch
RBT-81x0: 60 configured, 24 active
RBT-82x0: 180 configured, 72 active
RBT-8400: 300 configured, 120 active
SSIDs per radio
8
Minimum link speed within a Mobility Domain
128 Kbps

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 7 of 21
F0615-O
Network Parameters:
Parameter:
Supported Value:
Forwarding database entries
RBT-81x0: 8192
RBT-82x0: 8192
RBT-8400: 16383
Statically configured VLANs
128
Virtual ports (sum of all statically configured
VLAN physical port memberships)
256
Spanning trees (STP/PVST+ instances)
64
ACLs and Location Policies
ACEs per switch
RBT-81x0: 700
RBT-82x0: 700
RBT-8400: 2308
ACEs per ACL:
RBT-81x0: 25
RBT-82x0: 25
RBT-8400: 267
Locations Policies per switch:
All models: 1
The Location Policy can have up to 150 rules.
ACL rules (ACE‘s) with Local Switching (Direct Path
Forwarding) enabled: 16
IGMP Streams
500
Note: Replications of a stream on multiple VLANs count as
separate streams on each VLAN.
Management Parameters:
Parameter:
Supported Value:
Maximum instances of the RoamAbout
Software Management system simultaneously
managing a network
3
Telnet management sessions
RBT-81x0: 8
RBT-82x0: 8
RBT-8400: 8
Note: The maximum combined number of management
sessions for Telnet and SSH together is 8 for the RBT-8400,
RBT-81x0, and the RBT-82x0.
SSHv2 management sessions
RBT-81x0: 8
RBT-82x0: 8
RBT-8400: 8
Telnet client sessions (client for remote login)
RBT-81x0: 8
RBT-82x0: 8
RBT-8400: 8
NTP servers
3
SNMP trap receivers
8
Syslog servers
4
RADIUS servers
100 configured on the switch
10 in a server group
4 server group in a AAA rule

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 8 of 21
F0615-O
Client and Session Parameters:
Parameter:
Supported Value:
Authenticated and associated clients per radio
100
Clients who are authenticated but not yet associated are
included in the total
Active clients per radio
50
Total number of active clients simultaneously sending or
receiving data
Active AAA sessions (clients trying to
establish active connections) per RAS switch
RBT-81x0: 600
RBT-82x0: 1800
RBT-8400: 2500
AAA users configured in local user database
RBT-81x0: 999
RBT-82x0: 999
RBT-8400: 999
FIRMWARE CHANGES AND ENHANCEMENTS:
Firmware Release 6.0.4.4:
Resolved an issue where a bit on the non-mesh supported Access Points could be randomly set, causing the
APs to reset several times.
Resolved an issue where an external antenna attached to the TRPZ-MP-422 Access Point was not transmitting
the configured power.
Resolved an issue for the RBT-8400 where system generated core crash files were truncated and unreadable.
Firmware Release 6.0.4.2:
Added support for the TRPZ-MP-620 Outdoor Access Point. Direct Path Forwarding (Local Switching), Mesh
Services, and Wireless Bridging are only supported on the TRPZ-MP-620 and TRPX-MP-422 Access Points.
The RBT-8400 image is smaller than previous releases due to a shared library format introduced in the 6.0
firmware. Statically linked executables, which called to individual library functions, were replaced with run-time
calls, reducing the total number of individual library routines to be opened, and reducing the overall size of the
firmware required to operate the network switch. This format also increases the amount of memory available for
data transfer and table maintenance.
Resolved the issue where the Static IP configuration and deployment for the AP4102 and AP3000 did not
remain persistent with the AP upon reboot.
Resolved the erroneous message error printed to the CLI when the RBT-8400 reboots with 5.0.12.2:
Bootloader upgrade 5.0.x to 5.0.x needed. (x could be any number)
cp: /boot0/bload: No space left on device
Resolved an issue where the TRPZ-MP-422 Access Point image does not load with the 6.0.x code.
Resolved an issue where the configured APs in a network plan would crash upon RBT firmware upgrade due to
a DNS update entry on the RBT switch.
Resolved an issue where the Radius CLASS attribute was not sent with stop packets.
Resolved an issue where the RBT switch spoofed a DNS reply with a 169.254.x.x if the DNS server took more
than 3 seconds to respond. Certain Linux and Vista users will drop this packet causing everything to fail
Resolved an issue where the configured APs would crash with various exception messages, including TLB data
miss and sigtrap.
Resolved an issue where an expired password could be used to log into the system.
Resolved an issue where the APs may reset if the traffic load to the RBT switch host IP address exceeds
200Mb/s.
Resolved an issue where the configured AP name is not shown in the SNMP trap.
Resolved an issue where IP addresses were transposed in MIB queries that returned IP address information.

CUSTOMER RELEASE NOTES
10/17/07 P/N: 9038177-17 Subject to Change Without Notice Page: 9 of 21
F0615-O
Firmware Release 5.0.12.2:
Added support for the TRPZ-MP-422 Access Point.
Added support for the following DFS2 compliant North American model Access Points:
RBT-1002 Rev 6A (AP ID: AP1002C), RBT-4102 Rev 6A (AP ID: AP4102C), RBT-1602 Rev 6A (AP ID:
AP1602C). Please see the DFS2 Tech Tip on page 16 for further information.
Resolved an issue where the RBT switch can lock-up when a Nessus scan is deployed against the switch.
Resolved an issue where the RBT switch sends the NAS port attribute four (4) times in a RADIUS request.
Resolved an issue where the MX tunnel functionality would fail to report the status of other RB switch members
in the network domain.
Resolved an issue where the VLAN member information was not added to the RBT switch configuration when
using the WebView Quickstart for initial configuration.
Resolved a WebView issue where a second VLAN‘s interface IP information would display an error if the bit
mask were set for less than 8 bits.
Firmware Release 5.0.11.4:
Resolved a DAP crash issue where a buffer in the Access Point is being written past the end with too much data
and corrupting the header of the following buffer.
Resolved an issue where the RBT-8400 CPU utilization increases due to a DHCP request packet looping issue
with the port- trunk functionality.
Resolved an ASSERT and exception DAP crash due to a corrupted link header when the DAP is rebooting.
This issue occurred when a packet entered the AP through the Ethernet MAC, and the Access Point stored this
packet in memory spot in which the operational code needed zeroed out.
Resolved an issue where the RBT-1002 Ethernet port would transition to half-duplex under heavy traffic load
(approximately 25 Mbps throughput).
Resolved an issue where the WebAAA login page would not resolve due to a certificate failure on a client using
the Vista OS and Microsoft Internet Explorer version 7. The workaround is for the client to open the Internet
Explorer browser as ―Administrator‖ and accept the WebAAA certificate.
Resolved an issue where a client using the Vista OS and Microsoft IE 7 failed to get the WebAAA login page
when the Common Name in the RBT switch Web certificate equals ‗*.<domain>.com‘.
Resolved an issue where the radio information was not displayed after issuing the ―show sessions‖ command.
Resolved an issue where the RBT-8400 locked-up due to a processor losing entries in the FDB, and over time,
the processor would lose the CPU entry, causing the lock-up.
Resolved an issue where DAP‘s were crashing due to Filter Database issues and causing ASSERT errors on
the RBT switch.
Resolved an issue where the message ―radar is no longer detected‖would continuously scroll across a console
screen when the DAPs auto-tuned the channel from a DFS channel to a non-DFS channel.
Resolved an issue when the RBT-8400 would show ‗Username: IP=127.0.0.1‘ after a switch reboot.
Resolved an issue where the auto-configuration setting changes for the B/G radio via WebView were not shown
in the active RBT switch configuration.
Resolved an issue when the DAP reboots with an ASSERT error when WMM-powersave is enabled.
Functionality description for an open issue where the DAP system uptime is changing, but the DAP has not
rebooted. DAP‘s that change from a low bias switch to a high bias switch are expected to reset without showing
a system log error.
Resolved an issue where the DAP would crash when countermeasures attempted to use an 11a radio to attack
a rogue on an 11b channel.
Resolved an issue where AP_Handshakes errors continuously scrolled across the console connection.
Resolved an issue with a DAP Exception when the DAP tried to tune 11a radio to an 11bg channel.
When configuring the Web portal and saving the default login page, remove everything between the quotes
in the Action value of the form tag in the HTML code.
Resolved an issue where the Access Point buffers were filling up with Rogue Detection messages.
Resolved an issue when a wireless client was previously connected to an SSID (WebAAA, last-resort), then
switched to a new bonded auth SSID, the machine auth phase was skipped.

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.