Registering service ports

By default, port numbers for LSF services are defined in the lsf.conf file. You can also configure ports by modifying the /etc/services file or the NIS or NIS+ database. If you define port numbers in the lsf.conf file, port numbers that are defined in the service database are ignored.

About this task

LSF uses dedicated UDP and TCP ports for communication. All hosts in the cluster must use the same port numbers to communicate with each other.

The service port numbers can be any numbers 1024 - 65535 that are not already used by other services.

Procedure

Ensure that the port numbers you supply are not already used by applications that are registered in your service database by checking the /etc/services file or by using the command ypcat services

lsf.conf

About this task

Procedure

Log on to any host as root.

Edit the lsf.conf file and add the following lines:

LSF_RES_PORT=3878
LSB_MBD_PORT=3881
LSB_SBD_PORT=3882

Add the same entries to the lsf.conf file on every host.
Save the lsf.conf file.
Run the lsadmin reconfig command to reconfigure LIM.
Run the badmin mbdrestart command to restart the mbatchd daemon.
Run the lsfstartup command to restart all daemons in the cluster.

/etc/services

Configuring services manually

About this task

Tip: During installation, use the hostsetup --boot="y" option to set up the LSF port numbers in the service database.

Procedure

Use the LSF_TOP/version/install/instlib/example.services file as a guide for adding LSF entries to the services database.

If any other service that is listed in your services database has the same port number as one of the LSF services, you must change the port number for the LSF service. You must use the same port numbers on every LSF host.
Log on to any host as root.

Edit the /etc/services file and add the contents of the LSF_TOP/version/install/instlib/example.services file:

# /etc/services entries for LSF daemons
#
res     3878/tcp # remote execution server
lim     3879/udp # load information manager
mbatchd 3881/tcp # management lsbatch daemon
sbatchd 3882/tcp # server lsbatch daemon
#
# Add this if ident is not already defined
# in your /etc/services file
ident 113/tcp auth tap # identd

Run the lsadmin reconfig command to reconfigure LIM.
Run the badmin reconfig command to reconfigure mbatchd.
Run the lsfstartup command to restart all daemons in the cluster.

NIS or NIS+ databases

About this task

If you are running NIS, you need to modify the services database only one time per NIS management host. On some hosts, the NIS database and commands are in the /var/yp directory; on others, NIS is found in the /etc/yp directory.

Procedure

Log on to any host as root.
Run the lsfshutdown command to shut down all the daemons in the cluster.
To find the name of the NIS management host, use the ypwhich -m servicescommand.
Log on to the NIS management host as root.

Edit the /var/yp/src/services or /etc/yp/src/services file on the NIS management host and add the contents of the LSF_TOP/version/install/instlib/example.services file:

# /etc/services entries for LSF daemons.
#
res     3878/tcp # remote execution server
lim     3879/udp # load information manager
mbatchd 3881/tcp # management lsbatch daemon
sbatchd 3882/tcp # server lsbatch daemon
#
# Add this if ident is not already defined
# in your /etc/services file
ident 113/tcp auth tap # identd

Ensure that all the lines you add either contain valid service entries or begin with a comment character (#). Blank lines are not allowed.

Change the directory to /var/yp or /etc/yp.
Run the ypmake services command.

On some hosts, the primary copy of the services database is stored in a different location.

On systems that run NIS+, the procedure is similar. For more information, see your system documentation.
Run the lsadmin reconfig command to reconfigure LIM.
Run the badmin reconfig command to reconfigure the mbatchd daemon.
Run the lsfstartup command to restart all daemons in the cluster.