Support Knowledge Center

Barcelona Supercomputing Center

Nord III User's Guide

Nord III User's Guide

Table of Contents

  1. Introduction
  2. System Overview
  3. Connecting to Nord III
    1. Password Management
    2. Transferring files
    3. Active Archive Management
  4. File Systems
    1. Root Filesystem
    2. GPFS Filesystem
    3. Local Hard Drive
    4. Quotas
  5. Running Jobs
    1. LSF Commands
    2. Job directives
    3. MPI particulars
    4. Jobscript examples
    5. Queues
  6. Software Environment
    1. C Compilers
    2. FORTRAN Compilers
    3. Modules Environment
    4. BSC Commands
    5. TotalView
    6. Tracing jobs with BSC Tools
  7. Getting help
    1. Frequently Asked Questions (FAQ)
  8. Appendices
    1. SSH
    2. Transferring files
    3. Using X11

Introduction ↩

This user’s guide for the Nord III cluster is intended to provide the minimum amount of information needed by a new user of this system. As such, it assumes that the user is familiar with many of the standard features of supercomputing as the Unix operating system.

Here you can find most of the information you need to use our computing resources and the technical documentation about the machine. Please read carefully this document and if any doubt arises do not hesitate to contact us (Getting help).

System Overview ↩

Nord III is a supercomputer based on Intel SandyBridge processors, iDataPlex Compute Racks, a Linux Operating System and an Infiniband interconnection.

The current Peak Performance is 28 Gigaflops. The total number of processors is 1,344 Intel SandyBridge-EP E5–2670 cores at 2.6 GHz (84 compute nodes) with 10.5 TB of main memory. See below a summary of the system:

Connecting to Nord III ↩

The first thing you should know is your username and password. Once you have a login and its associated password you can get into the cluster through one of the following login nodes:

You must use Secure Shell (ssh) tools to login into or transfer files into the cluster. We do not accept incoming connections from protocols like telnet, ftp, rlogin, rcp, or rsh commands. Once you have logged into the cluster you cannot make outgoing connections for security reasons.

To get more information about the supported secure shell version and how to get ssh for your system (including windows systems) see the Appendices. Once connected to the machine, you will be presented with a UNIX shell prompt and you will normally be in your home ($HOME) directory. If you are new to UNIX, you will need to learn the basics before doing anything useful.

Password Management ↩

In order to change the password, you have to login to a different machine ( This connection must be established from your local machine.

    % ssh -l username

    username@dtransfer1:~> passwd
    Changing password for username.
    Old Password: 
    New Password: 
    Reenter New Password: 
    Password changed.

Mind that that the password change takes about 10 minutes to be effective.

Transferring files ↩

There are two ways to copy files from/to the Cluster:

Direct copy to the login nodes.

As said before no connections are allowed from inside the cluster to the outside world, so all scp and sftp commands have to be executed from your local machines and never from the cluster. The usage examples are in the next section.

On a Windows system, most of the secure shell clients come with a tool to make secure copies or secure ftp’s. There are several tools that accomplish the requirements, please refer to the Appendices, where you will find the most common ones and examples of use.

Data Transfer Machine

We provide special machines for file transfer (required for large amounts of data). These machines are dedicated to Data Transfer and are accessible through ssh with the same account credentials as the cluster. They are:

These machines share the GPFS filesystem with all other BSC HPC machines. Besides scp and sftp, they allow some other useful transfer protocols:

    localsystem$ scp localfile
    username's password:

    localsystem$ sftp
    username's password:
    sftp> put localfile
    localsystem$ scp localdir
    username's password:
    localsystem$ sftp
    username's password:
    sftp> get remotefile
    bbcp -V -z <USER><FILE> <DEST>
    bbcp -V <ORIG>  <USER><DEST>
    gftp-text ftps://<USER>
    get <FILE>
    put <FILE>

Data Transfer on the PRACE Network

PRACE users can use the 10Gbps PRACE Network for moving large data among PRACE sites.

The selected data transfer tool is Globus/GridFTP which is available on

In order to use it, a PRACE user must get access to

    % ssh -l pr1eXXXX

Load the PRACE environment with ‘module’ tool:

    % module load prace globus

Create a proxy certificate using ‘grid-proxy-init’:

    % grid-proxy-init 
    Your identity: /DC=es/DC=irisgrid/O=bsc-cns/
    Enter GRID pass phrase for this identity:
    Creating proxy ........................................... Done
    Your proxy is valid until: Wed Aug  7 00:37:26 2013

The command ‘globus-url-copy’ is now available for transferring large data.

    globus-url-copy [-p <parallelism>] [-tcp-bs <size>] <sourceURL> <destURL>


All the available PRACE GridFTP endpoints can be retrieved with the ‘prace_service’ script:

    % prace_service -i -f bsc

More information is available at the PRACE website

Active Archive Management ↩

Active Archive (AA) is a mid-long term storage filesystem that provides 3.7 PB of total space. You can access AA from the Data Transfer Machine ( and under /gpfs/archive/your_group.

NOTE: There is no backup of this filesystem. The user is responsible for adequately managing the data stored in it.

To move or copy from/to AA you have to use our special commands:

These commands submit a job into a special class performing the selected command. Their syntax is the same than the shell command without ‘dt’ prefix (cp, mv, rsync, tar).

dtq shows all the transfer jobs that belong to you. (works like mnq)

dtcancel works like mncancel (see below) for transfer jobs.

    % dttar -cvf  /gpfs/archive/usertest/outputs.tar ~/OUTPUTS 
    # Example: Copying data from /gpfs to /gpfs/archive    
    % dtcp -r  ~/OUTPUTS /gpfs/archive/usertest/
    # Example: Copying data from /gpfs/archive to /gpfs
    % dtcp -r  /gpfs/archive/usertest/OUTPUTS ~/
    # Example: Moving data from /gpfs to /gpfs/archive    
    % dtmv ~/OUTPUTS /gpfs/archive/usertest/
    # Example: Moving data from /gpfs/archive to /gpfs
    % dtmv /gpfs/archive/usertest/OUTPUTS ~/

Additionally, these commands accept the following options:

It is important to note that these kind of jobs can be submitted from both the ‘login’ nodes (automatic file management within a production job) and ‘’ machine. AA is only mounted in Data Transfer Machine. Therefore if you wish to navigate through AA directory tree you have to login into

File Systems ↩

IMPORTANT: It is your responsibility as a user of our facilities to backup all your critical data. We only guarantee a daily backup of user data under /gpfs/home and /gpfs/projects.

Each user has several areas of disk space for storing files. These areas may have size or time limits, please read carefully all this section to know about the policy of usage of each of these filesystems. There are 3 different types of storage available inside a node:

Root Filesystem ↩

The root file system, where the operating system is stored doesn’t reside in the node, this is a NFS filesystem mounted from one of the servers.

As this is a remote filesystem only data from the operating system has to reside in this filesystem. It is NOT permitted the use of /tmp for temporary user data. The local hard drive can be used for this purpose as you could read in Local Hard Drive.

GPFS Filesystem ↩

The IBM General Parallel File System (GPFS) is a high-performance shared-disk file system providing fast, reliable data access from all nodes of the cluster to a global filesystem. GPFS allows parallel applications simultaneous access to a set of files (even a single file) from any node that has the GPFS file system mounted while providing a high level of control over all file system operations. In addition, GPFS can read or write large blocks of data in a single I/O operation, thereby minimizing overhead.

An incremental backup will be performed daily only for /gpfs/home and /gpfs/projects (not for /gpfs/scratch).

These are the GPFS filesystems available in the machine from all nodes:

Local Hard Drive ↩

Every node has a local hard drive that can be used as a local scratch space to store temporary files during executions of one of your jobs. This space is mounted over /scratch/tmp directory and pointed out by $TMPDIR environment variable. The amount of space within the /scratch filesystem is about 500 GB. All data stored in these local hard drives at the compute nodes will not be available from the login nodes. Local hard drive data are not automatically removed, so each job has to remove its data before finishing.

Quotas ↩

The quotas are the amount of storage available for a user or a groups’ users. You can picture it as a small disk readily available to you. A default value is applied to all users and groups and cannot be outgrown.

You can inspect your quota anytime you want using the following command from inside each filesystem:

     % bsc_quota

The command provides a readable output for the quota. Check BSC Commands for more information.

If you need more disk space in this filesystem or in any other of the GPFS filesystems, the responsible for your project has to make a request for the extra space needed, specifying the requested space and the reasons why it is needed. For more information or requests you can Contact Us.

Running Jobs ↩

LSF is the utility used at Nord III for batch processing support, so all jobs must be run through it. This document provides information for getting started with job execution at the Cluster.

LSF Commands ↩

These are the basic commands to submit, control and check your jobs:

 bsub < job_script

submits a “job script” passed through standard input (STDIN) to the queue system. Job directives explains the available options to write a jobscript

 bjobs [-w][-X][-l job_id]

shows all the submitted jobs.

 bkill <job_id>

remove the job from the queue system, canceling the execution of the processes, if they were still running.


shows all the pending or running jobs from your group. Check BSC Commands for more information.

Job directives ↩

A job must contain a series of directives to inform the batch system about the characteristics of the job. We encourage that you read the bsub command’s manual from any of Nord’s terminals:

    % man bsub

Here we provide a short summary of most common directives:

    #BSUB -J job_name

Specify the name (description) of the job.

    #BSUB -q debug

Specify the queue for the job to be submitted. The debug queue is only intended for small tests, so there is a limit of 1 job per user, using up to 64 cpus (4 nodes), and one hour of wall clock limit. The queue might be reassigned by LSF internal policy, as with the sequential queue.

    #BSUB -W HH:MM

Specify how much time the job will be allowed to run. This is a mandatory field. NOTE: take into account that you can not specify the amount of seconds in LSF. You must set it to a value greater than the real execution time for your application and smaller than the time limits granted to the user. Notice that your job will be killed after the elapsed period.

    #BSUB -cwd pathname

The working directory of your job (i.e. where the job will run).If not specified, it is the current working directory at the time the job was submitted.

    #BSUB -e/-eo file

The name of the file to collect the stderr output of the job. You can use %J for job_id. -e option will APPEND the file, -eo will REPLACE the file.

    #BSUB -o/-oo file

The name of the file to collect the standard output (stdout) of the job. -o option will APPEND the file, -oo will REPLACE the file.

    #BSUB -n number

The number of tasks for the job. In MPI executions corresponds to the number of MPI processes and for sequential executions the number of cores.

    #BSUB -x

Use the nodes exclusively. This is the default behaviour except for sequential executions.

    #BSUB -M number

Specify maximum amount of memory necessary for each task, specified in MB. This option is used to better schedule the jobs and select the compute nodes adequate to fulfill the job’s needs. By default 1800 MB are reserved per task. Exclusive jobs will still get all available memory. You may check this FAQ for a more in-depth explanation. Note: For non-LowMem requests you must specify a ptile of 16.

    #BSUB -R "span[ptile=number]"

The number of processes assigned to a node. Note that full nodes will be allocated except for sequential executions. Examples:

    # if you want to use 4 processes per node and 4 threads:

    #BSUB -R "span[ptile=4]"
    export OMP_NUM_THREADS=4
    # if your program has high memory 
    # consumption you can reduce the number 
    # of processes per node

    #BSUB -R "span[ptile=14]"

MPI particulars ↩

There are different MPI implementations available for usage. Some of them present special requirements to be used.


OpenMPI is an Open Source MPI implementation and is loaded by default on our machines. You can use it like this:

    % module load openmpi
    % mpicc / mpif90 your_files

Once compiled, your jobscript must invoke mpirun:

    #BSUB -n 128
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err
    #BSUB -J openmpi_example
    #BSUB -W 00:05

    module load openmpi
    mpirun binary.exe


IntelMPI is an MPI implementation developed by Intel. You can use it like this:

    % module load intel impi
    % mpicc / mpif90 your_files

Once compiled, your jobscript must invoke mpirun:

    #BSUB -n 128
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err
    #BSUB -J impi_example
    #BSUB -W 00:05

    module load impi
    mpirun binary.exe


IBM POE is an alternative MPI library binary compatible with IntelMPI. Use POE for executions with a large number of cores. First, in order to compile your MPI code using IBM POE:

    % module load poe
    % mpicc / mpif90 your_files

Once compiled, your jobscript must mention it explicitly:

    #BSUB -n 128
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err
    #BSUB -J poe_example
    #BSUB -W 00:05
    #BSUB -a poe

    module load poe
    poe binary.exe

Jobscript examples ↩

Purely sequential


    #BSUB -n 1
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err
    #BSUB -J sequential
    #BSUB -W 00:05


Sequential with OpenMP threads


    #BSUB -n 16 
    #BSUB -R "span[ptile=16]"
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err
    #BSUB -J sequential_OpenMP
    #BSUB -x
    #BSUB -W 00:05

    export OMP_NUM_THREADS=16

Parallel using MPI


    #BSUB -n 128
    #BSUB -o output_%J.out
    #BSUB -e output_%J.err
    # In order to launch 128 processes with 
    # 16 processes per node:
    #BSUB -R "span[ptile=16]"
    #BSUB -J WRF.128-4
    #BSUB -W 02:00

    # You can choose the parallel environment through modules
    module load intel openmpi

    mpirun ./wrf.exe

Parallel using MPI and OpenMP threads


    # The total number of processes:
    # 128 MPI processes + 2 OpenMP threads/process = 256 cores
    #BSUB -n 128             # processes
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err

    # This will allocate 8 processes per node so we have # 
    # 8 cores per node for the threads                   #
    #BSUB -R "span[ptile=8]"

    # exclusive mode (enabled by default)
    #BSUB -x

    # Then (128 MPI tasks) / (8 tasks/node) = 16 nodes  #
    # reserved                                          #
    # 16 nodes * 16 cores/node = 256 cores allocated    #
    # (Matches the amount of cores asked for above)     #

    #BSUB -J WRF.128-4
    #BSUB -W 02:00

    # Clean your environment modules
    module purge

    # You can choose the parallel environment through
    # modules
    module load intel openmpi

    # 8 MPI processes per node and 16 cpus available 
    # (2 threads per MPI process):
    export OMP_NUM_THREADS=2

    mpirun ./wrf.exe

Parallel using MPI and extra memory

The following example shows how to ask for 3000 MB/task instead of the default 1800 MB/task. As no ‘-R’ options are included it will still put 16 processes on each node, so the Common (2 GB/core) nodes won’t be able to execute this job. This effectively guarantees that either MedMem (128 nodes with 4 GB/core) or HighMem (128 nodes with 8 GB/core) nodes will be used, or a mixture of both.


    # Total number of tasks
    #BSUB -n 128
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err

    # Requesting 3000 MB per task
    # As no ptile is specified, only Medium and High memory nodes
    # are elegible for this execution (max 128 nodes, 2048 cores)
    #BSUB -M 3000

    #BSUB -W 01:00

    module purge
    module load intel openmpi

    mpirun ./my_mpi.exe

The following example requests the same memory per task as the preceding one but it is set to be executed on any nodes. This is done by reducing the amount of tasks per node so the total memory requested by all the tasks in the same node is below the LowMem memory threshold. This would be necessary to execute jobs that need more nodes or cpus than the MedMem and HighMem nodes can provide.


    # Total number of tasks
    #BSUB -n 128
    #BSUB -oo output_%J.out
    #BSUB -eo output_%J.err

    # Requesting 3000 MB per task
    #BSUB -M 3000

    # Only 9 task per node.
    # All compute nodes are available for execution
    #BSUB -R "span[ptile=9]"

    #BSUB -W 01:00

    module purge
    module load intel openmpi

    mpirun ./my_mpi.exe

Queues ↩

There are several queues present in the machines and different users may access different queues. All queues have different limits in amount of cores for the jobs and duration. You can check anytime all queues you have access to and their limits using:

    % bsc_queues

Check BSC Commands for more information.

Sequential executions

For any job that requires a node or less resources, the sequential queue is automatically applied. This queue is the only one that uses the same node for more than one job at a time. It also has the least priority in the machine and the number of concurrently executed sequential jobs is limited to avoid disturbing large jobs’ execution.

If you request 16 processes per node or use -x option, the full node will be assigned to your job. If you have memory problems, mind to specify the exclusive flag because just specifying a ptile may still share the node with other users.

Software Environment ↩

All software and numerical libraries available at the cluster can be found at /apps/. If you need something that is not there please contact us to get it installed (see Getting Help).

C Compilers ↩

In the cluster you can find these C/C++ compilers :

icc / icpc -> Intel C/C++ Compilers

    % man icc
    % man icpc

gcc /g++ -> GNU Compilers for C/C++

    % man gcc
    % man g++

All invocations of the C or C++ compilers follow these suffix conventions for input files:

.C, .cc, .cpp, or .cxx -> C++ source file.
.c -> C source file
.i -> preprocessed C source file
.so -> shared object file
.o -> object file for ld command
.s -> assembler source file

By default, the preprocessor is run on both C and C++ source files.

These are the default sizes of the standard C/C++ datatypes on the machine

Default datatype sizes on the machine
Type Length (bytes)
bool (c++ only) 1
char 1
wchar_t 4
short 2
int 4
long 8
float 4
double 8
long double 16

Distributed Memory Parallelism

To compile MPI programs it is recommended to use the following handy wrappers: mpicc, mpicxx for C and C++ source code. You need to choose the Parallel environment first: module load openmpi / module load impi / module load poe. These wrappers will include all the necessary libraries to build MPI applications without having to specify all the details by hand.

    % mpicc a.c -o a.exe
    % mpicxx a.C -o a.exe 

Shared Memory Parallelism

OpenMP directives are fully supported by the Intel C and C++ compilers. To use it, the flag -qopenmp must be added to the compile line.

    % icc -qopenmp -o exename filename.c
    % icpc -qopenmp -o exename filename.C

You can also mix MPI + OPENMP code using -openmp with the mpi wrappers mentioned above.

Automatic Parallelization

The Intel C and C++ compilers are able to automatically parallelize simple loop constructs, using the option “-parallel” :

    % icc -parallel a.c

FORTRAN Compilers ↩

In the cluster you can find these compilers :

ifort -> Intel Fortran Compilers

    % man ifort

gfortran -> GNU Compilers for FORTRAN

    % man gfortran

By default, the compilers expect all FORTRAN source files to have the extension “.f”, and all FORTRAN source files that require preprocessing to have the extension “.F”. The same applies to FORTRAN 90 source files with extensions “.f90” and “.F90”.

Distributed Memory Parallelism

In order to use MPI, again you can use the wrappers mpif77 or mpif90 depending on the source code type. You can always man mpif77 to see a detailed list of options to configure the wrappers, ie: change the default compiler.

    % mpif77 a.f -o a.exe

Shared Memory Parallelism

OpenMP directives are fully supported by the Intel Fortran compiler when the option “-qopenmp” is set:

    % ifort -qopenmp 

Automatic Parallelization

The Intel Fortran compiler will attempt to automatically parallelize simple loop constructs using the option “-parallel”:

    % ifort -parallel

Modules Environment ↩

The Environment Modules package ( provides a dynamic modification of a user’s environment via modulefiles. Each modulefile contains the information needed to configure the shell for an application or a compilation. Modules can be loaded and unloaded dynamically, in a clean fashion. All popular shells are supported, including bash, ksh, zsh, sh, csh, tcsh, as well as some scripting languages such as perl.

Installed software packages are divided into five categories:

Modules tool usage

Modules can be invoked in two ways: by name alone or by name and version. Invoking them by name implies loading the default module version. This is usually the most recent version that has been tested to be stable (recommended) or the only version available.

    % module load intel

Invoking by version loads the version specified of the application. As of this writing, the previous command and the following one load the same module.

    % module load intel/2017.1

The most important commands for modules are these:

You can run “module help” any time to check the command’s usage and options or check the module(1) manpage for further information.

BSC Commands ↩

The Support team at BSC has provided some commands useful for user’s awareness and ease of use in our HPC machines. These commands are available through a special module (bsc/current) loaded at the beginning of any session. A short summary of these commands follows:

You can check more information about these commands through any of the following manpages:

% man bsc_commands
% man bsc_jobs
% man bsc

TotalView ↩

TotalView is a graphical portable powerful debugger from Rogue Wave Software designed for HPC environments. It also includes MemoryScape and ReverseEngine. It can debug one or many processes and/or threads. It is compatible with MPI, OpenMP, Intel Xeon Phi and CUDA.

Users can access to the latest version of TotalView 8.13 installed in:


Important: Remember to access with ssh -X to the cluster and submit the jobs to x11 queue since TotalView uses a single window control.

There is a Quick View of TotalView available for new users. Further documentation and tutorials can be found on their website or in the cluster at:


Tracing jobs with BSC Tools ↩

In this section you will find an introductory guide to get execution traces in Nord. The tracing tool Extrae supports many different tracing mechanisms, programming models and configurations. For detailed explanations and advanced options, please check the complete Extrae User Guide

The most recent stable version of Extrae is always located at:


This package is compatible with the default MPI runtime in Nord (OpenMPI). Packages corresponding to older versions and enabling compatibility with other MPI runtimes (IntelMPI, MVAPICH) can be respectively found under this directory structure:


In order to trace an execution, you have to load the module extrae and write a script that sets the variables to configure the tracing tool. Let’s call this script It must be executable (chmod +x ./ Then your job needs to run this script before executing the application.

Example for MPI jobs:

#BSUB -n 128 
#BSUB -o output_%J.out 
#BSUB -e output_%J.err 
#BSUB -R "span[ptile=16]" 
#BSUB -J  job_name
#BSUB -W 00:10

module load extrae

mpirun ./ ./app.exe

Example for threaded (OpenMP or pthreads) jobs:

#BSUB -n 1 
#BSUB -oo output_%J.out 
#BSUB -eo output_%J.err 
#BSUB -J job_name 
#BSUB -W 00:10 

module load extrae

./ ./app.exe

Example of script:


export EXTRAE_CONFIG_FILE=./extrae.xml
export LD_PRELOAD=${EXTRAE_HOME}/lib/<tracing-library>


Job Type Tracing library An example to get started
MPI (C codes) (Fortran Codes)
OmpSs - OMPSS/job.lsf
*Sequential job (manual instrumentation) SEQ/
**Automatic instrumentation of user
functions and parallel runtime calls
- SEQ/

* Jobs that make explicit calls to the Extrae API do not load the tracing library via LD_PRELOAD, but link with the libraries instead.

** Jobs using automatic instrumentation via Dyninst neither load the tracing library via LD_PRELOAD nor link with it.

For other programming models and their combinations, check the full list of available tracing libraries at section 1.2.2 of the Extrae User Guide.

Getting help ↩

BSC provides users with excellent consulting assistance. User support consultants are available during normal business hours, Monday to Friday, 09 a.m. to 18 p.m. (CEST time).

User questions and support are handled at:

If you need assistance, please supply us with the nature of the problem, the date and time that the problem occurred, and the location of any other relevant information, such as output files. Please contact BSC if you have any questions or comments regarding policies or procedures.

Our address is:

Barcelona Supercomputing Center – Centro Nacional de Supercomputación
C/ Jordi Girona, 31, Edificio Capilla 08034 Barcelona

Frequently Asked Questions (FAQ) ↩

You can check the answers to most common questions at BSC’s Support Knowledge Center. There you will find online and updated versions of our documentation, including this guide, and a listing with deeper answers to the most common questions we receive as well as advanced specific questions unfit for a general-purpose user guide.

Appendices ↩


SSH is a program that enables secure logins over an insecure network. It encrypts all the data passing both ways, so that if it is intercepted it cannot be read. It also replaces the old an insecure tools like telnet, rlogin, rcp, ftp,etc. SSH is a client-server software. Both machines must have ssh installed for it to work.

We have already installed a ssh server in our machines. You must have installed an ssh client in your local machine. SSH is available without charge for almost all versions of UNIX (including Linux and MacOS X). For UNIX and derivatives, we recommend using the OpenSSH client, downloadable from, and for Windows users we recommend using Putty, a free SSH client that can be downloaded from Otherwise, any client compatible with SSH version 2 can be used.

This section describes installing, configuring and using the client on Windows machines. No matter your client, you will need to specify the following information:

For example with putty client:

Putty client
Putty client

This is the first window that you will see at putty startup. Once finished, press the Open button. If it is your first connection to the machine, your will get a Warning telling you that the host key from the server is unknown, and will ask you if you are agree to cache the new host key, press Yes.

Putty certificate security alert
Putty certificate security alert

IMPORTANT: If you see this warning another time and you haven’t modified or reinstalled the ssh client, please do not log in, and contact us as soon as possible (see Getting Help).

Finally, a new window will appear asking for your login and password:

Cluster login
Cluster login

Transferring files ↩

To transfer files to or from the cluster you need a secure ftp (sftp) o secure copy (scp) client. There are several different clients, but as previously mentioned, we recommend using of Putty clients for transferring files: psftp and pscp. You can find it at the same web page as Putty (

Some other possible tools for users requiring graphical file transfers could be:


You will need a command window to execute psftp (press start button, click run and type cmd). The program first asks for the machine name (, and then for the username and password. Once you are connected, it’s like a Unix command line.

With command help you will obtain a list of all possible commands. But the most useful are:

You will be able to copy files from your local machine to the cluster, and from the cluster to your local machine. The syntax is the same that cp command except that for remote files you need to specify the remote machine:

Copy a file from the cluster:
> pscp.exe local_file
Copy a file to the cluster:
> pscp.exe local_file

Using X11 ↩

In order to start remote X applications you need and X-Server running in your local machine. Here is a list of most common X-servers for windows:

The only Open Source X-server listed here is Cygwin/X, you need to pay for the others.

Once the X-Server is running run putty with X11 forwarding enabled:

Putty X11 configuration
Putty X11 configuration