About a year ago, we have started a journey to make ISE even more the robust solution our customers expect it to be.
This journey is a journey everyone subscribed with – our Engineering team have and are investing a huge amount of resources to ensure that ISE’s code is simply better, in terms of robustness and quality, our testing environments are better and continually improving, our processes are better in terms of maintaining high quality, and today we are announcing another milestone in this journey. ISE 2.4, our latest release, had made it to the “Suggested Release” milestone!
We are pleased to announce that version 2.4 of the Identity Services Engine (ISE), a Long Term Release, is now tagged as the “Suggested Release” for all customers. This version was initially released on March 29, 2018 and 2.4, Patch 5 was released on Nov 27, 2018. Tagging ISE 2.4 as the “Suggested Release” is a big step forward in delivering quality software to our customers. Prior to this, we had two different “suggested releases” for two different types of customers. With this step, we now have a single release that has been really stable in hundreds of customer deployments.
Call for action - upgrade to 2.4 patch 5 (or latest 2.4 patch):
All customers looking to deploy ISE, whether as a standalone product or as part of their Cisco Software Defined Access deployment together with Cisco DNA Center, are encouraged to check out the 2.4 release with Patch 5 at least. For more information about the 2.4 release, please visit product support.
To make it easier for customers to make the right selection of software, when a user goes to cisco.com’s download center, the “Suggested Release” would have a star icon tagging it as such:
In order to ensure we are focusing our investment, in parallel to this announcement we have announced the End of Sale of ISE 2.0, 2.0.1, 2.1 and ISE 2.3. While customers will still receive full support for these releases prior to these release transition into the “Maintenance Support” phase, we do believe that customers should migrate to ISE 2.4 as soon as possible. Please consult the EoS bulletins below for additional information.
What's in a number?
On a slightly more forward-looking note, we'd like to take the opportunity and update that we will be naming / numbering our coming release 2.6 and not 2.5 as we originally planned. As 2.6 is also going to be a release full of capabilities and improvements, we'd like to make it a long term release. For sake of simplicity, we're trying to keep our long term releases (LTRs) numbered even. So no content change, no date change - just the number changes.
Hi, I am trying to set up a site to site VPN for one of our client with palo alto. However VPN phase 1 is not coming up and when I ran debug I am getting NO_PROPOSAL_CHOOSEN error even though both side are configured poperly setup is like b...
Remote Site - to HQ - Redundant ISPHello,I have am having an issue with a remote site redundant IPSEC tunnel config. When the remote site is on the primary IPSEC tunnel, the traffic from Host A to Host B is successful. When the primary link fails, t...
Hi everyone, I encounter a problem that really strange and tried different ways can't solve the ASA 5515 9.1 not able to allow traffic from inside to outside.Any suggest much appreciated. Keith Here is the sanitized config:asa# sh run: Saved:ASA Vers...
Is this considered a major upgrade or minor? I need to upgrade my Active / Standby Failover pair with 0 downtime. I will upgrade standby and reboot, when it comes up with 9.9 code, will it break the failover with 9.8(4)3 or stay in failover with erro...
Hi all,I'm working on setting up an IKEv2/IPSec VPN tunnel from an FTD (6.2) managed by FMC to Azure. The tunnel is up and icmp is working fine but our server engineer is reporting issues with RDP and domain controller replication.We're wondering if...