An administrator configures a server group with two AAA servers. During the authentication process, the first server sends a RADIUS reject message in response to an authentication request.
What should the administrator implement to ensure that the authentication is also attempted with the second AAA server in the group?
To ensure that authentication is attempted with the second AAA server in the group after receiving a RADIUS reject message, EAP load balancing should be implemented. This technique distributes the authentication requests across the available AAA servers, ensuring that even if one server fails to authenticate, another server can be utilized to handle the request.
Previous poster is correct, Fail-through would be the best solution to the admin's issues. Not A or B. Eap Termination does not receive a challenge from a AAA server, machine auth does, but does not fail-through. VRRP is wrong, but a server-group with fail-through enabled is correct: https://www.arubanetworks.com/techdocs/ArubaOS_64_Web_Help/Content/ArubaFrameStyles/1CommandList/aaa_server_group.htm D is the closest to being right, the controller round-robins between the AAA servers based on expected wait times for an auth request: arubanetworks.com/techdocs/ArubaOS_64_Web_Help/Content/ArubaFrameStyles/AAA_Servers/Load_Balancing.htm A+B are wrong, C is only half right, D is the closest to correct.
None of These are correct. It should be Fail-Through https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=1197a
If using 802.1x auth, the reject ends the process. But if you terminate eap on the managed device, fail through will work. But best answer is still fail through.
a is correct answer for me, eap termination must be enable for fail through