Configuring SSH (using Putty) to SSH to Linux Nodes from Windows
|
NOTE: This document can be used as a guide for assistance in setting up SSH on a Windows machine to submit FLUENT jobs to Linux. If you have any trouble setting up SSH correctly please contact your local IT Department for assistance. 1.Download and install Putty, Puttygen, Plink, Puttytel, from: (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) 2.Choose the Start menu, All Programs , Putty , PuTTYGen to create a cryptographic key. 3.Click Generate , moving the mouse as instructed. 4.Change Key comment to include your Windows username. 5.Do not enter a Key passphrase IMPORTANT NOTE : If your Linux/UNIX cluster uses OpenSSH you will need to convert the key to OpenSSH format. Check with your Systems Administrator. Choose the Conversions menu and choose Export OpenSSH key. 6.Choose Save private key file without passphrase to C:temp ssh-priv. ppk ( or any directory that does not have spaces in the name, important for successful FLUENT launch ) 7.Click on the "Save public key" button to save a copy of the public key without a passphrase". This will save a local copy of the public key for future reference. 8.Open an SSH session to one of your cluster nodes, cd into ~/.ssh, and open the authorized_keys file in your favorite editor (for example, VI or EMACS). 9.Select all of the text in the edit box entitled "Public key for pasting into OpenSSH authorized_keys file", copy it, and paste it into the edit session you opened in Step 8. 10.Save and close the edit session for the authorized_keys file. 11.Chmod 600 .ssh/ authorized_keys 12.Add and Modify the Windows environment variables by going into Control Panel, System Advanced , Environment Variables. a.Append the PuTTY install directory to Path variable, for example, C:Program FilesPutty. You must add this to the System Environment variable area. b.Add a KEYPATH environment variable with full path to private key file, such as C:Program FilesPutty ssh-priv.ppk . You can use a user variable if the key file is used only by you. Use a system variable if other users are sharing the key file. Testing the Key As an initial test, run the following from the command prompt (quotes around %KEYPATH% is required): plink -i `%KEYPATH%` username@unixmachinename pwd 1.If plink prompts you to store the key in cache, select Yes . 2.If plink prompts you to trust key, select Yes . NOTE : Before configuring the ANSYS Fluent Launcher on Windows to submit jobs to the Linux/UNIX cluster verify that you have tested the key using the above procedure and that the username and password are identical on the Windows machine and the Linux/UNIX machine(s). SSH/RSH Configuration -- If you used Putty to configure your encrypted key then choose the radio button Other from the ` Remote Spawn Command `, type : plink -i c:Directory (WITHOUT spaces) where the private key is locatedprivate_key.ppk -l (lower case L) your login username ~~~~~~~~~~~~~~~~ Firewall Exceptions If you have a Firewall enabled on both the client and the headnode you will need to add some executables to the exceptions list as shown below. The list below shows just the exceptions if you choose 3D when launching FLUENT. If you run in 2D or double-precision, for example, 2ddp or 3ddp then you will have to add those into the exceptions list. C:Program FilesANSYS Incv130fluentwin643dfl1304.exe C:Program FilesANSYS Incv130fluentwin643d_nodefl_mpi1304.exe C:Program FilesANSYS Incv130fluentwin643d_nodefl_mpi1304.lib C:Program FilesANSYS Incv130fluentwin643d_hostfl1304.exe C:Program FilesANSYS Incv130fluentwin643d_hostfl1304.lib C:Program FilesANSYS Incv130fluentcortexwin64cx1304.exe |
||
|