cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Announcements
Choose one of the topics below to view our ISE Resources to help you on your journey with ISE

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.

521
Views
1
Helpful
1
Replies
Highlighted
Beginner

ISE 2.2/2.3/2.4 Smart Licensing

Good morning, Customer has a smart account and a Virtual account and 2 "product instances" for ISE. When we connect a third ISE deployment to SSM, one product instance goes away and we still only 2 product instances. Is this a known limitation?

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
VIP Advocate

Re: ISE 2.2/2.3/2.4 Smart Licensing

Which license are you talking about?  They all work a bit differently

BASE License - only gets consumed when an associate product (i.e. ISE PAN) requests it

TACACS license - gets consumed straight away and disappears from the pool (1 license consumed per deployment)

APEX/PLUS - same as BASE license.

SO in summary, if you only purchased 2 TACACS licenses, then you cannot enable TACACS on the 3rd ISE deployment.

But all the other licenses can be sliced and diced as you like it.  It's good practice perhaps to assign a different virtual domain for each deployment, from which you then create the token and register your deployment's PAN.

View solution in original post

1 REPLY 1
Highlighted
VIP Advocate

Re: ISE 2.2/2.3/2.4 Smart Licensing

Which license are you talking about?  They all work a bit differently

BASE License - only gets consumed when an associate product (i.e. ISE PAN) requests it

TACACS license - gets consumed straight away and disappears from the pool (1 license consumed per deployment)

APEX/PLUS - same as BASE license.

SO in summary, if you only purchased 2 TACACS licenses, then you cannot enable TACACS on the 3rd ISE deployment.

But all the other licenses can be sliced and diced as you like it.  It's good practice perhaps to assign a different virtual domain for each deployment, from which you then create the token and register your deployment's PAN.

View solution in original post