![]() ![]() Each VM you enable the TACACS device admin persona will require a TACACS node license. Not mentioned by those above is that TACACS licensing has also changed to per node. Expect this to change in the future where customers will be given a grace period for extra VM's and then there will eventually be a hard enforcement. ![]() ISE v2.4 is not enforcing VM licensing today but it does nag you in the GUI and also with alarms in the dashboard if you are not compliant. The new licenses will be issued as a PAK key and can be fufilled online via the licensing portal, you then install the VM licenses just like endpoint licenses. So the complications are going to be if a customer only bought 2 VM licenses and have since grown their deployment and are now using more. The ISE BU will take however many VM licences were bought in the past and convert them one to one for R-ISE-VMM-K9=. I think this is the hardest part for some customers, often these things get lost with time. When an ISE environment is upgraded to v2.4 you email and either provide the Cisco sales order number the traditional VM licenses were purchased on or attach the original SO if you have it. All existing customers should have bought traditional VM licenses when and if they deployed their pre v2.4 ISE VM's. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |