Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

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 customer
  • The Siteresolver, configured and hosted by MazeMap


Pre-Installation checks

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.
    • 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








  • No labels