Register service ports

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 ranging from 1024 to 65535 that are not already used by other services.

Procedure

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

lsf.conf

About this task

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

Procedure

  1. Log on to any host as root.
  2. Edit lsf.conf and add the following lines:
    LSF_RES_PORT=3878
    LSB_MBD_PORT=3881
    LSB_SBD_PORT=3882
  3. Add the same entries to lsf.conf on every host.
  4. Save lsf.conf.
  5. Run lsadmin reconfig to reconfigure LIM.
  6. Run badmin mbdrestart to restart mbatchd.
  7. Run lsfstartup to restart all daemons in the cluster.

/etc/services

Configure 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

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

    If any other service 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.

  2. Log on to any host as root.
  3. Edit the /etc/services file by adding 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 # master lsbatch daemon
    sbatchd 3882/tcp # slave lsbatch daemon
    #
    # Add this if ident is not already defined
    # in your /etc/services file
    ident 113/tcp auth tap # identd
  4. Run lsadmin reconfig to reconfigure LIM.
  5. Run badmin reconfig to reconfigure mbatchd.
  6. Run lsfstartup to restart all daemons in the cluster.

NIS or NIS+ database

About this task

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

Procedure

  1. Log on to any host as root.
  2. Run lsfshutdown to shut down all the daemons in the cluster
  3. To find the name of the NIS master host, use the command:
    ypwhich -m services
  4. Log on to the NIS master host as root.
  5. Edit the /var/yp/src/services or /etc/yp/src/services file on the NIS master host adding 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 # master lsbatch daemon
    sbatchd 3882/tcp # slave lsbatch daemon
    #
    # Add this if ident is not already defined
    # in your /etc/services file
    ident 113/tcp auth tap # identd

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

  6. Change the directory to /var/yp or /etc/yp.
  7. Use the following command:
    ypmake services

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

    On systems running NIS+ the procedure is similar. Refer to your system documentation for more information.

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