Panasonic 8000 - Manual (Page 36)

1 AAA troubleshooting
Nortel Secure Router 8000 Series
_________ Troubleshooting - VAS
Check that the authentication port number is the same as that configured on the NAS and
the RADIUS server template.
Check that the password configured on the RADIUS server is consistent with the shared
key configured on the NAS.
Check that the attributes of the FTP directory are delivered. Then, check that user001
adds the delivered attributes.
After attributes of the FTP directory are delivered, the user can log on to the FTP server.
The fault disappears.
Troubleshooting procedure
Step 1 Check whether the RADIUS server has records about the logon user.
Step 2 If there are no logon records, use the debugging radius packet command on the NAS to
check whether NAS has sent out authentication request packets.
Step 3 If the NAS fails to send out authentication request packets, check AAA and the RADIUS
server template on the NAS. Note that the user can view the sent RADIUS authentication
request packets when logging on.
Step 4 If the RADIUS server still has no logon user records, check the IP address and the port
configuration. Note the following:
• The server and the NAS can ping through each other.
• Port configuration on the RADIUS server must be the same as that on the RADIUS
server template.
Step 5 If the faulty authentication persists when the NAS and RADIUS server can communicate, the
possible causes are as follows:
• The NAS address is not added.
• The shared key on the NAS is incorrect.
• The user name and password are incorrect.
Step 6 If the authentication succeeds but the authorization fails after the NAS and RADIUS server
can communicate, check whether the user is authorized by the RADIUS server.
----End
Summary
If RADIUS authentication fails, ensure the following:
• successful communication between the NAS and the RADIUS server
• successful authentication
• successful authorization
You can locate the fault through the debugging information on the NAS and RADIUS server.
1-18 Nortel Networks Inc. Issue 01.01 (30 March 2009)