Logo

Cisco Mobility Services Engine

Menu path: Configuration > Integration Overview > Cisco Mobility Services Engine.

The Cisco Mobility Services Engine (MSE) provides clients location information to A3. This information is used to filter client Connection Profiles usage, effectively offering location-based captive portals.

MSE Configuration

  1. MSE must be hosted on a server and access points equipped with CMX software.
  2. A user name with write permission must be established. They will be referred to as msewrite and password.
  3. Notifications must be established for each zone that will be used to filter Connection Profiles. This is done with the MSE Web UI and must specify a zone and notification name. For example, zone=Campus>Building>Level>Zone and notification-name=Zone1.

A3 Configuration

  1. Create or modify one or more Connection Profiles to be used for individual locations, filling in the Advanced filter field with specifications of the form:

extended.mse_inout.locationMapHierarchy == "<zone>"

For example:

extended.mse_inout.locationMapHierarchy == "Campus>Building>Level>Zone"

  1. Create the MSE definition. The fields in the form for the engine's definition are:
Field Usage Example
Enable MSE Enables use of MSE location data. slider on icon
URL of MSE Service The URL used to access the MSE service. http://192.168.1.6:8083
User Name The user name of an MSE account with write permission. admin
Password The password associated with User Name. secret
Note

Note

NOTE: the httpd_collector service must be started to use this service using STATUS>Services.

When everything is operational, clicking on a MAC address in the Clients table will offer a new tab with the map and localization of the device.

Copyright © 2021 Extreme Networks. All rights reserved. Published April 2021.