02-26-2019 12:20 AM - edited 03-08-2019 07:14 PM
Dear Team,
Is there any documentation regarding recommended latency between users and ISE nodes ?
I have customer with users across 100+ sites, and latency between sites and ISE in HQ is around 200ms.
Regards,
Omar
Solved! Go to Solution.
02-26-2019 10:48 AM
There are two pieces here, but what you are asking is not exactly an ISE thing but a general radius concept. ISE has a very high timeout interval, 120 seconds.
Latency between ISE nodes and the PAN, less than 200 ms or 300 ms depending on the version you are running.
And then the second which is the latency of radius authentication (user/endpoint/NAD). What you have to pay attention to here is the latency between the NAD (Switch/WLC), ISE, and the ID store. Usually referred to as the radius timeout interval, it's usually set at something like 5 seconds by default. I have seen issues where an aggressive 1000ms radius timeout is set on a WLC and it causes problems when ISE or AD cannot process the request quick enough.
The radius timeout interval is usually configurable on all devices, but there is always a default. The time has to include everything in the authentication path, RTT of ISE and NAD, time it takes ISE to authenticate the device, time it takes AD to respond.
If you can stay under 5 seconds then you are unlikely to have issues with default timers. I would check the WLC's though.
02-26-2019 01:45 AM
02-26-2019 10:48 AM
There are two pieces here, but what you are asking is not exactly an ISE thing but a general radius concept. ISE has a very high timeout interval, 120 seconds.
Latency between ISE nodes and the PAN, less than 200 ms or 300 ms depending on the version you are running.
And then the second which is the latency of radius authentication (user/endpoint/NAD). What you have to pay attention to here is the latency between the NAD (Switch/WLC), ISE, and the ID store. Usually referred to as the radius timeout interval, it's usually set at something like 5 seconds by default. I have seen issues where an aggressive 1000ms radius timeout is set on a WLC and it causes problems when ISE or AD cannot process the request quick enough.
The radius timeout interval is usually configurable on all devices, but there is always a default. The time has to include everything in the authentication path, RTT of ISE and NAD, time it takes ISE to authenticate the device, time it takes AD to respond.
If you can stay under 5 seconds then you are unlikely to have issues with default timers. I would check the WLC's though.
03-01-2019 02:15 AM
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