HP-UX AAA Server A.08.00.01 Administrator's Guide

and radacct respectively) are in the LISTEN state and used by the correct process.
For example:
# lsof -i :<authentication port>
The authentication port (default, 1812) and accounting port (default, 1813) must
be in the LISTEN state and used by the radius process.
NOTE: The lsof tool is an open source tool and is not available by default on
HP-UX operating systems.
3. If another process is using the authentication or accounting port, configure different
ports in the /etc/services file or from the Start Options in the Administration
screen of Server Manager
Troubleshooting an Unresponsive HP-UX AAA Server
To troubleshoot an unresponsive HP-UX AAA Server, first determine whether the
HP-UX AAA Server is receiving requests.
To determine whether the HP-UX AAA Server is receiving requests, perform the
following steps:
1. View the HP-UX AAA Server logfile using the Server Logfile screen as described
in “Using Server Manager to Retrieve Logfile Information” (page 138). The server
logfile messages are displayed.
2. If the message was received, check the logfile for error messages and compare
them to the errors listed in the following sections:
• “Troubleshooting Common Configuration Problems” (page 475): Lists errors
caused because of incorrect configuration on the HP-UX AAA Server or the
RADIUS client
• “Troubleshooting External Services” (page 478): Lists errors caused by
unresponsive or failed external services
3. If the HP-UX AAA Server received the request and remained unresponsive, but
did not log an error in the logfile, see “Troubleshooting External Services”
(page 478).
If the HP-UX AAA Server did not receive the request, perform the following steps:
1. Verify that the DNS server is available by entering the nslookup command. For
more information on the nslookup command, see nslookup(1M).
2. Ensure that the RADIUS client is receiving requests from the supplicant and is
configured to send requests to the correct HP-UX AAA Server.
3. If proxy HP-UX AAA Servers are used, see “Identifying Proxy Server Failures”
(page 484) to check for proxy server failures.
474 Troubleshooting Procedures