05-14-2020 06:43 AM
Hi Guys,
I am having a little issue with our Cisco ISE setup, the issue being that for some reason cisco ISE is generating a authentication failure log from every switch we have configured.
It is failing our RADIUS-TEST user which is configured locally on the switch to test radius connectivity.
I was wondering if anyone else had this issue and how they resolved it?
Solved! Go to Solution.
05-17-2020 07:25 AM
In order to avoid the failed authentications, the radius-test user should ideally be a valid user from the persepctive of your ISE deployment. It can be local to ISE as long as ISE-local authentication is in your identity source sequence.
05-14-2020 07:43 AM
If i understand correctly Local user in switch can not communicated with ISE right ?
and you need ISE username / Password to test again Radius test with ISE - is this make sense ?
05-14-2020 07:56 AM
Basically when we look at our live logs, we are seeing errors for the username of our RADIUS account to test connectivity.
I am not sure if this is the local account configured or the automate-tester causing this issue?
I have also noticed when I do test aaa etc new-code we get user rejected, are the two linked?
For example we get below error in the log:
5405 RADIUS Request dropped
24412 User not found in Active Directory
However this is not an AD user it is a user configured on the access switch.
05-14-2020 01:28 PM
at this time not sure, we need more information and Logs, how your ISE / Switch configured.
05-17-2020 07:25 AM
In order to avoid the failed authentications, the radius-test user should ideally be a valid user from the persepctive of your ISE deployment. It can be local to ISE as long as ISE-local authentication is in your identity source sequence.
05-19-2020 03:31 AM
Hi Marvin,
Thank you for your help.
That seemed to resolved the failed authentication issue I had to then create a authorization rule to permit it after.
I was just wondering It's great that it now passes all checks however, as we have over 100+ switches you can imagine what the logs will look like when the user is checked against constantly is there a way to stop this over populating the logs?
Kind regards
Kalid Orfally
05-19-2020 04:53 AM - edited 05-19-2020 04:55 AM
Sure you can suppress events for that user.
We often do this when there is a load balancer in front of PSNs that send regular queries as health checks.
Here's a good blog post showing exactly how to do it:
...and the Admin Guide reference:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide