This guide will explain what needs to be done Step-by-step to install the LIPI, when you don’t plan to connect it to the internet. If you are, however, considering using internet for the installation and for operational use of the LIPI, kindly refer to https://mazemap.atlassian.net/l/c/xBtcNDmq
Time needed: 30 minutes.
PREREQUISITES for the LIPI Installation
Requirements for the LIPI server
Can be virtual or physical, does not matter.
No OVA currently available, one of the supported OSes needs to be installed.
Supported Operating systems: Newest stable Ubuntu or Debian.
Server/Virtual Machine(VM) specs: Tested to work with single Core VM with 3.5 GB Ram and 7 GB HDD.
Requirements for the network
Open port 443 from LIPI server to CMX (https for API).
Open port 443 from all wireless clients to LIPI (https for position requests).
Traffic from Wireless Clients to LIPI must not pass through NAT.
Requirements for the CMX
CMX set up with Location services activated and sufficient licenses.
Building maps, with correct map scaling and a minimum of 3 GPS markers per floor need to be set up on Cisco Prime, exported and imported into CMX.
GPS markers should use coordinates created using MazeMaps own map. MazeMap provides a tool for generating these. You can find the POI inspector-tool here: https://debug.mazemap.com/
Access points must be placed correctly (within a meter of actual location) in the maps in Cisco Prime.
Enable the API server
Code Block cmxos apiserver enable cmxos apiserver restartCMX GUI user for MazeMap with Full Read Only privileges set up on CMX.
CMX CLI API user with full Read and API access. Both CMX GUI and CLI users should have the same username/password
To create a CMX CLI user ssh into your CMX and run the following command:Code Block cmxos apiserver user add
You will be asked to type in a username and password for the user - use the same username and password as you used for the GUI user.
Dependencies
In order to upgrade the LIPI you will need the following:
...