Table of Contents

The MazeMap-CMX integration comprises of three services that must be configured

...

to work together

• The Cisco CMX, configured and hosted by the customer
• The LIPI Server, configured and hosted by the customerThe Siteresolver, configured and hosted by MazeMap

Pre-Installation checks

Requirements for the LIPI server

• • Can be Virtual virtual or physical, does not matter.

  • No OVA currently available, one of the supported OSes needs to be installed.

  • Supported Operating systems: Ubuntu 16.04 LTS, Debian Jessie, RHEL 7, Cent OS 7 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 primePrime, 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.
  • API 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: 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.

Installation Instructions

...

The following assumes that reader is proficient in basic Linux usage and networking

LIPI 

...

Siteresolver

• The private IP address of the LIPI server (the address that WiFi clients will use to connect to the LIPI without traversing NAT)
• The public IP address or range of addresses for the WiFI clients. This is most commonly the public IP address
  of the NAT

Testing the service

Does it work at all?: LIPI debug tool

When you believe the LIPI, CMX and Siteresolver is set up up correctly, the first step is to test it using the debug tool. This will show wether the CMX is able to provide positioning data to the wireless client

1. Go to the following link: https://debug.mazemap.com/lipi
2. Click "refresh" in the top right hand corner
3. If the Siteresolver is set up correctly, the LIPI server will show up in the list

Testing the quality: Visual Debug tool + CMX GUI

Once all tests pass in the LIPI debug tool, the next step is evaluate the quality of the position data. Using this tool, we will evaluate two aspects of the positioning data: update rate and accuracy

• The Visual Debug Tool can be found here: https://debug.mazemap.com/position/
• The URL for the CMX GUI will vary from customer to customer
• Find the client in the CMX GUI, and open the Visual Debug Tool
• Verify that the locations in the CMX GUI and the Visual Debug Tool Match

Common issues

...

Maintenance

...

• of

...

• the

...

• Public addresses,
  NAT
  , IP ranges assigned to WiFi clients
• Virtual networks used by WiFi clients, LIPI, CMX
• Wireless infrastructure
• Routing of wireless clients, LIPI server or CMX
• Firewall configurations that affect Wireless clients, LIPI server or CMX