Verifying SSH authentication between the source and destination HMC

You can run the mkauthkeys command from the Hardware Management Console (HMC) that manages the source server to verify that the secure shell (SSH) authentication keys are correctly set up between the HMC that manages the source server and the HMC that manages the destination server. SSH authentication allows the HMCs to send and receive partition mobility commands to and from each other.

About this task

To verify that the SSH authentication keys are set up correctly between the HMC that manages the source server and the HMC that manages the destination server, complete the following steps:

Procedure

Run the following command from the HMC command line of the HMC that manages the source server:
```
mkauthkeys -u <remoteUserName> --ip <remoteHostName> --test
```
Where:
- remoteUserName is the name of the user on the HMC that manages the destination server. This parameter is optional. If you do not specify a user name for the HMC that manages the destination server, then the migration process uses the current user name as the remoteUserName.
- remoteHostName is the IP address or the host name of the HMC that manages the destination server.
If this command produces a return code of 0, then the SSH authentication keys are set up correctly between the HMC that manages the source server and the HMC that manages the destination server.
If this command produces an error code, then continue to the next step to set up the SSH authentication keys between the HMC that manages the source server and the HMC that manages the destination server.
Run the following command to set up the SSH authentication keys between the HMC that manages the source server and the HMC that manages the destination server:
```
mkauthkeys -u <remoteUserName> --ip <remoteHostName> -g
```
Where remoteUserName and remoteHostName represent the same values that they represented in the previous step.
The —g option automatically sets up the SSH authentication keys from the HMC that manages the source server to the HMC that manages the destination server, and it automatically sets up the SSH authentication keys from the HMC that manages the destination server to the HMC that manages the source server. If you do not include the —g option, the command automatically sets up the SSH authentication keys from the HMC that manages the source server to the HMC that manages the destination server, but the command does not automatically set up the SSH authentication keys from the HMC that manages the destination server to the HMC that manages the source server.