Platform LSF Administration Guide Version 6.2

Chapter 4
Working with Hosts
Administering Platform LSF
113
Host Naming
LSF needs to match host names with the corresponding Internet host addresses.
LSF looks up host names and addresses the following ways:
◆ In the /etc/hosts file
◆ Sun Network Information Service/Yellow Pages (NIS or YP)
◆ Internet Domain Name Service (DNS).
DNS is also known as the Berkeley Internet Name Domain (BIND) or
named,
which is the name of the BIND daemon.
Each host is configured to use one or more of these mechanisms.
Network addresses
Each host has one or more network addresses; usually one for each network to which
the host is directly connected. Each host can also have more than one name.
Official host name
The first name configured for each address is called the official name.
Host name aliases
Other names for the same host are called aliases.
LSF uses the configured host naming system on each host to look up the official host
name for any alias or host address. This means that you can use aliases as input to LSF,
but LSF always displays the official name.
Using host name ranges as aliases
The default host file syntax
ip_address official_name [ alias [ alias ...]]
is powerful and flexible, but it is difficult to configure in systems where a single host
name has many aliases, and in multihomed host environments.
In these cases, the
hosts file can become very large and unmanageable, and
configuration is prone to error.
The syntax of the LSF
hosts file supports host name ranges as aliases for an IP address.
This simplifies the host name alias specification.
To use host name ranges as aliases, the host names must consist of a fixed node group
name prefix and node indices, specified in a form like:
host_name [ index_x - index_y , index_m , index_a-index_b ]
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:
...