Product specifications

4–InfiniPath Cluster Setup and Administration
Host Environment Setup for MPI
IB6054601-00 H 4-27
A
812E5iw1GCZfNefBmWbegWVKFwGlNbqBnZK7kDRLSOKQtuhYbGPcrVlSjuVps
fWEju64FTqKEetA8l8QEgAAAIBNtPDDwdmXRvDyc0gvAm6lPOIsRLmgmdgKXT
GOZUZ0zwxSL7GP1nEyFk9wAxCrXv3xPKxQaezQKs+KL95FouJvJ4qrSxxHdd1
NYNR0DavEBVQgCaspgWvWQ8cL
0aUQmTbggLrtD9zETVU5PCgRlQL6I3Y5sCCHuO7/UvTH9nneCg==
Change the file to mode 600 when you are finished editing.
4. On each node, the system file /etc/ssh/sshd_config must be edited,
so that the following four lines are uncommented (no # at the start of the line)
and set to yes. (These lines are usually there, but are commented out and
set to no by default.)
RhostsAuthentication yes
RhostsRSAAuthentication yes
HostbasedAuthentication yes
PAMAuthenticationViaKbdInt yes
5. After creating or editing the three files in Steps 2, 3, and 4, sshd must be
restarted on each system. If you are already logged in via
ssh (or any other
user is logged in via
ssh), their sessions or programs will be terminated, so
restart only on idle nodes. Type the following (as root) to notify sshd to use
the new configuration files:
# killall -HUP sshd
At this point, any end user should be able to login to the ip-fe front end system
and use ssh to login to any InfiniPath node without being prompted for a
password or pass phrase.
Configuring for ssh Using ssh-agent
The ssh-agent, a daemon that caches decrypted private keys, can be used to
store the keys. Use ssh-add to add your private keys to ssh-agent’s cache.
When ssh establishes a new connection, it communicates with ssh-agent to
acquire these keys, rather than prompting you for a passphrase.
The process is described in the following steps:
1. Create a key pair. Use the default file name, and be sure to enter a
passphrase.
$ ssh-keygen -t rsa
NOTE:
This command terminates all ssh sessions into that system. Run from
the console, or have a way to log into the console in case of any
problem.