Résumé du contenu de la page N° 1
50 Minuteman Road
Andover, MA 01810 (USA)
Tel: (978) 684-1000
CUSTOMER RELEASE NOTES
®
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 abil
Résumé du contenu de la page N° 2
CUSTOMER RELEASE NOTES 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.
Résumé du contenu de la page N° 3
CUSTOMER RELEASE NOTES 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
Résumé du contenu de la page N° 4
CUSTOMER RELEASE NOTES 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 Mobil
Résumé du contenu de la page N° 5
CUSTOMER RELEASE NOTES Existing Product Features RF Load Balancing Mesh Services Local Switching – also known as Direct Path Wireless Bridging Forwarding 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 las
Résumé du contenu de la page N° 6
CUSTOMER RELEASE NOTES 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 RA
Résumé du contenu de la page N° 7
CUSTOMER RELEASE NOTES 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 f
Résumé du contenu de la page N° 8
CUSTOMER RELEASE NOTES 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 VLAN
Résumé du contenu de la page N° 9
CUSTOMER RELEASE NOTES Management Parameters: Parameter: Supported Value: Maximum instances of the RoamAbout 3 Software Management system simultaneously managing a network 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 clie
Résumé du contenu de la page N° 10
CUSTOMER RELEASE NOTES 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
Résumé du contenu de la page N° 11
CUSTOMER RELEASE NOTES Firmware Release 7.0.5.6: Resolved an issue when using the active-scan feature triggered packet loss on legacy MPs/ RASs with older Intel wireless adaptors. Firmware Release 7.0.4.3: Resolved an issue where reloading a configuration with cluster mode enabled prevented RASM from determining the active seed. CAPWAP data plane UDP port changed from 5001 to 5247. Resolved an issue where the active-scan feature triggered packet loss on legacy APs with older In
Résumé du contenu de la page N° 12
CUSTOMER RELEASE NOTES Firmware Release 6.0.5.1: The 6.0.5.1 release now supports 25 ACL rules (ACEs) per ACL, total of inbound and outbound, to be mapped to the user if the AP has Direct Path Forwarding (Local Switching) enabled. There can be more than one ACL, with 25 ACEs, applied to multiple users on the AP. If an ACL with 26 or more rules is mapped to the user with Local Switching enabled, the users in the network will not connect or authenticate to that wireless network. Entera
Résumé du contenu de la page N° 13
CUSTOMER RELEASE NOTES Firmware Release 6.0.4.2: 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 RAS 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. Firmware Release 5.0.12.2: Added support for the TRPZ-MP-422 Ac
Résumé du contenu de la page N° 14
CUSTOMER RELEASE NOTES Firmware Release 5.0.11.4: 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. Resolv
Résumé du contenu de la page N° 15
CUSTOMER RELEASE NOTES Firmware Release 5.0.9.2: Added support for the RBT-8210. This RAS, 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
Résumé du contenu de la page N° 16
CUSTOMER RELEASE NOTES Firmware Release 4.2.5.1: Resolved an issue where ―set dap‖ commands would not return a ―succeed: changes accepted‖ notification. Resolved an issue where a switch reset with multiple core files after a system upgrade. Core resets were attributed to the enabling of rogue detection in the fabric. Firmware Release 4.1.11.0: Added support for the RBT-4102 North American Access Point. Resolved an issue where RBT-1602s would reset every 18 hours and report a fing
Résumé du contenu de la page N° 17
CUSTOMER RELEASE NOTES Firmware Release 4.0.21.0: Resolved an issue where ACLs were not properly assigned to users due to the incorrect parsing of the Enterasys filter ID string (Enterasys:version=1:policy=) returned from a RADIUS server. The default MAC authentication RADIUS password has been changed from ‗nopassword‘ to ‗NOPASSWORD‘. Firmware Release 4.0.20.0: Added support for the RBT-1602 Access Point. Increased the limit of local mac authenticated users from 75
Résumé du contenu de la page N° 18
CUSTOMER RELEASE NOTES KNOWN RESTRICTIONS AND LIMITATIONS: Firmware Release 7.0.7.3: 802.11n adapter incompatibility with Spectralink Voice Protocol (SVP) enabled service profiles. Description — Some 802.11n wireless adapters may experience packet loss on wireless services with the Spectralink Voice Protocol enabled. This problem only exists when using the TRPZ-MP-432 with frame aggregation enabled. Workaround — When using SVP on the TRPZ-MP-432 disable frame aggregation. The
Résumé du contenu de la page N° 19
CUSTOMER RELEASE NOTES Firmware Release 7.0.5.6: 802.11n adapter incompatibility with Spectralink Voice Protocol (SVP) enabled service profiles. Description — Some 802.11n wireless adapters may experience packet loss on wireless services with the Spectralink Voice Protocol enabled. This problem only exists when using the TRPZ-MP-432 with frame aggregation enabled. Workaround — When using SVP on the TRPZ-MP-432 disable frame aggregation. The aggregate throughput exceeds the bandwi
Résumé du contenu de la page N° 20
CUSTOMER RELEASE NOTES Firmware Release 7.0.4.3: Using the auto-ap feature does not allow load-balancing on individual radios. Description — When using the auto-ap feature, it is not possible to set all of the AP attributes. Per AP load-balancing control is not supported on auto-ap. The system global settings for load-balancing apply to all auto-aps. Workaround — If you must configure a load-balance group for a specific AP, configure the AP as a regular AP. Using telnet over a WAN
