been getting these messages lately in the logs. For the same configuration/client/setup/etc most of the time it's ok.
For example for one client in a day it makes 10 auth's and only one of them ends with a log message like in the subject.
One more thing that is common is that these radius auth's come from branch office devices so I was thinking there's something to do with maybe transport delay's or similar.
It's kind of difficult to troubleshoot because it happens when it happens and leave on massive logging for days is not a first step.
Does anyone have any experience with similar log entries.
Here is a same post for your reference.
Yeah, I saw that post.
But as I mentioned most of the time it's ok - authentication goes through ok.
No configuration change on the IC cluster.
And I also checked - the radius client is a member of group that is again tied to a sign-in policy that again is associated only with one realm.
I just pulled it out from the documentation, and should help to understand the relam selection in IC. I think whenever you are having the issue, the client may be requesting Authentication protocol which is not part of the available realms.