Page Comparison

We now have a simplified way of installing the LIPI program indoor positioning software using our new CLI Tool. This is a comprehensive document about LIPI and is divided into 5 parts :as shown below.

Please note that you will still need to involve someone who has access to the LIPI server, has experience with SSH and Linux, and preferably has access to CMX GUI. More details regarding prerequisites are discussed in the Part V of this document.

...

• If the MazeMap API key is set, the tool can download new versions of lipi and
  the configuration file from MazeMap servers.

• After running initial --setup, the tool will install a cron task which regularly
  runs the command lipi --status report. This will send lipi health data to MazeMap
  on a regular basis so that we can provide a better level of service to you. This is
  only installed if the MazeMap API Key is set during setup. If this is not installed
  we can not help debugging an installation, and we will not be able to help users
  if they have trouble accessing the LIPI service. See Run status check, and report to MazeMap
  to see what is reported to MazeMap.

• When installing a new version of LIPI, the update tool will prefer to use the
  configuration files of the currently running LIPI version. This can be overridden
  using the --config-path flag or by running --update-config before running
  --install.

• Every --install and --update-config creates a new installation version. This
  is done to allow switching between new and previous installations or configurations
  at will. If something goes wrong, a previous version can be activated using
  --activate. The installation or update process will activate the previous version
  if the new version can't be started or seem unresponsive (if --status does not
  show a fully healthy installation).

Manual fixing:

• --setup stored values in a file params.txt. Running --setup again will overwrite it.

• A LIPI service has a config.json in its installation folder, which can be copied,
  edited and used using --config-path, if needed.

• The folders under LIPI installation path are self contained and can be deleted at will.
  Just make sure to not delete the running version. Use --list or --status to see which
  version is running.

• LIPI is started using systemctl. Status and control of that service is available.
  systemctl [status|start|stop|restart] lipi.service.

...

• 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 API server

    Code Block
    cmxos apiserver enable cmxos apiserver restart

  • CMX GUI user for MazeMap with Full Read Only privileges set up on MSE/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

...