IMC Wireless Service Manager 7.3 (E0505) Copyright 2015,2016 Hewlett Packard Enterprise Development LP

Transcription

1 Wireless Service Manager 7.3 (E0505) Copyright 2015,2016 Hewlett Packard Enterprise Development LP 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 10. Logging in to 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 WSM 7.3 (E0505) can be upgraded from WSM 7.2 (E0502), WSM 7.2 (E0502P04), WSM 7.2 (E0502P05), WSM 7.2 (E0502H07) and WSM 7.2 (E0502H08). Features released in WSM 7.3 (E0505)

2 Support for refreshing the specified page by selecting an item from the navigation tree in the default view. This Feature is configurable under Service > WLAN Manager Support for querying clients by client IP address in the client list. This feature is configurable under Service > WLAN Manager > Resource Management > Clients. Optimized V2 report format. This feature is configurable under Service > WLAN Manager > Wireless Service Report. Optimized the location view topology saving function. This Feature is configurable under Service > WLAN Manager > Wireless Topology > Location View. Features released in WSM 7.2 (E0502H08) None. Features released in WSM 7.2 (E0502H07) None. Features released in WSM 7.2 (E0502P05) None. Features released in WSM 7.2 (E0502P04) Support for recording the location history of offline APs in the location view. This feature is configurable under Service > WLAN Manager > Wireless Topology > Location View. Support for AP model management and network planning for Aruba APs. This feature is configurable under Service > WLAN Manager > Configuration Management > AP Model Management. Support for integration with AirWave. This feature is configurable under Service > WLAN Manager > Resource Management > ACs/Fit APs/Clients. Support for displaying information about Aruba IAPs through SNMP. This feature is configurable under Service > WLAN Manager > Resource Management > Fit APs. Added device Synchronization Configuration to configuration management. This feature is configurable under Service > WLAN Manager > Configuration Management > Synchronization Configuration. Support 2.4 GHz and 5 GHz power usage configuration in wireless network planning. This feature is configurable under Service > WLAN Manager > Wireless Topology > Location View. Optimized the troubleshooting function. This Feature is configurable under Service > WLAN Manager > Resource Management > Clients. Features released in WSM 7.2 (E0502)

3 Support for Quick Service Process. This Feature is available in the top right corner of the home page. Support for Client Traffic Analysis on the client list. This Feature is configurable under Service > WLAN Manager > Resource Management > Client List. The radio information display function is added in the location view. This Feature is configurable under Service > WLAN Manager > Wireless Topology > Location View. Features released in WSM 7.1 (E0303P10) None. Features released in WSM 7.1 (E0303P08) Support for WT management 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, 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 WSM 7.1 (E0303P04)

4 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. 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 WSM 7.1 (E0303P01) None. Features released in 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 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 WSM 7.3 (E0505) fixes the following problems, including all bugs fixed after WSM 7.1 (E0303).

5 Resolved Problems in WSM 7.3 (E0505) 1. The location view topology does not display client information because APs associated with backup ACs are added to the topology when AC backup is configured. 2. The location view topology fails to display APs when a lot of obstacles exist in the topology. 3. Some data lack fields such as vendor when Rest interface queryallclientbasicinfo is used to query basic client information. 4. Errors occur when the WLAN Overview page is displayed on the mobile phone client. 5. The system fails to load client information when the Oracle database is used and client information is viewed by clicking a client in the location view topology. Resolved Problems in WSM 7.2 (E0502H08) 1. Failed to synchronize information about MSM760 devices because model MSM525 does not exist. 2. Deleting AP port information for the master AC when the master AC fails and the backup AC takes over. 3. After the switch port and associated AC are changed for an AP, the energy policy is still performed on the former port. Resolved Problems in WSM 7.2 (E0502H07) 1. Spelling mistake for the AriWave Client Info pop-up menu of the Operation column. 2. WSM cannot display the signal strength of clients associated with IAPs. 3. IAPs do not support client and AP bandwidth statistics. 4. An error occurs when online history data is displayed for clients associated with IAPs. 5. The Group field is empty on the brief information page for an Aruba AP. 6. WSM cannot manage WLANs provided by IAPs. 7. An error occurs when client online history is sorted by username. Resolved Problems in WSM 7.2 (E0502P05) 1. After an HP MSM430 or MSM460 is added to a topology location view, the Show Radio Information menu is unavailable on the location topology. 2. The login page displays a prompt that indicates report view script creation or start failure if is deployed in distributed mode on Windows and uses a SQL Server database. 3. If a WSM V1 type scheduled report exists, platform reports fail to be loaded when WSM is being upgraded. 4. An error page appears when troubleshooting is performed for a client unassociated with an AP. 5. In the client list, the Signal Strength field for clients associated with an Aruba AC displays Signal Strength: unknown.

6 6. The WSM components are exposed to OpenSSL security vulnerabilities CVE , CVE , CVE , CVE , and CVE Resolved Problems in WSM 7.2 (E0502P04) 1. The navigation bar is not displayed when you switch from the Comware Based tab to the MSM tab on the fast WLAN deployment page. 2. The system copies the cancelled but not the most recently selected energy policy when you perform the following steps: a. Copy and then cancel copying an energy policy. b. Copy another energy policy. 3. The system goes to the Network Planning page, not the Configuration Management page when you perform the following steps:. Click AP Model Management on the Network Planning page. a. Click Fit AP Group on the Configuration Management page to open the Fit AP Group Management page. b. Click Back on the Fit AP Group Management page. 4. The management status is changed successfully for a Cisco Fit AP radio. However, the radio details show that the management status is not changed. 5. An error converged topology page appears when you perform the following steps:. Save the added non-wireless devices or devices that are incorrectly determined as wireless devices by the platform. a. Exit the converged topology. b. Open the converged topology again. 6. The spectrum guard page is still refreshing when the Expand icon for advanced query is clicked on the page. 7. In WSM QSP, the tabs on the WIPS configuration page cannot be switched correctly. 8. In WSM QSP, data on the WIDS configuration page disappears when the enabling/disabling IDS and importing authorized AP list operations are performed. 9. The system prompts error when generating a wireless custom report. 10. There lacks initialization data, when you view the Client Count in Dashboard. 11. When client number display is disabled in the location view topology, the client numbers are displayed on the location view topology. 12. When client number display is enabled in the wireless topology and clients come online and go offline frequently, the client number flashes frequently on the wireless topology. 13. When uses an Oracle database, the number of fit APs on the fit AP list is inconsistent with the number of fit APs represented by Others in the Fit AP Model pie chart on the service overview page. 14. On the AC list, the Synchronizing state should be included in the synchronization result. 15. On the WLAN Manager > Configuration Management > Threshold Configuration page, the thresholds for major alarms and minor alarms use unreasonable input value ranges. Resolved Problems in WSM 7.2 (E0502)

7 1. Use the basic query and advanced query functions to query data on the fit AP list, click the Export All button, all APs are exported when the basic query function is used and only queried APs are exported when the advanced query function is used. 2. Fat AP configuration is not displayed when only HP fat APs exist in and the MSM tab in configuration management is selected 3. The jserver process cannot be started when client number display is enabled in the wireless topology, and too many temporary pictures are generated. 4. The 5 GHz RF heat map is not available for Aruba devices in the topology 5. The Performance Collection Parameters button is not displayed on the client lists. 6. The number of clients cannot be counted when the number of clients is displayed in the converged topology, no matter in Star or Number mode. Resolved Problems in WSM 7.1 (E0303P10) 1. The customized columns for clients cannot be exported. 2. The MSM or Cisco tab has no data when the 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. Resolved Problems in 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.

8 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 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 management privilege of some devices views the AC topology. No Fit APs are displayed in the AC topology. Resolved Problems in 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. 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 home page. Resolved Problems in 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.

9 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 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. 13. The HP tab is not displayed on the configuration management 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.3 (E0505) distribution list contains the following files and programs: 1. WSM\manual\readme_wsm_7.3 (E0505).html - This file 2. WSM\install - WSM installation program Installation Prerequisites

10 Server Requirements Windows (32 bit) Size Nodes Fit AP: 0~500 or Fat AP:0~300 System Requirements (Lowest Requirements) Disk Performance CPU Java Disk Size On-line Size of Collecting (Speed >= Memory heap of operators Units 2.5GHz) size Installing Running 0~50K 10 2CPU 4G 1G 3GB 60GB Windows (64 bit) (Recommended) Size Nodes 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 System Requirements (Lowest Requirements) Disk Performance CPU Java Disk Size On-line Size of Collecting (Speed >= Memory heap of operators Units 2.5GHz) size Installing 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

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

12 300~700 Fit AP: 1000~3000 or Fat AP: 700~2000 Fit AP: 3000~5000 or Fat AP: 2000~ K~150K 10 6CPU 16G 6G 4GB 200GB 100K~250K 10 8CPU 24G 8G 5GB 250GB Enterprise Network: Fit AP: 160K~400K ~10000 or 12CPU 32G 12G 7GB 300GB Fat AP: 3000~5000 Service provider: Fit AP: 5000~8000 or Fat AP: 3000~ K~400K 10 12CPU 32G 12G 7GB 300GB The following are the minimum hardware requirements and supported software programs to run : 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) o Red Hat Enterprise Linux 6.1 X64 (Enterprise and Standard versions only) o Red Hat Enterprise Linux 6.4 X64 (Enterprise and Standard versions only)

13 o Red Hat Enterprise Linux 7.0 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 Oracle 12c Release 1 (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) Platform Compatibility o HP Platform version: HP PLAT 7.3 (E0503) or later. 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 management factors, and are specific to each infrastructure. Please consult HP or your local account teams and precise requirements can be provided.

14 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, prompts the user to install JRE for the client. Upgrade To upgrade WSM: 1. Back up the database on the Environment tab in the Deployment Monitoring Agent. 2. Manually copy the installation directory to a backup path. 3. Stop 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. 6. Click OK in the popup message dialog box. 7. Click Start in the Upgrade Common Components dialog box to upgrade common components.

15 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 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 on the Monitor tab to stop all processes of. 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. If processes imcwlandm, imcwlanperfdm, and imcwipsdm are still in operation after WSM 7.3 (E0505) is uninstalled, delete statements related to the three processes in file QvProcessManager.xml in directory {%_HOME%}\server\conf and then restart. Please first back up the file in case any mistakes occur. Running the Deployment Monitoring Agent The Deployment Monitoring Agent is a GUI program to manage the deployment of the modules and monitor the performance and the state of processes of the 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 installation path.

16 If Deployment Monitoring Agent cannot start, make sure the HP 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. must be started from the Deployment Monitoring Agent. Starting To start, click Start on the Monitor tab of the Deployment Monitoring Agent. Logging in to through a Web Browser Once the server is running, you can access the 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 server (the default is localhost if you launch the Web browser on the server machine), and port is the Web server port (the default is 8080) used by. You can also access the 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 Server (the default is localhost if you launch the Web browser on the server machine), and port is the Web server port for HTTPS (the default is 8443) used by. When the login page appears, use the username "admin" and password "admin" to log into. Refer to the Online Help for details on how to add operators, and add your devices to. The default security level in the IE properties is High. If you try to log in to with this default, the system will prompt "Content from the Web site listed below is being

17 blocked by the Internet Explorer Enhanced Security Configuration." Click Add to add the website to the trusted sites. If you do not add the website to the trusted sites and determine not to display the prompt any more, you may fail to log in to. 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 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 server in the popup dialog box. On your first access to, 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 " 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 login page if you enter in the address bar. To enter the 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 server. On the Process tab of the Deployment Monitoring Agent, you can see all 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 server only when is started. For information about starting, see "Running the Server."

18 Distributed Deployment The components can be installed on more than one server to meet specific performance requirements. A distributed system typically has one master server with Platform deployed and multiple subordinate servers with service components deployed. To install 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 in distributed mode, see 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 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 master All None

19 in Master- Slave deployment environment. server (all users addressed) WSM -- TCP 22 Yes SSH port, used to Configure device. master server (all addressed) All users None WSM -- TCP 23 Yes Telnet port, used to Configure device. All master server (all users addressed) None WSM -- UDP 161 Yes SNMP port, used to manage SNMP devices, elements. master server (all addressed) All users None WSM -- TCP 1433 Yes SQL Server database listening port (Windows only). All master server (all users addressed) None WSM -- TCP 7668 Yes Used to manage HP Wireless device. All WSM server (all users addressed) None Memory Allocation The amount of memory allocated to the 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 server. Move to the "client\bin" (or "client/bin" on Linux OS) subdirectory of the original 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:

20 setmem.bat 1024 setmem.sh 1024 (Windows OS) (Linux OS) The default and maximum memory that can be allocated to the jserver is listed below: OS Type Default allocable memory Maximum allocable memory Windows 32-bit 512 MB Windows 64-bit 2048 MB 1024 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 management >> management 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.

21 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. Aruba 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 Cisco 2106 Wireless LAN Controlle r Cisco 5508 Wireless LAN Controlle r Cisco Virtual Wireless Controlle r (AIR- CTVM- K9) Aruba 800 Aruba 3xxx Aruba 70xx Aruba 72xx Aruba IAP 103 Aruba IAP 20x Aruba IAP 21x Aruba IAP 22x Aruba IAP 31x Aruba IAP 32x Aruba IAP 33x Topology management Displaying ACs and Y Fat APs in IP view Y No Fat AP No Fat AP Wireless device topology Y Y Y Y Location view topology Y Y Y Y Wireless custom view topology Y Y Y Y Physical connection between Fit APs and N Y Y Y ACs in the Fit AP

22 topology Operation about user management from online clients that attached to the AP Y Y Y Y Resource group management WSM Home Partial Y Partial Partial Category view Y Y Y Y Wireless custom view Y Y Y Y Location view Y Y Y Y AC Group (batch configuration profile deployed to a group N Y N N of controllers) Only H3C supports AP uplink POE switch management -- used to managed N Y Y Y the link between switch and the AP Fit AP group Y Y Y Y AC Team - This is for 700 and 720, see the list of the controllers working Y as a team, # of the N N N controller team, and data on it. (Team status) Wireless location management Wireless real-time location N Y N N GIS management Displaying hotspots Y detail Y Y Y Set default display position Y Y Y Y Add hotspot Y Y Y Y

23 Update hotspot Y Y Y Y Delete hotspot Y Y Y Y GIS locating Y Y Y Y Muti-key support Y Y Y Y WIDS management Displaying lists of Rogue APs and Rogue clients Y(6.0 after) Y N N Displaying details of Rogue APs and Y(6.0 after) Y N N Rogue clients Setting rogue devices as friendly Y(6.0 after) Y N N devices Configuring Wireless Intrusion Detection System N Y N N policies Rouge AP counterwork N Y N N WIPS management WIPS Configuration N Y N N APs Detected N Y N N Clients Detected N Y N N SSIDs Detected N Y N N Security Events N Y N N Sensor Management N Y N N Virtual Security Domain N Y N N Management Dynamic Detection Information Management N Y N N Restful Interface Query basic information of device Query fault information of device Y Y Y Y Y Y N N

24 Query performance information of device Y Y Y Y Wireless service reports Service Report Not all reports Y Not all reports Not all reports Subordinate summary Report (NO LONGER IN WSM) N Y N N Wireless service alarms AC Y Y N N AP Y Y N N Client Y Y N N WIDS (Wireless Intrusion N Y N N Detection System) NMS () Access Point: provides traps for the AP (lets you Y Y N N see if AP is online/offline) Wireless device management AC management Y Y Y Y Fat AP management Y Y N N Fit AP management Y Y Y Y Client management Y Y Y Y WLAN management(ssid) Y Y Y Y Radio management Y Y Y Y Configuration wizard AC configuration wizard Fat AP configuration wizard Y Y Y Y Y Y N N Policy

25 configuration Radio Policy N Y Y Y Service Policy Y Y Y Y Template management Creating Radio policy templates manually Displaying Radio policy template information Creating service policy templates manually Displaying service policy template information Mesh management MP policy management Mesh profile management Mesh interface configuration Configure peer MAC address Energy policy management Energy Policy Management N Y N N N Y N N N Y N N N Y N N N Y N N N Y N N N Y N N N Y N N Partial Y N N Network planning AP Model Management Y Y N Y Antenna Management Y Y N Y AP Add Virtual AP Y Y N Y Performance statistics

26 displaying history trend graphs Y Y Y Y displaying history information for ACs Y Y Y N displaying history information for Fit Y Y N Y APs displaying history information based N Y N N on SSIDs displaying history information in location views Y Y Y Y Querying WLAN information Querying WLAN information Y Y Y Y Operating system Windows Y Y Y Y Linux Y Y Y Y DataBase Windows+SqlServer Y Windows+Mysql Y Y Y Linux+Oracle Linux+Mysql Y Y Y Y Report Support This section list specifies which reports are or are not supported. Report Name Support Field AC Statistics Report Partial AC Name, IP Address, AP Number, Availability, Transmitted Traffic, Received Traffic, Max Transmit Speed, Avg Transmit Speed, Max Receive

27 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 Association Summary Report N None AP Association Detail Report N None AP Availability Detail Report Y All AP Availability Summary Report Y All Site Access Points and Neighbors Y All 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 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 Radio Speed Report Y All AP Traffic Summary Report Y All

28 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 All SSID Statistics Report Y All SSID Online Client Num Statistics Report Y All Hotspot Statistics Report by AP Y All Hotspot Statistics Report by Hotspot Partial 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 Wireless Asset Statistics Report Partial exclude Max APs, Max Clients, Radios/Clients Client Summary Report Y All Client Detail Report Y All Client Number Trendline Report Y All

29 Issued: December 2016 Copyright 2015,2016 Hewlett Packard Enterprise Development LP