Advanced POWER Virtualization on IBM System p5 - Previous ...

. Append the PLM server public key to the list of HMC public keys:
$ cat ~/.ssh/id_rsa.pub >>~/.ssh/hmc_authorized_keys2
$ ls -l .ssh
total 5
-rw-r--r-- 1 root system 227 Aug 09 22:16 hmc_authorized_keys2
-rw------- 1 root system 883 Aug 09 21:59 id_rsa
-rw-r--r-- 1 root system 227 Aug 09 21:59 id_rsa.pub
-rw-r--r-- 1 root system 225 Aug 09 22:07 known_hosts
Copy the updated public key list back to the HMC:
$ scp .ssh/hmc_authorized_keys2
hscroot@590hmc:.ssh/authorized_keys2
hscroot@590hmc's password:
hmc_authorized_keys2 100% 227 0.2KB/s
00:00
c. Complete the key exchange and verify the SSH configuration.
The initial SSH exchange between two servers performs the SSH key
exchange. Run the ls command remotely on the HMC by entering the
following command on the PLM server (you should not be prompted for a
password):
# ssh hscroot@590hmc ls
WebSM.pref
websm.script
This ssh command should be repeated with the fully qualified name and
the IP address of the HMC to have a complete key exchange. This will
reduce the likelihood of problems during the PLM and RMC configuration:
$ ssh hscroot@590hmc.mydomain.com ls
$ ssh hscroot@192.164.10.10 ls
d. Obtain the name of the managed system.
Use the following command on the PLM server:
# ssh hscroot@p5hmc1 lssyscfg -r sys -F name
Unless the name of the managed system has been changed on the HMC
using the Properties tab on the managed system, the default managed
system name is similar to the following:
Server-9119-590-SN02Cxxxx
386 <strong>Advanced</strong> <strong>POWER</strong> <strong>Virtualization</strong> on IBM System p5