When both RADIUS authentication and local authentication are configured on an S series switch, why a user is disconnected after more than 10s

26

When both RADIUS authentication and local authentication are configured on an S series switch, the switch performs local authentication if it does not receive any response from the RADIUS server for some reasons (for example, the RADIUS server fails). As shown in the following configuration file, RADIUS authentication and accounting are configured on the switch. The user successfully logs in through local authentication, but RADIUS accounting fails because the RADIUS server does not respond. Therefore, the user is disconnected.
#
radius-server template rad //Configure a RADIUS server template.
radius-server shared-key cipher %#%#HN!rP_Lc1<+L+H/&YUzN]CBy;_09Z>9T5\.k{T1/%#%#
radius-server authentication 10.7.66.66 1812 weight 80
radius-server accounting 10.7.66.66 1813 weight 80
#
aaa
authentication-scheme default
authentication-mode radius local //Configure the authentication scheme default and set the authentication modes to RADIUS authentication and local authentication.
authorization-scheme default
accounting-scheme default
accounting-mode radius //Configure the accounting scheme default and set the accounting method to RADIUS accounting.
domain default
domain default_admin
radius-server rad //Apply the RADIUS server template to the global default administrative domain. By default, the domain uses the authentication scheme default and accounting scheme default.
local-user user1 password cipher %#%#9X%T3y\jN;_&5(FU-B4P;);/tc^%VI\mA1KeeH%#%#
local-user user1 privilege level 15
local-user user1 service-type telnet terminal
#
Solution:
�?For administrators (logging in through Telnet, SSH, FTP, HTTP, or terminals), accounting is not required, so RADIUS accounting configuration can be deleted.
�?For non-administrator users, run the accounting start-fail online command in the accounting scheme view. After the command is executed, the users are not disconnected if accounting fails. However, accounting results are inaccurate. Before using this method, ensure that service will not be affected.

Other related questions:
Both RADIUS authentication and local authentication are configured. Is local authentication performed when RADIUS authentication fails
The AR first performs RADIUS authentication. If RADIUS authentication fails, the AR does not perform local authentication. The AR performs local authentication only when the RADIUS server has no response.

If both RADIUS authentication and local authentication are configured, in which situation do S series switches perform local authentication
If multiple authentication modes are configured, an S series switch chooses these authentication modes in the configuration order. It uses the authentication mode that was configured later only when it does not receive any response in the current authentication. If the user fails in an authentication, the switch does not use another authentication mode. For example, if both RADIUS authentication and local authentication are configured on a switch and the RADIUS authentication is configured first, the switch performs local authentication only when the connection with the RADIUS server times out. This rule also applies to switches configured with both HWTACACS authentication and local authentication.

Clients pass 802.1x authentication on an S series switch, and are disconnected after 10 seconds
For S series switches except S1700 switches, if handshake with online 802.1x users is enabled on a switch, the switch sends handshake packets to a client after the client is authenticated. If the client does not respond to the handshake packets, the switch forces the client offline. The client goes offline 10 seconds after it is authenticated. This may be caused by a handshake failure. In this case, run the undo dot1x handshake command in the system view to disable the handshake function.

Local and remote RADIUS or HWTACACS authentication is configured on an S series switch. When the remote authentication server does not respond, local users cannot log in and the message "aaa user cut" is displayed. Why
Users fail to log in because accounting fails. The S series switch is configured with authentication and accounting, but does not support accounting. To solve the problem, run the following command to configure the switch to keep users online after accounting fails. [HUAWEI] aaa [HUAWEI-aaa] accounting-scheme scheme1 [HUAWEI-aaa-accounting-scheme1] accounting start-fail online

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top