The back story… you’ve deployed your ISE appliance and the world is great! Your management need you to make a change “right now” but that virtual machine in the lab you have been using for testing is 91 days old and the eval no longer works. You raise a case to get budget and a PO over to Cisco for a lab ISE appliance or license but this change is critical, if only there was a way to use your appliance license on your VM?
Perhaps you should log into your ISE appliance and make a note of the Product Identifier (PID), Version Identifier (VID) and the Serial Number (SN).
What you might want to do now is shutdown your ISE VM and mount the disk… I always have a CentOS server kicking around for this kind of thing, so if I was to do this, I would mount the ISE virtual disk as an extra disk that CentOS has access to.
From within CentOS you can use fdisk -l to view the hard drive partitions… When you’re hacking a VM you mount as many of the ISE partitions as you can (some will fail) to see what’s there. On my test machine
/dev/sdb7 was the partition of interest as it had an
/opt directory (cisco always install stuff in opt).
mount-point/opt/system/bin/ you might find a file called
cars_udi_util, that’s the puppy that the license is bound to.
What you might want to do is rename that file and replace it with something that always gives the “right” answer. Attached is cars_udi_util.txt, a shell script I have been testing, edit the top of the file and insert the PID/VID/SN you found earlier.
Now save the cars_udi_util.txt to
mount-point/opt/system/bin/cars_udi_util, that’s right remember to remove the
Unmount the disk, shutdown Centos and boot up ISE.
Now I’ve been hacking my machine and after this change the services wouldn’t start (
show application status ise) to fix that I ran
application reset-config ise from the ISE CLI Shell, rebooted and Voila! …The machine booted up with a blank default config.
After changing the default admin password (from cisco) it would now be possible for you to use your proper appliance license on your VM… of course this is only a temporary thing and I fully expect & recommend you undo these changes as soon as your new license arrives from Cisco.