Cisco Cisco 3365 Mobility Services Engine Technical Manual
Contents
Introduction
Prerequisites
Requirements and topology of solution
Components used
Integrating MSE with ISE
Setting Up Authorization
Troubleshooting
Related Cisco Support Community Discussions
Introduction
This article will demonstrate how to integrate MSE (Mobility Service Engine) with Identity Services
Engine (ISE) for Location based authorization. The purpose is to allow or deny access to wireless
device based on their physical location.
Engine (ISE) for Location based authorization. The purpose is to allow or deny access to wireless
device based on their physical location.
Prerequisites
Requirements and topology of solution
While MSE Configuraiton is out of the scope of this document, here is general concept of the
solution:
solution:
-MSE is managed by Prime Infrastructure (formerly NCS) for configuration, maps creation, and
WLC assignment
WLC assignment
-MSE communicates with the Wireless LAN Controller (WLC) (after being assigned to it by Prime)
using NMSP Protocol. This basically gives information about Received Signal Strength (RSSI)
received per APs for connected clients, which allows MSE to calcultate their location.
using NMSP Protocol. This basically gives information about Received Signal Strength (RSSI)
received per APs for connected clients, which allows MSE to calcultate their location.
Basic steps to do that:
First you have to define a map on Prime Infrastructure (PI), set coverage area on this map, and
place the APs.
place the APs.
When you add MSE to prime, choose CAS service.
Once MSE is added, in prime, choose sync services, and check your WLC / and maps to assign
them to the MSE.
them to the MSE.