Radius server unreachable events
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2020 05:10 AM
vSZ version 5.2.0.0.699 with 411 R710s APs on campus. Every few days we are getting a bunch of radius server unreachable events. What is odd is the details of the event do not even point to our radius server. All events are reported like this
AP [Int301@F8:E7:1E:2A:A4:40] is unable to reach radius server [127.0.0.1].
Of course 127.0.0.1 is not our radius server. We are using Cloudpath as our radius server. Our wifi is rock solid so there are no other symptoms other than a rash of these events every few days.
Any ideas what causes this?
AP [Int301@F8:E7:1E:2A:A4:40] is unable to reach radius server [127.0.0.1].
Of course 127.0.0.1 is not our radius server. We are using Cloudpath as our radius server. Our wifi is rock solid so there are no other symptoms other than a rash of these events every few days.
Any ideas what causes this?
63 REPLIES 63
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2020 09:10 AM
Is there a patch for 5.2.1 or just 5.2.0?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2020 05:14 AM
Hello Jeronimo and Raymond,
Can you please open up a TAC case so that we can verify if you are facing same issue on your setup and all details would be shared by the case. This issue has been seen on 5.2.0 (with few customer's only) and reload of controller or restart of radiusproxy service resolve's it, hence it is necessary to validate the logs before applying the patch. @EightOhTwoEleven On 5.2.1 we do not have this issue validated as of now.
Best Regards
Vineet
Can you please open up a TAC case so that we can verify if you are facing same issue on your setup and all details would be shared by the case. This issue has been seen on 5.2.0 (with few customer's only) and reload of controller or restart of radiusproxy service resolve's it, hence it is necessary to validate the logs before applying the patch. @EightOhTwoEleven On 5.2.1 we do not have this issue validated as of now.
Best Regards
Vineet
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2020 02:02 PM
You mean this problem?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2020 10:19 PM
I have a fresh 5.2.1 vm and still have the same issue.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2020 08:17 PM
I have opened a case about this problem.

