1-43
11) The communication link between the NAS and the RADIUS server is down (at the physical layer
and data link layer).
12) The NAS is not configured with the IP address of the RADIUS server.
13) The UDP ports for authentication/authorization and accounting are not correct.
14) The port numbers of the RADIUS server for authentication, authorization and accounting are
being used by other applications.
Solution:
Check that:
15) The communication links between the NAS and the RADIUS server work well at both physical and
link layers.
16) The IP address of the RADIUS server is correctly configured on the NAS.
17) UDP ports for authentication/authorization/accounting configured on the NAS are the same as
those configured on the RADIUS server.
18) The port numbers of the RADIUS server for authentication, authorization and accounting are
available.
Symptom 3: A user is authenticated and authorized, but accounting for the user is not normal.
Analysis:
19) The accounting port number is not correct.
20) Configuration of the authentication/authorization server and the accounting server are not correct
on the NAS. For example, one server is configured on the NAS to provide all the services of
authentication/authorization and accounting, but in fact the services are provided by different
servers.
Solution:
Check that:
21) The accounting port number is correctly set.
22) The authentication/authorization server and the accounting server are correctly configured on the
NAS.
Troubleshooting HWTACACS
Refer to Troubleshooting RADIUS if you encounter a HWTACACS fault.
To Next Page
Loading...
