Troubleshooting AAA, RADIUS, and HWTACACS Configurations 241
Troubleshooting AAA, RADIUS, and HWTACACS Configurations
The RADIUS protocol of the TCP/IP protocol suite is located on the application
layer. It specifies how to exchange user information between the NAS and RADIUS
servers of an ISP.
Tasks for Troubleshooting AAA and Radius are described in the following sections:
User authentication/authorization always fails
RADIUS packet cannot be transmitted to RADIUS server.
After being authenticated and authorized, the user cannot send charging bill
to the RADIUS server.
User authentication/authorization always fails
The username may not be in the userid@isp-name format or NAS has not been
configured with a default ISP domain. Please use the username in proper
format and configure the default ISP domain on NAS.
The user may not have been configured in the RADIUS server database. Check
the database and make sure that the configuration information of the user
does exist in the database.
The user may have input a wrong password. Make sure that the supplicant
inputs the correct password.
The encryption keys of the RADIUS server and NAS server may be different.
Check carefully and make sure that they are identical.
There might be some communication fault between NAS and RADIUS server,
which can be discovered through pinging RADIUS from NAS. Ensure the
normal communication between NAS and RADIUS.
RADIUS packet cannot be transmitted to RADIUS server.
The communication lines (on physical layer or link layer) connecting NAS and
RADIUS server may not work well.
The IP address of the corresponding RADIUS server may not have been set on
NAS. Set a proper IP address for RADIUS server.
UDP ports of authentication/authorization and accounting services may not be
set properly. Make sure they are consistent with the ports provided by RADIUS
server.
After being authenticated and authorized, the user cannot send charging
bill to the RADIUS server.
1The accounting port number may be set improperly. Set a proper number.
2The accounting service and authentication/authorization service are provided on
different servers, but NAS requires the services to be provided on one server (by
specifying the same IP address). Make sure the settings of servers are consistent
with the actual conditions.