ISE 3.4p5 stability question

[ropery22]

Hi! Has anyone managed to play around with 3.4p5 release from a few days ago? How has the experience been so far?

I did the silly mistake and didn't go with the golden star - instead went with patch4 and now I've spent weeks juggling cases with TAC engineers (they're not so fond of patch4 themselves). My deployment has gotten a bit more stable, but not to the point where I'm happy with it (still getting dashboard spammed with false positives).

I'm afraid to rollback to patch3 as there are reported cases of new issues arising after coming back from patch4.

[Mark Elsen]

  - @ropery22     What are the essential problems you are facing + can you elaborate with detailed descriptions ?

  M.

[Arne Bier]

@ropery22 - I agree - patch 4 has to be one of the dodgiest patches in a long time - for me it's resulted in six TAC cases, and patch 5 apparently solves two of those cases.  It should fix the constant  "Log Collection error" Alarm as well as the Context Visibility missing most of the endpoint details.  It also appears that you run into the most stupid bug because you follow a certain patch path - e.g. I went from p3 to p4 and picked up bugs that others won't have if they went directly to patch 4.  Upgrading and patching ISE is like playing a game of roulette.

I have a lot of understanding for suffering through bugs with new complex features - but I can't recall the last time I upgraded because I wanted new ISE features. We upgrade to fix bugs - constantly- but this silly game the BU plays with breaking things that used to work is very time consuming but it doesn't get any better over time.

[beepmeep]

Sums up my experience pretty well... I have a customer that went 3.4P3 -> P4 for some reason I can't recall. He called me this morning because the application crashed due to disk being full. Spent 3-4 hours with tac cleaning up the system and eventually found that a M&T db reset a month ago had messed up some DB credentials...

I just discussed P5 with my customer yesterday and decided to wait a few weeks, so I'll be interested to read any experiences in this thread.

[Marcelo Morais]

@ropery22 ,

 please take a look at: ISE - CVE: release 3.x ., pay special attention to First Fixed Release column of all 3.4 .

 ISE 3.4 P3 is a stable version, but take a look for related vulnerabilities that may affect you.

PS: I preferred to update my Customers to 3.3 P9, which IMHO is much more stable than 3.4 P4 and 3.5 P1. I will test 3.4 P5 and 3.5 P2 next week.

Hope this helps !

[Arne Bier]

3.4p5 so far seems ok (I have not noticed that it's made anything worse than before). The constant "Log Collection" alarms have stopped (touch wood).

I like the idea of ISE 3.5 but I don't like the licensing change that the BU will implement. I think ISE 3.4 will become the last bastion of resistance 🤣

[Marcelo Morais]

@Arne Bier 

---

@Arne Bier wrote:

3.4p5 so far seems ok (I have not noticed that it's made anything worse than before). The constant "Log Collection" alarms have stopped (touch wood).

I like the idea of ISE 3.5 but I don't like the licensing change that the BU will implement. I think ISE 3.4 will become the last bastion of resistance 🤣

---

Thanks, good to know !

Are you using VMs compatible with SNS 38x5 in your 3.4 P5 Cluster ? If so, have you noticed any improvements ?

[Arne Bier]

@Marcelo Morais I have not laid eyes on an SNS-38x5 yet. I have some lined up for two different deployments but due to the current memory shortages the server shipments will be delayed.

[Eager_2_Learn]

Hi, anyone who has had more hands on with Patch 5 got anything further to add? Considering a move from P3 to P5 to address some annoying alarms and buggy context visibility.

Cheers

[Marcelo Morais]

@Eager_2_Learn ,

 ISE 3.4 P5 is the Suggested Release, and it's far more stable than ISE 3.4 P4, please take a look at ISE - Software Download.

PS: for ISE 3.x Field Notices and CVEs:

ISE - Field Notice: release 3.x

ISE - CVE: release 3.x

Hope this helps !