I have found clarity fairly useless for discovering problems, giving what I consider to be false positives. Your clue about server time vs client time is interesting, though. I have been able to confirm that our server time is close to our radtest monitoring statistics and that the client time is substantially longer. What takes the client so long?
-- Jason Trinklein Wireless Engineering Manager College of Charleston 81 St. Philip Street | Office 311D | Charleston, SC 29403 trinkle...@cofc.edu<mailto:trinkle...@cofc.edu> | (843) 300–8009 From: The EDUCAUSE Wireless Issues Constituent Group Listserv <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of "Enfield III, Charles Albert" <cae...@psu.edu> Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Date: Thursday, March 15, 2018 at 2:03 PM To: "WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: Re: [WIRELESS-LAN] Measuring RADIUS Performance One more note about clarity. If you click the details link underneath the summary of RADIUS stats, you can see some additional details on a per-server basis, including how much of the auth time is spent waiting on clients vs. waiting on servers. You may well find that most of your auth time is spent waiting on the clients, in which case you’re currently worrying about the wrong end of the channel. From: The EDUCAUSE Wireless Issues Constituent Group Listserv <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> On Behalf Of Adam Forsyth Sent: Thursday, March 15, 2018 11:44 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Measuring RADIUS Performance How do you measure the performance of your RADIUS Serve? How fast is fast enough? How slow is unacceptable? We have Aruba Airwave, and its Clarity module provides me a way to measure the amount of time that RADIUS Authentication takes. For our RADIUS MAC SSID's it says it takes 63ms, and for our 802.1x SSID it says 2392ms. The settings Airwave comes with by default are that <500ms is marked green meaning good, 500 -- 1000ms is marked yellow meaning warning and >1000ms is marked read meaning poor. Of course faster is always better, but I wondered if others have opinions on whether Airwave's ranges are reasonable, or whether they have unrealisticly expectations. If they're reasonable, then I probably need to figure out how to speed up our 802.1x RADIUS performance. -- Adam Forsyth Director of Network and Systems Luther College Information Technology Services 700 College Drive Decorah, IA 52101 563-387-1402 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.educause.edu%2Fdiscuss&data=02%7C01%7Ccae104%40psu.edu%7C8fb05e92444d42a67ada08d58a8ba2e9%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636567254735627116&sdata=v84pG9Rr4O6YVP%2Fqdxkscx9t%2F2NrgOhWEk92x4mZxxg%3D&reserved=0>. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.educause.edu%2Fdiscuss&data=02%7C01%7C%7Cff39a5bd830843bb656a08d58a9f12bc%7Ce285d438dbba4a4c941c593ba422deac%7C0%7C0%7C636567338183117924&sdata=4goKgPwpiMSfebSI1NRsZ3osuaOhVg0o72oAbEek9X8%3D&reserved=0>. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.