HP XC System Software Administration Guide Version 3.1

• When LSF-HPC with SLURM failover is disabled and the LSF execution host (which is not the head
node) goes down, issue the controllsf command to restart LSF-HPC with SLURM on the HP XC
system:
# controllsf start
• When failover is enabled, you need to intervene only when the primary LSF execution host is not
started on HP XC system startup (when the startsys command is run). Use the controllsf
command to restart LSF-HPC with SLURM.
# controllsf start
• When starting LSF-HPC with SLURM after a partial system shutdown, LSF is started on the head
node if:
— LSF failover is enabled.
— The head node has the resource management role and no other resource management node is
up.
— The head node has the resource management role and the enable headnode preferred
subcommand is set.
— LSF-HPC with SLURM was not shut down cleanly, perhaps as a result of running startsys
without running service lsf stop or controllsf stop on the head node.
— LSF-HPC with SLURM starts on the head node if the other resource management nodes are
unavailable
• LSF-HPC with SLURM failover may select the node that it just released.
LSF-HPC with SLURM failover attempts to ensure that a different node is used after it removes
control from the present node. However, if all other options are exhausted, LSF-HPC with SLURM
failover tries the current node again before giving up.
If you are trying to perform load balancing, log in to the primary LSF execution host node and execute
the controllsf start here command from that node.
242 Troubleshooting