1-422) The username is in the userid@isp-name format and a default ISP domain is specified on the NAS.3) The user is configured on the RADIUS server.4) The correct password is entered.5) The same shared key is configured on both the RADIUS server and the NAS.Symptom 2: RADIUS packets cannot reach the RADIUS server.Analysis:1) The communication link between the NAS and the RADIUS server is down (at the physical layerand data link layer).2) The NAS is not configured with the IP address of the RADIUS server.3) The UDP ports for authentication/authorization and accounting are not correct.4) The port numbers of the RADIUS server for authentication, authorization and accounting are beingused by other applications.Solution:Check that:1) The communication links between the NAS and the RADIUS server work well at both physical andlink layers.2) The IP address of the RADIUS server is correctly configured on the NAS.3) UDP ports for authentication/authorization/accounting configured on the NAS are the same asthose configured on the RADIUS server.4) The port numbers of the RADIUS server for authentication, authorization and accounting areavailable.Symptom 3: A user is authenticated and authorized, but accounting for the user is not normal.Analysis:1) The accounting port number is not correct.2) Configuration of the authentication/authorization server and the accounting server are not correcton the NAS. For example, one server is configured on the NAS to provide all the services ofauthentication/authorization and accounting, but in fact the services are provided by differentservers.Solution:Check that:1) The accounting port number is correctly set.2) The authentication/authorization server and the accounting server are correctly configured on theNAS.Troubleshooting HWTACACSRefer to Troubleshooting RADIUS if you encounter an HWTACACS fault.
