Extreme Networks

joshross28 · ‎10-31-2023

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)?

Ryan_Yacobucci · ‎11-01-2023

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

View solution in original post

Ludovico_Steven · ‎11-02-2023

You can use "status-server" on VOSS / Fabric Engine instead of "use-radius" for RADIUS reachability mode.

XIQ-SE supports it.

WillyHe · ‎11-02-2023

Article "https://extreme-networks.my.site.com/ExtrArticleDetail?an=000112893" is not available

Robert_Haynes · ‎11-02-2023

Thank you. I have fixed the permissions on the article.

WillyHe · ‎11-01-2023

The solution I prefer is the one that requires the least resources from both the switches and the radius servers.

regards
WillyHe

Extreme Networks

VOSS Radius Reachability Check with Dummy Requests - XIQ-SE

VOSS Radius Reachability Check with Dummy Requests - XIQ-SE