12-20-2018 01:12 AM - edited 12-20-2018 01:17 AM
I have a question about ISE policy sets hits.
I build a lab in our Lan with one ISE 2.4 standalone and one cisco 3560E as NAD and running some MAB test.
There is a core switch between 3650E and ISE, 3650E use a trunk uplink, on ISE I only created one policy set, with wired MAB condition.
After testing ,endpoints are removed from 3560E , but I observed that Default policy set hits keep increasing slowly.
Don't understand why this happens, the only possible reason i know are profiling and device tracking, any idea?
Solved! Go to Solution.
12-20-2018 06:58 AM
If you are doing RADIUS keep-alive checks on the switch and haven't built a policy set to capture that you are probably seeing that. The live logs should tell you what is hitting the default policy set. I usually set the default policy set to Deny Access because I don't want anything allowed on via the default policy set. Honestly I wish Cisco would get rid of it as we have to disable it on every install.
12-20-2018 05:45 AM
Have you removed accounting as well from your network devices?
ISE evaluates the policies for accounting requests as well for the RADIUS probe to work. I am suspecting that this could increase the number of hit counts. On the other hand, ISE is slow to update the hit counters. They were increasing for the tests that you have done previously may be?
12-20-2018 06:58 AM
If you are doing RADIUS keep-alive checks on the switch and haven't built a policy set to capture that you are probably seeing that. The live logs should tell you what is hitting the default policy set. I usually set the default policy set to Deny Access because I don't want anything allowed on via the default policy set. Honestly I wish Cisco would get rid of it as we have to disable it on every install.
12-20-2018 01:33 PM
Hard to say without seeing configs, but it almost looks like it's trying dot1x, and since that isn't there hits the default. You can also check the default network access protocols and make sure Process Host Lookup is selected as that is MAB. If it's unchecked MAB isn't allowed.
06-20-2019 09:51 PM
Hi
Same Problem here but with Wireless. Clients on Corporate SSID gets Authentiacted by the right Policy Set for Dot1x, but the Counter on the Default Policy Set is increaseing. Inside of the Default Policy Set no hits on AuthZ and AuthP Policy.
@davoodccnp Could you resolve this issue?
Regards
Thomas
06-21-2019 03:54 AM
08-28-2019 03:16 AM
Did you find anything about your issue ?
I've the same problem with my default policies : hits on policy sets are increasing but 0 hit on authentication and authorization rules, and nothing on the live logs either.
Marie
08-28-2019 04:10 AM
Hi Marie
No solution yet. Cisco TAC Case is still open.
Regards
Thomas
02-05-2020 02:07 AM
same issue here. Any news on the TAC Case ?
02-16-2020 11:17 PM
Hi
Still no solution for this problem.
Regards
Thomas
02-16-2020 11:21 PM
Hi
The case is still open. Problem is still existing.
Regards
Thomas
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