ISE sizing

[tachyon05]

Is ISE sizing the same for on prem and AWS deployments?

The sizing guide seems to state ISE small, medium, and large sizes can be determined based on max # of concurrent sessions.  Where can I see the current concurrent session and historical concurrent session counts?

Does the pic below indicate a small deployment using 3715 can handle 25,000 concurrent sessions?

[ahollifield]

What version are you currently running?  In 2.X yes you can see this.  In 3.X no.  You can get some general data from Log Analytics in 3.2+.

Yes.

https://cs.co/ise-scale 

https://cs.co/ise-cloud 

[tachyon05]

We are running 3.2, and I just enabled System 360.  Where can I see this data in Log Analytics?

[ahollifield]

You can look at the RADIUS Authentications reports in there.  Note that Log Analytics is a separate checkbox from System 360.  Again, this does not give you license utilization over time but will get you general RADIUS authentication stats.  Also note that Log Analytics only has a 7 day retention time.

[tachyon05]

Thanks.  It looks like info presented in Log Analytics are about total authentication counts, and it goes into details about count of passed, failed, by identity groups etc., but I don't see where it tracks concurrent count.  I am trying to figure out how to size my ISE deployment since the differences in small / medium / large deployments are based on concurrent active sessions.  

The total count 2497, or the passed and failed counts, shown below is not the same as concurrent active sessions, right?  If not, where can I find this info?

[ahollifield]

It depends on the time filter you have selected. Those are total auths for that time period yes, not necessarily concurrent. This is just for a base-line to give you an idea. Unfortunately ISE 3.X does not currently track historical license utilization