ISE upgrade

[sujanyakj]

We are having sns3595 medium vm with release 2.4 ISE box. We are planning to upgrade to ISE release 2.7 sns3595.

In the cisco document, it was mentioned that the compatible RHEL release is 7.6 for ISE version 2.7

As per the linux team, we got the confirmation that they are having linux Server with RHEL 7.

If i download the upgrade bundle from cisco for relaese 2.7 , would that be compatible with server requirements.

[ahollifield]

Why are you upgrading to ISE 2.7?  https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-2943876.html

You should upgrade to 3.1.  

It would also be advisable to redeploy the 36XX 3.1 OVA from scratch and then import the ISE configuration backup.  Rather than upgrade your existing VM.

Only ISE 2.6 and later can upgrade to 3.1.  So you will need to deploy a new 2.6 node, import 2.4 backup, backup 2.6, and then import 2.6 config into 3.1.

[sujanyakj]

Hi @ahollifield ,

We have plans to move to 3.1 release in future as it dependency on VM common license.

[ahollifield]

So why spend the effort now to move 2.7 on an old VM license?

[Marcelo Morais]

Hi @sujanyakj ,

1st

. ISE 3.1 supports upgrade from: 2.6+.
. ISE 2.7 supports upgrade from: 2.2+.

2nd

. Release 3.1 supports RHEL 8.2.
. Release 2.7 supports RHEL 7.6.
. Release 2.4 supports RHEL 7.3.

3rd

. ISE 3.0+ ONLY supports Smart Licensing !!!

. If you’re using the Old VM License (i.e., R-ISE-5VM-K9=), you should migrate the Old VM License to the legacy VM Medium License (R-ISE-VMM-K9=) and then migrate the legacy VM Medium License to the VM Common License !!!

. Customers who are on ISE 2.X and ISE 3.0 can continue to use the legacy VM Licenses until the EOL Date of the Licenses. They also can migrate the legacy VM Licenses to the VM Common License and stay on ISE 2.X or ISE 3.0 !!!

Hope this helps !!!