This topic provides step-by-step instructions to run the PuTTY plink utility.
All CLI commands are run in an SSH session. You can run the commands in either of the two following modes:
For interactive mode, you use the PuTTY executable to open the SSH restricted
shell. Type the following:
C:\support utils\putty>putty admin@<svcconsoleip>
If you were to issue the svcinfo lssshkeys command,
which lists the SSH client public keys that are stored on the SAN Volume Controller
cluster, the following output is displayed:
IBM_2145:admin>svcinfo lssshkeys -user all -delim :
id:userid:key identifier
1:admin:smith
2:admin:jones
Type exit and press Enter to escape
the interactive mode command.
The SSH protocol specifies that the first access to a new host server will result in a challenge to the SSH user to accept the SSH server public key. Because this is the first time that you connect to an SSH server, the server is not included in the SSH client list of known hosts. Therefore, there is a fingerprint challenge, which asks you do you accept the responsibility of connecting with this host. If you type y, the host fingerprint and IP address is saved by the SSH client. For PuTTY, you answer by typing y to accept this host fingerprint. This information is stored in the registry for the user name which is logged onto Windows.
The following is an example of the host fingerprint challenge when running
in interactive mode:
C:\Program Files\IBM\svcconsole\cimom>plink admin@9.43.225.208
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's key fingerprint is:
ssh-rsa 1024 e4:c9:51:50:61:63:e9:cd:73:2a:60:6b:f0:be:25:bf
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y
Using username "admin".
Authenticating with public key "imported-openssh-key"
IBM_2145:admin>
For single line command mode, you can type the following all on one command
line:
C:\Program Files\IBM\svcconsole\cimom>
plink admin@9.43.225.208 svcinfo lssshkeys
-user all -delim :
Authenticating with public key "imported-openssh-key"
/bin/ls: id:userid:key identifier
1:admin:smith
2:admin:jones
C:\Program Files\IBM\svcconsole\cimom>
The SSH protocol specifies that the first access to a new host server will result in a challenge to the SSH user to accept the SSH server public key. Because this is the first time that you connect to an SSH server, the server is not included in the SSH client list of known hosts. Therefore, there is a fingerprint challenge, which asks you do you accept the responsibility of connecting with this host. If you type y, the host fingerprint and IP address is saved by the SSH client. For PuTTY, you answer by typing y to accept this host fingerprint. This information is stored in the registry for the user name which is logged onto Windows.
The following is an example of the host fingerprint challenge when running
in single line command mode:
C:\Program Files\IBM\svcconsole\cimom>
plink admin@9.43.225.208 svcinfo lssshkeys
-user all -delim :
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's key fingerprint is:
ssh-rsa 1024 e4:c9:51:50:61:63:e9:cd:73:2a:60:6b:f0:be:25:bf
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y
Authenticating with public key "imported-openssh-key"
/bin/ls: /proc/20282/exe: Permission denied
dircolors: `/etc/DIR_COLORS': Permission denied
id:userid:key identifier
1:admin:smith
2:admin:jones
C:\Program Files\IBM\svcconsole\cimom>
| Note: If you are submitting a CLI command with all parameters in single line command mode, you will be challenged upon first appearance of the SSH server host fingerprint. Be careful to ensure that the SSH server host fingerprint is accepted before submitting a batch script file. |
The SSH protocol also specifies that once the SSH server public key is accepted, another challenge will be presented if the fingerprint of an SSH server changes from the one previously accepted. In this case, you will need to decide whether to accept this changed host fingerprint. For PuTTY, you answer by typing y to accept this host fingerprint. PuTTY stores this information in the registry for the user name which is logged onto Windows.
| Note: The SSH server keys on the SAN Volume Controller will be regenerated when a microcode load is performed on the cluster. Due to this behavior, you will see a challenge presented because the fingerprint of the SSH server has changed. |