LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 87
Working with Hosts
For example:
atlasD0[0-3,4,5-6, ...]
is equivalent to:
atlasD0[0-6, ...]
The node list does not need to be a continuous range (some nodes can be
configured out). Node indices can be numbers or letters (both upper case and lower
case).
Example Some systems map internal compute nodes to single LSF host names. A host file
might contains 64 lines, each specifying an LSF host name and 32 node names that
correspond to each LSF host:
...
177.16.1.1 atlasD0 atlas0 atlas1 atlas2 atlas3 atlas4 ... atlas31
177.16.1.2 atlasD1 atlas32 atlas33 atlas34 atlas35 atlas36 ... atlas63
...
In the new format, you still map the nodes to the LSF hosts, so the number of lines
remains the same, but the format is simplified because you only have to specify
ranges for the nodes, not each node individually as an alias:
...
177.16.1.1 atlasD0 atlas[0-31]
177.16.1.2 atlasD1 atlas[32-63]
...
You can use either an IPv4 or an IPv6 format for the IP address (if you define the
parameter LSF_ENABLE_SUPPORT_IPV6 in
lsf.conf).
Host name services
Solaris On Solaris systems, the /etc/nsswitch.conf file controls the name service.
Other UNIX
platforms
On other UNIX platforms, the following rules apply:
◆ If your host has an /etc/resolv.conf file, your host is using DNS for name
lookups
◆ If the command ypcat hosts prints out a list of host addresses and names,
your system is looking up names in NIS
◆ Otherwise, host names are looked up in the /etc/hosts file
For more information
The man pages for the gethostbyname function, the ypbind and named daemons,
the
resolver functions, and the hosts, svc.conf, nsswitch.conf, and
resolv.conf files explain host name lookups in more detail.