ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation Release v1.2.
Copyright © 2018 Extreme Networks, Inc. All rights reserved. Legal Notice Extreme Networks, Inc. reserves the right to make changes in specifications and other information contained in this document and its website without prior notice. The reader should in all cases consult representatives of Extreme Networks to determine whether any such changes have been made. The hardware, firmware, software or any specifications described or referred to in this document are subject to change without notice.
Table of Contents Preface......................................................................................................................................... 4 Conventions............................................................................................................................................................................. 4 Providing Feedback to Us........................................................................................................................................
Preface This section discusses the conventions used in this guide, ways to provide feedback, additional help, and other Extreme Networks publications. Conventions This section discusses the conventions used in this guide. Text Conventions The following tables list text conventions that are used throughout this guide. Table 1: Notice Icons Icon New! Notice Type Alerts you to... General Notice Helpful tips and notices for using the product. Note Important features or instructions.
Preface Terminology When features, functionality, or operation is specific to a switch family, such as ExtremeSwitching™ or Summit®, the family name is used. Explanations about features and operations that are the same across all product families simply refer to the product as the switch.
Preface Current Product Documentation www.extremenetworks.com/documentation/ Archived Documentation (for earlier versions and legacy products) www.extremenetworks.com/support/documentation-archives/ Release Notes www.extremenetworks.com/support/release-notes Open Source Declarations Some software files have been licensed under certain open source licenses. More information is available at: www.extremenetworks.com/support/policies/software-licensing.
1 Preparing to Migrate Location Based Services from ADSP Suggested Migration Path - WiNG and ADSP to ExtremeLocation Preparing ADSP for Migrating Location Based Services Preparing ExtremeLocation for Migrating Location Based Services Customers who use Proximity Awareness and Analytics services on AirDefense Service Platform (ADSP), can now migrate these services to ExtremeLocation as it provides enhanced location based services as well as and superior scalability performance.
Preparing to Migrate Location Based Services from ADSP Preparing ADSP for Migrating Location Based Services Note Migrating Location Based Services from ADSP to ExtremeLocation does not export location and analytics data. Migration only exports site setup, floor plans, and RTLS calibration data. ADSP has to be patched before you can export setup and calibration data to ExtremeLocation. Please contact GTAC (Global Technical Assistance Center) to request this ADSP patch.
2 Migrating ADSP Location Based Services Exporting Location Based Services Data from ADSP Transfer the Downloaded .zip File FloorPlan.zip File Structure Download the Migration Script Executing the Migration Script Migration Errors Migrating location based services from AirDefense Service Platform involves running a command from within the ADSP command line interface (CLI). This creates a zip file containing exported data like sites, floor plans, regions, and calibration information.
Migrating ADSP Location Based Services 1 From your operating system, launch WinSCP. The WinSCP user interface launches. Configure your login similar to the above image. ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Migrating ADSP Location Based Services 2 Select the Login button at the bottom of the WinSCP window. You are connected to the remote AirDefense Service Platform server. ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Migrating ADSP Location Based Services 3 From the main menu, select Commands > Open in PuTTY. A SSH PuTTY session is created for the remote ADSP server. WinSCP connects to the ADSP server using the smxmgr user account. 4 Enter the password for this account. The ADSP CLI displays. ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Migrating ADSP Location Based Services 5 At the prompt, type letmeout to exit out of the AirDefense Service Platform CLI. You are taken to the Home directory for the smxmgr account. 6 At the command prompt, type su to enter the superuser mode for this ADSP server and when prompted, type the root password. 7 At the command prompt, type command exportFloorplan. The command is executed and provides a status of progress.
Migrating ADSP Location Based Services This process will take time if your ADSP server manages a large number of sites and sensors. At the end of this process, the command displays a summary of files created by it. ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Migrating ADSP Location Based Services A zip (compressed zip file) is created for each site managed by this ADSP server. These zip files are then packaged in another zip file. This file can be found in the folder /usr/local/tmp and is always named as FloorPlan.zip. 8 At the command prompt, type exit followed by the Enter key. Repeat this command once more to gracefully exit out of ADSP CLI. The WinSCP window now becomes available for use. Transfer the Downloaded .
Migrating ADSP Location Based Services Download the migration scripts from within the ExtremeLocation user interface. For instructions, see Download the Migration Script on page 17 FloorPlan.zip File Structure Contents of the FloorPlan.zip file The FloorPlan.zip file is a collection of zip for each floor in the site and a csv file containing the mapping for the zip files in this FloorPlan.zip file. A typical floorplans.csv file contains the sites mapped to its zip file.
Migrating ADSP Location Based Services • logfile_reverse_RSSI.log - This file lists all the Sensor RSSI values for each client with sensor MAC and Client MAC for every marker listed in the above logfile_building.log file Download the Migration Script You must have exported the floor plans and other configuration details from within AirDefense Service Platform using the ADSP CLI environment. If not done so, please see Exporting Location Based Services Data from ADSP on page 9.
Migrating ADSP Location Based Services 2 Select Downloads from the drop down menu. The Downloads screen displays. Figure 2: Downloads Screen 3 Select ADSP Migration Script. The migration script is downloaded as a zip file. Save the file to a local directory and decompress it using your favorite compression tool. On extracting the file, verify if a new directory named migration-client has been created in the directory where the zip file was extracted.
Migrating ADSP Location Based Services Executing the Migration Script To migrate location based services from AirDefense Service Platform to ExtremeLocation, use the following steps: 1 Upload the FloorPlan.zip file to the ExtremeLocation server 2 Verify if the upload has completed successfully. If not, use the upload summary report (upload_summary-*.
Migrating ADSP Location Based Services 4 Execute the command: ./migrate_adsp_linux.sh upload [license=true|false]. Pass the following parameters to this command: API Key Pass the valid API key for your ExtremeLocation account. Path to ADSP exported Data Pass the complete path to the FloorPlan.zip file. license Set the flag to indicate that licenses have to be auto allocated to the sites. A report is generated on completion of this command.
Migrating ADSP Location Based Services 3 Verify if the following files are extracted in the migration-client directory. • • • • • • • eloc-migration-client-1.2-5D.jar log4j.properties migrate_adsp_linux.sh migrate_adsp_windows.bat migration-client.properties README-Linux.txt README-Windows.txt Note The file name for the .jar file will change for every new release. 4 Execute the command: migrate_adsp_windows.bat upload [license=true|false].
Migrating ADSP Location Based Services 5 Verify the content of the summary .csv file and resolve any issues indicated in the file. For more information on the errors that can occur and on suggested steps to resolve those issues, see Migration Errors on page 23. 6 Execute the command: migrate_adsp_windows.bat migrate license=true. Pass the following parameters to this command: API Key Pass the valid API key for your ExtremeLocation account.
Migrating ADSP Location Based Services Migration Errors Possible Causes of Migration Failure These are the possible causes for the migration to fail. Error Mitigation Passing wrong arguments to the script. The script prompts the error. User needs to pass correct arguments to the script. Passing wrong number arguments to the script. The script prompts the error. User needs to pass the correct number of arguments to the script.
Migrating ADSP Location Based Services Error Cause Unable to find host Please configure host in Failed to read migrationclient.properties property migrationclient.properties property setting setting UnknownHostException Unable to connect to the host name configured in the migrationclient.properties property setting The system cannot find the path specified Environment variable JAVA_HOME is not set Mitigation Please configure host in migrationclient.
Migrating ADSP Location Based Services Error Cause Failed to get migration Unable to get the status from the ExtremeLocation server. status. Retried 3 times. Giving up Request URL is not allowed since License is not present API key is not valid or tenant does not have valid license Mitigation Check network connectivity to and service availability of the ExtremeLocation server. Check API key and license applied on the tenant. Server Side Errors Server side errors are appended to the migration-client.
Migrating ADSP Location Based Services Error Cause Mitigation Failed to add floor: OR Failed to create floor Unable to create floor due to ExtremeLocation service down or not responding. Wait for ExtremeLocation service to become available and try to migrate failed floors again. Failed to create all devices. OR Failed to create some of the devices. Unable to create devices due to ExtremeLocation service down or not responding.
3 Verify Migration in ExtremeLocation Verify Migration RF Domain Configuration To verify that the location based services from AirDefense Service Platform is successfully migrated to ExtremeLocation: 1 Login to the web user interface from the ExtremeLocation login page 2 Review the Maps screen to check if all your sites have been imported 3 Since AirDefense Service Platform does not have geo-location information, place your sites individually in the maps screen 4 Verify if the site details have been importe
Verify Migration in ExtremeLocation 3 Select the Login button to login to the ExtremeLocation user interface. On successful login, the Maps screen appears. Figure 4: Maps Screen 4 Select the Sites drop-down list to expand it. The Sites drop-down list expands to display the sites and site groups configured for this ExtremeLocation account. Figure 5: Sites List ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Verify Migration in ExtremeLocation 5 Verify if your sites have successfully imported into ExtremeLocation. The imported sites will not be visible in the Maps view. This is because AirDefense Service Platform does not store geo-location information for the sites it manages. You will have to place each at its exact geo-location before you can proceed further. 6 Select your site from the drop-down list and then select the place it at its exact geo-location.
Verify Migration in ExtremeLocation 8 Review the Site Groups this Site is a member of. If required, modify the site groups to reflect the correct memberships for this site. ADSP uses Scopes to define a site. For example the below image displays a scope for a site. Figure 7: ADSP Site Scope When importing this site (LAB), each level of the scope is created as a site group and the site is made a member of each of these new site groups.
Verify Migration in ExtremeLocation 1 Select Configuration > RF Domains > . The RF Domain screen displays. ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Verify Migration in ExtremeLocation 2 Select Sensor from the menu on the left. The Sensor screen displays. 3 Select + Add Row from within the Location Tracking System list. This adds a new row in the Location Tracking System table. Only one row can be configured for this table. Provide the following information: Server Id Use the spinner control to assign a numeric ID for the ExtremeLocation server. The default ID value is 1. IP Address/ Hostname Provide the host name of the ExtremeLocation server.
Verify Migration in ExtremeLocation 4 In ExtremeLocation locate your tenant account number. This number is located next to the the top right of your screen. ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Verify Migration in ExtremeLocation 5 Specify your ExtremeLocation Tenant Account Number in the Tenant Account field . 6 Select OK to save the changes to the RF Domain Sensor configuration, or select Reset to revert to the last saved configuration. ExtremeLocation Migrating Location Based Services from ADSP to ExtremeLocation for version 1.2.
Verify Migration in ExtremeLocation 7 Select Basic from the RF Domain menu on the left. The RF Domain basic configuration screen appears. Figure 8: RF Domain Basic Configuration Screen 8 Select the Country drop-down to expand it and select the country of operation for this access point. 9 Select OK to save the changes to the RF Domain Basic configuration, or select Reset to revert to the last saved configuration. 10 Select Exit to exit the RF Domain configuration screen.
