Identity Collector 82.129 and Cisco ISE 3.2

[Alex-]

FYI, we observed a massive drops of accepted events between a Cisco ISE and and the Identity Collector when upgrading to version 82.129. We're talking of about 10% accepted events against the usual amount.

Rebooting the server and so on din't resolve the issue.

Reverting to 82.126 solved the issue which has been very stable with Cisco ISE so far.

If this isn't a known issue, I suppose we'll have to go through TAC.

[PhoneBoy]

Definitely sounds like a regression of some sort.

[the_rock]

Hey Alex,

Based on my online search, it would appear this is indeed a limitation, but no official statement/sk about it, so most likely its best to open TAC case.

[Chris_Atkinson]

To clarify were they valid events that correlated with impacted end users being dropped or just raw numbers?

[basels1]

Hi @Alex- 

Could you please share the SR number?

Have you encountered enforcement issues eventually?

Thank you,

Basel Saad | Identity Solutions Team Leader

[Alex-]

We didn't make a ticket as it's a production environment and we had to get this working.

However, the customer proposed to create another VM with just the collector integrated to ISE and not linked to the gateway , running the latest version, so we could do an SR.

[the_rock]

It would be good to know, for sure.