ISE Mobility License feature usage

[mpatel002]

 In a standard deployment if a rule uses both auth and profiling it would consume a base license and a plus license if you also needed posture you would need a Base, Plus and a Apex License. 

For the mobility license would  Auth + Profile + Posture consume 1 license or would it console 3 licenses (one for each feature) 

[Marvin Rhoads]

Yes.

It's the same as in the non-mobility licensing scheme except that it's restricted to wireless clients.

The other difference is that with Mobility you always have an equal number of Base, Plus and Apex licenses.

Without Mobility you can have fewer clients using Plus license features and fewer still using Apex if that suffices to cover your use case scenarios.

[mpatel002]

Just to be sure I size this right would a Mobility 100 endpoints license include 100 base,  100 plus and  100 apex licenses  so you could Auth and profile  100 endpoints or would the 100 endpoints be divided between Base Plus and Apex licenses so to Auth and  Profile 100 endpoints so  I wold need move up to the Mobility 250    

[Marvin Rhoads]

The Mobility 100 endpoint license would allow you to Authenticate/Authorize, Profile and perform Posture enforcement all simultaneously on 100 unique wireless endpoints.

A given endpoint type may not consume, say, the Posture services but it's not like another one could in it's stead because Posture doesn't exist independent of AuthC/AuthZ.

The licenses are consumed when the action is performed and not released until the client is disassociated from the WLAN.