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 we will try to implement ssl decryption on the Ironport and I was thinking if there is a way to block file typessuch as exe,pdf...) when Ironport decrypts SSL cert . I know how to do this for http traffic but was not sure how to configure it ...
Hi All, Quick design question. I have a WLAN that right now I send our AAA request to ISE. (ISE version 2.4) and I have two ISE nodes a Primary and a secondary. Would it be good practice to add my secondary node to the second server list on the WLAN....
Hello guys, I have a ipsec tunnel with a juniper device on the other end. we have to internal subnets : 192.168.25.0 and 192.168.135.0 The tunnel is only coming up with the first subnet and i can ping the other side 172.20...
Hello, I attempted to migrate anyconnect from ASA to FTD. We currently authenticate users using certificates only. The certs are issue to domain machine via our internal PKI. I exported the pkcs for the public cert and enrolled in FMC and that worke...
Hi Everyone. I've been trying to setup a simple network which has 1 firewall, 1 switch and 2 PCs. Please see the attachment for the topology. My goal is that I want my PCs can ping 188.8.131.52 of the 'internet' switch (from my attachment). But...