IBM LoadLeveler installation and customization

(GSI only)

Server installation

Applies only to a machine which should serve as LoadLeveler repository and/or central manager

for V2.2
- Install straightforward from CD
- Generic fix LoadL.so.2.2.0.23.bff
- Generic fix LoadL.full.2.2.0.23.bff ?
- Generic fix LoadL.full.2.2.0.24.bff
for V3.1
- Install straightforward from CD
- fixes from IBM page
Choose a special account, e.g. biodev as LoadLeveler user id.

Adapt the central config file, e.g. /u/biodev/LoadL_config,

ARCH = R6000
OPSYS= AIX43||AIX51||AIX52||AIX53
LOADL_ADMIN = ... list of admin accounts
ADMIN_FILE  = /u/biodev/LoadL_admin

and other general definitions.

Adapt the central admin file (e.g. /u/biodev/LoadL_admin) to include the machines under LL control and the possible job classes.

Client configuration

V2.2

(Currently used version, administered by biophysics)

The LL relevant binaries must be mounted according to the following entry in /etc/filesystems

   /usr/lpp/LoadL:
           dev             = "/usr/lpp/LoadL"
           vfs             = nfs
           nodename        = biops5z
           mount           = true
           options         = ro,bg,soft,intr
           account         = false

and for immediate usage:

   mkdir -p /usr/lpp/LoadL/
   mount -a

the following links must exist

   ln -s /usr/lpp/LoadL/full/lib/libllapi.a /usr/lib/libllapi.a
   ln -s /usr/lpp/LoadL/full/lib/libllmulti.a /usr/lib/libllmulti.a
   ln -s /usr/lpp/LoadL/full/lib/llapi_shr.o /usr/lib/llapi_shr.o

as well as the directories

   mkdir -p /var/loadl/execute
   mkdir -p /var/loadl/log
   mkdir -p /var/loadl/spool

a local configuration file /var/loadl/LoadL_config.local should exist. Adapt the following entries (example):
- for a 1 CPU machine:
```
BackgroundLoad  = 1.0
HighLoad        = 1.5
MAX_STARTERS    = 1
```
- for a 2 CPU machine:
```
BackgroundLoad  = 2.0
HighLoad        = 2.5
MAX_STARTERS    = 2
```
- for a 4 CPU machine:
```
BackgroundLoad  = 4.0
HighLoad        = 4.5
MAX_STARTERS    = 4
```
where the last line determines the number of simultaneous jobs possible.
in /etc/rc.local
```
#
# start LoadLeveler
#
/usr/lpp/LoadL/full/bin/llctl start
```
to start the LoadLeveler on boot. Outcomment this line when LoadLeveler should not run.

The file /etc/LoadL.cfg must exist, with entries e.g.:

   LoadLUserid = biodev
   LoadLGroupid = bio
   LoadLConfig = /u/biodev/LoadL_config

Update the ADMIN_FILE (see above, Server installation) to include the new machine.
To allow management via ll commands or xloadl, the rshd service must be (re-)enabled in /etc/inetd.conf, but access should be restricted to root in /.rhosts to the managing machine only.

V1.3

(centrally administered, obsolete, for reference only)

these directories are necessary:

mkdir /var/loadl
mkdir /var/loadl/execute
mkdir /var/loadl/log
mkdir /var/loadl/spool
mkdir /usr/lpp/LoadL
mkdir /usr/lpp/LoadL/nfs
/usr/bin/ln -s /usr/lpp/LoadL/nfs/lib/libjm_clientll.a /usr/lib/libjm_clientll.a
/usr/bin/ln -s /usr/lpp/LoadL/nfs/lib/libSDRll.a /usr/lib/libSDRll.a

in /etc/filesystems:

/usr/lpp/LoadL/nfs:
        dev             = "/usr/lpp/LoadL/nfs/ll13nfs43"
        vfs             = nfs
        nodename        = filesv1
        mount           = true
        options         = bg,soft,intr
        account         = false

(Note that the filesystem must be exported on filesv1)

in /etc/rc.local
```
#start LoadLeveler
/usr/lpp/LoadL/nfs/bin/llctl start
```
to start the LoadLeveler on boot. Outcomment this line when LoadLeveler should not run.
Copy the configuration file /var/loadl/LoadL_config.local from an already installed machine. Adapt the following entries:
- for a 1 CPU machine:
```
BackgroundLoad  = 2.0
HighLoad        = 2.5
MAX_STARTERS    = 1
```
- for a 2 CPU machine:
```
BackgroundLoad  = 2.0
HighLoad        = 2.5
MAX_STARTERS    = 2
```
- for a 4 CPU machine:
```
BackgroundLoad  = 4.0
HighLoad        = 4.5
MAX_STARTERS    = 4
```
where the last line determines the number of simultaneous jobs.

You use

mount -a           # mounts the LoadL filesystems from /etc/filesystems
llctl reconfig

to activate the changes immediately

Last update: 9-May-2013, M.Kraemer

Impressum Data privacy protection