Does ISE Profiler CoA Type Reauth apply to PSNs where Profiling Service is not Enabled?

[Arne Bier]

Hello Profiling gurus

In a multi-node ISE 2.3 patch 6 deployment I had a curious incident where only one PSN was enabled for Profiling Service (on purpose) and all the other PSN's did not have Profiling Service enabled.

We were seeing clients being kicked off by CoA on PSN's where Profiling Service is not enabled.

In the Details of the Endpoint I can see "CoA Source Component = Profiler"

Is that expected behaviour? If so, how can one prevent that from happening? e.g. wireless guest users were bouncing all over the place because of this. I don't care about profiling guest users.

After changing the ISE Profiling global setting CoA Type to "No CoA", the clients stopped being kicked off.

I must be missing something ..

[Arne Bier · Accepted solution]

I should have known better ... read the release notes ... patch 7 claims to have fixed something that sounds exactly like my issue

ISE: Endpoints keeps profiling even though profiling is disabled

CSCvi27613