ISE Upgrade from 2.7 to 3.2 questions

[asymptote007]

I am performing an ISE upgrade from 2.7 to 3.2 using CLI method. My underlying RHEL version is 7.x on which my VM running the ISE application is built. I've read that post upgrade I need to change the Guest OS to RHEL8.4(64-bit) which includes powering down the VM, changing Guest OS to RHEL 8.4, and powering up the VM after the change. Is there any documentation on how that is done exactly.

I've read that root access is required to upgrade RHEL and that requires a token generated by TAC. So will TAC help with upgradation to RHEL 8.4 ?

[Aref Alsouqi · Accepted solution]

Take a look at this link please, it shows you the steps to do it on VMware as an example:
Manage a Guest Operating System in the VMware Host Client

[balaji.bandi]

Personally i would build new ISE 3.2  with trail license (90days ) and restore the configuration and decomm old ISE 2.7  and move the License to new ISE 3.2 deployment.

below thread discussion have more information :

https://community.cisco.com/t5/network-access-control/ise-2-7-to-3-2-migration-questions/td-p/4891375