LSF Version 7.3 - Using Platform LSF HPC

❖ On SGI IRIX: LSF_VPLUGIN="/usr/lib32/libxmpi.so"
❖ On SGI Altix: LSF_VPLUGIN="/usr/lib/libxmpi.so"
You can specify multiple paths for LSF_VPLUGIN, separated by colons (:). For
example, the following configures both
/usr/lib32/libxmpi.so for SGI
IRIX, and
/usr/lib/libxmpi.so for SGI IRIX:
LSF_VPLUGIN="/usr/lib32/libxmpi.so:/usr/lib/libxmpi.so"
◆ LSF_PAM_USE_ASH=Y enables LSF to use the SGI Array Session Handler
(ASH) to propagate signals to the parallel jobs.
See the SGI system documentation and the
array_session(5) man page for
more information about array sessions.
For PAM to access the libxmpi.so library, the file permission mode must be 755
(
-rwxr-xr-x).
For PAM jobs on Altix, the SGI Array Services daemon arrayd must be running and
AUTHENTICATION must be set to NONE in the SGI array services authentication
file
/usr/lib/array/arrayd.auth (comment out the AUTHENTICATION
NOREMOTE method and uncomment the AUTHENTICATION NONE method).
To run a mulithost MPI applications, you must also enable
rsh without password
prompt between hosts:
◆ The remote host must defined in the arrayd configuration.
◆ Configure .rhosts so that rsh does not require a password.
The pam command
The pam command invokes the Platform Parallel Application Manager (PAM) to run
parallel batch jobs in LSF. It uses the
mpirun library and SGI array services to spawn
the child processes needed for the parallel tasks that make up your MPI application. It
starts these tasks on the systems allocated by LSF. The allocation includes the number
of execution hosts needed, and the number of child processes needed on each host.
The -mpi option on the bsub and pam command line is equivalent to mpirun in the
SGI environment.
The -auto_place option on the pam command line tells the mpirun library to launch
the MPI application according to the resources allocated by LSF.
The -n option on the pam command line specifies the number of tasks that PAM should
start.
You can use both
bsub -n and pam -n in the same job submission. The number
specified in the
pam -n option should be less than or equal to the number specified by
bsub -n. If the number of tasks specified with pam -n is greater than the number
specified by
bsub -n, the pam -n is ignored.
For example, you can specify:
bsub -n 5 pam -n 2 -mpi a.out
Here, the job requests 5 processors, but PAM only starts 2 parallel tasks.