HP RF Manager Release 6.0.177
Release Notes
www.hp.com/networkingTable of Contents
Table of Contents
INTRODUCTION ... 2
CHANGES FROM RF MANAGER 6.0.154 THROUGH 6.0.177 ... 2
RF MANAGER 6.0 MAJOR RELEASE (6.0.147) ... 3
NEW FEATURES IN RF MANAGER 6.0 ... 3
ENHANCEMENTS IN RF MANAGER 6.0 ... 4
BUG FIXES IN RF MANAGER 6.0 ... 5
KNOWN ISSUES IN RF MANAGER 6.0 ... 5
TECHNICAL SUPPORT ... 5
Introduction
These Release Notes cover RF Manager 6.0 versions through build 177 (6.0.177).Changes from RF Manager Versions 6.0.154 through 6.0.177
Changes in RF Manager 6.0.177: Compatibility with MSM software v5.7.1.0, 5.7.1.1, 5.7.2.0, and 6.0.0.0. Changes in RF Manager 6.0.162: Compatibility with MSM software v5.7.0.3 and v5.7.0.4. A “set support” command issue involving the inability to send support data to a remote ftp server has been fixed. An 802.11n issue related to upgrading from RF Manager patch build 5.9.262 to RF Manager 6.0 has been fixed. Changes in RF Manager 6.0.157: Compatibility with MSM software v5.5.3.x. An HP 3Com sensor packaging issue has been fixed. Changes in RF Manager 6.0.154: Compatibility with MSM software v5.5.1.x and 5.5.2.x. An issue with APs on AP/Sensor combo devices not getting detected as connected to a wired network has been fixed.RF Manager Version 6.0 Major Release (6.0.147)
RF Manager Version 6.0 Major Release (6.0.147)
RF Manager consists of the RF Manager IDS/IPS Controller (J9521A), typically called “RF Manager” or “Server” in this document, and these RF Security Sensors: 802.11n MSM415 RF Security Sensor (J9522A) 802.11a/b/g MSM325 Access Point with Sensor (US J9369A/B, WW J9373A/B) and 802.11a/b/g MSM320 Access Point with Sensor License (US J9360A/B, WW J9364A/B and J9384A) 802.11a/b/g MSM335 Access Point with Sensor (US J9356A/B, WW J9357A/B) HP 3Com AirProtect Wireless Intrusion Prevention System IEEE 802.11a/b/g/n Sensor SS‐300‐AT HP 3Com AirProtect Sensor 5750 To download HP 3Com sensor documentation, go to www.hp.com/support/manuals, and search for your HP 3Com sensor as follows: For 3Com AirProtect Wireless Intrusion Prevention System IEEE 802.11a/b/g/n Sensor SS‐300‐AT, search for Sensor SS‐300‐AT, and look for its configuration guide For 3Com AirProtect Sensor 5750, in Product Number or Name Search search for Sensor 5750, and look for its configuration guideNew Features in Version 6.0
1) New Security Dashboard Trending and analysis of security events by location as well as by threat categories Security vulnerability status displayed on the location tree (for each location) Customizable device summary view for APs, Clients, and Sensors as well as for Quarantine statistics 2) Forensic Analysis for Wireless Incidents Basic Forensics – Enhanced devices details (RSSI information, association history, bandwidth usage statistics, and so on) Advanced Forensic Analysis (requires software license) – Easy to use two‐click forensic analysis for common wireless incidents AP Incidents – Rogue APs, Mis‐configured APs, Honeypot APs, Banned APs, and DoS attacks against authorized APs Client Incidents – Unauthorized Associations, Mis‐associations, Bridging Clients, Banned Clients, and Ad‐hoc Networks In‐depth Analysis – Activity and associations, Prevention activities, and Administrator User actions 3) WLAN Performance management and troubleshooting (requires software license) Proactive management of WLAN performance issues – define your WLAN performance requirements and proactively monitor for any issues New dashboard for WLAN performance analysis (Trending and analysis charts for various WLAN performance issues, top APs and Clients by events, and so on) Fifteen new events for WLAN performance issues (Bandwidth, Coverage, Configuration, and Interference) WLAN performance analysis reports – RF Audit, Bandwidth Audit, and Configuration Audit Reports The Charts dashboard has been discontinuedEnhancements in Version 6.0 4) IPv6 Support Ability to deploy and manage HP RF Manager system in an IPv6 network; that is; you can assign IPv6 addresses to HP RF Manager Server and Sensors and manage them in an IPv6 network Event forwarding to external servers (for example: SNMP) in an IPv6 network 5) Support for 3Com AirProtect Sensors The HP RF Manager allows HP 3Com AirProtect Sensors to connect to the Server Upgrade of HP 3Com AirProtect Sensors from previous releases. The supported versions of HP AirProtect Sensor that can be upgraded are (5.1.116, 5.1.119, 5.9.x) 6) HP MSM Controller Integration Integration with HP MSM Controller allows the HP RF Manager to fetch information about Synchronized APs. The HP RF Manager treats these as Authorized APs
Enhancements in Version 6.0
1) WLAN attacks: detection and prevention enhancements Client Bridging: ability to detect and prevent authorized (that is; managed) Clients bridging Wi‐Fi and wired networks Does not require any agent on the users’ laptops Allows detection and prevention for both authorized and unauthorized users if they bridge between your wired network and a neighbor’s WLAN network WPA attacks: detect and notify regarding latest WPA attacks 2) Various UI and Usability Improvements Enhanced Location and RF Heat Map view – Easy to use; you can drag and drop devices while viewing the RF heat map New – Printable view of RF Heat Maps Customizable view for “Events” and “Devices” screens – Customizable view as well as persistent sort and filter options Better location tracking of unassociated Clients (as compared to previous releases) Non‐English SSID support (multilingual SSIDs supported) Time on the user action logs are now in the time zone of the user downloading the logs (as against in UTC) 3) Support for increased number of Sensors RF Manager v6.0 supports an increase of 50 Sensors thus raising the limit from 200 maximum Sensors supported per appliance to 250 4) Location based policy feature is no longer controlled by license This change enables the location based policy feature irrespective of whether customer has purchased the license for it or notBug Fixes in Version 6.0
Bug Fixes in Version 6.0
Sorting icons appeared garbled while viewing HTML reports in Mozilla browsers. Information of monitored networks as seen in the UI and CLI was not consistent. HP 3Com AirProtect Sensor 5750 (in ND/SNDC mode) crash and reboot on certain operations (for example; get vlan config, get logs). Incorrect use of engine‐id while sending traps in SNMPv3. Garbled information in SNMP traps when there are more than two participating devices in an event. The change in network status of APs was not recorded in some cases. While setting SSID templates, the system did not allow selection of CCMP as the encryption type when the Authentication type chosen was PSK. Scheduled reports continued to be delivered to deleted users.Known Issues in Version 6.0
Known Issue Workaround After upgrading to MSM firmware v6.0.0.0, the MSM320 and MSM325 working on autonomous mode may present instability when a radio or radios are setup to work in Sensor mode. Downgrade to 5.7.x or previous firmware version if Sensor mode is desired. Location tracking of unassociated Clients is not as accurate as active Clients. Location tracking is dependent upon the packets originating from the device. The location tracking accuracy will improve once the device becomes active. Internet Connection Sharing (ICS) using encrypted communications is not detected (and hence not prevented). None If a Sensor is configured with an IPv6 address in non RFC compliant format (some shorter sequence of zeros is compressed instead of the longest sequence of zeros), it would be accepted but would appear as ʺAutoʺ instead of ʺStaticʺ. Please re‐enter the IPv6 address in the RFC compliant format. Link speed view in Live RF maps do not show link rates higher than 54Mbps. None SNMPv3 Engine ID needs to be reconfigured after upgrade to 6.0. None FireFox 3.6 with JRE versions less than 14 has compatibilityissues. HP RF Manager UI will not open. Kindly use JRE version equal to greater than 14 with FireFox 3.6.
FireFox 3.6 with JRE version greater than or equal to 19 will give a security warning popup. Click No on the Security Warning Popup dialog for the application to proceed. In PDF reports, unusually‐long SSIDs (more than 16 characters), will not display correctly. Additional characters beyond the first 16, will spill over into the column to the right. You can avoid this by using SSIDs of 16 characters or less.
