Add a dynamic host in a non-shared file system environment

In a non-shared file system environment, you must install LSF binaries, a localized lsf.conf file, and shell environment scripts (cshrc.lsf and profile.lsf) on each dynamic host.

Specify installation options in the slave.config file

All dynamic hosts are slave hosts because they cannot serve as master host candidates. The slave.config file contains parameters for configuring all slave hosts.


  1. Define the required parameters.

    LSF_SERVER_HOSTS="host_name [host_name ...]"

    LSF_ADMINS="user_name [ user_name ... ]"


  2. Define the optional parameters.



    If the master host does not use the default LSF_LIM_PORT, you must specify the same LSF_LIM_PORT defined in lsf.conf on the master host.

Add local resources on a dynamic host to the cluster

Before you begin

Ensure that the resource name and type are defined in lsf.shared, and that the ResourceMap section of lsf.cluster.cluster_name contains at least one resource mapped to at least one static host. LSF can add local resources as long as the ResourceMap section is defined; you do not need to map the local resources.


In the slave.config file, define the parameter LSF_LOCAL_RESOURCES.
For numeric resources, define name-value pairs:
"[resourcemap value*resource_name]"
For Boolean resources, the value is the resource name in the following format:
"[resource resource_name]"
For example:
LSF_LOCAL_RESOURCES="[resourcemap 1*verilog] [resource linux]"

If LSF_LOCAL_RESOURCES are already defined in a local lsf.conf on the dynamic host, lsfinstall does not add resources you define in LSF_LOCAL_RESOURCES in slave.config.

When the dynamic host sends a request to the master host to add it to the cluster, the dynamic host also reports its local resources. If the local resource is already defined in lsf.cluster.cluster_name as default or all, it cannot be added as a local resource.

Install LSF on a dynamic host


Run lsfinstall -s -f slave.config.

lsfinstall creates a local lsf.conf for the dynamic host, which sets the following parameters:



LSF_LIM_PORT=port_number (same as the master LIM port number)

LSF_LOCAL_RESOURCES="resource ..."

Do not duplicate LSF_LOCAL_RESOURCES entries in lsf.conf. If local resources are defined more than once, only the last definition is valid.

LSF_SERVER_HOSTS="host_name [host_name ...]"


If LSF_STRICT_CHECKING is defined in lsf.conf to protect your cluster in untrusted environments, and your cluster has dynamic hosts, LSF_STRICT_CHECKING must be configured in the local lsf.conf on all dynamic hosts.

Configure dynamic host parameters


  1. In lsf.conf on the master host, define the parameter LSF_DYNAMIC_HOST_WAIT_TIME, in seconds, and assign a value greater than zero.

    LSF_DYNAMIC_HOST_WAIT_TIME specifies the length of time a dynamic host waits before sending a request to the master LIM to add the host to the cluster.

    For example:
  2. In lsf.conf on the master host, define the parameter LSF_DYNAMIC_HOST_TIMEOUT.
    LSF_DYNAMIC_HOST_TIMEOUT specifies the length of time (minimum 10 minutes) a dynamic host is unavailable before the master host removes it from the cluster. Each time LSF removes a dynamic host, mbatchd automatically reconfigures itself.

    For very large clusters, defining this parameter could decrease system performance.

    For example:
  3. In lsf.cluster.cluster_name on the master host, define the parameter LSF_HOST_ADDR_RANGE.
    LSF_HOST_ADDR_RANGE enables security by defining a list of hosts that can join the cluster. Specify IP addresses or address ranges for hosts that you want to allow in the cluster.

    If you define the parameter LSF_ENABLE_SUPPORT_IPV6 in lsf.conf, IP addresses can have either a dotted quad notation (IPv4) or IP Next Generation (IPv6) format; you do not have to map IPv4 addresses to an IPv6 format.

    For example:

    All hosts belonging to a domain with an address having the first number between 100 and 110, then 34, then a number between 1 and 10, then, a number between 4 and 56 will be allowed access. No IPv6 hosts are allowed.

Start LSF daemons


  1. Log on as root to each host you want to join the cluster.
  2. Source the LSF environment:
    • For csh or tcsh:
      source LSF_TOP/conf/cshrc.lsf
    • For sh, ksh, or bash:
      . LSF_TOP/conf/profile.lsf
  3. Do you want LSF to start automatically when the host reboots?
    • If no, go to the next step.

    • If yes, run the hostsetup command. For example:
      cd /usr/share/lsf/9.1/install
      ./hostsetup --top="/usr/share/lsf" --boot="y"

    For complete hostsetup usage, enter hostsetup -h.

  4. Is this the first time the host is joining the cluster?
    • If no, use the following commands to start LSF:
      lsadmin limstartup
      lsadmin resstartup
      badmin hstartup
    • If yes, you must start the daemons from the local host. For example, if you want to start the daemons on hostB from hostA, use the following commands:
      rsh hostB lsadmin limstartup
      rsh hostB lsadmin resstartup
      rsh hostB badmin hstartup