Enterasys Enterasys RoamAbout RBT-1002-EU How to use

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 1 of 28
F0615-O
50 Minuteman Road
Andover, MA 01810 (USA)
Tel: [phone]
Enterasys RoamAbout®Wireless Switch 8xx0 Release
Firmware Version 7.0.7.3
January 21, 2009
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; 3) the RBT-8400, which has the ability to control 40/80/120 access points; and 4) the new
RBT-8500 which can control 32/64/96/128 access points. The RoamAbout Switch Manager (RASM) can manage
all of these devices.
The 7.0.7.3 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: The following table provides the access points and features supported by the Wireless Switch 8xx0
Firmware Version 7.0.7.3
Access Point
Supported in
7.0.7.3
Hitless Failover
Direct Path
Forwarding
Wireless Mesh
Support
RBT3K-AG
Yes
No
No
No
RBT-1002
Yes
No
No
No
RBT-1002-EU
Yes
No
No
No
RBT-1602
Yes
Yes
No
No
RBT-4102
Yes
No
No
No
RBT-4102-EU
Yes
No
No
No
RBT-4102-BG
Yes
No
No
No
TRPZ-MP-372-CN
Yes
Yes
No
No
TRPZ-MP-372-IL
Yes
Yes
No
No
TRPZ-MP-422
Yes
Yes
Yes
Yes
TRPZ-MP-432
Yes
Yes
Yes
Yes (802.11a/b/g only)
TRPZ-MP-620
Yes
Yes
Yes
Yes
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.5.1 or greater of RAS firmware, up to 25 ACEs in an ACL
policy can be applied to a user of that AP. Please refer to the Firmware Changes and Enhancements
section for more information.

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 2 of 28
F0615-O
NOTE: To avoid conflicts with internal RAS VLAN numbering schemes, it is strongly advised to use VLAN IDs
less than 3520 on RBT-8xxx systems that are upgrading from MSS version 6.0 to 7.0. Failure to do so
will result in a loss of configuration data.
NOTE: RoamAbout Wireless Switch Firmware version 5.0.9.2 and greater supports the RBT-8210, the small
form factor switch that replaces the larger RBT-8200. The RBT-8210 uses the RBT-8200 firmware and
commands. The RBT-8210 prompt displays 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. Please refer to the Upgrading the RBT8xxx switches
section of this release note for more information.
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.2.2.4 Release Notes.
NOTE: RoamAbout Wireless Switch Firmware version 6.0.4.2 and greater replaces the term „DAP‟ with „AP‟.
NOTE: Beginning with the calendar year 2007, please be aware that the United States Daylight saving time
period begins on the second Sunday in March, and ends on the first Sunday in November. Refer to the
“Changing Timezone Properties” section in the “Configuring RoamAbout Switch System and
Administrative Parameters” chapter of the RoamAbout Switch Manager Interface Reference document
for detailed setup instructions.
FIRMWARE SPECIFICATION:
Status
Version No.
Type
Release Date
Current Release
7.0.7.3
Customer Maintenance
January 2009
Previous Release
7.0.5.6
Customer Maintenance
October 2008
Previous Release
7.0.4.3
Customer Maintenance
August, 2008
Previous Release
7.0.3.7
Customer Maintenance
June, 2008
Previous Release
6.0.7.2
Customer Maintenance
April, 2008
Previous Release
6.0.6.1
Customer Maintenance
March, 2008
Previous Release
6.0.5.1
Customer, added
RBT-8500 support
December 2007
Previous 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
October 2006

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 3 of 28
F0615-O
Status
Version No.
Type
Release Date
TRPZ-MP-620 support
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 TechTip on page 22for the channel availability information.
HARDWARE COMPATIBILITY:
Switches:
- RBT-8100, RBT-8110, RBT-8200, RBT-8210, RBT-8400, RBT-8500, and TRPZ-MXR-2.
Access Points:
- See the Supported Access Point Table on page 1 for detailed information for version 7.0.7.3
NETWORK MANAGEMENT SOFTWARE SUPPORT:
NMS Platform
Version No.
Module No.
RoamAbout Switch Manager 50 Access Point User License
7.0.7.3
RBT-NMS-50
RoamAbout Switch Manager 200 Access Point User License
7.0.7.3
RBT-NMS-200
RoamAbout Switch Manager unlimited User License
7.0.7.3
RBT-NMS-UNL
RoamAbout RF Planning Tool
7.0.7.3
RBT-RFPLAN
SmartPass Guest Access
7.0.7.3
TRPZ-SP
TRPZ-SP-ENT
RBT-8400 Platform
Version No.
Module No.
RBT-8400 40 Additional Access Point Upgrade License
7.0.7.3
RBT-8400-40
RBT-8400 80 Additional Access Point Upgrade License
7.0.7.3
RBT-8400-80
RBT-82x0 Platform
Version No.
Module No.
RBT-82x0 24 Additional Access Point Upgrade License
7.0.7.3
RBT-8200-24
RBT-82x0 48 Additional Access Point Upgrade License
7.0.7.3
RBT-8200-48
RBT-8500 Platform
Version No.
Module No.
RBT-8500 32 Additional Access Point Upgrade License
7.0.7.3
RBT-8500-32

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 4 of 28
F0615-O
SUPPORTED FUNCTIONALITY:
Please refer to the following documents available at http://secure.enterasys.com/support/manuals for more details
on new 7.0 enhancements and overall functionality:
RoamAbout Switch Manager 7.0 Configuration Guide
RoamAbout Mobility System Software 7.0 Command Reference Guide
RoamAbout Switch Manager 7.0 Management Guide
RoamAbout Mobility System Software 7.0 Feature Guide
RoamAbout Switch Manager 7.0 Feature Guide
RoamAbout Mobility System Software 7.0 Configuration Guide
RoamAbout Switch Manager 7.0 Planning Guide
RoamAbout Mobility System Software 7.0 Quick Start Guide
RoamAbout Switch Manager 7.0 Quick Start Guide
New Product Features in Release 7.0
Enterasys Virtual Controller Cluster
TRPZ-MP-432 to support 802.11n
Layer 2 ACL Enhancements
Snoop Filter Enhancements
Bandwidth Management by User and SSID
Dynamic RADIUS Extensions
MAC User Range Authentication
MAC Authentication Request Format
Additional User AAA Attributes for User Name and
Simultaneous Logins
Group-based Authentication and Authorization
Location Policy Enhancements
RADIUS Ping
RF Enhancements
Mesh Enhancements
NOTES:
Local switching is only available in RAS 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.
IGMP snooping is not supported with local switching.
Locally Switched AP‘s can support a total of 25 ACL rules, including both inbound and outbound
ACLs.
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.

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 5 of 28
F0615-O
Existing 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
RAS Seed Redundancy
Password Management
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 AP‘s
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
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.

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 6 of 28
F0615-O
UPGRADING THE RBT-8XX0 SWITCHES FROM PREVIOUS 4.0.X VERSIONS:
Minimum RAS Requirements for Upgrade
Product
Minimum RAS version required
Recommended Upgrade Path
RBT-8100
4.0.4.0
6.0.7.2 7.0.7.x
RBT-8200
4.1.4.0
6.0.7.2 7.0.7.x
RBT-8110, RBT-8210
4.2.5.1
6.0.7.2 7.0.7.x
RBT-8400
4.0.16.0
6.0.7.2 7.0.7.x
RBT-8500
6.0.5.1
6.0.7.2 7.0.7.x
Note: You must upgrade to RAS Version 5.0 or later before upgrading to RAS Version 7.0.
Preparing the RAS 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 RAS 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 RAS versions may not be converted
correctly.
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.

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 7 of 28
F0615-O
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 a RAS and reboot the software, type the following command:
RBT-8xx0# reset system [force]
After resetting the RAS, the switch boots using the new image. The RAS 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.
Upgrade Scenario:
To upgrade an RBT-8xx0 switch from one RAS version to another, type commands such as the following.
Note: This upgrade scenario uses the firmware image file 6.0.7.2 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]/R2060701.REL boot1:R2060701.REL success: received 11257345 bytes
in 16.230 seconds [693613 bytes/sec]
RBT-8200# set boot partition boot1 success: Boot partition set to boot1.
RBT-8200# show boot
Configured boot version: 6.0.7.2.0
Configured boot image: boot1: R2060701.rel
Configured boot configuration: file:configuration
Backup boot configuration: file:backup
Booted version: 6.0.6.1.0
Booted image: boot0:R2060601.REL
Booted configuration: file:configuration
Product model: RBT-8200
Upgrading an Individual Switch Using the RoamAbout Switch Manager (RASM)

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 8 of 28
F0615-O
Please refer to the chapter ―Managing with RoamAbout Switch Manager‖, section ―Distributing System
Images‖ in the RoamAbout Switch Manager Management Guide when upgrading the RBT-8xx0 switch to the
released version.
SYSTEM PARAMETER SUPPORT:
RoamAbout System Parameters:
Parameter:
Supported Value:
RASs in a single Network Domain
500
RASs in a single Mobility Domain
32
Roaming VLANs per RAS
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
APs per RAS
RBT-81x0: 60 configured, 24 active
RBT-82x0: 180 configured, 72 active
RBT-8400: 300 configured, 120 active
RBT-8500: 320 configured, 128 active
SSIDs per radio
8
Minimum link speed within a Mobility Domain
128 Kbps
Network Parameters:
Parameter:
Supported Value:
Forwarding database entries
RBT-81x0: 8192
RBT-82x0: 8192
RBT-8400: 16383
RBT-8500: 8192
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
RBT-8500: 2308
ACEs per ACL:
RBT-81x0: 25
RBT-82x0: 25
RBT-8400: 267
RBT-8500: 267
Locations Policies per switch:
All models: 1
The Location Policy can have up to 150 rules.
ACL rules (ACEs) with Local Switching (Direct Path
Forwarding) enabled: 25
IGMP Streams
500
Note: Replications of a stream on multiple VLANs count as
separate streams on each VLAN.

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 9 of 28
F0615-O
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
RBT-8500: 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
RBT-8500: 8
Telnet client sessions (client for remote login)
RBT-81x0: 8
RBT-82x0: 8
RBT-8400: 8
RBT-8500: 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
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
RBT-8500: 3200
AAA users configured in local user database
RBT-81x0: 999
RBT-82x0: 999
RBT-8400: 999
RBT-8500: 999

CUSTOMER RELEASE NOTES
1/21/09P/N: 9038177-27 Subject to Change Without Notice Page: 10 of 28
F0615-O
FIRMWARE CHANGES AND ENHANCEMENTS:
Firmware Release 7.0.7.3:
Resolved an issue where static WEP keys did not work for some service profiles.
Resolved an SNMP error that caused an AP to become unresponsive.
Resolved an issue where the RBT-8500 became unresponsive on the network.
Resolved an issue where a large number of user sessions caused the Web portal login page to become
inaccessible.
Resolved an issue where merging configurations between the primary and secondary seed caused the RASs to
become unresponsive.
Resolved an issue where using a question mark symbol in a Web AAA page URL caused the page to not
display properly.
Resolved an issue where the TCP connection to the RAS did not close immediately after sending a 403 error in
response to a request from a Skype client.
Resolved an issue where a corrupted cluster configuration update caused the RAS to become unresponsive.
Resolved an issue where configuring multiple user groups and using local authentication for web logins caused
the RAS to become unresponsive.
Resolved an issue where MSS did not report the maximum transmit power on any particular channel as a proxy
for the maximum power allowed by the regulatory domain.
Resolved an issue where a large number of location policies caused the cluster configuration to be
unresponsive.
Resolved an issue where the show network verbose command displayed the incorrect output in the CLI.
Resolved an issue where upgrading to a later version of MSS caused the RAS to become unresponsive.
Resolved an issue where a corrupted control packet caused the AP to become unresponsive.
Resolved an issue where an invalid IGMP message caused the RAS to become unresponsive.
Resolved a problem where some 802.11n wireless adapters experienced packet loss on wireless services
with the SVP enabled. Existed only on the TRPZ-MP-432.
Resolved a TCP buffer issue that caused a RAS within a Mobility Domain to crash.
Resolved a corrupt control packet issue causing APs to become unresponsive and reset.
Resolved an issue that, when using MacOS, an unsupported protocol option would cause SSH admin
connections to fail.
Resolved an issue where Auto-tune‘s lower boundary was not implemented for AP power tuning.
Resolved an issue where an invalid AP configuration caused the RAS to become unresponsive.
Resolved an issue where a large number of EAP offload sessions caused the RAS to crash.
Resolved an issue where, in certain configurations, the RAS incorrectly reports channel configuration.
Firmware Release 7.0.5.6:
Resolved an error message: ―network: radio_decode_data: read A-MSDU subframe snap header failed‖
occurred on the network.
Resolved an issue that caused MIC errors on the network when configuring WPA TKIP.
Resolved an RBT-8500 memory corruption at cfg_memory.c error message that caused network problems.
Resolved an issue where the RBT-8xxx sent too many access requests to the RADIUS server after configuring
RADIUS to authenticate users with EAP-TLS, or EAP-PEAP.
Resolved an issue where SSIDs using "#" as part of the name were not accepted in the configuration.
Resolved an issue with Internet Explorer and WebView where the date format was displayed incorrectly.
Resolved an issue reloading a configuration with cluster mode enabled prevented RASM from determining the
active seed.
Resolved an issue with clients that could not re-associate without first authenticating on the network.
CAPWAP data plane UDP port changed from 5001 to 5247.
Resolved an issue when using telnet over a WAN link adversely affected the telnet session.