IMC Wireless Service Manager 7.1 (E0303P10) Copyright (c) 2015 Hewlett-Packard Development Company, L.P. and its licensors.

Transcription

1 IMC Wireless Service Manager 7.1 (E0303P10) Copyright (c) 2015 Hewlett-Packard Development Company, L.P. and its licensors. Table of Contents 1. What's New in this Release 2. Problems Fixed in this Release 3. WSM Software Distribution Contents 4. Installation Prerequisites 5. Client Prerequisites 6. Upgrade 7. Removing WSM 8. Running the Deployment Monitoring Agent 9. Starting IMC 10. Logging in to IMC through a Web Browser 11. Monitoring the Server 12. Distributed Deployment 13. Platform Specific Issues 14. Port Usage 15. Memory Allocation 16. Known Problems 17. Feature Support Matrix 18. Report Support Terminology AC Fat AP Fit AP Access Controller Autonomous Access Points Controlled Access Points What's New in this Release The version IMC WSM 7.1 (E0303P10) can be upgraded from IMC WSM 7.1 (E0303), IMC WSM 7.1 (E0303P01), IMC WSM 7.1 (E0303P04) and IMC WSM 7.1 (E0303P08). Features released in IMC WSM 7.1 (E0303P10) None. Features released in IMC WSM 7.1 (E0303P08)

2 Support for WT and WTU license control. This Feature is configurable under Service >> WLAN Manager >> Resource Management >> Fit APs. Supports Location Aware for wireless location. This Feature is configurable under Service >> WLAN Manager >> Wireless Topology >> Locating Management. Supports RESTful APIs for Location Aware. This Feature is configurable under Supports alerts for the client number of AC. This Feature is configurable under Service >> WLAN Manager >> Resource Management >> ACs. Supports Top5 ACs by Clients widget in Home page. This Feature is configurable under Home >> Widgets. AP license policy changed. When the number of APs in a wireless network exceeds the licensed maximum number, IMC displays the licensed maximum number. Services are not affected. This Feature is configurable under Service >> WLAN Manager. WIPS supports detecting unassociated clients. This Feature is configurable under Service >> WLAN Manager >> WIPS Management >> Clients Detected. The Full Screen Monitor function is added on the Overview page. This Feature is configurable under Service >> WLAN Manager >> Overview. Add APs to GIS view. This Feature is configurable under Service >> WLAN Manager >> View Management >> GIS View. A real AP can replace the virtual Fit AP with the same name in Network Planning. This Feature is configurable under Service >> WLAN Manager >> Wireless Topology >> Location View. Export Fit AP information generated in the location view in network planning to a BOM file. This Feature is configurable under Service >> WLAN Manager >> Wireless Topology >> Location View. Display client quantity in Star or Number mode in the location view. This Feature is configurable under Service >> WLAN Manager >> Wireless Topology >> Location View. Supports PCI Compliancy report. This Feature is configurable under Report >> Report Template List. Features released in IMC WSM 7.1 (E0303P04) Supports fast deploying WLAN for MSM wireless devices. This Feature is configurable under Service >> WLAN Manager >> Fast Deploy WLAN. Supports configuration for static blacklist in WIDS. This Feature is configurable under Service >> WLAN Manager >> WIDS Management >> WIDS Config. SSID encryption key change by imc. This Feature is configurable under Alarm >> Security Control Center >> Security Control Policy. The Comware-based fit AP details page displays association failure information. This Feature is configurable under Service >> WLAN Manager >> Fit APs. Features released in IMC WSM 7.1 (E0303P01)

3 None. Features released in IMC WSM 7.1 (E0303) Supports RESTful APIs. This Feature is configurable under Supports locating clients by X-Share antenna for comware-based wireless devices. This Feature is configurable under Service >> WLAN Manager >> Wireless Topology >> Location View. Supports for new dashboard widgets (AP Bandwidth Trend, Fit AP Model Statistics, Rogue AP, Rogue Client, Clients Statistics and Reasons for Association Failures). This Feature is configurable under My Favorites >> Dashboard >> Configuration. Supports WSM applications in the desktop version. This Feature is configurable under Web Desktop Management. Supports converged topology. This Feature is configurable under Resource >> Network Topology >> Converged Topology. Supports fast deploying WLAN for comware-based wireless devices. This Feature is configurable under Service >> WLAN Manager >> Fast Deploy WLAN. Supports saving network planning reports on the IMC server. This Feature is configurable under Service >> WLAN Manager >> Wireless Topology >> Location View. Supports WIPS for comware-based wireless devices. This Feature is configurable under Service >> WLAN Manager >> WIPS Management. Supports OpenStreetMap in GIS view. This Feature is configurable under Service >> WLAN Manager >> View Management >> GIS View. Problems Fixed in this Release IMC WSM 7.1 (E0303P10) fixes the following problems, including all bugs fixed after IMC WSM 7.1 (E0303). Resolved Problems in IMC WSM 7.1 (E0303P10) 1. The customized columns for clients cannot be exported. 2. The MSM or Cisco tab has no data when the IMC platform includes only MSM or Cisco devices. 3. The cipher suite options do not include WEP128 when you add a service policy template. 4. The 2D icons are not displayed when you change the icon type to 2D on the topology. 5. The page does not display the operation result message when you click Add to Permit List or Add to Attack List in the operation column on a rogue AP details page.

4 Resolved Problems in IMC WSM 7.1 (E0303P08) 1. When you configure the 802.1X authentication mode for a wireless logical interface, the user online handshake feature cannot be disabled. 2. The Client Detail Report does not display the names of the clients that had been associated with APs. 3. After a user saves the added notes and then exits the converged topology, the links between APs and PoE switches are not displayed when the user opens the converged topology again. 4. No link is displayed between the AC and an AP when you add the AP first in the Converged Topology and then in the Wireless Custom View. 5. When you add a rectangular obstacle in location view, an extra area appears beside the obstacle. 6. In GIS view, information changes cannot be saved for an AP or a location view that has been added to GIS. 7. A location view topology page cannot be opened if you click the location view link from the detailed rogue AP information page. 8. An error page appears when you change the icon for a location view that has been added to GIS in GIS view. 9. Select a client associated with the fat AP from the client list to locate the client, and the client cannot be located in the location view where the fat AP is located. 10. View the execution result after an energy policy is successfully executed. The failure reason for the policy execution result is Unknown. 11. The subtype for a PCI report is incorrect. 12. The topology in the custom view fails to be opened when multiple users add Fit APs associated with different ACs to the custom view at the same time. 13. In the Client Summary Report, the total online duration for a location view is the duration sum for all location views when the system has multiple location views. 14. In the location view, move the position of an obstacle, save the topology, and reload the topology. The obstacle is still in the position before it is moved. 15. The OpenStreet map can be used in GIS when IMC is accessed through HTTPS. 16. The status of the Fit APs in the Fit AP list are incorrect when a Fit AP is added to the converged topology. 17. A viewer can add a wireless device in the converged topology. 18. Some radios are not added to the selected radio list when all Fit AP radios are selected in creating a radio policy. 19. A viewer that has the privilege of some devices views the AC topology. No Fit APs are displayed in the AC topology. Resolved Problems in IMC WSM 7.1 (E0303P04) 1. Display tips for a client in the Converged Topology, but Tips for the AC that connects to the client is displayed. 2. Add or modify a Client Detail Report, and the Add Scheduled Report page displays question marks. 3. Add an obstacle and exit the edit mode. The color for the obstacle is incorrect.

5 4. On the WSM overview page, the vendors are not displayed correctly when client statistics are displayed by vendor. 5. Syslog rules registered by WIPS are only forwarded to WIPS but are not saved in the Syslog component. 6. The locations of the virtual APs cannot be saved when you add virtual APs in location view. 7. The Remove All button is unavailable when you select one or more APs to be deployed for fast WLAN deployment. 8. Each part of the pie chart is identified by the number of Fit APs, not a percentage when you include the Fit AP widget on the IMC home page. Resolved Problems in IMC WSM 7.1 (E0303P01) 1. On the rogue AP details page, click the Open Topology link for the target location. The Applet topology appears. 2. On the Wireless Service Alarm page, click the header of a list to sort the list. The list is not sorted 3. On the Endpoint Identification Management page, click the Vendor link. The modification and delete functions do not exist. 4. Adding a rogue client or rogue AP to the permit list has failed. 5. The homepage responds slowly when there are a large number of wireless alarms in IMC. 6. Log in to the desktop version and click the GIS View link. Opening a GIS view has failed. 7. Fast deploying a WLAN has failed when select Hybrid Mode for the bound VLAN. Resolved Problems in IMC WSM 7.1 (E0303) 1. View client online history and client history. Signal strength and SNR cannot be displayed. 2. Configure radio parameters for an MSM device. Some parameters, such as Antenna Selection and Antenna Gain are not supported. 3. Enter the page for configuring APs in batches, and select AP model MSM 517. Supported radio list cannot be displayed correctly. 4. Select binding all radios when adding a WLAN for an MSM 335 AP. The WLAN failed to be added. 5. View detecting AP information on the rogue client details page. The detecting AP dialog box is blank. 6. View signal coverage in the location view by using an HTML5 topology. The coordinate origin for the signal coverage is incorrect. 7. Aruba devices are not supported on the Linux operating system. 8. The locating results cannot be correctly displayed in the HTML5 topology. 9. Network planning report does not show the channel list color legend. 10. The neighborhood scan status of MSM device is not supported. 11. HP 560 with MSM version 6.5 is not supported. 12. View the operation result for starting or stopping a radio or for radio power adjustment energy policy, and then click the navigation aids link for the Fit AP radio list. The operation result for the navigation aids is incorrect.

6 13. The HP tab is not displayed on the configuration page when an MSM AP rather than an MSM AC exists in the system. 14. HP 560 AP radios are not listed with Spectrum Guard. WSM Software Distribution Contents The WSM 7.1 (E0303P10) distribution list contains the following files and programs: 1. WSM\manual\readme_wsm_7.1 (E0303P10).html - This file 2. WSM\install - WSM installation program Installation Prerequisites Server Requirements Windows (32 bit) Size Nodes Fit AP: 0~500 or Fat AP:0~300 Performance Collecting Units On-line operators System Requirements (Lowest Requirements) CPU (Speed >= Memory 2.5GHz) Java heap size Disk Size of imc Installing Disk Size of imc Running 0~50K 10 2CPU 4G 1G 3GB 60GB Windows (64 bit) (Recommended) Size Nodes Fit AP: 0~500 or Performance Collecting Units On-line operators System Requirements (Lowest Requirements) CPU (Speed >= 2.5GHz) Memory Java heap size Disk Size of imc Installing Disk Size of imc Running 0~50K 10 2CPU 4G 1G 3GB 60GB

7 Fat AP: 0~300 Fit AP: 500~1000 or Fat AP: 300~700 Fit AP: 1000~3000 or Fat AP: 700~2000 Fit AP: 3000~5000 or Fat AP: 2000~3000 Enterprise Network: Fit AP: 5000~10000 or Fat AP: 3000~5000 Service provider: Fit AP: 5000~8000 or Fat AP: 3000~5000 Linux (32 bit) 16K~90K 10 4CPU 8G 4G 3GB 100GB 32K~150K 10 6CPU 16G 6G 4GB 200GB 100K~250K 10 8CPU 24G 8G 5GB 250GB 160K~400K 10 12CPU 32G 12G 7GB 300GB 160K~400K 10 12CPU 32G 12G 7GB 300GB Size Nodes Fit AP: 0~500 or Fat AP:0~300 Performance Collecting Units On-line operators System Requirements (Lowest Requirements) CPU (Speed >= Memory 2.5GHz) Java heap size Disk Size of imc Installing Disk Size of imc Running 0~50K 10 2CPU 4G 1G 3GB 60GB Linux (64 bit) (Recommended) Size Nodes Performance Collecting On-line operators System Requirements (Lowest Requirements) CPU (Speed >= Java Disk Size Memory heap of imc Disk Size of

8 Fit AP: 0~500 or Fat AP:0~300 Fit AP: 500~1000 or Fat AP: 300~700 Fit AP: 1000~3000 or Fat AP: 700~2000 Fit AP: 3000~5000 or Fat AP: 2000~3000 Enterprise Network: Fit AP: 5000~10000 or Fat AP: 3000~5000 Service provider: Fit AP: 5000~8000 or Fat AP: 3000~5000 Units 2.5GHz) size Installing imc Running 0~50K 10 2CPU 4G 1G 3GB 60GB 16K~90K 10 4CPU 8G 4G 3GB 100GB 32K~150K 10 6CPU 16G 6G 4GB 200GB 100K~250K 10 8CPU 24G 8G 5GB 250GB 160K~400K 10 12CPU 32G 12G 7GB 300GB 160K~400K 10 12CPU 32G 12G 7GB 300GB The following are software requirements for running WSM on a server: Operating system (Versions marked X64 are recommended): o Windows Server 2008 with Service Pack 2 o Windows Server 2008 X64 with Service Pack 2 o Windows Server 2008 R2 with Service Pack 1 o Windows Server 2012 X64 with KB o Windows Server 2012 R2 o Red Hat Enterprise Linux 5.5 (Enterprise and Standard versions only) o Red Hat Enterprise Linux 5.5 X64 (Enterprise and Standard versions only) o Red Hat Enterprise Linux 5.9 (Enterprise and Standard versions only) o Red Hat Enterprise Linux 5.9 X64 (Enterprise and Standard versions only)

9 o o Red Hat Enterprise Linux 6.1 X64 (Enterprise and Standard versions only) Red Hat Enterprise Linux 6.4 X64 (Enterprise and Standard versions only) VMware: o VMware Workstation 6.5.x o VMware Workstation 9.0.x o VMware ESX Server 4.x o VMware ESX Server 5.x Hyper-V: o Windows Server 2008 R2 Hyper-V o Windows Server 2012 Hyper-V Database o Microsoft SQL Server 2008 Service Pack 3 (Windows only) o Microsoft SQL Server 2008 R2 Service Pack 2 (Windows only) o Microsoft SQL Server 2012 Service Pack 2 (Windows only) o Microsoft SQL Server 2014 (Windows only) o Oracle 11g Release 1 (Linux only) o Oracle 11g Release 2 (Linux only) o MySQL Enterprise Server 5.5 (Linux and Windows) (Up to 1000 devices are supported) o MySQL Enterprise Server 5.6 (Linux and Windows) (Up to 1000 devices are supported) IMC Platform Compatibility o HP IMC Platform version: HP IMC PLAT 7.1 (E0303P13) and later patches. Note: 64-bit operating systems are recommended over 32-bit operating systems because of the larger amount of available memory for applications. Note: Optimal hardware requirements vary with scale, other factors, and are specific to each infrastructure. Please consult HP or your local account teams and precise requirements can be provided.

10 Client Prerequisites PC Requirements Minimum hardware requirements o 2.0 GHz Pentium 4 processor o 2048 MB of RAM o 50 GB hard disk space Operating system o Windows XP SP3 or later Browser o IE 10/11 is recommended. o Firefox 30 or later is recommended. o Chrome 35 or later is recommended. o Turn off the blocking settings in the browser. o Add the WSM website to the trusted sites of the browser. o The minimum resolution width is o JRE 1.6.0_update10 or later is recommended. If a client has no JRE, IMC prompts the user to install JRE for the client. Upgrade You can upgrade IMC WSM 7.1 (E0303), IMC WSM 7.1 (E0303P01), IMC WSM 7.1 (E0303P04) and IMC WSM 7.1 (E0303P08) to IMC WSM 7.1 (E0303P10). To upgrade WSM: 1. Back up the IMC database on the Environment tab in the Deployment Monitoring Agent. 2. Manually copy the IMC installation directory to a backup path. 3. Stop IMC in the Deployment Monitoring Agent. 4. Click Install on the Monitor tab of the Deployment Monitoring Agent. 5. Select the install/components directory in the upgrade package and click OK.

11 6. Click OK in the popup message dialog box. 7. Click Start in the Upgrade Common Components dialog box to upgrade common components. 8. After common components are upgraded, click Close. 9. In distributed deployment mode, stop the Deployment Monitoring Agent on the master server and restart the Deployment Monitoring Agent on every subordinate server. Click Yes in the popup message dialog box to upgrade common components on every subordinate server. 10. The Deployment Monitoring Agent displays all components that need to be upgraded. Click OK to start upgrading. 11. In distributed deployment mode, upgrade all components deployed on every subordinate server. 12. After all components are updated, start all processes in the Deployment Monitoring Agent. For more information about installation procedures, see IMC deployment guides. Removing WSM You can remove WSM component through the Deployment Monitoring Agent. To do this, follow these steps: 1. In the Deployment Monitoring Agent window, click Stop IMC on the Monitor tab to stop all processes of IMC. 2. On the Deploy tab, right-click the WSM component, and select Uninstall the Component from the shortcut menu. 3. When an un-installation success dialog box appears, click OK. Running the Deployment Monitoring Agent The Deployment Monitoring Agent is a GUI program to manage the deployment of the IMC modules and monitor the performance and the state of processes of the IMC server. After the installation finished, the Deployment Monitoring Agent is automatically started to guide the user through deployment. On Windows, run the Deployment Monitoring Agent by selecting All Programs > Intelligent Management Center > Deployment Monitoring Agent from the Start menu. On Linux, run the Deployment Monitoring Agent by executing dma.sh in the deploy directory of the IMC installation path.

12 If Deployment Monitoring Agent cannot start, make sure the HP IMC Server service is running. This service is automatically started along with the OS and runs as a daemon/background process. On Windows, you can start the service in Windows Services. On Linux, you can start the service with the service imcdmsd start command. IMC must be started from the Deployment Monitoring Agent. Starting IMC To start IMC, click Start IMC on the Monitor tab of the Deployment Monitoring Agent. Logging in to IMC through a Web Browser Once the server is running, you can access the IMC user interface using a Web browser. Enter the following address in the Address Bar of a browser: Where hostname is the host name or IP address of the IMC server (the default is localhost if you launch the Web browser on the IMC server machine), and port is the Web server port (the default is 8080) used by IMC. You can also access the IMC user interface with Web browser through HTTPS. Enter the following address in the address bar of a browser: Where hostname is the host name or IP address of the IMC Server (the default is localhost if you launch the Web browser on the IMC server machine), and port is the Web server port for HTTPS (the default is 8443) used by IMC. When the IMC login page appears, use the username "admin" and password "admin" to log into IMC. Refer to the IMC Online Help for details on how to add operators, and add your devices to IMC. The default security level in the IE properties is High. If you try to log in to IMC with this default, the system will prompt "Content from the Web site listed below is being

13 blocked by the Internet Explorer Enhanced Security Configuration." Click Add to add the IMC website to the trusted sites. If you do not add the IMC website to the trusted sites and determine not to display the prompt any more, you may fail to log in to IMC. To solve the problem, use either of the following methods: 1. Set the security level to Medium. o Start IE and select Tools > Internet Options. o Select the Security tab, and then click Custom Level. o In the popup dialog box, set the security level to Medium. 2. Add the website of the IMC server to the trusted sites. o Start IE and select Tools > Internet Options. o Select the Security tab, Select Trusted sites, and the click Sites. o Add the website of the IMC server in the popup dialog box. On your first access to IMC, the browser prompts "The application's digital signature cannot be verified. Do you want to run the application?" Below are the name "topo", and the publisher "IMC Development Team". Select the "Always trust content from this publisher" checkbox, and click Run. On your first access to the realtime performance view, the system prompts you to install Adobe Flash Player Installer. Click Install to download the installer package and install the application. Without this application, the realtime performance view is not available. Note: In centralized deployment, when the "User Access Manager - User SelfService" component is deployed, you will enter the Self-Service login page rather than the IMC login page if you enter in the address bar. To enter the IMC login page, change the content of the index.jsp file in directory \client\web\apps\root to <% response.sendredirect("/imc/index.jsp"); %>. Monitoring the Server On the Monitor tab of the Deployment Monitoring Agent, you can see the Disk Usage, CPU Usage, and Physical Memory Usage of the IMC server. On the Process tab of the Deployment Monitoring Agent, you can see all IMC processes and their running status. On the Environment tab of the Deployment Monitoring Agent, you can see the OS information and database usage. You can see the monitoring data of the IMC server only when IMC is started. For information about starting IMC, see "Running the IMC Server."

14 Distributed Deployment The IMC components can be installed on more than one server to meet specific performance requirements. A distributed IMC system typically has one master server with IMC Platform deployed and multiple subordinate servers with service components deployed. To install IMC on a subordinate server, execute the installslave.bat file on Windows (or installslave.sh on Linux) by either double-clicking the file or running the command in the folder where installslave.bat (or installslave.sh) is located. For information about deploying IMC in distributed mode, see IMC deployment guides. Platform Specific Issues Windows - General Issues Please be especially careful about how filenames are capitalized and used. This is essential in order to ensure consistent behavior across platforms that might use case-sensitive file systems. Linux - General Issues The IMC server must be run from a root user account in order to receive SNMP traps, accept syslog messages, and facilitate ftp file transfers. UNIX filenames are case sensitive. Care must be taken when references are made to python scripts and xml files. Port Usage WSM uses the following ports. Component Subcomponent Protocol Port Configurable Use Server Client Notes WSM -- TCP Yes Used for communication in Master- Slave IMC master server (all addressed) All IMC users None

15 WSM -- TCP 22 Yes WSM -- TCP 23 Yes WSM -- UDP 161 Yes WSM -- TCP 1433 Yes WSM -- TCP 7668 Yes deployment environment. SSH port, used to Configure device. Telnet port, used to Configure device. SNMP port, used to manage SNMP devices, elements. SQL Server database listening port (Windows only). Used to manage HP Wireless device. IMC master server (all addressed) IMC master server (all addressed) IMC master server (all addressed) IMC master server (all addressed) IMC WSM server (all addressed) All IMC users All IMC users All IMC users All IMC users All IMC users None None None None None Memory Allocation The amount of memory allocated to the IMC jserver can be adjusted by a script. The memory size should be tuned to make use of as much memory as required by your particular IMC server. Move to the "client\bin" (or "client/bin" on Linux OS) subdirectory of the original IMC installation directory (using the "cd" command), and use the setmem.bat (or setmem.sh on Linux OS) script. For example, to allocate 1024 MB RAM, move to the "installation directory\client\bin" (or "installation directory/client/bin" on Linux OS) directory, and run the script: setmem.bat 1024 setmem.sh 1024 (Windows OS) (Linux OS) The default and maximum memory that can be allocated to the IMC jserver is listed below:

16 OS Type Default allocable memory Maximum allocable memory Windows 32-bit 512 MB 1024 MB Windows 64-bit 2048 MB Depending on the physical memory Linux 32-bit 512 MB 1280 MB Linux 64-bit 2048 MB Depending on the physical memory Known Problems Installation/Upgrade/Patch For a correct installation, the installation path can contain letters, digits, underlines, and spaces, but cannot contain other special characters. The serial number of offline APs that never goes online cannot be displayed due to implementation. The radio information of offline APs cannot be displayed due to implementation. HP devices are not supported for location view history information. PB connection(configured via >> console on MSM device) failure between WSM and MSM device could cause the failure of configuration on MSM device. View detailed WLAN information for an HP device. The WPA encryption mode is not displayed. View detailed information about a client associated with an HP device. The information is not the same the actual condition. Click Synchronize, AuthorizeLocally, AcceptSuspicious, AcceptProducts, or RemoveandRediscover to change the work status of an HP Fit AP multiple times. The work status of the AP might be incorrect and the Action menu might disappear. Search Fit APs and clients in the Wireless Topology or Converged Topology by IP address. No Fit AP and client information is displayed. Feature Support Matrix This section describes the features that are supported by the device model types. MSM Models NOT Supported by WSM: WSM does not support 5.4 or lower. These MSM devices can only run on MSM 5.2 and therefore are not supported by WSM: MSM 313, R,323R.

17 Cisco Feature Note: WSM does not support MSM versions 5.4 or lower. HP MSM v5.5 to 6.5 MSM710 MSM720 MSM760 MSM760B MSM765zl HP Comware HP 830 HP 850 HP 870 Cisco 2106 Wireless LAN Controlle r Cisco 5508 Wireless LAN Controlle r Cisco Virtual Wireless Controlle r (AIR- CTVM- K9) Aruba Aruba 800 Aruba 3200 Topology Displaying ACs and Fat APs in IP view Wireless device topology Location view topology Wireless custom view topology Physical connection between Fit APs and ACs in the Fit AP topology Operation about user from online clients that attached to the AP Y Y No Fat AP No Fat AP Resource group WSM Home Partial Y Partial Partial

18 Category view Wireless custom view Location view AC Group (batch configuration profile deployed to a group of controllers) Only H3C supports AP uplink POE switch -- used to managed the link between switch and the AP Fit AP group AC Team - This is for 700 and 720, see the list of the controllers working as a team, # of the controller team, and data on it. (Team status) Y N N N Wireless location Sampling point Add sampling point Delete sampling point Update sampling point Wireless location Wireless real-time locating Position-based wireless access control - for Location Based Access Control. Requires UAM

19 v7/inode client v7 Wireless access area Position-based access control GIS Displaying hotspots detail Set default display position Add hotspot Update hotspot Delete hotspot GIS locating Muti-key support WIDS Displaying lists of Rogue APs and Rogue clients Displaying details of Rogue APs and Rogue clients Setting rogue devices as friendly devices Configuring Wireless Intrusion Detection System policies Rouge AP counterwork Y(6.0 after) Y N N Y(6.0 after) Y N N Y(6.0 after) Y N N WIPS WIPS Configuration APs Detected

20 Clients Detected SSIDs Detected Security Events Sensor Management Virtual Security Domain Management Dynamic Detection Information Management Web Service Interface Query basic information of device Query fault information of device Query performance information of device Wireless service reports Service Report Not all reports Y Not all reports Not all reports Subordinate summary Report (NO LONGER IN WSM) Wireless service alarms AC Y Y N N AP Y Y N N Client Y Y N N WIDS (Wireless Intrusion Detection System) NMS (IMC) Access Point: provides traps for the AP (lets you Y Y N N

21 see if AP is online/offline) Wireless device AC Fat AP Y Y N N Fit AP Client WLAN (SSID) Radio Configuration wizard AC configuration wizard Fat AP configuration wizard Y Y Y N Y Y N N Policy configuration Radio Policy Service Policy Template Creating Radio policy templates manually Displaying Radio policy template information Creating service policy templates manually Displaying service policy template information

22 Mesh MP policy Mesh profile Mesh interface configuration Configure peer MAC address Energy policy Energy Policy Management N Y Network planning AP Model Management Antenna Management Y Y N N Y Y N N AP Add Virtual AP Y Y N N Performance statistics displaying history trend graphs displaying history information for ACs Y Y Y N displaying history information for Fit APs displaying history information based on SSIDs displaying history information in location views Y Y N Y Querying WLAN

23 information Querying WLAN information Operating system Windows Linux DataBase Windows+SqlServer Windows+Mysql Linux+Oracle Linux+Mysql Report Support This section list specifies which reports are or are not supported. Report Name AC Statistics Report AP Association Summary Report Support Field Partial N AC Name, IP Address, AP Number, Availability, Transmitted Traffic, Received Traffic, Max Transmit Speed, Avg Transmit Speed, Max Receive Speed, Avg Receive Speed, Max Online Client Number, Avg Online Client Number, AP Average Utilization, AP Peak Utilization, Total Client Online Duration, Avg Client Online Duration None AP Association Detail Report N None AP Availability Detail Report Y All AP Availability Summary Report Site Access Points and Neighbors Y Y All All

24 Idle AP Statistics Report N None Busy AP Statistics Report N None Worst AP Statistics Report N None AP Logoff Summary Report Y All AP Logoff Detail Report Y All AP Statistics Report Radio Error Report Partial Partial Radio Speed Report Y All AP Traffic Summary Report Y All AP Traffic Detail Report Y All Radio Traffic Report Y All AP Speed Report Y All Radio Resource Usage Report N None Rogue AP History Report Y All Rogue AP Report Y All Rogue Client History Report Y All Rogue Client Report Y All Current Associated Client Statistics Report Y AP Name, AP Location, Availability, Transmitted Core Traffic, Received Core Traffic, Transmitted Radio Traffic, Received Radio Traffic, Max Transmit Speed, Avg Transmit Speed, Max Receive Speed, Avg Receive Speed, Max Online Client Number, Avg Online Client Number, AP Average Utilization, AP Peak Utilization, Total Client Online Duration, Avg Client Online Duration AP Name, Radio ID, AP Location, FCS Error Frames All SSID Statistics Report Y All SSID Online Client Num Statistics Report Y Hotspot Statistics Report by AP Y Hotspot Statistics Report by Hotspot Partial All All Hotspot Name, AP Number, Online AP Number, Availability, Transmitted Traffic, Received Traffic, Max Transmit Speed, Avg Transmit Speed, Max Receive Speed, Avg Receive Speed, Max Online Client Number, Avg Online Client Number, AP Average Utilization, AP Peak Utilization, Total Client Online Duration, Avg Client Online Duration

25 Wireless Asset Statistics Report Partial Client Summary Report Y All Client Detail Report Y All Client Number Trendline Report Y exclude Max APs, Max Clients, Radios/Clients All Issued: September 2015 Copyright (c) 2015 Hewlett-Packard Development Company, L.P. and its licensors.