04-18-2018 09:49 AM
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?
Solved! Go to Solution.
04-18-2018 03:52 PM
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.
04-18-2018 03:52 PM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide