02-21-2018 02:37 AM - edited 02-21-2020 10:46 AM
I am configuring an ISE 2.3 environment with 2 nodes
When debugging the dot1x authentications in a 2960x switch I get the following
157525: Feb 21 10:36:10.562: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.0.10.20:18112,1813 is not responding.
157526: Feb 21 10:36:10.562: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.0.10.20:18112,1813 is being marked alive.
157527: Feb 21 10:36:13.582: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.0.10.20:18112,1813 is not responding.
157528: Feb 21 10:36:13.582: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.0.10.20:18112,1813 is being marked alive.
157529: Feb 21 10:36:16.633: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.0.10.20:18112,1813 is not responding.
157530: Feb 21 10:36:16.633: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.0.10.20:18112,1813 is being marked alive.
157531: Feb 21 10:36:19.667: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.0.10.20:18112,1813 is not responding.
157532: Feb 21 10:36:19.667: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.0.10.20:18112,1813 is being marked alive.
157533: Feb 21 10:36:22.715: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.0.10.20:18112,1813 is not responding.
157534: Feb 21 10:36:22.715: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.0.10.20:18112,1813 is being marked alive.
157535: Feb 21 10:36:25.756: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.0.10.20:18112,1813 is not responding.
157536: Feb 21 10:36:25.756: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.0.10.20:18112,1813 is being marked alive.
157537: Feb 21 10:36:28.787: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.0.10.20:18112,1813 is not responding.
157538: Feb 21 10:36:28.787: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.0.10.20:18112,1813 is being marked alive.
Is this an issue?
Solved! Go to Solution.
02-21-2018 06:38 AM
Are you using a different port than the default 1812 for ISE?
I notice in the logs 10.0.10.20:18112,1813
I am guessing this is a typo when you were setting up the radius config on the switches?
It seems like it can hit the ISE server on 1813 but not 1812 which is probably causing some confusion in the switch if the server is actually up or not.
02-21-2018 06:38 AM
Are you using a different port than the default 1812 for ISE?
I notice in the logs 10.0.10.20:18112,1813
I am guessing this is a typo when you were setting up the radius config on the switches?
It seems like it can hit the ISE server on 1813 but not 1812 which is probably causing some confusion in the switch if the server is actually up or not.
02-21-2018 07:18 AM
Thanks, this was actually the issue, a misconfigured port on one of the Radius servers - changed to 1812 and warning goes away.
Thanks
01-07-2019 07:42 PM
Hi Roger, I have the same problem with two new 2960 switches in the network. How did you solve this issue?
Thanks and Regards,
04-19-2019 04:14 AM
I am also facing the same issue in C2960 switch. Please guide us to fix it.
@Sdiana wrote:Hi Roger, I have the same problem with two new 2960 switches in the network. How did you solve this issue?
Thanks and Regards,
11-12-2019 08:28 AM
Same here, any update?
06-13-2024 08:33 AM
Hi guys, any updates about 2960?
06-13-2024 08:42 AM
I use Catalyst 2960 in several of my projects without any issues. If you are certain the ISE configuration is correct, an IOS upgrade may resolve your issue.
06-13-2024 08:49 AM
Thank you for your reply.
My scenario is:
We are migrating our devices from PEAP to TEAP. Supplicant policy is pushed by GPO. On all devices(laptops) on other switches works everything correctly. Only this one switch (WS-C2960-24TC-L) has a problem. When I plug device with same GPO policy from this switch to other switch, which has a same configuration i got a problem with dot1x.
Many thanks.
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