rfplan_2_1_0_4_rn.pdf

Aruba RF Plan Release 2.1 1 Release Notes

RF Plan Release 2.1Release Notes

This document describes the features and issues pertinent to the Java-based RF Plan Release 2.1.0.4 in the following topics:

Requirements on page 2 New Features on page 2 Issues and Limitations Fixed in This Release on page 3 Issues and Limitations Fixed in Release 2.1.0.0 on page 4 Issues and Limitations Fixed in Release 2.0.1.1 on page 4 Issues and Limitations Fixed in Release 2.0.0.0 on page 4 Known Issues and Limitation of This Release on page 5 Documents in This Release on page 5 For More Information on page 6

2 Aruba RF Plan Release 2.1 0510365-02Release Notes August 2007

RequirementsThe RF Plan application requires Java Runtime Environment (JRE) 1.5.0. This will be installed automatically as part of the RF Plan software installation.

New FeaturesThis section describes the new features for the Java-based RF Plan application.

No new features were added with release 2.1.

New Features in Release 2.0

Support for Negative Floor IDsRelease 2.0 adds the ability to configure negative floor IDs for individual floors in a building. When adding a new floor or modifying an existing floor, you can configure it with a negative integer to specify a basement or some other underground floor where you do not need or want to deploy APs. You must be running RF Plan 2.0 and your controller must be running ArubaOS 3.0 or later.

PNG File FormatsThis release supports importing .png files as background images for a floor.

AutoCAD ImportWhen you import AutoCAD .dwg, .dxf, .dwf files, RF Plan now prompts you for the converted image size. You can specify 1024 x1024, 2048 x 2048, and 4096 x 4096. The image size was automatically converted in RF Plan 1.0.2. For more information, see Managing Images in the RF Plan Installation and User Guide.

Support for Fully-Qualified Location Names Release 2.0 supports the AP name as a fully-qualified location name (FQLN) in the form APname.floor.building.campus (the APname portion of the FQLN must be unique). You must use this AP name form for controllers running ArubaOS 3.0 or later.

Exported Application FormatsWhen exporting RF Plan application data, the following updated formats are available:

z RF Live Format (version 2.x)Export RF Plan application data to use in the RF Live platform available on the Mobility Management System release 2.0. This format supports the AP name in the FQLN form.

Aruba RF Plan Release 2.1 3Release Notes

z Controller WebUI Format (version 3.0)Export RF Plan application data to use in the ArubaOS WebUI RF Plan available on controllers running ArubaOS 3.0 or later. This format supports the AP name in the FQLN form.

z Controller WebUI Format (Legacy)Export RF Plan application data to use in the ArubaOS WebUI RF Plan available on controllers running ArubaOS 2.5. This format supports floors and AP names with only positive floor IDs. Negative floor ID information is not exported. This format does not support the AP name in the FQLN form; the AP location name is in the form buildingID.floorID.apID.

For more information about these and other available formats, see the RF Plan Installation and User Guide.

Searchable Online HelpThe previous version of RF Plan did not have a searchable online help. In version 2.0, you can now search for a term or phrase in the online help.

Enhanced Image OperationsWhen selecting the crop tools, floor alignment tools, or floor computation tools, you enter an enhanced mode of operation. A status bar displays the mode you are in and provides real-time information about actions you are performing. To exit any of these modes without saving your changes, press [ESC].

For more information, see Setting Backgrounds in the RF Plan Installation and User Guide.

Issues and Limitations Fixed in This ReleaseThe following issues and limitations have been fixed in release 2.1.0.4:

Additions/corrections have been made to the country code lists: z Macau and Pakistan added to country code list (21563, 22008)z Allowed channels are 149-161 for Korea (21413)

The initialize APs function did not work correctly when the 802.11 b/g data rate is set to 5.5 Mbps. (21551)

Due to changes to the FCC rules for Dynamic Frequency Selection (DFS), channels 52, 56, 60, and 64 cannot be used for the US or Canadian regulatory domains. These settings have not been removed in the MMS, but if your controller is configured for the US or Canada, these channels will be ignored, and the AP will be automatically migrated to a valid channel. It is recommended that you disable these channels in the configuration. (20210)


Issues and Limitations Fixed in Release 2.1.0.0The following issues and limitations have been fixed in release 2.1.0.0:

The Floor Level number has been added to the display of the floor name in the left-hand tree view when a building node is expanded in the tree to display its floors. (18678)

The floor number is shown in brackets after the floor name, for example:Basement [-1]Ground [0]Floor 1 [1]

Importing a plan from RF Live to RF Plan will sometimes fail with an error. This has been fixed. (18656)


RF Plan could time out when drawing the heatmap. This has been fixed. (18838)


After import of an AutoCAD file, if the user accepts the embedded building dimensions, the suggested number of APs and AMs automatically updates. (12104, 13055)

When exporting a plan to an Aruba Mobility Controller, the conversion process of AutoCAD files to JPEG images has been shortened. (12804)

An Invalid Image Format error message or a Java exception message no longer displays when using two-dimensional.dxf files. (11569)

Plans with a large number of campuses no longer take three to four minutes to save to disk. (11747, 12624)

RF Plan no longer places APs on different floors than the embedded Mobility Controller version of the planning tool when mixed radios, 802.11a and 802.11g, are in use. (13035)

The custom overlap feature is now available for AP planning. Only the pre-defined low, medium, high overlap factors were available. (13197)

Predicted coverage maps are now displayed using bold colors. (13724)

Aruba RF Plan Release 2.1 5Release Notes

The number of APs displayed in the AP Count window now matches the number of APs actually shown. (13730)

The hide function now works properly on all floors after running the AP/AM optimization function. (13751)

When attempting to view predicted coverage, predicted coverage now displays when AP Coverage or Layered Data Rates is selected. (13867)

Known Issues and Limitation of This ReleaseThe following are issues for Release 2.0. Where bug IDs are applicable, they are included in the description of the issue.

Some AutoCAD files may not load correctly. If this occurs, you may see the following message: ax2007.exe has encountered a problem and needs to be closed. (16555)

When importing plan data, some images may be read twice. (18270)

Documents in This ReleaseThe following documents are included with this RF Plan release:

RF Plan Release Notes RF Plan Installation and User GuideThe documentation library is updated continuously. You can download the latest version of any of these documents from the Aruba support site:

https://support.arubanetworks.com


For More InformationTo contact Aruba Networks, Inc., refer to the information below:

Web Site

Main Site http://www.arubanetworks.com Support Site http://www.arubanetworks.com/supp

ort

Software Licensing Site https://licensing.arubanetworks.com Wireless Security Incident

Response Team (WSIRT)http://www.arubanetworks.com/support/wsirt

Support Email [email protected] WSIRT Email

Please email details of any security problem found in an Aruba product.

[email protected]

Telephone Numbers

Aruba Corporate +1 (408) 227-4500 FAX +1 (408) 227-4550 Support

z United States 800-WI-FI-LAN (800-943-4526)z France +33 (0) 1 70 72 55 59z United Kingdom +44 (0) 20 7127 5989z Germany +49 (0) 69 38 09 77 22 8z All other countries +1 (408) 754-1200

RequirementsNew FeaturesNew Features in Release 2.0

Issues and Limitations Fixed in This ReleaseIssues and Limitations Fixed in Release 2.1.0.0Issues and Limitations Fixed in Release 2.0.1.1Issues and Limitations Fixed in Release 2.0.0.0Known Issues and Limitation of This ReleaseDocuments in This ReleaseFor More Information