Diagnosis Guide

Information to collect before contacting the IBM Support Center

Before calling IBM Service, it is your responsibility to verify that the environment where the error has occurred is correct. Perform these steps:

• Verify that the correct authentication mechanism is installed, configured, updated for SP system use, and enabled on the source and target hosts and in the system partition. See SP Security Services configuration errors.
• Verify that there is one authentication mechanism in common between the source/target hosts, both locally on each host and in the system partition where the hosts reside. See Check enabled security.
• Verify that the user has the proper principal in the proper database and registry. See Verify configuration of Kerberos V4.
• Verify that the user has done the proper login to obtain credentials before issuing the remote command. See AIX remote command diagnostics.
• Verify that the user is in the proper authorization file on the target host. See AIX remote command diagnostics.
• Verify that the user is using the proper flags if forwarding credentials (Kerberos V5) or when running the remote command in the background. See AIX remote command diagnostics.
• Verify that your secure remote command program is installed and running properly.

If you are still having problems after performing these steps, collect the following information for the source and target hosts, for review by the IBM Support Center.

1. The PSSP level installed
2. The current PSSP PTF level
3. The current PTF level for bos.net.tcp.xxxx, where xxxx represents "client", "server" or "smit", followed by spaces and then version.release.modification.fix level. Issue this command:

   lslpp -L | grep tcp
   

4. The AIX Operating System Level, obtained by using the oslevel command.
5. The authentication and authorization settings, obtained by issuing the lsauthent and lsauthpar commands.
6. The exact syntax of the command that generated the error.
7. Any messages displayed with K5MUTE not set, or captured through syslog.
8. Any other diagnostic actions taken that you believe contribute to the solution of the problem, or provide additional information in debugging the problem.