ISE Radius Proxy Licensing and Scaling

[dadelima]

Hi Team, can you please advise for the scenario where ISE is acting as a RADIUS Proxy (External RADIUS server configured):

1) How does this consume licenses (eg 1 base per RADIUS auth proxied??)

2) Scaling performance (auth/s per PSN)

Thanks,

Dave.

[Arne Bier]

Hi @dadelima 

For performance and scaling have a look at this great resource.

Regarding the license consumption - good question.  If the request is proxied by ISE and ISE does not get involved in processing the request (i.e. you tell it not to proceed to Authorization) then there is no license consumption.  But if you tick the box below then ISE gets involved and if Auth is successful then the license will be consumed.

Having said all that, I have not tested this myself but I would be keen to.  If anyone else beats me to it then please let us know.

regards

[Arne Bier]

Hi @dadelima 

I tested it and there is no license consumption when doing radius proxy.  Even if you involve ISE during authorization, it still doesn't consume a license.  I only performed a very simple authorization rule (nothing that would require Plus License like profiling etc.) 

[hslai]

Contrast to Arne Bier's results, mine showed license consumed for each active RADIUS session, which is in line as what in ISE ordering guide.

Whenever in doubt, ask TAC to troubleshoot and escalate to our escalation team, as needed.

[hslai]

IIRC Arne mentioned it in another post that the license counts might take a bit to show. The results might not be accurate when we waiting either not long enough for ISE to display the actual license counts or too long when the sessions already cleaned up if no accounting local to ISE.