HP XC System Software Administration Guide Version 3.1

XC_LIBLIC=/opt/hptc/lib/libsyslic.so
c. Make sure the LSF_NON_PRIVILEGED_PORTS option is disabled or removed from this file ('N'
by default).
In Standard LSF Version 6.2 this is not supported, and you will get "bad port" messages from
the sbatchd and mbatchd daemons on a non-HP XC system node.
d. If you use ssh for node-to-node communication, set the following variable in lsf.conf (assuming
the ssh keys have been set up to allow access without a password):
LSF_RSH=ssh
e. Save the file and exit the text editor.
5. Optional: Configure any special queues specific to HP XC.
XC V2.1 recommends the use of a JOB_STARTER script to be configured for all queues on a HP XC
system. The default installation of LSF on the HP XC system provides default queue configurations
which can be found here: /opt/hptc/lsf/etc/configdir/lsb.queues. The JOB_STARTER
script and its helper scripts can be found in /opt/hptc/lsf/bin/ and may need to be moved to a
shared location depending on how they are configured for use. If they are moved, be sure to edit the
job_starter.sh script and update the loc definition, which provides the location of the helper
scripts.
The intent of the JOB_STARTER script is to handle the case in which a job is launched on a non-HP
XC system node with minimal impact, so it can be configured on all queues. Use good judgement in
employing this script on your system.
6. Optional: Adjust the LSF environment files if necessary
When a new or different version of LSF is installed, it renames the old profile.lsf and cshrc.lsf
files before replacing them with the files from the most recent installation.
Ensure that these files are consistent with the HP XC default LSF environment files as configured
above.
A.7 Configuring the LSF Alias
Now that LSF has been installed, log out and log back into the HP XC system to establish the proper LSF
environment.
The next step is to configure the LSF alias on the HP XC system. An alias is used on the HP XC system to
prevent hard-wiring LSF to any one node, so that the LSF node in HP XC can fail over to another node if
the current node becomes compromised (hung or crashed). HP XC provides infrastructure to monitor the
LSF node and fail over the LSF daemons to another node if necessary.
The selected IP and host name must not be in use but must be known on the external network. Our example
is using xclsf with an IP address of '16.32.2.140', and the head node for the HP XC system is xc-head.
Use the ping command to verify that the selected external host name is not currently in use:
# ping xclsf
PING xclsf.lab.example.com (IP address) 56(84) bytes of data.
From xc128.lab.example.com (IP address) icmp_seq=0
Destination Host Unreachable
Next configure controllsf (which manages LSF setup on HP XC) with the new alias:
# controllsf set virtual hostname xclsf
Confirm that the alias is set:
# controllsf show
LSF is currently shut down, and assigned to node .
Failover is disabled.
Head node is preferred.
The primary LSF host node is xc128.
SLURM affinity is enabled.
The virtual hostname is "xclsf".
260 Installing LSF-HPC with SLURM into an Existing Standard LSF Cluster