10-31-2023 07:06 AM - edited 10-31-2023 07:23 AM
We are bombarded with these rejected events. This is working as designed, correct? All of our VOSS switches are set to check reachability every 3 minutes. It seems odd that the check is performed with a rejection, maybe that's standard procedure.
Is Status-Server mode any more efficient (RFC 5997)?
Solved! Go to Solution.
11-01-2023 05:33 AM
Hello,
Check out:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000112893
Also, consider using the reachability checks to reduce load on XIQ-SE if large numbers of healthchecks are being sent:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000100006
Thanks
-Ryan
11-01-2023 06:03 AM - edited 11-01-2023 06:04 AM
Also check https://extreme-networks.my.site.com/ExtrArticleDetail?an=000100006 - there is a property override available in Control to handle reachability requests like this.
... and of course Mr Yacobucci already provided that earlier 😉
11-01-2023 05:33 AM
Hello,
Check out:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000112893
Also, consider using the reachability checks to reduce load on XIQ-SE if large numbers of healthchecks are being sent:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000100006
Thanks
-Ryan
11-01-2023 05:23 AM
Yes, this is normal, for reachability it does not matter if a reject or accept is received, as long as a radius response is received.
You could create a seperate rule to just accept this and not see the rejects.
server-status might be a more silent method